noseph

Markus, You should take a look at Black Viper's Web Site (http://www.blackviper.com/index.html). I have used it for years to help understand Windows configurations.

Sorry I didn't get back to you sooner, I took a very long weekend. Just paste 'kb836426' into Google and take the first support.microsoft site returned. It should be something like 'http://support.microsoft.com/default.aspx?scid=kb;en-us;836426'

SamChangePasswordUser error was not my real problem. I was receiving that error after the initial failure of Mini-Setup and a reboot. The error from the initial failure of Mini-Setup was - Setup: (critical error) Encountered an unhandled exception (c0000005) at address 5f1a340b with the following parameters: 0 14. I found kb836426 that resolves a similar problem with W2K3. I tried the fix and it works for WXPsp2. I had Telephony service disable in my sysprep image. Once I set it to automatic, started it and ran sysprep -factory. everything is fine.

I found kb836426 that resolves a similar problem with W2K3. I tried the fix and it works for WXPsp2. I had Telephony service disable in my sysprep image. Once I set it to automatic, started it and ran sysprep -factory. Everything is fine.

I am trying to deploy a XPsp2 image. The sysprep factory mode runs with out incident, however after resealing, the sysprep boot to mini-setup fails. The last entries in setuplog shows that 'Setup was unable to change the password for user account Administrator because of the following error: SamChangePasswordUser returned status c000006a.' This entry is just after 'BEGIN_SECTION,Computer Name Page', there is no 'END_SECTION,Computer Name Page'. The Administrator Password is blank in the XPsp2 image. I am using the latest sysprep.exe (5.2.3790.1830) from the Server 2003 SP1 Deploy CAB. I have also tried to leave the Administrator password blank (*) in the sysprep.inf. With this I get a different Critical Error - 'Setup encountered the following unhandled exception: Exception c0000005 at address 5F1A340B with the following parameters: 00000000 00000014'. Upon futher examination I find that I only get the SamChangePasswordUser error if I let the system reboot a second time or more, at which point it is not running Mini-Setup, as it failed the first time thru with the unhandled exception.

I am having the same issue. I am using the latest sysprep.exe from the W2K3sp1 Deploy cab. Did you get a resolution to this.

I am trying to deploy a XPsp2 image. The sysprep factory mode runs with out incident, however after resealing, the sysprep boot to mini-setup fails. The last entries in setuplog shows that 'Setup was unable to change the password for user account Administrator because of the following error: SamChangePasswordUser returned status c000006a.' This entry is just after 'BEGIN_SECTION,Computer Name Page', there is no 'END_SECTION,Computer Name Page'. The Administrator Password is blank in the XPsp2 image. I am using the latest sysprep.exe (5.2.3790.1830) from the Server 2003 SP1 Deploy CAB.

I was waiting for my Microsoft Premier Support Rep to supply the Server 2003 sp1 OPK, but I am impaitent. I was able to use the ramdisk.sys and setupldr.bin from Server 2003 sp1 as described above to get WinPE 2004 to boot to a ramdisk (x:). My problem is - where is my CD drive now? What is it's drive letter? Never mind. I must be getting tired. I found it at E:.

The tabctl32.ocx is the only optional component. The vb6runtime is installed. I have also tried to register the components seperately, with the same results. I guess my real question is, are VB6 programs with ActiveX controls supported in WinPE?

I have a VB6 application that I wrote that contains an ActiveX control (SSTab). I am having a problem getting it to run in the WinPE environment. The application is complaining "Failed to load control 'SSTab' from TABCTL32.OCX". TABCTL32.OCX is in the system32 directory on my WinPE CD and is the one from the VB6sp6 installation package. Other VB6 applications seem to run fine. Any help or suggestions.