6 ms·
A bit of XENIX history
- CurtHagenlocher 13y ago> Xenix should be the 16-bit “successor” to DOS Shouldn't this be "32-bit"? MS-DOS itself was always 16-bit.
- hapless 13y agoAt the time, DOS and the original (8088) IBM PC primarily competed with 8-bit micros: 8080 systems running CP/M and the 6502-based Apple II. In that context, they were probably talking about the upcoming generation of microcomputers, based around bigger chips: 80286, 68k, etc
- kjs3 13y agoXenix ran on the 8086, FWIW. As I recall, the intent of the statement was the thought on M$ part that users would want a more capable system when the new processors were mainstream and DOS would be retired and replaced with Xenix. Obviously, this didn't pan out.
- akira2501 13y agoThe 8080 had a 16bit address bus, though; which is what I always assumed was meant by referring to a machine by it's "bit count."
- ANTSANTS 13y agoBy that logic, the 6502 is a 16-bit CPU, because it (and just about every other CPU we call 8-bit) has a 16-bit address bus. The 68000 has a 16-bit data bus and ALU, a 24-bit address bus, and 32-bit registers, but is usually considered a 16-bit CPU. I guess for older CPUs, the data bus and the ALU size are the determining factors.
- ja27 13y agoXENIX was my first nix. Back around 1985 my high school had a Tandy TRS80 with the 68000 processor and 6-12 terminals. They used it to replace a Burroughs mini for the COBOL class. I just barely missed punching cards for the Burroughs and instead learned vi and stupid tricks like writing to other users' ttys. I still torment my Microsoftie friends when I remind them that they're the ones that got me started on nix, long before Linux or OSX came around.
- ja27 13y agoMy next phase of using XENIX unfortunately never happened. I ran some version of MINIX on 8088 hardware and would gladly have picked up XENIX if it were available sub-$100 back then. Instead I migrated to DESQview, which amazed me with what it was able to accomplish compared to early Microsoft Windows versions. It wasn't until 386BSD appeared that I ran a unix on home PC hardware again before moving on to the early Linuxes.
- eschaton 13y agoThe TRS-80 Model II/16 or just the Model 16? It shouldn't surprise you that there was also a version of 68000 Xenix for the Lisa.
- ja27 13y agoNot sure. I'm also one of the few that used A/UX on the 68k Macs.
- cstross 13y agoHmm. I joined SCO in early 1991, and one of my first jobs in techpubs was working on documenting compatability between SCO-branded Xenix and SCO's release of SVR3.2 UNIX -- which was able to run binaries compiled for SCO Xenix (unsurprisingly) but offered a bunch of extras. AIUI SCO had been doing a lot of development of Xenix from 1986/87 onwards, when Microsoft made the strategic decision to focus on OS/2 and the successor to DOS. Taking on Xenix was what enabled SCO to grow to a $200M/year turnover multinational in about 5 years; and failing to understand the implications of Linux was probably what killed SCO (or rather, when they finally got it, they split the company and sold the UNIX IP to Caldera, who renamed themselves SCO and attempted to sue the universe) -- the rest is history.
- chollida1 13y ago> Hmm. I joined SCO in early 1991 Meta question, and I'll try to ask it delicately:) I know that you worked for SCO along time ago and its a different company than the one who started the lawsuit, but have you every had anyone refuse to hire you, or even joke about it, because you worked at SCO/had the name SCO on your resume? With the SCO lawsuit a few years back there was an awful lot of vitriol from some people about how they'd never hire someone with SCO on their resume. I'd be curious to know if anyone ever did get black listed due to working at SCO/Caldera.
- deleted 13y ago[deleted]
- jfischer 13y agoHa! Charlie left the software industry and moved to bigger and better things (http://www.antipope.org/charlie/blog-static/fiction/faq.html http://www.antipope.org/charlie/blog-static/fiction/faq.html). He does have some good stories about his days at SCO on his website (e.g. http://www.antipope.org/charlie/blog-static/2009/06/how_i_got_here_in_the_end_part_3.html http://www.antipope.org/charlie/blog-static/2009/06/how_i_go...).
- kjs3 13y agoThe company I started out at wrote the (infamous) C2 subsystem for SCO Unix. Every once in a great while, some elderly neckbeard will give me shit about that. Memories...
- zatkin 13y agoI wonder what would have happened if Xenix was the successor to DOS. We would probably be living in a completely different computing world today.
- kjs3 13y agoI have my doubts M$ was really that keen on that path; after all, there's a lot of stuff in Xenix that M$ wouldn't own and that's always been a problem for Gates and the boys. So OS/2 for a while was the heir apparent, which would have also changed things quite a bit (for good, I think, but many disagree). What we got was stepchild of VMS, which also could have been great, but has wandered off in it's own direction.
- rbanffy 13y agoThe possibility of running Xenix-native binaries elsewhere would negate much of Microsoft's later strategy. Hardware could be a commodity, but software should always be their own.
- deleted 13y ago[deleted]
- bluedino 13y agoHardware was too expensive. By the time RAM/HD/CPU prices became low enough to store and run a UNIX OS, something else would have came along and taken it's place. You could run DOS on a $999 computer, and you could run Windows on a $1999 computer. It took a $4999 computer to run UNIX. That's basically what kept home users on such futile operating systems. That's also what kept Windows NT off peoples desktops until 2000 or so.
- emersonrsantos 13y agoWe had the the SCO Xenix 2.3.4 running the billing system for the water and sewerage company on my hometown (about 100k homes) till the 2000s. The software was written in SGBD (FoxPro-like DB). It was up and running till 1997 on a i386 with 16MB RAM and 1gb SCSI serving dozens of users in various locations via VT100. No TCP/IP stack running, it was not supported by our hardware. I bet lots of companies still has this kind of setup, at least I saw a retailer doing the same setup but running MF Cobol instead of SGBD.
- stevekemp 13y agoI worked for a company, around 2002, that offered a managed billing platform for small mobile-phone operators. That platform was largely built around microfocus COBOL.
- johnpur 13y agoWow, the infamous "merged product"... In '89 I joined MS to run the "LM/X" product, where we extended the Unix networking model to support the SMB protocols. A very interesting time where MS worked with HP to get the kernel and networking changes into the mainline code base while at the same time AT&T was doing their own version. Sun was pushing their implementation of PC NFS, and many interesting "standards" meetings were held. If I remember correctly, the PC networking protocols showed in in XPG4 (X/Open Portability Guide) in 1992.
- ChuckMcM 13y agoI was Intel at the time and when the first pieces of the 80386 came back from the fab functional Intel was scrambling for ways to test it (I was in Systems Validation). We tried running Xenix on it and discovered various places where Microsoft's kernel team had 'cheated' by using reserved bits in various places which just happened to work on the 286. Needless to say it caused quite a commotion :-)
- yuhong 13y agoRemember the 32-bit multiply bug?
- repost 13y agoThat was a blast for from the past - I spent 1986-91 designing serial cards and writing drivers for Xenix systems at Specialix. We had 32 terminals running on 386 Xenix systems, tell that to the kids of today with their Ghz CPU's and fancy VM's and they won't believe you.