Blyster

they didnt point out that the earlier update had been superceeded, but in the description of the later update, they said that it was an update to the earlier one. Yeah, MS is always a little confusing. Blyster

kb835235 is an update for kb832333. If you have not slipstreamed any updates into the administation installation point, just leave kb832333 out. if 832333 has already been slipstreamed, 835235 should slipstream over it. If you are using the batch files provided on the unattened pages, then you will get and error while extracting them saying that a file already exists. This is due to the above packages both containing the same .msp file. Blyster

Do you not understand what i mean when i say that variables CAN'T be used in cmdlines.txt. You are still using %systemdrive%, why? It is considered a variable. This is what you might want to try [COMMANDS] "REGEDIT /S regtweaks.reg" "install_custom_programs.bat" You may need to modify your batch file depending on how you handled the paths to the setup files (relative vs. full). Also be aware that some installs actually require some services to be active or an actual user to logged in, so some of the program installs may fail trying to install them during this time. Blyster

Well, obviously you are doing something wrong because what you have is not working. The second point i made is that variables CAN'T be used in cmdlines.txt, which would describe why your batch file is not being run. You could simply call c:\install\install_custom_programs.bat instead of using %systemdrive%. Then again, if C is not your systemdrive, then this won't work. I was simply telling you why the batch file wasn't being run. There are numerous ways around using variables in cmdlines.txt, and this is just one way. Another way would be to put a .cmd file in the $OEM$ folder (with cmdlines.txt) that will call the batch file on the hard drive using the systemdrive variable. You could then call that .cmd file from cdmlines.txt instead of the batch file on the systemdrive. Just some advice - you seem to be trying to pack everything into your unattended CD all at once and are suffering from many problems. Take one thing at a time and perfect it then move on to the next so you always know what is causing your problem. Blyster

How would you expect it to install your video drivers when using Virtual PC? VPC is not emulating your exact video card. It is just emulating a standard VGA card. Are variables even aloud in cmdlines.txt? (i.e. %systemdrive%) You may need to move the .bat file to the base of the $OEM$ folder (where cmdlines.txt is) Blyster

Just download the trial version and see how the program works out for you. Nobody else can tell you if you are going to like it or if it is good for you. That's why they offer a trial download so people can test it. Blyster

Are you using the oobe disabled dll file from gosh? I think Administrator is changed in the edited file if i remember correctly. Blyster

It should be fine just the way you have it. Blyster

No, Virtual PC does not emulate SATA controllers either. Only way to test your SATA drivers is to use a real PC Blyster

Yes, just put cmdow.exe in $OEM$\$$\System32 folder like you described and it will be copied over during the text setup portion. Then add the cmdow @ /HID line at the top of the .cmd file you wish to hide and it should work no propblem. Blyster

I would assume this is just local network traffic between your computer and your brothers computer. Windows generally has several processes running in order to accomodate RPC's, etc... that just sit and listen (and also broadcast that they are there waiting). I don't think you have anythign to worry about. Although you could probably cut down on this meaningless chatter by disabling any uneeded services. Blyster

I am confused on what you are asking. winnt.sif is processed as soon as text setup starts. No command window is open when this happens. Be more specific as to what you are trying to accomplish. Blyster

I would try using the F6 method on an unmodified windows CD without the use of the IDE drive. The problem you are having seems to be that the real-mode driver is not being loaded properly(the one you integrated into the CD - May not have been integrated properly). Try this and see if it alleviates your problems. Blyster

Are you loading the SATA controller drivers using the F6 method at the beginning of the setup portion? As long as Windows has real-mode drivers and the BIOS supports booting off of the SATA controller you should have no problems. I have never had to have a standard IDE hooked up in orded to install Windows onto a SATA or RAID controller drive(s). Blyster

No problems with remote desktop here after using XPCreate to integrate all the hotfixes etc.. into my install. Did you by chance do any reducing of the source CD that may have gotten rid of important system files? Blyster

It almost sounds like something else got corrputed in the txtsetup.sif file. You could try grabbing a new txtsetup.sif file off the original cd and see if that works. When is the error happening? As soon as it boots off the cd and gets to the blue text setup screen? Blyster

