Thanks for the prompt reply.

I have commended the path of the harddisk in uaerc to correspond on my 3.9 (with whdload installed) drawer.

If I just double the e-uae executable (as I have already described), I can boot into my 3.9 setup.

However, if I point the conf path of uaeload to my uaerc, I get the error I described.

Hope this helps.

Ok, I 've a similar thread here -> https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=6701&forum=9#75281 that describes more or less the same problem I face. I think I have understood the reason. Will try to find sometime later today to test it.

OK, I am really close now!

Andreas was right; I had to point to my WHDload folder as a filystem on the E-UAE config file as well. Then I double clicked E-UAE executable, loaded Workbench 3.9, automounted my WHDload drawer games, opened Zool, double clicked the slave and it worked!

That's the good news. The bad news is that if I double click the slave from iGame in Ambient I get the following error:

UAE is not yet running or boots slow. Please use uae_rcli to your E_UAE system or try to increase uaeload timeout.

Inceasing the timeout didn't had any effect.

Still, I have copied uae_rcli to both MorphOS C: and to my 3.9 C:. Afterwards, I placed the following command to my startup-sequences (after LoadWB): Run >nil: C:uae_rcli

As a matter of fact, here below is my Startup-Sequense on the emulatd side (note that I am using the lite version which came with uaeload):
Quote:

And regarding MorphOS:S startup-sequence, looks like this:

Quote:

Again, what I am missing, here?

Quote:

At least this:
; This script is executed on system boot. Do *NOT* modify this file!
; Use S:user-startup instead.

Anyway, you shouldn't try to use uae_rcli on MorphOS side. You only need it inside the E-UAE.

I might try to install similar setup at some point later, can't help before looking better to those systems...

Well, I decide to go brave style and modify the startup sequence of MOSSYS: since I could find the startup sequence in SYS:s.

Bravery is ok but won't help here =)
Check the paths again and be sure they correspond and/or there is any error. This happens when iGame doesn't find the right directory. After you are sure that no errors are present, open iGame dire and erase "gamelist" and "repos.prefs" files then launch program again and redo settings.

Are you sure that uae_rcli has anything to do with iGame prefs?

Will check it of course later tonight but I have my doubts.

Also, I have found a 4 month old similar thread herethat describes slowness of UAE when enabled (hint: uaeload complains also for slow boot).

Yes it has. I tried to erase the line in s:startup-sequence invoking uae_rcli iGame will alert something is not going well and the whdgame won't start.
Double click on the whdgame icon inside emulated workbench and the game run normally. So uae_rcli is necessary to iGame so to start whdgames using its gui.

I finally did it! uae_rcli under e-uae was not set with executeable flag. Now it works like a charm. Thanks everyone for the assistance!

WeiXing3D: it's a good idea, i could test that but i must buy AmigaForever before and for the moment i have not the money for that.

Jambalah prepare a guide to install Workbench and Whdload for E-UAE:

https://fbcdn-sphotos-d-a.akamaihd.net/hphotos-ak-xfp1/t1.0-9/10462770_10201148804562300_2498292179593362605_n.jpg

I've mostly got rhlaunch working under UAE, the only issue I have is that on some games I get the following error:

IMG_20140622_075845_zpsa9d5ad6f.jpg

I'm tipping I need some form of backup KS1.3 rom loaded for certain games, however I have no idea how to do so, any advice?

Cool_amigaN, is it possible for you to post a step by step updated guide of what you have done just in case others want to do the same?

The more detailed information we have, the better.

[ Edited by madCrow 22.06.2014 - 06:07 ]

Quote:

http://www.whdload.de/docs/en/need.html

Sorry jPV,

I already know I need to use a different version of kickstart, my issue is how do I implement differing KS versions in UAE? Is it possible, for example, to have a backup KS for the software that needs it?

Your problem was that you need different kickstart images for WHDLoad, not for UAE. You need those kickstart images in your Amiga setup where WHDLoad can look them for the games which need those. Read the WHDLoad docs how to have several different versions available and how to name them.

Having different kickstarts for UAE won't help you here. But if you want those too, it's possible to make different config files and provide them to UAE when starting it. Can't check just now what was the option, but -f or something. But as said, this won't help the problem you described which is purely just WHDLoad issue.

