Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!star.cs.vu.nl!ast@cs.vu.nl
From: ast@cs.vu.nl (Andy Tanenbaum)
Newsgroups: comp.os.minix
Subject: Request for PS/2 help from Columbia University
Message-ID: <3777@ast.cs.vu.nl>
Date: 23 Oct 89 12:58:38 GMT
Sender: ast@cs.vu.nl
Reply-To: ast@cs.vu.nl (Andy Tanenbaum)
Organization: VU Informatica, Amsterdam
Lines: 34


Hi again.

First, I'd like to thank everyone who helped me get my minix system up
and running on an AT, and I'm now going to join the ranks of minix
hacks.  I haven't seen any talk recently about minix being ported to
PS/2's -- has anyone completed this task?  Could someone send me
source code or diffs to get something bootable on a PS/2?

People here in our CS dept. have apparently gotten more serious about
wanting to finish this port, because now I've got a desk with an AT
and a PS/2 model 80 -- both completely at my disposal until this is
done.  So right now, the AT is running minix, the PS/2 boots DOS 4.00
off the hard disk, and all attempts to bring minix over via floppy
have failed.

So far, all I've *really* done is set up the AT, apply a few patches
that to allow it to access a 1.44 meg floppy, and *attempt* to make a
boot diskette for the PS/2.  Although it did boot and I was able to
check, list, and make file systems, '=' caused an immediate hang.
But you all probably know that.


In looking at the archives on bugs.nosc.mil, I saw a few patches to
bios_wini.c and floppy.c for the PS/2, but nothing in kernel/main.c,
i8259.c, or anything that appeared like it would solve the interrupt
problem at all, at least enough to get a floppy-only minix running on
a PS/2.  I'm in the unique situation of having next to no
documentation on the PS/2, but the perfect environment to do this
port.

Any help would be muchly appreciated.

Please reply to Steve Abrams (abrams@cs.columbia.edu)