Win95/98 can coexist with previous MS-DOS versions like 6.22 perfectly without disturbing each other's settings. But you have to be careful since the names of the boot/system files are constantly changing depending on what OS (Win9x or DOS) is active. When you boot to Win9x the boot/system files of MS-DOS are renamed to xxx.dos. So e.g. autoexec.bat and config.sys are renamed to autoexec.dos and config.dos. Contrary when you boot into MS-DOS the system/boot files of Win9x are renamed to xxx.w40. So e.g. autoexec.bat and config.sys of Win9x are renamed to autoexec.w40 and config.w40.
So you have to be careful when you edit autoexec.bat/config.sys since depending on what OS started last these files can belong to either Win9x or MS-DOS.
If you want to edit the MS-DOS version of autoexec.bat/config.sys from Win9x (when Win9x is active) you have to edit autoexec.dos and config.dos. The next time when you boot to MS-DOS these files become to autoexec.bat and config.sys.

Falcosoft wrote:

Win95/98 can coexist with previous MS-DOS versions like 6.22 perfectly. But you have to be careful since the names of the boot/system files are constantly changing depending on what OS (Win9x or DOS) is active. When you boot to Win9x the boot/system files of MS-DOS are renamed to xxx.dos. So e.g. autoexec.bat and config.sys are renamed to autoexec.dos and config.dos. Contrary when you boot into MS-DOS the system/boot files of Win9x are renamed to xxx.w40. So e.g. autoexec.bat and config.sys of Win9x are renamed to autoexec.w40 and config.w40.
So you have to be careful when you edit autoexec.bat/config.sys since depending on what OS started last these files can belong to either Win9x or MS-DOS...

Shit... ok that makes perfect sense.

How about this for a solution then: I never touch the contents of either of the files but when I want DOS, I simply use a 6.22 boot diskette with my customized autoexec and config files on it. Then once I get my C prompt, all the native DOS files on the hard drive will work as if I booted from the hard drive? Does this follow?

I don't think it would be easier. The original Win9x/MS-DOS combo is not difficult at all, if you know the rules. The most important thing is:

If you want to edit the MS-DOS version of autoexec.bat/config.sys from Win9x (when Win9x is active) you have to edit autoexec.dos and config.dos. The next time when you boot to MS-DOS these files become to autoexec.bat and config.sys.

That's all.

Falcosoft wrote:

I don't think it would be easier. The original Win9x/MS-DOS combo is not difficult at all, if you know the rules. The most important thing is:

If you want to edit the MS-DOS version of autoexec.bat/config.sys from Win9x (when Win9x is active) you have to edit autoexec.dos and config.dos. The next time when you boot to MS-DOS these files become to autoexec.bat and config.sys.

That's all.

I'm sure it is that simple in principle but I have formatted this machine 12 times (and counting). I can be dumb at times but not this dumb. This computer has exhibited the most unreal degree of selectivity I have ever seen in my life. There are probably 30 or so steps I have gone through in slightly different orders and if I get even 1 of them wrong, the whole install is garbage and I have to start over. Just now for example, I tried to F4 to DOS as soon as Win95 finished installing, instead of first installing my video and LAN drivers, and it crashed at DMI pool data. I mean what kind of F'd up OS breaks itself unless you install precisely certain drivers in the correct order before trying to use DOS? Not to mention, the thing will not shut down properly (though this doesn't seem to hurt anything) and if any software install tries to restart windows it also crashes (also benign). Basically the whole thing is a big pile of crap that is supported by toothpicks.

Could be me... just saying, I aint THAT dumb. Since I've only ever gotten all my device drivers installed whilst being able to use DOS in a dual boot, once I get it back to that point, I will never touch it again. I will use a boot disk to get into DOS and only copy games to my D drive to run under windows.

I remember thinking that 98 was much more stable than 95 and I'm starting to relive that right now.

Wait... I think 'verifying dmi pool data...' is at the POST stage. This stage is even before your BIOS tries to load the OS.
Thus it can be that your problem is not specifically OS related, but some kind of BIOS setting/HW conflict.
The Win95 version of MSDOS.SYS is an editable file. You can set options there e.g. you can enable a boot menu. Instead of pressing F4 blindly you should enable it so you can see exactly at what stage the boot process fails.

in MSDOS.SYS you should set:

[Options]
BootMulti=1
BootGUI=1
BootMenu=1
BootMenuDelay=10
...

About verifying dmi pool data problem:
https://www.tek-tips.com/viewthread.cfm?qid=138098

Ask old hardware and driver/configuration questions in Marvin. This forum is for DOS games on modern systems. Marvin, the Paranoid Android

I support Falcosoft's recommendation.
I suspect that there is an underlying hardware issue with your PC, rather than an OS problem.

• I would start out by loading your BIOS (Setup) Defaults and then see what happens.
• If that doesn't solve the problem, make sure that the BIOS has properly detected your hard drive - cylinders, heads, sectors, etc.
• Is your CMOS battery still OK? Does it still properly keep the date & time?
• Re-seat your memory and other cards (graphics, sound, etc.) in your system.
• Check your cables (to your floppy, CD-ROM, hard drive) and make sure they are properly connected on both ends.
• Unplug any sound cards or other devices (like a CD-ROM drive) and then connect them one by one again.

PS: There is no need (more specifically, no benefit) to run DOS 6.22 together with Windows 95/98.
Windows 9x comes with DOS as well (DOS 7.x).
By configuring a Start up menu, you can either then boot straight into DOS 7.x or into Windows (with multiple configurations) - refer How to create a boot (start up) menu under Windows 9x/ME

Moved.

jesolo wrote:

I support Falcosoft's recommendation. I suspect that there is an underlying hardware issue with your PC, rather than an OS probl […]
Show full quote

I support Falcosoft's recommendation.
I suspect that there is an underlying hardware issue with your PC, rather than an OS problem.

• I would start out by loading your BIOS (Setup) Defaults and then see what happens.
• If that doesn't solve the problem, make sure that the BIOS has properly detected your hard drive - cylinders, heads, sectors, etc.
• Is your CMOS battery still OK? Does it still properly keep the date & time?
• Re-seat your memory and other cards (graphics, sound, etc.) in your system.
• Check your cables (to your floppy, CD-ROM, hard drive) and make sure they are properly connected on both ends.
• Unplug any sound cards or other devices (like a CD-ROM drive) and then connect them one by one again.

PS: There is no need (more specifically, no benefit) to run DOS 6.22 together with Windows 95/98.
Windows 9x comes with DOS as well (DOS 7.x).
By configuring a Start up menu, you can either then boot straight into DOS 7.x or into Windows (with multiple configurations) - refer How to create a boot (start up) menu under Windows 9x/ME

As you said, the idea of a hardware issue was foremost on my mind as well and I did examine every card and ever detail several times. I found a couple of... not really problems but improvements in terms of cleaning contacts and changing slot orders as well as jumper configurations for IRQs and such but after I finished with that, so long as I did everything in the correct order, i could get pretty far with the machine. In fact I have my sequence memorized and it results in a pretty stable system if you discount the problems switching between windows and DOS:

1) Format C
2) Install DOS 6.22
3) Install SBBASIC sound drivers in DOS
4) Install Windows 95
5) Update ATI drivers
6) Add NIC drivers
7) Add sound drivers in Windows
8) Install service pack 1
9) Install directx 7
10) Enable USB controller in BIOS
11) Install USB drivers
12) Plug in USB stick to get mass storage device drivers
13) Try to boot to DOS and back to windows, get DMI Pool Data hang, scrap entire install and start from 1)

Last night I stopped at 12 and things are working well. But I haven't dared to run dos natively. I'm using a boot floppy. I would rather not use a boot floppy of course but I just don't want to format the machine for a 13th time lol. I am fully convinced by this point that there is some sort of conflict in whatever manager controls which operating system boots. As stated above, there's some file shuffling that goes on and whether my fault or not, it's breaking when it has to do that shuffle. Sometimes it doesn't break as long as I don't change the contents of the startup files but sometimes it breaks without changing anything. It's temperamental for reasons unknown to me.

BTW sorry for posting in the wrong forum. Thanks for moving it.

Why not just skip installing DOS 6.22 and just use DOS 7.x (that comes with Windows 95)?
Create a start up (boot) menu configuration as per my other thread and this should then hopefully resolve your problems.

