WHDLoadMenu

[Torti-the-Smurf]

With "IconX/Programm.info" support, this would be perfect.

[Vesuri]

Originally Posted by Torti-the-Smurf

With "IconX/Programm.info" support, this would be perfect.

Do you mean starting WHDLoad as if the slave's icon would have been clicked from the Workbench? That indeed would be nice since the options set through the UI would then be saved into the icon files. WBRun from later AmigaOS releases would do the trick. I'll look into making this an option.

[markpaterson]

Is this compatible with AmigaOS 3.2? I added it to the top of the Startup-Sequence but it just loaded the menu even if I didn't hold the left mouse button. I had to manually quit the menu, which dumped me out to DOS. Then I commented it out of the startup sequence right there in the DOS using ED. Good job my brain somehow remembered how to do that from 30 years ago haha.

[markpaterson]

Also, is it possible to add non-WHDLoad games to the list? If so, how?

[gazj82]

Originally Posted by markpaterson

Is this compatible with AmigaOS 3.2? I added it to the top of the Startup-Sequence but it just loaded the menu even if I didn't hold the left mouse button. I had to manually quit the menu, which dumped me out to DOS. Then I commented it out of the startup sequence right there in the DOS using ED. Good job my brain somehow remembered how to do that from 30 years ago haha.

Make sure you have "StartWHDLoadMenu" in your startup-sequence.


If you have "RunWHDLoadMenu" then it will just run without looking for the left mouse button.

[trixster]

Sadly I cant get this to work. I've used the installer and RunWHDLoadMenu loads up the menu. This shows all my games, but then selecting any game opens up an output that shows:

whdloadmenu.output: file is not executable
runwhdloadmenu: file is not executable

all my games run fine if i load them from their icon, so im not quite sure why whdloadmenu cannot launch them...?

[Vesuri]

Originally Posted by trixster

RunWHDLoadMenu loads up the menu. This shows all my games, but then selecting any game opens up an output that shows:

whdloadmenu.output: file is not executable
runwhdloadmenu: file is not executable

This doesn't sound quite right: if RunWHDLoadMenu loads the menu, running it again should definitely work instead of resulting in "file is not executable".

Could you provide some more details:

• Which Kickstart version are you using?
• Which Workbench version are you using?
• To which directory is WHDLoadMenu installed in (full path, please)?
• Are you running in UAE or some other emulator?
• What sort of filesystem is the installation directory on?
• What does the output of the command

  list

  in the installation directory look like?

Thanks!

[Vesuri]

Version 1.7 is now available at http://aminet.net/package/util/misc/WHDLoadMenu . It improves the font rendering of the animated user interface. The antialiasing is still not perfect but I do think legibility has been greatly improved.

[pyksy]

WHDLoadMenuAnimated crashes with guru #80000004 on Kickstart 2.04/2.05. Works fine when using Kickstart 3.0/3.1.

Tested on FS-UAE with A500/A600 and Kickstart 2.04/2.05.

To reproduce, set up a bootable floppy or HD with WDLoadMenuAnimated command and boot with empty/no startup-sequence.
echo >ram:foo
whdloadmenuanimated ram:foo ram:bar nofade

[Vesuri]

Originally Posted by pyksy

WHDLoadMenuAnimated crashes with guru #80000004 on Kickstart 2.04/2.05. Works fine when using Kickstart 3.0/3.1.

Duh, I'm accidentally using a V39 convenience function for no real reason. Will fix. Thanks for the bug report!

[Vesuri]

Originally Posted by pyksy

WHDLoadMenuAnimated crashes with guru #80000004 on Kickstart 2.04/2.05.

This was addressed in version 1.8.

[neumanix]

Exactly what I was looking for! Thank you for this awesome program!

[PoulpSquad]

I'm having trouble running games with QuitKey= tool type.

EDIT 3:

Finally found how to fix it. I had to convert the raw value $5d to hexadecimal, 89.

Now I need to scour 1200+ games I installed those past weeks, and find each and every QuitKey tool type and convert them to hex...

[Jolabandola]

Originally Posted by PoulpSquad

I'm having trouble running games with QuitKey= tool type.

EDIT 3:

Finally found how to fix it. I had to convert the raw value $5d to hexadecimal, 89.

Now I need to scour 1200+ games I installed those past weeks, and find each and every QuitKey tool type and convert them to hex...

No you dont. Just edit the Whdload.prefs in S: to read Quitkey=$59 (F10) or whichever you choose. These settings are global.

[PoulpSquad]

I'm talking about tooltypes. Those override settings in the Whdload.prefs file as explained in the official documentation for WHDLoad:

http://whdload.de/docs/en/opt.html

Anyway it's sorted now, I searched with SimpleFind for every icon with the QuitKey= tooltype and changed all of them.

[Vesuri]

Originally Posted by PoulpSquad

I'm having trouble running games with QuitKey= tool type.

Thanks for the bug report! This is caused by the following (from WHDLoad documentation):

the value of the option is an integer, on the command line you must use decimal notation, as ToolType you can also use hexadecimal notation indicated by a leading "$"

I suppose it would be great if WHDLoadMenu would convert these on the fly. No promises, but perhaps worth looking into at some point!

[blade002]

Hmmm... not a great fan of this, the presentation is nice but on occassion it stuffed the colours completely on return to Workbench and the resolution in the game menu is clunky.

It's a nice effort, but for me there are better options.

[Leon Besson]

Originally Posted by blade002

Hmmm... not a great fan of this, the presentation is nice but on occassion it stuffed the colours completely on return to Workbench and the resolution in the game menu is clunky.

It's a nice effort, but for me there are better options.

Bromigo! It’s free to download! If you have issues then report it to the author of the code Mang!

Jees!

[blade002]

Originally Posted by Leon Besson

Bromigo! It’s free to download! If you have issues then report it to the author of the code Mang!

Jees!

It's still installed, I'll still use it along with Tiny Launcher, I'm not saying it's entirely "bad" but critiquing it only makes it better and just because it's free that doesn't mean criticism can't be made.

I'm more than happy to contact Mang and tell him what I said and despite this I do fully appreciate the effort that has gone into it, there are things also that I love about it.

Maybe he should ask for donations (If he hasn't already?) to make improvements, I would be sure to throw a few dollars his way.

[Vesuri]

Originally Posted by blade002

on occassion it stuffed the colours completely on return to Workbench

This is most likely caused by the feature to fade the frontmost screen or the feature to set the Workbench palette to all black. These are enabled by default and may be disabled using the NOFADE and NOSETPREFS command line options, which can be easily set when installing using the installer script. These features are meant to provide a smooth user experience when WHDLoadMenu is started on system startup, which is the main intended use case. Fading and especially palette setting should be disabled when started from Workbench. Sorry, the installer and the documentation should probably be more clear about this.

If the options don't work as expected, please report it as a bug with steps to reproduce the problem. Thanks!