Computer History Wiki - User contributions [en]

Netnews archive

2024-06-29T13:17:25Z

Neozeed: update the location to something more like the original. files are still on sourceforge though

[[Image:davidwiseman-tapes.jpg|200px|thumb|right|David Wiseman]]
There is an incredible archive [http://annex.retroarchive.org/utzoo/index.html here] of all the early [[Usenet]] posts from February 1981 until June of 1991.

== Magi's account ==

Magi's NetNews Archive involvement:

: Well, the thank-you's have been rather ebullient all day long today and I feel somewhat embarrassed by the attention. Especially given how long it took us to get the archive on line and visible! It has to be close to 10 years now. Sigh.
: The story is more a story of fits and starts than of resolve. And our contribution accounts for some (most?) of the first 10 years of the Google archive.

: If I recall correctly, the issue of Henry Spencer's (actually, the University of Toronto, Department of Zoology's) NetNews archive was raised at a Usenix conference in the early 90's. The question: can we get at them? Bruce Jones was especially interested in this. Henry's answer was that it really wasn't going to be easy because he had neither the disk space nor the tape drive to pull them all down to make them available.

: I, it turned out, did. So one bright winter day I drove from London (Ontario Canada) to Toronto (Ontario Canada) -- a two hour drive in my shiny new pickup truck and picked up 141 magtapes from the Zoology department at UofT and brought them back to the Department of Computer Science at the University of Western Ontario. (A not unimpressive bandwidth, by the way, of some 18Mb/sec :-) never underestimate the bandwidth of a pickup truck on the highway!)

: Then with the help of several people (some of whom have not yet been credited) we started to pull the data off of the tapes and onto disks in both the Computer Science department and the Robarts Research Institute. Lance Bailey, then with the Robarts Research Institute, did the pulling there and I with assistance from Bob Webber did it at Computer Science. Bruce Jones from UCSD took some vacation time and came up here to help pull data down for a week or so as well.

: But we quickly ran out of space and time: Lance left Robarts for UBC, Bruce's vacation ended, and Bob and I got busy doing other things (like our jobs). As a result, the archive project made very little progress over the next few years.

: Then Brewster Kahle started pushing on us (thanks Brewster!) to get it done. He even bought us a large disk to hold the archive when we truly ran out of space. With the help of Sue Thielen, who was out of work and bored, we got all of the rest of the tapes read down onto that disk. Unfortunately, that disk was not "close enough" to either a tape drive or the ftp server to make the data available to anyone. And it wasn't organized in anyway usefully.

: Brewster pushed very gently for a very long time but the new archive project was far from the top of the list of projects I was supposed to be working on and I just never got it going again.

: Late this summer Michael Schmitt from Google started pushing as well. And as luck would have it, I was able to hire a student to do the final sorting of the archive as well. And, that luck still holding, I managed to "steal" enough space on the ftp server for the entire archive! But it still took months to get that figured out and the archive transferred to a machine from which they pull the archive. It was the middle of October before we were able make the collection available to Google. And it is actually available, although totally unsorted, to anyone who wants it and can deal with pulling some 160 files ranging in size from 1.4Mb to 65Mb. Just drop me a line to say please and we'll arrange to make it visible to you.

: I'd still like to impose a bit more order on the raw archives than we have but the time just hasn't allowed for that...

== Original FTP site header ==

<pre>
230-Yes, you have found the on-line copy of Henry Spencer's UTZOO NetNews
230-Archive.
230-
230-It is not in a very reasonable format but it is all here. There were
230-141 magtapes in the collection and, so far, we have them organized to
230-reflect these tapes. You will find two types of files in this
230-directory:
230
230- newsNNNfM.tgz the archives, tar'd and compressed
230-and newsNNNfM.toc the tables of contents (tar listings)
230-
230-where NNN is the tape number (from 001 to 141)
230-and M is the save set number (from 1 to 3 but usually 1).
230-
230-There is also a file called AllTOC.tgz which is a compressed tar archive
230-containing all of the .toc files.
230-
230-Please note that news001f1.tgz contains A news. All of the other tapes
230-contain B news. The news in this archive was collected between February
230-of 1981 and June of 1991. (The Scavenged.tgz file contains A news articles
230-which were "found" off the end of some of the earlier tapes.)
230-
230-Also below here is an 'info' directory which contains several useful
230-files with "overviews" of some of the archive information. Hopefully
230-the filenames will explain what they are. (I know, probably not.)
230-
230-The 'pc' directory contains Windows code which can unpack .tgz files. I
230-have also been told that the latest versions of WinZip can also read them.
230-
230--- magi
</pre>

== Controversy ==

I just found out that the UTZOO archives have been destroyed. Only 3rd party mirrors exist. What an incredible loss, of nearly 2 decades of written history. Absolutely tragic.

From Archive.org:
<pre>
This is not a collection of the UTZOO Wiseman Usenet Archive.

In 2020 after sustained legal demands requesting a set of messages within the Usenet Archive be redacted, and to avoid further costs and accusations of manipulation should those demands be met, the archive has been removed from this URL and is not currently accessible to the public.

Included in this item is a file listing and the md5 sums of the removed files, for the use of others in verifying they have original materials.
</pre>

{{semi-stub}}

[[Category: Networking]]
[[Category: History]]

F2c

2024-06-20T08:42:38Z

Neozeed:

While not really a compiler, '''f2c''' is based on the [[UNIX]] [[FORTRAN]] compiler, but as it used the same backend as the [[C (language)|C]] compiler, f2c emits C, which in turn can be compiled by the native compiler.

F2C can be downloaded from http://www.netlib.org/f2c/

== Installing ==
F2C will build for MS-DOS (DPMI), Win32, and most UNIX. The biggest issue I've had testing has been the [[DEC Alpha]] because it's floating point seems to be too different.

F2c is somewhat straightforward to install... The two big 'camps' are Unix and Windows.

=== Unix/MinGW ===
For UNIX systems it's easier to install tar.gz's here:
*http://vpsland.superglobalmegacorp.com/install/f2c/f2c.tar.gz
*http://vpsland.superglobalmegacorp.com/install/f2c/libf2c.tar.gz

An additional squashfs backup has been placed on archive.org
*https://archive.org/details/f2c_20240618

Simply extract and run:
<pre>
tar -zxvf f2c.tar.gz
cd f2c
make -f makefile.u f2c
</pre>

Then run:
<pre>
cp f2c /usr/local/bin
cp f2c.h /usr/local/include
</pre>

If all went well you should have a f2c command.

Next you'll need to download and build the IO library

Simply extract and run:
<pre>
tar -zxvf libf2c.tar.gz
cd libf2c
make -f makefile.u
</pre>

Then run:
<pre>
cp libf2c.a /usr/local/lib
</pre>

=== Visual C++/MS-DOS ===
F2c can also be built using Visual C++. The key here is that you'll have to use the .vc makefiles.
For Windows/MS-DOS users it's easier to download these zip files:

*http://vpsland.superglobalmegacorp.com/install/f2c/f2c.zip
*http://vpsland.superglobalmegacorp.com/install/f2c/libf2c.zip

then simply unzip f2c.zip somewhere, then using the CLI tools simply

<pre>
cd f2c
nmake -f makefile.vc f2c.exe
</pre>

This will build the f2c translator. You may wish to copy it somewhere in your path, along with the f2c.h into your include path.

Next is the IO library.

<pre>
nmake -f makefile.vc
</pre>

This will now generate the vcf2c.lib which you'll need to link your programs against.

== Test program ==

Now you should be able to build a simple FORTRAN program like this:

hello.f
<pre>
C1234567890
C Hello world
program hello
print *, 'Hello!'
end

</pre>

Note that you'll need a blank line on the end. This just makes f2c all the happier.

=== Build instructions for Unix ===
Then run:
<pre>
bash-2.01$ f2c hello.f
hello.f:
MAIN hello:
bash-2.01$ cc hello.c -lf2c -o hello
bash-2.01$ file hello
hello: Mach-O executable (for architecture m68k) not stripped
bash-2.01$ ./hello
Hello!
</pre>

=== Build instructions for Windows ===
<pre>
c:\temp\x>f2c\f2c hello.f
hello.f:
MAIN hello:

c:\temp\x>cl hello.c -If2c libf2c\vcf2c.lib
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86
Copyright (C) Microsoft Corporation. All rights reserved.

hello.c
Microsoft (R) Incremental Linker Version 9.00.21022.08
Copyright (C) Microsoft Corporation. All rights reserved.

/out:hello.exe
hello.obj
libf2c\vcf2c.lib

c:\temp\x>hello
Hello!
</pre>

Naturally if you copy the f2c.h file into your include path, and hte vcf2c.lib into your libpath then you won't have to directly path to them.... But I think this should get you going.

== Programs that build with f2c ==
I'm not that big into [[FORTRAN]], but here is a small list of programs that I've built with f2c.

*[[Dungeon]] (version 2.5.6 works great!)
*[[Snoopy Calendar]]

[[Category: Fortran Compilers]]

File:Pharlap-286-retail box.jpg

2024-01-28T20:12:16Z

Neozeed: Found images from a yahoo auction: https://page.auctions.yahoo.co.jp/jp/auction/u1048060130

Found images from a yahoo auction:

https://page.auctions.yahoo.co.jp/jp/auction/u1048060130

286 DOS-Extender

2024-01-28T20:10:19Z

Neozeed: lame inital version

[[Image:Pharlap-286-retail box.jpg|thumb|right|200px|286 retail package]]

The '''286|Dos-Extender''' was a later follow up to the 386 [[DOS extender|MS-DOS extender]] created by [[Phar Lap]].

= Versions =
== 2.5 ==

== 3.x ==
{{stub}}

[[Category: DOS Enhancements]]

PS/2 Model 60 Sales Brochure

2023-08-24T07:43:41Z

Neozeed: more text added, need to remember how to bold, underline and do tables.

[[Image:ps2_model60_brochure_page1.jpg]]

The next generation in personal computing

IBM Personal System/2 Model 60

*A powerful combination of capability and capacity*

IBM Personal System/2 Model 60 combines high performance with high capacity, making it an excellent choice for anyone
who manages large amounts of information, big projects or tight schedules.

In a systems network setting, this model can be used to share files and programs and provide rapid communications.
No matter how much there is to do, everyone can work at peak efficiency.

Here are just a few ways Model 60 can work for you and your business.

Manage more in less time. Model 60's Micro Channel architecture, fast 80286 microprocessor and 1Mb memory are the right combination to cut through big processing jobs in a hurry. And this model offers large — and expandable — fixed-disk storage to match its powerful performance.

Make Model 60 your network workhorse. When used with the new IBM Operating System/2, Model 60 will support advanced applications, multiple applications and a large number of peripheral devices. So you can use it for such important tasks as spreadsheet processing and data base management.

Or use it as a file and print server or communications gateway. However or wherever you put Model 60 to work, you can count on it to pull an impressive share of the load.

*Highlights*

Model 60 is available with a 44Mb or 70Mb fixed disk. Whichever you choose, you'll be getting a system that offers advanced features and functions to meet today’s requirements... and tomorrow's demands

New Micro Channel architecture provides wide data paths for fast processing and communications. It accounts for this system's balanced performance — even when supporting multiple tasks and input/output operations.

80286 microprocessor works at high speeds to help you complete large jobs quickly. For even greater calculation speed, an optional IBM 80287 Math Co-Processor can be installed,

1Mb user memory (expandable to 15Mb with memory expansion options) supplies workspace for advanced applications — even multiple applications — and volumes of data.

Integrated functions give you significant capability from the start. Model 60 comes ready with advanced colour and graphics capabilities, plus built-in support for your display, printer, keyboard even for a modem or mouse. And because all these features are built in, not added on at extra cost, you get more for your money and a system that's reliable, too.

Built-in Video Graphics Array (VGA) capabilities provide video-like clarity and detail for your graphics and text. These
advanced capabilities result in a screen image that's brilliant and natural-looking. VGA also supports CGA, EGA, and MCGA graphics and text.

A palette of over 256,000 colours plus, 64 shades of grey provides a wide spectrum to work with. You can view up to 256 colours at a time — and colours automatically convert to grey on a monochrome display. There's almost no limit to the contrast and shading you'll be able to create and view on-screen.

44Mb, 70Mb and optional 115Mb fixed disks provide ready-access storage for large files and applications, even elaborate data bases.

= page 2 =

1.44Mb diskette drive lots you easily load files and programs stored on the 90mm [35-inch] diskettes used with Model 60. Compact and durable, each high-density diskett can hold as many as 720 pages’ of information.

Seven available expansion slots make it easy to add more functions to Model 60 to keep pace with changing needs.

“Switchless setup” means all you do is install your options, plug in your system, and begin.

Four superior analogue displays offer you a choice of price and function, and bring the built-in colour graphics
capabilities of Model 60 into clear focus. Whether you need crisp text or vivid, detailed colour graphics, you'll find the right display to suit your work and your budget

Wide range of communications options lets you connect Model 60 in a variety of local area networks and access the power of many larger systems.

*What you get*
IBM Personal System/2 Model 60 is packaged in two cartons, one containing the system unit. The other contains:

* One-page customer setup sheet
* System unit power cord
* Keyboard and cable
* Quick Reference manual
* System Reference diskette with tutorial
* Technical Directory

*Options*

Model 60 supports a wide array of optional devices, including many of the peripherals currently available for IBM Personal Computers. What follows is a listing of some of the new options available for Model 60:

* IGM Personal System/2 80287 Math Co-Processor (10MHz)
* IBM 80286 Memory Expansion Option
* IBM 80286 Memory Expansion Kit
* IBM Personal System/2 Mouse
* 44Mb, 70Mb and 115Mb Fixed Disk Options
* IBM Personal System/2 5.25" External Diskette Drive
* IBM Personal System/2 Data Migration Facility Adapter
* IBM 3363 Optical Disk Storage Unit
* IBM Dual Async Adapter/A
* IBM Multi-Protocol Adapter/A
* IBM 3270 Connection
* System 36/38 Workstation Emulation Adapter
* IBM Token-Ring Network Adapter/A
* IBM PC Network Adapter II/A
* IBM PC Network Baseband Adapter/A
* IBM Personal System/2 3117 Adapter/A
* IBM Personal System/2 High Speed Adapter/A

*Warranty/Service*

Every IBM product is built to meet high standards of quality and reliability, So you can count on Model 60 to perform smoothly year after year.

Model 60 is backed by a one year limited warranty, and extended warranty terms are available from IBM and IBM Authorised Dealers.

With an IBM Maintenance Agreement, you can arrange for on-site service.

Personal System/2, Operating Systern/2, Micro Channel, Quiet writer and Proprinter are trademarks of International
Business Machines Corporation.

A4 size [8 1/2 11°] double spaced, typewritien pages

IBM Personal System/2 Model 60 at a glance

Microprocessor

Permanent memory
(ROM)
Memory (RAM)

Integrated functions

Text/graphics
support

New display
modes

Dimensions

Auxiliary storage

Power supply

80286, 10 MHz
Optional: 18M 80287 Math
Co-Processor (10 MHz)

128Kb standard

1Mb standard, expandable to 15Mb with
memory expansion options

Video Graphics Array (VGA) and display
port, serial port, parallel port, pointing
device port, keyboard port and diskette
controller

VGA supports existing colour graphics
modes and provides up to 256 colours
(trom a palette of over 256,000) and 64
shades of grey (monochrome)

320 x 200 pels x 256 colours ~ all
points addressable

640 x 480 pels x 16 colours — all points
addressable

9 x 16 character box — 16 colours (text)
Approx. 597mm H x 166mm W =
482mm D [23.5" « 6.5" x 19°]

Model 60-041: one 1.44Mb 90mm [3.5-
inch} diskette drive and a 44Mb fixed
disk standard; additional 44Mb fixed disk
‘optional

Model 60-071: one 1.44Mb 90mm [3.5-
inch] diskette drive and a 70Mb fixed
disk standard; additional 70Mb or 115Mb
fixed disk optional

Also optional: either a second 1.44Mb
diskette drive or 5.25" External Diskette
Drive; 3363 Optical Disk Storage Unit
‘Seven available expansion slots

101 keys, including 12 function keys, 3
lighted mode indicators; 3-metre [9-foot]
coiled cable

207-watt (Model 60-041) or 225-watt
(Model 60-071) worldwide autosensing

IBM Token-Ring Network Adapter/A, IBM
PC Network Adapter Il/A, IBM PC Network
Baseband Adapter/A, IBM 3270
Connection, System 36/38

Workstation Emulation Adapter, IBM
‘Dual Async Adapter/A, IBM Multi-Protocol

--
IBM is a registered trademark of the
International Business Machines Corporation.

All specifications subject to change without notice.

References in this publication to IBM products, programs or services do not imply that IBM intendes to make these available in all countries in which IBM operates.

All rights reserved.

IBM Australia (Incorporated in NSW)
Coonara Avenue, West Pennant Hills, NSW 2120.

Order number: G617-4128

PS/2 Model 60 Sales Brochure

2023-08-24T07:30:04Z

Neozeed: slightly better ocr

PS/2 Model 60 Sales Brochure

2023-08-24T07:18:42Z

Neozeed: lame inital with poor orc

[[Image:ps2_model60_brochure_page1.jpg]]

The next generation in personal computing

IBM Personal System/2 Model 60

A powerful combination of capability and capacity

IBM Personal System/2 Model 60 combines high performance with high capacity, making it an excellent choice for anyone
who manages large amounts of information, big projects or tight schedules.

In a systems network setting , this model can be used
to share files and
programs and provide communications
fast. Whatever
task to accomplish, everyone can work
with maximum efficiency.
Here are some ways the
model 60 can work for
you and your business.
Manage more in less time.
The Micro Channel architecture of the
model 60, the microprocessor
80286 fast and the memory of
1 MB make up the combination
ideal for quickly accomplishing
heavy processing work.
And this model offers storage on
large and expandable fixed disk
to match its powerful
performance.
Make the Model 60 your horse of
network battle. When used
with the new IBM Operating System/
2, the 60 model will support
advanced apps,
several applications and a large
number of devices. YOU
so can use it for tasks
as important as the
spreadsheet processing and
database management.
Or use it as a file server
and printing or as a gateway
Communication. Whatever
how you use the 60 model, you
You can count on him to shoot
an impressive share of the load.
Strong points:
Model 60 is available with
a fixed disk of 44 MB or 70
Mo. Whichever you choose, you
get a system that offers
characteristics and
advanced functions to meet
according to the requirements
today... and tomorrow.
The new Micro architecture
Channel offers wide paths of
data for processing and
fast communications. He
represents balanced performance
of this system, even
when taking on multiple tasks
and input/output operations.
The 80286 microprocessor works
at high speeds to help you
to get the job done quickly
bulky. For a calculation speed
even higher, a coprocessor
optional IBM 80287 math can
be installed.
1 MB user memory
(expandable up to 15 MB with
memory expansion options).
application workspace
advanced, even for several
applications and volumes of
data.
Built-in functions give you
significant capacities from the
departure. Model 60 comes with
color and graphics capabilities
advances, as well as a grip
integrated support for your
screen, printer, keyboard - even
for a modem or a mouse. And
like all these features
are integrated and not
added at an additional cost,
you get more for your money
and an equally reliable system.
VGA (Video Graphics) capabilities
Array) integrated provide clarity
and details similar to those of a
video for your graphics and your
text. These advanced capabilities allow
to get an image on the screen
shiny and natural. VGA also supports
supports graphics and
CGA, EGA and MCGA text.
A pallet of more than 256,000
colors and 64 shades of gray
offers a broad spectrum with which
to work. You can display up to
256 colors at a time and the
colors are automatically
converted to gray on a screen
monochrome. There is almost
no limit to contrast
and to the shadows that you
you can create and view on screen.
IBM
Fixed disks of 44 MB, 70 MB and
115MB optional provide storage
easily accessible for
large files and applications, even
for elaborate databases.

File:Ps2 model60 brochure page2.jpg

2023-08-24T07:14:54Z

Neozeed:

File:Ps2 model60 brochure page1.jpg

2023-08-24T07:14:29Z

Neozeed: Order number: G617-4128

Order number: G617-4128

PS/2 model 60

2023-08-24T07:12:25Z

Neozeed: minor stuff

{{Infobox Machine
| name = IBM PS/2 model 60
| manufacturer = [[IBM]]
| image = ps2-60.jpg
| caption = An IBM PS/2 model 60
| word size = 16 bit
| year introduced = 1987
}}

This was a tower [[i286]] computer with [[MCA]] slots. Outwards it was identical to the [[PS/2 model 80]]. The model 60 & 80 had enough room for 2 5 1/4" Full Height hard disks, and two floppy drives. The model 60 included 7 MCA slots, and a special video slot.

