#129 Prince of Persia 2 Random Crashes

0.58
closed
None
5
2012-09-07
2003-04-21
Lorenzo Grande
No

Floppy Version. Configured to use SBPro/SBPro/High mem
if avail./Keyboard
Sound card settings set to autodetect IRQs

The games works near perfectly, but randomly crashes
without any logic and very frequently in different
places/events(and to the end of the third level of the
grottas don't go any further and crashes everyday) . I
don't was able to register the crashes exceptions , i
tried with drwatson , but it seems to ignore them.What
to use?
Thanks

Discussion

  • Richard
    Richard
    2003-11-19

    Logged In: YES
    user_id=547613

    This seems to be fixed with DosBox 0.60.

     
  • Lorenzo Grande
    Lorenzo Grande
    2003-11-22

    Logged In: YES
    user_id=761667

    The 0.60 version has fixed the problems between levels,but
    has introduced another one problem: the game now crashes or
    doesn't go any further between screens . I exit from a
    screen and the next screen doesn't show. It is fully black.
    The music also stops. But the emulator is still running,and
    the dialog box does'nt say nothing

     
  • Lorenzo Grande
    Lorenzo Grande
    2004-02-14

    Logged In: YES
    user_id=761667

    With the 0.61 all the previous problems seem to be fixed.But
    now there is a new one problem . The game goes perfectly till
    the start of the third level of the grottas. Then very
    frequently,in the first screen or second ,everything freezes
    and the prince disappears. Dosbox is however still alive and
    the dialog box says ,in a continue cycle (like a endless
    while,countinously refreshing the message),SDL Lock Failed.

     
  • Lorenzo Grande
    Lorenzo Grande
    2004-10-09

    Logged In: YES
    user_id=761667

    With DosBox 0.62 Prince of Persia works flawless, but
    sometime (very rarely) the game freezes without reasons.The
    dialog box says nothing and the emulator is still running
    and apparently not in deadlock status,he replies fast to the
    quit comand.
    All the previous bugs reported does not happen anymore.

     
  • Lorenzo Grande
    Lorenzo Grande
    2004-10-09

    Logged In: YES
    user_id=761667

    Ahem: another more recent thing: the game has crashed saying
    me, in the main window "insufficent near memory". Then the
    emulator has crashed with windows saying me (this is a
    translation): "The instruction at "0x6ac874f0" has referred
    at the memory at "0x0554c670". The memory can't be "read".
    Click for close the program." I'm using Windows 2000 Sp4

     
  • Peter Veenstra
    Peter Veenstra
    2004-10-12

    Logged In: YES
    user_id=535630

    hmm i was about to close the report as the bug seemed to be
    fixed.

    Any change on reproducing this bug ?

     
  • Lorenzo Grande
    Lorenzo Grande
    2004-10-16

    Logged In: YES
    user_id=761667

    It is very difficult to say: it everyday happens here.
    Everytime the freeze happens in different places, sometime a
    place freezes, the next time the same place doesen't
    freezes. Fortunately the freezes are happening
    unfrequently,one every about 20 minutes. The quit command
    that i use for shutdown the emulator is CTRL F9. However i
    can say more about the "The instruction at "0x6ac874f0" has
    referred at the memory at "0x0554c670" . It everyday
    happens, with game loaded or not, when i try to close the
    dosbox message window (not the shell) with the "x" in the
    right top of that window (where are the other two buttons
    for minimizing and for docking the window). Today the
    message was: "The instruction at "0x6ac874f0" has referred
    at the memory at "0x0554c6c8".The memory can't be
    "read".Click for close the program." When i play i take care
    to shut down every program, including Antivirus.There was an
    error on the OS that i use: i'm using WinXp Sp1, sorry, i
    have used for many time Win 2000 Sp4, and i have confused.
    When i will have some more info i will post .

     
  • Lorenzo Grande
    Lorenzo Grande
    2004-10-16

    Logged In: YES
    user_id=761667

    Finally i have a crash that happens everytime. It's not a
    freeze, Dosbox crashes entirely. At the third level of the
    grottas, just take the flying carpet when the roof is
    closed. The prince deaths, and appears "push a key to
    continue". If you push a key (usually i push Left Ctrl)
    Dosbox crashes. When crashes, the dialog box shutdowns with
    few time for read what is written. The few i have read is
    "Fatal Error". However this is an extra issue, not regarding
    the freeze already mentioned. For switching faster in the
    levels, i have founded gamesaves of Prince2 on
    abandonware-france.org

     
  • Lorenzo Grande
    Lorenzo Grande
    2004-11-27

    Logged In: YES
    user_id=761667

    I've made a fresh win2000Sp4 install and i've completed
    succesfully the game 2 times on 0.63, without any flaw. The
    only bug that seems happen ever is the already described on
    the magic carpet. Dosbox 0.63 console in that case writes:
    "Exit to error: CPU:GRP5:Illegal Call 7". I've checked on
    the Dos inside Windows, happens also there. Windows say that
    the Cpu has "met" an invalid instruction.
    However there's another thing: everyday in the stage where
    the prince gets the blue flame if the prince drops from the
    last ravine before the flame (the screen is contiguous with
    the real exit door) appears ingame, with the game graphic, a
    screen that says: "error in loadshad(). Quit?" with two
    options: "yes" and "no". Only no works. The game shut down
    on the dos shell. Dosbox(both 0.62 & o.63) still alive and
    working. I've checked, it happens also outside Dosbox on
    Windows dos. So it seems that POP2 inside DosBox finally run
    perfectly, also emulating the bugs of the original version.
    Great work!

     
  • Peter Veenstra
    Peter Veenstra
    2004-11-27

    Logged In: YES
    user_id=535630

    I'm glad we are able to emulate the games native bugs.

    Shows that we have improved and that it's time to move on

    Closing this report.