The problem is that sometimes the WB loads and the "whdload starting... Please wait!" prompt stays forever, without launching the game.
If I quit the emulator and start again the same game, or double click again the same game while waiting for the first launch to start, the game starts as supposed to do and everything is OK...?!

P.S. I have WHDLoad v17.0.5139

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

@Cass

I just saw the UAE`s log, and there is a "Remote cli is not running." message. Is it related to the problem? How can I enable the remote cli?

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

@Cass
I didn't see this post before. (I am more likely to see a post on www.Amigans.net , especially since there is less traffic there. Or you could email or PM to let me know about your post...)

Does this problem (1) always happen with whdload games, (2) happen with specific whdload games, or (3) at random with any whdload game.

You should not EVER see the message "whdload starting... Please wait!". Instead of "whdload" you should see the name of your game. That you are seeing this suggests that something is quite wrong with your RunInUAE installation, although I am not sure what yet.

Quote:

P.S. I have WHDLoad v17.0.5139

Does this mean that you installed WHDLoad (v17.0) on OS4? That is a VERY BAD thing to do, and I would not be at all surprised if it broke RunInUAE's WHDLoad handling. RunInUAE installs a "fake" WHDLoad command, so installing the real WHDLoad on top of it will thus break that.

WHDLoad must be installed *inside* E-UAE, to the Workbench3.1 installation.

P.S. The next release of RunInUAE (r7) will come with WHDLoad v17.0 (and install that correctly!).

Last edited by ChrisH on 29-May-2012 at 06:35 PM.
Last edited by ChrisH on 29-May-2012 at 06:33 PM.
Last edited by ChrisH on 29-May-2012 at 06:32 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

Quote:

ChrisH wrote: @Cass Does this problem (1) always happen with whdload games, (2) happen with specific whdload games, or (3) at random with any whdload game.

1) Always on the first launch
2) No, with every game on the first launch
3) After the first launch, I may relaunch and it works as it should be working on the first place

Quote:

You should not EVER see the message "whdload starting... Please wait!". Instead of "whdload" you should see the name of your game. That you are seeing this suggests that something is quite wrong with your RunInUAE installation, although I am not sure what yet.

Surely something goes wrong!

Quote:

Quote: P.S. I have WHDLoad v17.0.5139 Does this mean that you installed WHDLoad (v17.0) on OS4? That is a VERY BAD thing to do, and I would not be at all surprised if it broke RunInUAE's WHDLoad handling. RunInUAE installs a "fake" WHDLoad command, so installing the real WHDLoad on top of it will thus break that. WHDLoad must be installed *inside* E-UAE, to the Workbench3.1 installation.

I`ve installed the latest inside the emulated enviroment. The OS4 binaries are untouched.

Quote:

P.S. The next release of RunInUAE (r7) will come with WHDLoad v17.0 (and install that correctly!).

Looking forward to installing the newest version. I particularly like the way it handles the disks/executables etc. Everything transparently and nicely, with no user interaction. Looks like it`s part of the OS.

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

@ChrisH

Quote:

P.S. The next release of RunInUAE (r7) will come with WHDLoad v17.0 (and install that correctly!).

Great to know !
WHDLoad 17.1 is also on the way, for more info check: http://whdload.de/whdload/

That fix a couple of annoying problems, expecially this one:

Quote:

- fix: if the vbr is moved by WHDLoad the interrupts of levels 4-6 (vectors $70..$78) are directly forwarded to the installed program now, in previous releases all the sanity checks and checks for the keyboard were done in each interrupt which has increased the latency and duration of the interrupts, now these checks are only performed in interrupt levels 1-3 or if the option CheckInts/S is used for all levels it seems that the increased amount of code put into the interrupts by the later WHDLoad versions has caused problems with several games, this is hopefully fixed now and these games will work with the current WHDLoad as good as with versions 16.8 or 16.9

Maybe just maybe you can switch directly to this new 17.1 Beta

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@Cass Quote:

1) Always on the first launch 2) No, with every game on the first launch 3) After the first launch, I may relaunch and it works as it should be working on the first place

On the first launch of RunInUAE, or of any WHDLoad game? i.e. If you run one WHDLoad game, and then run another WHDLoad game, do you get problems with the second WHDLoad game?

Also, is RunInUAE running (in the background) before you run any WHDLoad games?


Anyway, please create a complete backup of your RunInUAE installation using the following program:
http://cshandley.co.uk/temp/RunInUAE_Debug_Backup.lha
(it will also be included with RunInUAE r7)

And then send your RunInUAE backup to me. This will be REALLY helpful.

_________________
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!

Just so people know: Cass found that his WHDLoad game problem was because he was starting WHDLoad games using iGame.

I have now found & fixed the iGame problem for the next release of RunInUAE, so you will be able to use iGame (again).

_________________
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!