Installing Win98

[grstatdoc-gr]

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?

• [X] I have searched and didn't find any similar question.

Code of Conduct & Contributing Guidelines

• [X] I agree to follow the code of conduct and the contributing guidelines.

[rderooy]

As mentioned on the Win98 installation guide on the wiki, you specify the host path to the ISO file. If the file (on the host) is in C:\ISO you would do an imgmount d C:\ISO\Win98.iso to mount it.

[grstatdoc-gr]

Some progress...mounted the HDD drive and the ISO on D... but I've run into the SU0409 error, and the Windows 98 SE: Setup Detection Notice Message SU0409 #123 thread doesn't seem to help me get past that. Mike Dean

On Fri, Jun 9, 2023 at 3:05 PM Robert @.***> wrote:

As mentioned on the Win98 installation guide on the wiki, you specify the host path to the ISO file. If the file (on the host) is in C:\ISO you would do an imgmount d C:\ISO\Win98.iso to mount it.

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

[rderooy]

Are you following the dosbox-x wiki guide on installing Win98?

[grstatdoc-gr]

Doing my best.... Mike Dean

On Fri, Jun 9, 2023 at 11:24 PM Robert @.***> wrote:

Are you following the dosbox-x wiki guide on installing Win98?

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

[grstatdoc-gr]

I am "boxed" into a corner with the Win98 installation... Even though I downloaded a bootable Win98 iso, I've run into the "El Torito CD-ROM boot record not found" So, I've tried Method 2, and have run into the SU0409 error While I really don't want to have to turn off my antimalware to finish the install, I may have to do so...

[grstatdoc-gr]

I did a win98 iso that does have a boot image (overcame that hurdle), but here is the next one:

[rderooy]

TBH, I don't know what you are doing to cause these issues. I have done tons of Win9x installs for testing, and have not seen these issues. And nobody else has reported these issues either.

From your last screenshot, I would hazard to guess that you did not imgmount a disk before starting the install.

[grstatdoc-gr]

These are the steps I've taken:

This is before I typed the BOOT A: command

[grstatdoc-gr]

Okay, I've reached this point: Now start DOSBox-X as follows to continue the installation process:

dosbox-x -conf win98.conf

The wiki isn't clear to me (it may be to everybody else) if I'm to type setup here:

Another question about regedit: _Once the files are copied, start REGEDIT and navigate to HKEY_LOCALMACHINE\Software\Microsoft\Windows\CurrentVersion\Setup and change SourcePath= to the location where you copied the files. e.g., SourcePath=C:\WIN98 Is it safe to add the SourcePath key as it doesn't exit in my Registry.

I haven't found this in the wiki (not sure where this is), but how do I get back to Z: from the guest machine in DOSBox-X?

These are the steps I've distilled for myself:

1. Open Command Prompt
2. Run dosbox-x -conf win98.conf
3. From DOSBox-X window: IMGMAKE hdd.img -t hd -size 16384 (I think I can skip this step) run IMGMOUNT C hdd.img (I think I can skip this step, too) IMGMOUNT D C:\dosroot\Win98.iso IMGMOUNT A -bootcd D BOOT A:

I don't usually ask for gentleness here, but since I'm fighting mental blocks in following the steps, some is welcome.

Wondering if there is a way of pasting commands in the DOSBox-X window...

[rderooy]

You cannot just skip a step. That step you are skipping is the cause of your problems. As explained on the wiki page you MUST imgmount a C: drive. You cannot use mount for this instead.

[grstatdoc-gr]

However, if I get the message that the drive is already mounted, when I rerun these steps...I don't have to recreate the drive and remount a drive that is already mounted, do I????? Mike Dean

On Mon, Jun 19, 2023 at 8:35 AM Robert @.***> wrote:

Yyou cannot just skip a step. That step you are skipping is the cause of your problems. As explained on the wiki page you MUST imgmount a C: drive. You cannot use mount for this instead.

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

[rderooy]

You should not do the mount c c:\dosroot first. Or before you issue the boot command, you must remove it with something like mount c -u and then imgmount the harddisk image file.

[grstatdoc-gr]

dosroot is where I will do most of my operations (since DOSBOX-X does not recommend mounting the entire C drive, and the programs I intend on running are stored there) But finally, I got Win98 to install. Thanks for your help. I guess the last thing I need to ask is how to start DOSBox-X in Win98 without having to open the command prompt to do it every time.

[grstatdoc-gr]

Not OK for me... Mental block: I guess I need to copy the win98 folder to the hdd.img, but am not sure how to do it with xcopy.

[grstatdoc-gr]

Progress, I think,,,, Still having problems getting the boot folder onto the hdd.img

[rderooy]

No. you are still doing the mount command, which causes the following imgmount command to fail.

[grstatdoc-gr]

