Repository navigation
WHD-booter is now 'smarter' than it once was? #2405
|
Once upon a time, if a new whdload game-pack was made available (via EAB for instance), one pretty much had to append their own snippet to the XML file, to get the game to load properly. Yesterday I discovered something, you can reference the EAB thread https://eab.abime.net/showthread.php?t=82101 for any background, but the resultant whdload pack is attached. When you go GUI->WHDLoad and select/load this file, you see...
....and clearly the lack of game name/UUID fields infers no match was found in the XML. However, if one clicks on 'Start'...the process selects AGA / 68020 / rom v39 as it probably should, and the game itself starts/runs just fine. Previously, the whd-booter process would get this terribly wrong, use the AROS rom, and likely select ECS chipset. Obviously something has changed, and no mention of this change is found in the wiki...can you explain this behaviour please? ...ie; is a match in the XML now optional? TIA |
Replies: 2 comments
|
There was always a fallback if something is not detected, but the fallback wasn't very reliable (or was outright wrong in some cases). The XML itself has changed to JSON format lately as well, since that's easier to parse and more streamlined. |
|
Ahh, right you are then, that explains it ...thanks =) |

There was always a fallback if something is not detected, but the fallback wasn't very reliable (or was outright wrong in some cases).
I changed it to fall back to a config that should work in most cases, that is an A1200 config with the ROM you saw.
The XML itself has changed to JSON format lately as well, since that's easier to parse and more streamlined.