DOSBox-X branch

Here you can discuss the development of patches.

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-8-03 @ 23:11

bfcastello wrote:
TheGreatCodeholio wrote:
bfcastello wrote:I have a small issue, not DOSBox-X related, but I believe someone here can help.

When I try to run SimCity 2000 from DOS, "C:\Games\SC2000\SC2000.exe" I get this message:

"Critical Error, Microsoft compatable mouse not found. Please load mouse driver"

Any ideas, please? Tks in advance.


Should not happen unless int33=false is in your dosbox.conf or you are booting a bootdisk to run the game without a mouse driver in the guest OS.

I know that Sim City 2000 is also one of those games that may get unstable or crashy if loaded too low in memory, try LOADFIX first.


I'm actually booting from a boot disk. I guess that I need a mouse driver...

Edit: Fixed with the installation of a mouse driver for DOS (MOUSE.COM). Never thought I would forget simple things I knew 25 years ago.


That's correct. DOSBox-X and DOSBox SVN cannot provide INT 33h emulation to a bootdisk, it can only provide in the built-in DOS system.
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby bfcastello » 2019-8-11 @ 01:13

OK, now I am going to play a DOS version of Spycraft: The Great Game... The game requires swapping between 3 CDs (something I have worked out how to do in DOSBox, so moving to the next question)

How do I make DOSBox ask me if I want to load the disk images before starting the boot process? I mean, ask me if I want to run the imgmount command with the parameters I wrote before the boot -l c?
"Design isn't just what it looks like and feels like. Design is how it works."
JOBS, Steve.
User avatar
bfcastello
Member
 
Posts: 419
Joined: 2017-9-07 @ 02:39
Location: Rio de Janeiro, Brazil and Catalonia, Spain

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-8-11 @ 01:24

bfcastello wrote:OK, now I am going to play a DOS version of Spycraft: The Great Game... The game requires swapping between 3 CDs (something I have worked out how to do in DOSBox, so moving to the next question)

How do I make DOSBox ask me if I want to load the disk images before starting the boot process? I mean, ask me if I want to run the imgmount command with the parameters I wrote before the boot -l c?


Currently you'll need to provide all ISO images to swap between with IMGMOUNT, just as you do now with DOSBox-X.

There is a mapper shortcut to swap CDs, just as there is another for swapping floppy disks.
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-8-11 @ 01:26

A problem has been identified in the built-in EGA.CPI files when locale data is loaded at boot up that puts the characters a bit too low for a game.

It's possible that real MS-DOS has the same problem, and the developer of this QBasic based game didn't test against any MS-DOS installation that loads locale/CPI data. The bug occurs because the game uses the EGA 640x350 mode, expects the BIOS to render 8x14 text, and only uses the top 12 rows of the font bitmap, which happens to work with the BIOS 8x14 font.

To be clear, it makes the large styled pixel text effect by printing on the screen and then using QBasic POINT() to read it back and redraw as larger rectangles.

I believe these builtin CPI/CPX files were inherited as-is from the main DOSBox SVN project, and might be worth looking into.

https://github.com/joncampbell123/dosbox-x/issues/1196
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby bfcastello » 2019-8-11 @ 01:33

TheGreatCodeholio wrote:
bfcastello wrote:OK, now I am going to play a DOS version of Spycraft: The Great Game... The game requires swapping between 3 CDs (something I have worked out how to do in DOSBox, so moving to the next question)

How do I make DOSBox ask me if I want to load the disk images before starting the boot process? I mean, ask me if I want to run the imgmount command with the parameters I wrote before the boot -l c?


Currently you'll need to provide all ISO images to swap between with IMGMOUNT, just as you do now with DOSBox-X.

There is a mapper shortcut to swap CDs, just as there is another for swapping floppy disks.


Yeah, I did it. I also found a way to select what to do before boot. To sum up, First I mount my C: image, then run a batch file named C:\PLAY.BAT, where I used a code from the iOS version of DOSBox (iDOS2/DOSPad) from Litchie. I changed it to a select of only two options, normal boot and a boot with the three images selected. Done. Just had to run DOSBox-X, it runs PLAY.BAT, and if I choose 2 (SpyCraft), it mounts the CD images then boot C. Option 1 just boots C:. Excellent.
"Design isn't just what it looks like and feels like. Design is how it works."
JOBS, Steve.
User avatar
bfcastello
Member
 
Posts: 419
Joined: 2017-9-07 @ 02:39
Location: Rio de Janeiro, Brazil and Catalonia, Spain

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-8-28 @ 01:13

Hey, found an issue with the FAT drive support. It affects both DOSBox-X and DOSBox SVN and it probably affects other branches as well.

Writing a file and stopping at a multiple of the cluster size causes an extra cluster to be allocated.
For example if the cluster size is 4096, writing 4096*N bytes causes this error.

It doesn't corrupt your disk images but SCANDISK will pick it up and complain about it, and helpfully increase the file size in the directory entry to include the extra garbage data therefore adding garbage to your files.

https://github.com/joncampbell123/dosbox-x/issues/1224

There's also an issue, fixed in DOSBox-X, that directories created in DOSBox through the FAT filesystem driver have a creation/modified date of 1980-00-00 00:00:00
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby _Rob » 2019-9-06 @ 14:01

Since you added proper MDA and MCGA, there was also Plantronics, and there is even a game now that supports it.
http://www.the8bitguy.com/4032/where-is-planet-x3/
I had an ATI videocard back in the 80's that had a Plantronics mode.

Other then that there was also the IBM 8514, a successor to VGA. I had a ATI Mach 8 back in the day that emulated it. It worked good enough that OS/2 2.0 would work in 1024x768 out of the box. I don't think any games exist that support it. But it worked with Autocad.

And then there was IBM's XGA. Never had it, and I'm not aware of any games that support it.

The 8514 and XGA are only really useful is your wanting to emulate very early OS/2 versions, as they were supported out of the box with high resolution and 256 colours. The 8514 was supposedly supported in OS/2 1.2 and the XGA in OS/2 1.3.
http://www.os2museum.com/wp/the-8514a-g ... celerator/
http://www.os2museum.com/wp/the-xga-graphics-chip/
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-9-06 @ 16:51

_Rob wrote:Since you added proper MDA and MCGA, there was also Plantronics, and there is even a game now that supports it.
http://www.the8bitguy.com/4032/where-is-planet-x3/
I had an ATI videocard back in the 80's that had a Plantronics mode.

