WHDLoad problem

[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

[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

[motorollin]

Did you try disabling the items in your WBStartup drawer?

--
moto

[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

[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

[motorollin]

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

--
moto

[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

[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