Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!pacbell!att!ihlpl!knudsen
From: knudsen@ihlpl.ATT.COM (Knudsen)
Newsgroups: comp.os.os9
Subject: Re: Hard disk startup problems
Summary: INIZ syntax trap
Keywords: Burke, hard disk, Problems
Message-ID: <6798@ihlpl.ATT.COM>
Date: 20 Sep 88 18:08:50 GMT
References: <14395@agate.BERKELEY.EDU> <23370@wlbr.EATON.COM>
Distribution: na
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 18

Since Pete reminded us to INIZ devices that aren't in
the boot, I thought I'd mention that in my experience,
INIZ is more likely to do something useful if you OMIT
the '/' from the device name, ie, say

INIZ H0  but not INIZ /H0.

As Pete would say, I don't know why.  I guess INIZ wants
module names (like LINK, UNLINK, DEBUG do), not path names.
Makes sense, but we phone-co OS-bred types always want to
put slashes on device names ;-).

BTW, I did a lot of hard drive work with a hand-loaded
(non booted) driver-descriptor pair and had absolutely
no trouble with it other than wasting almost 8K of precious
system memory.  (That's 16K if you forget to MERGE the .dd and .dr).
It's a shame that an early rumor got started
that you can't load .dd's and .dr's in Level II.
It just costs you more memory.