Path: utzoo!attcan!uunet!zephyr!tektronix!psueea!parsely!bucket!leonard
From: leonard@bucket.UUCP (Leonard Erickson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: wierd problems during HD boot
Keywords: config.sys
Message-ID: <1487@bucket.UUCP>
Date: 19 Jun 89 20:28:58 GMT
References: <598@aablue.UUCP>
Reply-To: leonard@bucket.UUCP (Leonard Erickson)
Organization: Rick's Home Grown Unix; Portland, OR
Lines: 35

In article <598@aablue.UUCP> jb@aablue.UUCP (John B Scalia) writes:
<The problem I'm encountering is that the unit, while booting from the
<hard disk doesn't seem to want to read config.sys or its autoexec.bat
<file. I've tried doing low levels with both Disk Manager from Ontrack
<and Everex's own disk utilities. Both give the same end results.
<
<In either case I low level, partition, and logically format the drive
<into what should be C:, D:, & E: drives. When I boot the unit, everything
<looks normal, except stupid things, like my environment size and the path
<I want, never get set.

First, did you format C: with the /S parameter (I'd assume so, as otherwise
it wouldn't boot at all). Second, use FDISK and see if the partition is marked
ACTIVE.

The next thing is to re-check your config.sys. It sounds like you are using
the SHELL command. The format of this command is *very* critical!

shell=C:\command.com C:\ /p /e:512

c:\command.com	the command interpeter is command.com
c:\		reload from the root directory on drive C
/p		"permanent" (ie exit will be ignored
		AND AUTOEXEC.BAT WILL BE EXECUTED!)
/e:512		set environment space to 512 bytes
		(512 paragraphs in DOS 3.1)

The order and the spaces can be critical. My guess is that you don't have a
/p.

-- 
Leonard Erickson		...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I'm all in favor of keeping dangerous weapons out of the hands of fools.
Let's start with typewriters." -- Solomon Short