Thanks jPV, copied all the nessecary ROMS and relocation files to the emulated A1200 and renamed the files accordingly and everything is working perfectly!

Once again, thank you very much for your time (and patience).

Now to install iGame.

One more question...

Is it possible to configure E-UAE so that the mouse pointer stays within the confines of the emulation screen? As when the mouse pointer hits either the left or right hand side edges another mouse pointer that goes outside the emulation screen and makes things very confusing.

Also, how can I make my desktop look prettier? The standard WB3.1 is a little bland and lacking in color.

[ Edited by madCrow 24.06.2014 - 14:05 ]

@madCrow

There are lots of Workbench (3.x) enhancing packs available: From AmigaSYS (my old time favorite) to ClassicWB and ofc the most notable AmiKit.

However, the more you skin/edit/add third party programs to the default environment, the more bloatware it gets (emulation gets "heavier", more cpu cycles are needed etc).

Frankly, the only reason I need 3.x is to boot straight to WHDload. If that's the case for you as well, then I suggest to have the more stripped version of classic AOS as possible.

Hi,
I'm Waitsnake from Germany and I'm new to MOS and hope to learn a bit more about this operating system family and also amiga systems. As kid I start with C64 and than unfortunately go direct to PC (Win & Linux) and later to Mac and I miss all the Amiga stuff. ;-(


As mentioned in this topic before I also tried to install iGame, UAELoad, WHDLoad, E-UAE with WB 3.1 and so forth according to an manual I found here: E-UAE_installation_on_MorphOS.

I use MOS 3.6 with Chrysalis pack 3.6.1 beta installed. It comes with E-UAE 0.8.29-WIP4 from 01.07.2014.

I had the same issues that WB 3.1 was not able to install when using as virtual hard disk a directory from MOS (filesystem2=rw,DH0:System:HardDisks/W orkbench,1) and it allways seems to hangup the complete emulation at around 12% of install progress when the installer start to create folders and icons on the file system.

In the logfile I saw some strange error messages that seems to correlate with the problem: „FILESYS: UNKNOWN PACKET 1f".

I try to look for the source code to find this error message. I only could found the source code of an older version (0.8.28) linked to this page here: www.amigaforever.com.

In the file filesys.c You see that 0x1f=31 is defined as ACTION_INHIBIT and the big switch inside the function handle_packet() does not handle this type and the switch will run into the default-case that only returns false and print this error message.

In the file history the author even mentioned: „Known limitations: * Does not support ACTION_INHIBIT (big deal).“. So that seems an important issue of E-UAE anyway.


Than I found some more information about that ACTION_INHIBIT here: Amiga DOS packets (see at "dos.library/ACTION_INHIBIT" ). It seems to be an kind of flush action that writes all file buffers to hard disc when requested, like the sync command in Linux systems.


With a google search I found the source code of fs-uae. Inside the winuaechangelog.txt you found that they implement this ACTION_INHIBIT with Beta 1 and with Beta 2 they fix some infinite loop that this function causes.

Well I really don't know much about that filesystem stuff and I'm not sure if the missing implementation of ACTION_INHIBIT in the E-UAE of MOS really causes the hangup of the emulation. I just hope that someone with more knowledge will pay a bit attention on it and take a look if it is a issue or not.

The source code of ACTION_INHIBIT in FS-UAE can be found here: filesys.cpp

A good workaround of this problem is to avoid file system access and use a hardfile (hdf) instead of that. Unfortunely file system is needed to connect iGame in MOS to the games installed in E-UAE.

[ Edited by Waitsnake 21.07.2014 - 21:56 ]

Hi Waitsnake and welcome!
Your error occours when you try install Workbench 3.1 directly from Ambient. If you perform the same action inside E-UAE installation goes flawless. You can create Workbench and Games directories directly from Ambient but you have to install Workbench using E-UAE emulation.
Inside the guide read page 22, from line 1 to 7: if you are using iGame launcher you can use a hardfile (hdf) with virtual hard disk (filesystem) provided that both are "2". So you can have: hardfile2= and filesystem2=. In fact usingiGame launcher you must use virtual hard disk only to store WHDLoad games while Workbench can be installed inside a hardfile.

Edit:
sorry Waitsnake, I was reading your post again: you wrote that emulation hangs at 12%. So , does this problem happen when you are installing Workbench 3.1 after you have started E-UAE?

[ Edited by Jambalah 22.07.2014 - 19:48 ]

Hi Jambalah,
thanks for your answer and sorry. I guess I miss the point in my last post.

1.) I tried to install WB 3.1 in E-UAE on MOS and I was using filesystem2 to mount directories from MOS into E-UAE (for System and Games).
I tried the installation a couple of times and always at 12% the complete emulation hangs, well even the MOS hangs more or less (windows moving around still reacts, but any other action hangs as well). I take a closer look at installation and see that first 11% of installation do nothing else than interact with user. The copy of files and directories just starts at 12% and this is the moment when E-UAE hangs.

