fbrito

My unattended Windows XP SP2 always had only 1 user called "Proprietário" (and also the hidden administrator account) that sometimes logged on automatically and other times didn't (Windows boot stopped on login even with only 1 user) depending on the computer. I never bothered to understand why on some computers it logged on automatically and others didn't becauser it was not an issue for me. Now because my company started selling some computers with a motherboard with a Sata controller that had to be installed pressing F6 during the initial setup, I made a cd (with XPCREATE) with not only SP2 but also with all the patches since then and the Sata controller. It all went fine when I tested on VMware but on "real computers" at the first logon the system would stop at login screen where there were no accounts to select. I had to go into safe mode and using administrator create an account. I didn't changed nothing that would mess the user accounts. My previous user account was created because in the WINNT.SIF the "FullName=" was set "Proprietário". Since then I tried everything to solve this mystery including creating a OOBEINFO.INI file with 2 user accounts, changing the WINNT.SIF FullName string (it changes the "Registered to" in the system properties but I still get a "Proprietário" account) but a funny thing happens: in the VMware installation the system always logs on automatically using an account called "Proprietário" even if I don't have "Proprietário" in WINNT.SIF or OOBEINFO.INI. I even tried using this the following code in WINNT.SIF to log as administrator on the first boot but it had no effect whatsoever and the system logged on as "Proprietário" as always. [GUIUnattended] AutoLogon=Yes AutoLogonCount=1 My question: where is Windows XP getting the "Proprietário" name for the account since it is neither included in WINNT.SIF or OOBEINFO.INI? And by the way, why is my OOBEINFO.INI being ignored by Windows XP? (it is placed in the $OEM$\$$\System 32\OOBE folder)

I've seen some angry posts from the author of the program about this but a fact remains: lot's of people can't install the program. Instead of offending people, the Xplode author should find out why it won't install and fix it. Yes I've read the EULA, I scrolled, I clicked inside the EULA, I clicked on the hyperlinks on the EULA. Nothing works. I guess I'll try at work on a fresh OS install.