13 ms·
Why did Windows 95 setup use three operating systems?
- jmclnx 2y agoI never thought of Windows 3.1 as an OS. The other 2 was MS-DOS and Windows 95.
- rusk 2y agoAgree, the terminology in those days was “shell”. Though Windows 95 was arguably similar running atop “DOS 7” it actually imposes its own 32-bit environment with its own “protected mode” drivers once booted. Dropping to DOS reverted to “real mode”.
- tliltocatl 2y agoSo did the lastest Win3.1 for workgroups, just MS spared all the fanfare for Win95. Not sure if the 3.1 version in the installers does.
- rusk 2y agoWindows 3.1 was just a graphical shell. All the drivers and stuff were still managed by DOS. You still needed to configure your system with config.sys EDIT it’s coming back to me. Windows 3.1 did have a a subsystem for running 32 bit apps called Win32 I think that’s what you mean. This was very much in the application space though. It still used cooperative multitasking and Win 95 introduced preemptive.
- YakBizzarro 2y agoIt was Win32s https://en.m.wikipedia.org/wiki/Win32s https://en.m.wikipedia.org/wiki/Win32s
- rusk 2y agoThanks ”Win32s lacked a number of Windows NT functions, including multi-threading, asynchronous I/O, newer serial port functions and many GDI extensions. This generally limited it to "Win32s applications" which were specifically designed for the Win32s platform,[4] although some standard Win32 programs would work correctly”
- kjellsbells 2y agoIt was a strange time back then for anyone who wanted to get online. Win3.1 had no TCP/IP stack so many folks used a third party download called Trumpet Winsock. IIRC you might have needed win32s in order to use it. Looking back, Microsoft were clearly in an incredibly complicated transitioning phase, with very little margin for error (no patching over the Internet!)
- phire 2y agoTrumpet Winsock works on a 286, but apparently NCSA Mosaic version 2.0 needed Win32s. So I guess there would have been a time in 1994 where many people were forced to retire their 286es. Though Mosaic was quickly replaced by Netscape Navigator in late 1994 which worked on Win16. And then Windows 95 came along, and it really needed a 486 with 4MB of ram, ideally 8MB.
- dboreham 2y ago1994 wasn't a time where everyone was using a web browser.
- int_19h 2y agoMuch later, the HX DOS Extender (https://www.japheth.de/HX.html https://www.japheth.de/HX.html) had something vaguely similar called Win32 emulation mode. Meaning that you could load a Win32 PE image, and it could call quite a few Win32 APIs, all while running under plain DOS (in 32-bit flat mode), with HX DOS providing the implementation. It had just enough parts of the API implemented to be able to run Quake 2 in DOS.
- nkrisc 2y agoI was only 5 or 6 maybe when I used Windows 3.1 so I may be misremembering, but didn’t it have an X on the desktop to close the GUI and return to the DOS prompt?
- mixmastamyk 2y agoMy memory is that closing Program Manager exited windows.
- rusk 2y agoThere was a way to “drop to DOS” alright, which is what you would have had to do for games and the like. Can’t remember the exact mechanism but it could have been the x on the “program manager” window. The raise Windows you’d type “win” and if you wanted to “boot to windows” you would call “win” from your autoexec.bat
- nkrisc 2y agoThat sounds about right. My dad had commands written on sticky notes on the monitor for me. As a recall I had to in order to play Commander Keen.
- LocalH 2y agoWindows 3.1 didn't have any "X" buttons. It had the system menu (the one shaped like a spacebar, since the hotkey was Alt-Space). If you quit Program Manager, it would end the Windows session (since Program Manager was your shell). If you had a replacement shell (as some did back then, Norton Desktop etc), then quitting that would exit Windows and return to a pure DOS prompt.
- DHowett 2y agoBryan Lunduke has an article about this myth, actually! https://lunduke.locals.com/post/4037306/myth-windows-3-1-was-just-a-shell-on-top-of-dos https://lunduke.locals.com/post/4037306/myth-windows-3-1-was... It’s backed up by another Old New Thing article at https://devblogs.microsoft.com/oldnewthing/20100517-00/?p=14013 https://devblogs.microsoft.com/oldnewthing/20100517-00/?p=14... The TL;DR is that Windows 3.1 effectively replaced DOS and acted as a hypervisor for it, while drivers could be written for Windows (and many were) or DOS (and presumably many more of those were actually distributed). The latter category was run in hypervised DOS and the results bridged to Windows callers. (Edited after submission for accuracy and to add the Old New Thing link.)
- phire 2y agoOne of the major motivations for windows, is that the driver situation for DOS really sucked. Every single office suite had to talk directly to printers. Text mode was reasonably uniform, but printing graphics required the application to know about the printer. And games needed to talk directly to the video card and sound card if you wanted anything more than PC speaker beeps and non-scrolling screens on one of the default BIOS graphics modes. One of the major selling points of Windows 1.0 was a unified 2D graphics API, for both screen and printing. The graphics vendor would supply a driver and any windows application could use its full resolution and color capabilities needing to be explicitly coded for that graphics card. This rendering API also supported 2D accelerators, so expensive graphics card could accelerate rendering. 2D accelerators were often known as Windows accelerators. Windows 3.1 still relied on DOS for disk and file IO, but everything was can be done by VXD drivers, and should never need to call back to DOS or the BIOS (which was slow, especially on a 286) With Windows 95, Disk/File IO were moved into VXD drivers, and it was finally possible to do everything without ever leaving protected mode (though, DOS drivers were still supported). Read more about the history of Device drivers here: http://www.summitsoftconsulting.com/WinDDHistory.htm http://www.summitsoftconsulting.com/WinDDHistory.htm And I really enjoyed this documentary about the development of Windows 1.0: https://www.youtube.com/watch?v=vqt94b8bNVc https://www.youtube.com/watch?v=vqt94b8bNVc
- int_19h 2y ago
- rbanffy 2y agoI think it’d be fair to call it more than a shell. It was also a set of libraries that implemented the common user interface elements of Windows apps, similar to the Macintosh Toolbox but not in ROM.
- rusk 2y agoNot sufficient on its own to qualify it as an OS though. The VM subsystem described in sibling comment makes a big difference though!
- Hilift 2y agoAnother competitor shell at the time was "WordPerfect Office for DOS". Which I witnessed some people launch from Windows 3.11. I believe it had WordPerfect and what preceded GroupWise for email. https://mendelson.org/wpdos/shell.html https://mendelson.org/wpdos/shell.html
- tzs 2y agoI don't think it actually reverted to real mode. I believe Win 95 continued with what they had done in Windows for Workgroups 3.11, which was the first Windows that required an 80386. What that did is use DOS as a first stage boot loader, then switched into protected mode and created a v86 task which took over the state of DOS. The protected mode code than finished booting. v86 mode was a mode for creating a virtual machine that looked like it was running on a real mode 8086 but was actually running in a virtual address space using the 80386 paging VM system. When you ran DOS programs they ran in v86 mode. If a DOS program tried to make a BIOS call it was trapped and handled by the 32-bit protected mode code. v86 mode tasks could be given the ability to directly issue I/O instructions to designated devices, so if you had a device that didn't have a 32-bit protected mode driver a DOS driver in a v86 task could be used. For devices that did have a 32-bit protected mode they would not give v86 mode direct access. Instead they would trap on direct access attempts and handle those in 32-bit protected mode code. I wish Linux had adopted a similar use of v86 mode. I spent a while on some Linux development mailing list trying to convince them to add a simplified version of that. Just virtualize the BIOS in a v86 task, and if you've got a disk that you don't have a native driver use that v86 virtualized BIOS to access the disk. Eventually someone (I think it may have been Linus himself) told me to shut up and write the code if I wanted it. My answer was I couldn't do that because none of my PCs could run Linux because there were no Linux drivers for my SCSI host adaptors. I wanted the feature so that I could run Linux in order to write drivers for my host adaptors. OS/2 did the v86 virtualized BIOS thing, and that was how I was able to write OS/2 drivers for my SCSI host adaptors.
- ndiddy 2y agoWindows 3.1 is basically 95% of an OS. When you're booted into Windows 3.1, MS-DOS is only used to run MS-DOS software and to handle filesystem access. Windows 3.1 controls the processes, memory, video card, system timer, keyboard, mouse, printer, etc. (pretty much every system resource besides disk I/O) while it's running.
- xeromal 2y agoI love that little nugget of info at the end. You could originally run excel standalone without an OS and it came with windows 2.1 bundled
- rusk 2y agoI think it needed DOS … just not the Windows “shell”
- skissane 2y agoIt came bundled with a stripped down version of Windows 2.x - missing the application launcher (in Windows 1.x/2.x known as MS-DOS Executive, replaced by Program Manager and File Manager in Windows 3.x), so it could only be used to run one application (Excel) unless you fiddled with its configuration. Yes it needed DOS because pre-3.11 Windows versions actually used the DOS kernel for all file access. When 32-bit file access was introduced in WfW 3.11, that was no longer true-but it was an optional feature you could turn off. In all pre-NT Windows versions, Windows is deeply integrated with DOS, even though in 9x/Me that integration is largely for backward compatibility and mostly unused when running 32-bit apps - but still so deeply ingrained into the system that it can’t work without it. IIRC, Microsoft tried to sell the same stripped down single-app-only Windows version to other vendors, but found few takers. The cut-down Windows 3.x version used by Windows 95 Setup is essentially the 3.x version of the same thing. Digital Research likewise offered a single app version of their GEM GUI to ISVs, and that saw somewhat greater uptake.
- simonjgreen 2y agoMost interesting part of the whole thing for me! The later WinPE environments are some of the most overlooked computer environments out there but they were absolutely everywhere. EPOS, ATMs, digital signage, vending machines. And of course the subject of so many BSOD photos…
- KerrAvon 2y agoNone of that stuff was pre-NT, though. Windows 2.1 was not something you'd want to deploy on an ATM.
- reddalo 2y agoDon't modern versions of Windows do the same? For example, I clearly remember that the Windows 10 installer first launches a Windows 7-like environment.
- heraldgeezer 2y agoYes that is Windows Preinstallation Environment (also known as Windows PE and WinPE) https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-intro?view=windows-11 https://learn.microsoft.com/en-us/windows-hardware/manufactu... https://en.wikipedia.org/wiki/Windows_Preinstallation_Environment https://en.wikipedia.org/wiki/Windows_Preinstallation_Enviro...
- zokier 2y agoAren't all modern (>xp) windowses just NT6 under the hood? Is there such clear delineation between 7 and 10 for example?
- rbanffy 2y agoIt feels like NT4, with 2000 on top of it, then a layer of XP, then Vista, then 7, then 8, then 10, and, finally, 11. It’s not uncommon to do something that lands me on a dialog box I still remember from Windows NT 3.1. The upside is that they take backwards compatibility very seriously, probably only second to IBM.
- WeylandYutani 2y agoYes it may not be the prettiest but I can get 20 year old games to run with relatively little troubleshooting.
- rbanffy 2y agoYou can still run 50 year old games on your newest IBM Z16 mainframe. Microsoft is just a baby in this business. If you have a Unisys Clearpath boxes, you can even get get some 60 year old games running, provided you can read the punchcards ;-)
- pram 2y agoThe "mini" Windows 3.1 it came with was pretty much fully functional though, you could literally boot directly into PROGMAN.EXE as the main Windows 95 shell.
- Dalewyn 2y agoProgram Manager is a shell and was actually included in Windows all the way through XP SP2 when it was phased out. You can probably run it in Windows Vista through 10 if you copy the .exe over, too.
- joombaga 2y agoMaybe! Is the XP version 32-bit? 64-bit windows never supported 16-bit programs.
- Just_Harry 2y agoUnfortunately not, I just tried running the copy included with Windows XP SP1 on Windows 11—it relies on SheRemoveQuotesW which was removed from Shell32 in Windows Vista. (It doesn't seem to be able to use a copy of a Windows-XP-sourced shell32.dll from the working directory, either).
- Dalewyn 2y agoThat's because Windows 11 only comes in 64-bit flavors and Program Manager as bundled with XP would be 32-bit. WoW64[1] can't bridge 64- and 32-bit binaries in the context of system components, such as the shell. Try running that under 32-bit Windows 10, I never tried it myself but I have a feeling it should work. [1]: https://en.wikipedia.org/wiki/WoW64 https://en.wikipedia.org/wiki/WoW64
- IWeldMelons 2y agocan technically be patched with ReeactOS's implementation of the functiom.
- rbanffy 2y agoIf they were going to install a bare Windows 3, they could at least make an effort to ship a bare 95.
- Animats 2y agoBecause, when they did it right, in Windows NT 3.51, the users with legacy 16 bit applications screamed. There was a 16-bit DOS compatibility box, but it wasn't bug-compatible with DOS. Microsoft underestimated the inertia of the applications market. NT 3.51 was fine if you used it as a pure 32-bit operating system. You could even configure it without DOS compatibility. Few did.
- Onavo 2y agoSomething the Unix world can certainly learn from.
- bigfatkitten 2y agoSun used to take binary compatibility very seriously. Solaris 8 (and perhaps later releases) still had a compatibility layer for SunOS 4.x binaries. Solaris 11 can still run Solaris 2.6 binaries. Linux is another matter entirely, if your binaries run at all from one distribution release to the next you're doing well.
- ghssds 2y agoLinux doesn't need binary compatibility as much as Windows, lot of source packages will compile right away with a vast array of different operating systems, typically excluding Windows but including Linux, and Linux is a few clicks away from running a fair number of MS-DOS and Windows applications, probably more than any single Windows version. Linux is king in compatibility.
- bigfatkitten 2y agoThat doesn't help you at all when you don't have the source and even then, compiler changes break source compatibility all the time.
- Onavo 2y agoNot just Linux, Mac too (people forget that they run a certified BSD kernel).
- brian-armstrong 2y agoThe fact that Windows can upgrade an installation in place with relatively high success is impressive. Is it possible to have an install that's been repeatedly upgraded all the way from MS-DOS without needing a reformat somewhere along the way?
- ClassyJacket 2y agoThere's various youtubers who have tried upgrading MS OSes thru as many versions as possible and they have taken it pretty far
- agumonkey 2y agoIncluding preserving custom user config (colors, background images) I feel strange about hating on MS after the 2000s
- redwall_hp 2y agoLet me fix that: Internet Explorer 6 existed and far overstayed its welcome well into the 2000s.
- pjmlp 2y agoAnd then people instead of learning this lesson, helped Google turn the Web into ChromeOS.
- agumonkey 2y agowhat tech told us is that problem lies between chair and (keyboard|parliament|wheel|...) it seems
- account42 2y agoOn the other hand, IE6 held web developers back from bloating their sites and turning them into "apps" when all the users want are a document with maybe a little interactivity here and there.
- impoppy 2y ago> Raymond has been involved in the evolution of Windows for more than 30 years. He occasionally appears on the Windows Dev Docs Twitter account to tell stories which convey no useful information. Way to go Mr. Raymond!
- TimTheTinker 2y agoI always thought Windows (until 7) looked so lacking in polish around the edges compared to even the earliest versions of Macintosh system software -- especially during install, boot, crash, and shutdown. During boot, for example, even modern Windows boxes [correction: pre-EFI only] show a BIOS screen followed by a brief blinking cursor before the Windows graphics mode takes over. It was much worse in earlier versions. The Macintosh screen never dropped you into a text-mode console, no matter what. Everything on the screen was graphics-mode, always -- and there weren't glaring design changes between system versions like in Windows (except at the Mac OS X introduction, which was entirely new). Installing Macintosh system software onto a HDD was literally as easy as copying the System Folder. System installer programs did exist, but in principle all that was happening was optionally formatting the target drive and then copying System Folder contents. So simple. Of course there were problems and shortcomings, but the uncompromising design esthetic is noteworthy and admirable.
- sdflhasjd 2y ago>During boot, for example, even modern Windows boxes show a BIOS screen followed by a brief blinking cursor before the Windows graphics mode takes over. This hasn't really been the case for more than 10 years now. EFI based systems will boot without changing display modes. Some hobby custom PCs might have compatibility modes enabled, but any laptop or prebult system is going to go from logo to login without flickering.
- bigstrat2003 2y agoIt also has nothing to do with Windows. Apple controls both the hardware and the OS, Microsoft controls only the OS. If the OEM decides to have the system boot up in text mode, there's nothing Microsoft can do.
- johannes1234321 2y agoMicrosoft has (had?) quite some power over OEMs and could set requirements on the system. A system not compatible to windows won't see much sales. However Microsoft values compatibility, which probably is in conflict with requiring more.
- wmf 2y agoClearly they should have used QNX for the installer so it would have fit on a single floppy.
- dusted 2y agoRaymond Chens blog and book (The Old New Thing) is an absolute delight! I always had a big respect for how intuitive the Windows 95 GUI is, and reading his description of the thoughts and methods behind its inception, it's no surprise that it became so good. It seems like Microsoft was extremely pragmatic and reasonable in many of their endeavors back then. It's a wonder how it degenerated into the absolute unit of sh*t that is modern Windows (even if the filesystem and kernel is arguably a lot better, everything on top seems to be developed by an army of interns)
- rqtwteye 2y agoArmy of interns should about right. I always suspect that Teams is developed by some beginners who are learning Scrum. But yes, Windows 95 to Windows 2000 were a huge jump in usability. From Windows 8 on and the “Metro” interface they threw it all away.
- Cumpiler69 2y ago>I always suspect that Teams is developed by some beginners who are learning Scrum I get the same feeling from Google's android and Pixels. Lots of neat features keep getting added, but the SW and HW issues that end up in the final product make it seem like an incredibly amateurish effort for such a wealthy company hiring top talent.
- hulitu 2y agoI think they rotate the interns every year. That will explain the GUI^WUX advances. /s
- Cumpiler69 2y agoUI/UX keep getting shittier over time is an industry wide phenomenon not a Google exclusive one. To me everything kinda peaked in late 2000's and has been on a downwards slope ever since the mobile became the dominant platform so everything from desktop PCs to cars had to look and function like a phone.
- bsaul 2y agoThere's really something missing today as opposed to the 80s and 90s : back in the days, you had new computer brands coming out every year, with they own OSs and hardware... It really was a perpetual amazement and joy. Of course at that time i didn't have to work with all those things, which made any compatibility issues not that important to me. Yet i wonder : how can we relive through those enjoyments ? It was a bit similar when mobile phones started, but it settled much quickly, without leaving any but 2 survivors for the last decade. What makes it so hard today to release new hardware+software for the mainstream market ?
- TheAmazingRace 2y agoI think it boils down to inertia. Microsoft absolutely played their cards expertly well in the nascent days of the microcomputer, all the way through to the new millennium. They also adopted bully tactics to prevent upstarts (like Be for example) from upsetting the apple cart and had ironclad contracts with OEMs when distributing Microsoft Windows. It also helps that the IBM PC became such a pervasive standard. The competition, such as Commodore, Atari, Acorn, you name it, couldn’t help but find ways to blow their own feet off any time they had an opportunity to make an impact. Heck… even Apple came very close to self destruction in the late 90s, with Steve Jobs and NeXT being their Hail Mary pass. In short, now that we’ve had personal computers for decades, it’s very difficult to break into this market with a unique offering due to this inertia. You have to go outside normal form factors and such to find any interesting players anymore, such as the Raspberry Pi and GNU/Linux. As an aside, I kinda wish Atari Corporation was run by less unscrupulous folks like the Tramiels. Had they realized their vision for the Atari platform better and hadn’t taken their “we rule with an iron fist and treat our partners like garbage” mentality with them from Commodore, they might have stuck around as a viable third player.
- gugagore 2y agoI was looking for a blogpost from many years back about features Windows cannot provide, because it would result in logical inconsistencies if multiple applications used the feature. The blogpost gave examples like setting the desktop background or file-application associations "definitively" from applications, and mentioned at least one example of two applications fighting resulting in some chattering in the Windows UI. I thought it was Raymond Chen's blog but I haven't been able to find it. I thought someone here might recall and have a pointer.
- TonyTrapp 2y ago"What if two programs did this?" https://devblogs.microsoft.com/oldnewthing/20050607-00/?p=35413 https://devblogs.microsoft.com/oldnewthing/20050607-00/?p=35... This is a recurring theme featured in multiple of Raymond Chen's blog posts, though. This is just the earliest one I can remember. Here's a few more: https://www.google.com/search?q=%22two+programs%22+site%253Adevblogs.microsoft.com+inurl%253Aoldnewthing https://www.google.com/search?q=%22two+programs%22+site%253A... The "what if two programs did this" mantra I learned from these blog posts helped me greatly in judging whether certain feature requests from users make any sense at all. As soon as it involves touching system configuration, even if there is an API for it, it's probably a very bad idea.
- eonmist 2y agoI remember the talk back then was: "The better way is to install Windows 95 on top of DOS."
- pluto124 2y agoReading these comments is like seeing revisionist history. Windows 95 was the biggest piece of crap. The thing crashed constantly. Windows 11 today looks better and runs better. There is simply no comparison. Anyone who says different has no idea what they are talking about.
- dole 2y agoAh, another user who missed out on Windows ME.
- Aachen 2y agoI was little, but I remember using Windows 95 on a machine that had it pre-installed and it ran stably from what I recall. They're good childhood memories more than that I'd be a revisionist agent That Windows Vista and newer look better, even if their design languages are mixed (old and new configuration panels mixed depending on which ones they could be bothered to recreate, for example) and are more complex, I don't think anyone argues. I've never heard of anyone using the simpler classic theme for reasons other than nostalgia or performance
- INTPenis 2y agoDoesn't Windows setup still use some weird minimal version of Windows? I remember having to hack my employers provisioning once to install virtio drivers and I ended up in this "purgatory OS" where I could use DOS commands to add drivers.
- deleted 2y ago[deleted]
- yabones 2y agoIt's called "WinPE" or Windows Preinstallation Environment. It's very strange. Tools you really think would work like Powershell are completely absent by default, and when added work in unexpected ways. Adding drivers is also painful, since it doesn't really support all of the regular windows drivers. To sideload drivers you have to do it twice, once for the install image and once for the winpe image. *My knowledge of this stuff is about 7 years outdated, so it's possible they've improved it since then... Unlikely but possible. https://en.wikipedia.org/wiki/Windows_Preinstallation_Environment https://en.wikipedia.org/wiki/Windows_Preinstallation_Enviro... https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference?view=windows-11 https://learn.microsoft.com/en-us/windows-hardware/manufactu...
- iamwpj 2y agoI did a bunch of work with WinPE for Win 7,8, and 10. Customizing the environment for automated deployment was a ton of fun. I really came to appreciate the tooling available in WinPE (and it's eccentricities). It's probably what really paved the way for my transition to Linux.
- MiscIdeaMaker99 2y agoI still have my Windows 95 installation floppies. It was a phenomenal operating system at the time, but I don't miss it one bit.
- imxinadic2016 2y ago[dead]
- gslin 2y agoIt seems also answer https://retrocomputing.stackexchange.com/questions/14903/why-does-part-of-the-windows-98-setup-program-look-older-than-the-rest https://retrocomputing.stackexchange.com/questions/14903/why... this.