Newsgroups: comp.os.minix
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!in2.uu.net!caen!news.umass.edu!news.hampshire.edu!hamp!aswNS
From: aswNS@hamp.hampshire.edu (Albert S Woodhull)
Subject: Re: TINYROOT hangs at "/dev/" on VECTRA 286
Message-ID: <c197cb$8272.3a@news.hampshire.edu>
Date: Mon, 25 Dec 1995 13:39:02 GMT
References: <4blom5$d6u@mark.ucdavis.edu>
Organization: Hampshire College, Amherst MA
X-Newsreader: TIN [version 1.2 PL2]
Lines: 42

On 25 Dec 1995 08:51:17 GMT Keith Kong (kkong@vision.ece.ucdavis.edu)
wrote in comp.os.minix:

> I am trying to install minix 1.7.1 on an HP Vectra 286
> machine with 1.6Meg RAM using TINYROOT.  After successfully
> loading the skeleton files onto the ramdisk, the message
> asking the user to finish the name of the device to mount on
> /usr comes up and then the computer hangs.  Nothing I type
> shows up and cntrl-alt-del doesn't work (maybe it's not supposed
> to?).  In any event, I can only turn off the computer and restart.

The fact that you got the message asking for the device to mount on /usr 
means that the kernel booted successfully and the RAM disk was loaded 
to the point that exectuion of the /etc/rc script began. 

I do not have any familiarity with the HP Vectra machine. If it has 1.6M
of memory I would assume that means 1M in addition to the DOS standard 
640K. If it is ordinary extended memory Minix can use it. If it uses it
as expanded memory the extra 1M won't be seen by Minix. A memory shortage
coyuld explain your problem.

I would suggest trying to boot without loading the RAM disk, keeping the 
root on the floppy. The way to do this is the following:

At  the "Press = to boot Minix" prompt press ESC to enter the boot monitor.
Type "rootdev=bootdev"
Type "main" and you will see the "Press = ..." prompt again. Do it.

This will maximize the amount of memory for running processes.

If this doesn't work I would suspect either your disks or an 
incompatibility in your system. If you can get the use of someone else's
computer (preferably a totally generic PC) you can see if the disks work
OK on that without disturbing anything on your friend's system if you 
don't proceed to the actual installation.

Albert S. Woodhull, Hampshire College, Amherst, MA
awoodhull@hamp.hampshire.edu
woodhull@shaysnet.com
413-549-2962



