@Cass

So, did you manage to get AP running?


@all

I've just released an updated version of glUAE (it's in OS4Depot queue) which contains 3 new key features:
1. automatic creation of the S/startup-sequence file (as mentioned in a previous post);
2. possibility of choosing the application-specific configuration file if none is found at startup (and, upon quitting, it is also possible to make that configuration permanent - this is handy when a satisfying configuration is found, so that the next time around the application will automatically make use of it);
3. when a specific disk image is passed to glUAE, it will be mounted to DF0: (glUAE automatically sorts all the disk images it finds in the input path and mounts them to DF0: ... DF3:, so that was not granted before).

@Tomas Quote:

How the heck do people get runinuae to work anyways? Every time I gave it a try in past it always complained about one of the workbench disks/adf images.

I would have looked at your problem, if I had been told about it. Sadly I cannot read forums everyday. Email works better...

ANYWAY, please try installing RunInUAE that comes with Update 4 (of AmigaOS4.1). This comes with all the ROMs & Workbench files you need, so it all "just works". (Although if you had an AmigaForever CD, then it should have "just worked" anyway.)

Last edited by ChrisH on 02-Jun-2012 at 06:17 PM.

_________________
Author of the PortablE programming language.
I love using Amiga OS4.1 on my A1-X1000 & Sam440
Don't forget the official support forum for OS4!

@ChrisH

I hope you can help me getting an old favourite 'Tornado' working, when I try to run it I get a screen switch to a lo-res Workbench screen with a long string of output 'Unknown command, no lock-ups no freezes just nothing afterwards except some sounds!

_________________
SAM 460 with 2GB or RAM, 1000GB HD, 4 port SATA, DVDRW drive and Radeon HD 4650 GFX card.

@saimo

Sorry for the delay, I`ve been testing some things.

I`ve setup a config similar to the original HW ( A4000.uaerc ), then I modified the WB backups I had by removing all the patches and setting up the right drivers (e.g. UAE GFX monitor driver instead of CV3d).

After launching the glUAE_LA with the app as parameter ( AMOS Pro in that case ) , the UAE GUI pops up to select a config (I select the A4000.uaerc ) and it boots to WB just like the original HW, waiting to run any application (not launching AMOS Pro) ...

_________________
Ordell Robbie: Is she dead, yes or no?
Louis: Pretty much.

@Cass

Quote:

Sorry for the delay, I`ve been testing some things.

No problem.

Quote:

I`ve setup a config similar to the original HW ( A4000.uaerc ), then I modified the WB backups I had by removing all the patches and setting up the right drivers (e.g. UAE GFX monitor driver instead of CV3d). After launching the glUAE_LA with the app as parameter ( AMOS Pro in that case ) , the UAE GUI pops up to select a config (I select the A4000.uaerc )

If you call it simply .uaerc, UAE will not bother you with that question anymore

Quote:

and it boots to WB just like the original HW, waiting to run any application (not launching AMOS Pro) ...

A few questions:
1. were you using the glUAE I uploaded to OS4Depot 4 days ago?
2. did you use the AP install I gave you or an install of yours?
3. can you show me the first-level listing of your AP install directory?