Jump to content

Jadestar

Member
  • Posts

    106
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by Jadestar

  1. Here's an update. So i appended that switch to the above 8 updates mentioned in my first post. during T13, 4 windows popped up which are the "wrong switch" thing. So i figured 4 of em worked. According to add/remove programs with "show updates" 2 of them installed...so 6 didnt. The strange thing is that when automatic updates is finished downloading stuff...it shows the 2 updates that are in ad/remove programs as updates ready to be installed. KB939653 & KB938127 are the updates that are both in add/remove programs and still in windows updates. These updates below are the 6 that didnt have correct switches (4 of which said so, 2 didnt...and i dont know which is which) that didnt install. KB928365 kb936181 kb933579 kb928366 kb934238 kb932471 I'd also like to point out that in the $hf-mig$ dir in /windows, there are both the uninstallers for the 2 updates above that are in add/remove programs...ALSO..after running automatic updates and installing 127 again, a new directories appeared in hf-mig except with -ie7 on the 127 update. so now in hf-mig theres a dir called kb938127 and kb938127-ie7 and the file sizes are different. the -ie7 version is about .4mbs lower. Thanks again.
  2. As I posted already, wmp11 and ie7 work totally fine already. All the files in my svcpack update and work. Its the ones that i listed first that dont. I'll try that one you said you use for most hotfixes and see what happens. Do hotifxes need to be in any specific order? Thanks muchly.
  3. So using the svcpack method aswell as ryanvms integration and dotnet stuff I've managed to nail the computer down to only having 8 updates left. Ie7 and wmp11 work totally fine in svcpack. However, I've tried numerous switches with the following updates and they either do not install all together or a window comes up during T13 that basically says "these switches dont work, try these" and it just gives generic switches for the windows installer. Here goes. KB939653 kb928365 kb936181 kb938127 kb933579 kb928366 kb934238 kb932471 I'd like to note that I've tried type 1 and type 2 switches on these and really..im confused as to tell which is which because according to a post I read on here I believe the type2 switches have a different icon then what I assumed were type 2 hotfixes (the dotnet ones like 365 and 366) So if anyone has these ones integrated and they WORK please let me know what switches I need and where i should put em. I'll post my svcpack info below aswell. [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [setupData] CatalogSubDir="\i386\SVCPACK" [ProductCatalogsToInstall] [setupHotfixesToRun] dotnetaio.exe IE7.exe /passive /norestart wmp11.exe /Q:A /R:N kb939653.exe /q /n /z kb933729.exe /q /n /z kb941202.exe /q /n /z kb890830.exe /q /n /z kb936021.exe /q /n /z kb939683.exe /q /n /z kb933360.exe /q /n /z kb936782.exe /q /n /z kb938127.exe /q /n /z kb938828.exe /q /n /z kb921503.exe /q /n /z kb938829.exe /q /n /z kb929399.exe /q /n /z qchain.exe
  4. If you don't want a password set, you would have to use the following: NET USER xp * /ADD To have the account login automatically the first time, import the following into the Registry during installation: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="xp" "DefaultPassword"="" "AutoAdminLogon"="1" Hope this helps. Well I did find a method that works, using the OOBE method. It created the user as an administrator and autologged it in the first time..and everytime after that. I appreciate the help but i dont believe that would work since the net user whatever i did before does work just typing it in cmd while in windows so there isnt any reason i could think of that not setting a password wouldnt work...but I could be wrong. But it's solved anyways so thanks for the reply. Maybe next disc ill try that and see what happens.
  5. From what I've read using the wpl method ONLY works on a windows repair and will not work on a fresh install of xp...even on the same machine. Using it on a different machine is totally out of the question since the markers for if activiation is required will fail on everyone requiring activation since all the hardware is different aswell as the partitions.
  6. Ok so here's the deal. My unattended setup seems to work great. I have almost every winxp update integrated into it using ryanVM and some svcpack methods. The only problem i'm having is that once everything is installed, windows goes to the user select window and there are NO users there at all. This is WinXP Home. I'll post my info here in a sec. One weird thing is that on ONE and ONE ONLY computer it does create a user called Owner but on 2 others, it doesnt which I find very strange. anyways...here's my winnt.sif and other files. ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates=1 [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS UnattendSwitch=Yes [GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO AutoLogon=No OEMSkipRegional=1 TimeZone=10 OemSkipWelcome=1 AutoLogonCount=0 [userData] ProductKey= FullName="Owner" OrgName="" ComputerName=* [TapiLocation] CountryCode=107 Dialing=Tone AreaCode=403 [RegionalSettings] LanguageGroup=1 [branding] BrandIEUsingUnattended=Yes Home_Page=www.google.ca [Proxy] Proxy_Enable=0 Use_Same_Proxy=1 [identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes [Dispay] AutoConfirm=1 [WindowsFirewall] Profiles=WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode=0 cmdlines.txt [Commands] "useraccounts.cmd" useraccounts.cmd net user xp /add net localgroup Administrators xp /add and yeah...no user..i dont get it. i dont want it to have a password..autlogon would be nice but i can worry about that later. it just needs to be a regular ol administrator type user (the one user accounts lets you create in windows). I saw someones file that did the guirunonce but that requires a user to be logged in first and well...theres no user to login (other than Administrator which is not allowed in xp home under non-safe mode). So I've been pulling my hair out on this trying to figure it out. I hope someone can help and tell me what I'm doing wrong.. Thanks muchly.
×
×
  • Create New...