I was given this machine many years ago. When I first went to work as a computer engineer for the Army, these machines were servers used for office automation. These machines were equiped with very large external disks for the time, and we could basically do everything you can do today with the windows clients and servers.
I have used it to test all my iSBC 012CX, iSBC 010CX, and iSBC 020CX memory boards. I also used it to test all of my iSBC 286/10 and iSBC 286/10A CPU boards. All the working boards come up in the iSDB monitor found in the ROMs.
Here is a picture of the system in one of my relay racks.
1236 MST 13 January 2012
I have been working off and on on the Intel 310 computer. I have known good iSBC 286/10 CPU boards. I have known good iSBC 020CX and EX RAM boards. The system will come up and the debugger works correctly.
The system needs an iSBC 215G with iSBX 218A board to work with the floppy and the Maxtor WD-1140 hard drive. The system contains a 5-1/4" 360K byte floppy drive. With these items in the system, I get the mechanical sound of a hard drive reset. No activity on the floppy. I have also tried and iSBC 214 intergrated controller with no luck. So either the boards are bad or the hard drive was wipped. This system was operational and booted XENIX version 3.X.
I have the load disk images for XENIX 3.X and most of the manuals. I had hoped to get this system to boot and operate on the original hardware and software. I may try to reload the system from disks generated from the disk images.
With a working system, I could then write a driver to use a PATA disk on a iSBX 350 board. THis would give me a multigigabyte hard drive for XENIX. I am not sure what the limits are on drive or partition size, but we used to have gigabyte SMB drives on these systems in the day.
So if I cannot load the original system, then I may need to emulate the system, and get the software developed there to be able to boot the actual system on the new hardware. This is going to require a major effort! An alternative operating system is Minix. It will run native on an 8086 or 80286.
1317 MST 20 October 2012
I have an SCO Xenix-386 V2.3.4 system with the full development system running as a virtual machine under VirtualBox. It has no network connectivity but will create and mount floppy disk images. This is one way to move data to/from the Xenix system. I have also been looking at TCP/IP stacks for which I have the source code. This is probably the mest long term solution to the problem. In the mean time, I am modifing one of my floppy disk managenent tools to allow we to create, read files from and write files to an SCO V3 floppy. I have enough data to decode the SCO superblock and figure out the complete disk format.
The floppy image of the Intel Xenix-286 V3.0 disks is radically different from the SCO Xenix-386 V2 disks. The Intel disks have a much simpler superblock. Obviously, the Intel floppy disk images will not mount on the SCO Xenix system.
I have broken out all the Intel Xenix-286 disk images. I have also converted them to raw .IMG files. The short T0H0 has been padded out to be 8192 bytes long like all the other tracks and heads. I have both the .DMK and .IMG files loaded in the archives. The .DMK files will create a complete set of 5-1/4 floppy disks. The .IMG files I am using to decode the disk format and for loadable images for virtual machines and emulators.
The operating system disk images are located on the page above under the Operating Systems heading.
1437 MST 17 November 2012