search

joncampbell123 / dosbox-x

DOSBox-X fork of the DOSBox project
GNU General Public License v2.0
2.81k stars 383 forks source link

Installing Win98 #4328

Open grstatdoc-gr opened 1 year ago

grstatdoc-gr commented 1 year ago

Question

How do I install win98 when I have the iso file in the DOSBox-X directory? I have created a hdd image file, but am having problems after that: IMGMOUNT D Win98.iso doesn't work (I get the "The image must be on a host, local or network drive. Must specify image file(s) to mount" error So, I'm stumped as to access the iso file to continue the process

Have you checked that no similar question(s) exist?

Code of Conduct & Contributing Guidelines

rderooy commented 1 year ago

The config -get ne2000 for you clearly shows ne2000=false meaning it being disabled. So Z:\SYSTEM\NE2000.COM not showing is expected.

I think it is showing "false" because the dosbox-x binary lacks either Ethernet or SLIRP support. As mentioned on the dosbox-x networking wiki page, for Windows the Visual Studio (VS) build lacks SLIRP support. So you would have to use the MinGW build instead.

grstatdoc-gr commented 1 year ago

I see that now... My next question is overcoming the inability to mount hdd.img under MinGW sdl1 (I recall that sdl2 is not recommended....)

grstatdoc-gr commented 1 year ago

Ok...I misunderstood the config -get command...it returns what is in the config file. But, I have ne2000=true in the config file

image

... but getting ne2000.com to show up in the z:\system directory is what I need to solve

image
grstatdoc-gr commented 1 year ago

I put a reference to the mingw low end in my win98 batch file, but I am still stumped by cannot create drive from file error:

image

(in addition to the ne2000.com file not being in the system directory)

rderooy commented 1 year ago

Yes the config -get output is influenced by your config file. But clearly the ne2000=true setting in your config file is being ignored. And it is likely being ignored because your dosbox-x binary lacks NE2000 or SLIRP support. Which is why it is not showing 'true'. So if you solve the reason for the setting being ignored you will solve both issues.

rderooy commented 1 year ago

Can anyone else check with the MinGW binary if NE2000 + SLIRP works on Windows? I don't have any Windows.

rderooy commented 1 year ago

For the "cannot create drive from file" error. Can you run the ver command, and show the output?

grstatdoc-gr commented 1 year ago

Well, I had hoped the running the MinGW build would solve that...but I have no real idea of finding a dosbox-x binary that has both ne2000 and slirp support. Without that, the hope of running TAS Baseball in DOSBox-x will have to be scuttled (since it can only run in a 32-bit environment)

grstatdoc-gr commented 1 year ago

Another trip to the config file, as ver reports?: DOSBox-X version 2023.05.01 (SDL1). Reported DOS version 7.10

rderooy commented 1 year ago

It is not a trip to the config file. The config file gets read on startup only. Meaning you are showing the values in memory.

I wanted to check if it was actually showing DOS 7.1 since the filesystem on the HDD is likely FAT32 which is only supported with DOS 7.1 or later. I suspect what you ran into is a bug in the MinGW build, possibly this one: https://github.com/joncampbell123/dosbox-x/issues/4355

grstatdoc-gr commented 1 year ago

Ok, thanks for the clarification. I read about that bug, and had the impression that there is a build that fixed the problem, but I haven't latched on to it.

On Sun, Jul 2, 2023, 14:03 Robert @.***> wrote:

It is not a trip to the config file. The config file gets read on startup only. Meaning you are showing the values in memory.

I wanted to check if it was actually showing DOS 7.1 since the filesystem on the HDD is likely FAT32 which is only supported with DOS 7.1 or later. I suspect what you ran into is a bug in the MinGW build, possibly this one:

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

— Reply to this email directly, view it on GitHub https://github.com/joncampbell123/dosbox-x/issues/4328#issuecomment-1616818069, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARDZRGKSH6CXQUWDCC6PF3LXOHO35ANCNFSM6AAAAAAZBBCOBI . You are receiving this because you authored the thread.Message ID: @.***>

grstatdoc-gr commented 1 year ago

So, is there a build I can download that fixes bug #2355? Also, is there a current download that includes ne2000.com, since the download I have never had that file?

grstatdoc-gr commented 1 year ago

