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

[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?

[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:

[starf81]

Yes, I did...

[starf81]

Yes... it works.

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

[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...

[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:

[starf81]

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

Yes... I've renamed WBStartup and user-startup so the system has booted without loading them.

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).

It works perfectly!

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

Just to avoid doubts, I've replaced cpu libs with the ones in the CyberStorm floppy but WHDLoad does not work :-(

[starf81]

girv73 wrote:

I'll hazard a guess that you're getting an interrupt from some of your add-on hardware and it's causing confusion - this happens quite a lot on Mediator equipped A1200s, for example.

Booting without startup-sequence is perhaps not initialising the hardware (eg: gfx card?), so you're not getting the interrupts, so WHDLoad works alright. No idea why it would suddenly start going like this though. Does it happen for all games or just a few ?

Unfortunately, if this is the problem, there's no workaround that I know of

It is plausible but I can't understand why it has happened so suddenly.

All games don't work but each one shows a different behaviour. As I said, some go to a blank screen, others freezes, other play music but don't show graphic.

I'm really going crazy... but I want say you that I really appreciate your help!
Amiga community is so so great!!!

[starf81]

Flashlab wrote:
I've had this exact same problem too when I installed some system enhancers too.

In the end I had to use my backup to restore the system. I never found out what it was. it was one of the utils mentioned in the OS3.9 enhancements topic (Amber RAM maybe?).

I guess some of the utils patches a library or some other system file because commenting out startup-sequence items or disableing WBStartUp didn't work for me either...

So... utilities could corrupt libs.
I think it is the only solution for this trouble.

I try to restore libs with the ones of a fresh installation and... I'll let you know if I solve!

Thank you again!
Alex

[starf81]

Yes.

[starf81]

TiredOLife wrote:
In the prefs, there is an option Keep Amiga Video.
I have this set to 15khz.

I can't find this feature.
Where is located?

[starf81]

Ok, thank you... but it was already set on 15khz.

[starf81]

I've restored a backup of some days ago.
It is the same backup from which I've recovered folders during my tests... well, now WHDLoad works.
I've tried to recover folders from my latest WB (the one that doesn't work). I've copied C, S, Prefs, WBStartup and WHDLoad still works!

So... now it's ok, I'd have discovered what was the matter but I had no success.

I'm going to backup again my sys partition...