WHDLoad problem

[starf81]

Hello,

my A3000 (see the sign for the configuration) works like a charm. This happened up to yersteday when WHDLoad - one of my favourite utility - has stopped working.
I explain the issue: after the spash screen, games seems start as usual but after a few seconds they freeze or a blank screen is showed or music is played but there is no graphic on the screen. Pressing the right "exit key" for the game I'm trying to start, the WB screen comes back without any problem.

It is driving me crazy... I can't believe... :boohoo:

Any ideas?

Thank you in advance
Alex

[motorollin]

Make sure your TCP/IP stack isn't running at the same time as WHDLoad. If you have run it, reboot then launch the game.

--
moto

[starf81]

I knew this issue... my stack is not running.
It happens also just after the boot  :-(

Since I've recently installed various WB enhancer, do you know if there are other utilities and/or appz that could create conflicts with WHDLoad?

[motorollin]

Maybe. Try moving all your items out of WBStartup and commenting any patches out of startup-sequence and user-startup and see if the problem goes away. If it does, then re-add things one at a time and re-test after each one.

--
moto

[starf81]

Good idea!
I'm going to try... after tests, I'll let you know!

[starf81]

I've tried to restore old folders (S, C, Libs, Fonts) and files (startup-sequence and user-startup) from a backup I made some days ago. I've also de-activaed files in WBStartup but... WHDLoad doesn't work  :boohoo:  :boohoo:  :boohoo:

[motorollin]

Did you try disabling the items in your WBStartup drawer?

--
moto

[starf81]

Yes, I did...

[motorollin]

Ok, try this. Boot with no startup-sequence, CD to the directory containing a WHDLoad game, and then type ¨C:WHDLoad gamename.slave¨ where gamename.slave is the slave file for the game you want to play. Does that work ok?

--
moto

[starf81]

Yes... it works.

So... WHDLoad is ok but there is something that creates conflicts with it.

[motorollin]

Precisely. So you need to disable everything in your WBStartup drawer, any hacks/patches in startup-sequence and user-startup. Then boot Workbench and see if WHDLoad works. Then re-enable things one at a time to find out what breaks WHDLoad.

--
moto

[starf81]

I've completely disabled WBStartup folder and user-startup.
Nothing has changed... now I'm going to put again my hands on Startup-Sequence...

[motorollin]

Remember only comment lines out by putting a ; at the beginning of the line, so you can replace whatever you remove.

--
moto

[starf81]

Yes, it is what I was doing... :-)

I've tried to disable some lines without success.
Here is my startup-sequence. I put an "*" at the beginning of lines I've disabled.

I'd be grateful if you could take a look... which are lines you'd try to disable?

; $VER: Startup-Sequence_HardDrive 45.2 (19.1.2001)
; Startup-Sequence for AmigaOS 3.9

If EXISTS C:SquirrelSCSI
    C:SquirrelSCSI
EndIf

Set SCSIUpdate 1
If EXISTS C:IDEFix
    C:IDEFix
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Expansion/XSurfIDE
    Set SCSIUpdate 0
EndIf
If EXISTS SYS:Prefs/Env-Archive/NOSCSIUPDATE
    Set SCSIUpdate 0
EndIf

*C:morelibspace

If $SCSIUpdate EQ 1
    SetPatch QUIET
Else
    SetPatch SKIPROMUPDATES "scsi.device" QUIET
EndIf
Unset SCSIUpdate

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
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: DEVS:DOSDrivers/~(#?.info)

C:LoadMonDrvs

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET
*C:AFA_OS_loader
*Run > NIL: "System:Sys/VisualPrefs/VisualPrefs"
*C:IPrefs
*C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

SYS:System/REXXMast >NIL:

IF EXISTS S:User-Startup
  Execute S:User-Startup
EndIF

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:

[motorollin]

Looks like a very standard startup-sequence. Just to confirm, you have disabled user-startup and WBStartup with this ammended startup-sequence?

It might be worth booting with no startup-sequence and just running setpatch, let setpatch reboot the machine, boot with no s-s, run setpatch again, then once again launch the WHDLoad game from the CLI window. This will test whether Setpatch is causing problems with WHDLoad (can't see why, but it doesn't hurt to rule it out).

Finally, are you certain that the libraries for your accelerator are installed correctly?

--
moto