windows 98 se dxdiag

[rokko34]

Describe the bug Ret from illegal descriptor type 0. I try dinamyc_x86 and normal core no difference.

To Reproduce Steps to reproduce the behavior:

1. Boot hdd image with windows 98.
2. Click on start menu and run... type dxdiag then click exit
3. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Environment (please complete the following information):

• Operating system windows 10 64-bit
• DOSBox-X release version 0.83.12
• Used configuration, e.g. dosbox-x.conf

dosbox-x.txt

[rokko34]

The "kilépés" button is the exit button in hungarian language. kilépés=exit in hungarian. One more thing it's Windows 98 SE.

[Diatonator]

Got the same stuff. On the same stuff, except mine OS is RU edition.

[win98se]

Same issue on 0.83.16, guest OS is Windows Me (both DirectX 7.1a and 9.0c has this problem).

[ruthan]

Its still crashing whole machine.. this utility is something which everyone will try.

Also CPU speed is wrong on all my machines its reporting 66MHz, Pentium MMX or Pentium II at 66 MHz make no sense.

[Wengier]

I could reproduce this problem. Please check out the updated DOSBox-X Windows build, which hopefully addresses this issue:

• dosbox-x-update.zip

[ruthan]

With this build its ok, no crash. Im not sure how about these build, for everything there are at least 4 builds, im using VS and SDL2 usually, so build should be default. Other thing about which im not sure, there are more assets - font files and some *.bmp, which are not part of package which i downloaded as normal build.

If it is just code change and it will work with every version and its not depend on these assets, its fixed.

[Wengier]

@ruthan The font files, bmp etc are accessory files to make DOSBox-X work better. For example with the TTF font files you can use a different TTF font for the screen text rather than the default one. Theoretically these accessory files should be included in every build, but users are generally advised to use the Windows installer so that these files are automatically installed. These files have nothing to do with this particular issue though.

[win98se]

Please check out the updated DOSBox-X Windows build, which hopefully addresses this issue:

• dosbox-x-update.zip

On this build, running dxdiag causes the window to turn totally black and can't be restored to normal anymore, not even by pressing Ctrl+Alt+Del twice and restarting the VM, unless reopening the whole program.

[Wengier]

So I am hearing different results from different users. Perhaps the versions of guest Windows systems you use are different?

[win98se]

So I am hearing different results from different users. Perhaps the versions of guest Windows systems you use are different?

Same results with Windows 95. My first scenario is Windows Me.

---

Below are my configurations for Windows Me and Windows 95 respectively -

[sdl]
autolock=true
showdetails=true

[dosbox]
title=Windows Me
fastbioslogo=true
startbanner=false
memsize=512

[video]
vmemsize=8
vesa modelist width limit=0
vesa modelist height limit=0

[dos]
ver=8.0
hard drive data rate limit=0

[cpu]
cputype=pentium_mmx
core=dynamic_x86
cycles=max

[voodoo]
glide=true

[sblaster]
sbtype=sb16vibra

[fdc, primary]
int13fakev86io=false

[ide, primary]
int13fakeio=true
int13fakev86io=false

[ide, secondary]
int13fakeio=true
int13fakev86io=false
cd-rom insertion delay=4000

[render]
aspect=true
scaler=none

[autoexec]
@imgmount c winme.img
@cls
@boot c:

[sdl]
autolock=true
showdetails=true

[dosbox]
title=Windows 95
fastbioslogo=true
startbanner=false
memsize=480

[video]
vmemsize=8
vesa modelist width limit=0
vesa modelist height limit=0

[dos]
ver=7.1
hard drive data rate limit=0

[cpu]
cputype=pentium_mmx
core=dynamic_x86
cycles=max

[voodoo]
glide=true

[sblaster]
sbtype=sb16vibra

[fdc, primary]
int13fakev86io=true

[ide, primary]
int13fakeio=true
int13fakev86io=true

[ide, secondary]
int13fakeio=true
int13fakev86io=true
cd-rom insertion delay=4000

[render]
aspect=true
scaler=none

[autoexec]
@imgmount c win95.img
@cls
@boot c:

[Wengier]

@win98se I tried your config file for Windows 98 SE, and it worked fine (no crash). For Windows 95, it requires a different version of DirectX rather than DirectX 9.0c as supported by Windows 98 SE. Running dxdiag from DirectX 8.0a did result a "illegal operation" message box from Windows 95, but I can close it peacefully and continue running Windows 95. For the next time I run dxdiag it asks me whether to bypass the DirectDraw part, and if I select "Yes" everything appears to run just fine.

[win98se]

On this build, running dxdiag causes the window to turn totally black and can't be restored to normal anymore, not even by pressing Ctrl+Alt+Del twice and restarting the VM, unless reopening the whole program.

I notice that the same bug also occurs on SDL1 VS builds of 0.83.16 and 0.83.20. Other versions (including any MinGW builds) are not tested here; SDL2 VS builds of 0.83.16 and 0.83.20 works fine though (but with the crash bug still exist for these two versions).

So the bug is unlikely caused by https://github.com/joncampbell123/dosbox-x/commit/e601a949fd918a727ed8b89d76a6bd38bc8c386d.

I tried your config file for Windows 98 SE, and it worked fine (no crash). For Windows 95, it requires a different version of DirectX rather than DirectX 9.0c as supported by Windows 98 SE.

Also, it's not exactly a crash, it's just the window turning totally black. I know there is no DirectX 9 for Windows 95, and if not mistaken, it ~should be DirectX 7.1 on both Windows 95 and Windows Me~ is DirectX 7.0a on Windows 95, and DirectX 7.1a on Windows Me in my case.

I probably need a SDL2 build to test with the (whether fixed or not) bug.

[ruthan]

I tested, Win98 SE and VS+SDL2 - now ok.

[win98se]

I tested, Win98 SE and VS+SDL2 - now ok.

MinGW SDL2 build from https://github.com/joncampbell123/dosbox-x/actions/runs/1606250236 also works fine and with the bug resolved.