RIS Problem - Hangs after RIPrep

[Tom Deaton]

Would appreciate help on a RIS problem I've been fighting. Computer with VIA
chipset. Windows 2000 SP4.

I install the W2K Pro base image from RIS server and it installs and runs
fine. I then RIPrep the image back to the server and attempt to install it.
The system hangs at Windows 2000 Setup Please wait... dialog.

The setupapi.log file indicates the VIA Tech Power Management device is
being installed over and over and over ([NO_DRV] section).

Any suggestions?

 

[Bill Curtis [MSFT]]

What happens if you try to removing/disabling the VIA Tech Power Management
Device? Does the problem still occur?

 

[TomD]

Bill, thanks for response.

Removing and/or disabling the device doesn't help.

What happens if you try to removing/disabling the VIA Tech Power Management
Device? Does the problem still occur?

--
- Bill Curtis [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Would appreciate help on a RIS problem I've been fighting. Computer with VIA
chipset. Windows 2000 SP4.

I install the W2K Pro base image from RIS server and it installs and runs
fine. I then RIPrep the image back to the server and attempt to install it.
The system hangs at Windows 2000 Setup Please wait... dialog.

The setupapi.log file indicates the VIA Tech Power Management device is
being installed over and over and over ([NO_DRV] section).

Any suggestions?

 

[Bill Curtis [MSFT]]

Are you attempting to install the RipRep image to the same system?

--
- Bill Curtis [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Bill, thanks for response.

Removing and/or disabling the device doesn't help.

What happens if you try to removing/disabling the VIA Tech Power Management
Device? Does the problem still occur?

--
- Bill Curtis [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Would appreciate help on a RIS problem I've been fighting. Computer

with
VIA

chipset. Windows 2000 SP4.

I install the W2K Pro base image from RIS server and it installs and runs
fine. I then RIPrep the image back to the server and attempt to

install
it.

The system hangs at Windows 2000 Setup Please wait... dialog.

The setupapi.log file indicates the VIA Tech Power Management device is
being installed over and over and over ([NO_DRV] section).

Any suggestions?

 

[TomD]

Yes. I install the base W2K Pro which installs and runs fine. I RiPrep an
image then attempt to install the RiPreped image back to the exact same
system and it fails. The RiPreped image hangs on the Windows 2000 Setup
Please wait... dialog

Are you attempting to install the RipRep image to the same system?

--
- Bill Curtis [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Bill, thanks for response.

Removing and/or disabling the device doesn't help.

What happens if you try to removing/disabling the VIA Tech Power Management
Device? Does the problem still occur?

--
- Bill Curtis [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."



Would appreciate help on a RIS problem I've been fighting. Computer with
VIA
chipset. Windows 2000 SP4.

I install the W2K Pro base image from RIS server and it installs and runs
fine. I then RIPrep the image back to the server and attempt to install
it.
The system hangs at Windows 2000 Setup Please wait... dialog.

The setupapi.log file indicates the VIA Tech Power Management device is
being installed over and over and over ([NO_DRV] section).

Any suggestions?

 

[Bill Curtis [MSFT]]

Do both images (Cd-based and Riprep) share the same NTOSKRNL.EXE? Also,
make sure that your CD-Based image and your Riprep image are at the same
Service Pack level.


- Bill Curtis [MSFT]
“This posting is provided "AS IS" with no warranties, and confers no
rights.”

 

[TomD]

Yes, both images have the identical NTOSKRNL.EXE.

Regarding service pack level, the base Pro image is SP4. The Riprep-ed image
would also be SP4. Nothing is done to the base Pro image prior to Riprep-ing
it back to the server.