2.) I just boot from a WB 3.1 start diskette and try only try to copy 1 or 2 files (e.g. the calculator app or something else) from the start diskette to the folders mounted by filesystem2. Sometimes the copy works. But more often this simple file copy also hangs up the E-UAE. So problem is not the WB 3.1 installer itself but it seems to be an issue of E-UAE when using the feature of filesystem2 and copy any file to it.

In both cases I see these „FILESYS: UNKNOWN PACKET 1f" error messages in E-UAE console output at the time of first file access to an filesystem2 mounted device. So I was thinking something could be wrong with E-UAE and I was hoping one of the developers of this software is active in this forum and he could take an eye on it. As I mentioned in my last post I was guessing the issue of E-UAE seems to be related to that missing implementation of the ACTION_INHIBIT feature from Amiga DOS.


3.) I was creating an empty hardfile on an other operating system and than use this file with the hardfile2 feature of E-UAE and than I could install WB 3.1 without any problem. So the issue is only related to filesystem2 and hardfile2 works a treat.


Problem I see in future with this workaround of 3.) is that even if I have now a working WB 3.1 installation using hardfile2 I still need the filesystem2 for the game folder that bridges iGame application on MOS with WB 3.1 on E-UAE. And I saw in 2.) that any simple write access from WB 3.1 to an filesystem2 mounted device could lead to an hangup and this could really ruin your day.

@Waitsnake

"always at 12% the complete emulation hangs, well even the MOS hangs more or less"
"FILESYS: UNKNOWN PACKET 1f"

Same for me in my E-UAE setup with AmigaOS 3.0. Copying files hangs the system.
But, strangly, it works with E-UAE/AmigaOS 3.9, no hangs, no "unknown packet" messages, etc.

I remember a user had the same problem on AmigaOS 4.1 (I read this on AmigaWorld or Amigans some weeks ago).

Quote:

Anyone can comment on the above, please?

???
I've created two new empty directories to use as virtual hard disk partitions to perform a Workbench 3.1 installation (I did the same when I was writing the guide, see snapshots) and... it doesn't work anymore... I have the same problem above mentioned during installation which stops at 12% while installer is copyng WBStartup.info inside hard disk. How is it possible? I'm using the same adf images I used before and I tried Wb installation on the 3.5 too (I haven't upgraded MorphOS on my MDD yet). I've tried with filesystem and filesystem2 and always failed. I'm really disappointed...

A complete installation of Workbench 3.1 via E-UAE work for me on a HDF but i must rename "Locale3.1" volume to "Locale", bizarre...

After some days of tests I discovered that I can't install both Workbench 3.0 and 3.1 if I use E-UAE-0.8.29-WIP3 and WIP4. This morning I tried with E-UAE-0.8.28-2 and all went flawless trying to install WB3.0 and WB 3.1 (I've performed installation of both system three times with no problems). The FILESYS: UNKNOWN PACKET 1f error (if this is an error) was always prompted but installations always went ok. So I ask to Waitsnake and Papiosaur and all people that want to give a try to repeat what I tested so to confirm that all works with this E-UAE version.
I will try with E-UAE-0.8.29-PPCJIT_BETA03_MORPHOS next so to make a complete test.