You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Speaking of fragmentation, I've had this crazy idea for a long while that might be an interesting project. What you do with the project, is install the base OS (Windows 3.1, 95, 98, ME) and then overwrite system files with ones compiled from the project. You would have a project that, bit by bit, replaces the Microsoft components with open source ones, until eventually the open source bits can stand on their own as a complete Windows 3.1/9x/ME compatible system. Then once you've done that you can adapt the kernel to run on modern processors and hardware, and retro gamers could rejoice and enjoy their own games again without worrying where Microsoft would take you today :) It would be the 3.1/9x/ME complement to ReactOS's focus on NT-based Windows. Bonus points if the open source Windows clone runs atop FreeDOS.
Can DOSbox-X integral DOS be made compatible with Win9x/ME Windows part? So that we can have a Win9x/ME simultaneously with the extra features of DOSbox-X that are "lost" when booting MS-DOS as guest?
The text was updated successfully, but these errors were encountered:
Closing as the same is already in discussion at #1217. One potential solution I read there: install Win98 in a image, then imgmount it and run its win.com from DOSbox-X native prompt (instead of booting from the image) - haven't tested that yet myself.
Originally posted by @joncampbell123 in #188 (comment)
It seems FreeDOS doesn't support "running" win.com of Win9x/ME, but that is/was possible from "LZ-DOS".
Can DOSbox-X integral DOS be made compatible with Win9x/ME Windows part? So that we can have a Win9x/ME simultaneously with the extra features of DOSbox-X that are "lost" when booting MS-DOS as guest?
The text was updated successfully, but these errors were encountered: