WHDLoad problems with some games

[Cass]

I tried to install the SlamTilt. I'm using the v16.0 WHDLoad usr bin, the patch and the Back2Roots ADFs.
The game freezes after the intro, on the "Loading" screen. I've tried the various tooltypes combinations, but still nothing.

I've also done a simple HD install (no WHDLoad), and the Game.exe freezes the mouse & KB on the WB screen but no game. If I run the Rebootstart (using a RAD), the game starts with no problems.

Is it a 3.9 WB problem :-? ?!
________
Daimler Motor Company

[Cass]

Well I figured out the problem: AmigaOS ROM Update V44.57 (BB2). I guess WHDLoad does not like this ROM update on a 4000, as on my 3000 it works fine. I reverted to BB1 ROM Update and the games seem to be working ok now. I emailed Bert.

You may also try on SS:
C:SetPatch SKIPROMUPDATES exec.library QUIET

Anyone else with a 4000 and BB2 ROM Update that can verify it is indeed 4000's (or 1200's, maybe its IDE?) and some games not working?

Here! I'll try tomorrow to reinstall the Slamtilt, and I'll give feedback.
________
Easy vape vaporizer

[Cass]

I tried to run SlamTilt from the WHDLoad install but still no luck: The whole system freezed (no QuitKey responce!).

Here are some well known problems (from the WHDLoad manual):

 If I have my TCP/IP stack running, nearly every installed program will freeze after a short time because the card creates PORTS interrupts (the same type as interrupts created by the keyboard) which cannot correctly replied to by the installed program. This is because as soon as the request has been acknowledged with an rte, the next interrupt occurs. To avoid this problem, the TCP/IP stack must be stopped before starting WHDLoad.

I run it from a reset, and no TCP stack on the background...

-your machine is incompatible
Especially a 68040/060 CPU or some turboboards/other hardware may cause problems. Try to turn off all extra hardware and try to start the install again.

Also worth to consider...
________
Dodge kingsway history

[Cass]

Happy happy happy!!! :-D

I found something that made my problematic WHDload installs, finally run: disabling the WBstartup, I was able to run some games which meant that something was going on with a patch or a similar prog.

The culprit was the dnetc_ppc client!!! All I had to do was to stop the client from the Myzard GUI. Probably it was creating interrupts that couldn't be handled by WHDLoad...
________
Shemale Young