The first version of the IBM PC was introduced in August 1981. Apple responded by running an ad in the Wall Street Journal with the headline 'Welcome, IBM. Even though he was usually tight with money, Steve Jobs allowed the Mac team to buy an early unit to dissect and evaluate.

The day it became available, we ran to the store and purchased one to take back to the lab. Needless to say, we were not very impressed with it. From the perspective of the Macintosh that we were already in the midst of bringing to life, it seemed like ancient history the day it came out. There was little, if any, Woz-like cleverness in the hardware design, using dozens of extraneous chips without having any cool features. The 8088 was a decent processor compared to the 6502, but it paled next to the 68000 we were using in the Mac. But the most clunky part of the system was the software.

MS-DOS seemed like a clone of an earlier system, CP/M, and even the demo programs lacked flair. It came with some games written in BASIC that were especially embarrassing. The most embarrassing game was a lo-res graphics driving game called 'Donkey'. The player was supposed to be driving a car down a slowly scrolling, poorly rendered 'road', and could hit the space bar to toggle the jerky motion. Every once in a while, a brown blob would fill the screen, which was supposed to be a donkey manifesting in the middle of the road. If you didn't hit the space bar in time, you would crash into the donkey and lose the game. We thought the concept of the game was as bad the crude graphics that it used.

