fs-uae-wrapper 0.6

plain

Options used:

• None

Plain module is kind of dummy or failsafe if you will, since all it do is run fs-uae with provided configuration and command line options. It will be chosen in case when there is no wrapper option provided neither via the configuration file nor command line parameter.

cd32

Options used:

• wrapper (required) with cd32 as an value

• wrapper_archive (required) path to the archive with CD32 iso/cue/wav

• wrapper_archiver (conditionally required) archiver to use for storage save state

• wrapper_gui_msg (optional) if set to “1”, will display a graphical message during extracting files

• wrapper_save_state (optional) if set to “1”, will load/archive save state directory, defined as $CONFIG/[save-state-dir-name] using provided wrapper_archiver archiver. If this option is enabled, wrapper_archiver will be required.

Let’s see some sample config for a game, which is saved as ChaosEngine.fs-uae:

 1 [config]
 2 wrapper = cd32
 3 wrapper_archive = ChaosEngine.7z
 4 wrapper_archiver = 7z
 5 wrapper_gui_msg = 1
 6 
 7 amiga_model = CD32
 8 title = The Chaos Engine CD32
 9 
10 cdrom_drive_0 = Chaos Engine, The (1994)(Renegade)(M4)[!][CDD3445].cue
11 
12 save_states_dir = $CONFIG/fs-uae-save/
13 
14 joystick_port_1_mode = cd32 gamepad
15 platform = cd32

Next, the invocation of the wrapper would be as follows:

$ fs-uae-wrapper ChaosEngine.fs-uae

Now, there several thing will happen:

• Config file will be read, and wrapper module will be find (because we already put it on line 2)

• New temporary directory will be created

• Archive with game assists will be extracted in that directory

• Configuration file will be copied into that directory, and renamed to Config.fs-uae

• If wrapper_save_state is set, and there is saved state archive, it also would be extracted there

• fs-uae will be launched inside that directory

Next, after fs-uae quit, there will:

• Optionally create archive containing save state with name like the configuration file with additional _save suffix. In this example it would be ChaosEngine_save.7z.

• Wipe out temporary directory

archive

Options used:

• wrapper (required) with archive as an value

• wrapper_archive (required) path to the archive with assets (usually means whole system directories, floppies or hard disk images)

• wrapper_archiver (conditionally required) archiver to use for storage save state

• wrapper_gui_msg (optional) if set to “1”, will display a graphical message during extracting files

• wrapper_persist_data (optional) if set to “1”, will compress (possibly changed) data, replacing original archive

• wrapper_save_state (optional) if set to “1”, will archive save state directory, defined as $CONFIG/[save-state-dir-name] using provided wrapper_archiver archiver. If this option is enabled, wrapper_archiver will be required.

Example configuration:

1 [config]
2 wrapper = archive
3 wrapper_archive = Workbench_3.1.tar.bz2
4 wrapper_archiver = lha
5 wrapper_gui_msg = 1
6 wrapper_persist_data = 1
7 wrapper_save_state = 1
8 ...

And execution is as usual:

$ fs-uae-wrapper Workbench.fs-uae

This module will do several steps (similar as with cd32 wrapper):

• create temporary directory

• extract provided in configuration archive

• extract save state (if wrapper_save_state is set to 1 and archive with save exists)

• copy configuration under name Config.fs-uae

• run the fs-uae emulator

• optionally create archive with save state (if save state directory place is not a global one)

• optionally create new archive under the same name as the original one and replace it with original one.

This module is quite useful in two use cases. First is a usual work with Workbench, where there is a need to keep changes of filesystem. Second is the opposite - if there is a need to test some software, but not necessary keep it in a Workbench, than it will act as a temporary copy of the system, so that next time fs-uae will be run, there will be no files of tested software cluttering around.