IBM Thinkpad 600x issues

[djc]

I imaged a Thinkpad 600x with WinXP Pro sp1. The image was created using
setup manager and sysprep. I have done this many times over for win2k
systems but this is the first using XP and the XP versions of setup manager
and sysprep.

Are there any known issues with WinXP Pro (i have sp1) and IBM Thinkpad
600x's? The image has been deployed to 3 different machines and all are
flaky? The critical update for kb824105 keeps failing from the windows
update site. I just won't install!

Before I start a total sweep of updating everything under the sun on this
does anyone know of any known issues?

thanks in advance. any info is appreciated.

 

[Guest]

Hi

Are the 3 different machines have the same spec as IBM Thinkpad600X
If the answer is NO, you need to perform a repair installation of XP on the other 3 machines

For could not update kb824105, try go to C: System/system32/catroot2 and rename the catroot2 folder to oldcatroot2 and then reboot

Pete

----- djc wrote: ----

I imaged a Thinkpad 600x with WinXP Pro sp1. The image was created usin
setup manager and sysprep. I have done this many times over for win2
systems but this is the first using XP and the XP versions of setup manage
and sysprep

Are there any known issues with WinXP Pro (i have sp1) and IBM Thinkpa
600x's? The image has been deployed to 3 different machines and all ar
flaky? The critical update for kb824105 keeps failing from the window
update site. I just won't install

Before I start a total sweep of updating everything under the sun on thi
does anyone know of any known issues

thanks in advance. any info is appreciated

 

[djc]

thanks for the reply. can you give me a little more detail on that
suggestion? for example, whats that folder for?

Hi,

Are the 3 different machines have the same spec as IBM Thinkpad600X?
If the answer is NO, you need to perform a repair installation of XP on the other 3 machines.

For could not update kb824105, try go to C: System/system32/catroot2 and

rename the catroot2 folder to oldcatroot2 and then reboot.