WIN2K on new drive

  • Thread starter Thread starter MTT
  • Start date Start date
M

MTT

I'm replacing a failed 40G drive with a new 80G drive. The
system detects the drive just fine. I've booted using a
WIN98 boot disk. From DOS I've fdsk'd to create a new
partition and formatted. When I reboot from the WIN2K CD,
all seems to go well until the machine reboots after
coping installation files. When it reboots I get a message
like "window root\system32\ntoskrnl.exe file missing or
corrupt, reinstall this file". If I reboot from the CD and
try to repair the installation, Windows tells me the disk
is corrupt. So, I reformat from DOS and try again only to
get the same result. CD has been used successfully many
times and is not scratched up or otherwise visibly
damaged. If I boot into DOS, using the WIN98 disk again, I
can see all the WINNT files on drive C:, including
NTOSKRNL.exe in.

I've run chkdisk and scandisk and no problems have been
found.

One thing I did notice was the size of NTOSKRNL.exe on C:
is smaller than what I find on the CD in the I386
directory??

Anyone know how to copy a file from CD to hard drive in
DOS? When I try I get file not found messages.
 
To do a clean install, either boot the Windows 2000 install CD-Rom or setup
disks. The set of four install disks can be created from your Windows 2000
CD-Rom; change to the \bootdisk directory on the CD-Rom and execute
makeboot.exe (from dos) or makebt32.exe (from 32 bit) and follow the
prompts.

When you get to the point, delete the existing NTFS and or other partitions
found. After you delete the partition(s) abort the install, then again
restart the pc booting the CD-Rom or setup disks to avoid unexpected drive
letter assignments with your new install.
 
Dave-
I tried it your way and get the message
"setup is unable to format the partition, select a
different partition". Of course there is no other
partition. Got any other ideas?
-----Original Message-----
To do a clean install, either boot the Windows 2000 install CD-Rom or setup
disks. The set of four install disks can be created from your Windows 2000
CD-Rom; change to the \bootdisk directory on the CD-Rom and execute
makeboot.exe (from dos) or makebt32.exe (from 32 bit) and follow the
prompts.

When you get to the point, delete the existing NTFS and or other partitions
found. After you delete the partition(s) abort the install, then again
restart the pc booting the CD-Rom or setup disks to avoid unexpected drive
letter assignments with your new install.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

MTT said:
I'm replacing a failed 40G drive with a new 80G drive. The
system detects the drive just fine. I've booted using a
WIN98 boot disk. From DOS I've fdsk'd to create a new
partition and formatted. When I reboot from the WIN2K CD,
all seems to go well until the machine reboots after
coping installation files. When it reboots I get a message
like "window root\system32\ntoskrnl.exe file missing or
corrupt, reinstall this file". If I reboot from the CD and
try to repair the installation, Windows tells me the disk
is corrupt. So, I reformat from DOS and try again only to
get the same result. CD has been used successfully many
times and is not scratched up or otherwise visibly
damaged. If I boot into DOS, using the WIN98 disk again, I
can see all the WINNT files on drive C:, including
NTOSKRNL.exe in.

I've run chkdisk and scandisk and no problems have been
found.

One thing I did notice was the size of NTOSKRNL.exe on C:
is smaller than what I find on the CD in the I386
directory??

Anyone know how to copy a file from CD to hard drive in
DOS? When I try I get file not found messages.
Click to expand...


.
Click to expand...
 
yes, just as you instructed.
-----Original Message-----
Did you delete the partition and let Windows 2000 setup create a new one?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

Dave-
I tried it your way and get the message
"setup is unable to format the partition, select a
different partition". Of course there is no other
partition. Got any other ideas?
Click to expand...


.
Click to expand...
 
I'm wondering if the drive controller or mb bios is having a problem with
the larger drive. Or possibly the drive is defective. Check the drive
manufacturer's web site for a utility to check the drive. Are you using the
IDE controller on the mb? If so check the mb manufacturer for an updated
bios. If you're F6'ing at "setup is inspecting...." and supplying a
controller driver, then check the controller manufacturer's web site for the
latest Windows 2000 driver for your controller.
 
I'm replacing a failed 40G drive with a new 80G drive. The
system detects the drive just fine. I've booted using a
WIN98 boot disk. From DOS I've fdsk'd to create a new
partition and formatted. When I reboot from the WIN2K CD,
all seems to go well until the machine reboots after
coping installation files. When it reboots I get a message
like "window root\system32\ntoskrnl.exe file missing or
corrupt, reinstall this file". If I reboot from the CD and
try to repair the installation, Windows tells me the disk
is corrupt. So, I reformat from DOS and try again only to
get the same result. CD has been used successfully many
times and is not scratched up or otherwise visibly
damaged. If I boot into DOS, using the WIN98 disk again, I
can see all the WINNT files on drive C:, including
NTOSKRNL.exe in.
Click to expand...

It would seem that your computer does not like the hard drive. In your
BIOS, what does the computer report for the drive size?
 
I have the latest BIOS for the MB and Seagate says their
disks don't require any special drivers. According to all
the trouble shooting info I can find on the Seagate site,
the drive is OK. I have a support request into Seagate and
am going to try a different WIN2K CD tomorrow. I'm
thinking of giving it a try with a smaller primary and
than adding a logical partition.

baffled.

-----Original Message-----
I'm wondering if the drive controller or mb bios is having a problem with
the larger drive. Or possibly the drive is defective. Check the drive
manufacturer's web site for a utility to check the drive. Are you using the
IDE controller on the mb? If so check the mb manufacturer for an updated
bios. If you're F6'ing at "setup is inspecting...." and supplying a
controller driver, then check the controller
Click to expand...
manufacturer's web site for the
latest Windows 2000 driver for your controller.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

yes, just as you instructed.
Click to expand...


.
Click to expand...
 
Not talking about a disk drive driver. Drive controller driver. In other
words the device the drive cable plugs into.
 
MTT said:
I'm replacing a failed 40G drive with a new 80G drive. The
system detects the drive just fine. I've booted using a
WIN98 boot disk. From DOS I've fdsk'd to create a new
partition and formatted. When I reboot from the WIN2K CD,
all seems to go well until the machine reboots after
coping installation files. When it reboots I get a message
like "window root\system32\ntoskrnl.exe file missing or
corrupt, reinstall this file". If I reboot from the CD and
try to repair the installation, Windows tells me the disk
is corrupt. So, I reformat from DOS and try again only to
get the same result. CD has been used successfully many
times and is not scratched up or otherwise visibly
damaged. If I boot into DOS, using the WIN98 disk again, I
can see all the WINNT files on drive C:, including
NTOSKRNL.exe in.

I've run chkdisk and scandisk and no problems have been
found.

One thing I did notice was the size of NTOSKRNL.exe on C:
is smaller than what I find on the CD in the I386
directory??

Anyone know how to copy a file from CD to hard drive in
DOS? When I try I get file not found messages.
Click to expand...
W2K doesn't install on FAT32 partitions greater than 32 Gigs. It doesn't
behave properly on disks using translation utilities either. The suggestion
is to either use ntfs or create a system partition less than 32 Gigs.
 
Check your memory. I had file corruption problems like this once and the
culprit was a bad stick of memory.
 
Back
Top