Re:Did the Windows 95 setup team forget that MS-DOS can do g...
by Philpax on Monday February 17, 2025 @01:12AM
(#43075755)
From the original article:
> At the other extreme, you can write Windows 95 setup as a 32-bit GUI program, but that means that if the user is starting from MS-DOS or Windows 3.1, you have to install Windows 95 before you can run Windows 95 setup, which is a bit of a catch-22.
Re:Did the Windows 95 setup team forget that MS-DOS can do g...
by Firehawke on Monday February 17, 2025 @03:18AM
(#43076510)
Back then a lot of the time you couldn't just boot from the Windows 95 CD-ROM; a lot of BIOSes didn't support bootable CDs yet, and would have to use a boot floppy as a shim. This would necessitate booting to a MS-DOS environment.
Also, if you didn't have partitions set up, you'd need to use MS-DOS FDISK and FORMAT to get things started, too. No way you'd have enough space in RAM to decompress and cram the entire Win95 UI into RAM to run it.
All in all, it makes more sense to go with the lightweight Win 3.1 intermediary step to bootstrap to the next phase.
Re:Did the Windows 95 setup team forget that MS-DOS can do g...
by cm2187 on Monday February 17, 2025 @03:24AM
(#43076558)
Plus I imagine win95 was still under development while they were writing the installer. Better to grab a mature component.
Re:Did the Windows 95 setup team forget that MS-DOS can do g...
by hypercube33 on Monday February 17, 2025 @08:01AM
(#43078524)
Windows 95 was also shipped on like 15 floppy disks so there was no live booting beyond the dos bootstrap disk
Re:Did the Windows 95 setup team forget that MS-DOS can do g...
by 486sx33 on Monday February 17, 2025 @09:08PM
(#43085358)
Some versions over 20!
https://www.reddit.com/r/RetroWindowsGaming/comments/ddwcz9/...
I thought this was going a different place. Surely if you want to run an operating system, running Windows 95 itself would make more sense - then you could e.g. use the same drivers for setup that you're going to use in the real system.