I follow (now that I had commented out that mount command). Thanks. It took a while for me to understand that Z: in DOSBox-X is the C:\DOSBox-X folder (as I was reading the steps, I had the belief that I had to put the needed files somewhere else to get it to work)

[grstatdoc-gr]

Finally -- thanks, Robert, for putting up with my stumbles and missteps -- I am running Windows 98 in DOSBox-X! But now, I could use a road map to:

1. Install the .net versions suggested.
2. Resize the Win98 screen after starting it so that it wouldn't distort the text
3. Copy file into the Win98 C:\ folder, as I'm not seeing how to do that once I have Win98 running.

thanks!

[grstatdoc-gr]

Not sure if I ought to request that this question be closed and start a new one in Windows ME.... But, in a few words, I have installed successfully WinMe in my Windows 11 DOSBox-X, added the network configuration info to winme.conf. But from the WinMe end, I am not sure if I can get it to see the NE200 as a network card, or if I'm trying to do something that is not possible (my reading the networking section in the wiki has, unfortunately, left my head spinning, and WinMe is expecting a NIC card, which isn't feasible(?) in a guest system) I think this is the last step I need to solve to get TAS Baseball to run optimally (I can run the program in WinMe and Win98 and print reports, but is the best way to get the reports off the guest system to use the copy command from the command prompt? ) Thanks.

[rderooy]

It is possible to get NE2000 networking working in WinME. But the emulated NE2000 card will not get autodetected, as it does not implement PnP extensions. As such you must manually add it as documented on the wiki. https://dosbox-x.com/wiki/Guide%3AInstalling-Windows-ME#_enabling_networking

But for this to work, the NE2000 emulation must be enabled in your config AND working on your host, which depends on the type of backend you chose (PCAP or SLIRP). In particular PCAP, while more capable, can be difficult or even impossible to setup in some environments.

Once again, this is a pretty advanced topic.

Also as an FYI, using WinME will not make any difference compared to Win98 as to the supported SMB version. It will still be limited to SMBv1.

[grstatdoc-gr]

Windows ME does not seem to like the IRQ = 10 and I/O range = 0300-031F

I am using SLIRP on the backend

[grstatdoc-gr]

Somewhat of an annoyance, following the first error:

[rderooy]

There is a reason the WinME wiki page says:

In general Windows ME has received less testing with DOSBox-X, and also has more compatibility issues with programs designed for Windows 95 and 98. As such, unless you have a specific requirement for Windows ME, the DOSBox-X team recommends to use Windows 98SE instead.

For the IRQ/IO resources it is critical that the exact same resources are defined in the dosbox-x config file AND in Device Manager in WinME.

[grstatdoc-gr]

Well, it was a try on Windows 98... Mike Dean

On Thu, Jun 29, 2023 at 10:36 AM Robert @.***> wrote:

There is a reason the WinME wiki page says:

In general Windows ME has received less testing with DOSBox-X, and also has more compatibility issues with programs designed for Windows 95 and 98. As such, unless you have a specific requirement for Windows ME, the DOSBox-X team recommends to use Windows 98SE instead.

For the IRQ/IO resources it is critical that the exact same resources are defined in the dosbox-x config file AND in Device Manager in WinME.

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

[grstatdoc-gr]

I had supposed that the ne2000.sys driver was already in the Win98SE iso, but it looks like I will have to add it, since my Win98 can't find it. Mike Dean

On Thu, Jun 29, 2023 at 11:04 AM Mike Dean @.***> wrote:

Well, it was a try on Windows 98... Mike Dean

On Thu, Jun 29, 2023 at 10:36 AM Robert @.***> wrote:

There is a reason the WinME wiki page says:

In general Windows ME has received less testing with DOSBox-X, and also has more compatibility issues with programs designed for Windows 95 and 98. As such, unless you have a specific requirement for Windows ME, the DOSBox-X team recommends to use Windows 98SE instead.

For the IRQ/IO resources it is critical that the exact same resources are defined in the dosbox-x config file AND in Device Manager in WinME.

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

[grstatdoc-gr]

Solved the driver problem, sort of... Win98 reports that NE 2000 Compatible "is either not present, not working properly, or does not have all the drivers installed (Code 10)" The current driver provider is Microsoft, and the date is 4-23-1999, which is the best driver for the system. The resources indicate IRQ of 10 and I/O range of 0300-031F.

Is there a setting in the config file that also addresses the Standard IDE/ESDI Hard Disk Controller or, since it is a guest machine off a virtual hard drive, can be ignored? Thanks.

Mike Dean

On Thu, Jun 29, 2023 at 11:55 AM Mike Dean @.***> wrote:

I had supposed that the ne2000.sys driver was already in the Win98SE iso, but it looks like I will have to add it, since my Win98 can't find it. Mike Dean

On Thu, Jun 29, 2023 at 11:04 AM Mike Dean @.***> wrote:

Well, it was a try on Windows 98... Mike Dean

On Thu, Jun 29, 2023 at 10:36 AM Robert @.***> wrote:

There is a reason the WinME wiki page says:

In general Windows ME has received less testing with DOSBox-X, and also has more compatibility issues with programs designed for Windows 95 and 98. As such, unless you have a specific requirement for Windows ME, the DOSBox-X team recommends to use Windows 98SE instead.

For the IRQ/IO resources it is critical that the exact same resources are defined in the dosbox-x config file AND in Device Manager in WinME.

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

[rderooy]

The NE2000 driver is included with Win95, 98 and ME. There are no third party network drivers to install. The issue could be either with the host configuration, dosbox-x config file or win9x configuration.

[grstatdoc-gr]

Ok.... Checking the configuration for the NE 2000 card in Win 98: IRQ = 10; I/O range = 0300-031F

In the win98.conf file: ne2000 = true; nicirq = 10; nicbase = 300

(I figure the dosbox-x.conf file is not used when launching DOSBOX-X in win98 mode. I'm hoping I don't have to delete everything and start from scratch, seeing that I installed win98 first and later added the ne2000 info ... Mike Dean

On Thu, Jun 29, 2023 at 1:57 PM Robert @.***> wrote:

The NE2000 driver is included with Win95, 98 and ME. There are no third party network drivers to install. The issue could be either with the host configuration, dosbox-x config file or win9x configuration.

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

[grstatdoc-gr]

I'm not sure if a properly configured NE2000 adapter is not supposed to show up in Device Manager, but after setting it up with the IRQ of 10 and I/O range of 300-31F, it doesn't show.... I would expect the driver to be in the Win98/drivers folder, but I haven't found it...

Under Hard Disk Controllers, I have one with: IRQ=15, I/O range=0170-0177 and 0376-0377 and another one that was installed (when I got the NE200 going) with: IRQ=14; I/O range=01F0-01F7 and 03F6-03F7 It's this latter one that "is either not present, not working properly or does not have all the drivers installed (Code 10)" Mike Dean

On Thu, Jun 29, 2023 at 8:33 PM Mike Dean @.***> wrote:

Ok.... Checking the configuration for the NE 2000 card in Win 98: IRQ = 10; I/O range = 0300-031F

In the win98.conf file: ne2000 = true; nicirq = 10; nicbase = 300

(I figure the dosbox-x.conf file is not used when launching DOSBOX-X in win98 mode. I'm hoping I don't have to delete everything and start from scratch, seeing that I installed win98 first and later added the ne2000 info ... Mike Dean

On Thu, Jun 29, 2023 at 1:57 PM Robert @.***> wrote:

The NE2000 driver is included with Win95, 98 and ME. There are no third party network drivers to install. The issue could be either with the host configuration, dosbox-x config file or win9x configuration.

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

[grstatdoc-gr]

So, I can safely rule out the lack of a current driver and IRQ-I/O settings, leaving me somewhat stymied Mike Dean

On Thu, Jun 29, 2023 at 9:49 PM Mike Dean @.***> wrote:

I'm not sure if a properly configured NE2000 adapter is not supposed to show up in Device Manager, but after setting it up with the IRQ of 10 and I/O range of 300-31F, it doesn't show.... I would expect the driver to be in the Win98/drivers folder, but I haven't found it...

Under Hard Disk Controllers, I have one with: IRQ=15, I/O range=0170-0177 and 0376-0377 and another one that was installed (when I got the NE200 going) with: IRQ=14; I/O range=01F0-01F7 and 03F6-03F7 It's this latter one that "is either not present, not working properly or does not have all the drivers installed (Code 10)" Mike Dean

On Thu, Jun 29, 2023 at 8:33 PM Mike Dean @.***> wrote:

Ok.... Checking the configuration for the NE 2000 card in Win 98: IRQ = 10; I/O range = 0300-031F

In the win98.conf file: ne2000 = true; nicirq = 10; nicbase = 300

(I figure the dosbox-x.conf file is not used when launching DOSBOX-X in win98 mode. I'm hoping I don't have to delete everything and start from scratch, seeing that I installed win98 first and later added the ne2000 info ... Mike Dean

On Thu, Jun 29, 2023 at 1:57 PM Robert @.***> wrote:

The NE2000 driver is included with Win95, 98 and ME. There are no third party network drivers to install. The issue could be either with the host configuration, dosbox-x config file or win9x configuration.

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

[rderooy]

This is using the SLIRP backend on DOSBox-X SDL2 2023.05.01 on Linux.

NE2000 Settings in the associated dosbox-x config are:

[ne2000]
ne2000=true
nicirq=10
macaddr=AC:DE:48:88:99:AD
backend=slirp

[etnernet, pcap]
enable=false

[ethernet, slirp]
enable=true

[rderooy]

Also, can you try to start DOSBox-X, but before you issue the boot command, check if Z:\SYSTEM\NE2000.COM exists? You don't need to load it (it is a DOS driver, not a Windows driver, and anything you load before issuing the boot command will be cleared anyway). I just want to know if it exists. If it does not, than your DOSBox-X binary may have been compiled without NE2000 emulation support.

[grstatdoc-gr]

Hmmmmm... I get a "Bad command or file name" when I look for the file And, the only item I have in the drivez folder is README.TXT So, if my DOSBox-X binary was compiled w/o NE2000 emulation support, how do I correct this?

In my win98.conf file: [ne2000] ne2000 = true

nicbase = 300

nicirq = 10 macaddr = AC:DE:48:88:99:AA backend = slirp

[ethernet, pcap] enable=false

realnic = list

timeout = default

[ethernet, slirp] enable=true

ipv4_network = 10.0.2.0

ipv4_netmask = 255.255.255.0

ipv4_host = 10.0.2.2

ipv4_nameserver = 10.0.2.3

ipv4_dhcp_start = 10.0.2.15

is it safe to uncomment the lines I have commented out? Thanks! this has been quite helpful

[grstatdoc-gr]

Looked in the wrong place for that file...

but no, that file is not there, so I need to correct this.

[rderooy]

You will only see the Z:\SYSTEM\NE2000.COM binary if...

• the dosbox-x binary is compiled with NE2000 & SLIRP support
• you started dosbox-x with the NE2000 emulation options enabled in the corresponding dosbox-x config file.

If both of these are not true, the NE2000.COM will not be there.

Since you are on Windows, are you using the VS (Visual Studio) or MinGW compiled binary? I don't use Windows myself, but I think NE2000 and SLIRP may only work with one of the two.

[grstatdoc-gr]

OK, the next task is finding one of those builds...or is it already included in the dosbox-x-winXP-2023.05.01-setup.exe file?

[grstatdoc-gr]

I found it under releases...so got that to work(?)

[grstatdoc-gr]

However, I have found that while I was successful in IMGMOUNT C hdd.img under the previous dosbox setup, with the newer MinGW setup, I get the "unable to create drive from file" error. (I would have expected the imgmount command to work in either case...)

[grstatdoc-gr]

I seem to have enough space on my hard drive, but in remaking the hdd.img file, I am getting this error:

[grstatdoc-gr]

Well, I started over from scratch and tried the MinGW option, but couldn't recreate the hdd.img file. I'll start over again and try the VS one.

[grstatdoc-gr]

Guess I can conclude that I can created the 16GB hdd in the VS option, but not the MinGW one in Windows 11

[grstatdoc-gr]

Struggling to remember that I have to run the DOSBox-X with the Win98.conf file before trying to create large hdd files!

[grstatdoc-gr]

So, I got the NE2000 Compatible to install, IRQ=10, I/O range=300-31F in both the config file and the Win98 OS, backend=slirp in the config file, and still can't pinpoint why the NE2000 Compatible isn't working correctly (Code 10)

[rderooy]

Do you at least see the Z:\SYSTEM\NE2000.COM file before you issue the boot command? If you don't, it will never work.

Also, you did not need to re-create your HDD image file. All you needed to do was to run a device discovery in Win98 for it to detect the NE2000 adapter.

[grstatdoc-gr]

This is the contents of z:\system (I commented out the boot command in the win98,config file):

[grstatdoc-gr]

I am finding that when I run the mingw_lowend_sdl1 version, I get the "cannot create drive from file" error when I run the imgmount c hdd.img command. The ne2000.com file isn't in the z:\system directory, either

[grstatdoc-gr]

so now things reduce to "what can I do to get the ne2000.com file in the z:system directory", since uninstalling and reinstalling DOSBox-x didn't work for me?

[rderooy]

Here is what I get:

Also in the DOSBox-X log output, I get the following messages to indicate Ethernet and SIRP are enabled.

LOG: ETHERNET: NE2000 Ethernet emulation backend selected: slirp
LOG: SLIRP: Slirp version: 4.7.0
LOG: SLIRP: Successfully initialized
LOG: NE2000: Base=0x300 irq=10

[grstatdoc-gr]

I'll give that a look shortly

On Sun, Jul 2, 2023, 11:47 Robert @.***> wrote:

Here is what I get: [image: image] https://user-images.githubusercontent.com/17701098/250392208-52150e70-9462-4e87-a837-f43fc302721a.png

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

[grstatdoc-gr]

commands done....still doesn't want to show up:

not sure at all how to find/generate the log output for the two get commands ... I do have a messages file generated, but the get files output wasn't in there.