Setup - First Boot Hang

[Stuart]

After DOS setup runs, the machine hangs when it boots for
the first time. The start up screen appears, the
text "Starting up..." appears, the progress bar goes to
50%, the marquee band keeps rolling but nothing happens.
Let it run for 12 hours, nothing.
In boot log mode, it gets to "viaagp.sys" driver and stops.
Went into Recovery Console and renamed that driver, and
the one previous (ndis.sys), but still gets
to "viaagp.sys" and locks up. I'm guessing that boot log
isn't accurate or some kind of override is being employed
by start up.

This is an older PC board, 2000, but pretty common. Any
ideas anyone ?

thanks

 

[Dave Patrick]

Try removing all non-essential hardware and start setup again. 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.

Once you get the OS installed then add the hardware back in one at a time.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


:
| After DOS setup runs, the machine hangs when it boots for
| the first time. The start up screen appears, the
| text "Starting up..." appears, the progress bar goes to
| 50%, the marquee band keeps rolling but nothing happens.
| Let it run for 12 hours, nothing.
| In boot log mode, it gets to "viaagp.sys" driver and stops.
| Went into Recovery Console and renamed that driver, and
| the one previous (ndis.sys), but still gets
| to "viaagp.sys" and locks up. I'm guessing that boot log
| isn't accurate or some kind of override is being employed
| by start up.
|
| This is an older PC board, 2000, but pretty common. Any
| ideas anyone ?
|
| thanks

 

[Stuart]

Hi Dave,

Thanks for responding.

On this particular system deleting partitions might be a
valid choice, however, I have 4 more servers to do after
this. Explaining to my clients that I have to wipe out
their systems to "upgrade" might be met with skepticism.
This is the test bed dual boot system.

I pulled the non-essential hdw and rebooted each time.
Nothing changed, Do you think I should pull the non-ess.
hdw and rerun setup ? I didn't try that.

I'm a Win developer since Win 2.03 and it's hard for me to
believe with all the advances the OS's have made since
then, we have no better way to diagnose than
to "reformat" ??

As a developer I can diagnose problems down to the driver
or a wrong version dll. Is this not possible with the boot
logs and the safe modes and Recovery Console ? Why do all
these tools exist if they can't be used for diagosing
problems ?

Gettin' frustrated...

Thanks.

 

[Dave Patrick]

OK ... I guess the "After DOS setup runs" threw me a little. Thinking you
were running setup from a win9x floppy or such. As far as the hardware, if
it is all on the Windows 2000 HCL, then removing any of it shouldn't be
necessary. The setupapi.log may reveal something.

http://www.microsoft.com/windows2000/techinfo/administration/setupapi.asp

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


:
| Hi Dave,
|
| Thanks for responding.
|
| On this particular system deleting partitions might be a
| valid choice, however, I have 4 more servers to do after
| this. Explaining to my clients that I have to wipe out
| their systems to "upgrade" might be met with skepticism.
| This is the test bed dual boot system.
|
| I pulled the non-essential hdw and rebooted each time.
| Nothing changed, Do you think I should pull the non-ess.
| hdw and rerun setup ? I didn't try that.
|
| I'm a Win developer since Win 2.03 and it's hard for me to
| believe with all the advances the OS's have made since
| then, we have no better way to diagnose than
| to "reformat" ??
|
| As a developer I can diagnose problems down to the driver
| or a wrong version dll. Is this not possible with the boot
| logs and the safe modes and Recovery Console ? Why do all
| these tools exist if they can't be used for diagosing
| problems ?
|
| Gettin' frustrated...
|
| Thanks.

 

[Stuart]

Thanks Patrick,

Hopefully this will help. I also got an upgrade for the
bios. Between the 2 maybe I'll get lucky !

thanks

 

[Bryan]

Hey, guess what Dave. You can run mkboot32.exe in DOS
mode, you can only run makeboot.exe. And guess what else,
I try installing Win2K again and I get a Disk I/O error
Status=00001006 NTDetect Failed message. I can't find a
darn thing on Micrsoft about this specific error! Now I
sit dead in the water with a computer I can't install
Windows on. Funny things is, I had Win2K installed
perfectly. Then while trying to install the proper video
driver, something got mucked up. Then I got some error
during bootup when the Windows 2000 with NT technology
startup screen in on. The error paints itself write in
the middle of that image, and I can't boot any further,
ANYMORE. So I try install Win2K all over again, and I end
up at the point above with the Disk I/O error. Mail me a
gun, so I can shoot the system or myself, which ever seems
good to me at the time. Please cc: me on your reply.

 

[Dave Patrick]

Usually means Ntdetect.com file is missing or damaged. Recreate the setup
disks or better yet just boot the Windows 2000 install CD-Rom.


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


:
| Hey, guess what Dave. You can run mkboot32.exe in DOS
| mode, you can only run makeboot.exe. And guess what else,
| I try installing Win2K again and I get a Disk I/O error
| Status=00001006 NTDetect Failed message. I can't find a
| darn thing on Micrsoft about this specific error! Now I
| sit dead in the water with a computer I can't install
| Windows on. Funny things is, I had Win2K installed
| perfectly. Then while trying to install the proper video
| driver, something got mucked up. Then I got some error
| during bootup when the Windows 2000 with NT technology
| startup screen in on. The error paints itself write in
| the middle of that image, and I can't boot any further,
| ANYMORE. So I try install Win2K all over again, and I end
| up at the point above with the Disk I/O error. Mail me a
| gun, so I can shoot the system or myself, which ever seems
| good to me at the time. Please cc: me on your reply.