Look at it more closely. I had to change one of the headings(the hardwareid heading for the si3112). Also, the way you had the id's formatted was wrong(you had id = "...","..."). It was only a few minimal changes, but when setup it looking for a certain format, only that format will do. I really dont think changing the 3 to a 4 is a big deal as they both point to the same directory if i'm not mistaken. It was done more for consistency. Search the forums for txtsetup explained. I think it was Gosh who described the sequence of numbers very well. Good Luck Blyster

This is easy enough to fix. What you have added to the txtsetup.txt file is not correct. It should be like this: [SourceDisksFiles] si3112.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1095&DEV_3112&SUBSYS_31121095 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_34238086 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_311215D9 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_B0021458 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_01661028 = "Si3112" PCI\VEN_1095&DEV_3112&SUBSYS_82141033 = "Si3112" PCI\VEN_1095&DEV_3512&SUBSYS_35121095 = "Si3112" PCI\VEN_1095&DEV_3512&SUBSYS_01661028 = "Si3112" [SCSI.load] si3112 = si3112.sys,4 [SCSI] si3112 = "Silicon Image SiI 3112 SATALink Controller" [SourceDisksFiles] hpt3xx.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1103&DEV_0005 = "hpt3xx" PCI\VEN_1103&DEV_0004 = "hpt3xx" PCI\VEN_1103&DEV_0006 = "hpt3xx" [SCSI.load] hpt3xx = hpt3xx.sys,4 [SCSI] hpt3xx = "HighPoint HPT3xx ATA RAID Controller (WinXP)" Hope this helps. Also remeber to copy both the hpt3xx.sys and the si3112.sys file to the i386 directory before burrning the cd. Lastly, include to the path to the GUI drivers that should be place in the $OEM$\$1 structure. Blyster

That is one of the old pages for the unattended site. It has been reformatted and moved. Try this link here : http://unattended.msfn.org/xp/installhotfixes.htm Blyster

@daywalker I could have sworn i saw Movie Maker 2 listed on the windows update after a fresh install of xpsp2. I may have just been seeing things though, no biggie. @AirMaleDWF Out of all the things that it could have been, i had misnamed svcpack.inf. Pretty stupid thing to do, but after looking at things so long, you tend to overlook the obvious Blyster

It looks like its not even finding the xource cd. Maybe the ini file is pointing to the worng place alltogether. In his screenshot and the posted log file, the copy cd section lasts 2 seconds. I really wish my cd would copy that fast(hehe). i think you are correct about modifying the xpcreate.ini file AirMaleDWF, but not necesarily to the hard drive. Blyster

xpcreate will add sp2,.NET framework,movie maker 2, journal viewer,Highmat CD Support, Baseline security analyser just fine. The methods used to slipstream sp2 into the installation point didnt change since sp1 so xpcreate handles it just fine. Nothing has changed Blyster

Not sure if this is possible since they are both part of the oobe(Out of Box Experience). Using UnattendedSwitch="Yes" disables to whole process. The only solution i can think is put winnt.sif on a floppy and in cmdlines.txt on the cd make it call "a:\cmdlines.cmd". This way, any users can be added in the cmdlines.cmd on the floppy using net user. This way, you could leave UnattendedSwitch="Yes" on the winnt.sif on the floppy and have it skip oobe(the internet and user setup) while adding users through the cmdlines.cmd on the floppy as well. Blyster

If you wouldn't mind posting a link to the drivers you are using, i could make sure what you are adding to txtsetup.sif is correct. Basically it is 3 steps: 1) correctly modify txtsetup.sif 2) copy the driver to the i386 folder 3) put the correct path to the GUI drivers in winnt.sif Blyster

I know the symptoms you are describing are related to a worm going around. My work got hit by this yesterday. Can't remember what it's called, but rename regedit.exe to regedit.com and run regedit.com. Navigate to the HKLM\...\Run(can't remeber whole key) and look for and remove the suspicious app running from the system32 folder. Thats about all i can remember reading about it. If i get more complete data, i'll post it here. Blyster