Commodore Amiga

[lookers]

All whdload Games

[Seiya]

i tested whdload and it working good.
Do you use default emulator? (default is "New" in Gemus).

[.mad.]

HALT3 is WINUAE error.
so a setting in the UAE file is to blame.
*replace the uae files with the defaults in Gamebase emulator setup.

you could be using an old UAE file with a NEW emulator (vice versa).

some settings are added or renamed in the config file between emulator versions.
so using new scripts with old UAE files and emulator versions, will break it over time.

if you need to regularly swap between emulator versions for certain games /PC setup?
you need to have old and new script/config files.
even kickstart rom checksums have changed between some WINUAE versions.

example...
winuae3.exe
winuae3.txt
amiga3.uae
whd3.uae

winuae5.exe
winuae5.txt
amiga5.uae
whd5.uae

[Seiya]

All whdload Games

i have 2 computer with my Gamebase and i have no problem with WHDLoad.

WHDLoad are set in this way:

Code: Select all

mode=whd
cd=dh1:name;
whdload=name.slave PRELOAD;

if you want to use WinUAE 5.3 with WHDLoad you must change these values:

Code: Select all

emu=5.3
mode=whd
cd=dh1:name;
whdload=name.slave PRELOAD;

if you add other values or you insert WHDLoad without these values the emulator crash or give HALT3

"Old emulator" not working with WHDLoad and Harddisk becuase this script was for WHDLoad in Gamebase Amiga 1.6 and 2.3. I use that only for ADF games.
3DFX emulator is to use with games that use OpenGL and PowerPC (but it is yet experimental, better not use that)
Midi emulator is to use for games that use midi with munt32 integrated in emulator
Wipeout emulator is to run Wipeout game only
Old emulator is only for ADF that not run good with other emulators
Denise is a try to have alternative emualtor, but not works with scripts.

[lookers]

OK, I'll try these solutions.
Thank you

[.mad.]

WHDLoad are set in this way:

Code: Select all

mode=whd
cd=dh1:name;
whdload=name.slave PRELOAD;

if you want to use WinUAE 5.3 with WHDLoad you must change these values:

Code: Select all

emu=5.3
mode=whd
cd=dh1:name;
whdload=name.slave PRELOAD;

if you add other values or you insert WHDLoad without these values the emulator crash or give HALT3

with latest WinUAE, script could probably do with an update (more command-line options are available).
even though it worked, my old way of running WHDLoad files was a bit dodgey.

[Seiya]

i have the suspect that whdload compatibility is not totally due to the scripts, but from slave file. I notice that whdload from some authors working always good, while whdload from other never working.
Before change scripts i want investigate on this thing.

[.mad.]

i have the suspect that whdload compatibility is not totally due to the scripts, but from slave file. I notice that whdload from some authors working always good, while whdload from other never working.
Before change scripts i want investigate on this thing.

yes, the slave file can cause problems.
i know some games need reinstalling from the floppy disks when a new slave is released.
just overwriting the slave file with latest version will not work.

*i would think, most will be correct and up to date from Retroplay's archive.

but still a good idea to mark which WHD have problems, and try to find alternate versions of the install.
there might be a common factor why they don't work from a certain author?

[Seiya]

i notice that:
all JOTD whdload working good
Retroplay: generally working good, but some of them no.

Some authors put "workbench31.x.slave" and "Generickick13.slave" and Generickick31.slave".

launching Workbench31.x and Generickick31 WHDrun try to access to A600 kick 3.1 and whdload crashes.
Generick13 or Workbench13 generally working.

some whdload run the first time, but at second run WHDRun.exe crash telling that he cannot delete files. Deleting manually from GBGame/WHD working again, but only 1 time. The second time again the same error.

[.mad.]

some whdload run the first time, but at second run WHDRun.exe crash telling that he cannot delete files. Deleting manually from GBGame/WHD working again, but only 1 time. The second time again the same error.

I think i know about that problem, and made a fix for it.
i added a batch file to delete the GameBase REZIP folder before running a WHD.
*the drive letter needs to be changed in the batch if you dont have it on C:\.

The problem is sort of GameBase related.
when WHDRUN.EXE was created the GameBase (v1.2) rezip folder was called GBGame\rezip\
this folder was deleted by GameBase when closed, and WHDRUN checks for the folder name REZIP.

Now the default GameBase (v1.3) rezip folder is called GBGame\0\
so it needs to be changed back to GBGame\ in the INI
WHDRUN has not been updated for the change.

to get around all the loose files extracting in the GameBase rezip folder by WHDRUN (some with errors).
i made HDF versions of each one using a script i found online at EAB.
then WHDRUN is NOT needed.
This makes WHDLoads very PC freindly for all the filenames and foreign characters in the Amiga names not allowed on PC (MSDOS).
i am told this is not a good idea for using on a REAL Amiga, and many do not like it.
But we are talking about GameBase and WinUAE.

[Seiya]

if from my Gamebase i run Workbench 3.0 and 2.0 and in install WHDLoad, every game working. But whdrun was good to start directly the game.
i don't understand because modern whdload from some develpers working and from others no.

now a question must be done: an update of WHDRun?

[.mad.]

if from my Gamebase i run Workbench 3.0 and 2.0 and in install WHDLoad, every game working. But whdrun was good to start directly the game.
i don't understand because modern whdload from some develpers working and from others no.

now a question must be done: an update of WHDRun?

i don't understand it either.
when kick 3.1 is required, i've always used a A1200 for WHDLoad (not A600).
i can't say i ever had the need to run ANY game on a A600 setup via GameBase.
*maybe that is part of the problem with kickstart version?.

WHDRUN is a fabulous piece of software for GameBase and we would be lost without it.
it was made before GameBase was updated with better unpacking and script options.
WHDRUN takes control of the WHDLoad unpacking of the files for GameBase.
GameBase could easily do the upacking to it's own "rezip" folder and edit the startup-sequence now.

i read a long time ago the source is not available anymore for WHDRUN, so i don't think it will ever get updated.
we just need to use batch files and script edits to get around the few problems.

i suppose https://www.autohotkey.com/ could be used to make somthing very similar from scratch.

[hmueck]

i read a long time ago the source is not available anymore for WHDRUN, so i don't think it will ever get updated.

I found the source here, but I'm no programmer.
https://github.com/MrFlibb/WHDRun

[.mad.]

I found the source here, but I'm no programmer.
https://github.com/MrFlibb/WHDRun

Nice find, i thought it was lost forever.
going to read through this, and see if i can understand any of it.
Thanks!

I think HDF's are still the way forward for 100% compatability with emulation on the PC side.
there were approx 30 that will not work when unpacked on a PC, due to amiga file names.
others had LHA unpack errors with 7z and foreign charcters.
that's when i last checked in 2018.

i can make BANDIZIP the unpacker for GameBase.
which does help extract most /if not all of those characters correctly.
but it would need further testing to be 100% sure.

[Seiya]

i don't understand it either.

because you said you have made an HDF to resolve many problems with WHD. I inteded that installing WHD and WHDLoad games on harddisk (so, not using WHDRun.exe) many modern slave working good.
But i don't like this system in Gamebase.