Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

What if IBM didn't choose the Intel CPU!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    What if IBM didn't choose the Intel CPU!

    Word for thought, useless but hey!

    What "if" IBM Choose the 6502 back then, where would Intel be today? Where would the PC industry have gone, where would the company that held the patents to the 6502 be today?

    Since "most" other computers back then used the 6502 type cpu, if would of been interesting.

    GEEKS WITH A GRUDGE!

    #2
    Hi

    IBM did make a 68000 based PC-like system in the early 1980's

    http://en.wikipedia.org/wiki/IBM_System_9000

    It was a system for lab instrumentation but had a lot of PC characteristics.

    Ironically it has many of the characteristics of a "what if" type IBM system sometimes you hear discussed.

    It used the 68000 CPU with large VERSAbus based boards (the predecessor to VME)

    http://en.wikipedia.org/wiki/Versabus

    I think had IBM pursued a lower cost version of it instead of the PC it would have crushed all competitors including Apple.

    Thanks and have a nice day!

    Andrew Lynch

    Comment


      #3
      Trixter had a good blog post recently on just this subject.

      Comment


        #4
        Motorola couldn't build enough 68000 CPUs to meet the limited volume requirements of Apple, Atari, Commodore, Apollo, etc. I doubt they could have quickly ramped up production to meet the huge numbers of PCs and clones that got sold. A 68000 based IBM Workstation would have been an expensive flop especially in 1981.

        The 8-bit CPUs were by 1981 starting to show their limits. So if IBM used one, the 1984 refresh would have had to use a different CPU architecture just to remain viable. The whole PC -> AT -> 386 progression would not have happened and PC deployment might have stalled when all existing software had to be tossed.

        Comment


          #5
          As used to as we are with Intel pushing the limits of integration, the 68K was a huge gamble using high-density short-channel NMOS (HMOS). I suspect that yields were pretty low and that the usual second-sources weren't ready to take the gamble.

          I think it was WESCON where I got my hands on 68K documentation--this was the same WESCON where TI was giving away samples of the PACE, complete with documentation (Moto wasn't giving away samples of the 68K). Fairchild didn't want to talk to you about the 9440 unless you were in the defense industry, etc. The 8086 and Z8000 had been out for a while and got mostly yawns as being souped-up versions of the 8-bit CPUs.

          The 68K was exciting--large, linear address space, generous in the register department, simple instruction set and--this one got everyone's notice--an asynchronous bus, in addition to "user" and "supervisor" modes of operation. That is, there is a "handshake" between the CPU and addressed devices, including memory. An address must be responded to with an acknowledge that the device being addressed actually existed. No acknowledge--you get a bus error trap on the CPU that throws you into the privileged supervisor mode.

          What this meant was that a device or memory address not present would cause an error exception. Can you say "virtual memory"? One of the most-asked questions at that WESCON was "Can I use this to implement virtual memory?" In other words, if I get a Bus Error interrupt, is there enough information present for me (the supervisor-mode executive) to restart the instruction causing the error if I remedy the error condition?.

          In short, "Can I run Unix on this chip?" (Usually meaning 4BSD) was a big item of interest.

          Sadly, the answer was "not really--there are some instructions (mostly memory-to-memory) that cannot be restarted with the information provided by the BERR interrupt." I think that cost Motorola dearly--and they remedied the situation later in the 68K family. Some vendors (Apple, Apollo) went ahead anyway. Apple simply proscribed use of the instructions that couldn't be restarted; Apollo on their Domain workstations ran two 68000s; one that ran slightly ahead of the other--when the first got a bus error, the condition could be satisfied before the second CPU encountered it. Clever, but expensive.

          The only other plausible contender at the time was National Semiconductor, who contracted out the design of a very advanced CPU, the NS32000 series. But the story was always "Real Soon Now" and the thing missed the boat completely by coming out too late--it later found embedded use in things needing lots of CPU such as laser printers. And National didn't have the best track record for support--it had lost interest in the SC/MP, then the PACE and the new CPU might well be next. NS was always better in the digital world at second-sourcing CPUs.

          Intel, at the time, was involved in its own "Real Soon Now", the IA432--a hugely expensive "next generation" CPU chip set. The 8086 was initially intended only as a stopgap "bridge" product until the really serious people jumped on the 432 bandwagon.

          So when IBM came out with the 9000 lab computer, you could almost taste the hope that the yet-to-be-annouced Personal Computer would use it. But that was extremely unlikely--IBM had already deployed the 8085-based Datamaster systems and the Displaywriter was 8086-based. That the PC would use Intel bits and pieces was never really in doubt--Intel could supply chips in quantity and I suspect IBM got a real sweetheart deal by incorporating other Intel chips in the contract. In fact, the early 5150s didn't use a NEC 765 floppy controller, but rather the Intel labeled clone--the 8272. Intel and NEC were involved in a number of cross-licensing deals--I've heard that Intel couldn't get the 8272 to work and so let NEC complete the job in exchange for manufacturing license for NEC's advanced display controller.

          I don't think that the 6502 was even in the running. How would IBM have competed against the likes of Apple and Atari with yet another 6502 design? In particular, IBM had no interest in developing software for the PC intially. Trot the thing out, make the internals public right from the start; offer development tools and stand back and see what happens.
          Reach me: vcfblackhole _at_ protonmail dot com.

          Comment


            #6
            Yea, the 68010 was specially created to solve the bus error problem. Of course, Intel took a while to create the 80386 to compete (and even longer to create the 386SX), but IMO the real screwup is the reason why it took 10 years after Intel launched the 386 before 32-bit programming became popular.

            Comment


              #7
              Well, there was the 65816, but....

              Comment


                #8
                I remember getting a reaction of utter disgust from an Intel engineer to the effect of "we give you a memory-managed 32-bit state of the art design and the software people piss it all away running DOS".

                I couldn't really argue with him.

                The 65816 didn't come out until too late--1984.
                Reach me: vcfblackhole _at_ protonmail dot com.

                Comment


                  #9
                  Originally posted by Chuck(G) View Post
                  I remember getting a reaction of utter disgust from an Intel engineer to the effect of "we give you a memory-managed 32-bit state of the art design and the software people piss it all away running DOS"..
                  And the sad thing is that it was MS to blame. MS turned what was originally OS/2-386 into an entire fiasco, with it later even attacking 32-bit OS/2 later on, and MS was the one originally shipping the MS OS/2 2.0 SDK to developers back in 1990!

                  Comment


                    #10
                    Yeah, Microsoft really screwed with the OS/2 developers. When the pre-orders (about $3K IIRC, but my mind may be playing tricks) for the new OS/2 SDK came out, Microsoft shipped NT 3.1 SDKs instead, until threatened with a lawsuit to either refund in full or supply the real thing. Almost right up to the day that MS announced NT, BillG was still making smoochies with Cannavino telling the world how committed MS was to OS/2 and how wonderful the world would then be.

                    To their credit, IBM shipped out the new SDK for OS/2 2.0 for just a modest upgrade fee if you already had the 1.x kit.

                    (cf. Section VII of "The OS/2 Notebook", (c) 1990 by Microsoft Press)
                    Reach me: vcfblackhole _at_ protonmail dot com.

                    Comment


                      #11
                      An MC68000 would of made the 5150 far too expensive. A 6502 was a bit of a weakling in IBM's eyes (and for the most part was a "hobbyist" CPU found in inexpensive home computers) but the Zilog Z80 would of been an excellent alternative. Right off the bat they would have CP/M and it's software.
                      Potentially, this could of completely changed history because unless Microsoft ported DOS to the Z80 CP/M would of had the advantage instead of the other way around like it currently is.
                      [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
                      --------------------------------------------------------------------------------------------
                      [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

                      = Excellent space heater

                      Comment


                        #12
                        Originally posted by NeXT View Post
                        ...because unless Microsoft ported DOS to the Z80 CP/M would of had the advantage instead of the other way around like it currently is.
                        ...and you'd be stuck with 16-bit address buses, bankswitching for more memory, small I/O address spaces and a world filled with competitors doing exactly the same thing. Let's not forget that in the early days of DOS, there wasn't a whole heckuva lot of difference between it and CP/M--and in view of CP/M-86, DOS 1 was inferior in API support. Interestingly, if you're running 32-bit Windows, you can still write 16-bit programs that place many system request ordinals in CL and long call location 5 in your TPA, er PSP--just like 8-bit CP/M. CP/M-86 at once went for a program interrupt--and a better choice of one--224. IBM had already done an 8085 box and obviously wasn't convinced that it would capture any market as a home computer.
                        Reach me: vcfblackhole _at_ protonmail dot com.

                        Comment


                          #13
                          Hi
                          IBM was a major chip manufacturer at the time. If they needed to second source the MC68000 from Motorola to meet production demands I am confident they could have negotiated a good deal similar to the one they had with Intel at the time. IBM had enormous resources that dwarfed anything that Apple, Amiga, Atari, Apollo, Sun, etc could ever hope to muster. Production capacity can be ramped up over time with enough resources I think they could have done it easily.

                          Instead of the plodding development of the Intel 8088 -> 80386 with all its broken architecture I think we would have seen an accelerated 68000 to 68020 to 68030 and beyond on a similar time line if not sooner. The key would be adding an MMU into the mix early. The major difference is IBM would have used VERSAbus instead of the awful 8 bit ISA bus on the PC. The next logical progression would have been VME which is highly suited for the MC68000 and a hugely *much* better bus than the 16 bit AT ISA bus ever could hope to achieve. Modern VME bus systems are still in production and with the middle connector are at least comparable to PCI if not better.

                          It is all speculation in any event but I maintain IBM really screwed up by not adopting the 68000 when they had a chance. Put a decent Sys V or BSD derivative OS on it (Xenix or AIX) and it would have smoked any competition. I think IBM lost 10 or more critical years trying to remediate the deep brokenness of the IBM PC legacy architecture. Even today, it's effects are still lingering in the background. We'll probably never be completely free of it unless we migrate to ARM or something equally drastic.

                          Instead Apple semi-led the adoption of the 68000 and so screwed it up with the Mac it basically killed the architecture. I had a bit of hope for them after they fired Jobs and released the Mac II line but they managed to kill that too. And the PPC clones. Its amazing to me Apple is even still in business after the mess they made in the 1990's.

                          Just think, we could have started with 6U chassis VME based 68K CPU boards with full 32 bit support from day one. I think it would have been a better world. Oh well, I guess it was never meant to be.

                          Thanks and have a nice day!

                          Andrew Lynch
                          Last edited by NobodyIsHere; February 24, 2013, 04:32 PM.

                          Comment


                            #14
                            Yea, that was bad enough, but the really bad one (and definitely much worse than the JDA) is the "Microsoft Munchkins" and other unethical attacks on 32-bit OS/2 later on that I mentioned in my blog post.
                            Last edited by yuhong; February 24, 2013, 05:48 PM.

                            Comment


                              #15
                              Originally posted by lynchaj View Post
                              Just think, we could have started with 6U chassis VME based 68K CPU boards with full 32 bit support from day one. I think it would have been a better world. Oh well, I guess it was never meant to be.
                              IBM tried that with the 9000 lab computer. Not a success. Would the potential benefits of 32 bit be worth paying an extra $4,000 in 1982 (basically comparing dual floppy systems with 128kB of RAM roughly $6,000 for a stripped 9000 versus roughly $2,000 for an expanded PC). The magic price point for a PC was $1,000 which would be difficult to achieve as long as Motorola priced the 68000 higher.

                              Comment

                              Working...
                              X