In the beginning days of Windows 95, I also used to have separate instances of DOS 6.22 and Windows 95 BUT, I ran them on two separate partitions using OS/2 Warp 3's Boot Manager.
Later on, I realised there was no benefit of having both DOS 6.22 and Windows 95/98 on the same system, since DOS 7.x works just as well (so long as you don't use any low level disk utilities that are meant for earlier DOS versions/partitions).

As a matter of interest, what is your hardware specs and what version of Windows 95 are you running? Windows 95 retail edition?

I think it's the A version but the disk says "with USB support" which is a lie because it has none 🤣. The splash screen also says with internet explorer so maybe that kind narrows it down? It also has Microsoft PLUS. All the versions confuse me.

I always thought 6.22 was the last bonafide DOS before they started reshaping it into a more Windows oriented platform, deprecating features that existed in earlier versions, as you sort of eluded to. In practical terms that may mean nothing to me but I guess it's always been a personal bias to think of 6.22 as the last REAL dos.

I suppose I could use a 3rd party boot manager like you did. That would probably work much better than fighting with the built in one. I should really look into that.

It's worth noting that even if I wanted to I can't even use the DOS that comes with 95 because it's also pretty broken. I try the "restart in DOS mode" and it crashes. "Shut down computer" crashes. The only thing that doesn't crash is "restart computer" so that's what I do and then just hit the power button at the spinning ATI logo. I think my copy of 95 has more bugs than a bait shop.

You most likely have either Windows 95B (OSR2.1) or Windows 95C (OSR 2.5) - If you open up the Control Panel and double click System or, right-click on "My Computer" and choose "Properties", it should tell you which Windows version you have.
Refer to the Wikipedia page for further detail on the differences between the different versions: https://en.wikipedia.org/wiki/Windows_95#Editions

The USB drivers are not installed by default and, with Windows 95, has very limited support (for e.g., with USB flash drives and other removable media, you still need to install separate drivers).
There is a file called "usbsupp.exe " that you need to run and it should be on your OEM installation CD located at "drive:\Other\USB" where "drive" is your CD-ROM drive letter.

The issue that I described earlier has more to do with when you format your hard drive with FAT32 (as opposed to FAT16) and the fact that Windows 95 has long file name support - hence, not a good idea to run those older disk utilities. However, when you install Windows 95, you can use Scandisk and Defrag to provide those functions for you.

Apart from the above, I haven't come across any software that runs on DOS 6.22 but, not on DOS 7.x - if you do wish to have DOS 6.22 still on your system, then rather install them on two separate partitions and use a Boot Manager.
Personally, it's just easier and less hassle to install Windows 95 and boot straight into DOS 7 - thereby, you have everything on one partition and you can also use Windows 95's Windows Explorer for file management of your DOS programs.

Thanks, some good directions for me to pursue. I'll look into the boot manager solution and check the 95 version. The usbsupp is the name of the file I used to get USB support through an independent search, not off the CD. It may be the same file. It's pretty good for USB sticks but doesn't work for optical mice because it seems to lack the HID driver for them. All in all, I'm pretty happy with the computer's setup when it does work. I'll see about posting some pictures of the guts of the computer. It's been through a lot in its lifetime and deserves a proper showcase.

The shutdown issue is well known and only fixed in WinME, so its not just your PC. (I don't know If that is good or bad news though)

You are correct that Dos7 but you wont notice unless your tying to say run some old strange bit of hardware like a printer or scanner, use Dos antivirus, or other things that makes no difference on a gamming PC or has a Win95 install for system management. In fact you can free up more memory in 7 then you can in 6.22
http://www.mdgx.com/mem7.htm

I usually create an icon on my desktop to command.com and specify the autoexec.bat and config.sys from within the shortcut. ONLY modify the start up files from within the shortcut to ensure you don't mess up the incorrect ones.

If your dead set on keeping 6.22 then your boot disk will work as well, It can still point to the drivers on c:\ without any issues

Thanks that's great info. Is there any specific lines of code I need to add to make the computer believe it is booting natively from C? So far the problem I've had (not that big a deal) is that once booted from diskette, if I switch to C:\DOS and call a function, it thinks I'm running a different version of DOS and doesn't really believe that DOS is installed on C. This is despite having PATH lines in my diskette that match my copy on C.

You shouldn't have to do anything?
as long as the disk is formatted as a 6.22 bootdisk then all you would need to do is copy the autoexec.bat and config.sys files across to it.
It wont believe its booting from c:\, its more of a case it just doesn't care the majority of the OS is on another drive.

You could always create the bootdisk from within dos to ensure both are the same version. Format a: /s will create the bootdisk for you.