Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!amdcad!sun!pitstop!sundc!seismo!uunet!munnari!otc!metro!ditsyda!evans
From: evans@ditsyda.oz (Bruce Evans)
Newsgroups: comp.os.minix
Subject: Re: Any clues why?
Message-ID: <1755@ditsyda.oz>
Date: 7 Feb 89 10:36:01 GMT
References: <19562@dhw68k.cts.com>
Organization: CSIRO DIT Sydney, Australia
Lines: 21

in article <19562@dhw68k.cts.com>, allan@dhw68k.cts.com (Alan Perry) says:
>Well, despite my continued (though slow) efforts, Minix still does not run
>on my Unisys PW2 850 (Mitsubishi MP386).  I am running with 1.1 with two

Whatever happened to the kernel debugger I posted last December? After a
year's practice with it :-), I can usually locate kernel bugs within a few
minutes. I rarely need or use debugging printfs. The debugger has a good
chance of working whether Minix does or not, since it is essentially
independent.

>['=' key works but Minix crashes soon after the floppy light turns on]

The '=' key "always" works unless you're enhancing and putting bugs into
the bootstrap programs. Getting the floppy light shows that all the
hardware tasks have at least started. If the keyboard is still alive an
F1 dump will probably show FS stuck waiting for WINCHE or FLOPPY. Otherwise
the interrupt handling is probably inconsistent as discussed for PS/50's.

I suspect the floppy. What about converting bios_wini.c to bios_floppy.c?

Bruce Evans		evans@ditsyda.oz.au
D