Other then that there was also the IBM 8514, a successor to VGA. I had a ATI Mach 8 back in the day that emulated it. It worked good enough that OS/2 2.0 would work in 1024x768 out of the box. I don't think any games exist that support it. But it worked with Autocad.

And then there was IBM's XGA. Never had it, and I'm not aware of any games that support it.

The 8514 and XGA are only really useful is your wanting to emulate very early OS/2 versions, as they were supported out of the box with high resolution and 256 colours. The 8514 was supposedly supported in OS/2 1.2 and the XGA in OS/2 1.3.
http://www.os2museum.com/wp/the-8514a-g ... celerator/
http://www.os2museum.com/wp/the-xga-graphics-chip/


I was able to obtain a Plantronics ColorPlus card from eBay some time back so that I could support it in DOSLIB and add DOSBox-X emulation. When development happens I will be able to study and implement real hardware behavior as close as possible.
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby pantercat » 2019-9-06 @ 19:51

Hello, I'm having problems with the debugger in the latest versions of dosbox-x

Until version 0.82.14 (at least) it worked fine, but in the latest versions (I have tried 0.82.18, 0.82.20 and 0.82.21) when I try to modify some byte in memory with the sm instruction. ie:

sm 9000:00000134 90 90
sm 9000:0134 90 90

It seems that it does not take into account the value of the segment and I get the following error and the bytes in memory are not changed.

GetHexValue parse error at: 0134 90 90
GetHexValue parse error at: 00000134 90 90

I'm using debian testing and have compiled dosbox-x with ./build-debug

Thank you and keep up the good work.
pantercat
Newbie
 
Posts: 47
Joined: 2018-9-06 @ 17:22

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-9-06 @ 20:05

I might have accidentally broken the parsing for seg:off specifications, try replacing the ':' with a space.

sm 9000 00000134 90 90
sm 9000 0134 90 90
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby pantercat » 2019-9-06 @ 20:23

It works! Thank you very much! :)
pantercat
Newbie
 
Posts: 47
Joined: 2018-9-06 @ 17:22

Re: DOSBox-X branch

Postby _Rob » 2019-9-09 @ 07:21

I'm having a strange problem with the latest release builds on both Linux and Windows with Win98SE.