Since the game was written in BASIC, you could list it out and see how it was written. We were surprised to see that the comments at the top of the game proudly proclaimed the authors: Bill Gates and Neil Konzen. Neil was a bright teenage hacker who I knew from his work on the Apple II (who would later become Microsoft's technical lead on the Mac project) but we were amazed that such a thoroughly bad game could be co-authored by Microsoft's co-founder, and that he would actually want to take credit for it in the comments. I found another account of Donkey in a conversation between Bill Gates and Bixhorn. For those who might want a little more history about 'Donkey.bas': ARI BIXHORN: Now, to help set the context for just how far Visual Basic has come and really how far the Basic language has come, I'd like to take a step back just a few years and look at an application that was written in Basic. This application, called Donkey.bas was actually written by none other than the gentleman standing to the left of me.

Bill, how long ago was it that you wrote Donkey.bas? BILL GATES: Actually, it was myself and Neil Thompson at four in the morning with this prototype IBM PC sitting in this small room.

IBM insisted that we had to have a lock on the door and we only had this closet that had a lock on it, so we had to do all our development in there and it was always over 100 degrees, but we wrote late at night a little application to show what the Basic built into the IBM PC could do. And so that was Donkey.bas.

It was at the time very thrilling. So go ahead and show them what that looks like. ARI BIXHORN: Let's go ahead and take a look at Donkey.bas. This is back in the day where the Basic language still had line numbers. We still had great constructs like 'gotos' and I think that the development environment speaks for itself. But to really see how cutting edge Donkey.bas was, let's go ahead and run it.

(Laughter.) And as we can see, the goal of Donkey.bas is quite simply - or not so simply to avoid the Donkeys. (Laughter.) Okay, well as we can see Donkey.bas is a minute to learn and a lifetime to master. (Laughter, applause.) The full interview is at http://www.microsoft.com/billgates/speeches/2001/06-19teched.asp. The description of the original IBM PC and commentary about it is correct, but it should be noted that this whole system was really a congruence of accidents, not a well-planned system. Intel's 8088/8086 chip was a stopgap solution, rushed to market in about 10 weeks, in order to get a 16-bit toehold in the market while their proper 16-bit chip was developed.

Similarly, the IBM PC was developed in a year's time as a proof of concept (IBM typically took 5 years to bring a product from concept to market.) It was released as a stopgap to get a toehold in the market while the 'real' personal computer was developed for later release. And finally, MS-DOS was an act of desperation by Microsoft. They promised IBM an OS when they had none. They bought QD-DOS from Seattle Computer Products, changed just enough to make it run on the IBM machine and shipped the results. It was just dumb luck (bad luck for the consumer, IMO) that this kluged-together system took off and became so popular that the real devices these were meant to be stopgaps for could never come to market. (The Intel chip that the 8088 was a stopgap for was the iAPX 432, originally to be named the 8800, was released, but it was a commercial failure.

I don't think the intended successors to the PC or DOS ever materialized.). @Phoebus66: In short the IBM hardware and that MS-Dos software were a perfect match that would set te mark on everything that followed in its path: Unvisionary Compartmentalized Brute Force design methodology. The PC is the exact opposite of compartmentalized. The Project Chess team was deliberately organized to be completely open internally, but completely separated from the usual IBM vertical integration. And that's why they designed an open-architecture computer with off-the-shelf parts. And that's why it succeeded. For the rest, sure; as Don Estridge himself put it, 'Many said that there was nothing technologically new in this machine.

That was the best news we could have had; we actually had done what we had set out to do.' IBM's own marketing acknowledged that it was less powerful than or more expensive than most of its established competitors, but it was 'The IBM of personal computers', with all that entails. @David Charlap: the IBM PC was developed in a year's time as a proof of concept (IBM typically took 5 years to bring a product from concept to market.) It was released as a stopgap to get a toehold in the market while the 'real' personal computer was developed for later release. The PC was not intended as a stopgap to get a toehold in the market.

IBM had decided that it was too late to get into the PC market, and it probably wasn't worth it anyway, until Bill Lowe convinced John Opel to give him a chance. It wasn't a proof of concept; Lowe claimed that they really could get to market in a year—and they actually did so. There was no 'real' PC planned to be released later; it was Project Chess or nothing. And the PC ended up being pretty much what Lowe envisioned from the start (well, from the point where they rejected his idea of buying Atari and selling a slightly spiffed-up Atari 800 as an IBM). And finally, MS-DOS was an act of desperation by Microsoft.

They promised IBM an OS when they had none. They bought QD-DOS from Seattle Computer Products, changed just enough to make it run on the IBM machine and shipped the results. Buying 86-DOS (not QD-DOS; that's an entirely different thing—you may be thinking QDOS, the original name for 86-DOS?) wasn't an act of desperation, it was the plan from the start. Bill Gates told IBM about 86-DOS in their contract meeting, suggesting that he could license and port it as a stripped-down CP/M clone that IBM could sell for a lot less than CP/M. And that's exactly what he did.

Pci 8086 Driver Download

And it wasn't a stopgap for a 'real' OS that Microsoft had planned but couldn't get done in time. The real OS already existed—CP/M-86—and it was an option from the day the PC was released, and it had nothing to do with Microsoft.

Ibm 8086 Computer

After a fresh install of Windows 10 Pro 64bit I have one outstanding device that I cannot find the drivers for. In the Device manager it is listing the device as 'PCI Serial Port' with the following hardware ID: PCI VEN8086&DEV1D3D A quick google search shows that this should be handled by the Intel AMT drivers. I downloaded the drivers and did the auto install but it did not resolve the issue. I then found where the installer had extracted the files and tried to do a manual install but again Windows said that it could not find a compatible driver. Does anyone have suggestions for how else I can resolve this issue? I also have a PnP USB audio device that is not working properly, it is also listed in the 'Other Device' section but on other computers it says that a driver is not required. Could this be related to the PCI Serial Port not functioning properly?

Welcome to the forum That's the Serial over LAN device and part of the AMT component as you suspected. Depending on if you have an early or late generation S30, you might have unknowingly grabbed the wrong driver package.

This would cause it not to install correctly. One of these two drivers should work. Extract and install manually from Device Manager. On the PnP USB audio device, can you get a Vendor and Device ID like you did for the PCI Serial Port?

It could be the audio component of your graphics adapter, part of your onboard audio, or a standard USB port that didn't install correctly. If it looks like it might be a standard USB port, try this driver. Thanks a lot! I installed the driver you posted (Intel AMT Driver) and the warning PCI serial port on the Device Manager has disappeared. I would ask you other two questions: the first is.what does this driver do? The second question corcerns another warning I see in the Device Manager about the 'SAS Controller'.

This problem doesn't allow me to see, in the computer resources, one HDD linked to the blue Sata port on the motherboard. How could I resolve the problem? Which is the necessary driver for SAS controller? I think this is the driver for 'serial over LAN'.

It's a function supported by Intel's AMT package for manageability. For SAS support on S30, it's a bit of a tricky solution. Onboard SAS can be supported, but only if you have the proper HDD enablement module installed.

You can check to see if ther's a module installed by looking at the right most DIMM slot towards the bottom of the slot. Just to the right of that is a small header designed to support the HDD enablement module. If you've got a little green PCB installed in that location, then you should have onboard SAS support, meaning the blue SATA ports on the motherboard will support either SATA or SAS. Here's an image showing where this module would be installed on S30.: S30 HDD enablement module install location To utilize these ports, you'll want to make sure you have the Intel RSTe driver package installed on your system.