Reference disks for this model can be found [http://ps2page.tripod.com/ps2files/85xxref.htm here].

= Models =
The PS/2 Model 60 came in two variants:

* MFM
* ESDI

[[PS/2 Model 60 Sales Brochure]]

{{stub}}
[[Category:PS/2 machines]]

386 DOS-Extender

2023-06-19T22:23:55Z

Neozeed: re-org, rename links

[[Image:Pharlap-386-Programmers-guide-to-DPMI-and-windows.jpg|thumb|right|200px|Old Manual]]

The '''386|Dos-Extender''' was the first real [[DOS extender|MS-DOS extender]] created by [[Phar Lap]].

By using special [[compiler]]s [[Watcom C]] 386, and HighC 386 you could create a 32-bit [[program]] that would run on an unmodified [[MS-DOS]] system equipped with a [[Intel 80386|386]] [[CPU]]. It was significantly easier to deploy 386 extended [[application]]s, however it did carry a significant price tag, compared to deploying [[OS/2 2.0]], although it was much more simpler.

= Versions =
== 4.1 ==
A copy of the 4.1 SDK as been scanned and placed on archive.org! You can find it [https://archive.org/details/phar-lap-386-dox-extender-4.1-sdk here].

Documents include:
* [https://archive.org/details/386-dosx-installation-instructions 386|DOS-Extender Installation Instructions]
* [https://archive.org/details/386-vmm-installation-instructions 386|VMM Installation Instructions]

* [https://archive.org/details/386-asm 386|ASM Reference Manual]
* [https://archive.org/details/386-debug 386|DEBUG Reference Manual]
* [https://archive.org/details/386-dosx 386|DOS Extender Reference Manual]
* [https://archive.org/details/386-link 386|LINK Reference Manual]
* [https://archive.org/details/386-vmm 386|VMM Reference Manual]

* [https://archive.org/details/386-lib 386|LIB Utility Guide]

* [https://archive.org/details/386-asm-reference-card 386|ASM Reference Card]
* [https://archive.org/details/386-debug-reference-card 386|DEBUG Reference Card]
* [https://archive.org/details/386-dosx-reference-card 386|DOS-Extender Reference Card]
* [https://archive.org/details/386-link-reference-card 386|LINK Reference Card]

* [https://archive.org/details/386-asm-release-notes-41 386|ASM Release Notes 4.1]
* [https://archive.org/details/386-debug-release-notes-41 386|DEBUG Release Notes 4.1]
* [https://archive.org/details/386-dosx-release-notes-41 386|DOS-Extender Release Notes 4.1]

* [https://archive.org/details/cfig-386 CFIG386 Utility Guide]

== 5.x ==
== 6.x ==

{{stub}}

[[Category: DOS Enhancements]]

386 DOS-Extender

2023-06-19T22:18:06Z

Neozeed: add in some links for 4.1

[[Image:Pharlap-386-Programmers-guide-to-DPMI-and-windows.jpg|thumb|right|200px|Old Manual]]

The '''386|Dos-Extender''' was the first real [[DOS extender|MS-DOS extender]] created by [[Phar Lap]].

By using special [[compiler]]s [[Watcom C]] 386, and HighC 386 you could create a 32-bit [[program]] that would run on an unmodified [[MS-DOS]] system equipped with a [[Intel 80386|386]] [[CPU]]. It was significantly easier to deploy 386 extended [[application]]s, however it did carry a significant price tag, compared to deploying [[OS/2 2.0]], although it was much more simpler.

= Versions =
== 4.1 ==
A copy of the 4.1 SDK as been scanned and placed on archive.org! You can find it [https://archive.org/details/phar-lap-386-dox-extender-4.1-sdk here].

Documents include:
* [https://archive.org/details/386-asm 386-asm]
* [https://archive.org/details/386-asm-reference-card 386-asm-reference-card]
* [https://archive.org/details/386-asm-release-notes-41 386-asm-release-notes-41]
* [https://archive.org/details/386-debug 386-debug]
* [https://archive.org/details/386-debug-reference-card 386-debug-reference-card]
* [https://archive.org/details/386-debug-release-notes-41 386-debug-release-notes-41]
* [https://archive.org/details/386-dosx 386-dosx]
* [https://archive.org/details/386-dosx-installation-instructions 386-dosx-installation-instructions]
* [https://archive.org/details/386-dosx-reference-card 386-dosx-reference-card]
* [https://archive.org/details/386-dosx-release-notes-41 386-dosx-release-notes-41]
* [https://archive.org/details/386-lib 386-lib]
* [https://archive.org/details/386-link 386-link]
* [https://archive.org/details/386-link-reference-card 386-link-reference-card]
* [https://archive.org/details/386-vmm 386-vmm]
* [https://archive.org/details/386-vmm-installation-instructions 386-vmm-installation-instructions]
* [https://archive.org/details/cfig-386 cfig-386]

== 5.x ==
== 6.x ==

{{stub}}

[[Category: DOS Enhancements]]

Installing Windows NT 3.1 on Qemu-legacy

2023-06-09T09:22:38Z

Neozeed: update some links to archive.org

Installing Windows NT 3.1 on Qemu

[[Image:Windows NT 3.1 on Qemu.jpg|300px|thumb|right|Windows NT 3.1 running on Qemu]]

This page is basically obsolete by the newer versions of Qemu, along with better drivers I've found. But for old schoolers I'm leaving this here. Modern 0.14.0 users will want [[Installing Windows NT 3.1 on Qemu]].

Windows NT 3.1 will install, however it does not have PCI support so you'll be restricted to the ISA machine. Also NT 3.1 cannot drive IDE CD-ROM's. So you would have to follow the network installation guide.

== CPU TYPE ==
When NT 3.1 was released pentium CPU's were still beta, and the cpuid thing had not been finalized enough in the install script.

Newer versions of Qemu (0.12.3 tested) you can simply use the flag:
<pre>
-cpu pentium
</pre>

And you can install without having to do anything with the inf files.

Otherwise you will have to fix the setup.inf script to always install the 486 path.

You need to edit a string in the files INITIAL.IN_ and SETUP.IN_

Open each one in notepad and search for:
[ProcessorVar]

Then change the string below it from

STF_PROCESSOR = "" ? $(!LIBHANDLE) GetProcessor

to

STF_PROCESSOR = $(ProcessorID_I586)

== MS-DOS prepare ==

You'll have no choice but to have a MS-DOS Qemu VM installed & operational to start a Windows NT 3.1 installation. Start with the [[Installing MS-DOS on Qemu]] tutorial, then come back here.

With MS-DOS installed and able to access a CD-ROM, you will need a blank floppy image, in addition to either an ISO image with NT 3.1 or a 3.1 CD-ROM.

I'll be using my physical NT 3.1 CD with WIN32 SDK, and Qemu 0.10.5 which will allow me to set my cpu to an Intel Pentium CPU so I won't have to worry about the inf files.

<pre>
qemu -L . -cpu pentium -hda windowsnt31.disk -cdrom \\.\d: -fda nt31boot.vfd
</pre>

The first thing in MS-DOS I'm going to do is format the floppy to make sure it's blank to appease the installer.

<pre>
format a:
</pre>

Then change to the cdrom & run winnt.exe...

<pre>
d:
cd i386
winnt /F /C
</pre>

I'm going to skip the verifies for disk space & floppy writes.. When setup has completed it's job exit Qemu, and this would make a great time to boot back into MS-DOS, and alter the setup.inf & initial.inf files as mentioned above. You may have to expand them manually but it's really not that hard.

== Install ==

Run it like this:

<pre>
qemu -L . -cpu pentium -hda windowsnt31.disk -M isapc -fda nt31boot.vfd -boot a
</pre>

Windows NT will boot from the floppy, and it will naturally detect NO SCSI drivers. I recommend changing the mouse to the "Microsoft Mouse Port Mouse (including BallPoint)" driver. It will then go thru the motion of copying files (yet again) and then it'll prompt to reboot. Quit Qemu as we won't need the floppy now.

<pre>
qemu -L . -hda windowsnt31.disk -cpu pentium -M isapc -net nic -net user -soundhw sb16,adlib
</pre>

And we'll be into the GUI phase of the install.

Remember the ne2000 nic is 0x300 IRQ 2/9. Also you'll want to load it for TCP/IP, drop the NetBEUI, and configure the TCP/IP as follows:

*ADDRESS 10.0.2.15
*MASK 255.255.255.0
*GATEWAY 10.0.2.2
*DNS 10.0.2.3

The soundblaster can be configured, the port is 220, and the IRQ is 5.

== Where to go from here ==

Well Windows NT 3.1 is more of a landmark for Microsoft's first homegrown 32bit OS, and at the same point it's interesting how much it's changed, and how little in some other ways. I would however recommand getting service pack 3 for NT 3.1

You can download it from [https://archive.org/download/windows-nt-3.1-files-from-vpsland/WindowsNT%203.1%20servicepack%203%20i386.zip here]. You'll have to get creative with either MS-DOS & CD-ROM images to copy it in there, or some other method..

16 bit versions of Netscape *WILL* run on NT 3.1!
There is a nice little cache here: http://ftp.lanet.lv/ftp/windows/www/netscape3.0/?C=M;O=A

I recommend the [http://ftp.lanet.lv/ftp/windows/www/netscape3.0/n16e301p.exe n16e301p.exe]. You can install Video for windows after 'fixing' the setup program to not abort on NT 3.1 but it won't run correctly, nor will [[cooltalk]] run correctly.

By default Windows NT 3.1 will only detect 64MB of ram. This is a 'fault' of ntdetect.com & ntldr. You can however download servicepack 5 for Windows NT 3.51, and copy it's ntdetect.com/ntldr to see up to 3GB of ram! You can download service pack 5 right [http://vpsland.superglobalmegacorp.com/install/WindowsNT3.51/sp5_351i.exe here]. I recommend using Netscape from within NT 3.1. Make sure you have installed service pack 3 for NT 3.1 before you do this!!

If you have access to Visual C++ 1.0 32bit you'll be in luck as you can rebuild a few things. In the transition from 3.1 to 3.5 the executable format changed.. You'll find that plenty of cli utilities will NOT run on 3.1.

You may also want to grab a copy of the Windows NT 3.1 resource kit: https://archive.org/download/windows-nt-3.1-files-from-vpsland/Resource%20Kits/

And for anyone interested you'll want to read [http://support.microsoft.com/kb/108581 this] MS article on how to configure the POSIX subsystem to run [[vi]] correctly.

== Qemu 0.12.4 ==

The latest version of Qemu (and I think all of the 12.x line) do *NOT* have a working ISAMACHINE mode for some reason. However for the sake of NT 3.1, I've been able to run it under the PCI machine, however by default there is something (I don't know what) conflicting on IRQ 9 with the 'first' NE2000 adapter.

Simply modify the file pc.c, and look for the following

<blockquote>
static const int ne2000_io[NE2000_NB_MAX] = { 0x300, 0x320, 0x340, 0x360,
0x280, 0x380 };
static const int ne2000_irq[NE2000_NB_MAX] = { 9, 10, 11, 3, 4, 5 };
</blockquote>

And change that to

<blockquote>
static const int ne2000_io[NE2000_NB_MAX] = { 0x320, 0x340, 0x360,
0x280, 0x380 };
static const int ne2000_irq[NE2000_NB_MAX] = { 10, 11, 3, 4, 5 };
</blockquote>

And you'll be good to go.

[[Category:QEMU Tutorials]] [[Category:Qemu]]

Installing Windows NT 3.1 on Qemu

2023-06-09T09:21:19Z

Neozeed: update download links

Installing Windows NT 3.1 on Qemu

[[Image:Windows NT 3.1 on Qemu.jpg|300px|thumb|right|Windows NT 3.1 running on Qemu]]

*For the older and somewhat relevant information see [[Installing Windows NT 3.1 on Qemu-legacy]].

Windows NT 3.1 will install, however it is incompatible with IDE CD-ROM's. This is simply because they did not exist at the time. So you would have to follow the network installation guide. You will also want the [https://archive.org/download/windows-nt-3.1-files-from-vpsland/pcnet.7z AMD Pcnet] driver, which is vastly better then the old legacy NE2000.

== CPU TYPE ==
When NT 3.1 was released pentium CPU's were still beta, and the cpuid thing had not been finalized enough in the install script. So as a precaution we will need to flag the 486 cpu type.

== MS-DOS prepare ==

You'll have no choice but to have a MS-DOS Qemu VM installed & operational to start a Windows NT 3.1 installation. Start with the [[Installing MS-DOS on Qemu]] tutorial, then come back here.

With MS-DOS installed and able to access a CD-ROM, you will need a blank floppy image, in addition to either an ISO image with NT 3.1 or a 3.1 CD-ROM.

I'll be using my physical NT 3.1 CD with WIN32 SDK, and Qemu 0.10.5 which will allow me to set my cpu to an Intel Pentium CPU so I won't have to worry about the inf files.

<pre>
qemu.exe -L pc-bios -cpu 486 -m 64 -hda nt31.disk -net nic,model=pcnet -net user -fda nt31.vfd -cdrom \\.\d: -fda nt31boot.vfd
</pre>

The first thing in MS-DOS I'm going to do is format the floppy to make sure it's blank to appease the installer.

<pre>
format a:
</pre>

Then change to the cdrom & run winnt.exe...

<pre>
d:
cd i386
winnt /F /C
</pre>

I'm going to skip the verifies for disk space & floppy writes.. When setup has completed it's job exit Qemu, and this would make a great time to boot back into MS-DOS, and alter the setup.inf & initial.inf files as mentioned above. You may have to expand them manually but it's really not that hard.

== Install ==

Run it like this:

<pre>
qemu.exe -L pc-bios -cpu 486 -m 64 -hda nt31.disk -net nic,model=pcnet -net user -soundhw sb16,adlib -fda nt31boot.vfd -boot a
</pre>

Windows NT will boot from the floppy, and it will naturally detect NO SCSI drivers. I recommend changing the mouse to the "Microsoft Mouse Port Mouse (including BallPoint)" driver. It will then go thru the motion of copying files (yet again) and then it'll prompt to reboot. Quit Qemu as we won't need the floppy now.

<pre>
qemu.exe -L pc-bios -cpu 486 -m 64 -hda nt31.disk -net nic,model=pcnet -net user -soundhw sb16,adlib -fda pcnet.vfd
</pre>

And we'll be into the GUI phase of the install. Since we've got an AMD PCnet driver in the floppy drive we can do the network setup. Remember the AMDPcnet will need its driver installed from "A:\WINNT" ... Also you'll want to load it for TCP/IP, drop the NetBEUI, and configure the TCP/IP as follows:

*ADDRESS 10.0.2.15
*MASK 255.255.255.0
*GATEWAY 10.0.2.2
*DNS 10.0.2.3

The soundblaster can be configured, the port is 220, and the IRQ is 5.

The install will probably want to format your pcnet disk as an emergency disk, it doesn't matter at this point, and worst case you can always re extract your driver disk if you reinstall.

== Logging on for the first time ==
This is a little tricky on Qemu, as you have to do the following to simulate a CAD

CONTROL+ALT+2
sendkey ctrl-alt-delete
CONTROL+ALT+1

And now you should have the logon prompt.

You may want to setup an autologon via the registry. You can find more information via [http://support.microsoft.com/kb/97597 kb97597].

== Where to go from here ==

Well Windows NT 3.1 is more of a landmark for Microsoft's first homegrown 32bit OS, and at the same point it's interesting how much it's changed, and how little in some other ways. I would however recommand getting service pack 3 for NT 3.1

You can download it from [https://archive.org/download/windows-nt-3.1-files-from-vpsland/WindowsNT%203.1%20servicepack%203%20i386.zip here]. You'll have to get creative with either MS-DOS & CD-ROM images to copy it in there, or some other method..

16 bit versions of Netscape *WILL* run on NT 3.1!
There is a nice little cache [http://ftp.lanet.lv/ftp/windows/www/netscape3.0/?C=M;O=A here]:

I recommend the [http://ftp.lanet.lv/ftp/windows/www/netscape3.0/n16e301p.exe n16e301p.exe]. You can install Video for windows after 'fixing' the setup program to not abort on NT 3.1 but it won't run correctly, nor will [[cooltalk]] run correctly.

By default Windows NT 3.1 will only detect 64MB of ram. This is a 'fault' of ntdetect.com & ntldr. You can however download servicepack 5 for Windows NT 3.51, and copy it's ntdetect.com/ntldr to see up to 3GB of ram! You can download service pack 5 right [http://vpsland.superglobalmegacorp.com/install/WindowsNT3.51/sp5_351i.exe here]. I recommend using Netscape from within NT 3.1. Make sure you have installed service pack 3 for NT 3.1 before you do this!!

If you have access to [[Visual C++ 1.1]] or the [[Windows NT 3.1 SDK]] you'll be in luck as you can rebuild a few things. In the transition from 3.1 to 3.5 the executable format changed.. You'll find that plenty of cli utilities will NOT run on 3.1.

You may also want to grab a copy of the Windows NT 3.1 resource kit [https://archive.org/download/windows-nt-3.1-files-from-vpsland/Resource%20Kits/ here]:

And for anyone interested you'll want to read [http://support.microsoft.com/kb/108581 this] MS article on how to configure the POSIX subsystem to run [[vi]] correctly.

[[Category:QEMU Tutorials]] [[Category:Qemu]]

Talk:ITU V.35 serial line interface

2023-05-18T06:34:23Z

Neozeed: Created page with "Wonder if it's worth mentioning that you have to screw in both sides at the same time.. or all the various adapters and stuff as manufacturers didn't like the giant cables....."

Wonder if it's worth mentioning that you have to screw in both sides at the same time.. or all the various adapters and stuff as manufacturers didn't like the giant cables..

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 08:34, 18 May 2023 (CEST)

Installing Windows 95 on Qemu

2023-01-20T23:27:49Z

Neozeed: uploaded the files to archive.org for better safe keeping.

First of all [[Windows 95]] will run on Qemu.. Yes even the hokey Windows 95a. However the PCI support from the first version of Windows 95 is.. not all that good. Prepare for hell.

For what it's worth, I find that Qemu 0.90 is the best overall version of Qemu.. 0.10.5 will 'work' but don't be surprsed if the sound doesn't work 100%... And there are MASSIVE pauses while the disk image expands...

[[Image:Windows 95a (Japanese) on Qemu.jpg|600px|thumb|right|Windows 95 Japanese running on Qemu]]

== Requirements ==

I've found that you really need four key things for a good Qemu Windows 95 system:

*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/infinst_enu.exe Intel PCI drivers for 95]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/VBE9X.zip VBEMP video driver for 95]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/win95-8029(506).exe 8029 NIC driver for 95]
*mkisofs for building an install CD with tools..

Optional would be Internet Explorer 5.5sp2.. which is the last version to run on Windows 95.

== Rough guide ISA ==

The first thing I did was to grab a bootdisk & make sure I could fdisk/format the hard disk & mount a CD-ROM.. Now if you don't have a good bootdisk for MS-DOS or an MS-DOS intall set, I'd recommend [http://www.bootdisk.com bootdisk.com]

I'm using a real CD-ROM with Windows 95.. It's the 'upgrade' version so there is a little hackery to get around installing Windows 3.1..

The first thing you'll need to do is create a virtual hard disk. Because Windows 95 is a fat16 OS you can only have 2GB max partitions.. So I just create a 2gb disk.. I think the 'minimum' you would want would be 200MB..

<pre>
qemu-img create -f qcow win95.disk 2G
</pre>

Anyways for the first boot on Qemu 0.10.5 it looks like this:

<pre>
qemu -L . -hda win95.disk -m 32 -M isapc -cdrom \\.\d: -fda bootfloppy.vfd -boot a
</pre>

This will create & run a Windows 95 ISA machine, mount the physical CD-ROM and boot from the 'floppy'. From here you'll want to fdisk & format the hard drive.. It's not that hard with MS-DOS 6.22 as it'll want to just do it (keep hitting 1!)..

From the it will want to reboot, and you can format the hard disk....

<pre>
format c: /s/u/v:hard_disk/q
</pre>

Now with the disk formatted, I'm going to 'assume' your boot disk can read the CD-ROM.. I prep a fake windows 3.1 directory, and then copy the install files to the hard disk...

<pre>
c:
cd \
md install
cd install
md win95
cd win95
copy d:\win95\*.* .
cd \
md win
cd win
dir > win.com
md system
cd system
dir > win386.exe
</pre>

Ok, now from here I'd close Qemu, and start it up like this:
<pre>
qemu -L . -hda win95.disk -m 32 -M isapc -soundhw sb16 -vga std
</pre>

This forces the virtual machine to have a Soundblaster 16 & standard VGA. The cirrus drivers in Windows 95a will *NOT* work with Qemu... Also we are still going to install this as an ISA computer. Once MS-DOS has done it's quick boot (no config.sys/autoexec.bat) we go ahead and run windows setup.
<pre>
cd install\win95
setup
</pre>

From here the setup program will start to copy files, and then prompt you that it wants to check for a previous windows install.. It'll find the 'stub' windows and then prompt for a new install in the C:\windows direcotory. So far so good. From here I usually modify the hardware myself, unselect all network cards, scsi cards, remove the video except for the standard VGA adapter, remove all audio cards, and select only the soundblaster, and let it do it's thing.

Then it will reboot the VM a few times, ask about printers, and whatnot.. Then you will have a running Windows 95 machine on ISA hardware. From here I'd recommend you shut down the VM, and backup the disk image.. This way you have something to fallback on that will boot, because from here the PCI 'upgrade' gets trickey.

== PCI phase ==

This phase is trickey as you have to do a lot of foot work, but I find the PCI stuff works better then ISA... And I like SVGA not 16 colors..

=== Creating an update CDROM ===

In a directory with the NIC driver, PCI drivers & Internet explorer you'll need to run mkisofs. It's somewhat simple just use something like this:

<pre>
..\mkisofs.exe -o ..\update.iso -J -r -v -V 95up_disk .
</pre>

=== Starting the updates ===
Ok with your disk image backed up, it's time to start the PCI fun. We now run Qemu like this:

<pre>
qemu -L . -hda win95.disk -soundhw sb16 -M pc -m 32 -vga std -cdrom update.iso
</pre>

On the first boot nothing will have changed, you've got to kick in the hardware detection in the control panel to get Windows 95 to realize you are on a PCI machine now. From here it will go crazy installing device drivers for all kinds of things. And it will want to reboot a few times. I interuppeted it on the 3rd reboot about the fifo IDE stuff... I just hit cancel until the explorer window opened up. Once you can get to explorer it's time to run the Intel PCI updates for Windows 95.

==== PCI driver ====

This should be run first, it's called infinst_enu.exe . You HAVE to have gotten Windows 95 to do some PCI detection ahead of time, otherwise the driver will say there is NO PCI chipsets in the system. And yes most devices will not work until you've run this update.. It's annoying. Run the utility, let it do it's thing and it'll reboot a few times. Now you should have the PCI stuff running. If the video prompts for a driver you should just ignore it for now.

==== Video driver ====

Next I just opened up the hardware manager, and pointed the video card to the 'new' driver located on the CD in VBE9X\UNI .. After installing the driver, and a reboot the VGA card was 'still in the way'. Simply open up the hardware manager and remove the VGA card, and reboot and it'll now be running the new SVGA / VESA driver. The only 'issue' I've had with this driver is that MS-DOS prompts seem to corrupt the screen... alt+enter seems to 'fix' it..

==== Network driver ====

The network driver is simple to install. Shut down Qemu, and now use the following command to run Qemu :
<pre>
qemu -L . -hda win95.disk -soundhw sb16 -net nic,model=ne2k_pci -net user -M pc -m 32 -vga std
</pre>

On bootup it will detect that a new NIC has been added.. Point it to your CD-ROM for the driver, then it will need the Windows 95 install files (remember c:\install\win95) to get it going. Also you may want to check protocols and remove everything, and add TCP/IP in there as it's the only thing that will work with user mode networking...

=== So far ===

Ok, this should be about it to get your system running... You should have sound, networking & video ... Enjoy the best of 1995!

== Where to go from here ==

With a base install of Windows 95, there are a bunch of little things that you will most likely want.

*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/InstMsiA.exe Installer 2.0 for 95]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/95sp1.exe Service pack 1 for Windows 95]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/DX80eng.exe Direct X 8.0]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/l3codecp.exe MP3 codec]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/opengl95.exe OpenGL for 95]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/w95ws2setup.exe Winsock 2 update]
*[https://archive.org/download/windows-95a-on-qemu_additonal_drivers/MSN%20messenger%205%20for%2095.exe MSN Messenger 5.0 for Windows 95]

And once you've installed Internet explorer 5.5sp2 that is about as far as Windows 95 will go.

[[Category:QEMU Tutorials]] [[Category:Qemu]]

MS-DOS

2023-01-19T08:46:16Z

Neozeed: add a brief summary of 4.00M

[[Image:MS-DOS 5.0.jpg|thumb|200px|right|MS-DOS 5.0 under Virtual PC.]]

'''MS-DOS''' was made popular by [[Microsoft]] for not only being the bundled [[operating system]] on the [[IBM-PC]] but also being available to the other clone [[OEM]]'s of the time.

Microsoft had sold [[IBM]] on the idea of MS-DOS when talks for [[CP/M]] had broken down. At the time Microsoft had no such product but was able to secure the rights to "[[86-DOS]]", a CP/M clone written by Tim Paterson, for the sum of $50,000. This has been the best ROI ever, as MS-DOS has made Microsoft untold billions of dollars.

MS-DOS uses the Int21 [[interface]] to allow programs to communicate with MS-DOS. It is designed to be a [[single tasking]] OS, that runs on the 8088/8086 [[Central Processing Unit|CPU]], and on the [[real mode]] of the [[80286]] and higher CPU's. There are ways to crudely [[multi-task]] via [[TSR]]'s and other shells that hook the [[clock]] [[interrupt]] and jump execution, although these are usually unstable at best.

DOS made use of the FAT [[file system]], and thus its popularity.

== Versions ==

=== MS-DOS 1.0 ===

This was the first version to launch with the [[IBM 5150]], or better known as the IBM PC. 1.0 'featured' a flat filesystem, and only supported the 5 1/4" [[diskette]]s.

=== MS-DOS 2.0 ===

I think this release added support for the [[IBM XT]] and hard [[disk]]s. [[Hierarchical]] filesystems were a new addition as well.

=== MS-DOS 3.0 ===

I think this release added support for 5 1/4" high density disks, and the [[IBM AT]].

=== MS-DOS 3.1 ===
Did this version exist?

=== MS-DOS 3.2 ===
[[Image:MS-DOS 3.2 box.jpg|150px|right]]

Released April (or, according to some, August), 1986.
This was the first OEM version of MS-DOS, a generic version for IBM-compatible PCs which for the first time included MS-written versions of the IBM utilities found in PC-DOS.

Earlier versions of MS-DOS could not be considered complete, they only included the core parts (i.e. the MS-developed parts of PC-DOS), were licensed to non-IBM vendors, and had to be augmented with modifications as/if needed for the particular hardware and with vendor-written versions of utilities found in PC-DOS. Documentation also had to be provided by said vendors.

MS-DOS version 3.2 changed all this, but the reason a generic MS-DOS could be produced was that vendors had started to see the point of being truly IBM compatible.

=== MS-DOS 3.3 ===

I think this release added support for the 3 1/2" high density floppy.

I also recall this version being VERY popular... Even to the point where people avoided MS-DOS 4.00 to run this version.

MS-DOS 3.3 also included some support for the FAT16 filesystem, however its format command still was limited to FAT12 filesystems.

IBM (after a joint development agreement with Microsoft) was the main developer of MS-DOS 3.3, and PC-DOS 3.3 was nearly identical to the OEM version of MS-DOS 3.3

=== MS-DOS 4.0 ===


This was the first release to support logical drives & extended partitions. This was also the first time that Microsoft had sold MS-DOS as a retail product, which was a break from the traditional OEM channels that Microsoft had fostered. I recall it selling for $50. DOS 4 still included the ancient programs edlin & gwbasic.

MS-DOS 4.0 could use partitions larger than 32MB. I've seen it on 512MB disks, it may go up to the full limitation of FAT16 of 2GB.

The first release 4.00 was VERY buggy, but I forget exactly why, although I recall something about 'large' 32MB files and various other things. Most people downgraded to 3.30. 4.01 addressed whatever issue it was, and it was good news.

Also making its apperance in MS-DOS 4.0 was the DOS shell, a simple GUI, to help people navigate their systems.

MS-DOS 4.0 was, as for version 3.3, mainly developed by IBM.

4.0 would have been released in 1988.

=== MS-DOS 4.00M ===
Also known as European DOS, or Multitasking DOS, this is the oddball outcast, while not a strict MS-DOS descendant, rather it is a re-write of MS-DOS to facilitate multitasking. It adds support for NE style executables, a task switcher, along with a few utilities to monitor the system. Also included is the needed LINK4 NE linker for the OS. So far no SDK or any real documentation has been found, although it is possible to build simple programs with Microsoft C 3.00 and link them with LINK4. MS-DOS 4.00M served as the foundation to what was to become OS/2.

There is one known disk set from ICL for this release, although it doesn't have a proper official place in the release tree, but it's name does place it here. The files are dated 11-26-85.

=== MS-DOS 5.0 ===
[[Image:MS-DOS 5.0 upgrade.jpg|150px|right|MS-DOS 5.0]]

This release was significant to allow for FAT partitions larger then 32MB, going up to 2GB. Also big features were himem.sys which allowed MS-DOS to execute in the top 64KB of [[protected mode]] because of a hardware bug in the IBM AT's handling of extended memory. Emm386.sys also was made popular allowing 386's to simulate [[EMS memory]] with [[extended memory]], and loading device drivers & TSR's into the reserved hardware space.

Version 5.0 also brought [[Qbasic]] 1.0, to replace the aging [[GWBasic]]. Included were the example programs money, gorilla, nibbles & remline. Along with a proper editor based on the Qbasic interface, supplementing the ancient edlin.

DOS-5 also used an install program with the same look & feel from Windows 3.0.

There is also a horrible promotion video [http://www.youtube.com/watch?v=dmEvPZUdAVI on youtube].

With version 5.0 Microsoft was again the main developer of MS-DOS.

=== MS-DOS 6.0 ===

This release added disk compression in order to compete with [[Stacker]]. Also included were some simple tools licensed from Central Point, including an anti virus program MSAV, a graphical backup program MSBACKUP, a defrag program licensed from symantec.

MS-DOS 6.0 was mainly to compete with the feature full DR-DOS 6.0

=== MS-DOS 6.21 ===
=== MS-DOS 6.22 ===
[[Image:MS-DOS 6.22 upgrade box.jpg|150px|right|MS-DOS 6.22]]

This release was to rectify the various lawsuits around the bundled disk compression.

This was also the last retail version of MS-DOS. As version 7 of MS-DOS was the base part of Windows 95.

[[Category: Microsoft Operating Systems]]

OS/2

2023-01-19T08:32:02Z

Neozeed: add in space for all the newly shared betas

[[Image:OS2 1.x neonlogo.jpg|thumb|150px|right|OS/2's early logo]]

'''OS/2''' started as a collaborative effort between [[IBM]] and [[Microsoft]] to put together the next generation [[operating system]] for the [[IBM AT]] and [[PS/2]] machines.

Microsoft, famous for hedging bets, started the [[Windows]] project around the same time, as a low cost entry interface with rudimentary (cooperative) [[multitasking]].

Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and the upcoming PS/2 model 60, hence the demand for the [[i286]] 16-bit version. Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller. Instead, the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.

Microsoft leapt at the chance to formalize DOS extenders into [[DPMI]], and use it in Windows, cementing OS/2's 1.x inability to run DPMI programs. Microsoft was also upset that IBM locked them out of the graphical components of the OS, and that OS/2 worked BACKWARDS compared to Windows... the 0/0 in the screen coordinates is the bottom right, while everywhere else it's the top left..

There is a great writeup on the divorce on google's [http://groups.google.com/group/comp.os.ms-windows.misc/msg/d710490b745d5e5e usenet archive], or locally here [[Gordon Letwin OS/2 usenet post]]. There is also a perspective from an Autodesk programmer available [http://www.sibbald.com/windows/windows01.html here].

With a bit more research and having things in hand, OS/2 as mentioned in the book Inside OS/2, is clearly an evolution from the MS-DOS 4.00M, the multitasking version of DOS. There was clearly a need for an 'advanced' operating system on the desktop, unfortunately in retrospect Microsoft had to get involved with IBM and derail the industry for nearly a decade.

== Versions ==

=== Pre-Release version ===
In the beginning there is several known pre-release versions, then followed up with the infamous $3,000 SDK package. These include:

* A/DOS
* SIZZLE
* FOOTBALL

The SDK versions have recently surfaced on archive.org and are currently known to be:
* [[Microsoft OS/2 beta 1.00|1.00]]
* 1.01
* 1.02
* 1.03
* 1.05
* 1.06

=== 16 bit versions ===
All of these versions require an [[i286]] cpu, and an [[IBM AT]], or [[PS/2]] compatible computer. All of the 16bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever increasing prevalence of [[MS-DOS]] based applications. At the same time, the 16bit version supported swapping, DLL's, threads and preemptive multitasking. There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].

*1.0
[[Image:Microsoft OS2 1.0 - Heathkit Zenith OEM.jpg|thumb|right|150px|OS/2 1.0]]
This version was all textmode, and had an interface that was inspired from TopView. Although it could multitask, most people didn't realize it, as all programs ran full screen. It ran in 286 protected mode, except for the single "DOS" mode session. As a result all device drivers for OS/2 had to be able to run in real & protected mode. Until 1.3 all versions were released by OEM hardware vendors (Compaq, Zenith etc, along with IBM), this was normal practice for Microsoft at the time.

The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].

*1.1
[[Image:IBM OS2 1.1 full package.jpg|thumb|right|150px|OS/2 1.1 full package]]
OS/2 1.1 was released in 1988, and was the first version to include the Presentation Manager. It 'looked' identical to that of [[Windows 2.0]]. IBM OS/2 1.1 included the PM version of Borland Sidekick to fill in the gap of accessories for OS/2. While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2. Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the triple fault method of the 286.

*1.2
[[Image:IBM OS2 1.2 box cover.jpg|thumb|right|150px|OS/2 1.2 box]]
I think this version was released in September of 1988. This release was significant with the inclusion of the HPFS filesystem. HPFS was significantly faster then the aging FAT filesystem as it placed its tables in the middle of the disk, and it allowed for larger filesystems, long filenames and extended attributes. A later service pack allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c). From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.

OS/2 1.2 from IBM included the 'standard' edition, along with the EE or extended edition. The EE edition included basic communications capability (x.25, rs232 terminal), and a SQL database.

[[InfoWorld]] included an excellent review of OS/2 1.2 [http://books.google.com/books?id=1DsEAAAAMBAJ&lpg=PT79&dq=%22OS%2F2%201.2%22&pg=PT66#v=onepage&q=%22OS/2%201.2%22&f=false|here].

*1.21
I think this version was a Microsoft exclusive, and the final version that they were directly involved in.

*1.3
[[Image:Microsoft OS2 front.JPG|thumb|right|150px|Microsoft OS/2 1.3]]
This was the last version of the 16 bit OS/2 family. The 1.3 user interface resembled that of [[Windows 3.0]]. Microsoft did include a 32bit HPFS driver in their Lan Manager package which allowed for the fastest HPFS implementation prior to OS/2 2.0 & Windows NT 3.1

Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2. The beta included a copy of all of the applettes & games from Windows 3.0 that could run in the Presentation Manager of OS/2. These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2. Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released. You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].

Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product. Windows NT on the i386 platform included support for 16bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server. Since they all were text mode, they would run unmodified up through Windows 2000.

=== 32bit versions ===
All of these versions require an [[i386]] SX or better CPU running on either an [[IBM AT]] compatible motherboard, or the [[IBM PS/2]] 32bit machines.

==== OS/2 2.x ====

*2.0 LA (LA Internal revision 6.167 91-10-08)
[[Image:IBM OS2 2.0 LA cover.jpg|150px|thumb|right|OS/2 2.0 LA]]
This was the first 32bit version. It was released after the IBM/Microsoft divorce, and was strictly an IBM release. There was no seamless Windows in this release, and Win-OS/2 only featured Windows 3.0a in standard mode.

The LA version does not include 'seamless' WIN-OS/2 sessions, and much like OS/2 2.0 GA it does not support Windows's 386 enhanced mode. While it is possible to launch Windows in a Window the display corrupts and it is exceptionally unstable.

Attempting to use any production GA drivers will result in a kernel crash.

*2.0 GA (GA Internal revision 6.307 92-03-01)
[[Image:IBM OS2 2.0 cover.jpg|150px|thumb|right|OS/2 2.0]]
This release included [[Windows 3.0]] for use in Win OS/2. At the time of the release the Presentation Managers graphic drivers were still 16 bit, although a later service pack was released which included 32bit drivers. It's interesting to note that OS/2's market share was so low at this time, that OS/2 2.0 included the ability to load older 16bit device drivers as the kernel was still a hybrid 16bit/32bit kernel.

The GUI had radically changed from 1.3 to 2.0 as it now included the Workplace Shell, a full OO GUI. Many people considered WPS to be 'the' killer application at the time, as Windows still had the program manager.

The new Presentation Manager replacement, Workplace Shell, included a deal with Commodore for the "look and feel" of [[AmigaDOS]], and as part of the deal, Commodore picked up a license for [[REXX]] into its products as first seen by AmigaDOS 2.0 .

The default syslevel for OS/2 2.0 is XR02000. The last known service pack for OS/2 2.0 brings it up to XR06100. The XR06100 update also installs the OS/2 32-bit Graphics Engine, XR02010.

*2.1 (06/1993)
This release brought the Win OS/2 functionality up to [[Windows 3.1]]. From the user standpoint it still looked like 2.0 . OS/2 2.1 also included the multimedia update which would allow for sound effects for almost every conceivable motion. It was very annoying.

OS/2 2.1 also supported more video cards, more printers, and included support for [[PCMCIA]] and [[APM]], making it acceptable for laptop use.

The update XR06200 brings OS/2 2.1 up to 2.11 functionality.

*2.11 (02/1994)
*2.11 SMP (08/1994)

OS/2 2.11 supported multiple processors, and from a user standpoint it was halfway between 2.11 and Warp. I remember this version being insanely expensive, as it was targeted to the 'server' crowd, IBM had shortsightedly decided end users wouldn't want SMP. While [[Windows NT]] Workstation always supported two physical processors.

==== OS/2 Warp 3 ====
[[Image:IBM OS2 Warp 3.0 blue spine cover.jpg|150px|thumb|right|OS/2 Warp 3.0 BlueSpine]]
*3.0 (09/1994)
This was the WARP release. At the time this release preempted the [[Windows 95]] release. IBM had done their best to tune OS/2 to run in 4MB of ram on a 386sx cpu. Warp also included the 'bonus pack' which included SLIP/PPP TCP/IP, a dialer application and a word processor & spreadsheet. A simple gopher client & NNTP client were also included.

IMHO this is where IBM missed the boat, by making TCP/IP difficult to configure, and by not including LAN drivers (that was WARP CONNECT), while [[Windows 95]] & [[Windows_NT#Windows_NT_3.5|NT 3.5]] both included SLIP/PPP *AND* lan drivers.

I *THINK* it was this release that included the ability to run [[Win32s]], which was a boon for Netscape & Mosaic.

*3.01 (1995)
OS/2 Warp with Win-OS/2

*3.02 (1995)
OS/2 Warp Connect
OS/2 Warp Server
OS/2 Warp Server Advanced

*3.05 (01/1996)
OS/2 Warp Server Advanced for SMP

==== OS/2 Warp 4 ====
[[Image:logo-warp.gif|thumb|150px|right|OS/2 Warp Logo]]
*4.0
OS/2 4.0 included both Java and Netscape in this release. Sadly IBM had still not 'gotten it' with regards to TCP/IP and insisted on a 'connect' version of 4.0 that included the LAN drivers. 4.0 also included the ability to install servicepacks online.

*4.01
Workspace on-Demand 1.0 (WSOD)
Workspace on-Demand 2.0

*4.5
IBM OS/2 Warp Server for e-business
Fixpak >=13 applied to OS/2 Warp 4 or WSOD

*4.51
Aurora Convenience Package 1 (ACP1), Merlin Convenience Package 1 (MCP1)

*4.52
Aurora Convenience Package 2 (ACP2), Merlin Convenience Package 2 (MCP2)

This was the last IBM release of OS/2.

== PowerPC port ==

It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship. IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revelutionalized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run x86 code (albeit slow..) and then switch to PPC mode. The company [[NexGen]] opened up everyone's eyes that a specialized [[RISC]] cpu could in fact run x86 instructions much quicker then a real Intel cpu... This opened the way to the Pentium CPUs and effectivly killed the [[RISC]] revolution.

There is a most excellent review to be found [http://www.os2museum.com/wp/?page_id=30 here] that also includes screenshots.

== Running OS/2 under an Emulator ==

=== 16 bit versions ===
The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place. I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile. Be sure to limit the VM to 16MB of ram, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.

Right now the best solution is either [https://pcem-emulator.co.uk/ PCem] or [http://ci.86box.net/ 86Box]. With the appropriate [http://tinyurl.com/rs20170821 ROMS] it's possible to install onto an emulated 286/386 class based machine.

==== OS/2 1.0 ====
[[Image:OS2 1.0.png|thumb|200px|right|OS/2 1.0 under VirtualBOX]]
*First version from November 1987 - no success.
*There is a later 1987 version that does run, it may be an OS/2 1.1 beta?
It seems the 1.0 IBM kernels rely on 286 triple faults and Virtual Box does not emulate it. However there is an early Microsoft OS/2 1.1 beta that uses the 386 method of switching to protected mode, and will run on modern machines (as long as the speed fix in place.).

==== OS/2 1.1 ====
[[Image:OS2 1.1.jpg|thumb|200px|right|OS/2 1.1 under Bochs]]
There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines. Even without an emulator you'd need to do this on anything in pentium II speeds.. With the speed stuff in hand, you can now run 1.1 on VirtualBOX as it's floppy driver now works with OS/2 to detect speed/density correctly.

OS/2 1.1c is the first version that supports the 386's method of switching from [[protected mode]] to [[real mode]]. Prior to level c of OS/2 1.1 the method was a 286 [[triple fault]], which almost all emulators do not fully support, or it may simply be in the IBM versions. I'm still not sure as early versions of OS/2 are hard to track down.

==== OS/2 1.2 ====
[[Image:OS2 1.2.png|thumb|200px|right|OS/2 1.2 on VirtualBOX]]
With the above hex edits in place, OS/2 1.2 installs somewhat ok. The big 'issue' I found was that the IBM version of OS/2 1.2 does not support PS/2 mice on the IBM AT computers. However you can take the PS/2 driver from OS/2 1.3 and use it.

==== OS/2 1.21 ====
[[Image:OS2 1.21.png|thumb|200px|right|OS/2 1.21 on VirtualBOX]]
Again there is an issue of no included working mice drivers, and poaching the driver from 1.3 works fine.

==== OS/2 1.3 ====
[[Image:Os213.png|thumb|200px|right|OS/2 1.3 under Virtual PC.]]
The only version of OS/2 1.x that can run under an emulator without any hacks applied. The three problems that you will run into is emulated floppy disks are too quick, and other various timing anomalies that will lead to a COUNTRY.SYS failure.

The method for install requires you to install OS/2 1.3 on a physical machine, update it, then make a whole disk image of it. I can confirm that OS/2 1.3 runs under [[Virtual PC 2007]] just fine. While it does have some issues with the floppy (it'll throw an error reading the floppy every time you put in a new disk) it will allow you to use the floppy. This makes OS/2 1.3 the easiest to install programs into.

At the moment, none of the 1.x versions will install under emulation, they all must be imaged from a physical machine.

* [http://support.microsoft.com/kb/102628/en-us Microsoft OS/2 1.3 HCL]

=== 32 bit versions ===

==== OS/2 2.0 ====
OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce. As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'. Sadly many of these betas did not survive. There is 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.

===== Betas =====
These are the ones I currently have access to, or directly know about:

====== Microsoft Developer's Relase 1 ======
====== Microsoft Developer's Relase 2 ======

====== Build 123 ======
[[Image:OS2 2.0 6.123.png|thumb|200px|right|OS/2 2.0 Build 123 on 86Box.]]
The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the inport busmouse adapter, along with the generic VGA adapter.

This build is the 'divorce' edition when IBM started to ship the betas itself, this version uses the OS/2 1.2 Presentation Manager. The MS-DOS is built around MS-DOS 4.0 and includes no DPMI support at all.
You can read more about it [http://www.os2museum.com/wp/os-2-2-0-spring-91-edition/ on OS/2 Museum]. The disks can be downloaded from archive.org [[https://archive.org/details/os2-2.0-6.123 HERE]].

To install I used [[86box]] i486 Socket 2, IBM PS/ValuePoint 433DX/Si, with a Pentium OverDrive 63Mhz processor, and a 'type 9' disk setup on IDE. The mouse is set to PS/2 mode.

The kernel has the following version string:

Internal revision 6.123, 91/02/04 $

The Copyright dialog has this dated for 1990.

====== Build 605 ======
Not sure why it's build 605 as it way out of sequence. Perhaps they thought they were close to the end. This is one of the last Presentation Manager based releases. It can be downloaded from [[https://archive.org/details/os2-2.0-6.605 archive.org here]].

The kernel string reports as:

Internal revision 6.605, 91/09/11

The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in 89.

605 also introduced the minimal text setup spanning install disk 1-4, with the rest being setup under the Presentation Manager.

====== Build 177 ======
[[Image:OS2 2.0LA in VirtualBOX.png|thumb|200px|right|OS/2 2.0 LA running under VirtualBOX.]]

At the moment the only way I've been able to install OS/2 2.0 LA on Virtual PC/VirtualBOX is to 'cheat' and use the install & disk 1 from OS/2 2.0 GA, and replace the following files on disk1, from LA's disk 1:

*CMD.EXE
*HARDERR.EXE
*SYSINST1.EXE
*SYSINST2.EXE
*FDISK.COM
*SYSLEVEL.OS2
*DISK.NUM

Then boot from GA's install, then use it's disk 1. Then use LA's disk from that point onward, and it'll install.

====== Build 304 ======

===== GA =====
[[Image:OS2 2.0 in Qemu.png|thumb|200px|right|OS/2 2.0 running under Qemu.]]
[[Image:Vpc5x os2v20 wps.png|thumb|200px|right|OS/2 2.0 running under Virtual PC 5 for OS/2]]

I've run OS/2 2.0 & 4.0 under Virtual PC, and Qemu... I guess it really comes down to if you move disk images around between various hardware platforms. Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner... Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host pc. I've heard that VMWare has given up the compatibility mode fixes.

I'm now running OS/2 2.0 under VMWare Player, and it seems to be running OK. I've found one issue with networking, the Set PermaNet Server feature must be set to TRUE, under the LAPS configuration tool.

*[[Qemu]]
*[[Virtual PC 2007]]

==== OS/2 2.1 ====

Adds 32-bit Graphics Subsystem. S3 display drivers are usable under Virtual PC.

* [http://drivers.s3graphics.com/en/download/drivers/legacy/Trio64V_765/eng30316.zip eng30316.zip] S3 drivers

==== OS/2 Warp 3 ====
*For installation with XDF diskettes, Virtual PC works, however you'll need to use the floppy drivers & xdf driver from OS/2 4.0
*You should first apply the latest fixpak (XRGW040) to use Guest Additions from Virtual PC.
*After this also GRADD device drivers (from Additions, IBM or Scitech SNAP) can be installed.

==== OS/2 Warp 4 ====

Fixpak 5 or better 9 should be applied for GRADD.

==== OS/2 Warp Server for e-business (4.5) ====

Works with Virtual PC.

==== OS/2 Convenience Package 1 (4.51) ====

Works with Virtual PC.

==== OS/2 Convenience Package 2 (4.52) ====

Works with Virtual PC and VirtualBox.

== Popular Applications ==

=== Autodesk ===
* AutoCad

=== IBM ===
* IBM DisplayWrite5/2

=== Informix ===
* Wingz

=== Lotus ===
* Lotus 1-2-3/G
* Lotus Freelance Graphics

=== Micrografx ===
* Micrografx Designer 3.0
* Micrografx Draw for OS/2

=== Microsoft ===
Microsoft did port over a bunch of their languages, along with a few applications, namely:

* Languages
** Microsoft MASM 6.0
** Microsoft C 5.1, 6.0
** Microsoft COBOL PDS
** Microsoft Basic 6.0
** Microsoft Basic PDS 7.0, 7.1
** [[Microsoft Fortran]]
* Productivity
** Microsoft Word 5.0, 5.5
** Microsoft Word (for Presentation Manager) 1.1
** Microsoft Excel 2.2, 3.0

All of these products are 16 bit only. While there was two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.

=== StarDivision ===
* StarWriter 2.0 for OS/2
* StarOffice 3.0

=== Watcom ===
* Watcom C / C++
* Watcom Fortran 77
* Watcom SQL

[[Category: Microsoft Operating Systems]]

PC Rogue

2023-01-12T18:30:05Z

Neozeed: update source link

[[Image:pcrogue.png|400px|thumb|right|Rogue splash screen]]

Rogue was sold commercially by ID Software and was available for a wide variety of platforms.

The [[source code]] is available and can be compiled with [[MANX]]'s [[Aztec C]] 3.40a.

There are three versions of Rogue that run under DOS on a [[IBM-compatible PC|PC]]:

* The first was a direct port, of Rogue 3.6, which has no graphic options.
* The second one was a per-release of the commercial labeled 'Public Domain'.
* Finally, a port of Rogue 5.0.2 which has the CGA Splash screen show above.

The PC version of Rogue was copy protected, and if you pirated it, you would be killed, and your gravestone would say 'Killed by Copy Protection Mafia'.

The copy protection was easily defeated by Copy II PC.

==External links==

* [https://web.archive.org/web/20120226052526/http://www.roguelikedevelopment.org/archive/files/sourcecode/rog11src.zip Source code]

{{semi-stub}}

[[Category: Games]]

Hack (game)

2023-01-12T10:42:36Z

Neozeed: added some github for Amiga & MS-DOS Hack

[[Image:Hack-1984.png|right|]]

First there was [[Rogue]], then Hack. The original Hack was [http://nethackwiki.com/wiki/Jay_Fenlason%27s_Hack Jay Fenlason's Hack], which apart from a few MS-DOS binaries, has largely been lost. It can be recompiled from sources at the [https://nethackwiki.com/wiki/Hack_1.0#Availability NetHack archives.]

Andries Brouwer later released his Hack on Dec 17 1984. The source code to Hack 1.0 preliminary version, can be found on the UTZOO archives, namely on [http://shiftleft.com/mirrors/utzoo-usenet/news019f2.tgz tape news019f2].

*[http://www.megalextoria.com/usenet-archive/news019f2/b34/net/sources/00002127.html Original announcement]

Don Kneller, made many of the ports including [https://github.com/neozeed/pchack PC-Hack] to [https://nethackwiki.com/wiki/MS-DOS#Hack_on_MS-DOS MS-DOS], and [https://github.com/neozeed/hack-1.01-Amiga Hack-1.01 for the Amiga].

Hack had several updates through 1985, there was a 1.0.1, 1.0.2 and a 1.0.3

Then it later took on a life of it's own on the internet much like NetBSD as [[Nethack]]. You can find information [http://nethackwiki.com/wiki/Main_Page here].

{{semi-stub}}

[[Category:Games]]

XENIX

2023-01-07T10:18:18Z

Neozeed: Add backup link to Xenix-2.3.4.exe

[[Image:Xenix 386.jpg|thumb|right|200px|Xenix on a 386]]

'''Xenix''' (formally '''XENIX''', e.g. in contemporary [[Microsoft]] material) was Microsoft's [[software port|port]] of AT&T [[UNIX]]; it was a [[portable]] [[operating system]] with ports to various platforms. It was based on [[UNIX Sixth Edition|v6]], [[Unix Seventh Edition|v7]], [[SYSIII]], and later [[SYSV]].

: ''XENIX was originally developed on a DEC Virtual Address Extension (VAX) running the Virtual Memory System (VMS) and a PDP-11 running UNIX V7, albeit now using Microsoft's own in-house minicomputers, and then converted into assembly language specific to the new 16-bit Motorola 68000 and Intel 8086 microprocessors. This put XENIX at the high end of the microcomputer market, which was still dominated by 8-bit machines, but well below the lowest end of the minicomputer market'' - "XENIX -- Microsoft Short-lived Love Affair with Unix "

Unfortunately, "Xenix even incorporated the elements of BSD and became the most widely installed base of any Unix variant. Talking about the different modifications of Xenix, it was ported to Zilog Z8001, Intel 8086, Tandy Corporation’s 68000 based computers, and even a variant for Apple Lisa."

<blockquote>Modifications to Western Electric v7 included those necessary to transport the UNIX system from the larger PDP-11 mini computer to the 16-bit microprocessors. Currently scheduled machines included the DEC LSI-11/23, Zilogs Z8001 and Z8002, Intel's 8086 and 286, and Motorola's MC68000. - Robert Greenburg, uSloth. </blockquote>

Because of the price of the OS, about $500USD for the OS, and $500USD for the developer tools, combined with cheap [[IBM PC|PC]] and [[IBM-compatible PC|compatibles]], Xenix was the most widespread UNIX until the rise of [[Linux]]. Xenix due to its inherent [[multi-user]] capabilities became widespread in sales environments with POS (Point of Sales) terminals, and for scheduling systems commonly found in hotels and restaurants. Occasionally you can still find this setup still running on aging [[hardware]].

With the rise of the [[IBM PC]], it primarily became an [[Intel x86|x86]] based OS. Xenix eventually became [[SCO Unix]], then later SCO [[OpenServer]], where it still languishes today.

== Platforms ==

=== Intel ===

Xenix supported the following platforms:

*[[IBM 386]] [386 GT] The 32bit ones will run on Qemu/Virtual PC ( Sometimes called 386AT )
*IBM [[PS/2]] [386 MC] This version was specifically for [[MCA]] computers with a 386 or higher CPU. ( Sometimes called 386PS )
*SCO Announced Xenix for the Model 50(286), 60(286) and 80[Ran 386 MC], but its unknown if there are archives of it.
*[[IBM AT|IBM 286]] [286] - This version is now easy to find, but hard to run... It does not work on a 386.
*IBM PC [8088 or x86] - This is 'easy' to find.

This is a list of version numbers for the various Architectures:

*SysV 386 – 3.2, 4.2
*386 – 2.2.3b, 2.3.1, 2.3.2f, 2.3.4a, 2.3.4h ( SCO v2.2.3b, v2.3.2f, v2.3.4h)
<nowiki>*</nowiki>(You Plan to Install TCP/IP (XENIX.386 v2.3.4 only)
*286 – 2.1.3*, 2.2.1e, 2.2.3b, 2.3.2b, 2.3.2d ( SC0 v2.1.3, v2.2.1e, v2.2.3b, v2.3.2d)
<nowiki>*</nowiki>(Honey DanBer UUCP package v2.3.2 onward)
*8086 – 2.1.3* (SCO v2.1.3)

*These are currently the only two that boot on pcjs's website.

=== Motorola ===

*IBM System 9000 [[M68000]] [c 1984]
*[[Apple Lisa]] [[M68000]] [c 1984] The emulator [[idle]] can run this.

=== Others ===

*[[PDP-11]] - No versions of this exists online. There is a note that Xenix with Programmers console ran on a PDP-11/34. [https://comp.os.vms.narkive.com/Qoy6kBJU/xenix-vax-pdp# Xenix on PDP]
*[[Tandy TRS-80 Model II]] [[Z80A]] - There are disk images floating around.
*[[Zilog Z8001]] [c 1979] - I have only found sales literature that mentions this.*

<nowiki>*</nowiki> Note: This sounds like vaporware since neither the Onyx 1 nor the Commodore 900 ran Xenix

== Software ==

A quick list of a few software programs that were available on Xenix. I know the [[x86]] platform was the most supported, I now know that some of these made it to the less popular [[68000]] platform.

=== Microsoft ===

Microsoft made several of their programs in the 1980's available on the Xenix platform.
Microsoft Multiplan, and the BASIC Compiler.

=== Languages ===

*[[C programming language|C]]
*[[Basic]] - Basic [[Compiler]], Basic [[Interpreter]]
*[[Cobol]]
*[[FORTRAN|Fortran]]
*[[Pascal]]
*[[Assembler]]

"the base operating system does not include development tools such as a C compiler, but it does include the linker and, importantly, an assembler (which is needed to rebuild the configuration files). The assembler is, however, disguised to make it less obvious what it is by giving it a different name and that is what I have been trying to remember ever since I saw this post. Finally, this morning, it came to me. You ''should'' find that you have something called 'storel' (read it as 's-to-rel' as in 'something that transforms .s files into relocatable (ie .o) files' and the name becomes a little less obscure) on the system - I ''think'' that it lives in /bin. but it ''might'' be somewhere else such as /etc." (Source: [http://www.vcfed.org/forum/archive/index.php/t-49002.html here])

=== Applications ===

*Autodesk AutoCAD 10i
*Microsoft Multiplan (available on the Apple Lisa)
*Microsoft Word v5.0
*vi (Not really an application, but more of a torture device. May not be present on the x86 version, so ed will have to be used.)

=== Databases ===

*Foxpro

=== Games ===

* [[Rogue]]

=== SCO* ===

*SCO Professional
*SCO Lyrix (available on the Apple Lisa)
*SCO Integra
*SCO Manager
*SCO Multiview

<nowiki>*</nowiki> - ''SCO in this case refers to the original Santa Cruz Operation, and not the later SCO Group who bought the name and started the SCO/Linux lawsuits.''

== Getting this to run ==

The 8086 version of XENIX runs fine in an emulator.

Note: The 286 version of XENIX will only run on a 286 processor or a 286 processor emulator that handles the upper byte of the Global Descriptor byte 7, documented as reserved for use on a iAPX 386, by essentially ignoring it, and letting XENIX use it. A poor programming choice as best. (Now, that we know the publication dates of Intel's documentation (1982), we know they ignored the Intel documentation about the use of the upper byte of the descriptor words.. Details [http://www.os2museum.com/wp/ibm-xenix-two-steps-forward/comment-page-1/#comment-363304 here])

[[User:Neozeed]] wrote about [[Installing Xenix 2.x on Qemu|how to get it to run under QEMU 0.14]].

A repository has a file, that when run, unpacks Qemu 0.14, and has a disk, that boots straight into Xenix 2.3.4/386; the uname -a does confirm both the platform and the version.

Also, there is: [ftp://major.butt.care/mirrors/Unix/Xenix/Xenix-2.3.4.exe Xenix 2.3.4/386][https://archive.org/details/xenix-234-installer Backup]

Another directory has the same file from a SCO Mega pack called:
SCO Xenix 2.3.4 - preinstalled, run in Windows.

==External links==

===Announcements===

* [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=897/ENUS284-159&infotype=AN&subtype=CA&appname=skmwww XENIX Operating System for the IBM System 9000]
* [https://www.cbronline.com/news/santa_cruz_ships_xenix_v_for_ps2_developed_in_london/ Santa Cruz ships XENIX V for PS2 - Developed in London]

===History===

* [http://seefigure1.com/images/xenix/xenix-timeline.jpg The XENIX timeline] - The most comprehensive time vs port list
* [http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml Microsoft Short-lived Love Affair with Unix] - A detailed history
* [https://fossbytes.com/xenix-history-microsoft-unix-operating-system/ History Of Xenix - Microsoft's Forgotten Unix-based Operating System]
* [http://seefigure1.com/2014/04/15/xenixtime.html A bit of XENIX history] - XENIX history
* [http://www.edm2.com/index.php/XENIX XENIX] - Brief wiki page on XENIX; includes a bibliography

* [https://archive.org/details/byte-magazine-1981-06/page/n249 The UNIX Operating System and the XENIX Standard Operating Environment] - Byte Magazine Article on Xenix, BYTE June 1980, pg 249


===Emulators===

* [http://www.hampa.ch/pce/download.html PCE - PC Emulator] - [x86] Architecture
* [https://download.qemu.org/qemu-0.14.0.tar.gz QEMU v0.14runs SCO Xenix for i386 and i286]
* [https://www.pcjs.org/software/pcx86/sys/unix/sco/xenix/386/2.3.4h/ SCO Xenix 386 v2.3.4h] - 80386 version of Xenix

* [https://www.pcjs.org/disks/pcx86/unix/sco/xenix/286/2.1.3/ SCO Xenix 286 v2.1.3] - Runs Xenix 286 2.1.3 in a browser window.
* [https://www.pcjs.org/disks/pcx86/unix/sco/xenix/086/2.1.3/ SCO Xenix System V Release 2.1.3 for i8086] - Runs Xenix 8086 2.1.3 in a browser window.

* [https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand Tenon Xenix 286 2.3.2d on Linux w/ Qemu. ]

===Repositories===

* [ftp://major.butt.care/mirrors/Unix/Xenix/ 386, 286, x86, 386MC, Tandy, Lisa, Text, and Docs] Comprehensive Mirror
* [https://github.com/retrohun/blog/tree/master/dt/xenix286ondemand Xenix286 on demand]

* [https://winworldpc.com/product/xenix/286 Xenix 286]
* [http://www.vcfed.org/forum/showthread.php?30490-Xenix-Development-Systems Xenix Development Systems]

* [https://macintoshgarden.org/apps/xenix-30-apple-lisa Xenix 3.0 for Apple Lisa]
* [http://tenox.pdp-11.ru/xenix/ Tenox Operating Systems Archive] - Includes Xenix documentation in PDF format]
* [https://archive.org/details/Xenix386Ports SCO Xenix and a set of ported software]

===Archaeology===

* [https://museo.freaknet.org/gallery/software/xenix/versions.txt A list of version numbers pulled from disks]
* [http://seefigure1.com/2014/04/15/xenixtime.html A bit of XENIX History] (from a MS Developer '86 ~ '89)
* [http://www.os2museum.com/wp/category/xenix/ Category Archives: Xenix] - precursor to the next group
** [https://www.os2museum.com/wp/the-xenix-386-2-2-3-mystery/ The XENIX 386 2.2.3 Mystery]
** [http://www.os2museum.com/wp/the-xenix-2-2-3-mystery-continued/ The XENIX 2.2.3 Mystery, Continued]
** [http://www.os2museum.com/wp/oldest-surviving-386-pc-os/ Oldest Surviving 386 PC OS?]
* [https://soylentnews.org/search.pl?query=Xenix Searching For: Xenix] - Xenix at SoylentNews
** [https://soylentnews.org/article.pl?sid=17/03/03/1620222 Restoring Xenix 386 2.2.3c, Part 1]
** [https://soylentnews.org/article.pl?sid=17/03/07/1632251 Xenix 2.2.3c Restoration: No Tools, No Problem (Part 2)]
** [https://soylentnews.org/article.pl?sid=17/03/11/2014253 Xenix 2.2.3c Restoration: Damage Mapping (Part 3)]
** [https://soylentnews.org/article.pl?sid=17/03/13/086250 Xenix 2.2.3c Restoration: Xrossing The X (Part 4)] - Includes some extraordinary efforts to get some utilities to run
* [https://www.bell-labs.com/usr/dmr/www/xenix.gif XENIX ad from Dennis Ritchie's home page at Bell Labs]
* [https://www.linux-magazine.com/index.php/Online/Features/Remembering-XENIX Remembering XENIX]
* [https://www.snellman.net/blog/archive/2015-09-01-the-most-obsolete-infrastructure-money-could-buy/ The most obsolete infrastructure money could buy - my worst job ever] - XENIX 286 problem from hell

{{semi-stub}}

{{Nav Unix}}

[[Category: Unix-based OS's]]

Talk:Installing VMS V1.0 on SIMH

2022-12-13T01:31:15Z

Neozeed: added

I see Bitsavers has VMS V1.5. Is your RK07 image the only copy of V1.0? [[User:Larsbrinkhoff|Larsbrinkhoff]] ([[User talk:Larsbrinkhoff|talk]]) 08:55, 23 May 2022 (CEST)

No, there's also a tape image. As far as my weak memory serves me right it was Matt Burke who provided the tape image some time ago. I think it is not an image of a genuine tape but reconstructed from sources or a system backup, but it seems to be o.k., if not perfect. I made an RK07 image using this tape as to save the old VMS novice from the need of using DSC (Disk Save and Compress, the precursor of BACKUP). And there has been an RK07 distribution disk for small VAX-11/780 systems as stated in the installation manual AA-D021B-TE VAX-11 Software Installation Guide.

See: [http://www.bitsavers.org/bits/DEC/vax/vms/OldVMS_V1.4.iso.7z OldVMS_V1.4.iso] if you are interested in my OldVMS collection. [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 09:08, 23 May 2022 (CEST)

I just wanted to add, this is super cool! I just added a backup to the fileset, just in case as always! [[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 02:31, 13 December 2022 (CET)

Installing VMS V1.0 on SIMH

2022-12-13T01:29:38Z

Neozeed: Added a backup to the files on archive.org

The aim of this tutorial is to show how to install [[VMS]] V1.0 on the [[SIMH]] [[VAX-11/780]] [[simulator]].

== Preparations ==

=== simh vax780 simulator ===

You have to use the [[SIMH]] '''vax780''' simulator because the [[VAX-11/780]] was the only VAX existing when VMS was introduced.

All other VAX computers need later versions of VMS to run.

=== VMS V1.0 ===

Get a VMS V1.0 [[RK06/07 disk drive|RK07]] disk image from [https://drive.google.com/drive/folders/1Pon-KHWM2oq0iZx2mtfeR2N1hi-KJsXu?usp=sharing here] [https://archive.org/details/Vaxorcist_vax-vms-v-1.0 (backup)], unzip and put it in into the directory where the SIMH vax780 simulator resides.

=== vax780.ini for a typical small 16-user VAX-11/780 system ===

Use the following vax780.ini file for a typical small 16-user VAX-11/780 system.

You cannot set a memory size smaller than 1MB in the simh vax780 simulator directly, but there is a workaround in VMS:

You set the maximum available memory in '''SYSBOOT>''' on the first boot.

[[File:VAX-11-780 2RK07.jpg|400px|thumb|right|Small [[VAX-11/780]] system with two [[RK06/07 disk drive|RK07]] disk drives, and an [[LA120]] Console Printer Terminal]]

A [[VAX-11/780]] system like this - but without the tape drive - (DEC order no. SV-AXHHB) cost 141,300 US$ back in 1980.

The [[MASSBUS]] [[TE16]] tape drive subsystem ('''TEE16''') added in this configuration was 20,200 US$, and an additional 512KB memory ('''MS780-DB''') would have taken 13,900 US$.

<pre>
; ================================================
; vax780.ini
; ================================================
;
; Small Size 16 User System made of:
; - 512K bytes of memory (set within SYSBOOT>)
; - 16 DZ11 terminal lines
; - 2 RK07 disk drives
; - line printer
; - TE16 magnetic tape unit
; The tape unit is non-standard in small systems,
; but very useful e.g. to install more software

SET QUIET

SET CPU 1M
SET THROTTLE 1M
;SET CPU IDLE=VMS

SET CONSOLE LOG=VMS010-01.LOG

ATT CS CONSOLE.RX1 ; DXA1:

SET DZ LINES=16
ATT DZ 6666

SET LPT ENA
ATT LPT printer.txt

SET RP DIS

SET RL DIS

SET HK0 RK07 ; DMA0:
ATT HK0 VAX-VMS_V1.0.RK7

SET HK1 RK07 ; DMA1:
ATT HK1 DATA.RK7

SET HK2 DIS
SET HK3 DIS
SET HK4 DIS
SET HK5 DIS
SET HK6 DIS
SET HK7 DIS

SET RQ DIS
SET RY DIS
SET TQ DIS
SET TS DIS

SET TU ENA
SET TU0 TE16 ; MTA0:

SET TU1 DIS
SET TU2 DIS
SET TU3 DIS
SET TU4 DIS
SET TU5 DIS
SET TU6 DIS
SET TU7 DIS

BOOT HK0/R5:1
;BOOT HK0
</pre>

== Installation ==

=== First boot ===
Start the simh vax780 simulator:

Windows:
<pre>run vax780.exe</pre>

Linux:
<pre>./vax780</pre>

Be aware that Linux is case sensitive!
----
SIMH tells you it will write a log:

<pre>
Logging to file "VMS010-01.LOG"
</pre>

VMS boots to the '''SYSBOOT>''' prompt. Enter the following three commands and confirm each with '''<Enter>''':

<pre>
SYSBOOT> USE 16USER.PAR

SYSBOOT> SET PHYSICALPAGES 1024

SYSBOOT> CONTINUE
</pre>

This way you do:

- Choose the parameter file for a small 16-user system

- Reduce available memory to 1024 pages = 512K

- Continue booting

VMS continues booting and asks you for the current date and time:

<pre>
VAX/VMS Version 1.00 21-AUG-1978 15:54

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 21-MAY-1989 8:51
</pre>

Enter date and time as shown above and confirm with '''<Enter>'''.

The boot process continues up to the boot statistics screen now:

<pre>
OPCOM, 21-MAY-1989 08:51:11.84, LOGFILE INITIALIZED, OPERATOR=_OPA0:

$ !
$ ! VAX/VMS system startup - Release 1
$ !
$ SHOW TIME
21-MAY-1989 08:51:12
$ SET NOVERIFY
%MOUNT-I-MOUNTED, CONSOLE mounted on _DXA1:
Login quotas - Interactive limit=64, Current interactive value=0
SYSTEM job terminated at 21-MAY-1989 08:51:15.16

Accounting information:
Buffered I/O count: 142 Peak working set size: 100
Direct I/O count: 37 Peak virtual size: 111
Page faults: 271 Mounted volumes: 1
Elapsed CPU time: 0 00:00:01.90 Elapsed time: 0 00:00:04.31
</pre>

Press '''<Enter>''' to get to the login prompt.

Log in with username '''SYSTEM''' and password '''MANAGER'''.

The password is NOT echoed.

<pre>
Username: SYSTEM
Password:
Welcome to VAX/VMS Version 1.00
$
</pre>

You're in!

Try '''DIR''' as a first VMS command to show the files in your login directory:

<pre>
$ DIR

DIRECTORY DM0:[SYSMGR]
21-MAY-89 08:51

ACCOUNTNG.DAT;1 1. 21-MAY-89 08:51
FORMSTYPE.DAT;1 2. 21-AUG-78 15:54
OPERATOR.LOG;1 1. 21-MAY-89 08:51
SYSHUTDWN.COM;1 0. 21-AUG-78 15:54
SYSTARTUP.COM;1 0. 21-AUG-78 15:54

TOTAL OF 4./112. BLOCKS IN 5. FILES

$
</pre>

=== A first look around ===
Let's have a first look at our installed VMS V1.0!

==== For the users completely new to VMS ====
Try the following commands.

You can abreviate all commands to the extend that they do not get ambiguous, e.g. '''SH''' instead of '''SHOW'''

VMS is not case-sensitive, but it is common practice to enter commands in UPPERCASE.
----
'''SHOW SYS''' shows you what's going on your system:

<pre>
$ SH SYS
VAX/VMS Processes on 21-MAY-1979 18:04:45.10
Pid Process Name UIC State Pri Dir. I/O CPU Page flts Ph.Mem
00010000 NULL 000,000 COM 0 0 00:00:28.69 0 0
00010001 SWAPPER 000,000 HIB 16 0 00:00:00.12 0 0
00010017 ERRFMT 001,006 HIB 7 5 00:00:00.03 26 29
00010018 OPCOM 001,004 LEF 11 2 00:00:00.06 29 33
00010019 JOB_CONTROL 001,004 HIB 11 6 00:00:00.09 31 77
0001001A DMA0ACP 001,003 HIB 9 88 00:00:00.50 47 69
0002001B SYSTEM 001,004 CUR 5 6 00:00:00.28 71 86
$
</pre>

- '''Pid''' = Process ID

- '''Process Name''' (self-explaining)

- '''UIC''' = Process owner (User ID)

- '''State''' = Process state

- '''Pri''' = Process priority

- '''Dir. I/O''' = Process direct I/O count

- '''CPU''' = Process CPU time used

- '''Page flts''' = Process page faults

- '''Ph.Mem''' = Process physical memory

----
'''SHOW DEV''' shows the devices on your VAX:

<pre>
$ SH DEV
List of Devices on 21-MAY-1979 18:09:45.68
Device Device Device Err. Volume Free Trans Mount
Name Status Characteristics Count Label Blocks Count Count
DMA0: on line MNT 0 VAXVMSRL1 29528 19 1
DMA1: on line 0
OPA0: on line 0
DXA1: on line MNT FOR 0 CONSOLE 0 1 1
LPA0: on line 0
TTA0: on line 0
TTA1: on line 0
TTA2: on line 0
TTA3: on line 0
TTA4: on line 0
TTA5: on line 0
TTA6: on line 0
TTA7: on line 0
TTB0: on line 0
TTB1: on line 0
TTB2: on line 0
TTB3: on line 0
TTB4: on line 0
TTB5: on line 0
TTB6: on line 0
TTB7: on line 0
MTA0: on line 0
$
</pre>
- '''DMA0''' is the first RK07 disk drive (the VMS system drive)

- '''DMA1''' is the second RK07 disk drive (the data drive, still empty)

- '''OPA0''' is the operator terminal (from which you boot the system)

- '''DXA1''' is the console floppy drive (very important to boot a real VAX-11/780, just a dummy for simh)

- '''LPA0''' is the system line printer

- '''TTA0''' - '''TTB7''' are the sixteen user terminals

- '''MTA0''' is the TE16 magtape drive

----
'''HELP''' shows the available help topic and brief instructions for using '''HELP''':
<pre>
$ HELP

Help can be obtained on a particular topic by typing :
HELP topic subtopic subsubtopic ...
A topic can have the following format :
1) an alphanumeric string (e.g. a command name, option, etc...)
2) same preceded by a "/" (=interpreted as a qualifier)
3) the match-all symbol "*"
Examples:
HELP ASSIGN PARAMETERS
HELP SET TERMINAL /LOWERCASE
Abbreviations result in all matches being displayed.

Additional information available:

ALLOCATE APPEND ASSIGN BASIC CANCEL CLOSE COBOL
CONTINUE COPY CREATE DEALLOCATE DEASSIGN DEBUG DECK
DEFINE DELETE DEPOSIT DIFFERENCES DIRECTORY DISMOUNT DUMP
EDIT EOD EOJ ERROR EXAMINE EXIT FORTRAN
GOTO HELP IF INITIALIZE INQUIRE JOB LIBRARY
LINK LOGOUT MACRO MCR MOUNT ON OPEN
PASSWORD PRINT PURGE READ RENAME REQUEST RUN
SET SHOW SORT SOS SYNCHRONIZE STOP SUBMIT
TYPE UNLOCK WAIT WRITE login procedure specify
symbols
$
</pre>
----
Be careful not to destroy the newly installed system; you are logged in as '''SYSTEM''' who can e.g. easily delete crucial system files.

The use of '''SHOW''' commands cannot do any harm.

==== For users who already know "newer" VMS versions (V4.x and later) ====

You will probably miss some of the commands you know from "newer" VMS versions ...

Some utilities have different names, others are not yet existing.

- '''BACKUP''' is '''DSC''' in VMS V1.0

- '''MONITOR''' is '''DISPLAY''' in VMS V1.0 (needs to be called '''MCR DISPLAY''')

- '''SHOW MEMORY''' is not yet implemented in VMS V1.0

- ...

=== Orderly shutdown ===

VMS needs an orderly shutdown.

Don't just break out of the simulation using '''<Strg + e>''' and tell simh to exit.

You might loose data not yet written to disk and (if Murphy comes around) destroy the file structures on your disk.

Use the following command to perform an orderly shutdown:

'''@SYS$SYSTEM:SHUTDOWN'''

You will be asked for the shutdown delay in minutes (you can specify '''0''' minutes for an immediate shutdown).

Furthermore you can give an optional reason for the shutdown to be displayed at the terminals of the users on your system (just press '''<Enter>''' to skip).

<pre>
$ @SYS$SYSTEM:SHUTDOWN
System shutdown command procedure.
21-MAY-1989 16:41:14
HOW MANY MINUTES UNTIL SHUTDOWN?: 0
REASON?: REBOOT
Login quotas - Interactive limit=0, Current interactive value=1
Non-operator logins are disabled.
OPCOM, 16:43:45.70, OPERATOR TERMINAL STATUS, _OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK,
OPER(1,2,3,4,5,6,7,8,9,10,11,12)

_OPA0:,SYSTEM 16:43:46.57
"BATCH AND DEVICE QUEUES HAVE BEEN STOPPED"

_OPA0:,SYSTEM 16:43:51.14
"SYSTEM SHUTDOWN IN 0 MINUTES. LOGINS ARE DISABLED, PLEASE LOGOFF.

_OPA0:,SYSTEM 16:43:55.68
"REBOOT

Invoke installation dependent shutdown procedure.
Stop all user processes.
Dismount all mounted volumes.
OPCOM, 16:44:02.02, SYSTEM ACCNT=SYSTEM
OPCOM, _OPA0:, "OPERATOR REQUESTED SHUTDOWN"

OPCOM, 21-MAY-1989 16:44:02.15, LOGFILE CLOSED, OPERATOR=_OPA0:

**** FATAL BUG CHECK, VERSION = 1.00 OPERATOR, Operator requested system shutdown

CURRENT PROCESS = SYSTEM

REGISTER DUMP

R0 = 00000024
R1 = 00000000
R2 = 00000004
R3 = 7FFE8F05
R4 = 80059670
R5 = 7FFEE284
R6 = 31000513
R7 = 7FFEF99C
R8 = 7FFEF87C
R9 = 7FFEF98C
R10= 7FFEF9A4
R11= 7FFE6C10
AP = 00000000
FP = 7FFEEBD0
SP = 7FFEEBC8
PC = 0000045D
PSL= 00DF0000

KERNEL/INTERRUPT STACK

7FFEEBD0 00000000
7FFEEBD4 00000000
7FFEEBD8 7FFDC778
7FFEEBDC 7FFEEBE4
7FFEEBE0 800087E9
7FFEEBE4 00000000
7FFEEBE8 00000000
7FFEEBEC 7FFDC778
7FFEEBF0 7FFDC760
7FFEEBF4 8000B4E3
7FFEEBF8 80000096
7FFEEBFC 03C00000

EXEC STACK

PROCESS PRIVILEGES

80062400 FFFFFFFF
80062404 FFFFFFFF

IMAGE NAME = DMA0:[SYSEXE]OPCCRASH.EXE;1

Infinite loop, PC: 80008462 (BRB 80008462)
sim> exit
Goodbye
</pre>

For VMS V1.0 it is expected behavior to get a '''FATAL BUG CHECK''' at the end of the shutdown.

When you get the simh prompt ('''sim>''') you can safely exit the simulator using the '''exit''' command.

=== Subsequent boots ===
Now that you have sucessfully installed VMS V1.0 you no longer need to boot into '''SYSBOOT>'''.

Make a comment out of the command '''BOOT HK0/R5:1''' in the vax780.ini file by putting a semicolon in front of it.

Remove the semicolon from the ''';BOOT HK0''' line to make it a command.

From now on you'll boot directly into VMS V1.0!

Congratulations!

== "Connecting" User Terminals ==
I recommend using a [[Telnet]] [[client]] such as [[PuTTY]] to connect to the 16 terminal lines.

I use the following PuTTY settings:
* Host Name: 127.0.0.1 (or your PCs IP address)
* Connection type: Telnet
* Port: 6666
* Terminal/Keyboard/The Backspace key/: Control-?
* Terminal/Keyboard/The function keys and keypad: VT100+

<pre>
Connected to the VAX 11/780 simulator DZ device, line 0

Username: SYSTEM
Password:
Welcome to VAX/VMS Version 1.00
$
</pre>

== Recommended Reading ==
* [http://bitsavers.org/pdf/dec/vax/vms/1.5/1a/AA-D021B-TE_SoftwareInstallationGuide_Feb79.pdf AA-D021B-TE Software Installation Guide]

* [http://bitsavers.org/pdf/dec/vax/vms/2.0/AA-D030B-TE_VAX_VMS_2.0_Primer_198003.pdf AA-D030B-TE VAX/VMS Primer]

[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

MacMiNT

2022-12-09T11:59:14Z

Neozeed: Updated download links since so many things are dead

[[Image:MacMiNT.png|right|thumb|MacMiNT under Basilisk II]]

MINT back in the day for [[Atari ST]]’s was a [[UNIX]]-like layer that ran on top of [[Atari TOS|TOS]] (The Atari [[MS-DOS]] like [[operating system|OS]]) and provided basic Unix services. With the program aptly called JET (Just Enough TOS), the [[Macintosh]] [[68000]]’s can setup a TOS compatible [[interrupt vector]] table, and run TOS procedure emulation to run the [[MINT]] binaries under [[MacOS]]!

So, it’s UNIX!

Sort of. Consider it an "Operating Environment", much like what Windows 3.1 was to MS-DOS.

First you need to disable [[virtual memory]]… That’s bad.
Next it doesn’t support [[TCP/IP]] so it’s like being on [[Unix v6]]. But it’s fun at any rate.

You can find the binaries [https://archive.org/details/macmint/MacMiNT.png here on archive.org]

It includes gcc 2.5.8, and a somewhat basic environment. It does have lots of potential, but the biggest gripe is that it will crash with virtual memory enabled. Also since it is 68000 based programs it is running under emulation on the PowerMAC computers. It will run on various 68k emulated MAC's namely [[Basilisk II]].

== Games ==

I've even managed to port [[Zork]] to Mint via [[f2c]]. It was pretty straight forward... You can download it [http://vpsland.superglobalmegacorp.com/install/f2c/dungeon-2.5.6-m68k-mint.zip here].

{{semi-stub}}

[[Category: Operating Environments]]
[[Category: Atari]]

Installing NeXTSTEP on Qemu

2022-12-08T21:30:16Z

Neozeed: Updated download links since so many things are dead

This is my notes on installing [[NeXTSTEP]] onto Qemu. I had originally posted this on bsdnexus, however the links I had used for the graphics are nolonger working.

Please note that I’m not going to build an 'accelerated' version of [[Qemu]], I’m trying to keep this build as 'stable' as possible. I'm going to assume you know how to use vi. I would recommend trying the 0.9.0 before you try anything else. 0.8.0 seems somewhat unstable, and the busmouse driver doesn't work on 0.9.1 .

I've tried to keep links to QEMU up to date, but official site no longer carries the old stuff so it'll probably fall into disrepair eventually.

It is worth nothing that my Pentium 3 cannot start the GUI portion. I really don’t know why. (I did try -O1 for CFLAGS)

Also with regard to the NeXTSTEP part I'm using ISO images. I have just had too many problems with the physical media.

== Required Downloads ==

Download the following to c:\install\qemu-build

=== MinGW ===

from http://www.mingw.org/download.shtml

*[https://archive.org/download/qemuwin32-nextstep-mingw32/MinGW-5.1.4.exe MinGW-5.1.4.exe]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/MSYS-1.0.11-rc-1.exe MSYS-1.0.11-rc-1.exe]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/msysDTK-1.0.1.exe msysDTK-1.0.1.exe]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/gcc-core-3.4.5-20060117-3.tar.gz gcc-core-3.4.5-20060117-1.tar.gz]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/gcc-g++-3.4.5-20060117-3.tar.gz gcc-g++-3.4.5-20060117-1.tar.gz]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/w32api-3.13-mingw32-dev.tar.gz w32api-3.13-mingw32-dev.tar.gz]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/mingwrt-3.15.2-mingw32-dev.tar.gz mingwrt-3.15.2-mingw32-dev.tar.gz]

I've tried to mirror as close as I could to the versions that I built with... Since they are newer they may even work on Vista/7..

=== Aditional Dependancies ===

*[https://archive.org/download/qemuwin32-nextstep-mingw32/SDL-1.2.13.tar.gz SDL-1.2.13.tar.gz]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/zlib-1.2.5.tar.gz zlib-1.2.5.tar.gz]

=== Qemu ===

*[https://archive.org/download/qemuwin32-nextstep-mingw32/qemu-0.8.0.tar.gz qemu-0.8.0.tar.gz]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/qemu-0.9.0.tar.gz qemu-0.9.0.tar.gz]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/qemu/qemu-0.9.1.tar.gz qemu-0.9.1.tar.gz]

=== Boot diskette image for NeXTSTEP ===

*[https://archive.org/download/qemuwin32-nextstep-mingw32/3.3_Beta_Drivers.vfd 3.3_Beta_Drivers.floppyimage]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/3.3_Boot_Disk.vfd 3.3_Boot_Disk.floppyimage]
*[https://archive.org/download/qemuwin32-nextstep-mingw32/3.3_Core_Drivers.vfd 3.3_Core_Drivers.floppyimage]

=== Drivers for NeXTSTEP 3.3 ===

*[https://web.archive.org/web/20090817044058/http://www-teaching.physics.ox.ac.uk/NextStep/NE2K_driver.fdd NE2K_driver.fdd]
*[http://www.nextcomputers.org/NeXTfiles/Software/NEXTSTEP/Drivers/nextstep_3.3/released/CL_GD5434.pkg.compressed CL_GD5434.pkg.compressed]

== Busmouse patch ==

=== For Qemu 0.8.0 ===
[[Qemu-0.8.0-openstep-busmouse-2.diff]]

=== For Qemu 0.9.0 ===
[[Qemu-0.9.0-openstep-busmouse-2.diff]]

== Installation of the compiler environment ==
=== Installation of MinGW ===

*Install MinGW
Choose the 'current' version, then check the following options:
*MinGW Base tools
*G++ compiler
*MinGW make

Allow it to instal into c:\MinGW

=== Installation of MSYS ===
*install msys - default options

<pre>
Do you wish to continue with the post install? [yn ] y

Do you have MinGW installed? [yn ] y

Please answer the following in the form of c:/foo/bar.
Where is your MinGW installation? c:/mingw
</pre>

=== Installation of the msysDTK ===

*install msysDTK - default options

=== Installing gcc/g++ 3.4.5 ===
Start -> run -> mingw -> msys -> msys

<pre>
cd /mingw
tar -zxvf /c/install/qemu-build/w32api-3.13-mingw32-dev.tar.gz
tar -zxvf /c/install/qemu-build/mingwrt-3.15.2-mingw32-dev.tar.gz
</pre>

gcc -v should return:

<pre>
Reading specs from c:/mingw/bin/../lib/gcc/mingw32/3.4.5/specs
Configured with: ../gcc-3.4.5-20060117-3/configure --with-gcc --with-gnu-ld --wi
th-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --dis
able-nls --enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry --d
isable-shared --enable-sjlj-exceptions --enable-libgcj --disable-java-awt --with
out-x --enable-java-gc=boehm --disable-libgcj-debug --enable-interpreter --enabl
e-hash-synchronization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.5 (mingw-vista special r3)
</pre>

== Compilation ==

With the c compiler looking good, it's time to extract the dependancies for Qemu.

<pre>
cd /
mkdir -p /usr/src
cd /usr/src
</pre>

=== SDL ===

Extract and build SDL 1.2.13.
<pre>
tar -zxvf /c/install/qemu-build/SDL-1.2.13.tar.gz
cd SDL-1.2.13
./configure
make
make install
</pre>

=== zlib ===

Extract and build zlib
<pre>
cd /usr/src
tar -zxvf /c/install/qemu-build/zlib-1.2.3.tar.gz
./configure
make
make install
</pre>

=== Configuring Qemu ===

To compensate for qemu's configure, and some oddities in MinGW's handling of /usr/local you'll need to do some fixes..

<pre>
cd /mingw/include
ln -s /usr/local/include/zconf.h .
ln -s /usr/local/include/zlib.h .
ln -s /usr/local/include/SDL .
cd /mingw/lib
ln -s /usr/local/lib/libSDL.a .
ln -s /usr/local/lib/libz.a .
cd /bin
ln -s true.exe texi2html.exe
ln -s true.exe pod2man.exe
</pre>

==== qemu-0.8.0 NOTES ====

Extract Qemu and integrate the [[Qemu-0.8.0-openstep-busmouse-2.diff|patch]].
<pre>
cd /usr/src
tar -zxvf /c/install/qemu-build/qemu-0.8.0.tar.gz
cd qemu-0.8.0
cat /c/install/qemu-build/qemu-0.8.0-openstep-busmouse-2.diff | patch -p1
</pre>

Now configure Qemu
<pre>
./configure --target-list=i386-softmmu
make
</pre>

==== qemu-0.9.0 NOTES ====

Extract Qemu and integrate the [[Qemu-0.9.0-openstep-busmouse-2.diff|patch]].

<pre>
cd /usr/src
tar -zxvf /c/install/qemu-build/qemu-0.9.0.tar.gz
cd qemu-0.9.0
cat /c/install/qemu-build/qemu-0.9.0-openstep-busmouse-2.diff | patch -p1
</pre>

Now configure Qemu
<pre>
./configure --target-list=i386-softmmu
make
</pre>

So far this is the 'best' version of Qemu for NeXTSTEP.

==== qemu-0.9.1 NOTES ====

I've heard the reason this version will not work on Vista is something trivial:
<pre>
My patch to hw/ide.c:

just revert guess_disk_lchs function to the same from 0.9.0'.
</pre>

== Installing NeXTSETP ==

Ok now lets start with nextstep. Im going to populate a standalone copy of qemu

<pre>
mkdir /c/install/nextstep
mkdir /c/install/nextstep/keymaps
cp i386-softmmu/qemu /c/install/nextstep
cp keymaps/* /c/install/keymaps
cp /usr/local/bin/SDL.dll /c/install/nextstep
cp pc-bios/bios.bin /c/install/nextstep
cp pc-bios/vgabios-cirrus.bin /c/install/nextstep
</pre>

Lets create the 2 gig disk image..

<pre>
qemu-img create -f qcow /c/install/nextstep/ns33.qcow 2G
</pre>

Ok now here is the iso's that Im going to use in my c:\install directory:

<pre>
04/15/2006 09:10 PM 373,764,096 NeXTSTEP 3.3 User (m68k, i386).iso
04/15/2006 10:04 PM 1,474,560 3.3_Beta_Drivers.floppyimage
04/15/2006 10:04 PM 1,474,560 3.3_Boot_Disk.floppyimage
04/15/2006 10:04 PM 1,474,560 3.3_Core_Drivers.floppyimage
</pre>

Ok lets get started! Im using the cmd.exe so I can paste stuff in & out. Also I copy the disk images ontop of 'disk'
because some qemu hosts dont have the ctrl-alt-2 function...

<pre>
cd \install\nextstep
copy ..\3.3_Beta_Drivers.floppyimage beta
copy ..\3.3_Boot_Disk.floppyimage boot
copy ..\3.3_Core_Drivers.floppyimage core
copy boot disk
</pre>

== Launching Qemu Install ==

Now let's run Qemu like this:
<pre>
C:\install\nextstep>qemu.exe -L . -m 32 -hda ns33.qcow -cdrom "..\NeXTSTEP 3.3 User (m68k, i386).iso" -net nic,model=ne2k_pci -net user -soundhw sb16 -fda boot -boot a
</pre>

=== Step 1 ===
[[Image:NeXTSTEP install 1.png]]
<pre>
-v (enter)
</pre>

I like the verbose booting so I can see what is going on.

=== Step 2 ===
[[Image:NeXTSTEP install 2.png]]
<pre>
1 (enter)
</pre>

=== Step 3 ===
[[Image:NeXTSTEP install 3.png]]
<pre>
1 (enter)
</pre>

=== Step 4 ===
[[Image:NeXTSTEP install 4.png]]

It's time to copy the core disk onto 'disk' and press enter to continue. From a 2nd cmd.exe do a :
<pre>
copy core disk
(enter)
</pre>

=== Step 5 ===
[[Image:NeXTSTEP install 5.png]]

Time to copy the beta disk onto the 'disk' and press enter to continue. From the 2nd cmd.exe do a:
<pre>
copy beta disk
(enter)
</pre>

=== Step 6 ===
[[Image:NeXTSTEP install 6.png]]

Now this part of the disk is corrupt (its on all the beta 3.3 disks) so we have to select some scsi driver in order to get to the ATAPI. I choose #2
<pre>
2 (enter)
</pre>

=== Step 7 ===
[[Image:NeXTSTEP install 7.png]]

Now we can proceed to the ATAPI
<pre>
7 (enter)
</pre>

=== Step 8 ===
[[Image:NeXTSTEP install 8.png]]
<pre>
2 (enter)
</pre>

=== Step 9 ===
[[Image:NeXTSTEP install 9.png]]
<pre>
1 (enter)
</pre>

=== Step 10 ===
[[Image:NeXTSTEP install 10.png]]

NeXTSTEP kernel booting...

[[Image:NeXTSTEP install 11.png]]

NeXTSTEP kernel booting...

=== Step 12 ===
[[Image:NeXTSTEP install 12.png]]

I like the advanced install. So lets go with #2
<pre>
2 (enter)
</pre>

=== Step 13 ===
[[Image:NeXTSTEP install 13.png]]

We are going to install on the #1 (and only) disk
<pre>
1 (enter)
</pre>

=== Step 14 ===
[[Image:NeXTSTEP install 14.png]]

Since the ne2000 currently doesnt work, I want a small partition to copy files on & off the vm.
<pre>
2 (enter)
</pre>

=== Step 15 ===
[[Image:NeXTSTEP install 15.png]]

Lets go with 32 megabytes
<pre>
32 (enter)
</pre>

=== Step 16 ===
[[Image:NeXTSTEP install 16.png]]

Ok looks good!
<pre>
3 (enter)
</pre>

=== Step 17 ===
[[Image:NeXTSTEP install 17.png]]
<pre>
1 (enter)
</pre>

=== Step 18 ===
[[Image:NeXTSTEP install 18.png]]

Now the disk is being partitioned & formatted. This could take a minute.

=== Step 19 ===
[[Image:NeXTSTEP install 19.png]]

files are being copied.

=== Step 20 ===
[[Image:NeXTSTEP install 20.png]]

Ok we are done here. Press enter

<pre>
(enter)
</pre>

=== Step 21 ===
[[Image:NeXTSTEP install 21.png]]

Now at this point you can kill the emulator. For the sake of being 'easy' lets copy the core file back ontop of the 'disk'
Now we re-launch qemu as follows:

<pre>
C:\install\nextstep>qemu.exe -L . -m 32 -hda ns33.qcow -cdrom "..\NeXTSTEP 3.3 User (m68k, i386).iso" -net nic,model=ne2kpc -net user -soundhw sb16 -fda core
</pre>

=== Step 22 ===
[[Image:NeXTSTEP install 22.png]]

Again lets boot verbose
<pre>
-v (enter)
</pre>

=== Step 23 ===
[[Image:NeXTSTEP install 23.png]]
<pre>
1 (enter)
</pre>

=== Step 24 ===
[[Image:NeXTSTEP install 24.png]]

copy the beta onto disk.
<pre>
1 (enter)
</pre>

=== Step 25 ===
[[Image:NeXTSTEP install 25.png]]

=== Step 26 ===
[[Image:NeXTSTEP install 26.png]]
<pre>
(enter)
</pre>

copy core onto disk
<pre>
(enter)
</pre>

There may be an 'error' that it cannot mount the floppy.. Don't worry, just hit ok and try again and it'll work.

Click on the monitor (from the top). We are going to install the VGA driver for now.

Select the Default VGA Adapter (v3.30) and press the 'Add' button

Now sleect the mouse button (from the top), then select the "PS/2-Style Mouse (v3.30)". Click the remove button.

Now select the audio icon (the speaker icon from the top) and lets add the "Sound Blaster 16 (v3.30)" driver.

You will get a warning about an irq conflict, you can close it. (this is why we changed the sb16.c file from irq 5 (the busmouse) to irq7.

Select IRQ 7.

Now press the Done button.

press enter.
(enter)

At this point NeXTSTEP 3.3 is installed. Pressing enter will sync the disk & reboot the VM. Next you select your keyboard, and you are good to go.

Hopefully this has helped someone out there!

== Final Notes ==

After you install update #3 the keyboard will not work right.. you need to specify a keymap.

Here is how I like to run Qemu 0.9.0 for NeXTSTEP

<pre>
qemu -L . -m 32 -hda ns33.disk -boot c -net nic,model=ne2kpci -net user -soundhw sb16
</pre>

[[Category:Qemu]]
[[Category:QEMU Tutorials]]

OS/2

2022-04-22T11:17:58Z

Neozeed: /* Build 605 */

[[Image:OS2 1.x neonlogo.jpg|thumb|150px|right|OS/2's early logo]]

'''OS/2''' started as a collaborative effort between [[IBM]] and [[Microsoft]] to put together the next generation [[operating system]] for the [[IBM AT]] and [[PS/2]] machines.

Microsoft, famous for hedging bets, started the [[Windows]] project around the same time, as a low cost entry interface with rudimentary (cooperative) [[multitasking]].

Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and demanded the [[i286]] 16-bit version. Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller. Instead the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.

Microsoft leapt at the chance to formalize DOS extenders into [[DPMI]], and use it in Windows, cementing OS/2's 1.x inability to run DPMI programs. Microsoft was also upset that IBM locked them out of the graphical components of the OS, and that OS/2 worked BACKWARDS compared to Windows... the 0/0 in the screen coordinates is the bottom right, while everywhere else it's the top left..

There is a great writeup on the divorce on google's [http://groups.google.com/group/comp.os.ms-windows.misc/msg/d710490b745d5e5e usenet archive], or locally here [[Gordon Letwin OS/2 usenet post]]. There is also a perspective from an Autodesk programmer available [http://www.sibbald.com/windows/windows01.html here].

== Versions ==

=== 16 bit versions ===
All of these versions require an [[i286]] cpu, and an [[IBM AT]], or [[PS/2]] compatible computer. All of the 16bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever increasing prevalence of [[MS-DOS]] based applications. At the same time, the 16bit version supported swapping, DLL's, threads and preemptive multitasking. There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].

*1.0
[[Image:Microsoft OS2 1.0 - Heathkit Zenith OEM.jpg|thumb|right|150px|OS/2 1.0]]
This version was all textmode, and had an interface that was inspired from TopView. Although it could multitask, most people didn't realize it, as all programs ran full screen. It ran in 286 protected mode, except for the single "DOS" mode session. As a result all device drivers for OS/2 had to be able to run in real & protected mode. Until 1.3 all versions were released by OEM hardware vendors (Compaq, Zenith etc, along with IBM), this was normal practice for Microsoft at the time.

The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].

*1.1
[[Image:IBM OS2 1.1 full package.jpg|thumb|right|150px|OS/2 1.1 full package]]
OS/2 1.1 was released in 1988, and was the first version to include the Presentation Manager. It 'looked' identical to that of [[Windows 2.0]]. IBM OS/2 1.1 included the PM version of Borland Sidekick to fill in the gap of accessories for OS/2. While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2. Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the triple fault method of the 286.

*1.2
[[Image:IBM OS2 1.2 box cover.jpg|thumb|right|150px|OS/2 1.2 box]]
I think this version was released in September of 1988. This release was significant with the inclusion of the HPFS filesystem. HPFS was significantly faster then the aging FAT filesystem as it placed its tables in the middle of the disk, and it allowed for larger filesystems, long filenames and extended attributes. A later service pack allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c). From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.

OS/2 1.2 from IBM included the 'standard' edition, along with the EE or extended edition. The EE edition included basic communications capability (x.25, rs232 terminal), and a SQL database.

[[InfoWorld]] included an excellent review of OS/2 1.2 [http://books.google.com/books?id=1DsEAAAAMBAJ&lpg=PT79&dq=%22OS%2F2%201.2%22&pg=PT66#v=onepage&q=%22OS/2%201.2%22&f=false|here].

*1.21
I think this version was a Microsoft exclusive, and the final version that they were directly involved in.

*1.3
[[Image:Microsoft OS2 front.JPG|thumb|right|150px|Microsoft OS/2 1.3]]
This was the last version of the 16 bit OS/2 family. The 1.3 user interface resembled that of [[Windows 3.0]]. Microsoft did include a 32bit HPFS driver in their Lan Manager package which allowed for the fastest HPFS implementation prior to OS/2 2.0 & Windows NT 3.1

Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2. The beta included a copy of all of the applettes & games from Windows 3.0 that could run in the Presentation Manager of OS/2. These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2. Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released. You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].

Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product. Windows NT on the i386 platform included support for 16bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server. Since they all were text mode, they would run unmodified up through Windows 2000.

=== 32bit versions ===
All of these versions require an [[i386]] SX or better CPU running on either an [[IBM AT]] compatible motherboard, or the [[IBM PS/2]] 32bit machines.

==== OS/2 2.x ====

*2.0 LA (LA Internal revision 6.167 91-10-08)
[[Image:IBM OS2 2.0 LA cover.jpg|150px|thumb|right|OS/2 2.0 LA]]
This was the first 32bit version. It was released after the IBM/Microsoft divorce, and was strictly an IBM release. There was no seamless Windows in this release, and Win-OS/2 only featured Windows 3.0a in standard mode.

The LA version does not include 'seamless' WIN-OS/2 sessions, and much like OS/2 2.0 GA it does not support Windows's 386 enhanced mode. While it is possible to launch Windows in a Window the display corrupts and it is exceptionally unstable.

Attempting to use any production GA drivers will result in a kernel crash.

*2.0 GA (GA Internal revision 6.307 92-03-01)
[[Image:IBM OS2 2.0 cover.jpg|150px|thumb|right|OS/2 2.0]]
This release included [[Windows 3.0]] for use in Win OS/2. At the time of the release the Presentation Managers graphic drivers were still 16 bit, although a later service pack was released which included 32bit drivers. It's interesting to note that OS/2's market share was so low at this time, that OS/2 2.0 included the ability to load older 16bit device drivers as the kernel was still a hybrid 16bit/32bit kernel.

The GUI had radically changed from 1.3 to 2.0 as it now included the Workplace Shell, a full OO GUI. Many people considered WPS to be 'the' killer application at the time, as Windows still had the program manager.

The new Presentation Manager replacement, Workplace Shell, included a deal with Commodore for the "look and feel" of [[AmigaDOS]], and as part of the deal, Commodore picked up a license for [[REXX]] into its products as first seen by AmigaDOS 2.0 .

The default syslevel for OS/2 2.0 is XR02000. The last known service pack for OS/2 2.0 brings it up to XR06100. The XR06100 update also installs the OS/2 32-bit Graphics Engine, XR02010.

*2.1 (06/1993)
This release brought the Win OS/2 functionality up to [[Windows 3.1]]. From the user standpoint it still looked like 2.0 . OS/2 2.1 also included the multimedia update which would allow for sound effects for almost every conceivable motion. It was very annoying.

OS/2 2.1 also supported more video cards, more printers, and included support for [[PCMCIA]] and [[APM]], making it acceptable for laptop use.

The update XR06200 brings OS/2 2.1 up to 2.11 functionality.

*2.11 (02/1994)
*2.11 SMP (08/1994)

OS/2 2.11 supported multiple processors, and from a user standpoint it was halfway between 2.11 and Warp. I remember this version being insanely expensive, as it was targeted to the 'server' crowd, IBM had shortsightedly decided end users wouldn't want SMP. While [[Windows NT]] Workstation always supported two physical processors.

==== OS/2 Warp 3 ====
[[Image:IBM OS2 Warp 3.0 blue spine cover.jpg|150px|thumb|right|OS/2 Warp 3.0 BlueSpine]]
*3.0 (09/1994)
This was the WARP release. At the time this release preempted the [[Windows 95]] release. IBM had done their best to tune OS/2 to run in 4MB of ram on a 386sx cpu. Warp also included the 'bonus pack' which included SLIP/PPP TCP/IP, a dialer application and a word processor & spreadsheet. A simple gopher client & NNTP client were also included.

IMHO this is where IBM missed the boat, by making TCP/IP difficult to configure, and by not including LAN drivers (that was WARP CONNECT), while [[Windows 95]] & [[Windows_NT#Windows_NT_3.5|NT 3.5]] both included SLIP/PPP *AND* lan drivers.

I *THINK* it was this release that included the ability to run [[Win32s]], which was a boon for Netscape & Mosaic.

*3.01 (1995)
OS/2 Warp with Win-OS/2

*3.02 (1995)
OS/2 Warp Connect
OS/2 Warp Server
OS/2 Warp Server Advanced

*3.05 (01/1996)
OS/2 Warp Server Advanced for SMP

==== OS/2 Warp 4 ====
[[Image:logo-warp.gif|thumb|150px|right|OS/2 Warp Logo]]
*4.0
OS/2 4.0 included both Java and Netscape in this release. Sadly IBM had still not 'gotten it' with regards to TCP/IP and insisted on a 'connect' version of 4.0 that included the LAN drivers. 4.0 also included the ability to install servicepacks online.

*4.01
Workspace on-Demand 1.0 (WSOD)
Workspace on-Demand 2.0

*4.5
IBM OS/2 Warp Server for e-business
Fixpak >=13 applied to OS/2 Warp 4 or WSOD

*4.51
Aurora Convenience Package 1 (ACP1), Merlin Convenience Package 1 (MCP1)

*4.52
Aurora Convenience Package 2 (ACP2), Merlin Convenience Package 2 (MCP2)

This was the last IBM release of OS/2.

== PowerPC port ==

It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship. IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revelutionalized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run x86 code (albeit slow..) and then switch to PPC mode. The company [[NexGen]] opened up everyone's eyes that a specialized [[RISC]] cpu could in fact run x86 instructions much quicker then a real Intel cpu... This opened the way to the Pentium CPUs and effectivly killed the [[RISC]] revolution.

There is a most excellent review to be found [http://www.os2museum.com/wp/?page_id=30 here] that also includes screenshots.

== Running OS/2 under an Emulator ==

=== 16 bit versions ===
The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place. I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile. Be sure to limit the VM to 16MB of ram, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.

Right now the best solution is either [https://pcem-emulator.co.uk/ PCem] or [http://ci.86box.net/ 86Box]. With the appropriate [http://tinyurl.com/rs20170821 ROMS] it's possible to install onto an emulated 286/386 class based machine.

==== OS/2 1.0 ====
[[Image:OS2 1.0.png|thumb|200px|right|OS/2 1.0 under VirtualBOX]]
*First version from November 1987 - no success.
*There is a later 1987 version that does run, it may be an OS/2 1.1 beta?
It seems the 1.0 IBM kernels rely on 286 triple faults and Virtual Box does not emulate it. However there is an early Microsoft OS/2 1.1 beta that uses the 386 method of switching to protected mode, and will run on modern machines (as long as the speed fix in place.).

==== OS/2 1.1 ====
[[Image:OS2 1.1.jpg|thumb|200px|right|OS/2 1.1 under Bochs]]
There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines. Even without an emulator you'd need to do this on anything in pentium II speeds.. With the speed stuff in hand, you can now run 1.1 on VirtualBOX as it's floppy driver now works with OS/2 to detect speed/density correctly.

OS/2 1.1c is the first version that supports the 386's method of switching from [[protected mode]] to [[real mode]]. Prior to level c of OS/2 1.1 the method was a 286 [[triple fault]], which almost all emulators do not fully support, or it may simply be in the IBM versions. I'm still not sure as early versions of OS/2 are hard to track down.

==== OS/2 1.2 ====
[[Image:OS2 1.2.png|thumb|200px|right|OS/2 1.2 on VirtualBOX]]
With the above hex edits in place, OS/2 1.2 installs somewhat ok. The big 'issue' I found was that the IBM version of OS/2 1.2 does not support PS/2 mice on the IBM AT computers. However you can take the PS/2 driver from OS/2 1.3 and use it.

==== OS/2 1.21 ====
[[Image:OS2 1.21.png|thumb|200px|right|OS/2 1.21 on VirtualBOX]]
Again there is an issue of no included working mice drivers, and poaching the driver from 1.3 works fine.

==== OS/2 1.3 ====
[[Image:Os213.png|thumb|200px|right|OS/2 1.3 under Virtual PC.]]
The only version of OS/2 1.x that can run under an emulator without any hacks applied. The three problems that you will run into is emulated floppy disks are too quick, and other various timing anomalies that will lead to a COUNTRY.SYS failure.

The method for install requires you to install OS/2 1.3 on a physical machine, update it, then make a whole disk image of it. I can confirm that OS/2 1.3 runs under [[Virtual PC 2007]] just fine. While it does have some issues with the floppy (it'll throw an error reading the floppy every time you put in a new disk) it will allow you to use the floppy. This makes OS/2 1.3 the easiest to install programs into.

At the moment, none of the 1.x versions will install under emulation, they all must be imaged from a physical machine.

* [http://support.microsoft.com/kb/102628/en-us Microsoft OS/2 1.3 HCL]

=== 32 bit versions ===

==== OS/2 2.0 ====
OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce. As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'. Sadly many of these betas did not survive. There is 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.

===== Betas =====
These are the ones I currently have access to, or directly know about:

====== Microsoft Developer's Relase 1 ======
====== Microsoft Developer's Relase 2 ======

====== Build 123 ======
[[Image:OS2 2.0 6.123.png|thumb|200px|right|OS/2 2.0 Build 123 on 86Box.]]
The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the inport busmouse adapter, along with the generic VGA adapter.

This build is the 'divorce' edition when IBM started to ship the betas itself, this version uses the OS/2 1.2 Presentation Manager. The MS-DOS is built around MS-DOS 4.0 and includes no DPMI support at all.
You can read more about it [http://www.os2museum.com/wp/os-2-2-0-spring-91-edition/ on OS/2 Museum]. The disks can be downloaded from archive.org [[https://archive.org/details/os2-2.0-6.123 HERE]].

To install I used [[86box]] i486 Socket 2, IBM PS/ValuePoint 433DX/Si, with a Pentium OverDrive 63Mhz processor, and a 'type 9' disk setup on IDE. The mouse is set to PS/2 mode.

The kernel has the following version string:

Internal revision 6.123, 91/02/04 $

The Copyright dialog has this dated for 1990.

====== Build 605 ======
Not sure why it's build 605 as it way out of sequence. Perhaps they thought they were close to the end. This is one of the last Presentation Manager based releases. It can be downloaded from [[https://archive.org/details/os2-2.0-6.605 archive.org here]].

The kernel string reports as:

Internal revision 6.605, 91/09/11

The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in 89.

605 also introduced the minimal text setup spanning install disk 1-4, with the rest being setup under the Presentation Manager.

====== Build 177 ======
[[Image:OS2 2.0LA in VirtualBOX.png|thumb|200px|right|OS/2 2.0 LA running under VirtualBOX.]]

At the moment the only way I've been able to install OS/2 2.0 LA on Virtual PC/VirtualBOX is to 'cheat' and use the install & disk 1 from OS/2 2.0 GA, and replace the following files on disk1, from LA's disk 1:

*CMD.EXE
*HARDERR.EXE
*SYSINST1.EXE
*SYSINST2.EXE
*FDISK.COM
*SYSLEVEL.OS2
*DISK.NUM

Then boot from GA's install, then use it's disk 1. Then use LA's disk from that point onward, and it'll install.

====== Build 304 ======

===== GA =====
[[Image:OS2 2.0 in Qemu.png|thumb|200px|right|OS/2 2.0 running under Qemu.]]
[[Image:Vpc5x os2v20 wps.png|thumb|200px|right|OS/2 2.0 running under Virtual PC 5 for OS/2]]

I've run OS/2 2.0 & 4.0 under Virtual PC, and Qemu... I guess it really comes down to if you move disk images around between various hardware platforms. Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner... Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host pc. I've heard that VMWare has given up the compatibility mode fixes.

I'm now running OS/2 2.0 under VMWare Player, and it seems to be running OK. I've found one issue with networking, the Set PermaNet Server feature must be set to TRUE, under the LAPS configuration tool.

*[[Qemu]]
*[[Virtual PC 2007]]

==== OS/2 2.1 ====

Adds 32-bit Graphics Subsystem. S3 display drivers are usable under Virtual PC.

* [http://drivers.s3graphics.com/en/download/drivers/legacy/Trio64V_765/eng30316.zip eng30316.zip] S3 drivers

==== OS/2 Warp 3 ====
*For installation with XDF diskettes, Virtual PC works, however you'll need to use the floppy drivers & xdf driver from OS/2 4.0
*You should first apply the latest fixpak (XRGW040) to use Guest Additions from Virtual PC.
*After this also GRADD device drivers (from Additions, IBM or Scitech SNAP) can be installed.

==== OS/2 Warp 4 ====

Fixpak 5 or better 9 should be applied for GRADD.

==== OS/2 Warp Server for e-business (4.5) ====

Works with Virtual PC.

==== OS/2 Convenience Package 1 (4.51) ====

Works with Virtual PC.

==== OS/2 Convenience Package 2 (4.52) ====

Works with Virtual PC and VirtualBox.

== Popular Applications ==

=== Autodesk ===
* AutoCad

=== IBM ===
* IBM DisplayWrite5/2

=== Informix ===
* Wingz

=== Lotus ===
* Lotus 1-2-3/G
* Lotus Freelance Graphics

=== Micrografx ===
* Micrografx Designer 3.0
* Micrografx Draw for OS/2

=== Microsoft ===
Microsoft did port over a bunch of their languages, along with a few applications, namely:

* Languages
** Microsoft MASM 6.0
** Microsoft C 5.1, 6.0
** Microsoft COBOL PDS
** Microsoft Basic PDS 7.0, 7.1
** [[Microsoft Fortran]]
* Productivity
** Microsoft Word 5.0, 5.5
** Microsoft Word (for Presentation Manager) 1.1
** Microsoft Excel 2.2, 3.0

All of these products are 16 bit only. While there was two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.

=== StarDivision ===
* StarWriter 2.0 for OS/2
* StarOffice 3.0

=== Watcom ===
* Watcom C / C++
* Watcom Fortran 77
* Watcom SQL

[[Category: Microsoft Operating Systems]]

OS/2

2022-04-22T11:16:55Z

Neozeed: It's 605 not 603.

[[Image:OS2 1.x neonlogo.jpg|thumb|150px|right|OS/2's early logo]]

'''OS/2''' started as a collaborative effort between [[IBM]] and [[Microsoft]] to put together the next generation [[operating system]] for the [[IBM AT]] and [[PS/2]] machines.

Microsoft, famous for hedging bets, started the [[Windows]] project around the same time, as a low cost entry interface with rudimentary (cooperative) [[multitasking]].

Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and demanded the [[i286]] 16-bit version. Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller. Instead the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.

Microsoft leapt at the chance to formalize DOS extenders into [[DPMI]], and use it in Windows, cementing OS/2's 1.x inability to run DPMI programs. Microsoft was also upset that IBM locked them out of the graphical components of the OS, and that OS/2 worked BACKWARDS compared to Windows... the 0/0 in the screen coordinates is the bottom right, while everywhere else it's the top left..

There is a great writeup on the divorce on google's [http://groups.google.com/group/comp.os.ms-windows.misc/msg/d710490b745d5e5e usenet archive], or locally here [[Gordon Letwin OS/2 usenet post]]. There is also a perspective from an Autodesk programmer available [http://www.sibbald.com/windows/windows01.html here].

== Versions ==

=== 16 bit versions ===
All of these versions require an [[i286]] cpu, and an [[IBM AT]], or [[PS/2]] compatible computer. All of the 16bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever increasing prevalence of [[MS-DOS]] based applications. At the same time, the 16bit version supported swapping, DLL's, threads and preemptive multitasking. There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].

*1.0
[[Image:Microsoft OS2 1.0 - Heathkit Zenith OEM.jpg|thumb|right|150px|OS/2 1.0]]
This version was all textmode, and had an interface that was inspired from TopView. Although it could multitask, most people didn't realize it, as all programs ran full screen. It ran in 286 protected mode, except for the single "DOS" mode session. As a result all device drivers for OS/2 had to be able to run in real & protected mode. Until 1.3 all versions were released by OEM hardware vendors (Compaq, Zenith etc, along with IBM), this was normal practice for Microsoft at the time.

The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].

*1.1
[[Image:IBM OS2 1.1 full package.jpg|thumb|right|150px|OS/2 1.1 full package]]
OS/2 1.1 was released in 1988, and was the first version to include the Presentation Manager. It 'looked' identical to that of [[Windows 2.0]]. IBM OS/2 1.1 included the PM version of Borland Sidekick to fill in the gap of accessories for OS/2. While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2. Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the triple fault method of the 286.

*1.2
[[Image:IBM OS2 1.2 box cover.jpg|thumb|right|150px|OS/2 1.2 box]]
I think this version was released in September of 1988. This release was significant with the inclusion of the HPFS filesystem. HPFS was significantly faster then the aging FAT filesystem as it placed its tables in the middle of the disk, and it allowed for larger filesystems, long filenames and extended attributes. A later service pack allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c). From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.

OS/2 1.2 from IBM included the 'standard' edition, along with the EE or extended edition. The EE edition included basic communications capability (x.25, rs232 terminal), and a SQL database.

[[InfoWorld]] included an excellent review of OS/2 1.2 [http://books.google.com/books?id=1DsEAAAAMBAJ&lpg=PT79&dq=%22OS%2F2%201.2%22&pg=PT66#v=onepage&q=%22OS/2%201.2%22&f=false|here].

*1.21
I think this version was a Microsoft exclusive, and the final version that they were directly involved in.

*1.3
[[Image:Microsoft OS2 front.JPG|thumb|right|150px|Microsoft OS/2 1.3]]
This was the last version of the 16 bit OS/2 family. The 1.3 user interface resembled that of [[Windows 3.0]]. Microsoft did include a 32bit HPFS driver in their Lan Manager package which allowed for the fastest HPFS implementation prior to OS/2 2.0 & Windows NT 3.1

Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2. The beta included a copy of all of the applettes & games from Windows 3.0 that could run in the Presentation Manager of OS/2. These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2. Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released. You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].

Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product. Windows NT on the i386 platform included support for 16bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server. Since they all were text mode, they would run unmodified up through Windows 2000.

=== 32bit versions ===
All of these versions require an [[i386]] SX or better CPU running on either an [[IBM AT]] compatible motherboard, or the [[IBM PS/2]] 32bit machines.

==== OS/2 2.x ====

*2.0 LA (LA Internal revision 6.167 91-10-08)
[[Image:IBM OS2 2.0 LA cover.jpg|150px|thumb|right|OS/2 2.0 LA]]
This was the first 32bit version. It was released after the IBM/Microsoft divorce, and was strictly an IBM release. There was no seamless Windows in this release, and Win-OS/2 only featured Windows 3.0a in standard mode.

The LA version does not include 'seamless' WIN-OS/2 sessions, and much like OS/2 2.0 GA it does not support Windows's 386 enhanced mode. While it is possible to launch Windows in a Window the display corrupts and it is exceptionally unstable.

Attempting to use any production GA drivers will result in a kernel crash.

*2.0 GA (GA Internal revision 6.307 92-03-01)
[[Image:IBM OS2 2.0 cover.jpg|150px|thumb|right|OS/2 2.0]]
This release included [[Windows 3.0]] for use in Win OS/2. At the time of the release the Presentation Managers graphic drivers were still 16 bit, although a later service pack was released which included 32bit drivers. It's interesting to note that OS/2's market share was so low at this time, that OS/2 2.0 included the ability to load older 16bit device drivers as the kernel was still a hybrid 16bit/32bit kernel.

The GUI had radically changed from 1.3 to 2.0 as it now included the Workplace Shell, a full OO GUI. Many people considered WPS to be 'the' killer application at the time, as Windows still had the program manager.

The new Presentation Manager replacement, Workplace Shell, included a deal with Commodore for the "look and feel" of [[AmigaDOS]], and as part of the deal, Commodore picked up a license for [[REXX]] into its products as first seen by AmigaDOS 2.0 .

The default syslevel for OS/2 2.0 is XR02000. The last known service pack for OS/2 2.0 brings it up to XR06100. The XR06100 update also installs the OS/2 32-bit Graphics Engine, XR02010.

*2.1 (06/1993)
This release brought the Win OS/2 functionality up to [[Windows 3.1]]. From the user standpoint it still looked like 2.0 . OS/2 2.1 also included the multimedia update which would allow for sound effects for almost every conceivable motion. It was very annoying.

OS/2 2.1 also supported more video cards, more printers, and included support for [[PCMCIA]] and [[APM]], making it acceptable for laptop use.

The update XR06200 brings OS/2 2.1 up to 2.11 functionality.

*2.11 (02/1994)
*2.11 SMP (08/1994)

OS/2 2.11 supported multiple processors, and from a user standpoint it was halfway between 2.11 and Warp. I remember this version being insanely expensive, as it was targeted to the 'server' crowd, IBM had shortsightedly decided end users wouldn't want SMP. While [[Windows NT]] Workstation always supported two physical processors.

==== OS/2 Warp 3 ====
[[Image:IBM OS2 Warp 3.0 blue spine cover.jpg|150px|thumb|right|OS/2 Warp 3.0 BlueSpine]]
*3.0 (09/1994)
This was the WARP release. At the time this release preempted the [[Windows 95]] release. IBM had done their best to tune OS/2 to run in 4MB of ram on a 386sx cpu. Warp also included the 'bonus pack' which included SLIP/PPP TCP/IP, a dialer application and a word processor & spreadsheet. A simple gopher client & NNTP client were also included.

IMHO this is where IBM missed the boat, by making TCP/IP difficult to configure, and by not including LAN drivers (that was WARP CONNECT), while [[Windows 95]] & [[Windows_NT#Windows_NT_3.5|NT 3.5]] both included SLIP/PPP *AND* lan drivers.

I *THINK* it was this release that included the ability to run [[Win32s]], which was a boon for Netscape & Mosaic.

*3.01 (1995)
OS/2 Warp with Win-OS/2

*3.02 (1995)
OS/2 Warp Connect
OS/2 Warp Server
OS/2 Warp Server Advanced

*3.05 (01/1996)
OS/2 Warp Server Advanced for SMP

==== OS/2 Warp 4 ====
[[Image:logo-warp.gif|thumb|150px|right|OS/2 Warp Logo]]
*4.0
OS/2 4.0 included both Java and Netscape in this release. Sadly IBM had still not 'gotten it' with regards to TCP/IP and insisted on a 'connect' version of 4.0 that included the LAN drivers. 4.0 also included the ability to install servicepacks online.

*4.01
Workspace on-Demand 1.0 (WSOD)
Workspace on-Demand 2.0

*4.5
IBM OS/2 Warp Server for e-business
Fixpak >=13 applied to OS/2 Warp 4 or WSOD

*4.51
Aurora Convenience Package 1 (ACP1), Merlin Convenience Package 1 (MCP1)

*4.52
Aurora Convenience Package 2 (ACP2), Merlin Convenience Package 2 (MCP2)

This was the last IBM release of OS/2.

== PowerPC port ==

It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship. IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revelutionalized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run x86 code (albeit slow..) and then switch to PPC mode. The company [[NexGen]] opened up everyone's eyes that a specialized [[RISC]] cpu could in fact run x86 instructions much quicker then a real Intel cpu... This opened the way to the Pentium CPUs and effectivly killed the [[RISC]] revolution.

There is a most excellent review to be found [http://www.os2museum.com/wp/?page_id=30 here] that also includes screenshots.

== Running OS/2 under an Emulator ==

=== 16 bit versions ===
The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place. I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile. Be sure to limit the VM to 16MB of ram, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.

Right now the best solution is either [https://pcem-emulator.co.uk/ PCem] or [http://ci.86box.net/ 86Box]. With the appropriate [http://tinyurl.com/rs20170821 ROMS] it's possible to install onto an emulated 286/386 class based machine.

==== OS/2 1.0 ====
[[Image:OS2 1.0.png|thumb|200px|right|OS/2 1.0 under VirtualBOX]]
*First version from November 1987 - no success.
*There is a later 1987 version that does run, it may be an OS/2 1.1 beta?
It seems the 1.0 IBM kernels rely on 286 triple faults and Virtual Box does not emulate it. However there is an early Microsoft OS/2 1.1 beta that uses the 386 method of switching to protected mode, and will run on modern machines (as long as the speed fix in place.).

==== OS/2 1.1 ====
[[Image:OS2 1.1.jpg|thumb|200px|right|OS/2 1.1 under Bochs]]
There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines. Even without an emulator you'd need to do this on anything in pentium II speeds.. With the speed stuff in hand, you can now run 1.1 on VirtualBOX as it's floppy driver now works with OS/2 to detect speed/density correctly.

OS/2 1.1c is the first version that supports the 386's method of switching from [[protected mode]] to [[real mode]]. Prior to level c of OS/2 1.1 the method was a 286 [[triple fault]], which almost all emulators do not fully support, or it may simply be in the IBM versions. I'm still not sure as early versions of OS/2 are hard to track down.

==== OS/2 1.2 ====
[[Image:OS2 1.2.png|thumb|200px|right|OS/2 1.2 on VirtualBOX]]
With the above hex edits in place, OS/2 1.2 installs somewhat ok. The big 'issue' I found was that the IBM version of OS/2 1.2 does not support PS/2 mice on the IBM AT computers. However you can take the PS/2 driver from OS/2 1.3 and use it.

==== OS/2 1.21 ====
[[Image:OS2 1.21.png|thumb|200px|right|OS/2 1.21 on VirtualBOX]]
Again there is an issue of no included working mice drivers, and poaching the driver from 1.3 works fine.

==== OS/2 1.3 ====
[[Image:Os213.png|thumb|200px|right|OS/2 1.3 under Virtual PC.]]
The only version of OS/2 1.x that can run under an emulator without any hacks applied. The three problems that you will run into is emulated floppy disks are too quick, and other various timing anomalies that will lead to a COUNTRY.SYS failure.

The method for install requires you to install OS/2 1.3 on a physical machine, update it, then make a whole disk image of it. I can confirm that OS/2 1.3 runs under [[Virtual PC 2007]] just fine. While it does have some issues with the floppy (it'll throw an error reading the floppy every time you put in a new disk) it will allow you to use the floppy. This makes OS/2 1.3 the easiest to install programs into.

At the moment, none of the 1.x versions will install under emulation, they all must be imaged from a physical machine.

* [http://support.microsoft.com/kb/102628/en-us Microsoft OS/2 1.3 HCL]

=== 32 bit versions ===

==== OS/2 2.0 ====
OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce. As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'. Sadly many of these betas did not survive. There is 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.

===== Betas =====
These are the ones I currently have access to, or directly know about:

====== Microsoft Developer's Relase 1 ======
====== Microsoft Developer's Relase 2 ======

====== Build 123 ======
[[Image:OS2 2.0 6.123.png|thumb|200px|right|OS/2 2.0 Build 123 on 86Box.]]
The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the inport busmouse adapter, along with the generic VGA adapter.

This build is the 'divorce' edition when IBM started to ship the betas itself, this version uses the OS/2 1.2 Presentation Manager. The MS-DOS is built around MS-DOS 4.0 and includes no DPMI support at all.
You can read more about it [http://www.os2museum.com/wp/os-2-2-0-spring-91-edition/ on OS/2 Museum]. The disks can be downloaded from archive.org [[https://archive.org/details/os2-2.0-6.123 HERE]].

To install I used [[86box]] i486 Socket 2, IBM PS/ValuePoint 433DX/Si, with a Pentium OverDrive 63Mhz processor, and a 'type 9' disk setup on IDE. The mouse is set to PS/2 mode.

The kernel has the following version string:

Internal revision 6.123, 91/02/04 $

The Copyright dialog has this dated for 1990.

====== Build 605 ======
Not sure why it's build 605 as it way out of sequence. Perhaps they thought they were close to the end. This is one of the last Presentation Manager based releases. It can be downloaded from [[https://archive.org/details/os2-2.0-6.605 archive.org here]].

The kernel string reports as:

Internal revision 6.605, 91/09/11

The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in 89.

====== Build 177 ======
[[Image:OS2 2.0LA in VirtualBOX.png|thumb|200px|right|OS/2 2.0 LA running under VirtualBOX.]]

At the moment the only way I've been able to install OS/2 2.0 LA on Virtual PC/VirtualBOX is to 'cheat' and use the install & disk 1 from OS/2 2.0 GA, and replace the following files on disk1, from LA's disk 1:

*CMD.EXE
*HARDERR.EXE
*SYSINST1.EXE
*SYSINST2.EXE
*FDISK.COM
*SYSLEVEL.OS2
*DISK.NUM

Then boot from GA's install, then use it's disk 1. Then use LA's disk from that point onward, and it'll install.

====== Build 304 ======

===== GA =====
[[Image:OS2 2.0 in Qemu.png|thumb|200px|right|OS/2 2.0 running under Qemu.]]
[[Image:Vpc5x os2v20 wps.png|thumb|200px|right|OS/2 2.0 running under Virtual PC 5 for OS/2]]

I've run OS/2 2.0 & 4.0 under Virtual PC, and Qemu... I guess it really comes down to if you move disk images around between various hardware platforms. Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner... Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host pc. I've heard that VMWare has given up the compatibility mode fixes.

I'm now running OS/2 2.0 under VMWare Player, and it seems to be running OK. I've found one issue with networking, the Set PermaNet Server feature must be set to TRUE, under the LAPS configuration tool.

*[[Qemu]]
*[[Virtual PC 2007]]

==== OS/2 2.1 ====

Adds 32-bit Graphics Subsystem. S3 display drivers are usable under Virtual PC.

* [http://drivers.s3graphics.com/en/download/drivers/legacy/Trio64V_765/eng30316.zip eng30316.zip] S3 drivers

==== OS/2 Warp 3 ====
*For installation with XDF diskettes, Virtual PC works, however you'll need to use the floppy drivers & xdf driver from OS/2 4.0
*You should first apply the latest fixpak (XRGW040) to use Guest Additions from Virtual PC.
*After this also GRADD device drivers (from Additions, IBM or Scitech SNAP) can be installed.

==== OS/2 Warp 4 ====

Fixpak 5 or better 9 should be applied for GRADD.

==== OS/2 Warp Server for e-business (4.5) ====

Works with Virtual PC.

==== OS/2 Convenience Package 1 (4.51) ====

Works with Virtual PC.

==== OS/2 Convenience Package 2 (4.52) ====

Works with Virtual PC and VirtualBox.

== Popular Applications ==

=== Autodesk ===
* AutoCad

=== IBM ===
* IBM DisplayWrite5/2

=== Informix ===
* Wingz

=== Lotus ===
* Lotus 1-2-3/G
* Lotus Freelance Graphics

=== Micrografx ===
* Micrografx Designer 3.0
* Micrografx Draw for OS/2

=== Microsoft ===
Microsoft did port over a bunch of their languages, along with a few applications, namely:

* Languages
** Microsoft MASM 6.0
** Microsoft C 5.1, 6.0
** Microsoft COBOL PDS
** Microsoft Basic PDS 7.0, 7.1
** [[Microsoft Fortran]]
* Productivity
** Microsoft Word 5.0, 5.5
** Microsoft Word (for Presentation Manager) 1.1
** Microsoft Excel 2.2, 3.0

All of these products are 16 bit only. While there was two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.

=== StarDivision ===
* StarWriter 2.0 for OS/2
* StarOffice 3.0

=== Watcom ===
* Watcom C / C++
* Watcom Fortran 77
* Watcom SQL

[[Category: Microsoft Operating Systems]]

OS/2

2022-04-22T11:02:03Z

Neozeed: Update notes on 6.123

[[Image:OS2 1.x neonlogo.jpg|thumb|150px|right|OS/2's early logo]]

'''OS/2''' started as a collaborative effort between [[IBM]] and [[Microsoft]] to put together the next generation [[operating system]] for the [[IBM AT]] and [[PS/2]] machines.

Microsoft, famous for hedging bets, started the [[Windows]] project around the same time, as a low cost entry interface with rudimentary (cooperative) [[multitasking]].

Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and demanded the [[i286]] 16-bit version. Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller. Instead the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.

Microsoft leapt at the chance to formalize DOS extenders into [[DPMI]], and use it in Windows, cementing OS/2's 1.x inability to run DPMI programs. Microsoft was also upset that IBM locked them out of the graphical components of the OS, and that OS/2 worked BACKWARDS compared to Windows... the 0/0 in the screen coordinates is the bottom right, while everywhere else it's the top left..

There is a great writeup on the divorce on google's [http://groups.google.com/group/comp.os.ms-windows.misc/msg/d710490b745d5e5e usenet archive], or locally here [[Gordon Letwin OS/2 usenet post]]. There is also a perspective from an Autodesk programmer available [http://www.sibbald.com/windows/windows01.html here].

== Versions ==

=== 16 bit versions ===
All of these versions require an [[i286]] cpu, and an [[IBM AT]], or [[PS/2]] compatible computer. All of the 16bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever increasing prevalence of [[MS-DOS]] based applications. At the same time, the 16bit version supported swapping, DLL's, threads and preemptive multitasking. There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].

*1.0
[[Image:Microsoft OS2 1.0 - Heathkit Zenith OEM.jpg|thumb|right|150px|OS/2 1.0]]
This version was all textmode, and had an interface that was inspired from TopView. Although it could multitask, most people didn't realize it, as all programs ran full screen. It ran in 286 protected mode, except for the single "DOS" mode session. As a result all device drivers for OS/2 had to be able to run in real & protected mode. Until 1.3 all versions were released by OEM hardware vendors (Compaq, Zenith etc, along with IBM), this was normal practice for Microsoft at the time.

The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].

*1.1
[[Image:IBM OS2 1.1 full package.jpg|thumb|right|150px|OS/2 1.1 full package]]
OS/2 1.1 was released in 1988, and was the first version to include the Presentation Manager. It 'looked' identical to that of [[Windows 2.0]]. IBM OS/2 1.1 included the PM version of Borland Sidekick to fill in the gap of accessories for OS/2. While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2. Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the triple fault method of the 286.

*1.2
[[Image:IBM OS2 1.2 box cover.jpg|thumb|right|150px|OS/2 1.2 box]]
I think this version was released in September of 1988. This release was significant with the inclusion of the HPFS filesystem. HPFS was significantly faster then the aging FAT filesystem as it placed its tables in the middle of the disk, and it allowed for larger filesystems, long filenames and extended attributes. A later service pack allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c). From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.

OS/2 1.2 from IBM included the 'standard' edition, along with the EE or extended edition. The EE edition included basic communications capability (x.25, rs232 terminal), and a SQL database.

[[InfoWorld]] included an excellent review of OS/2 1.2 [http://books.google.com/books?id=1DsEAAAAMBAJ&lpg=PT79&dq=%22OS%2F2%201.2%22&pg=PT66#v=onepage&q=%22OS/2%201.2%22&f=false|here].

*1.21
I think this version was a Microsoft exclusive, and the final version that they were directly involved in.

*1.3
[[Image:Microsoft OS2 front.JPG|thumb|right|150px|Microsoft OS/2 1.3]]
This was the last version of the 16 bit OS/2 family. The 1.3 user interface resembled that of [[Windows 3.0]]. Microsoft did include a 32bit HPFS driver in their Lan Manager package which allowed for the fastest HPFS implementation prior to OS/2 2.0 & Windows NT 3.1

Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2. The beta included a copy of all of the applettes & games from Windows 3.0 that could run in the Presentation Manager of OS/2. These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2. Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released. You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].

Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product. Windows NT on the i386 platform included support for 16bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server. Since they all were text mode, they would run unmodified up through Windows 2000.

=== 32bit versions ===
All of these versions require an [[i386]] SX or better CPU running on either an [[IBM AT]] compatible motherboard, or the [[IBM PS/2]] 32bit machines.

==== OS/2 2.x ====

*2.0 LA (LA Internal revision 6.167 91-10-08)
[[Image:IBM OS2 2.0 LA cover.jpg|150px|thumb|right|OS/2 2.0 LA]]
This was the first 32bit version. It was released after the IBM/Microsoft divorce, and was strictly an IBM release. There was no seamless Windows in this release, and Win-OS/2 only featured Windows 3.0a in standard mode.

The LA version does not include 'seamless' WIN-OS/2 sessions, and much like OS/2 2.0 GA it does not support Windows's 386 enhanced mode. While it is possible to launch Windows in a Window the display corrupts and it is exceptionally unstable.

Attempting to use any production GA drivers will result in a kernel crash.

*2.0 GA (GA Internal revision 6.307 92-03-01)
[[Image:IBM OS2 2.0 cover.jpg|150px|thumb|right|OS/2 2.0]]
This release included [[Windows 3.0]] for use in Win OS/2. At the time of the release the Presentation Managers graphic drivers were still 16 bit, although a later service pack was released which included 32bit drivers. It's interesting to note that OS/2's market share was so low at this time, that OS/2 2.0 included the ability to load older 16bit device drivers as the kernel was still a hybrid 16bit/32bit kernel.

The GUI had radically changed from 1.3 to 2.0 as it now included the Workplace Shell, a full OO GUI. Many people considered WPS to be 'the' killer application at the time, as Windows still had the program manager.

The new Presentation Manager replacement, Workplace Shell, included a deal with Commodore for the "look and feel" of [[AmigaDOS]], and as part of the deal, Commodore picked up a license for [[REXX]] into its products as first seen by AmigaDOS 2.0 .

The default syslevel for OS/2 2.0 is XR02000. The last known service pack for OS/2 2.0 brings it up to XR06100. The XR06100 update also installs the OS/2 32-bit Graphics Engine, XR02010.

*2.1 (06/1993)
This release brought the Win OS/2 functionality up to [[Windows 3.1]]. From the user standpoint it still looked like 2.0 . OS/2 2.1 also included the multimedia update which would allow for sound effects for almost every conceivable motion. It was very annoying.

OS/2 2.1 also supported more video cards, more printers, and included support for [[PCMCIA]] and [[APM]], making it acceptable for laptop use.

The update XR06200 brings OS/2 2.1 up to 2.11 functionality.

*2.11 (02/1994)
*2.11 SMP (08/1994)

OS/2 2.11 supported multiple processors, and from a user standpoint it was halfway between 2.11 and Warp. I remember this version being insanely expensive, as it was targeted to the 'server' crowd, IBM had shortsightedly decided end users wouldn't want SMP. While [[Windows NT]] Workstation always supported two physical processors.

==== OS/2 Warp 3 ====
[[Image:IBM OS2 Warp 3.0 blue spine cover.jpg|150px|thumb|right|OS/2 Warp 3.0 BlueSpine]]
*3.0 (09/1994)
This was the WARP release. At the time this release preempted the [[Windows 95]] release. IBM had done their best to tune OS/2 to run in 4MB of ram on a 386sx cpu. Warp also included the 'bonus pack' which included SLIP/PPP TCP/IP, a dialer application and a word processor & spreadsheet. A simple gopher client & NNTP client were also included.

IMHO this is where IBM missed the boat, by making TCP/IP difficult to configure, and by not including LAN drivers (that was WARP CONNECT), while [[Windows 95]] & [[Windows_NT#Windows_NT_3.5|NT 3.5]] both included SLIP/PPP *AND* lan drivers.

I *THINK* it was this release that included the ability to run [[Win32s]], which was a boon for Netscape & Mosaic.

*3.01 (1995)
OS/2 Warp with Win-OS/2

*3.02 (1995)
OS/2 Warp Connect
OS/2 Warp Server
OS/2 Warp Server Advanced

*3.05 (01/1996)
OS/2 Warp Server Advanced for SMP

==== OS/2 Warp 4 ====
[[Image:logo-warp.gif|thumb|150px|right|OS/2 Warp Logo]]
*4.0
OS/2 4.0 included both Java and Netscape in this release. Sadly IBM had still not 'gotten it' with regards to TCP/IP and insisted on a 'connect' version of 4.0 that included the LAN drivers. 4.0 also included the ability to install servicepacks online.

*4.01
Workspace on-Demand 1.0 (WSOD)
Workspace on-Demand 2.0

*4.5
IBM OS/2 Warp Server for e-business
Fixpak >=13 applied to OS/2 Warp 4 or WSOD

*4.51
Aurora Convenience Package 1 (ACP1), Merlin Convenience Package 1 (MCP1)

*4.52
Aurora Convenience Package 2 (ACP2), Merlin Convenience Package 2 (MCP2)

This was the last IBM release of OS/2.

== PowerPC port ==

It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship. IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revelutionalized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run x86 code (albeit slow..) and then switch to PPC mode. The company [[NexGen]] opened up everyone's eyes that a specialized [[RISC]] cpu could in fact run x86 instructions much quicker then a real Intel cpu... This opened the way to the Pentium CPUs and effectivly killed the [[RISC]] revolution.

There is a most excellent review to be found [http://www.os2museum.com/wp/?page_id=30 here] that also includes screenshots.

== Running OS/2 under an Emulator ==

=== 16 bit versions ===
The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place. I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile. Be sure to limit the VM to 16MB of ram, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.

Right now the best solution is either [https://pcem-emulator.co.uk/ PCem] or [http://ci.86box.net/ 86Box]. With the appropriate [http://tinyurl.com/rs20170821 ROMS] it's possible to install onto an emulated 286/386 class based machine.

==== OS/2 1.0 ====
[[Image:OS2 1.0.png|thumb|200px|right|OS/2 1.0 under VirtualBOX]]
*First version from November 1987 - no success.
*There is a later 1987 version that does run, it may be an OS/2 1.1 beta?
It seems the 1.0 IBM kernels rely on 286 triple faults and Virtual Box does not emulate it. However there is an early Microsoft OS/2 1.1 beta that uses the 386 method of switching to protected mode, and will run on modern machines (as long as the speed fix in place.).

==== OS/2 1.1 ====
[[Image:OS2 1.1.jpg|thumb|200px|right|OS/2 1.1 under Bochs]]
There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines. Even without an emulator you'd need to do this on anything in pentium II speeds.. With the speed stuff in hand, you can now run 1.1 on VirtualBOX as it's floppy driver now works with OS/2 to detect speed/density correctly.

OS/2 1.1c is the first version that supports the 386's method of switching from [[protected mode]] to [[real mode]]. Prior to level c of OS/2 1.1 the method was a 286 [[triple fault]], which almost all emulators do not fully support, or it may simply be in the IBM versions. I'm still not sure as early versions of OS/2 are hard to track down.

==== OS/2 1.2 ====
[[Image:OS2 1.2.png|thumb|200px|right|OS/2 1.2 on VirtualBOX]]
With the above hex edits in place, OS/2 1.2 installs somewhat ok. The big 'issue' I found was that the IBM version of OS/2 1.2 does not support PS/2 mice on the IBM AT computers. However you can take the PS/2 driver from OS/2 1.3 and use it.

==== OS/2 1.21 ====
[[Image:OS2 1.21.png|thumb|200px|right|OS/2 1.21 on VirtualBOX]]
Again there is an issue of no included working mice drivers, and poaching the driver from 1.3 works fine.

==== OS/2 1.3 ====
[[Image:Os213.png|thumb|200px|right|OS/2 1.3 under Virtual PC.]]
The only version of OS/2 1.x that can run under an emulator without any hacks applied. The three problems that you will run into is emulated floppy disks are too quick, and other various timing anomalies that will lead to a COUNTRY.SYS failure.

The method for install requires you to install OS/2 1.3 on a physical machine, update it, then make a whole disk image of it. I can confirm that OS/2 1.3 runs under [[Virtual PC 2007]] just fine. While it does have some issues with the floppy (it'll throw an error reading the floppy every time you put in a new disk) it will allow you to use the floppy. This makes OS/2 1.3 the easiest to install programs into.

At the moment, none of the 1.x versions will install under emulation, they all must be imaged from a physical machine.

* [http://support.microsoft.com/kb/102628/en-us Microsoft OS/2 1.3 HCL]

=== 32 bit versions ===

==== OS/2 2.0 ====
OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce. As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'. Sadly many of these betas did not survive. There is 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.

===== Betas =====
These are the ones I currently have access to, or directly know about:

====== Microsoft Developer's Relase 1 ======
====== Microsoft Developer's Relase 2 ======

====== Build 123 ======
[[Image:OS2 2.0 6.123.png|thumb|200px|right|OS/2 2.0 Build 123 on 86Box.]]
The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the inport busmouse adapter, along with the generic VGA adapter.

This build is the 'divorce' edition when IBM started to ship the betas itself, this version uses the OS/2 1.2 Presentation Manager. The MS-DOS is built around MS-DOS 4.0 and includes no DPMI support at all.
You can read more about it [http://www.os2museum.com/wp/os-2-2-0-spring-91-edition/ on OS/2 Museum]. The disks can be downloaded from archive.org [[https://archive.org/details/os2-2.0-6.123 HERE]].

To install I used [[86box]] i486 Socket 2, IBM PS/ValuePoint 433DX/Si, with a Pentium OverDrive 63Mhz processor, and a 'type 9' disk setup on IDE. The mouse is set to PS/2 mode.

The kernel has the following version string:

Internal revision 6.123, 91/02/04 $

The Copyright dialog has this dated for 1990.

====== Build 603 ======
Not sure why it's build 603 as it way out of sequence. Perhaps they thought they were close to the end. This is one of the last Presentation Manager based releases.

====== Build 177 ======
[[Image:OS2 2.0LA in VirtualBOX.png|thumb|200px|right|OS/2 2.0 LA running under VirtualBOX.]]

At the moment the only way I've been able to install OS/2 2.0 LA on Virtual PC/VirtualBOX is to 'cheat' and use the install & disk 1 from OS/2 2.0 GA, and replace the following files on disk1, from LA's disk 1:

*CMD.EXE
*HARDERR.EXE
*SYSINST1.EXE
*SYSINST2.EXE
*FDISK.COM
*SYSLEVEL.OS2
*DISK.NUM

Then boot from GA's install, then use it's disk 1. Then use LA's disk from that point onward, and it'll install.

====== Build 304 ======

===== GA =====
[[Image:OS2 2.0 in Qemu.png|thumb|200px|right|OS/2 2.0 running under Qemu.]]
[[Image:Vpc5x os2v20 wps.png|thumb|200px|right|OS/2 2.0 running under Virtual PC 5 for OS/2]]

I've run OS/2 2.0 & 4.0 under Virtual PC, and Qemu... I guess it really comes down to if you move disk images around between various hardware platforms. Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner... Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host pc. I've heard that VMWare has given up the compatibility mode fixes.

I'm now running OS/2 2.0 under VMWare Player, and it seems to be running OK. I've found one issue with networking, the Set PermaNet Server feature must be set to TRUE, under the LAPS configuration tool.

*[[Qemu]]
*[[Virtual PC 2007]]

==== OS/2 2.1 ====

Adds 32-bit Graphics Subsystem. S3 display drivers are usable under Virtual PC.

* [http://drivers.s3graphics.com/en/download/drivers/legacy/Trio64V_765/eng30316.zip eng30316.zip] S3 drivers

==== OS/2 Warp 3 ====
*For installation with XDF diskettes, Virtual PC works, however you'll need to use the floppy drivers & xdf driver from OS/2 4.0
*You should first apply the latest fixpak (XRGW040) to use Guest Additions from Virtual PC.
*After this also GRADD device drivers (from Additions, IBM or Scitech SNAP) can be installed.

==== OS/2 Warp 4 ====

Fixpak 5 or better 9 should be applied for GRADD.

==== OS/2 Warp Server for e-business (4.5) ====

Works with Virtual PC.

==== OS/2 Convenience Package 1 (4.51) ====

Works with Virtual PC.

==== OS/2 Convenience Package 2 (4.52) ====

Works with Virtual PC and VirtualBox.

== Popular Applications ==

=== Autodesk ===
* AutoCad

=== IBM ===
* IBM DisplayWrite5/2

=== Informix ===
* Wingz

=== Lotus ===
* Lotus 1-2-3/G
* Lotus Freelance Graphics

=== Micrografx ===
* Micrografx Designer 3.0
* Micrografx Draw for OS/2

=== Microsoft ===
Microsoft did port over a bunch of their languages, along with a few applications, namely:

* Languages
** Microsoft MASM 6.0
** Microsoft C 5.1, 6.0
** Microsoft COBOL PDS
** Microsoft Basic PDS 7.0, 7.1
** [[Microsoft Fortran]]
* Productivity
** Microsoft Word 5.0, 5.5
** Microsoft Word (for Presentation Manager) 1.1
** Microsoft Excel 2.2, 3.0

All of these products are 16 bit only. While there was two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.

=== StarDivision ===
* StarWriter 2.0 for OS/2
* StarOffice 3.0

=== Watcom ===
* Watcom C / C++
* Watcom Fortran 77
* Watcom SQL

[[Category: Microsoft Operating Systems]]

OS/2

2022-04-22T07:02:06Z

Neozeed: Getting ready to add details into the known 2.00's

[[Image:OS2 1.x neonlogo.jpg|thumb|150px|right|OS/2's early logo]]

'''OS/2''' started as a collaborative effort between [[IBM]] and [[Microsoft]] to put together the next generation [[operating system]] for the [[IBM AT]] and [[PS/2]] machines.

Microsoft, famous for hedging bets, started the [[Windows]] project around the same time, as a low cost entry interface with rudimentary (cooperative) [[multitasking]].

Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and demanded the [[i286]] 16-bit version. Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller. Instead the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.

Microsoft leapt at the chance to formalize DOS extenders into [[DPMI]], and use it in Windows, cementing OS/2's 1.x inability to run DPMI programs. Microsoft was also upset that IBM locked them out of the graphical components of the OS, and that OS/2 worked BACKWARDS compared to Windows... the 0/0 in the screen coordinates is the bottom right, while everywhere else it's the top left..

There is a great writeup on the divorce on google's [http://groups.google.com/group/comp.os.ms-windows.misc/msg/d710490b745d5e5e usenet archive], or locally here [[Gordon Letwin OS/2 usenet post]]. There is also a perspective from an Autodesk programmer available [http://www.sibbald.com/windows/windows01.html here].

== Versions ==

=== 16 bit versions ===
All of these versions require an [[i286]] cpu, and an [[IBM AT]], or [[PS/2]] compatible computer. All of the 16bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever increasing prevalence of [[MS-DOS]] based applications. At the same time, the 16bit version supported swapping, DLL's, threads and preemptive multitasking. There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].

*1.0
[[Image:Microsoft OS2 1.0 - Heathkit Zenith OEM.jpg|thumb|right|150px|OS/2 1.0]]
This version was all textmode, and had an interface that was inspired from TopView. Although it could multitask, most people didn't realize it, as all programs ran full screen. It ran in 286 protected mode, except for the single "DOS" mode session. As a result all device drivers for OS/2 had to be able to run in real & protected mode. Until 1.3 all versions were released by OEM hardware vendors (Compaq, Zenith etc, along with IBM), this was normal practice for Microsoft at the time.

The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].

*1.1
[[Image:IBM OS2 1.1 full package.jpg|thumb|right|150px|OS/2 1.1 full package]]
OS/2 1.1 was released in 1988, and was the first version to include the Presentation Manager. It 'looked' identical to that of [[Windows 2.0]]. IBM OS/2 1.1 included the PM version of Borland Sidekick to fill in the gap of accessories for OS/2. While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2. Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the triple fault method of the 286.

*1.2
[[Image:IBM OS2 1.2 box cover.jpg|thumb|right|150px|OS/2 1.2 box]]
I think this version was released in September of 1988. This release was significant with the inclusion of the HPFS filesystem. HPFS was significantly faster then the aging FAT filesystem as it placed its tables in the middle of the disk, and it allowed for larger filesystems, long filenames and extended attributes. A later service pack allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c). From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.

OS/2 1.2 from IBM included the 'standard' edition, along with the EE or extended edition. The EE edition included basic communications capability (x.25, rs232 terminal), and a SQL database.

[[InfoWorld]] included an excellent review of OS/2 1.2 [http://books.google.com/books?id=1DsEAAAAMBAJ&lpg=PT79&dq=%22OS%2F2%201.2%22&pg=PT66#v=onepage&q=%22OS/2%201.2%22&f=false|here].

*1.21
I think this version was a Microsoft exclusive, and the final version that they were directly involved in.

*1.3
[[Image:Microsoft OS2 front.JPG|thumb|right|150px|Microsoft OS/2 1.3]]
This was the last version of the 16 bit OS/2 family. The 1.3 user interface resembled that of [[Windows 3.0]]. Microsoft did include a 32bit HPFS driver in their Lan Manager package which allowed for the fastest HPFS implementation prior to OS/2 2.0 & Windows NT 3.1

Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2. The beta included a copy of all of the applettes & games from Windows 3.0 that could run in the Presentation Manager of OS/2. These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2. Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released. You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].

Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product. Windows NT on the i386 platform included support for 16bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server. Since they all were text mode, they would run unmodified up through Windows 2000.

=== 32bit versions ===
All of these versions require an [[i386]] SX or better CPU running on either an [[IBM AT]] compatible motherboard, or the [[IBM PS/2]] 32bit machines.

==== OS/2 2.x ====

*2.0 LA (LA Internal revision 6.167 91-10-08)
[[Image:IBM OS2 2.0 LA cover.jpg|150px|thumb|right|OS/2 2.0 LA]]
This was the first 32bit version. It was released after the IBM/Microsoft divorce, and was strictly an IBM release. There was no seamless Windows in this release, and Win-OS/2 only featured Windows 3.0a in standard mode.

The LA version does not include 'seamless' WIN-OS/2 sessions, and much like OS/2 2.0 GA it does not support Windows's 386 enhanced mode. While it is possible to launch Windows in a Window the display corrupts and it is exceptionally unstable.

Attempting to use any production GA drivers will result in a kernel crash.

*2.0 GA (GA Internal revision 6.307 92-03-01)
[[Image:IBM OS2 2.0 cover.jpg|150px|thumb|right|OS/2 2.0]]
This release included [[Windows 3.0]] for use in Win OS/2. At the time of the release the Presentation Managers graphic drivers were still 16 bit, although a later service pack was released which included 32bit drivers. It's interesting to note that OS/2's market share was so low at this time, that OS/2 2.0 included the ability to load older 16bit device drivers as the kernel was still a hybrid 16bit/32bit kernel.

The GUI had radically changed from 1.3 to 2.0 as it now included the Workplace Shell, a full OO GUI. Many people considered WPS to be 'the' killer application at the time, as Windows still had the program manager.

The new Presentation Manager replacement, Workplace Shell, included a deal with Commodore for the "look and feel" of [[AmigaDOS]], and as part of the deal, Commodore picked up a license for [[REXX]] into its products as first seen by AmigaDOS 2.0 .

The default syslevel for OS/2 2.0 is XR02000. The last known service pack for OS/2 2.0 brings it up to XR06100. The XR06100 update also installs the OS/2 32-bit Graphics Engine, XR02010.

*2.1 (06/1993)
This release brought the Win OS/2 functionality up to [[Windows 3.1]]. From the user standpoint it still looked like 2.0 . OS/2 2.1 also included the multimedia update which would allow for sound effects for almost every conceivable motion. It was very annoying.

OS/2 2.1 also supported more video cards, more printers, and included support for [[PCMCIA]] and [[APM]], making it acceptable for laptop use.

The update XR06200 brings OS/2 2.1 up to 2.11 functionality.

*2.11 (02/1994)
*2.11 SMP (08/1994)

OS/2 2.11 supported multiple processors, and from a user standpoint it was halfway between 2.11 and Warp. I remember this version being insanely expensive, as it was targeted to the 'server' crowd, IBM had shortsightedly decided end users wouldn't want SMP. While [[Windows NT]] Workstation always supported two physical processors.

==== OS/2 Warp 3 ====
[[Image:IBM OS2 Warp 3.0 blue spine cover.jpg|150px|thumb|right|OS/2 Warp 3.0 BlueSpine]]
*3.0 (09/1994)
This was the WARP release. At the time this release preempted the [[Windows 95]] release. IBM had done their best to tune OS/2 to run in 4MB of ram on a 386sx cpu. Warp also included the 'bonus pack' which included SLIP/PPP TCP/IP, a dialer application and a word processor & spreadsheet. A simple gopher client & NNTP client were also included.

IMHO this is where IBM missed the boat, by making TCP/IP difficult to configure, and by not including LAN drivers (that was WARP CONNECT), while [[Windows 95]] & [[Windows_NT#Windows_NT_3.5|NT 3.5]] both included SLIP/PPP *AND* lan drivers.

I *THINK* it was this release that included the ability to run [[Win32s]], which was a boon for Netscape & Mosaic.

*3.01 (1995)
OS/2 Warp with Win-OS/2

*3.02 (1995)
OS/2 Warp Connect
OS/2 Warp Server
OS/2 Warp Server Advanced

*3.05 (01/1996)
OS/2 Warp Server Advanced for SMP

==== OS/2 Warp 4 ====
[[Image:logo-warp.gif|thumb|150px|right|OS/2 Warp Logo]]
*4.0
OS/2 4.0 included both Java and Netscape in this release. Sadly IBM had still not 'gotten it' with regards to TCP/IP and insisted on a 'connect' version of 4.0 that included the LAN drivers. 4.0 also included the ability to install servicepacks online.

*4.01
Workspace on-Demand 1.0 (WSOD)
Workspace on-Demand 2.0

*4.5
IBM OS/2 Warp Server for e-business
Fixpak >=13 applied to OS/2 Warp 4 or WSOD

*4.51
Aurora Convenience Package 1 (ACP1), Merlin Convenience Package 1 (MCP1)

*4.52
Aurora Convenience Package 2 (ACP2), Merlin Convenience Package 2 (MCP2)

This was the last IBM release of OS/2.

== PowerPC port ==

It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship. IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revelutionalized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run x86 code (albeit slow..) and then switch to PPC mode. The company [[NexGen]] opened up everyone's eyes that a specialized [[RISC]] cpu could in fact run x86 instructions much quicker then a real Intel cpu... This opened the way to the Pentium CPUs and effectivly killed the [[RISC]] revolution.

There is a most excellent review to be found [http://www.os2museum.com/wp/?page_id=30 here] that also includes screenshots.

== Running OS/2 under an Emulator ==

=== 16 bit versions ===
The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place. I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile. Be sure to limit the VM to 16MB of ram, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.

Right now the best solution is either [https://pcem-emulator.co.uk/ PCem] or [http://ci.86box.net/ 86Box]. With the appropriate [http://tinyurl.com/rs20170821 ROMS] it's possible to install onto an emulated 286/386 class based machine.

==== OS/2 1.0 ====
[[Image:OS2 1.0.png|thumb|200px|right|OS/2 1.0 under VirtualBOX]]
*First version from November 1987 - no success.
*There is a later 1987 version that does run, it may be an OS/2 1.1 beta?
It seems the 1.0 IBM kernels rely on 286 triple faults and Virtual Box does not emulate it. However there is an early Microsoft OS/2 1.1 beta that uses the 386 method of switching to protected mode, and will run on modern machines (as long as the speed fix in place.).

==== OS/2 1.1 ====
[[Image:OS2 1.1.jpg|thumb|200px|right|OS/2 1.1 under Bochs]]
There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines. Even without an emulator you'd need to do this on anything in pentium II speeds.. With the speed stuff in hand, you can now run 1.1 on VirtualBOX as it's floppy driver now works with OS/2 to detect speed/density correctly.

OS/2 1.1c is the first version that supports the 386's method of switching from [[protected mode]] to [[real mode]]. Prior to level c of OS/2 1.1 the method was a 286 [[triple fault]], which almost all emulators do not fully support, or it may simply be in the IBM versions. I'm still not sure as early versions of OS/2 are hard to track down.

==== OS/2 1.2 ====
[[Image:OS2 1.2.png|thumb|200px|right|OS/2 1.2 on VirtualBOX]]
With the above hex edits in place, OS/2 1.2 installs somewhat ok. The big 'issue' I found was that the IBM version of OS/2 1.2 does not support PS/2 mice on the IBM AT computers. However you can take the PS/2 driver from OS/2 1.3 and use it.

==== OS/2 1.21 ====
[[Image:OS2 1.21.png|thumb|200px|right|OS/2 1.21 on VirtualBOX]]
Again there is an issue of no included working mice drivers, and poaching the driver from 1.3 works fine.

==== OS/2 1.3 ====
[[Image:Os213.png|thumb|200px|right|OS/2 1.3 under Virtual PC.]]
The only version of OS/2 1.x that can run under an emulator without any hacks applied. The three problems that you will run into is emulated floppy disks are too quick, and other various timing anomalies that will lead to a COUNTRY.SYS failure.

The method for install requires you to install OS/2 1.3 on a physical machine, update it, then make a whole disk image of it. I can confirm that OS/2 1.3 runs under [[Virtual PC 2007]] just fine. While it does have some issues with the floppy (it'll throw an error reading the floppy every time you put in a new disk) it will allow you to use the floppy. This makes OS/2 1.3 the easiest to install programs into.

At the moment, none of the 1.x versions will install under emulation, they all must be imaged from a physical machine.

* [http://support.microsoft.com/kb/102628/en-us Microsoft OS/2 1.3 HCL]

=== 32 bit versions ===

==== OS/2 2.0 ====
OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce. As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'. Sadly many of these betas did not survive. There is 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.

===== Betas =====
These are the ones I currently have access to, or directly know about:

====== Microsoft Developer's Relase 1 ======
====== Microsoft Developer's Relase 2 ======

====== Build 123 ======
[[Image:OS2 2.0 6.123.png|thumb|200px|right|OS/2 2.0 Build 123 on 86Box.]]
The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the inport busmouse adapter, along with the generic VGA adapter.

This build is the 'divorce' edition when IBM started to ship the betas itself, this version uses the OS/2 1.2 Presentation Manager. The MS-DOS is built around MS-DOS 4.0 and includes no DPMI support at all.
You can read more about it [http://www.os2museum.com/wp/os-2-2-0-spring-91-edition/ on OS/2 Museum].

====== Build 603 ======
Not sure why it's build 603 as it way out of sequence. Perhaps they thought they were close to the end. This is one of the last Presentation Manager based releases.

====== Build 177 ======
[[Image:OS2 2.0LA in VirtualBOX.png|thumb|200px|right|OS/2 2.0 LA running under VirtualBOX.]]

At the moment the only way I've been able to install OS/2 2.0 LA on Virtual PC/VirtualBOX is to 'cheat' and use the install & disk 1 from OS/2 2.0 GA, and replace the following files on disk1, from LA's disk 1:

*CMD.EXE
*HARDERR.EXE
*SYSINST1.EXE
*SYSINST2.EXE
*FDISK.COM
*SYSLEVEL.OS2
*DISK.NUM

Then boot from GA's install, then use it's disk 1. Then use LA's disk from that point onward, and it'll install.

====== Build 304 ======

===== GA =====
[[Image:OS2 2.0 in Qemu.png|thumb|200px|right|OS/2 2.0 running under Qemu.]]
[[Image:Vpc5x os2v20 wps.png|thumb|200px|right|OS/2 2.0 running under Virtual PC 5 for OS/2]]

I've run OS/2 2.0 & 4.0 under Virtual PC, and Qemu... I guess it really comes down to if you move disk images around between various hardware platforms. Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner... Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host pc. I've heard that VMWare has given up the compatibility mode fixes.

I'm now running OS/2 2.0 under VMWare Player, and it seems to be running OK. I've found one issue with networking, the Set PermaNet Server feature must be set to TRUE, under the LAPS configuration tool.

*[[Qemu]]
*[[Virtual PC 2007]]

==== OS/2 2.1 ====

Adds 32-bit Graphics Subsystem. S3 display drivers are usable under Virtual PC.

* [http://drivers.s3graphics.com/en/download/drivers/legacy/Trio64V_765/eng30316.zip eng30316.zip] S3 drivers

==== OS/2 Warp 3 ====
*For installation with XDF diskettes, Virtual PC works, however you'll need to use the floppy drivers & xdf driver from OS/2 4.0
*You should first apply the latest fixpak (XRGW040) to use Guest Additions from Virtual PC.
*After this also GRADD device drivers (from Additions, IBM or Scitech SNAP) can be installed.

==== OS/2 Warp 4 ====

Fixpak 5 or better 9 should be applied for GRADD.

==== OS/2 Warp Server for e-business (4.5) ====

Works with Virtual PC.

==== OS/2 Convenience Package 1 (4.51) ====

Works with Virtual PC.

==== OS/2 Convenience Package 2 (4.52) ====

Works with Virtual PC and VirtualBox.

== Popular Applications ==

=== Autodesk ===
* AutoCad

=== IBM ===
* IBM DisplayWrite5/2

=== Informix ===
* Wingz

=== Lotus ===
* Lotus 1-2-3/G
* Lotus Freelance Graphics

=== Micrografx ===
* Micrografx Designer 3.0
* Micrografx Draw for OS/2

=== Microsoft ===
Microsoft did port over a bunch of their languages, along with a few applications, namely:

* Languages
** Microsoft MASM 6.0
** Microsoft C 5.1, 6.0
** Microsoft COBOL PDS
** Microsoft Basic PDS 7.0, 7.1
** [[Microsoft Fortran]]
* Productivity
** Microsoft Word 5.0, 5.5
** Microsoft Word (for Presentation Manager) 1.1
** Microsoft Excel 2.2, 3.0

All of these products are 16 bit only. While there was two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.

=== StarDivision ===
* StarWriter 2.0 for OS/2
* StarOffice 3.0

=== Watcom ===
* Watcom C / C++
* Watcom Fortran 77
* Watcom SQL

[[Category: Microsoft Operating Systems]]

Talk:Installing 4.3 BSD Quasijarus on SIMH

2021-09-19T13:52:01Z

Neozeed:

==Disk label I/O error==

I get this:

<pre>
=copy
cpu: uVAX II
From: tms(0,1)
To: ra(0,1)
ra: I/O error
ra(0,0,0,1): can't read disk label
To:
</pre>
[[User:Larsbrinkhoff|Larsbrinkhoff]] ([[User talk:Larsbrinkhoff|talk]]) 09:45, 6 September 2021 (CEST)
: Apparently this is due to running on a MicroVAX II rather than 3900. [[User:Larsbrinkhoff|Larsbrinkhoff]] ([[User talk:Larsbrinkhoff|talk]]) 09:49, 6 September 2021 (CEST)

Looks like the disk / bus interface didn’t exist …

Next time post the ini and which emulator

I went ahead with a test from 3.8-1 from a million years ago... I didnt create the disk image, just attached the premade tape:

<pre>
C:\Users\jsteve\Downloads\vax>vax i.ini

VAX simulator V3.8-1
RQ: creating new file
Loading boot code from ka655x.bin

�[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot mua0:
(BOOT/R5:0 MUA0

2..
-MUA0
1..0..

copy
cpu: uVAX 3000
From: tms(0,1)
To: ra(0,1)
ra0: unlabeled
Copy completed: 308 records copied

HALT instruction, PC: 00000006 (HALT)
sim>
</pre>

I grabbed the latest 'backport' and it wont init the rom

<pre>
jsteve@JaybirdDC:~/simh/sim/BIN$ ./vax

VAX simulator V3.11-0
sim> boot cpu
Loading boot code from ka655x.bin
</pre>

and the usual distro crap

<pre>
root@JaybirdDC:~# uname -a
Linux JaybirdDC 4.4.0-17763-Microsoft #1432-Microsoft Mon Aug 18 18:18:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux
root@JaybirdDC:~# cc -v
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
root@JaybirdDC:~# cat /etc/issue
Ubuntu 20.04 LTS \n \l
</pre>

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 11:37, 19 September 2021 (CEST)

Talk:Installing 4.3 BSD Quasijarus on SIMH

2021-09-19T09:37:33Z

Neozeed: /* Disk label I/O error */

A/UX

2021-09-08T12:44:03Z

Neozeed: add some A/UX instructions

{{Infobox OS
| image = softpc-on-aux.png
| caption = A/UX 3.0.0 desktop
| name = A/UX
| creator = Apple/UniSoft
| current version = 3.11
| year introduced = 1988
| type = Multitasking, multiuser
| architecture = [[Macintosh]]
}}

After [[Steve Jobs]] left [[Apple]], they scrambled to put together a system that could compete with [[NeXT]]. Hearing that NeXT was going to enter the [[UNIX|Unix]] [[workstation]] market, Apple commissioned [[UniSoft]] to help port [[SYSVr2]] to its [[Macintosh II]] lineup.

== Significant Versions ==
=== 0.7 ===
[[Image:AUX 0.7 desktop.png|thumb|right|150px|A/UX 0.7's UI]]
This version is more infamous because it included the source code to the kernel, which can be built with a little bit of work. There is no real Toolbox in this version, but rather a bare minimal SYSV port. This version uses a SYSV filesystem, while later versions of A/UX used 4.2BSD's FFS.
=== 1.1.1 ===
[[Image:AUX 1.1.1 desktop.png|thumb|right|150px|A/UX 1.1.1's GUI]]
This is a super barebones version, the toolbox is barely able to run the terminal application and some simple desktop widgets.
=== 2.0 ===
[[Image:AUX 2.0 desktop.png|thumb|right|150px|A/UX 2.0's GUI]]
Version 2.0 is more polished, and able to run a finder that is more parallel to [[System 6]].
=== 3.0 ===
[[Image:AUX 3.0 desktop.png|thumb|right|150px|A/UX 3.0's GUI]]
This is the best version to get ahold of. 3.0 emulates a [[System 7|System 7.0.1]] environment.
=== 3.1.1 ===
This version was the final released version, in 1995
=== 4.0 ===
This version was announced, and abandoned in 1996

== How do I get this to run?! ==

=== Physical Hardware ===
You will need an actual [[Macintosh]] that is supported. The best machines are the Quadra series. Note, not all Quadras will run A/UX.

The supported Macintosh Machines:
* A/UX 1.0 ~ A/UX 2.0
[ 68020 w/PMMU, 68030 ]
* Macintosh II, Rev B, with a 68851 PMMU
* Macintosh SE/30
* Macintosh IIx, IIcx, IIsi, IIci, IIfx

A/UX 3.0 ~ A/UX 3.1.1
[ 68040 ]
* Centris 610, Centris 650
* Quadra 605, 610, 650, 700, 800, 900, 950.
* AWG 60, 80, 95

The Macintosh environment from 3.0.1 did not run on Shoebill at one point; now it does.

However the unix side of 3.0.0 and 3.0.1 (below) does work. You can create a hybrid setup by replacing the /mac directory on 3.0.1 media with the /mac directory of 3.0.0 install media.

=== Emulation ===
There is now 2 emulators capable of running A/UX, [[Shoebill]] and [[Qemu]].

==== Shoebill ====
Shoebill emulator can run A/UX 1.1.1, 2.0 & 3.0.0 (*NOTE that version 3.0.0 seems to work the best). The latest version includes SDL support which can run on *NIX'es and Windows.

==== Qemu ====
The latest qemu-system-m68k includes a Quadra 800 machine profile which can run 3.0.1 and above.

You can build it from the current dev branch, full instructions are [https://www.emaculation.com/forum/viewtopic.php?f=37&p=71794#p71794 here].

<pre>
git clone -b q800.upstream https://www.gitlab.com/mcayland/qemu q800-upstream
cd q800-upstream
./configure --target-list=m68k-softmmu --enable-gtk --enable-sdl
make
</pre>

With Qemu in hand, you'll need to configure it for install with the [https://surfdrive.surf.nl/files/index.php/s/ZcJMgrSBqFAqfQA/download BootFloppy], [https://vpsland.superglobalmegacorp.com/install/MacOS/OS/Apple-AUX-3.0.1.7z ISO] and a pre-partitioned disk image.
General instructions are from [https://www.emaculation.com/doku.php/m68k-qemu-on-windows here].

(as of now the SCSI disk won't respond with Apple codes so the disk tool won't work).
<pre>
qemu-img.exe create -f raw AUX301.img 2G
qemu-img.exe create -f raw pram.img 256
</pre>

The command line to install is like this:
<pre>
qemu-system-m68k.exe ^
-L pc-bios ^
-m 32 ^
-M q800 ^
-display sdl ^
-serial stdio ^
-bios Quadra800.rom ^
-g 800x600x8 ^
-net nic,model=dp83932 -net user ^
-drive file=pram-i1.img,format=raw,if=mtd ^
-device scsi-hd,scsi-id=0,drive=fd0,vendor="SEAGATE",product="ST225N",ver="1.0" ^
-drive file=AUXBootfloppy.img,media=disk,format=raw,if=none,id=fd0 ^
-device scsi-hd,scsi-id=1,drive=hd0,vendor="SEAGATE",product="ST225N",ver="1.0" ^
-drive file=AUX301.img,media=disk,format=raw,if=none,id=hd0 ^
-device scsi-cd,scsi-id=3,drive=cd0,vendor="MATSHITA",product="CD-ROM CR-8005",ver="1.0k" ^
-drive file=AUX301.iso,format=raw,media=cdrom,if=none,id=cd0
</pre>

==What Runs?==

Some early GNU stuff will compile, however keep in mind that during the lifespan of A/UX GNU started up the Apple protest over the 'look and feel' lawsuit.

==External links==

* [http://www.aux-penelope.com/ A/UX Server Penelope] - General information
** [http://www.aux-penelope.com/hardware.htm Hardware Requirements]
* [https://www.macintoshrepository.org/1696-a-ux-apple-unix-for-68k-version-3-0-1-3-1-update A/UX (Apple UNIX for 68k) version 3.0.1 + 3.1 update] - More sources for the emulator and OS
* [https://virtuallyfun.com/wordpress/category/aux/ A/UX archives] - Posts on various topics

===Documentation===

* [http://christtrekker.users.sourceforge.net/doc/aux/faq.html Semi-official FAQ list for A/UX]
* [http://n-1.nl/apple_aux/aux-faq/part1/ Apple A/UX FAQ List (1/4)] - A/UX Faq: THE place to start
* [http://n-1.nl/apple_aux/aux-faq/part2/ Apple A/UX FAQ List (2/4)]
* [http://n-1.nl/apple_aux/aux-faq/part3/ Apple A/UX FAQ List (3/4)]
* [http://n-1.nl/apple_aux/aux-faq/part4/ Apple A/UX FAQ List (4/4)]


===UNIX Timeline===

* [http://www.unix.org/Posters/download/unix_posterA3.pdf The Single UNIX Specification History & Timeline]

{{Nav Unix}}

[[Category: Apple Operating Systems]]
[[Category: Unix-based OS's]]

A/UX

2021-09-08T04:58:23Z

Neozeed: separate emulation

{{Infobox OS
| image = softpc-on-aux.png
| caption = A/UX 3.0.0 desktop
| name = A/UX
| creator = Apple/UniSoft
| current version = 3.11
| year introduced = 1988
| type = Multitasking, multiuser
| architecture = [[Macintosh]]
}}

After [[Steve Jobs]] left [[Apple]], they scrambled to put together a system that could compete with [[NeXT]]. Hearing that NeXT was going to enter the [[UNIX|Unix]] [[workstation]] market, Apple commissioned [[UniSoft]] to help port [[SYSVr2]] to its [[Macintosh II]] lineup.

== Significant Versions ==
=== 0.7 ===
[[Image:AUX 0.7 desktop.png|thumb|right|150px|A/UX 0.7's UI]]
This version is more infamous because it included the source code to the kernel, which can be built with a little bit of work. There is no real Toolbox in this version, but rather a bare minimal SYSV port. This version uses a SYSV filesystem, while later versions of A/UX used 4.2BSD's FFS.
=== 1.1.1 ===
[[Image:AUX 1.1.1 desktop.png|thumb|right|150px|A/UX 1.1.1's GUI]]
This is a super barebones version, the toolbox is barely able to run the terminal application and some simple desktop widgets.
=== 2.0 ===
[[Image:AUX 2.0 desktop.png|thumb|right|150px|A/UX 2.0's GUI]]
Version 2.0 is more polished, and able to run a finder that is more parallel to [[System 6]].
=== 3.0 ===
[[Image:AUX 3.0 desktop.png|thumb|right|150px|A/UX 3.0's GUI]]
This is the best version to get ahold of. 3.0 emulates a [[System 7|System 7.0.1]] environment.
=== 3.1.1 ===
This version was the final released version, in 1995
=== 4.0 ===
This version was announced, and abandoned in 1996

== How do I get this to run?! ==

=== Physical Hardware ===
You will need an actual [[Macintosh]] that is supported. The best machines are the Quadra series. Note, not all Quadras will run A/UX.

The supported Macintosh Machines:
* A/UX 1.0 ~ A/UX 2.0
[ 68020 w/PMMU, 68030 ]
* Macintosh II, Rev B, with a 68851 PMMU
* Macintosh SE/30
* Macintosh IIx, IIcx, IIsi, IIci, IIfx

A/UX 3.0 ~ A/UX 3.1.1
[ 68040 ]
* Centris 610, Centris 650
* Quadra 605, 610, 650, 700, 800, 900, 950.
* AWG 60, 80, 95

The Macintosh environment from 3.0.1 did not run on Shoebill at one point; now it does.

However the unix side of 3.0.0 and 3.0.1 (below) does work. You can create a hybrid setup by replacing the /mac directory on 3.0.1 media with the /mac directory of 3.0.0 install media.

=== Emulation ===
There is now 2 emulators capable of running A/UX, [[Shoebill]] and [[Qemu]].

==== Shoebill ====
Shoebill emulator can run A/UX 1.1.1, 2.0 & 3.0.0 (*NOTE that version 3.0.0 seems to work the best). The latest version includes SDL support which can run on *NIX'es and Windows.

==== Qemu ====
The latest qemu-system-m68k includes a Quadra 800 machine profile which can run 3.0.1 and above.

==What Runs?==

Some early GNU stuff will compile, however keep in mind that during the lifespan of A/UX GNU started up the Apple protest over the 'look and feel' lawsuit.

==External links==

* [http://www.aux-penelope.com/ A/UX Server Penelope] - General information
** [http://www.aux-penelope.com/hardware.htm Hardware Requirements]
* [https://www.macintoshrepository.org/1696-a-ux-apple-unix-for-68k-version-3-0-1-3-1-update A/UX (Apple UNIX for 68k) version 3.0.1 + 3.1 update] - More sources for the emulator and OS
* [https://virtuallyfun.com/wordpress/category/aux/ A/UX archives] - Posts on various topics

===Documentation===

* [http://christtrekker.users.sourceforge.net/doc/aux/faq.html Semi-official FAQ list for A/UX]
* [http://n-1.nl/apple_aux/aux-faq/part1/ Apple A/UX FAQ List (1/4)] - A/UX Faq: THE place to start
* [http://n-1.nl/apple_aux/aux-faq/part2/ Apple A/UX FAQ List (2/4)]
* [http://n-1.nl/apple_aux/aux-faq/part3/ Apple A/UX FAQ List (3/4)]
* [http://n-1.nl/apple_aux/aux-faq/part4/ Apple A/UX FAQ List (4/4)]


===UNIX Timeline===

* [http://www.unix.org/Posters/download/unix_posterA3.pdf The Single UNIX Specification History & Timeline]

{{Nav Unix}}

[[Category: Apple Operating Systems]]
[[Category: Unix-based OS's]]

User talk:Larsbrinkhoff

2021-09-08T04:42:48Z

Neozeed: from me!

==Talk: page entries==

Please remember to sign them! :-) Thanks! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 13:56, 9 July 2019 (CEST)

hey just saw your messages as I was about to go on an A/UX binge. Also the emacs stuff. You can email me directly neozeed <at> GOOG .... you know gmail <dot> com...
[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 06:42, 8 September 2021 (CEST)

Installing UTX/32 2.1B on SIMH

2021-08-31T02:20:00Z

Neozeed: add git link

These are my notes from installing UTX/32 2.1B onto SIMH.
This is for the [[Gould]] [[SEL V6]] processor.
This is pretty rough:

== Requirements ==
* You'll need the SEL32 version of SIMH [on github AZBevier/sims](https://github.com/AZBevier/sims)
* UTX tape (currently in the SEL32 source tree!)
* patience

== Phase 1 / tape boot ==
Thankfully there are pre-cooked ini files for the installation that go A/B/C so to start the tape install we start with:
<pre>
sel32 utxtest2a.ini
</pre>

=== Prep the disk ===
After booting from tape we need to prep the disk.

<pre>
# prep /dev/dk0c
Ready to prep dk0c at 0x800 <yes>?

dk0: pack not prepped, using dfts
Disk is on UDP/DPII type controller.

Main menu options are:
0 - Leave prep
1 - Format the disk
2 - Initialize the disk for UTX/32
3 - Partition the disk and/or set swapping partition(s)
4 - Remap a bad block
5 - Display and/or modify the disk flaw map
6 - Display and/or modify the disk track labels
7 - Display and/or modify data blocks
8 - Expert mode
Which option ? 2
Umap magic number = 0x0 instead of 0x4e554d50 or 0x554d4150
Umap is corrupt, will have to reprep
Warning: some data may be lost on the pack, proceed <no>? yes
Rebuild UTX flaw map from diagnostic flaw map <no>? yes
0 - Gould Model Unknown, Undefined Drive type
1 - Gould Model 8880, Dual Floppy
2 - Gould Model 8838, CDC 80Mb 9 inch removable cartridge
3 - Gould Model 9342, CDC 80Mb 14 inch removable
4 - Gould Model 8148, CDC 160Mb removable
5 - Gould Model 8820, CDC 150Mb fixed SCSI
6 - Gould Model 9346, CDC 300Mb removable
7 - Gould Model 8821, CDC 300Mb fixed SCSI
8 - Gould Model 8858, CDC 340Mb fixed
10 - Gould Model 8812, CDC 500Mb fixed
11 - Gould Model 8155, CDC 697Mb fixed
13 - Gould Model 8813, CDC 850Mb fixed
14 - Gould Model 8888, CDC 858Mb fixed
17 - Gould Model 8887, Fuji 337Mb fixed
18 - Gould Model 8884, Fuji 474Mb fixed
19 - Gould Model 8889, Fuji 689Mb fixed
20 - Gould Model 8881, NEC 800Mb fixed
Please select a drive type: [CR, +, -, ##] ? 6
How many spare tracks should be allocated <15> ?

UMAP: Created: Fri Jun 24 16:24:18 1988
ID = 0 RPM = 3600
Last valid disk sector = 250191
Last available data block = 248975
HW alternates: 0 entries covering 0 tracks
SW alternates: 0 entries covering 0 tracks
Spare tracks: Start = 248976 Number = 15 Free = 15

No software substitutions.
About to write the Umap at address 249216
Do you really want to do this <no>? yes
Umap written at address 249216.
New UTX flaw map created at block 249232

Main menu options are:
0 - Leave prep
1 - Format the disk
2 - Initialize the disk for UTX/32
3 - Partition the disk and/or set swapping partition(s)
4 - Remap a bad block
5 - Display and/or modify the disk flaw map
6 - Display and/or modify the disk track labels
7 - Display and/or modify data blocks
8 - Expert mode
Which option ?

Which option ? 3
The pack (ID = 0) was previously prepped on Tue Apr 25 15:27:26 1989
Geometry (823/19/16) DIAG Dmap (249248) Umap (249216) UTX Dmap (249232)

Pack ID 0, Cylinders available 819 , Blocks available 248976
Drive type: Gould Model 9346, CDC 300Mb removable
(Cylinder bounded partitioning in effect)
Part Overlaps _Cylinders_ _Blocks_ Swap
(a) __c_____ 0 - 82 25232 no
(b) __c_____ 83 - 148 20064 yes
(c) ab_def__ 0 - 818 248976 no
(d) __c_____ 149 - 379 70224 no
(e) __c_____ 380 - 708 100016 no
(f) __c_____ 709 - 818 33440 no
(g) ________ 0 - 0 0 no
(h) ________ 0 - 0 0 no
</pre>

=== Format the slices ===
<pre>
newfs /dev/dk0a
newfs /dev/dk0d
newfs /dev/dk0e
newfs /dev/dk0f
</pre>

=== restore the first tape ===
<pre>
mount /dev/dk0a /mnt
cd /mnt
restore -xvf /dev/rmt12
...
Specify next volume #: 1
...
Specify next volume #: /dev/rmt12
...
set owner/mode for '.'? [yn] y
</pre>

== Second boot / Stand alone disk boot ==
I assume you've shut down the emu, and now we are using the B ini file:
<pre>
---------------------reboot
boot utxtest2b.ini
</pre>

Mount and run restore. You will have to swap tapes, be careful!
<pre>
mount -a
cd /usr
restore -xvf /dev/rmt12
...
Specify next volume #: 1
...
Mount tape volume 2
^E
at mta0 utx21b3.tap
c
<enter>
...
set owner/mode for '.'? [yn] y
df ?
cd /
halt
</pre>

We should now be good to boot from the final ini, the C and that's about it!
remember the tape device is mta0 on SIMH /dev/rmt12 in UTX
<pre>
utx21b1.tap
utx21b2.tap
at mta0 utx21b3.tap

at mta0 utx21b1.tap
</pre>

[[Category:SIMH Tutorials]]

Installing UTX/32 2.1B on SIMH

2021-08-31T01:50:27Z

Neozeed: Lame initial version

These are my notes from installing UTX/32 2.1B onto SIMH.
This is for the [[Gould]] [[SEL V6]] processor.
This is pretty rough:

== Requirements ==
* You'll need the SEL32 version of SIMH
* UTX tape (currently in the SEL32 source tree!)
* patience

== Phase 1 / tape boot ==
Thankfully there are pre-cooked ini files for the installation that go A/B/C so to start the tape install we start with:
<pre>
sel32 utxtest2a.ini
</pre>

=== Prep the disk ===
After booting from tape we need to prep the disk.

<pre>
# prep /dev/dk0c
Ready to prep dk0c at 0x800 <yes>?

dk0: pack not prepped, using dfts
Disk is on UDP/DPII type controller.

Main menu options are:
0 - Leave prep
1 - Format the disk
2 - Initialize the disk for UTX/32
3 - Partition the disk and/or set swapping partition(s)
4 - Remap a bad block
5 - Display and/or modify the disk flaw map
6 - Display and/or modify the disk track labels
7 - Display and/or modify data blocks
8 - Expert mode
Which option ? 2
Umap magic number = 0x0 instead of 0x4e554d50 or 0x554d4150
Umap is corrupt, will have to reprep
Warning: some data may be lost on the pack, proceed <no>? yes
Rebuild UTX flaw map from diagnostic flaw map <no>? yes
0 - Gould Model Unknown, Undefined Drive type
1 - Gould Model 8880, Dual Floppy
2 - Gould Model 8838, CDC 80Mb 9 inch removable cartridge
3 - Gould Model 9342, CDC 80Mb 14 inch removable
4 - Gould Model 8148, CDC 160Mb removable
5 - Gould Model 8820, CDC 150Mb fixed SCSI
6 - Gould Model 9346, CDC 300Mb removable
7 - Gould Model 8821, CDC 300Mb fixed SCSI
8 - Gould Model 8858, CDC 340Mb fixed
10 - Gould Model 8812, CDC 500Mb fixed
11 - Gould Model 8155, CDC 697Mb fixed
13 - Gould Model 8813, CDC 850Mb fixed
14 - Gould Model 8888, CDC 858Mb fixed
17 - Gould Model 8887, Fuji 337Mb fixed
18 - Gould Model 8884, Fuji 474Mb fixed
19 - Gould Model 8889, Fuji 689Mb fixed
20 - Gould Model 8881, NEC 800Mb fixed
Please select a drive type: [CR, +, -, ##] ? 6
How many spare tracks should be allocated <15> ?

UMAP: Created: Fri Jun 24 16:24:18 1988
ID = 0 RPM = 3600
Last valid disk sector = 250191
Last available data block = 248975
HW alternates: 0 entries covering 0 tracks
SW alternates: 0 entries covering 0 tracks
Spare tracks: Start = 248976 Number = 15 Free = 15

No software substitutions.
About to write the Umap at address 249216
Do you really want to do this <no>? yes
Umap written at address 249216.
New UTX flaw map created at block 249232

Main menu options are:
0 - Leave prep
1 - Format the disk
2 - Initialize the disk for UTX/32
3 - Partition the disk and/or set swapping partition(s)
4 - Remap a bad block
5 - Display and/or modify the disk flaw map
6 - Display and/or modify the disk track labels
7 - Display and/or modify data blocks
8 - Expert mode
Which option ?

Which option ? 3
The pack (ID = 0) was previously prepped on Tue Apr 25 15:27:26 1989
Geometry (823/19/16) DIAG Dmap (249248) Umap (249216) UTX Dmap (249232)

Pack ID 0, Cylinders available 819 , Blocks available 248976
Drive type: Gould Model 9346, CDC 300Mb removable
(Cylinder bounded partitioning in effect)
Part Overlaps _Cylinders_ _Blocks_ Swap
(a) __c_____ 0 - 82 25232 no
(b) __c_____ 83 - 148 20064 yes
(c) ab_def__ 0 - 818 248976 no
(d) __c_____ 149 - 379 70224 no
(e) __c_____ 380 - 708 100016 no
(f) __c_____ 709 - 818 33440 no
(g) ________ 0 - 0 0 no
(h) ________ 0 - 0 0 no
</pre>

=== Format the slices ===
<pre>
newfs /dev/dk0a
newfs /dev/dk0d
newfs /dev/dk0e
newfs /dev/dk0f
</pre>

=== restore the first tape ===
<pre>
mount /dev/dk0a /mnt
cd /mnt
restore -xvf /dev/rmt12
...
Specify next volume #: 1
...
Specify next volume #: /dev/rmt12
...
set owner/mode for '.'? [yn] y
</pre>

== Second boot / Stand alone disk boot ==
I assume you've shut down the emu, and now we are using the B ini file:
<pre>
---------------------reboot
boot utxtest2b.ini
</pre>

Mount and run restore. You will have to swap tapes, be careful!
<pre>
mount -a
cd /usr
restore -xvf /dev/rmt12
...
Specify next volume #: 1
...
Mount tape volume 2
^E
at mta0 utx21b3.tap
c
\<enter\>
...
set owner/mode for '.'? [yn] y
df ?
cd /
halt
</pre>

We should now be good to boot from the final ini, the C and that's about it!
remember the tape device is mta0 on SIMH /dev/rmt12 in UTX
<pre>
utx21b1.tap
utx21b2.tap
at mta0 utx21b3.tap

at mta0 utx21b1.tap
</pre>

[[Category:SIMH Tutorials]]

86-DOS

2021-06-24T02:18:29Z

Neozeed: 86dos is now offline.

{{Infobox OS
| image = 86-dos.png
| caption = Booting up the 86-DOS system
| name = 86-DOS
| creator = Seattle Computer Products
| current version = 1.0 (1981)
| year introduced = 1981
| type = Singletasking, Singleuser
| architecture = [[IBM PC]]
}}

86-DOS was the CP/M work alike that was being written by Tim Patterson.

There is a great information site [https://web.archive.org/web/20181002215506/http://www.86dos.org/index.htm http://www.86dos.org/index.htm]

One thing that is interesting about 86-DOS on the [[S-100]] type machines, is that unlike the [[IBM PC]] The S-100's could access the full megabyte of ram. According to Tim Patterson this feature was used within Microsoft until the creation of 32bit tools to link the linker that Microsoft had built because it needed so much memory. Although I was always under the impression that Microsoft had their compilers ported to a VAX and cross compiled stuff from there as it was faster, and didn't have the same memory limits... but that's from some unbased rumor I heard so you know... grain of salt.

== How do I get this to run ==

There is a download like available to a [[SIMH]] image of the boot disk [http://schorn.ch/cpm/zip/86dos.zip here] Simple download the zip file & extract it, then use a version of SIMH's 3.0 or higher Altair Z80 emulator to bootstrap it. Although the name may seem misleading, the Altair z80 simulates a development environment that allows for an 8086 coprocessor to execute the 86-DOS Operating System.

{{stub}}
[[Category:Operating Systems]]

Netnews archive

2020-08-02T14:25:04Z

Neozeed:

[[Image:davidwiseman-tapes.jpg|200px|thumb|right|David Wiseman]]
There is an incredible archive [https://sourceforge.net/projects/utzoo/files/ here] of all the early usenet posts from February 1981 until June of 1991.

= Magi's recount =
Magi's NetNews Archive Involvement
Well, the thank-you's have been rather ebullient all day long today and I feel somewhat embarrassed by the attention. Especially given how long it took us to get the archive on line and visible! It has to be close to 10 years now. Sigh.
The story is more a story of fits and starts than of resolve. And our contribution accounts for some (most?) of the first 10 years of the Google archive.

If I recall correctly, the issue of Henry Spencer's (actually, the University of Toronto, Department of Zoology's) NetNews archive was raised at a Usenix conference in the early 90's. The question: can we get at them? Bruce Jones was especially interested in this. Henry's answer was that it really wasn't going to be easy because he had neither the disk space nor the tape drive to pull them all down to make them available.

I, it turned out, did. So one bright winter day I drove from London (Ontario Canada) to Toronto (Ontario Canada) -- a two hour drive in my shiny new pickup truck and picked up 141 magtapes from the Zoology department at UofT and brought them back to the Department of Computer Science at the University of Western Ontario. (A not unimpressive bandwidth, by the way, of some 18Mb/sec :-) never underestimate the bandwidth of a pickup truck on the highway!)

Then with the help of several people (some of whom have not yet been credited) we started to pull the data off of the tapes and onto disks in both the Computer Science department and the Robarts Research Institute. Lance Bailey, then with the Robarts Research Institute, did the pulling there and I with assistance from Bob Webber did it at Computer Science. Bruce Jones from UCSD took some vacation time and came up here to help pull data down for a week or so as well.

But we quickly ran out of space and time: Lance left Robarts for UBC, Bruce's vacation ended, and Bob and I got busy doing other things (like our jobs). As a result, the archive project made very little progress over the next few years.

Then Brewster Kahle started pushing on us (thanks Brewster!) to get it done. He even bought us a large disk to hold the archive when we truly ran out of space. With the help of Sue Thielen, who was out of work and bored, we got all of the rest of the tapes read down onto that disk. Unfortunately, that disk was not "close enough" to either a tape drive or the ftp server to make the data available to anyone. And it wasn't organized in anyway usefully.

Brewster pushed very gently for a very long time but the new archive project was far from the top of the list of projects I was supposed to be working on and I just never got it going again.

Late this summer Michael Schmitt from Google started pushing as well. And as luck would have it, I was able to hire a student to do the final sorting of the archive as well. And, that luck still holding, I managed to "steal" enough space on the ftp server for the entire archive! But it still took months to get that figured out and the archive transferred to a machine from which they pull the archive. It was the middle of October before we were able make the collection available to Google. And it is actually available, although totally unsorted, to anyone who wants it and can deal with pulling some 160 files ranging in size from 1.4Mb to 65Mb. Just drop me a line to say please and we'll arrange to make it visible to you.

I'd still like to impose a bit more order on the raw archives than we have but the time just hasn't allowed for that...

= Original ftp site headder =
<pre>
230-Yes, you have found the on-line copy of Henry Spencer's UTZOO NetNews
230-Archive.
230-
230-It is not in a very reasonable format but it is all here. There were
230-141 magtapes in the collection and, so far, we have them organized to
230-reflect these tapes. You will find two types of files in this
230-directory:
230
230- newsNNNfM.tgz the archives, tar'd and compressed
230-and newsNNNfM.toc the tables of contents (tar listings)
230-
230-where NNN is the tape number (from 001 to 141)
230-and M is the save set number (from 1 to 3 but usually 1).
230-
230-There is also a file called AllTOC.tgz which is a compressed tar archive
230-containing all of the .toc files.
230-
230-Please note that news001f1.tgz contains A news. All of the other tapes
230-contain B news. The news in this archive was collected between February
230-of 1981 and June of 1991. (The Scavenged.tgz file contains A news articles
230-which were "found" off the end of some of the earlier tapes.)
230-
230-Also below here is an 'info' directory which contains several useful
230-files with "overviews" of some of the archive information. Hopefully
230-the filenames will explain what they are. (I know, probably not.)
230-
230-The 'pc' directory contains Windows code which can unpack .tgz files. I
230-have also been told that the latest versions of WinZip can also read them.
230-
230--- magi
</pre>

== Controversy ==
I just found out that the UTZOO archives have been destroyed. Only 3rd party mirrors exist. What an incredible loss, of nearly 2 decades of written history. Absolutely tragic.

From Archive.org:
<pre>
This is not a collection of the UTZOO Wiseman Usenet Archive.

In 2020 after sustained legal demands requesting a set of messages within the Usenet Archive be redacted, and to avoid further costs and accusations of manipulation should those demands be met, the archive has been removed from this URL and is not currently accessible to the public.

Included in this item is a file listing and the md5 sums of the removed files, for the use of others in verifying they have original materials.
</pre>

{{stub}}

[[Category: Networking]]

Netnews archive

2020-08-02T13:02:43Z

Neozeed: UTZOO has been destroyed.

[[Image:davidwiseman-tapes.jpg|200px|thumb|right|David Wiseman]]
There is an incredible archive [https://sourceforge.net/projects/utzoo/files/ here] of all the early usenet posts from February 1981 until June of 1991.

== headder ==
<pre>
230-Yes, you have found the on-line copy of Henry Spencer's UTZOO NetNews
230-Archive.
230-
230-It is not in a very reasonable format but it is all here. There were
230-141 magtapes in the collection and, so far, we have them organized to
230-reflect these tapes. You will find two types of files in this
230-directory:
230
230- newsNNNfM.tgz the archives, tar'd and compressed
230-and newsNNNfM.toc the tables of contents (tar listings)
230-
230-where NNN is the tape number (from 001 to 141)
230-and M is the save set number (from 1 to 3 but usually 1).
230-
230-There is also a file called AllTOC.tgz which is a compressed tar archive
230-containing all of the .toc files.
230-
230-Please note that news001f1.tgz contains A news. All of the other tapes
230-contain B news. The news in this archive was collected between February
230-of 1981 and June of 1991. (The Scavenged.tgz file contains A news articles
230-which were "found" off the end of some of the earlier tapes.)
230-
230-Also below here is an 'info' directory which contains several useful
230-files with "overviews" of some of the archive information. Hopefully
230-the filenames will explain what they are. (I know, probably not.)
230-
230-The 'pc' directory contains Windows code which can unpack .tgz files. I
230-have also been told that the latest versions of WinZip can also read them.
230-
230--- magi
</pre>

== Controversy ==
I just found out that the UTZOO archives have been destroyed. Only 3rd party mirrors exist. What an incredible loss, of nearly 2 decades of written history. Absolutely tragic.

From Archive.org:
<pre>
This is not a collection of the UTZOO Wiseman Usenet Archive.

In 2020 after sustained legal demands requesting a set of messages within the Usenet Archive be redacted, and to avoid further costs and accusations of manipulation should those demands be met, the archive has been removed from this URL and is not currently accessible to the public.

Included in this item is a file listing and the md5 sums of the removed files, for the use of others in verifying they have original materials.
</pre>

{{stub}}

[[Category: Networking]]

3Com 3C501

2020-06-04T08:27:25Z

Neozeed: Poorly imported from https://arvutimuuseum.ee/th99/n/P-R/40023.htm

ETHERLINK (3C501; ASSY.#1221)

[[Image:3com 3c501 front.jpg]]

[[Image:3com501-jumper.png]]

{|
|NIC Type
|Ethernet
|-
|Transfer Rate
|10Mbps
|-
|Data Bus
|8-bit ISA
|-
|Topology
|Linear Bus
|-
|Wiring Type
|RG-58A/U 50ohm coaxial
|-
|
|AUI transceiver via DB-15 port
|-
|Boot ROM
|Available
|}

CABLE TYPE SELECTION
{|
! style="text-align:left;"| Type
! Setting
|-
|RG-58A/U 50ohm coaxial
|Option 1
|-
|AUI transceiver via DB-15 port
|Option 2
|}

BOOT ROM CONFIGURATION
{|
! style="text-align:left;"| Setting
! JP3
|-
|Disabled
|Pins 2 & 3 Closed
|-
|Enabled
|Pins 1 & 2 Closed
|}

I/O BASE ADDRESS SELECTION
BOOT ROM CONFIGURATION
{|
! style="text-align:left;"| Address
!JP4
!JP5
!JP6
!JP7
!JP8
!JP9
|-
|300h
|Pins 2 & 3
|Pins 2 & 3
|Pins 2 & 3
|Pins 2 & 3
|Pins 1 & 2
|Pins 1 & 2
|-
|310h
|Pins 1 & 2
|Pins 2 & 3
|Pins 2 & 3
|Pins 2 & 3
|Pins 1 & 2
|Pins 1 & 2
|}
Note:Pins designated should be in the closed position.

BOOT ROM ADDRESS SELECTION
{|
! style="text-align:left;"| Address
!JP12
!JP13
!JP14
!JP15
!JP16
!JP17
!JP18
!JP19
|-
|CC000h
|Pins 2&3
|Pins 2&3
|Pins 1&2
|Pins 1&2
|Pins 2&3
|Pins 2&3
|Pins 1&2
|Pins 1&2
|-
|EC000h
|Pins 2&3
|Pins 2&3
|Pins 1&2
|Pins 1&2
|Pins 2&3
|Pins 1&2
|Pins 1&2
|Pins 1&2
|}
Note:Pins designated should be in the closed position.

INTERRUPT REQUEST SELECTION
{|
! style="text-align:left;"| IRQ
!JP20
!JP21
!JP22
!JP23
!JP24
!JP25
|-
|2
|Closed
|Open
|Open
|Open
|Open
|Open
|-
|3
|Open
|Closed
|Open
|Open
|Open
|Open
|-
|4
|Open
|Open
|Closed
|Open
|Open
|Open
|-
|5
|Open
|Open
|Open
|Closed
|Open
|Open
|-
|6
|Open
|Open
|Open
|Open
|Closed
|Open
|-
|7
|Open
|Open
|Open
|Open
|Open
|Closed
|}

DMA CHANNEL SELECTION
{|
! style="text-align:left;"| Channel
!JP26
!JP27
!JP28
!JP29
!JP30
!JP31
|-
|DMA1
|Closed
|Open
|Open
|Closed
|Open
|Open
|-
|DMA2
|Open
|Closed
|Open
|Open
|Closed
|Open
|-
|DMA3
|Open
|Open
|Closed
|Open
|Open
|Closed
|}
{{stub}}

File:3com 3c501 back.jpg

2020-06-04T08:27:12Z

Neozeed: From Ebay Auction: https://www.ebay.com/itm/3COM-IE-4-ETHERLINK-8-BIT-ISA-ADAPTER-ASSY-1221/141923436340

From Ebay Auction: https://www.ebay.com/itm/3COM-IE-4-ETHERLINK-8-BIT-ISA-ADAPTER-ASSY-1221/141923436340

File:3com 3c501 blade.jpg

2020-06-04T08:26:58Z

Neozeed: From Ebay Auction: https://www.ebay.com/itm/3COM-IE-4-ETHERLINK-8-BIT-ISA-ADAPTER-ASSY-1221/141923436340

From Ebay Auction: https://www.ebay.com/itm/3COM-IE-4-ETHERLINK-8-BIT-ISA-ADAPTER-ASSY-1221/141923436340

File:3com 3c501 front.jpg

2020-06-04T08:26:31Z

Neozeed: From Ebay Auction: https://www.ebay.com/itm/3COM-IE-4-ETHERLINK-8-BIT-ISA-ADAPTER-ASSY-1221/141923436340

From Ebay Auction:
https://www.ebay.com/itm/3COM-IE-4-ETHERLINK-8-BIT-ISA-ADAPTER-ASSY-1221/141923436340

File:3com501-jumper.png

2020-06-04T08:11:04Z

Neozeed: Jumpers on a 3c501 from https://arvutimuuseum.ee/th99/n/P-R/40023.htm

Jumpers on a 3c501 from https://arvutimuuseum.ee/th99/n/P-R/40023.htm

4.4BSD Lite

2020-03-17T17:08:09Z

Neozeed: /* downloading */

[[Image:4.4 BSD Lite2 CD front.jpg|200px|right|thumb|A 4.4BSD lite CD]]
4.4 BSD Lite was the second last release from the [[CSRG]]. After they had to withdraw the [[Net/2]] source, the files found to be in contention with [[32v]] were removed, and this distribution was released.

Then all of the derived projects had to ensure that they didn't have those files, or anything derived from them.

I think at the time this would have impacted:

* [[NetBSD]]
* [[FreeBSD]]
* [[BSD/OS|BSD/386]]

Just like Net/2, this was not a complete OS onto itself, however it was the vast majority needed.

from init_main.c
<pre>
@(#)init_main.c 8.9 (Berkeley) 1/21/94
</pre>

== downloading ==
4.4 BSD Lite can still be found on the internet...
*[http://http.pl.scene.org/pub/unix/systems/BSD/4.4BSD-Lite/4.4BSD-Lite.tar.gz 4.4BSD-Lite.tar.gz]

The next and final release was [[4.4 BSD Lite2]]

{{stub}}

[[Category: CSRG BSD]]

4.4BSD Lite Release 2

2020-03-17T17:07:34Z

Neozeed: /* downloads */

I think this is the last of the [[CSRG]] 4.x BSD's...

from init_main.c

<pre>
@(#)init_main.c 8.16 (Berkeley) 5/14/95

</pre>

== downloads ==
It can be still found on the internet...
*[http://http.pl.scene.org/pub/unix/systems/BSD/4.4BSD-Lite/4.4BSD-Lite2.tar.gz 4.4BSD-Lite2.tar.gz]

[[Category: CSRG BSD]]

Talk:4.2 BSD

2019-10-19T00:50:15Z

Neozeed: SunOS 2/3

I have a game called "orbit". The README says "This should work with no changes on Berkeley 4.2". The graphics seem to be raster bitmaps. I see references to "sun", and not as a star. There is 68000 assembly code in it. Timestamps are August 22, 1983. I don't suppose there's a 4.2BSD for a Sun workstation? Tarball here: https://github.com/PDP-10/Spacewar/blob/not-pdp10/orbit.tar.gz?raw=true [[User:Larsbrinkhoff|Larsbrinkhoff]] ([[User talk:Larsbrinkhoff|talk]]) 17:31, 15 October 2019 (CEST)

: Mystery solved: http://www.classiccmp.org/pipermail/cctalk/2019-October/050060.html [[User:Larsbrinkhoff|Larsbrinkhoff]] ([[User talk:Larsbrinkhoff|talk]]) 13:30, 18 October 2019 (CEST)

SunOS 2.0 and 3.0 are 4.2 from what I recall. And they most certainly use the 68000 instruction set. They would be the most likely target.

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 02:50, 19 October 2019 (CEST)

User talk:ForOldHack

2019-09-25T12:03:42Z

Neozeed: reply to the kirk cd request

==Sigs on Talk: pages==

We generally try and follow the Wikipedia style of signing posts on Talk: pages (so that people reading them will know straight off, without having to look in the history, who made comments, and when). There's even special Wiki syntax to do this easily; just add <nowiki>~~~~</nowiki> to the end of your post, and it will be automagically transformed in this sig, with the user and time. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 13:21, 11 March 2019 (CET)

: Hmm, something else is going on. '[[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:41, 12 March 2019 (CET)' gives me date and time, and <nowiki>~~~~</nowiki> gives me 4 tildies.

: Oh, now I understand to escape the wiki process and get tildies, use <nowiki>~~~~</nowiki>, but to get the sig use [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:42, 12 March 2019 (CET)

:: I have not seen such a funny time stamp in 34 years, when we were using uwasa.fi as a mail relay. ( Time is Wasausa, Finland ) [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:45, 12 March 2019 (CET)

: Please don't forget; I can add the sig manually, but it's easier for you. Thanks! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:52, 22 March 2019 (CET)

== Note ==

I would like to print to npib78003.local [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 05:45, 27 March 2019 (CET)

== Infobox line captions ==

The captions in info boxes are specified in the template, as are the argument names; trying to change either in the invocation has no effect.

If you want to change the 'Year introduced' caption, I'd be OK with that, but just to 'Introduced' I think might be potentially confusing without something to indicate that it's a temporal meaning - e.g. 'Date introduced', or something. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 12:04, 7 April 2019 (CEST)

:Introduced sounds like marketing speak, I would prefer Release dates, since that would cover both people receiving mag tapes, and downloading comparable source. I got Redhat 5.0 on the day of release, and was able to torrent it, and was able to install it quickly. I went to a user group meeting, and for the cost of $5, got 1) a backup CD, 2) a great Tshirt, 3) a great how-to manual, and 4) some nifty stickers. Needless to say, from that day forward, I saw the lack of value in Microsoft Products. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 11:52, 12 April 2019 (CEST)

:: OK, 'Date released' would work in [[Template:Infobox Software]], [[Template:Infobox OS]], and [[Template:Infobox App]]. I'll go ahead and make that change (although it will only be in the caption, not in the argument name - if I change that, I'd have to change every article that calls those templates).
:: Not sure that to do about [[Template:Infobox Machine]], etc - would 'Date introduced' work there? [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 16:20, 16 April 2019 (CEST)

: Back to the Temporal part, We want a label to indicate its first start of general use, so that a corresponding date tag, could map to what hardware it would run on, i.e. XENIX would have a 1985 release date, and the current hardware was XTs, Turbo XTs, ATs and a few clones,
:Verses ATT SYS V, I guess I see through the eyes of my first C teacher, Barry Kercheval, who liked Sun workstations, because of their OS, and their compiler. The MS-DOS C compilers at the time were hacks, Microsoft C was bad, Aztek C was a bit better, Manx C would make code easy to port from Amiga to PC, and we would get constant diffrences between those and XENIX, and the other boxes we would remote into to look at their compilers. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 11:52, 12 April 2019 (CEST)

:: The way I'd handle OS's where they were released on different dates on different hardware would be to put multiple entries in the 'Date released' box (sort of like the mutiple entries under 'Capacity' [[RL0x disk drive|here]]); one line for each type of hardware. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 16:20, 16 April 2019 (CEST)

:For RT-11, A list of boxes that it could run on, and the corresponding CPUs and memory cards that would support it, would be useful. i.e. It would not run on this hardware, but certainly would run on the current hardware of the day. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 11:52, 12 April 2019 (CEST)

== External link syntax ==

We generally like to give the title of our external links, using the syntax <nowiki>'[URL title]'</nowiki>, so instead of:

[http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html]

one sees this:

[http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html Digital Equipment Corporation Indicator Panels]

Much nicer for our readers! The title is formally given inside <title> tags in the HTML of the page, and displayed by the browser (often in the window title bar, but exactly how will depend on the browser and OS).

PS: You shouldn't stick a sig in additions to ''content'' pages (where it intrudes), you only need to do it on Talk: pages. The reasoning (it dates to a very early stage on Wikipedia, before even I started there) seems to be that if one wants to know where something in a content page comes from, one looks at the History of that page; on Talk: pages (especially if one is reading one later - see for example the discussion at [[Help talk:Introduction to Categories]]), one can easily see who posted a given item directly, without needing to grub around in the history. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:25, 7 April 2019 (CEST)

:Very sorry, I had forgot, and even forgot to look it up. I am so amazed by the tiny bits I have found, I only used some of those machines a few times, they were apprently very popular because they were so fantastic.
:Ill follow this convention on. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:57, 8 April 2019 (CET)

Sure. BTW, [https://en.wikipedia.org/wiki/Wikipedia:SIG here] is the Wikipedia sig policy, which we follow (although we don't follow Wikipedia in most things, in this one we do). [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:12, 9 April 2019 (CEST)

:When a user sees this: [[http://mercury.lcs.mit.edu/~jnc/humour/sys286.notes System 286 release notes]] it had me choking with laughter. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 10:59, 12 April 2019 (CET)

:: Actually, I didn't write that - someone else at MIT did (don't recall who). The only humour thing I did was the first "Alice's" hack - Alice's PDP-10, maybe? [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:36, 13 April 2019 (CEST)

== new user ==

I don't see a new user. You are the newest user since 8 March 2019.
[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 11:25, 11 April 2019 (CEST)

Right, you created a new page, [[User talk:ForOldHack/My sandbox‎‎]], in the 'User talk' namespace. On this wiki, only [https://en.wikipedia.org/wiki/Wikipedia:Administrators admins] can create new user accounts. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:12, 11 April 2019 (CEST)

Yes, I understand. Page deleted. It does help a lot that you have more Wikipedia experience then I. Thanks. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 10:35, 12 April 2019 (CEST)

: Technically, you 'blanked' the page; it (and its history) are still there. It is actually possible to remove a page totally, but only admins have that ability. Please let me know if you ever want a page (e.g. that one) nuked. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:43, 13 April 2019 (CEST)

:Yes, I have grabbed the information off that page, it can go into the great bit bucket (trash/recycler/ /dev/null)

:How many euphemisms can we come up with for deleting a file/page? [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 19:43, 17 April 2019 (CEST)

:: OK, I have deleted that page. If I misunderstood you, or you change your mind, please let me know and I can restore it. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 16:45, 24 April 2019 (CEST)

No, I copied the information here. It was an experiment and it did not come out as planned. ( silent back pages ).
Good to know we can bring back pages if we make mistakes.

But the more I read here about DEC/PDP/VAX, The more I agree with your respect for its elegance. I wish I had had more time with the hardware, and could have worked with it the way I have worked with PCs.

Got a Mac Performa 630CD running today, just by cleaning it thoroughly, and giving it time to ... coalesce.

It seems as though this Wiki is coming along with the company of a few devoted fans. Great work.

== Visualization ==

This is an exercise to create a text based
visualization tool to categorize memory boards and their resultant available operating systems:

Chips: Motherboard OS
1x16 DRAM IBM PC V1 DOS 1.0 ( August 1981 )
DOS 1.1 ( August 1981 )
CPM-86
UCSD-p

Hm... Chart:

[https://d1k5w7mbrh6vq5.cloudfront.net/images/cache/01/fd/0f/01fd0fcde84b7edd8bcbb946c2729d01.png?c8c3be714 Dos chart, and early windows, no server.]

[[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 10:35, 12 April 2019 (CEST)

== Kirk CD set! ==

You can find them on his site [https://www.mckusick.com/csrg/index.html here for sale]. Its a KLUNKY ordering thing, straight out of 1993, but I got my CD/DVD set in Hong Kong no worries!
Totally worth it!

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 14:03, 25 September 2019 (CEST)

Mach

2019-08-02T01:22:23Z

Neozeed: add in download location for 6.1

{{Infobox OS
| image = Mach-on-VAX780.png
| caption = Mach (1986) booting on a SIMH VAX
| name = Mach
| creator = CMU
| current version = 3.0 (1994)
| year introduced = 1985
| type = Multitasking, multiuser
| architecture = [[VAX]], [[m68k]], [[m88k]], [[i386]], [[i860]], [[ROMP]], [[POWER]], [[HPPA]], [[Sparc]]
}}

Mach was the [[microkernel]] from CMU that popularized the microkernel craze of the late 1980's and into the 1990's. While seen as a dead end effort, it did at the time bring in many new things to the aging [[UNIX|Unix]] [[kernel]]. Mach, based loosely on [[BSD]] was a low level kernel adding [[thread]]s insteads of forked [[process]]es, and had the ability to run on SMP hardware. BSD was then ported back as a user process on top of the Mach micro kernel.

== Archived Releases ==
I'm putting together a list of all the versions of Mach that I have tracked down over the years. I'll add in building & running instructions as I can. If you know or are in possession of other releases, please let me know!

=== CMU ===

==== 1.x ====
During the original development started at CMU, using various accent technologies and 4.3BSD as a starting point. There is 2 partial trees for these releases made in 1986. I'm assuming these are some version 1.x thing Both of these releases are on Kirk's DVD set.

==== 2.x ====
There is currently 2 versions saved of the '2.5' variation, both were found on the CSRG CD-ROM set.
* mk35
* X147

==== 3.x ====
Starting with 3.0 the 4.3BSD kernel was removed from the source making this a 'pure' Microkernel. So far the following versions have been saved:

* mk42
* mk78
* mk80
* mk82
* mk83
* mk83a
* mk84

=== Utah ===
After the winding down on Mach research at CMU, the University of Utah picked up Mach in 1994 and was released as Mach4. Known releases are:

* UK02p21
* UK22

Further work went into the [[OSKit]], a modular system to build kernels.

Later on Mach4 was shut down, and later attention was put into the new [[L4]] kernel.

=== OS/F ===
The OS/F group made various releases based on the Utah versions. Many were encumbered, however I have managed to track back a few releases:

* MK6.1 The only known version online is [http://mirrors.pdp-11.ru/_misc/ftp.mrynet.com/os/Mach3.0/ here].
* [https://web.archive.org/web/19970606230508/https://www.osf.org/RI/PubProjPgs/MK72.htm MK7.2]
* [https://web.archive.org/web/19971016172524/http://www.opengroup.org/RI/PubProjPgs/MK73.htm MK7.3]

== Mach Operating Systems ==

Some of the [[operating system]]s that used Mach were [[NeXTSTEP]]/[[OPENSTEP]], [[Mach386]] & [[OSF/1]]. The [[GNU Hurd]] project also used Mach at one point before abandoning it for [[L4]].

The [[GNU]] project had taken a version of Mach, and used the GNU license to 'gnu-ify' mach and produce GNUMach.
While [[Windows NT]] may share design ideas with Mach, it is NOT a derived Mach microkernel.

== Servers ==

Mach could run various '[[server]]' programs that would then provide an operating system personality to the user.

=== BSDSS ===

4.4 BSD subsystem. It was pulled at the start of the lawsuit

=== BNR2SS ===

BSD Net/2 subsystem

=== Lites ===

One of the more popular servers was Lites. It was a BSD based personality that could then run early versions of NetBSD & FreeBSD.

There was also a msdos subsystem

== Criticism ==

Mach was seen as unnecesary as its main idea of running multiple servers hardly ever happened. Most projects based on Mach only ran a single server. Also every time a program made a [[system call]] it had to transition through the kernel to talk to the 'server' process, which had to go thru Mach again to do whatever it was, then back to the server, then thru Mach again to talk to the program. The overhead of the system call was was significant, and a way was never developed to bring the LPC calls down to something comparable to an older monolithic style OS. This is why XNU (the Nextstep/Openstep/Darwin/OSX kernel) used Mach as a [[library]] rather then as a full blown microkernel.

The rise of Linux also showed that a re-structured monolithic kernel could not only scale on SMP hardware, but could remain portable.

== Getting it to run ==

Installing Mach on the PC is not a task for the timid. It is VERY involved and difficult. I have decided to provide an image [http://vpsland.superglobalmegacorp.com/install/MachUK22-lites-nat.zip here]. I may document the install later, but it is extremly complex.

{{semi-stub}}

[[Category: Operating Systems]]

Darwin

2019-08-02T01:06:32Z

Neozeed: Adding that the Darwin releases were based around OS/F MK6.1

Darwin is the [[open source]] core of [[OS X]].

== Rhapsody ==
[[Image:Darwin 0.1 booted single user mode.png|150px|thumb|right|Darwin 0.1]]

In the beginning of the project it was a fork of [[OPENSTEP]]. As far as I've been able to track down there have been 3 public releases of this OPENSTEP Darwin. And there have been several more public releases, up to and including OS X Server 1.0 which was based on the OPENSTEP kernel. Further complicating things, Darwin 0.1 reports itself as Rhapsody 5.3, while Darwin 0.2 and 0.3 report themselves as Darwin 0.2/0.3

From the source code of Darwin 0.1, The kernel is based on OS/F's 6.1 kernel. This is evident in [https://unix.superglobalmegacorp.com/cgi-bin/cvsweb.cgi/kernel/mach/boolean.h?rev=1.1.1.1;cvsroot=Darwin0 boolean.h as an example]:
<pre>
/*
* OSF Research Institute MK6.1 (unencumbered) 1/31/1995
*/
</pre>

The following is a table of versions I've been able to put together with information from the [http://www.rhapsodyos.org/ Rhapsody Resource Page], and a mirror of the [http://mirror.informatimago.com/next/developer.apple.com/darwin/news/qa20010925.html Darwin Q&A].

{| class="wikitable"
|-
! Kernel Version
! OS Name
! OS X Version
! Darwin Version
! Code name
|-
| 5.0
| Rhapsody
| Rhapsody Developer Release
| N/A
| Grail1Z4
|-
| 5.1
| Rhapsody
| Developer Release 2
| N/A
| Titan1U
|-
| 5.2
| Rhapsody
| Rhapsody 1.0
| N/A
| Unknown
|-
| 5.3
| Rhapsody
| Mac OS X Server 1.0
| [[Darwin 0.1]]
| Hera1O9
|-
| 5.4
| Rhapsody
| Mac OS X Server 1.0.1
| [[Darwin 0.2]]?
| Loki1A2
|-
| 5.5
| Rhapsody
| Mac OS X Server 1.0.2
| [[Darwin 0.3]]
| Loki2G1
|-
| 5.6
| Rhapsody
| Mac OS X Server 1.2
| N/A
| Pele1Q10
|-
| 5.6
| Rhapsody
| Mac OS X Server 1.2v3
| N/A
| Medusa1E3
|}

=== Getting this to run ===

==== i386 ====
Darwin 0.x can be built using a Rhapsody/OS X Server 1.0 binary system as a starting point. However when it comes to emulation and physical hardware the EIDE driver has a problem losing interrupts. It is not only a problem with Darwin/Rhapsody but on physical machines as well. This poses a challenge to 'white box' builders to this day. However the emulator Qemu 0.90 can run Rhapsody albeit with a busmouse driver.

For the sake of preservation, the preserved downloads from [https://archive.org/details/darwin_0.1 Darwin 0.1 are on archive.org]. Some components in the 0.1 tars didn't make it to the 0.3 CD-ROM so they are needed to build a more 'complete' set.

At this moment I have the following version of Darwin setup to run on Qemu:

* [https://sourceforge.net/projects/aapl-darwin/files/qemu-images/Darwin03_qemu090_24_4_2017.7z/download Darwin 0.3]

==== PowerPC ====
There has been tremendous improvements to Qemu, and it is now possible to install MacOS 9, and OS X Server 1.x, along with OS X 10.x. Darwin for the PowerPC doesn't have an actual installer on the discs, but rather you boot up into MacOS, and restore a disk backup from CD onto your target hard disk, and boot into that. Information can be found about the progress of the Qemu PowerPC on [https://www.emaculation.com/forum/viewtopic.php?f=34&t=7047&p=55205#p55205 emaculation.com]

Currently I have images of 0.3 & 1.0.2:

* [https://sourceforge.net/projects/aapl-darwin/files/Darwin-0.3/Apple-CDROM/Darwin-0.3.toast/download Darwin-0.3.toast]
* [https://sourceforge.net/projects/aapl-darwin/files/Darwin-1.0/Apple-CDROM/DarwinOS-1.0.2.dmg/download DarwinOS-1.0.2.dmg]

The process right now involves installing MacOS 9, as 8.6 included on the 0.3 currently doesn't boot. And likewise, the restore program on 0.3 won't run under MacOS 9, but the restore program from the 1.0.2 image will run on MacOS 9.

For the impatient, I do have the images already extracted and setup with Qemu
* [https://sourceforge.net/projects/aapl-darwin/files/qemu-images/Darwin03-PowerPC_qemu-2.11_04_22_2018.7z/download Darwin03-PowerPC_qemu-2.11_04_22_2018.7z]
* [https://sourceforge.net/projects/aapl-darwin/files/qemu-images/Darwin1.00PowerPC_qemu-2.11_04_22_2018.7z/download Darwin1.00PowerPC_qemu-2.11_04_22_2018.7z]

Currently there is no networking.

== XNU ==

[[Image:Darwin 1.4.1 x86 booted.png|150px|thumb|right|Darwin 1.4.1]]

After the release of OS X Server 1.0, it was clear at this point that OS X was doomed, as 3rd party software vendors expressed no interest in porting applications to OPENSTEP/Cocoa API's. Instead Apple would have to go and create the Carbon framework, allowing traditional MacOS applications to use a subset of the toolbox API, and then be ported to OS X. Along the way the older OPENSTEP kernel was dropped in favor of a newer kernel based on Mach 3.0 and a C++ driver framework.

The Darwin OS includes both the XNU kernel, along with all the free tools.

As far as I recall it started being fully distributed in Darwin 1.0, which was a PowerPC only release, while later releases included native support for the x86.

{| class="wikitable"
|-
! Version
! Released
! Corresponds With
|-
! Darwin 1.0
! April 2000
! Mac OS X Developer Preview 4
|-
! Darwin 1.2
! October 2000
! Mac OS X Public Beta
|-
! Darwin 1.3.1
! April 2001
! Mac OS X 10.0.1
|-
! Darwin 1.4.1
! Fall 2001
! Mac OS X 10.1
|-
! Darwin 5.1-5.5
!
! Mac OS X v.10.1.1-10.1.5
|-
! Darwin 6.0-6.8
!
! Mac OS X v.10.2.0-10.2.8
|-
! Darwin 7.0-7.9
!
! Mac OS X v.10.3.0-10.3.9
|-
! Darwin 8.0-8.11
!
! Mac OS X v.10.4.0-10.4.11
|-
! Darwin 9.0-9.1
!
! Mac OS X v.10.5.0-10.5.1
|}

=== Versioning confusion ===

As mentioned over on [http://www.nextcomputers.org/forums/viewtopic.php?p=7625 this thread at nextcomputers.org], that although there was a released memo explaining the logic behind the version number changes so that way Darwin would match up to the build number of XNU, it lead to great confusion. However this letter at least sets it to the original intent.

<pre>
New Darwin Versioning Scheme

As of Software Update 1 for Mac OS X v10.1, we have moved to a new
numbering policy for the Darwin portions of Mac OS X. It you type
"uname -a" from the command-line, you will see that the Darwin version
number has changed to "5.1" (actually 5.1.0), which better aligns
Darwin's numbering scheme with our internal build processes. The "5"
refers to the major release - "4" was Mac OS X v10.0, and the earlier
numbers represented developer releases. The minor version '1' is
generally the update number, and the final number (e.g, the "0" in
5.1.0) represent 'variants'. For example, under the new scheme, the
Darwin in Mac OS X v10.1 would've been '5.0.0' whereas the Open Source
Darwin version released immediately afterwards (1.4.1) would've been
"5.0.1".

We apologize for any disruption this may cause existing projects, and
hope this change will enable us to provide greater consistency in the
future.

Sincerely,
Ernie Prabhakar
</pre>

The following releases can be downloaded [https://web-beta.archive.org/web/20090903180055/https://opensource.apple.com/static/iso/ here]:
*[https://sourceforge.net/projects/aapl-darwin/files/Darwin-1.0/Apple-CDROM/Darwin-1.0.toast/download Darwin 1.0 - OS X 10.0 DP 4] - [[Darwin 1.0 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwinx86-141.iso.gz Darwin 1.4.1 - OS X 10.1 x86] - [[Darwin 1.4.1 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwinppc-141.cdr.gz Darwin 1.4.1 - OS X 10.1 ppc] - [[Darwin 1.4.1 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwinx86-602.iso.gz Darwin 6.0.2 - OS X 10.2 x86] - [[Darwin 6.0.2 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwinppc-602.cdr.gz Darwin 6.0.2 - OS X 10.2 ppc] - [[Darwin 6.0.2 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwin-701.iso.gz Darwin 7.0.1 - OS X 10.3.1 unknown] - [[Darwin 7.0.1 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwinx86-801.iso.gz Darwin 8.0.1 - OS X 10.4 x86] - [[Darwin 8.0.1 Release notes|Release notes]]
*[https://opensource.apple.com/static/iso/darwinppc-801.cdr.gz Darwin 8.0.1 - OS X 10.4 ppc] - [[Darwin 8.0.1 Release notes|Release notes]]

=== Getting this to run ===
Compatibility is a mixed bag, and it was just as bad at the time, and on real hardware.

==== Darwin 1.4.1 ====
Recently I've found that it will run using Qemu 2.7.
I didn't have to do anything special and I've written about it [https://virtuallyfun.superglobalmegacorp.com/2016/09/20/darwin-1-4-1-installs-on-qemu-2-7/ here].

==== Darwin 8.0.1 ====
Darwin 8.0.1 to run under [[Qemu]] 0.13.0. As far as I know 1.4.1, has some kind of CPU issue, and 6.0.1 and 7.0.1 all have ACPI issues.
Installation is pretty simple, a config like this is more then enough to get going:

<pre>
C:\qemu-0.13.0>qemu.exe -L pc-bios -m 256 -hda 4gc.disk -cdrom 801.iso -net nic,model=e1000 -net user -no-reboot -boot d</pre>



{{Nav Unix}}

[[Category: Apple Operating Systems]]