#224 Daggerfall fails to work with AMD64 Builds

0.63
closed
5
2012-09-07
2005-04-11
Brian Hill
No

With the AMD64 Native version of DOSBox, attempting to
run Daggerfall results in an Internal Error with an
error message stating that the program cannot access
data in either Dagger.snd or ARCH3D.bsa. This occurs
with both the Daggerfall Demos as well as the Full
Version and in both 64-bit 0.63 and CVS.

Debug output does not provide much useful information
though I haven't had time to use some of the more
advanced debugging options, I only glanced at the debug
output. The game will crash upon selecting a province
your character is from; a time normally a sound is played.

The same Daggerfall install runs fine on 32-bit
versions of DOSBox.

Discussion

1 2 3 > >> (Page 1 of 3)
  • Brian Hill
    Brian Hill
    2005-04-11

    Logged In: YES
    user_id=373610

    By the way, I am running Gentoo Linux AMD64 2005.0 and the
    other games that I have tried (Descent, Dark Ages) work fine.

     
  • Brian Hill
    Brian Hill
    2005-04-12

    Logged In: YES
    user_id=373610

    I ran the debugger some more tonight and this is what it
    outputs right before the game crashes.

    105397569: FILES:file open command 0 file
    c:\dagdemo\arena2\map100i0.img
    105452384: MOUSE:Set sensitivity used with 49 49
    105468357: PIC:0 mask D9
    105468365: PIT:PIT 0 Timer at 90.00 Hz mode 3
    105468369: PIC:0 mask D8
    105468411: PIC:0 mask D9
    105468649: PIC:0 mask D8
    105469892: PIC:0 mask D9
    105469900: PIT:PIT 0 Timer at 18.21 Hz mode 3
    105469904: PIC:0 mask D8
    105469945: PIC:0 mask D9
    105470154: PIC:0 mask D8
    105470247: PIC:0 mask F8
    105470257: SBLASTER:DMA masked,stopping output, left 1357
    105470327: PIC:0 mask F8
    105472159: DOSMISC:DOS:Multiplex Unhandled call 1600
    105472660: DOSMISC:DOS:Multiplex Unhandled call 1600
    105482083: PIC:0 mask FC
    106531424: MISC:MPU-401:Reset FF
    110731845: PIC:0 mask F8
    110732163: CPU:Illegal Unhandled Interrupt Called A
    110759133: PIC:0 mask F9
    110759162: PIC:0 mask F9
    110759675: PIT:PIT 0 Timer set without new control word
    110759675: PIT:PIT 0 Timer at 18.21 Hz mode 3
    110759679: PIC:0 mask F8
    110759708: PIC:0 mask F8
    110773880: INT10:Set Video Mode 3
    110773880: VGA:Blinking 8
    111191646: FILES:file open command 0 file
    C:\DAGDEMO\ARENA2\BETHESDA.INF
    111191900: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111191915: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111191930: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111191945: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111191960: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111191975: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111191990: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192005: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192020: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192035: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192050: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192065: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192080: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192095: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192110: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192125: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192140: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192155: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192170: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192185: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192200: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192215: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192230: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111192245: DOSMISC:DOS:Multiplex Unhandled call 4A10
    111194241: VGA:H total 100, V Total 449
    111194241: VGA:H D End 80, V D End 400
    111194241: VGA:Width 640, Height 400, fps 70.086304
    111194241: VGA:normal width, normal height aspect 1.000000

     
  • Peter Veenstra
    Peter Veenstra
    2005-04-12

    Logged In: YES
    user_id=535630

    hmm I would suspect an fileposition errror.
    you might want to check for fseek and friends to check if
    they behave correctly.

     
  • Brian Hill
    Brian Hill
    2005-04-12

    Logged In: YES
    user_id=373610

    How would I check to see if fseek is working?

     
  • Peter Veenstra
    Peter Veenstra
    2005-04-13

    Logged In: YES
    user_id=535630

    in the file drive_local.cpp in src/dos around line 429 you
    notice an

    if 0

    try enabeling it and remove the line below the #endif

    -----now-----

    if 0

        fpos_t temppos;
        fgetpos(fhandle,&temppos);
        Bit32u * fake_pos=(Bit32u*)&temppos;
        *pos=*fake_pos;
    

    endif

        *pos=(Bit32u)ftell(fhandle);
    

    ----try---------

    if 1

        fpos_t temppos;
        fgetpos(fhandle,&temppos);
        Bit32u * fake_pos=(Bit32u*)&temppos;
        *pos=*fake_pos;
    

    endif

    // *pos=(Bit32u)ftell(fhandle);

     
  • Brian Hill
    Brian Hill
    2005-04-13

    Logged In: YES
    user_id=373610

    I tried that and I'm still getting the same error.

     
  • Peter Veenstra
    Peter Veenstra
    2005-04-13

    Logged In: YES
    user_id=535630

    hmm I would need the full logfile inorder to see what might
    be wrong.

    if you use the debug version you can create a new configfile
    file.
    that one has extra entries in it.
    one of the entries is logfile=
    set it to a reasonable file.

    If you could do it for the 32 and 64 bits version.
    if something nice occurs I will provide you with some
    instructions to get huge amount of relevant log messages (by
    adding some log messages to dos core).

     
  • Brian Hill
    Brian Hill
    2005-04-13

    Logged In: YES
    user_id=373610

    For some reason dosbox wasn't recognizing the logfile=
    command. perhaps I put it in the wrong section.

    I redirected stdio to a file however with debug mode enabled
    so it should provide similar information.

    I do not currently have a 32-bit binary with debug mode
    enabled. If you could provide one I could run debug on it as
    well.

     
  • Brian Hill
    Brian Hill
    2005-04-13

    Debug Log (64-bit)

     
    Attachments
  • Peter Veenstra
    Peter Veenstra
    2005-04-14

    Logged In: YES
    user_id=535630

    I will try to find the Demo as well. as I run a 32 bit
    version of dosbox.

    There are some odd things in there I want to see wether this
    game is really this odd. (as it opens the same file many
    times. it makes little sense. (at least to me)

     
1 2 3 > >> (Page 1 of 3)