Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!seismo!hal!baugh
From: baugh@hal.CSS.GOV (Nam Myoho Renge Kyo)
Newsgroups: comp.os.minix
Subject: Disk Drive Install
Keywords: MINIX 1.1
Message-ID: <181@hal.CSS.GOV>
Date: 4 Oct 89 15:11:40 GMT
Reply-To: baugh@hal.css.gov
Organization: ENSCO Inc., Melbourne FL
Lines: 45

'Folks,

	Well the disk problem continues. First a few corrections, in my last 
posting I said /dev/hd2, when I really meant /dev/hd5.  Woops. Also 
yes I did realize that it wouldn't be exactly 20000, I hadn't calculated it
out exactly.  Thanks to everybody who pointed this out.  That's what I get 
for not having the READ_ME file with me. 

Ok, so I also got directed to "...copy at_wini.c to wini.c in the kernel 
directory and then rebuild kernel."  which I have done.

SIDE NOTE: My system only has 1 floppy [1.2 mb] with it's 2 hard disks,
	   since it came in a baby-AT case.  I'll be getting a tower case and
	   I have a 3.5 inch floppy left over from my ol'PC, so all I've have
	   to do is get a 360kb drive when I buy the tower case. (However
	   that's in the future) 

Ok, so thorough a lot of floppy swappings, I get the kernel rebuilt with
at_wini.c in place, make a new bootdisk, re-boot, notice the difference in
MINIX size and a slightly smaller amount of ram available (all expected of
course...)  Then I create /dev/hd5 -> /dev/hd9 and try to build a file
system on /dev/hd6.  BOOM.  (well not that drastic, but....)  I get 
the following error :

		Error: put_block couldn't write
		Line 1 being processed when error detected.

	Now, here are some other facts that may help or be part of the
the problem.  First the disks were 'set-up' with SEAGATES OnTRACK Disk
Manager -- DM.  I've looked at them with fdisk (MSDOS 3.3) and they seem
to be partitioned ok. The Seagate 251 (40mb) is divided in half, one 
dos partition, the other is non-DOS according to fdisk, the Seagate 225 (20mb) 
is a single partition, non-DOS according to fdisk.  Now, when I have installed
the device driver the 40mb looks like C: & D:, the 20mb E:  .   Without
the driver, I couldn't get to D or E, but C looks fine. One other time tried
this, I could get to the first partition of the 40mb (C) and the 20mb, but the
20mb was accessed as D not E and the second partition of the 40mb was 
unavailable. The disk drive controller is a genunine IBM controller (from an
6mhz PC-AT) and works fine under dos.    Am I experiencing a MINIX 1.1 at_wini
problem, or does it look like hardware??
-- 
	Earl D. Baugh Jr.
	ENSCO INC.
	Internet : baugh@hal.CSS.GOV
	"Open the pod bay doors...."