-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems when starting Windows 9x #5422
Comments
There was a build from about 1-2 days ago where my cleanup broke the normal core, which can cause issues like that. That was fixed yesterday. Please try the latest daily build. The Win95 and Win98 images I test with daily still work fine from the latest commit. Are you running with too high a cycle count? There are known timing bugs with faster CPUs and Windows 95/98. Especially Windows 95. |
I'm a little confused now. I'm not sure what daily builds are, but I'm familiar with nightly builds, which is also the only one among the two that I can find here. I used the nightly build called "Update VS project" (the very newest so far), that's what it's called according to https://github.com/joncampbell123/dosbox-x/actions/runs/12880627144, and I'm experiencing what I mentioned I experienced with this build. I have tried both 4.13 GHz, 3.8 GHz, 1.4 GHz, 450 MHz, 266 MHz and 70 MHz, I have tried both Pentium III, II, I, MMX and Pro, I have tried both dynamic, dynamic_x86 and normal, and I still experience the same problem with Windows 9x. I don't think the build from about 1-2 days ago that you mentioned is the reason why Windows 9x won't run, because that build from yesterday, the one called "Ooh, VGA cleanup that splits I/O up has a flaw. map() needs", according to https://github.com/joncampbell123/dosbox-x/actions/runs/12875525739 , could run Windows 9x, builds called "retab dos.cpp", "Wait, false alarm. Retab skewed the comments", "Fill out bios.h", "Begin adding PC-98 BIOS data area constants, now that Hackipedia.org" and "forgot a header file" were canceled anyway, so I don't know which of them wich was supposed to could run Windows 9x and not. |
Are you able to boot into "Safe mode"? If so, go into Settings, try removing the network card drivers. EDIT: I mean Windows 95 "Safe mode" within the emulator, not your host system! EDIT: Oh, now I see the error on my Linux system. |
Describe the bug
I've tried both Windows 95, 98 and ME, and I run into an obstacle for each of the operating systems, so I can't run Windows 9x. Something must have happened between "Ooh, VGA cleanup that splits I/O up has a flaw. map() needs", and "Update VS project", but don't know which of the nightly builds it started with, since they are not downloadable, and I can't test them out. the first mentioned nightly build is so far the last downloadable that could run Windows 9x. I have tested Windows XP (which is NT) by the way with the latest nightly build, and it works.
Windows 95
Windows 98
Windows ME
Steps to reproduce the behaviour
Just start any Windows 9x.
Expected behavior
I expect any version of any Windows 9x to be able to work properly. :)
What operating system(s) this bug have occurred on?
Windows 11 Pro 24H2
What version(s) of DOSBox-X have this bug?
Latest nightly build (as far as I know).
Used configuration
Output log
Additional information
No response
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines
The text was updated successfully, but these errors were encountered: