That's how I remember it, too.
Just make a backup of your DOS files (autoexec.bat, config.sys) and choose a different directory for Windows 95.
Say WIN95 or WINDOWS.95
If needed, you can re-insert the old drivers with a text-editor (if you use Win95 DOS instead of DOS 6.22).
Things like MSCDEX and the DOS CD-ROM driver are often removed by Windows 95 Setup.
Just add them back. Windows 95 will use them.
Technically, Windows 95 itself does not need MSCDEX anymore, also.
It has the CD extension built-in. So it's sufficient to load the CD-ROM driver alone.
For Windows 95, I mean. DOS and Windows still need both.
This practice was used in the early days of Windows 95,
when proprietary CD-ROM drives still existed,
but Windows 95 had no Windows drivers for it.
Just one note about Windows 3.1x ws Windows for Workgroups 3.11.
WfW uses VFAT, which is managed/implemented by a *.vxd.
It may not work properly on Win95 DOS which supports FAT32 and FAT16+LFN.
There's a patch for DOS 7 which makes things more compatible, though.
Just keep in mind that it's not possible to use a Windows 3.1 HDD driver (FastDisk) here.
Useless information. Please do not read:
Ok, technically, it's possible to make DOS 7 to use old hard disk utilities.
The LOCK command can help here.
It will allow DOS programs that aren't DOS 7 aware to fully access the HDD.
However, that's dangerous to do if the DOS installation exceeds the old world order.
The old limitations, I mean.
CHS maxium, DOS 3.x partition maximum (32 MB for old FAT16),
2GB partition maximum in DOS 4-6 etc.
Things like that.
Applies for things like PC-Tools before version ~v6 (say PC Tools v4).
Programs released in the DOS 4 era should be fine already.
Good luck! 🙂🤞
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//