This includes more different core binaries, and mostly fixes the NE2000 to no longer panic and fault out when something dumb tries to probe it, by writing the wrong values in the wrong places.
For the curious build 334 is right here. We didn’t make the feature cut for version 10, so hopefully it’ll make 11. I’ll provide an unofficial build once v10 is announced, along with hopefully better networking back end modules, expanding things from pcap & SLiRP.
I used to use Veritas products (Volume Manager, File System and Cluster) professionally for quite a long time on Solaris and HP-UX. Except for Cluster, the software was exceptional for it’s time. Unfortunately after acquisition by Symantec and advancements of other storage technologies such as ZFS, the product suite disappeared from the radar completely.
Back to present time, I have a small x64 server that I use primarily as a NAS box plus run some applications, services and a few VMs. The machine runs Windows 2012 R2 Server which, for most parts I really like, with an exception of the storage stack, namely Storage Spaces. This is a completely botched feature both from functionality and management point of view. I don’t want to rant about it too much about it, so I just leave it as non working.
Unable work with Microsoft Bob of storage I have been looking for different alternatives, from using the Windows built-in VDS RAID-5 option found, to moving entirely to a different OS. This is when I remembered that, some (OMFG) 10 years ago Symantec has announced free Storage Foundation Basic, also available on Windows. Still continued and supported to this day, so obviously I wanted to give it a spin and evaluate whether it makes any sense to use such a dinosaur in a modern world.
I spun up a Windows 2012 R2 guest vm, added some data disks, downloaded the latest version 6.1 (released in 2014) from here and ran the installer.
PCem is different from other emulators in that when it starts up, reboots it’ll tear itself apart, and re-kick all the components. Normally other emulators do this once, and as a result I never noticed that slirp_exit doesn’t actually purge the socket state. And calling the socket teardown call causes a mbuf explosion in the code. Sadly GDB is pretty useless trying to debug it, since it’s claiming all the structure members don’t exist. Very strange.
Luckily I could duplicate the debug feature to go though current socket redirects, and close the sockets on the Windows side with a simple closesocket.
In this version I’ve setup the following TCP port redirects:
Ever have one of those days, where you suddenly get a weird email? Recently I thought the whole ‘google security’ thing was a bit over the top, then I get this fine email. I’m pretty sure it’s from a hotel I stayed at, looks like they had something there to MitM me. Great. But thankfully they used an old ass machine from the looks of it, so it triggered google.
You read it right, VMWare Player has made the jump from version 7 to version 12.
Big changes are better support for Windows 10, both as a host and as a guest, along with DirectX 10 and OpenGL 3.3 support. vCPU support has been bumped up to 16 processors, and the memory cap is now 64GB per VM and 2GB for video.
It’s hard to believe that it has been 20 years since the release of Windows 95. But here we are.
Windows 95 started it’s life as a 32bit upgrade from Windows 3.1 code named ‘Chicago’ to compete with the 32bit version of OS/2 for the desktop. Chicago is more famous for it’s incredible delays as the project suffered from feature creep, along with a complete UI redesign. It’s also worth noting that even back as far as October of 1992, just after the release of Windows 3.1 Microsoft was already hard at work on Win32s, the Win32 subset and compatibility layer for Windows 3.1 to run Windows NT Win32 applications.
In my opinion, Windows 3.0 was the most significant piece of software that Microsoft has ever shipped. This was the point where they broke away from IBM, and went their own way. And it showed that they were capable of launching a major environment without the support of their biggest partner. Although sadly, OS/2 paid the price.
Windows 95 would be a close second as to what would be Microsoft’s most significant software, as it brought 32bit computing to the masses, along with a completely different user interface, one that remains popular to this day with the start button. Even the marketing used to Rolling Stones song ‘Start me up’. Windows 95 is also the first time (and last) that I can ever recall there being a Microsoft release party where actual users showed up, but were enthused. Back when OS X shipped on physical media, you would see Apple fans camping out for the latest release, but for Microsoft this was the one time where the next release was going to be so significant with a whole new generation of applications like Office 95, and a much more easier to use interface people really were excited about it. As much as Windows 10 is a great improvement on Windows 8, I don’t see anywhere near this kind of enthusiasm compared to Windows 95.
Before Windows 95 people had to fight the Program Manager, which was a MDI application which means it has windows inside of windows. And it’s easy to obscure and lose place of programs. I’ve seen users re-install applications because ‘they lost them’ not realizing the program group was hiding behind another window. To many average users Program Manager was a nightmare to work with on a daily basis.
And to say that it’s complimentary program, File manager was also a MDI nightmare to work with was an understatement. Again windows get hidden behind windows, it is all inside of another window so it can be confusing moving things around, and trying to get a good view. To an average user, it’s tedious to work with and to get two full screen views of files, requires two copies of the application to run, which in the days of 4MB of ram or less was a luxury when you figure they were running an application as well. Not to mention since there is no task bar, it was also common for people to launch multiple copies of an application since it would be hiding behind a window they didn’t know about.
Windows 95 Desktop
The Windows 95 UI solved all of these problems by showing us what is running, and by unifying Program Manager, and File Manager into one. Now we can see what is running, we have a desktop to move things around, and we can open up multiple file windows and move them around at will. Even in this simple screen shot with multiple applications running, it’s trivial to see what is going on, and how to navigate it. We take it for granted today, but compared to the old Program Manager, File Manager paradigm this was simply an upgrade to get enthusiastic about!
Windows 95 launch
And just look at this picture, isn’t this the look of excitement? Over a piece of software? From Microsoft? The transition from 16bit to 32bit was so great, I really wonder if they ever again will have this kind of appeal. Going from 32bit to 64bit has been so seamless I suspect many 64bit users don’t even know they are.
32bit applications promised (and delivered) on greater stability, and of course being able to actually use RAM that people had bought. It was the end of segmented 64kb segments, and the use of 32bit flat memory models, that even in the game industry everyone had been flocking to 32bit MS-DOS extenders. Now 32bit was going mainstream on the desktop. Even though Borland had captured so much of the developer mindshare on MS-DOS, they just couldn’t achieve the same success level on Windows, and especially with Windows 95, it started the rise of Visual C++ and Visual Basic everywhere.
Networking was another strong point of Windows 95, as it included not only LAN support for TCP/IP, IPX and NetBEUI out of the box, but it also included dialup PPP support for all three protocols. This is basically where other consumer OS really blew it, and why Microsoft not only ended up owning the desktop, but also the server space in corporations. It was a common practise to sell the networking stack, and applications separately making a networked machine quite expensive. SCO Xenix charged for the OS, Streams, and TCP/IP. IBM charged separately for their TCP/IP as well. By 1994 IBM started to see this as a mistake, and included DIALUP ONLY networking for Warp. This stop gap measure was barely acceptable for 1994, but as the PC world got more and more connected this meant LAN connections along with wide area which IBM dropped the ball by charging yet even more for Warp Connect. Where Windows for workgroups, Windows 95, and Windows NT included all of this, and multi-protocol support.
Microsoft also was busy creating their own online service, MSN, a competitor to AOL, CompuServe, Prodigy et al. There is a better writeup on winsupersite than I could do, since I never did use it. But the upshoot is that Microsoft was late to the internet party, and did not include any browser with the first retail version of Windows 95. Later versions of course did include Internet Explorer.
The most significant early version of Internet Explorer has to be version 3, which is when Microsoft finally started to take it serious, and included things like SMTP/POP3 and USENET clients. Back then, USENET was actually big. This is before the rise of every website being a forum, instead we had a global distributed database that everyone could post onto. It wasn’t instant though, so it could take days for a reply. The kind of thing we take for granted now with many AJAX enabled websites able to alert you right away, or you can check the status with a simple refresh.
A worker packs the shelves of PC World, Croydon, with copies of the Microsoft Windows 95 upgrade computer package. The package will go on sale at midnight across the country.
I may have to touch on the rise and fall of Internet explorer at a later date, but check out the exciting back of the Windows 95 box that included Internet Explorer:
Windows 95 box SE, back
For those who want to remember, the Windows 95 start sound!
And speaking of which next year will be 20 years of Windows NT 4.0, and how it utterly changed the server market forever.
So PCem is an incredible emulator for the IBM PC platform. One thing that has been missing, and really missed has been networking. So a while ago, SA1988 came up with a patch that incorporated the BOCHS ne2k.cc into PCem.
So as requested, I took the copy of SLiRP I’ve used in SIMH, Cockatrice and Previous, and got it working in PCem.
Telnet from MS-DOS
This has to be one of the easier ports since PCem doesn’t use threads. But yes, it appears to work, although I haven’t done any major testing.
For those who want to experiment, here is a binary/source blob of the project. Right now we are just past the OMG it compiled phase to OMG it SENT and RECEIVED data phase.
If anyone wants to play, the NE2000 is set to 0x300 IRQ 10.
And you need to manually add the following to your pcem.cfg file: