WHDLoad problem

[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

[girv73]

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

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

[Flashlab]

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

[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

[TiredOLife]

Are you using P96?

[starf81]

Yes.

[TiredOLife]

In the prefs, there is an option Keep Amiga Video.
I have this set to 15khz.
I can then play whd games using a TV.
Does that help?

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

[TiredOLife]

In Sys:Prefs.
It's called PVS.

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

[starf81]

Another news: after restoring sys partition as described in my previous post, everything worked well.
After I've launched MiamiDX but it coudn't go online (it happens sometimes, I've to reboot and try again 3-4 times). So, I've rebooted and WHDLoad doesn't work again!
I can't understand why the stack creates conflicts also after rebooting. WHDLoad has been the first app I've launched.

What has done MiamiDX???

[starf81]

Another news again... this is THE DEFINITIVE one!!!

I've discovered the cause: the Ethernet cable!

It is an absurd story.
If the is connected, WHDLoad will not work.
If the cable is NOT connected, WHDLoad will works perfectly.

Does anyone get similar behaviours?

I know that stack TCP/IP could create conflicts with WHDLoad but I can't understand why it crashes also if I don't start MiamiDX. Just a connected Ethernet cable can hang up the program??

[motorollin]

starf81 wrote:
I can't understand why the stack creates conflicts also after rebooting. WHDLoad has been the first app I've launched.

The first time you run Miami it initializes the network card. The card is maybe still active and creating hardware interrupts after a warm reboot.

--
moto