Amiga.org
Amiga computer related discussion => Amiga Gaming => Topic started by: AmigaClassicRule on March 05, 2014, 01:35:00 AM
-
No matter which game I attempt to load in WHDLOAD it is 100% guaranteed failure. The screen goes black, then I get random jiberrish graphics...and I am forced to reboot the Amiga.
One game used to work only after trying different versions of whdload and when I attempt to quit the game it crashes with random jiberrish graphics again and I have to reboot the system.
What can I do? Anyone can help me?
Sometimes it is a black screen and nothing else happens. I cannot use my Amiga 4000D to play any games on WHDLOAD...it is a dead end for me.
-
What is in your A4000D? Do you have a GVP Spectrum, I think they have issues with WHDLoad. Maybe an old virus is in play?
WHDLoad Games run fine on my 4000D.
-
I am not so sure about virus but it is a basic 040 Amiga 4000D with 2 MB CHIP RAM and 16 MB FAST RAM and that is about it. It have an SFS0 file system and I put AmigaSYSAGA as the OS.
-
I used to have a lot of random issues like that, didn't get a whole lot of games to work. Realized it was the NTSC vs PAL issue. Try checking the jumper on the motherboard to see if it's set to NTSC. The majority of games I've seen need to be in PAL.
slaapliedje
-
Actually it is PAL. But I am thinking maybe it is a virus. So what I am doing is formatting my main HD and installing the OS all over again.
-
Yeah, that one was kicking my butt for a while, couldn't figure out why some games would be completely corrupted, though I think I had a game or two that would work okay. Soon as I switched it to PAL, everything was all sorts of happy.
Makes me wonder how you managed to get a virus, isn't that almost a non-existent problem anymore?
slaapliedje
-
You can force WHDLoad games to NTSC or PAL by setting the appropriate tooltype in each game (or the global preferences) - no need to fuss with the motherboard.
If you're using the CybergraphX setting or some other patch that allows you to use 56KHz audio modes, turn it off - it messes up native screen modes.
I highly doubt it's a virus.
EDIT: Also make sure your TCP/IP stack and USB stack are offline before starting WHDLoad.
-
I knew about the flags for WHDLoad, doesn't help the non-WHDload games that had issues with NTSC. I figure if any of them need to be set to NTSC, I could just toggle that one.
I didn't know TCP/IP stacks could mess with it, but I know Poseidon said it had the possibility of messing it up, though I haven't had any issues myself.
slaapliedje
-
Will to be honest and to be full honest my Amiga 4000D jumper is set to PAL. The System Info says PAL. There is no USB or USB software and there is no TCP/IP. I am going to follow the conclusion that there is a virus in my HD. Ones I install the OS again and if it fails after that...there is a problem with the hardware then.
Because no version of WHDLOAD seems to work no matter what version I go or do.
-
What are some of the games that are failing? Maybe others have had better luck? Have you tried hitting the "quit" key after your screen goes black? I agree, highly doubt it's a virus.
-
Good news guys!!! It was a virus! Ones I formatted the HD, reinstalled the system...everything is running 100% sweet! It was the Virus after all.
-
More likely, it was just some application, lib or patch that messed with WHDload somehow.
-
Good news guys!!! It was a virus! Ones I formatted the HD, reinstalled the system...everything is running 100% sweet! It was the Virus after all.
You would have been able to repair the damage using VirusZ if there was a virus which I suspect there was.
http://www.amiga.org/gallery/index.php?n=3713
-
Excellent!
Now reinstall the apps you had, but keep checking WHDload as you do it. This will tell you which app it was that was stopping it working. It won't be a virus, so it must have been something you were running...
-
More likely, it was just some application, lib or patch that messed with WHDload somehow.
AKA a virus/malware. :)
-
AKA a virus/malware. :)
No. I doubt there is any malware for Amiga. What i ment was, there are so many custom patches, libs, add-ons for WB, so its more likely some of those can cause incompatibillity with WHDLoad.
-
How I got it running ..
-Go with via SHELL to the correct path
and then typing:
WHDLOAD xxxxxxx.slave (where xxxxx is the filename)
It Works..
-
How I got it running ..
-Go with via SHELL to the correct path
and then typing:
WHDLOAD xxxxxxx.slave (where xxxxx is the filename)
It Works..
It sounds like you have a misconfigured WHDLoad, or some kind of patch installed that is interfering with their proper running (via icon) if you are having to start them from the shell. In any case, glad you got it working. :)