"Exception "Line 1111 Emulator" ($2c) Error at $1004" when exiting game
I get the "Line 1111 Emulator" error quite often when I exit a WHDload game. The specific error in topic was from CannonFodderCD32. Not always, but maybe 50% of the time. It doesn't happen mid-game, and savegames are also written as they should, so it isn't really a problem, except it's not right to look at. :)
Any idea what causes this? Using A1200+ACA1232+IndyAGAMkII+4GB CF. |
I used to get these all the time. Could be a maxtransfer problemwith your drive.
Read here: http://eab.abime.net/showthread.php?t=55425 http://eab.abime.net/showthread.php?t=17165 I fixed the maxstransfer of my ddrive and still go some of them. I never figured out what is going on. i don't know if it is WHDLoad's fault or what. I just gave up and now play my games on my CD32. |
Edit: Forget about this posting, it's completely wrong !! Sorry for my misinformation.
Line 1111 = Line F (EDIT: like the F in floatingpoint or FPU means) could mean that an FPU is missing !! However, even the latest, so called FINAL WHDLoad 17.1 is still very buggy. Enforcer still throws lots of hits. It seems that the author of WHDLoad has never heard of Enforcer and other debugging tools. But I don't care, because I will never play any (EDIT silly) games. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Alright, there are some things wrong in my statement.
Matthey is right, the "Line F emulator" can be caused by other coprocessor instructions too. My mistake. And yes, as StingRay says, I better should not blame the author of WHDLoad without knowing the real reason for the Enforcer hits. Removed the rest. It was wrong, too. |
Quote:
At least in my version for real miggy I don't have hits but when I start Workbench 2000 as I was having before (just booting). But it has the same enforcer hits running WB2000 in CWB39, so I guess there are programs that although "run", have those hits. That doesn't mean that it has to show an error the kind of "Line 1111", that doesn't let you but to quit the program. Anyway, perhaps his error isn't a problem of WHDLoad, but of any other library that hasn't the right version for no FPU if he hasn't. |
Quote:
@PeterK It's frustrating when a low level program like WHDload does not behave as it's not easy to debug and patch. Your frustration shows that you realize the importance of WHDload to the Amiga even if you don't play games. |
Quote:
|
Quote:
|
Quote:
MMU is disabled, and the ACA1232 has no FPU. Is there any way to list what WHDload detects about my system? |
This is the best post about how to know exactly what happens:
http://eab.abime.net/showpost.php?p=832698&postcount=3 Run it in WinUAE and better windowed. You can later leave commented winuaeenforcer in the s-s and the rest working forever. Edit: Or better comment them all as for the following post of PeterK. |
Sorry for my assumption or imputation that the author of WHDLoad doesn't know and care about the Enforcer hits.
I've just read a few lines in the WHDLoad documentation and now I must admit that these Enforcer hits which I always get with AmiKit are obviously no bugs in WHDLoad (I'm not talking about the Line 1111 emulator now). The author of this program says that Enforcer or MuForce or similar tools should not be used together with WHDLoad or you will get lots of these hits. So, StingRay's comment was correct. |
I hadn't try enforcer with the real Amikit, and it's true. I've tried to open a game; in this case Advantage Tennis and it was showing a lot of hits.
But I've tried with enforcer and CWB39 and I've got the same enforcer hits trying to open the same game. Edit: Sorry it seems I didn't undertand your post at all, PeterK. Now I do: you can't run enforcer with Whdload. But it's also true that I was having hits with Amikit just booting that I don't have in my version. |
All times are GMT +2. The time now is 01:39. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.