AROS Generic WHDLoad

[Amiga600]

Since I cannot seem to find one, I am wondering if someone can
create an AROS WHDLoad Wrapper (like the ones made for KS1.3 and 3.1)

Where it uses the AROS ROM (aros-ext.bin and aros-rom.bin) files as
opposed to the KS1.3/3.1 files

I think it would be useful for many, not just me, as it can be then used
directly from Workbench as a quick test bed to check for compatibility
for Amiga Games / Demos / Utilities for example

This would then allow folks to test Games against the AROS ROM to see
if its compatible directly from Workbench, saving them time formatting
a disk and selecting AROS ROM in the (Win)UAE Launcher

[giantclam]

Something like this? ~ http://archives.aros-exec.org/?funct....i386-aros.zip

[Amiga600]

No not that, I mean like a Generic AROS Slave which can be run from Workbench

For example there is Generic Slaves for Workbench 1.3 and Workbench 3.1 which
I can (and have) used for some of the Games in the Games Collection I am
building so they work correctly under the KS3 part of the Collection

Example you have Workbench1.3.Slave and Workbench 3.1.Slave files which basically
have a "data" folder where you put your files (eg. C DEVS S/Startup-Sequence etc)
would normally load Workbench, But I have modified the Startup-Sequence inside each
so they will load the Games instead which are incompatible with KS2/3 or have
issues which WHDLoad will fix making them load successfully without issues


For example for the Game Trix, I have this setup, which I load like so: WHDLoad Workbench13.slave PRELOAD PRELOADSIZE=912669

Trix\Workbench13.Slave <<-- The Slave file for Workbench 1.3
Trix\data\Readme
Trix\data\system-configuration
Trix\data\Trix <<-- Game Files
Trix\data\Trix.snd1 <<-- Game Files
Trix\data\Trix.snd2 <<-- Game Files
Trix\data\Trix.snd3 <<-- Game Files
Trix\data\s\startup-sequence <<-- Simply contains "Trix" which loads the Game

[Snoopy1234]

Amiga Forever has an AROS system ready to go if emulation is an option.

[AMIGASYSTEM]

Originally Posted by Amiga600

No not that, I mean like a Generic AROS Slave which can be run from Workbench

On AROS you can find JanusUAE which allows you to emulate any Amiga model and all types of Workbench.

In addition Workbench13.Slave you can run it with WHD MENU


Tutorial WHD MENU
[ Show youtube player ]


Tutorial JanusUAE:
[ Show youtube player ]

[Wepl]

Originally Posted by Amiga600

Since I cannot seem to find one, I am wondering if someone can
create an AROS WHDLoad Wrapper (like the ones made for KS1.3 and 3.1)

Where it uses the AROS ROM (aros-ext.bin and aros-rom.bin) files as
opposed to the KS1.3/3.1 files

A Slave using these kickstarts would need relocation information for them, not available AFAIK. Also this Slave would need to be updated for each change to the kickstarts.

I think it would be better to create a Slave directly in the build process from AROS which includes the kickstarts. The relocation information would be available and some Slave code could perform the init of the kickstart boot process.

The question is, how much stuff must be patched in the AROS kickstarts to work under WHDLoad. And the way to do this is probably a bit difficult using this approach.

[Amiga600]

Yeah I thought it would be difficult, but as they say, if ya dont ask, you will never know - Thanks Wepl for explaining it

[jotd]

I suppose they can be assembled at different locations and compared to easily extract relocation information.

But the main issue is redesigning the patches. Wepl had great fun doing 1.3, which made it pretty easy for me to adapt to 1.2 and 3.1 (and 1.1) but that one is completely different.

[Wepl]

I saw there is an ELF image of the kickstart/kernel on the boot/emergency floppy disk. This can be relocated without much efforts. A similar way can be used like the AROSBootstrap is performing.
The amount of necessary patches to make it run under WHDLoad still remains unclear.

And I think it would be for some AROS devs much easier to write a Slave which loads the kickstart/kernel than for the whddevs. Because for example many device driver could be omitted for a custom kickstart build for WHDLoad.

[jotd]

another argument: AROS kickstart is probably going to fail on a lot of kick1.3 games...