13 October 2011, 13:28 | #1 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
P96 Piccolo SD64
For a long time I've had problems running most whdload games through my WB, but they all work on a minimal startup.
Yesterday I decided to find out what exactly was causing the issue and got it down to the P96 driver for my Piccolo SD64. As soon as I remove that from devs/monitors, whdload works normally. Any experience with this out there? I've tried different screen modes and some of the tooltype options (both whdload and the driver), but no luck so far. Note: I should mention I'm using WHDLoad 17.0 Last edited by slk486; 13 October 2011 at 14:51. |
13 October 2011, 14:01 | #2 |
Moderator
Join Date: Nov 2001
Location: Germany
Posts: 869
|
maybe some kind of screen promoting?
|
13 October 2011, 14:05 | #3 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
As far as I know there's no screen promoting going on. Fake Native Modes are disabled, but maybe there is something I'm not aware of?
As examples, CD32 version of Disposable Hero works fine in a clean boot, but running from WB it freezes with white garbage on screen at the start, needing to restart Amiga, while the disk version (non fast) displays the console intro, but then doesn't go beyond the Gremlin logo, but can be quit to wb. Last edited by slk486; 13 October 2011 at 14:37. Reason: better example explanation |
13 October 2011, 14:34 | #4 |
Moderator
Join Date: Nov 2001
Location: Germany
Posts: 869
|
are you sure FakeNativeModes are set to NO?
|
13 October 2011, 14:36 | #5 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
Yeah, only tooltypes set to YES are DisplayChain and IgnoreMask (which I've tried as NO also).
|
13 October 2011, 14:40 | #6 |
Moderator
Join Date: Nov 2001
Location: Germany
Posts: 869
|
then I have no idea.
either the custom registers are not correctly initialized via OpenScreen or there is an hardware interrupt running by the card |
13 October 2011, 14:46 | #7 | |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
Quote:
There must be others with a Piccolo SD64 using WHDLoad surely? |
|
13 October 2011, 16:55 | #8 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
which refresh rate did you click when installing the driver?
|
13 October 2011, 18:00 | #9 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
|
13 October 2011, 18:59 | #10 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
ok can you tell us the following....
which os are you using? whats in your prefs/env-archive/piccasso96 drawer and the settings of each file? can you tell us whats in your monitor driver icon info? |
13 October 2011, 20:38 | #11 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
WB3.1
envarc: picasso96 drawer: AlertSupport: Yes AmigaVideo: 15khz AreaEndSupport: Yes BlackSwitching: No Debug: No DirectColorMask: No DisableAmigaBlitter: No DoNotSetMMU: No EnableBootVGA: No Experimental: No PlanarOnlyDBuf: No PlanarOnlyDIPFDBUF: No PlanesToFast: No ShowModes: Essential monitor icon info: BigSprite=NO BoardType=PiccoloSD64 DisplayChain=YES FakeNativeModes=NO FontsFix=NO GrantDirectAccess=NO IgnoreMask=YES NoBlitter=NO NoPlanar2ChunkyBlits=NO OverClock=NO SettingsFile=SYS: Devs/Picasso96Settings SoftSprite=NO System2ScreenBlits=NO A4000 with a GVP 060 Currently using Picasso96 2.1c, but same issue with the older version. |
14 October 2011, 09:02 | #12 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
thats really strange,have you got anything in your startup drawer that could be conflicting with it?
something in the startup sequence? you didnt install the printer patch did you? are you using the passthrough cable with the card? sorry for all the questions,just trying to eleminate the obvios. |
14 October 2011, 09:24 | #13 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
It's a ClassicWB P96 base, so there is stuff in the startup-sequence, but I've tried disabling everything except assigns etc, and the only thing that makes a difference is commenting out C:IPrefs, which led me to the P96 driver. Only thing in the WBStartup drawer is freewheel. I'm not sure about the printer patch. I don't see why I would have installed it, but might have clicked wrong on the install I'm Using a custom passthrough cable from an Indivision4000.
Don't be sorry, I'm very happy you're trying to help |
14 October 2011, 09:43 | #14 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
ok ive had an idea,can you do a printout of your startup sequence?
maybe its its not iprefs but where it is in the startup. |
14 October 2011, 09:57 | #15 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
Here it is:
;ClassicWB Startup-Sequence ;-------------------------- ;P96 UAE 3.1 IF EXISTS DEVS:scsi.device C:LoadModule DEVS:scsi.device EndIF C:GetMouseInput LOCAL IF $MouseInput EQ 1 Unset MouseInput C:SetPatch QUIET C:Assign >NIL: ENV: RAM: run >nil: C:MagicWB-Demon 4,123,123,123 5,175,175,175 6,170,144,124 7,255,169,151 8,0,0,255 ; Don't remove this entry! C:Assign >NIL: T: RAM: C:Execute S:Maxmem-Sequence EndCLI >NIL: EndIF IF $MouseInput EQ 2 Unset MouseInput C:Execute S:Bootmenu-Sequence EndCLI >NIL: EndIF Unset MouseInput C:MuMove4K C:SetPatch QUIET IF EXISTS C:StackAttack C:StackAttack EndIF C:Version >NIL: FailAt 21 IF EXISTS SYS:WBstartupD C:Rename >NIL: SYS:WBStartup SYS:WBStartupM C:Rename >NIL: SYS:WBStartupD SYS:WBStartup EndIF Resident >NIL: C:IconX PURE Resident >NIL: C:WBRun PURE Resident >NIL: C:Assign PURE Resident >NIL: C:Execute PURE IF EXISTS L:env-handler C:MakeDir RAM:T RAM:Clipboards L:env-handler C:Copy >NIL: ENVARC:Sys/def_kick.info ENV:Sys/def_kick.info ELSE C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ Assign >NIL: ENV: RAM:ENV EndIF Assign >NIL: T: RAM:T Assign >NIL: CLIPS: RAM:Clipboards Assign >NIL: REXX: S: Assign >NIL: PRINTERS: DEVS:Printers Assign >NIL: KEYMAPS: DEVS:Keymaps Assign >NIL: LOCALE: SYS:Locale Assign >NIL: LIBS: SYS:Classes ADD Assign >NIL: HELP: LOCALE:Help DEFER BindDrivers C:Mount >NIL: DEVSOSDrivers/~(#?.info) IF EXISTS DEVS:Monitors IF EXISTS DEVS:Monitors/VGAOnly DEVS:Monitors/VGAOnly EndIF C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s" Execute T:M Celete >NIL: T:M EndIF SetEnv Language "english" SetEnv Workbench $Workbench SetEnv Kickstart $Kickstart UnSet Workbench UnSet Kickstart IF EXISTS C:IconBeFast C:IconBeFast 0 EndIF C:AddDataTypes REFRESH QUIET C:IPrefs C:ConClip Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities IF EXISTS S:User-Startup Execute S:User-Startup EndIF Resident Execute REMOVE Resident Assign REMOVE IF EXISTS C:StackAttack C:StackAttack AUTO EndIF C:LoadWB EndCLI >NIL: |
14 October 2011, 10:16 | #16 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
ok can you try this first ,remove the first setpatch command,then move iprefs before any call for the monitors
oh and make a backup first.you know the drill. also you have a call for stackattack twice |
14 October 2011, 10:27 | #17 |
BlizzardPPC'less
|
Calling StackAttack twice during startup is stated in the docs. It should be OK.
Try setting BlackSwitching=Yes. |
14 October 2011, 10:32 | #18 |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
thanks, i dont use it.i was unsure about that one thats why i commented on it last.
|
14 October 2011, 10:42 | #19 |
Registered Looser
Join Date: Apr 2010
Location: Denmark
Posts: 336
|
First SetPatch is only if mousebutton is pressed, so that one isn't executed - still removed it though.
Moved C:IPrefs to before the Monitor calls, no difference. @Bamiga2002: Thanks for your input, I appreciate it! BlackSwitching=Yes doesn't help either. Last edited by slk486; 14 October 2011 at 10:47. |
14 October 2011, 10:47 | #20 | |
Registered User
Join Date: Apr 2011
Location: birmingham
Age: 55
Posts: 2,827
|
Quote:
can you make sure that the assigns for p96 in the user startup are at the top of the list? ok iprefs is in the same place as yours on mine,just before conclip im out of ideas here sorry. EDIT:-does your gvp card have to have its own commands in startup? |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ClassicWB P96 in real Amiga? | Retrofan | project.ClassicWB | 20 | 28 May 2011 10:21 |
ClassicWB P96 problem | nsd | project.ClassicWB | 3 | 30 November 2010 17:53 |
No Trash Can on P96 ? | Xeon | project.ClassicWB | 16 | 08 September 2009 16:07 |
Promoting 640x200 with P96 | MagerValp | support.Apps | 1 | 06 September 2009 09:26 |
Classic WB P96 | Anubis | project.ClassicWB | 5 | 08 May 2006 14:30 |
|
|