Major update of glUAE released

Date 16-Jun-2012 22:10:18
Topic: software OS4

With today's release, glUAE gets some key features that give the user even more power and comfort.
Moreover, all the available helpers have been updated and the website has been heavily revised to illustrate more clearly the many features that make glUAE so unique and powerful.



* Added direct WHDLoad support (before WHDLoad was treated just like any other AmigaDOS-based application, so the user had to provide a startup-sequence; now everything is done automatically - but still the user can provide a custom startup-sequence, if he so desires).
* Allowed to indicate an alternative UAE executable on a per-application basis (perfect for applications that run better on a certain version of UAE than on the default one).
* Allowed to choose at startup: the boot file, if no startup-sequence is found; a hardfile, if more than 1 is found; a UAE configuration, if none is found; the UAE executable, if the default/application-specific one is not found.
* Reworked the images mounting: when a specific image is specified for DF0:, the next 1, 2 or 3 images in the same directory are mounted to DF1:-DF3: in alphabetical order (before DF1:-DF3: would get the first other 3 images in absolute).
* Made the determination of the application form depend first of all on the input file type.
* Given the user more feedback in case of errors.
* Renamed the "first-run" splash screen as "first-launch".
* Replaced the installer with a brand-new, AmigaOS-standard installer/reinstaller/uninstaller.
* Made several internal improvements.
* Extended/reworked the documentation.


* Any application (game, demo, tool, or even a whole AmigaOS system) can be launched transparently.
* Applications can be launched from virtually everywhere in a variety of ways (Workbench, AmiDock, menu, shell, keyboard shortcut, script, etc.).
* Applications can come in many forms: .adf, .dms, .fdi and .ipf disk images; .hdf hardfiles; ordinary AmigaDOS files; WHDLoad installations.
* Each application can be packed to a single file.
* Applications can rely on a centralized system, an (optionally stripped-down) AmigaOS system that provides the common system files.
* Each application can access specific user-defined directories of the host system.
* Each application can be configured to run optimally.
* Multiple applications can run at the same time.
* Multiple instances of the same application can run at the same time.
* Configurable spash screens can be shown before/while applications load/execute.
* glUAE is entirely based on AmigaDOS scripts and: does not run in the background, but executes only to launch the applications and to perform cleanup operations after the applications quit; interacts with AmigaOS cleanly; only takes a few kilobytes of disk space.

This article comes from AmigaWorld - Amiga Community Portal

The URL for this story is: