Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: marcfrick2112 on November 21, 2011, 11:24:41 PM

Title: Newest WHDLoad acting flaky?
Post by: marcfrick2112 on November 21, 2011, 11:24:41 PM
Hey everyone.. I have NO idea what is causing this, but after upgrading to the newest WHDLoad, I find odd tooltype entries that cause the game not to run. I have Deleted those tooltype entries, but are still their after the next boot.

Here's what shows for Theatre of Death:

*typical WHDload stuff about slave, PAL, etc. then:*

PreloadSize=1518568
Config=C1:B:Custom1;C5:b:Custom5

Prior to updating WHD, to V. 17, iirc, all the games on my HDD worked 100%. sure I have found a few originals that didn't work, but no biggie....

ANYone else have this issue?

 when I run a game with these weird tooltypes, on the WHD loading screen, I see standard grey checkboxes to select Custom options, but my miggy crashes BAD before I can select anything..

I thought  copied the old version back, but I still have the issue... Any ideas?
Title: Re: Newest WHDLoad acting flaky?
Post by: marcfrick2112 on November 22, 2011, 09:14:27 AM
Ugh! Well, I still don't know what's going on between WHDLoad and Theatre of Death, but I found a work-around.... I write- and Delete-protected the icon.... :D

Now, if ya'll excuse me.. I have little pixelized people to blow up....
Title: Re: Newest WHDLoad acting flaky?
Post by: marcfrick2112 on November 23, 2011, 04:35:14 AM
Grr, still have this issue, even after 'downgrading' to V 16 of WHDLoad....
The Docs say this is normal for PRELOAD games.. but If I see ANY PRELOAD = xxxx, in the tooltypes, the game will not run... Ummm, Peeps, the ONLY thing that changed was that I upgraded WHDLoad, from V16, to current, 18? I have a REAL keyfile, I am a happy WHDLoad supporter... so, what the heck!!!
I ONLY upgraded my WHDload install, due to some old games not working right.... now, I have no idea if ANY game will run.. *without deleteing tooltypes*

ANYone have ANY ideas? Seriously... before that update... I had some 102 Amiga games on my HDD, all were playable via WHDLoad....... after installing V. 18. games may randomly NOT start... and even after I change the tooltypes back, (the icon of the game)... they come back after a re-boot...EVEN if I write and Delete protect the files... OK, WTF!!!!!!

Can someone just get me the old, reliable WHDLoad I USED to know and love????
I have Emailed Bert Jahn....
Title: Re: Newest WHDLoad acting flaky?
Post by: Lurch on November 23, 2011, 09:09:26 AM
Since I upgraded to 17 some games report that I don't have a registered version of whdload. My key is for 15.x so I don't know if that makes a difference.

Was thinking of switching back or going to 18... think I'll be downgrading :-/
Title: Re: Newest WHDLoad acting flaky?
Post by: Bamiga2002 on November 23, 2011, 10:00:11 AM
There is no WHDLoad v18, 17 is the latest (excluding 17.1 beta).
Title: Re: Newest WHDLoad acting flaky?
Post by: mailman on November 23, 2011, 10:41:00 AM
First thing. Always keep the old version under its name, example - if the latest version is 17, first rename the last one to WHDLOAD16_9 and keep the latest one under the name WHDLOAD.

Now, unless you don't have WHDLOAD in PROGDIR: of the game, your games should always use WHDLOAD which is in C:. If you think that the latest version works incorrect, then just rename the default tooltype of the game that crashes or does not work and use C:WHDLOAD16_9 (or any other of your choice and backup you have) instead of WHDLOAD. There is no way that going back to the previous "working" version creates issues that existed when using the latest one.

About the keyfile - make sure you have it in L: or/and S: or/and C: location. Try also checking WHDLOAD prefs in case there is some strange PATH written in which WHDLOAD is looking for keyfile (but I doubt it) or that makes something strange going on.

If all that fails, there is always a virus option in your system that simply changed something in some files (maybe even altered the keyfile and it is not recognisable).