first roadblock: the Windows Me installer corrupts the filesystem as it loads
Booting FreeDOS with minimal driver support seems to allow the install to proceed
The install has completed, now to see if the system actually works and if it didn’t replace FreeDOS with its own MSDOS
The system boots and works flawlessly, I installed VMWare tools to get all the required drivers and everything runs fine. Now the thing is: I have no idea how to check the underlying DOS version, lol
I’ll install the patch that restores the DOS mode functionality and see if it boots to FreeDOS
Hey so… Looks like this is a thing huh. I expected this to be harder to achieve
to my understanding it is loading the FreeDOS values, but it still replaces the shell and the kernel with its own so apart from the executables that come with FreeDOS there isn’t much of it left running. Windows 98 would do the same I think?
Interesting experiment though.
@Siph Oh wow, amazing
@Siph So it just looks like it kept the startup files and variables but still uses its own version of DOS.
if it's still loading DOS drivers/TSRs as part of normal Windows booting Is predict there would be some errors showing up in Device Manager complaining about not being 32-bit/real-time
@Mycroft that makes sense, I kind of suspected that it wasn’t FreeDOS’ kernel being loaded anymore
@Siph you can try creating a winme rescue disk image (or clone the VM), boot back toa FreeDOS image, sys the drive, reboot, and see if winme will load (may have to run win.com manually)
can try the same with win98 kernel
Generalist Hometown instance with a strong focus on community standards. No TERF, no SWERF, no Nazi, no Centrist.