Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!ge-dab!tarpit!bilver!vicstoy!bjrinn
From: bjrinn@vicstoy.UUCP (Jason Rinn)
Newsgroups: comp.os.minix
Subject: Re: NMI during boo
Message-ID: <1991May19.065825.14964@vicstoy.UUCP>
Date: 19 May 91 06:58:25 GMT
References: <1991May2.221459.7701@hubcap.clemson.edu> <1743@targon.UUCP>
Organization: The Philosophers Stone BBS, Orlando FL
Lines: 45

Well, its my first posting too, so here goes.
I appologize for my spelling and my terse summaries of previous messages. .ti

In article <1743@targon.UUCP> jan@targon.UUCP (Jan van Zeggelaar) writes:
>Hello out there. This is also my first posting to the net, so bear with me too.
>
>In article <1991May2.221459.7701@hubcap.clemson.edu> tboatma@hubcap.clemson.edu (Tommy Boatman) writes:
>>Hello All (this is my first post so please bear with me)
>>
>>I just became the proud owner of the MINIX demo disk for the IBM PC.
>>I got the file written to a disk and then tried to boot it.
>>At first everything seemed fine...but when i typed u to start MINIX
>>The system gave me a message at the top of the screen that read
>>
>>Nonmaskable interrupt
>>process number -9, pc=0x0060:0x00005c95
>>
>>Kernel panic: exception in kernel, mm or fs
>>Type any key to reboot
>>
  [describes his machine]   ]
>>-tommy
>
  [describes his machine also]]]
>
>                Jan Z.

I also had the problem described above, and managed to find a solution of
sorts.
It seems that the line in the /etc/rc that sets the date causes these 
interrupts.  At least, commenting it out prevented them.
The strange part is, on my system, they only occured when I first placed
the system on my HD and booted off a 360K disk.  Now, I boot off a 
720K disk with an exact copy of the same 360K, and it works fine.

BTW, my machine is a Pionex/Fountain 386sx with a WD 120M IDE HD a 1.2M and
1.44M floppy drive.

The temporary solution is to comment out the /etc/date line in the /etc/rc 
file, either with a friends machine or maybe the BIOS boot disk.
I hope this works for you.

             Jason Rinn

             bjrinn@vicstoy.UUCP