yes that's what I'm doing. If I drag a game foler with ADF's in it ..the screen pops up saying its not 68k....this was game that would working before with R2....
I assume you tried starting it the right way now? And it works?
sorry Chris....I typed that message on my phone while I was in the doctors office..what i meant to say is that when I drag a game folder containing 2 adf's into the AmiDock icon of RuninUAE I get a screen saying that the file is not 68k??? this exact same folder worked fine with the previous version of RunInUAE... I also noticed that the nice icon you had is gone in this R3 release?
I didn't follow a word of what you said (no idea what "it" refers to). Can you please explain clearly (1) what you were trying to do that failed (e.g. double-click HD installed game), (2) exactly what the problem(s) you found, and (3) how you fixed it.
I was trying to run HD installed SlamTilt dragging its icon on RunInUAE icon on AmiDock. RunInUAE started EUAE and WB3.1 but the game didn't start. In a Output window on AOS4 side RunInUAE/UAE told it can't find remote cli/remote cli is not running (or something like that). Then I checked AOS3.1 User-startup and there was run >nil: uae_rcli line twice. I removed the second line and now the game starts after UAE and WB3.1 is loaded.
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
@TSK Thanks for your detailed explanation. Looking at the installer script, the only explanations I can come-up with are that either: * You had a previous installation of RunInUAE, but deleted "EnvArc:RunInUAE.cfg" before reinstalling RunInUAE. * You never installed RunInUAE before, but the Workbench files you provided were already set-up for E-UAE (uae_rcli).
I will make the installer check the contents of User-Startup, before adding uae_rcli to it.
@328gts It was NEVER intended that you could "drag a game folder containing 2 adf's into the AmiDock icon of RuninUAE". If it did work in a previous version, then that was pure luck, because I'm not sure how it could have worked.
Please either: 1. Double-click the first ADF disk. 2. Drag the first ADF disk onto RunInUAE's icon in AmiDock.
sorry Chris I forgot to add that even if I drop a single adf that worked with the old version onto the AmiDock I still get the same message...I will try re-intalling it again...
re-installed for the 3[rd time & now I can get some ADF's to work when i drop them in AmiDock....still no success with my old 68k stuff off my 1200 though
I've got this problem that is probably stupid, but plz let me know what I'm doing wrong. When I run e-uae in a windows, I simply press ESC and it exits. That doesn't work on full screen. How do I quit e-uae while in full screen? Thx!
I've just discovered www . whdownload . com . Looks like a much easier way to install WHDLoad games you own, and of course most of them should automatically work with RunInUAE!
(I'm guessing that this is the site Saimo's gluae "Helpers" will be downloading from. Well, no need for "Helpers" with RunInUAE! Just download, unarchive & run :)
@ChrisH We now have two "classic" integration WIPs (yours and Saimo) and I guess this friendly competition will end up delivering the best "Classic" experience back to where it truly belongs (to Amiga of course!).
Btw, have a question: How you detect, which binary run in the UAE, and which, will be runs natively by os4 68k emualtor ? Did you check any HW banging instructions inside the 68k binary before redirect it to UAE or just give work for aos4 itself, or how ?
If you'd tried the alpha version, then you should know the answer...
I tryed that version which you send me, and after all just try to run 68k game and 68k sys.friendly software, and looks like for 68k game it try to run uae, but for 68k friendly soft it give all to os4. So i just in interest about technical detail how it's done ..
looks like for 68k game it try to run uae, but for 68k friendly soft it give all to os
That *shouldn't* be the case, unless I did it accidentally! It's merely supposed to detect a 68k executable, and then (for the first time only) ask whether to run it in E-UAE or not.
@all I have now made the fifth alpha release (please use the download link in the first post). Changes include:
* No-longer hangs when E-UAE is closed before the 68k program is run. * No-longer quits when an unexpected (but non-fatal) error occurs. * Added menu items for editing the time out & priority for E-UAE. * If the window was hidden, then it is temporarily opened to let you know E-UAE is being started. * The installer now offers to use your previous installation choices.