When I start it, it crashes just after the Win98SE splash screen. Here is the log
Code: Select all
$ dosbox-x --conf win98se.conf
LOG: Early LOG Init complete
LOG: Logging init: beginning logging proper. This is the end of the early init logging
LOG: Logging: No logfile was given. All further logging will be discarded.
LOG: DOSBox-X version 0.82.21
LOG: Current X11 keyboard layout (token) is: 'us'
LOG: Host keyboard layout is now us (US English)
LOG: Mapper keyboard layout is now us (US English)
LOG: SDL1 auto-detected desktop as 3632 x 1200
LOG: X11 main window is 640 x 400 maximized=0
LOG: X11 extension XRANDR is available
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,400) match=(2280,242)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: ISA BCLK: 8333333.333Hz (25000000/3)
LOG: monopal: green,
LOG: USING AVI+ZMBV
LOG: Max 3670016 sz 262144
LOG: Final 262144
LOG: SDLNet_TCP_Open: Couldn't connect to remote host
LOG: TiMidity: can't open control connection (host=127.0.0.1, port=7777)
LOG: MT32 emulation cannot work without the PCM and CONTROL ROM files.
LOG: To eliminate this error message, either change mididevice= to something else, or
LOG: place the ROM files in what will be the "current working directory" for DOSBox-X
LOG: when it starts up and initializes MIDI emulation.
LOG: The ROM files are: CM32L_CONTROL.ROM, MT32_CONTROL.ROM, CM32L_PCM.ROM, MT32_PCM.ROM
LOG: Pentium CMPXCHG8B emulation is enabled
LOG: VOODOO LFB now at d0000000
LOG: MPU-401 Registering I/O ports as if IBM PC MPU-401 at base 330h
LOG: GetDesktopResolution reading X11 desktop resolution
LOG: Root window (ID 684) is 3632 x 1200
LOG: X11 main window is 640 x 400 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,400) match=(2280,242)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: Allocated APM BIOS pm entry point at f000:e8ac
LOG: Writing code to fe8ac
LOG: FDC installing to io=3f0h IRQ=6 DMA=2
LOG: IDE: Not registering port 3F7h, FDC will occupy it.
LOG: X11 main window is 640 x 400 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,400) match=(2280,242)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: ISA Plug & Play BIOS enabled
LOG: VGA ROM BIOS init callback
LOG: pixratio 1.000, dw false, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 497 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,497) match=(2280,290)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 497 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,497) match=(2280,290)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG:    1734639 ERROR BIOS:Keyboard layout file auto not found
LOG:    1734639 ERROR BIOS:Keyboard layout file auto not found
LOG: XMS: 50 handles allocated for use by the DOS environment
LOG: EMS page frame at 0xe000-0xefff
LOG: COMMAND.COM env size:             720 bytes
LOG: COMMAND.COM environment block:    0x021a sz=0x002d
LOG: COMMAND.COM main body (PSP):      0x0248 sz=0x009a
LOG: COMMAND.COM stack:                0x0262
LOG: pixratio 1.350, dw false, dh false
LOG: Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 497 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,497) match=(2280,290)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: IDE: index 0 slave=0
LOG: VHD image detected: 512,63,64,1023
LOG: Using partition 0 on drive (type 0x06); skipping 63 sectors
LOG: FAT: BPB says 63 sectors/track 64 heads 512 bytes/sector
LOG: Mounted FAT volume is FAT16 with 64439 clusters
LOG: Mapping BIOS DISK C/H/S 1023/64/63 as IDE 4092/16/63
LOG: IDE: index 1 slave=0
LOG: Booting guest OS stack_seg=0x7000 load_seg=0x07c0
LOG: Removing UMB block 0xcc00-0xdfff
LOG: Alright: DOS kernel shutdown, booting a guest OS
LOG:   CS:IP=0000:7c00 SS:SP=7000:0100 AX=0000 BX=7c00 CX=0001 DX=0080
LOG:    1776391 ERROR BIOS:Disk 0 not active
LOG:    1777842 ERROR BIOS:INT15:Unknown call ax=4101
LOG: pixratio 1.200, dw true, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG:    6137858 ERROR BIOS:INT15:Unknown call ax=2403
LOG:    6303879 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303893 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303907 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303921 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303935 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303949 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303963 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303977 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6303991 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304005 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304019 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304033 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304047 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304061 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304075 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6304089 ERROR BIOS:INT15:Unknown call ax=D800
LOG:    6405259 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG:    9176833 ERROR BIOS:INT1A:Undefined call B0
LOG: pixratio 1.350, dw false, dh false
LOG: Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: pixratio 1.200, dw true, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: XRandR CRTC 1: pos=(0,0) size=(1920,1200) outputs=1
LOG: Our window lies on this CRTC display (window pos=(437,117) size=(720,417) match=(797,325)).
LOG:   Goes to output 0: name='XWAYLAND4' size_mm=(520 x 320)
LOG: Screen report: Method 'XRandR' (1920.000 x 1200.000 pixels) at (0.000 x 0.000) (520.000 x 320.000 mm) (20.472 x 12.598 in) (93.785 x 95.250 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: XRandR CRTC 1: pos=(0,0) size=(1920,1200) outputs=1
LOG: Our window lies on this CRTC display (window pos=(437,117) size=(640,417) match=(757,325)).
LOG:   Goes to output 0: name='XWAYLAND4' size_mm=(520 x 320)
LOG: Screen report: Method 'XRandR' (1920.000 x 1200.000 pixels) at (0.000 x 0.000) (520.000 x 320.000 mm) (20.472 x 12.598 in) (93.785 x 95.250 DPI)
LOG:  120564910 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG:  130285696 ERROR BIOS:Disk 0 not active
LOG: INT13: Check Extensions Present for drive: 0x80
LOG:  143355094 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG:  152277180 ERROR CPU:Write 0 to rom at e00a0
LOG:  152277181 ERROR CPU:Write ffff to rom at e00a2
LOG:  152277202 ERROR CPU:Write ffff to rom at e00a2
LOG:  152277204 ERROR CPU:Write ffff to rom at e00a0
LOG:  152277220 ERROR CPU:Write 0 to rom at e08a0
LOG:  152277221 ERROR CPU:Write ffff to rom at e08a2
LOG:  152277242 ERROR CPU:Write ffff to rom at e08a2
LOG:  152277244 ERROR CPU:Write ffff to rom at e08a0
LOG:  152277361 ERROR CPU:Write 0 to rom at e10a0
LOG:  152277362 ERROR CPU:Write ffff to rom at e10a2
LOG:  152277383 ERROR CPU:Write ffff to rom at e10a2
LOG:  152277385 ERROR CPU:Write ffff to rom at e10a0
LOG:  152277401 ERROR CPU:Write 0 to rom at e18a0
LOG:  152277402 ERROR CPU:Write ffff to rom at e18a2
LOG:  152277423 ERROR CPU:Write ffff to rom at e18a2
LOG:  152277425 ERROR CPU:Write ffff to rom at e18a0
LOG:  152277542 ERROR CPU:Write 0 to rom at e20a0
LOG:  152277543 ERROR CPU:Write ffff to rom at e20a2
LOG:  152277564 ERROR CPU:Write ffff to rom at e20a2
LOG:  152277566 ERROR CPU:Write ffff to rom at e20a0
LOG:  152277582 ERROR CPU:Write 0 to rom at e28a0
LOG:  152277583 ERROR CPU:Write ffff to rom at e28a2
LOG:  152277604 ERROR CPU:Write ffff to rom at e28a2
LOG:  152277606 ERROR CPU:Write ffff to rom at e28a0
LOG:  152277723 ERROR CPU:Write 0 to rom at e30a0
LOG:  152277724 ERROR CPU:Write ffff to rom at e30a2
LOG:  152277745 ERROR CPU:Write ffff to rom at e30a2
LOG:  152277747 ERROR CPU:Write ffff to rom at e30a0
LOG:  152277763 ERROR CPU:Write 0 to rom at e38a0
LOG:  152277764 ERROR CPU:Write ffff to rom at e38a2
LOG:  152277785 ERROR CPU:Write ffff to rom at e38a2
LOG:  152277787 ERROR CPU:Write ffff to rom at e38a0
LOG:  152277904 ERROR CPU:Write 0 to rom at e40a0
LOG:  152277905 ERROR CPU:Write ffff to rom at e40a2
LOG:  152277926 ERROR CPU:Write ffff to rom at e40a2
LOG:  152277928 ERROR CPU:Write ffff to rom at e40a0
LOG:  152277944 ERROR CPU:Write 0 to rom at e48a0
LOG:  152277945 ERROR CPU:Write ffff to rom at e48a2
LOG:  152277966 ERROR CPU:Write ffff to rom at e48a2
LOG:  152277968 ERROR CPU:Write ffff to rom at e48a0
LOG:  152278085 ERROR CPU:Write 0 to rom at e50a0
LOG:  152278086 ERROR CPU:Write ffff to rom at e50a2
LOG:  152278107 ERROR CPU:Write ffff to rom at e50a2
LOG:  152278109 ERROR CPU:Write ffff to rom at e50a0
LOG:  152278125 ERROR CPU:Write 0 to rom at e58a0
LOG:  152278126 ERROR CPU:Write ffff to rom at e58a2
LOG:  152278147 ERROR CPU:Write ffff to rom at e58a2
LOG:  152278149 ERROR CPU:Write ffff to rom at e58a0
LOG:  152278266 ERROR CPU:Write 0 to rom at e60a0
LOG:  152278267 ERROR CPU:Write ffff to rom at e60a2
LOG:  152278288 ERROR CPU:Write ffff to rom at e60a2
LOG:  152278290 ERROR CPU:Write ffff to rom at e60a0
LOG:  152278306 ERROR CPU:Write 0 to rom at e68a0
LOG:  152278307 ERROR CPU:Write ffff to rom at e68a2
LOG:  152278328 ERROR CPU:Write ffff to rom at e68a2
LOG:  152278330 ERROR CPU:Write ffff to rom at e68a0
LOG:  152278447 ERROR CPU:Write 0 to rom at e70a0
LOG:  152278448 ERROR CPU:Write ffff to rom at e70a2
LOG:  152278469 ERROR CPU:Write ffff to rom at e70a2
LOG:  152278471 ERROR CPU:Write ffff to rom at e70a0
LOG:  152278487 ERROR CPU:Write 0 to rom at e78a0
LOG:  152278488 ERROR CPU:Write ffff to rom at e78a2
LOG:  152278509 ERROR CPU:Write ffff to rom at e78a2
LOG:  152278511 ERROR CPU:Write ffff to rom at e78a0
LOG:  152278628 ERROR CPU:Write 0 to rom at e80a0
LOG:  152278629 ERROR CPU:Write ffff to rom at e80a2
LOG:  152278650 ERROR CPU:Write ffff to rom at e80a2
LOG:  152278652 ERROR CPU:Write ffff to rom at e80a0
LOG:  152278668 ERROR CPU:Write 0 to rom at e88a0
LOG:  152278669 ERROR CPU:Write ffff to rom at e88a2
LOG:  152278690 ERROR CPU:Write ffff to rom at e88a2
LOG:  152278692 ERROR CPU:Write ffff to rom at e88a0
LOG:  152278809 ERROR CPU:Write 0 to rom at e90a0
LOG:  152278810 ERROR CPU:Write ffff to rom at e90a2
LOG:  152278831 ERROR CPU:Write ffff to rom at e90a2
LOG:  152278833 ERROR CPU:Write ffff to rom at e90a0
LOG:  152278849 ERROR CPU:Write 0 to rom at e98a0
LOG:  152278850 ERROR CPU:Write ffff to rom at e98a2
LOG:  152278871 ERROR CPU:Write ffff to rom at e98a2
LOG:  152278873 ERROR CPU:Write ffff to rom at e98a0
LOG:  152278990 ERROR CPU:Write 0 to rom at ea0a0
LOG:  152278991 ERROR CPU:Write ffff to rom at ea0a2
LOG:  152279012 ERROR CPU:Write ffff to rom at ea0a2
LOG:  152279014 ERROR CPU:Write ffff to rom at ea0a0
LOG:  152279030 ERROR CPU:Write 0 to rom at ea8a0
LOG:  152279031 ERROR CPU:Write ffff to rom at ea8a2
LOG:  152279052 ERROR CPU:Write ffff to rom at ea8a2
LOG:  152279054 ERROR CPU:Write ffff to rom at ea8a0
LOG:  152279171 ERROR CPU:Write 0 to rom at eb0a0
LOG:  152279172 ERROR CPU:Write ffff to rom at eb0a2
LOG:  152279193 ERROR CPU:Write ffff to rom at eb0a2
LOG:  152279195 ERROR CPU:Write ffff to rom at eb0a0
LOG:  152279211 ERROR CPU:Write 0 to rom at eb8a0
LOG:  152279212 ERROR CPU:Write ffff to rom at eb8a2
LOG:  152279233 ERROR CPU:Write ffff to rom at eb8a2
LOG:  152279235 ERROR CPU:Write ffff to rom at eb8a0
LOG:  152279352 ERROR CPU:Write 0 to rom at ec0a0
LOG:  152279353 ERROR CPU:Write ffff to rom at ec0a2
LOG:  152279374 ERROR CPU:Write ffff to rom at ec0a2
LOG:  152279376 ERROR CPU:Write ffff to rom at ec0a0
LOG:  152279392 ERROR CPU:Write 0 to rom at ec8a0
LOG:  152279393 ERROR CPU:Write ffff to rom at ec8a2
LOG:  152279414 ERROR CPU:Write ffff to rom at ec8a2
LOG:  152279416 ERROR CPU:Write ffff to rom at ec8a0
LOG:  152279533 ERROR CPU:Write 0 to rom at ed0a0
LOG:  152279534 ERROR CPU:Write ffff to rom at ed0a2
LOG:  152279555 ERROR CPU:Write ffff to rom at ed0a2
LOG:  152279557 ERROR CPU:Write ffff to rom at ed0a0
LOG:  152279573 ERROR CPU:Write 0 to rom at ed8a0
LOG:  152279574 ERROR CPU:Write ffff to rom at ed8a2
LOG:  152279595 ERROR CPU:Write ffff to rom at ed8a2
LOG:  152279597 ERROR CPU:Write ffff to rom at ed8a0
LOG:  152279714 ERROR CPU:Write 0 to rom at ee0a0
LOG:  152279715 ERROR CPU:Write ffff to rom at ee0a2
LOG:  152279736 ERROR CPU:Write ffff to rom at ee0a2
LOG:  152279738 ERROR CPU:Write ffff to rom at ee0a0
LOG:  152279754 ERROR CPU:Write 0 to rom at ee8a0
LOG:  152279755 ERROR CPU:Write ffff to rom at ee8a2
LOG:  152279776 ERROR CPU:Write ffff to rom at ee8a2
LOG:  152279778 ERROR CPU:Write ffff to rom at ee8a0
LOG:  152279895 ERROR CPU:Write 0 to rom at ef0a0
LOG:  152279896 ERROR CPU:Write ffff to rom at ef0a2
LOG:  152279917 ERROR CPU:Write ffff to rom at ef0a2
LOG:  152279919 ERROR CPU:Write ffff to rom at ef0a0
LOG:  152279935 ERROR CPU:Write 0 to rom at ef8a0
LOG:  152279936 ERROR CPU:Write ffff to rom at ef8a2
LOG:  152279957 ERROR CPU:Write ffff to rom at ef8a2
LOG:  152279959 ERROR CPU:Write ffff to rom at ef8a0
LOG: Plug & Play OS reports itself active
LOG: PNP OS changed I/O read port to 0x277 (from 0x20B)
LOG: PNP OS changed I/O read port to 0x37B (from 0x277)
LOG: PNP OS changed I/O read port to 0x33B (from 0x37B)
LOG: PNP OS changed I/O read port to 0x23B (from 0x33B)
LOG:  175551203 ERROR BIOS:INT1A:PCI BIOS: unknown function b10e (0 2b0 15a1)
LOG: VOODOO LFB now at ff000000
LOG: VOODOO LFB now at d0000000
LOG: APM BIOS: Connected to 32-bit protected mode interface
LOG: APM BIOS negotiated to v1.2
LOG: Unknown APM BIOS call AX=5312
LOG: enable APM for device    1
LOG: engage APM for device    1
LOG: enable APM for device    1
LOG: Unknown APM BIOS call AX=5311
LOG:  178900070 ERROR INT10:Unhandled VESA Function 15
LOG:  178991485 ERROR INT10:Unhandled VESA Function 10
LOG:  179484117 ERROR CPU:Illegal Unhandled Interrupt Called 20
LOG:  179484422 ERROR CPU:Illegal Unhandled Interrupt Called 20
LOG:  182918144 ERROR BIOS:INT15:Unknown call ax=F963
LOG: INT 15h mouse initialized to 3-byte protocol
LOG: INT 15h reporting mouse device ID 0x03
LOG: IDE ATA command 20 dh=0xa0 count=0x01 chs=00/00/01
LOG: FDC: Reset complete
LOG: FDC: Command len=1 0e 00 00 00 00 00 00 00 00 00
LOG: FDC: Response len=10 00 00 00 00 88 40 12 00 78 00


When I then start it again, I get the question if I want to enter safe mode, and I instead to select to boot normally and this works. Here is the log up to the desktop.
Code: Select all
$ dosbox-x -conf win98se.conf
LOG: Early LOG Init complete
LOG: Logging init: beginning logging proper. This is the end of the early init logging
LOG: Logging: No logfile was given. All further logging will be discarded.
LOG: DOSBox-X version 0.82.21
LOG: Current X11 keyboard layout (token) is: 'us'
LOG: Host keyboard layout is now us (US English)
LOG: Mapper keyboard layout is now us (US English)
LOG: SDL1 auto-detected desktop as 3632 x 1200
LOG: X11 main window is 640 x 400 maximized=0
LOG: X11 extension XRANDR is available
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,400) match=(2280,242)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: ISA BCLK: 8333333.333Hz (25000000/3)
LOG: monopal: green,
LOG: USING AVI+ZMBV
LOG: Max 3670016 sz 262144
LOG: Final 262144
LOG: SDLNet_TCP_Open: Couldn't connect to remote host
LOG: TiMidity: can't open control connection (host=127.0.0.1, port=7777)
LOG: MT32 emulation cannot work without the PCM and CONTROL ROM files.
LOG: To eliminate this error message, either change mididevice= to something else, or
LOG: place the ROM files in what will be the "current working directory" for DOSBox-X
LOG: when it starts up and initializes MIDI emulation.
LOG: The ROM files are: CM32L_CONTROL.ROM, MT32_CONTROL.ROM, CM32L_PCM.ROM, MT32_PCM.ROM
LOG: Pentium CMPXCHG8B emulation is enabled
LOG: VOODOO LFB now at d0000000
LOG: MPU-401 Registering I/O ports as if IBM PC MPU-401 at base 330h
LOG: GetDesktopResolution reading X11 desktop resolution
LOG: Root window (ID 684) is 3632 x 1200
LOG: X11 main window is 640 x 400 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,400) match=(2280,242)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: Allocated APM BIOS pm entry point at f000:e8ac
LOG: Writing code to fe8ac
LOG: FDC installing to io=3f0h IRQ=6 DMA=2
LOG: IDE: Not registering port 3F7h, FDC will occupy it.
LOG: X11 main window is 640 x 400 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,400) match=(2280,242)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: ISA Plug & Play BIOS enabled
LOG: VGA ROM BIOS init callback
LOG: pixratio 1.000, dw false, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 497 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,497) match=(2280,290)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 497 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,497) match=(2280,290)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG:    1202059 ERROR BIOS:Keyboard layout file auto not found
LOG:    1202059 ERROR BIOS:Keyboard layout file auto not found
LOG: XMS: 50 handles allocated for use by the DOS environment
LOG: EMS page frame at 0xe000-0xefff
LOG: COMMAND.COM env size:             720 bytes
LOG: COMMAND.COM environment block:    0x021a sz=0x002d
LOG: COMMAND.COM main body (PSP):      0x0248 sz=0x009a
LOG: COMMAND.COM stack:                0x0262
LOG: pixratio 1.350, dw false, dh false
LOG: Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 497 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,497) match=(2280,290)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: IDE: index 0 slave=0
LOG: VHD image detected: 512,63,64,1023
LOG: Using partition 0 on drive (type 0x06); skipping 63 sectors
LOG: FAT: BPB says 63 sectors/track 64 heads 512 bytes/sector
LOG: Mounted FAT volume is FAT16 with 64439 clusters
LOG: Mapping BIOS DISK C/H/S 1023/64/63 as IDE 4092/16/63
LOG: IDE: index 1 slave=0
LOG: Booting guest OS stack_seg=0x7000 load_seg=0x07c0
LOG: Removing UMB block 0xcc00-0xdfff
LOG: Alright: DOS kernel shutdown, booting a guest OS
LOG:   CS:IP=0000:7c00 SS:SP=7000:0100 AX=0000 BX=7c00 CX=0001 DX=0080
LOG:    1244012 ERROR BIOS:Disk 0 not active
LOG:    1245464 ERROR BIOS:INT15:Unknown call ax=4101
LOG: pixratio 1.200, dw true, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: pixratio 1.350, dw false, dh false
LOG: Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: pixratio 1.200, dw true, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG:   75466105 ERROR BIOS:INT15:Unknown call ax=2403
LOG:   75632099 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632113 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632127 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632141 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632155 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632169 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632183 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632197 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632211 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632225 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632239 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632253 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632267 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632281 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632295 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75632309 ERROR BIOS:INT15:Unknown call ax=D800
LOG:   75732082 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG:   78513625 ERROR BIOS:INT1A:Undefined call B0
LOG: pixratio 1.350, dw false, dh false
LOG: Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: pixratio 1.200, dw true, dh false
LOG: Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 720 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(720,417) match=(2320,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG:  259456864 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG:  269143085 ERROR BIOS:Disk 0 not active
LOG: INT13: Check Extensions Present for drive: 0x80
LOG:  282073551 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG:  290990481 ERROR CPU:Write 0 to rom at e00a0
LOG:  290990482 ERROR CPU:Write ffff to rom at e00a2
LOG:  290990503 ERROR CPU:Write ffff to rom at e00a2
LOG:  290990505 ERROR CPU:Write ffff to rom at e00a0
LOG:  290990521 ERROR CPU:Write 0 to rom at e08a0
LOG:  290990522 ERROR CPU:Write ffff to rom at e08a2
LOG:  290990543 ERROR CPU:Write ffff to rom at e08a2
LOG:  290990545 ERROR CPU:Write ffff to rom at e08a0
LOG:  290990662 ERROR CPU:Write 0 to rom at e10a0
LOG:  290990663 ERROR CPU:Write ffff to rom at e10a2
LOG:  290990684 ERROR CPU:Write ffff to rom at e10a2
LOG:  290990686 ERROR CPU:Write ffff to rom at e10a0
LOG:  290990702 ERROR CPU:Write 0 to rom at e18a0
LOG:  290990703 ERROR CPU:Write ffff to rom at e18a2
LOG:  290990724 ERROR CPU:Write ffff to rom at e18a2
LOG:  290990726 ERROR CPU:Write ffff to rom at e18a0
LOG:  290990843 ERROR CPU:Write 0 to rom at e20a0
LOG:  290990844 ERROR CPU:Write ffff to rom at e20a2
LOG:  290990865 ERROR CPU:Write ffff to rom at e20a2
LOG:  290990867 ERROR CPU:Write ffff to rom at e20a0
LOG:  290990883 ERROR CPU:Write 0 to rom at e28a0
LOG:  290990884 ERROR CPU:Write ffff to rom at e28a2
LOG:  290990905 ERROR CPU:Write ffff to rom at e28a2
LOG:  290990907 ERROR CPU:Write ffff to rom at e28a0
LOG:  290991024 ERROR CPU:Write 0 to rom at e30a0
LOG:  290991025 ERROR CPU:Write ffff to rom at e30a2
LOG:  290991046 ERROR CPU:Write ffff to rom at e30a2
LOG:  290991048 ERROR CPU:Write ffff to rom at e30a0
LOG:  290991064 ERROR CPU:Write 0 to rom at e38a0
LOG:  290991065 ERROR CPU:Write ffff to rom at e38a2
LOG:  290991086 ERROR CPU:Write ffff to rom at e38a2
LOG:  290991088 ERROR CPU:Write ffff to rom at e38a0
LOG:  290991205 ERROR CPU:Write 0 to rom at e40a0
LOG:  290991206 ERROR CPU:Write ffff to rom at e40a2
LOG:  290991227 ERROR CPU:Write ffff to rom at e40a2
LOG:  290991229 ERROR CPU:Write ffff to rom at e40a0
LOG:  290991245 ERROR CPU:Write 0 to rom at e48a0
LOG:  290991246 ERROR CPU:Write ffff to rom at e48a2
LOG:  290991267 ERROR CPU:Write ffff to rom at e48a2
LOG:  290991269 ERROR CPU:Write ffff to rom at e48a0
LOG:  290991386 ERROR CPU:Write 0 to rom at e50a0
LOG:  290991387 ERROR CPU:Write ffff to rom at e50a2
LOG:  290991408 ERROR CPU:Write ffff to rom at e50a2
LOG:  290991410 ERROR CPU:Write ffff to rom at e50a0
LOG:  290991426 ERROR CPU:Write 0 to rom at e58a0
LOG:  290991427 ERROR CPU:Write ffff to rom at e58a2
LOG:  290991448 ERROR CPU:Write ffff to rom at e58a2
LOG:  290991450 ERROR CPU:Write ffff to rom at e58a0
LOG:  290991567 ERROR CPU:Write 0 to rom at e60a0
LOG:  290991568 ERROR CPU:Write ffff to rom at e60a2
LOG:  290991589 ERROR CPU:Write ffff to rom at e60a2
LOG:  290991591 ERROR CPU:Write ffff to rom at e60a0
LOG:  290991607 ERROR CPU:Write 0 to rom at e68a0
LOG:  290991608 ERROR CPU:Write ffff to rom at e68a2
LOG:  290991629 ERROR CPU:Write ffff to rom at e68a2
LOG:  290991631 ERROR CPU:Write ffff to rom at e68a0
LOG:  290991748 ERROR CPU:Write 0 to rom at e70a0
LOG:  290991749 ERROR CPU:Write ffff to rom at e70a2
LOG:  290991770 ERROR CPU:Write ffff to rom at e70a2
LOG:  290991772 ERROR CPU:Write ffff to rom at e70a0
LOG:  290991788 ERROR CPU:Write 0 to rom at e78a0
LOG:  290991789 ERROR CPU:Write ffff to rom at e78a2
LOG:  290991810 ERROR CPU:Write ffff to rom at e78a2
LOG:  290991812 ERROR CPU:Write ffff to rom at e78a0
LOG:  290991929 ERROR CPU:Write 0 to rom at e80a0
LOG:  290991930 ERROR CPU:Write ffff to rom at e80a2
LOG:  290991951 ERROR CPU:Write ffff to rom at e80a2
LOG:  290991953 ERROR CPU:Write ffff to rom at e80a0
LOG:  290991969 ERROR CPU:Write 0 to rom at e88a0
LOG:  290991970 ERROR CPU:Write ffff to rom at e88a2
LOG:  290991991 ERROR CPU:Write ffff to rom at e88a2
LOG:  290991993 ERROR CPU:Write ffff to rom at e88a0
LOG:  290992110 ERROR CPU:Write 0 to rom at e90a0
LOG:  290992111 ERROR CPU:Write ffff to rom at e90a2
LOG:  290992132 ERROR CPU:Write ffff to rom at e90a2
LOG:  290992134 ERROR CPU:Write ffff to rom at e90a0
LOG:  290992150 ERROR CPU:Write 0 to rom at e98a0
LOG:  290992151 ERROR CPU:Write ffff to rom at e98a2
LOG:  290992172 ERROR CPU:Write ffff to rom at e98a2
LOG:  290992174 ERROR CPU:Write ffff to rom at e98a0
LOG:  290992291 ERROR CPU:Write 0 to rom at ea0a0
LOG:  290992292 ERROR CPU:Write ffff to rom at ea0a2
LOG:  290992313 ERROR CPU:Write ffff to rom at ea0a2
LOG:  290992315 ERROR CPU:Write ffff to rom at ea0a0
LOG:  290992331 ERROR CPU:Write 0 to rom at ea8a0
LOG:  290992332 ERROR CPU:Write ffff to rom at ea8a2
LOG:  290992353 ERROR CPU:Write ffff to rom at ea8a2
LOG:  290992355 ERROR CPU:Write ffff to rom at ea8a0
LOG:  290992472 ERROR CPU:Write 0 to rom at eb0a0
LOG:  290992473 ERROR CPU:Write ffff to rom at eb0a2
LOG:  290992494 ERROR CPU:Write ffff to rom at eb0a2
LOG:  290992496 ERROR CPU:Write ffff to rom at eb0a0
LOG:  290992512 ERROR CPU:Write 0 to rom at eb8a0
LOG:  290992513 ERROR CPU:Write ffff to rom at eb8a2
LOG:  290992534 ERROR CPU:Write ffff to rom at eb8a2
LOG:  290992536 ERROR CPU:Write ffff to rom at eb8a0
LOG:  290992653 ERROR CPU:Write 0 to rom at ec0a0
LOG:  290992654 ERROR CPU:Write ffff to rom at ec0a2
LOG:  290992675 ERROR CPU:Write ffff to rom at ec0a2
LOG:  290992677 ERROR CPU:Write ffff to rom at ec0a0
LOG:  290992693 ERROR CPU:Write 0 to rom at ec8a0
LOG:  290992694 ERROR CPU:Write ffff to rom at ec8a2
LOG:  290992715 ERROR CPU:Write ffff to rom at ec8a2
LOG:  290992717 ERROR CPU:Write ffff to rom at ec8a0
LOG:  290992834 ERROR CPU:Write 0 to rom at ed0a0
LOG:  290992835 ERROR CPU:Write ffff to rom at ed0a2
LOG:  290992856 ERROR CPU:Write ffff to rom at ed0a2
LOG:  290992858 ERROR CPU:Write ffff to rom at ed0a0
LOG:  290992874 ERROR CPU:Write 0 to rom at ed8a0
LOG:  290992875 ERROR CPU:Write ffff to rom at ed8a2
LOG:  290992896 ERROR CPU:Write ffff to rom at ed8a2
LOG:  290992898 ERROR CPU:Write ffff to rom at ed8a0
LOG:  290993015 ERROR CPU:Write 0 to rom at ee0a0
LOG:  290993016 ERROR CPU:Write ffff to rom at ee0a2
LOG:  290993037 ERROR CPU:Write ffff to rom at ee0a2
LOG:  290993039 ERROR CPU:Write ffff to rom at ee0a0
LOG:  290993055 ERROR CPU:Write 0 to rom at ee8a0
LOG:  290993056 ERROR CPU:Write ffff to rom at ee8a2
LOG:  290993077 ERROR CPU:Write ffff to rom at ee8a2
LOG:  290993079 ERROR CPU:Write ffff to rom at ee8a0
LOG:  290993196 ERROR CPU:Write 0 to rom at ef0a0
LOG:  290993197 ERROR CPU:Write ffff to rom at ef0a2
LOG:  290993218 ERROR CPU:Write ffff to rom at ef0a2
LOG:  290993220 ERROR CPU:Write ffff to rom at ef0a0
LOG:  290993236 ERROR CPU:Write 0 to rom at ef8a0
LOG:  290993237 ERROR CPU:Write ffff to rom at ef8a2
LOG:  290993258 ERROR CPU:Write ffff to rom at ef8a2
LOG:  290993260 ERROR CPU:Write ffff to rom at ef8a0
LOG: Plug & Play OS reports itself active
LOG: PNP OS changed I/O read port to 0x277 (from 0x20B)
LOG: PNP OS changed I/O read port to 0x37B (from 0x277)
LOG: PNP OS changed I/O read port to 0x33B (from 0x37B)
LOG: PNP OS changed I/O read port to 0x23B (from 0x33B)
LOG:  314239162 ERROR BIOS:INT1A:PCI BIOS: unknown function b10e (0 2b0 15a1)
LOG: VOODOO LFB now at ff000000
LOG: VOODOO LFB now at d0000000
LOG: APM BIOS: Connected to 32-bit protected mode interface
LOG: APM BIOS negotiated to v1.2
LOG: Unknown APM BIOS call AX=5312
LOG: enable APM for device    1
LOG: engage APM for device    1
LOG: enable APM for device    1
LOG: Unknown APM BIOS call AX=5311
LOG:  317567243 ERROR INT10:Unhandled VESA Function 15
LOG:  317658659 ERROR INT10:Unhandled VESA Function 10
LOG:  318148685 ERROR CPU:Illegal Unhandled Interrupt Called 20
LOG:  318148990 ERROR CPU:Illegal Unhandled Interrupt Called 20
LOG:  321623588 ERROR BIOS:INT15:Unknown call ax=F963
LOG: INT 15h mouse initialized to 3-byte protocol
LOG: INT 15h reporting mouse device ID 0x03
LOG: IDE ATA command 20 dh=0xa0 count=0x01 chs=00/00/01
LOG: FDC: Reset complete
LOG: FDC: Command len=1 0e 00 00 00 00 00 00 00 00 00
LOG: FDC: Response len=10 00 00 00 00 88 40 12 00 78 00
LOG:  373101700 ERROR MOUSE:Unhandled videomode 7F on reset
LOG: pixratio 1.000, dw false, dh false
LOG: Aspect ratio: 1024 x 768  xToY=1.333 yToX=0.750
LOG: menuScale=1
LOG: X11 main window is 640 x 417 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(640,417) match=(2280,250)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: font texture id=2 will make 128 x 256
LOG: X11 main window is 1024 x 785 maximized=0
LOG: XRandR CRTC 0: pos=(1920,0) size=(1712,963) outputs=1
LOG: Our window lies on this CRTC display (window pos=(1960,42) size=(1024,785) match=(2472,434)).
LOG:   Goes to output 0: name='XWAYLAND0' size_mm=(310 x 170)
LOG: Screen report: Method 'XRandR' (1712.000 x 963.000 pixels) at (1920.000 x 0.000) (310.000 x 170.000 mm) (12.205 x 6.693 in) (140.274 x 143.884 DPI)
LOG: Unknown APM BIOS call AX=5311


Here is the dosbox config in question
Code: Select all
[dosbox]
title=Win98SE
machine=svga_s3
pci vga=true
enable pci bus=true
memsize=256
vmem=8

[sdl]
autolock=true
#output=surface
#output=direct3d
output=opengl

[render]
#aspect=false
#scaler=normal4x

[cpu]
cycles=max
core = normal
cputype = pentium_mmx
enable cmpxchg8b
isapnpbios = true

[keyboard]
aux=true
allow output port reset=true
auxdevice=intellimouse

[pci]
#voodoo=opengl

[serial]
serial1=disabled
serial2=disabled
serial3=disabled
serial4=disabled

[parallel]
parallel1=disabled
parallel2=disabled
parallel3=disabled

[ide,primary]
enable=true
pnp=true
int13fakev86io=true

[ide,secondary]
enable=true
pnp=true
int13fakev86io=true

[fdc, primary]
enable=true
pnp=true
instant mode=true
mode=ps2
int13fakev86io=true

[autoexec]
imgmount c: ~/emu/dosbox/win98se.img -ide 1m
imgmount d: "~/emu/dosbox/SimCity3000-Windows.iso" -t iso -ide 2m
boot -l c:


Any idea? This is consistent, it is only able to boot to the desktop every second boot. The boot where it asks the question if I want to go to safe mode. Could this be a timing issue?
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

Re: DOSBox-X branch

Postby _Rob » 2019-9-09 @ 07:27

Also on shutdown of Win98SE, it just hangs on the shutdown splash screen and in the log I see a continuous stream of these errors:

LOG: 1367968862 ERROR CPU:Illegal Unhandled Interrupt Called 6
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-9-10 @ 07:42

Debugger command "SM" has been updated to accept segment:offset syntax.
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby TheGreatCodeholio » 2019-9-10 @ 07:43

_Rob wrote:Also on shutdown of Win98SE, it just hangs on the shutdown splash screen and in the log I see a continuous stream of these errors:

LOG: 1367968862 ERROR CPU:Illegal Unhandled Interrupt Called 6


Are you attempting to use dynamic core?

Dynamic core does not work with preemptive multitasking OSes like Windows 95/98.

Also try using core=normal, and a fixed cycle count or cycles=max.
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: DOSBox-X branch

Postby _Rob » 2019-9-10 @ 10:47

Hi TheGreatCodeHolio, Yes I am using core=normal and cycles=max. That is why I posted my config above. I tried this with both your Linux 64bit built and your Windows built (SDL1, 64bit).
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

Illegal Unhandled Interrupt Called 6

Postby _Rob » 2019-9-15 @ 11:32

I just updated to 0.82.22. I compiled it myself on 64bit fedora 30, as no RPM was available this time around.

The situation has changed a bit. Now when I start it the following happens.

On the first boot:
I get the win98se boot splash screen and then suddenly on the console I see a continuous stream of these errors:
LOG: 118743219 ERROR CPU:Illegal Unhandled Interrupt Called 6

And in the dosbox window I get this:
Windows protection error. You need to restart your computer.

On the second boot
I get the question if I want to boot into safe mode, and I instead select to boot normal. It now successfully boots to the desktop and I can start programs. But when I do a shutdown, I again get the same continuous stream of error in the log (illegal unhandled interrrupt called 6) and it hangs on the shutdown splash screen.

Then when I close dosbox and start it again, I get the same as on the first boot. So only if I get the prompt asking to boot into safe mode, is when it will work. So to me it seems like this may be some kind of timing issue where the boot takes slightly longer due to the prompt, which allows it to boot successfully.

Just to confirm again, I am running with core=normal and cycles=max. I posted my conf file a few posts back.
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

Re: Illegal Unhandled Interrupt Called 6

Postby TheGreatCodeholio » 2019-9-15 @ 16:17

_Rob wrote:I just updated to 0.82.22. I compiled it myself on 64bit fedora 30, as no RPM was available this time around.

The situation has changed a bit. Now when I start it the following happens.

On the first boot:
I get the win98se boot splash screen and then suddenly on the console I see a continuous stream of these errors:
LOG: 118743219 ERROR CPU:Illegal Unhandled Interrupt Called 6

And in the dosbox window I get this:
Windows protection error. You need to restart your computer.

On the second boot
I get the question if I want to boot into safe mode, and I instead select to boot normal. It now successfully boots to the desktop and I can start programs. But when I do a shutdown, I again get the same continuous stream of error in the log (illegal unhandled interrrupt called 6) and it hangs on the shutdown splash screen.

Then when I close dosbox and start it again, I get the same as on the first boot. So only if I get the prompt asking to boot into safe mode, is when it will work. So to me it seems like this may be some kind of timing issue where the boot takes slightly longer due to the prompt, which allows it to boot successfully.

Just to confirm again, I am running with core=normal and cycles=max. I posted my conf file a few posts back.


That's unusual, I've had no problems with Windows 98 apart from an occasional INT 6 crash on shutdown. Does SCANDISK show any disk corruption?
DOSBox-X project: more emulation better accuracy.
DOSLIB and DOSLIB2: Learn how to tinker and hack hardware and software from DOS.
User avatar
TheGreatCodeholio
Oldbie
 
Posts: 695
Joined: 2011-8-18 @ 20:15
Location: Seattle, WA

Re: Illegal Unhandled Interrupt Called 6

Postby _Rob » 2019-9-16 @ 07:00

TheGreatCodeholio wrote:
_Rob wrote:I just updated to 0.82.22. I compiled it myself on 64bit fedora 30, as no RPM was available this time around.

The situation has changed a bit. Now when I start it the following happens.

On the first boot:
I get the win98se boot splash screen and then suddenly on the console I see a continuous stream of these errors:
LOG: 118743219 ERROR CPU:Illegal Unhandled Interrupt Called 6

And in the dosbox window I get this:
Windows protection error. You need to restart your computer.

On the second boot
I get the question if I want to boot into safe mode, and I instead select to boot normal. It now successfully boots to the desktop and I can start programs. But when I do a shutdown, I again get the same continuous stream of error in the log (illegal unhandled interrrupt called 6) and it hangs on the shutdown splash screen.

Then when I close dosbox and start it again, I get the same as on the first boot. So only if I get the prompt asking to boot into safe mode, is when it will work. So to me it seems like this may be some kind of timing issue where the boot takes slightly longer due to the prompt, which allows it to boot successfully.

Just to confirm again, I am running with core=normal and cycles=max. I posted my conf file a few posts back.


That's unusual, I've had no problems with Windows 98 apart from an occasional INT 6 crash on shutdown. Does SCANDISK show any disk corruption?


Well, each time I get the prompt if I want to boot into safe mode, it also does a scandisk and never gives any errors.
Just as a test, when at the prompt, I selected to go to DOS and did a manual scandisk. it found no errors. I then rebooted and it again ran into the same problem as described before under "first boot".
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

Can's create drive from file

Postby _Rob » 2019-9-19 @ 20:16

dosbox-x 0.82.21
Trying to reinstall win98se to ensure the HDD image was not corrupt... The image file is 2GB and was working before.

I used the Win98SE fdisk utility to manually delete the old partition and rebooted. I then let the Win98SE setup create a new partition with support for LBA, it then required me to reboot. After the reboot Windows and DOS reported no drive present, and looking through the logs I found this is because dosbox is refusing to mount the image.

Basically dosbox complains that it "Can't create drive from file". Here is that the log shows:

Code: Select all
LOG: IDE: index 0 slave=0
LOG: VHD image detected: 512,63,64,1023
LOG: Using partition 0 on drive (type 0x0b); skipping 63 sectors
LOG: FAT: BPB says 0 sectors/track 0 heads 0 bytes/sector
LOG: Rejecting image, boot sector has weird values not consistent with FAT filesystem


So it seems there may be some problem with LBA support in dosbox? Or is this because the filesystem has not yet been created at this point?
The mount command is:
imgmount c win98se.img -ide 1m
_Rob
Newbie
 
Posts: 25
Joined: 2019-2-03 @ 10:46

PreviousNext

Return to DOSBox Patches

Who is online

Users browsing this forum: Google [Bot] and 1 guest