I did find the ne2000.com file and added it to my z: directory (I had hoped to put it in the z:\system directory, but that will require a binary that contains that file....

Torinde commented 1 year ago

The 2355 is not a bug, but is about a dialog box from DOSbox-X (requesting confirmation when closing "are you sure you want to quit?") that can be made not to appear as described there.

rderooy commented 1 year ago

I installed Win10 in a virtual machine, and then the mingw sdl2 version of DOSBox-X 2023.05.01.

I used my existing win98 HDD image that I created on Linux.

I encountered the following issues.

I then took a step back and installed the mingw sdl2 version of DOSBox-X 2023.03.31. This had the following effects.

Regarding the NE2000 issues, it seems that the Windows MinGW build of version 2023.05.01 (as available from the installer package) was indeed build without NE2000 support.

grstatdoc-gr commented 1 year ago

I have found that the main version also does not have ne2000 support

rderooy commented 1 year ago

Not sure what you mean with "main" version. There is no version called as such. If you mean the VS build, then yes that is at least a known limitation as documented.

grstatdoc-gr commented 1 year ago

Yes, I am referring to the VS one (in contrast to the others appended with MinGW, SDL)

On Sat, Jul 8, 2023, 08:27 Robert @.***> wrote:

Not sure what you mean with "main" version. There is no version called as such. If you mean the VS build, then yes that is at least a known limitation as documented.

— Reply to this email directly, view it on GitHub https://github.com/joncampbell123/dosbox-x/issues/4328#issuecomment-1627379174, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARDZRGILQGTQWQCJ5J6JXMLXPF34ZANCNFSM6AAAAAAZBBCOBI . You are receiving this because you authored the thread.Message ID: @.***>

rderooy commented 1 year ago

There seems to be some confusion about SDL. To clarify, all dosbox versions use SDL. DOSBox-X in particular is available in either a SDL1 or SDL2 edition.

SDL2 is newer, and at least on Linux systems more commonly used. But some people still seem to prefer the SDL1 based version. This was originally because the SDL2 based version lacked some features, but I don't think that is the case any longer. And since SDL is amongst others responsible for input devices, using the newer SDL version can actually solve some issues.

grstatdoc-gr commented 1 year ago

I found the revised mingw low end assembly and downloaded it.... I'm still running into the cannot create drive from file error....

image

Wasn't it recommended to use MinGW_lowend_SDL1 in running Windows 98? Has it been tried with MinGW_lowend_SDL2? I'll give SDL2 a try and see what happens...

grstatdoc-gr commented 1 year ago

Looking at the state of things: Wondering if there will be a new version with NE2000 support (adding ne2000.com to drive Z didn't get it to work properly in Win98) ... or if there is a solution to the "cannot create drive from file" error under v2023.05.01, MinGW SDL1, 32-bit.

A side question: how do I get the title bar to show which type of DOSBox-X is running, whether it's the MinGW SDL1, 32-bit or one of the other types (like Windows SDL1, 32-bit)?

rderooy commented 1 year ago

I don't build the Windows version, so cannot answer that. But going to an older version fixed it for me. Perhaps also try the non-installer Windows builds that you can download from the github releases page.

As mentioned before, the NE2000.COM is not used by Win98 period. It is a DOS network driver, not a Windows network driver. All I wanted to know if you could see the file, as that at least indicates that NE2000 is actually enabled. Therefore adding it yourself will not change anything.

You can manually update the title using the title= option in the config file, but it is manual, so it will not automatically add VS or MinGW to it.

grstatdoc-gr commented 1 year ago

I will try the 2023.04.01 mingw low end release and see how that works. I had hoped that adding it would would have solved the problem of the driver not working right when I boot up Win98, but no such happenstance. I still don't know to solve the problem of ne2000 not working correctly once I boot up Win98 (the error message doesn't give sufficient clues of how to address it, and reinstalling it did not solve the problem.

grstatdoc-gr commented 9 months ago

I had paused pursuing this topic when baseball tournaments for me started, but am back to probing problems with the NE2000 adapter....the 2023.04.02 mingw low end release did not solve the problem of that driver not working right (I've downloaded the 2023.10.06 one to be current)... Well, I don't know how to get the Win98/Me windows in DOSBOX-X to send files to the host, as that is needed to run The Automated ScoreBook program (it runs OK in itself) properly. Has anyone else who has run 98/Me been able to send files to the host?