Red Barchetta

Well, really you shouldn't be talking about "craclz" on this forum anyway (if you want to do that, go to a "Warez" forum), however, yes I can see hoe that could make thing easier regardless of what the case is. But I'll tell you - and I messed with it a lot - regardless of what modifications you do or do not use. Every time I have ever tried to get any version of WMP (except of course for the version that is on the disk by default) to install/slipstream, whatever with WinXP, at any point other than after the OS is all setup, and a user is logged in (RunOnceEx process), I have always found - yest it works to a point, but something is always wrong with it (Even the WMP10 Slipstream method - I forget what it was I didn't like about that, it's been so long, but definitely I did find some problem with it!)....

Without loosing your data, as far as I know there is nothing built in to WinXP... However, there are several partitioning tools out there that will do it without a re-format some even freeware (I think Gparted was mentioned). However, if you use one of them - I would still backup everything first anyway.. Most of the time, there is no problem using such tools, BUT on the off chance there is that one time, it could be a real disaster if you don't have backups of all your important data... But in any case, just do a search for Partition Tools and you find a bunch of them....

You don't create user accounts with WinNT.sif - that would be done either with oobeinfo.inf, or the NET command (put in to a batch command file). And with the Administrator account - if you ant that to be visible on the welcome screen I would apply a tweak to make that account visible: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList] "Administrator"=dword:00000001

Well - it seemed that the HTTP authentication hotfix, when the /integrate switch was used, caused IE6 to open while OS was still installing (at the T-13 mark) - but that's really not needed until IE7 is installed anyway, and attempting to slipstream IE7 broke the RunOnceEx process, and the Hotfixes to make it work again just seemed to integrate, but not actually work! So what I did there was install IE7 via RunOnceEx, have the system Restart, Install the Hotfixes for IE7 (including the HTTP authentication update) via RunOnce, restart again (adding more stuff to be installed via RunOnceEx). Also, forget off hand what the exact problem here was, but had problems getting WMP11 to install with the OS, and any hotfixes for it would not hold if integrated - so like with IE7, install WMP11 via RunOnceEx, have the system restart, install WMP11 hotfixes (but there, provided you do it either before installing IE7 at all, or after the IE7 hotfixes are installed, just use RunOnceEx). I had one - unfortunately I don't remember what one, that just refused to integrate, even though it had the /integrate switch available, and it did try - but kept getting "Integration failed" - that one, I ended up just placing in the svcpack folder, and manually put the command for a silent install of it in the svcpack.inf file under the section [setupHotfixesToRun] - and that worked fine (got me why it would not integrate, but worked fine like that but... I think there were a few other issues, but off the top of my head, that's all I can recall - I know I have a file for my own reference with all that in there - I'll dig it out, and let you know if I missed anything (and most likely will have the exact KB number of the "problem" hotfixes there (can't swear to it, but the way I take notes, it is most likely).

I honestly have no idea - it was just put there automatically when I used the /integrate: command-line argument to slipstream the hotfixes.

REALLY! - That is surprising! - Or wait, was it by chance a straight replacement (exact same brand and model) and use the same CPU? If not, I don't understand - but hay - don't look a gift horse in the mouth!

O.K. - don't understand why but here you go: [CatalogHeader] [Version] BuildNumber=2600 MinorVersion=1 MajorVersion=5 Signature="$WINDOWS NT$" [SetupData] CatalogSubDir="\I386\svcpack" [SetupHotfixesToRun] KB938829.exe /q /n /z /b:SP2QFE KB938828.exe /q /n /z /b:SP2GDR KB936021.exe /q /n /z /b:SP2GDR KB921503.exe /q /n /z /b:SP2GDR Prep.cmd KB920342.exe /q /n /z /b:SP2QFE KB896344.exe /q /n /z KB909520.exe /q /n /z KB925876.exe /q /n /z /b:SP2GDR KB900725.exe /q /n /z KB931836.exe /q /n /z /b:SP2GDR KB929969.exe /q /n /z /b:SP2GDR KB926436.exe /q /n /z /b:SP2GDR KB926255.exe /q /n /z /b:SP2GDR KB924270.exe /q /n /z /b:SP2GDR KB923980.exe /q /n /z /b:SP2GDR KB917734_WMP9.exe /q /n /z KB932168.exe /q /n /z /b:SP2GDR KB931261.exe /q /n /z /b:SP2GDR KB930178.exe /q /n /z /b:SP2GDR KB928843.exe /q /n /z /b:SP2GDR KB928255.exe /q /n /z /b:SP2GDR KB927802.exe /q /n /z /b:SP2GDR KB927779.exe /q /n /z /b:SP2GDR KB925902.exe /q /n /z /b:SP2GDR KB924667.exe /q /n /z /b:SP2QFE KB918118.exe /q /n /z /b:SP2GDR KB898461.exe /q /n /z KB936357.exe /q /n /z /b:SP2GDR KB935840.exe /q /n /z /b:SP2GDR KB935839.exe /q /n /z /b:SP2GDR KB933566.exe /q /n /z /b:SP2GDR KB931784.exe /q /n /z /b:SP2GDR KB930916.exe /q /n /z /b:SP2GDR KB929123.exe /q /n /z /b:SP2GDR KB927891.exe /q /n /z /b:SP2GDR KB923689.exe /q /n /z KB920213.exe /q /n /z /b:SP2GDR KB925398_WMP64.exe /q /n /z KB885835.exe /q /n /z KB917344.exe /q /n /z /b:SP2GDR KB924496.exe /q /n /z /b:SP2GDR KB885836.exe /q /n /z KB886185.exe /q /n /z KB873339.exe /q /n /z KB891781.exe /q /n /z KB887472.exe /q /n /z KB888302.exe /q /n /z KB896428.exe /q /n /z KB901214.exe /q /n /z KB890859.exe /q /n /z KB896358.exe /q /n /z KB899587.exe /q /n /z KB899591.exe /q /n /z KB893756.exe /q /n /z KB905414.exe /q /n /z KB901017.exe /q /n /z KB902400.exe /q /n /z KB905749.exe /q /n /z KB904706.exe /q /n /z /b:SP2GDR KB910437.exe /q /n /z /b:SP2GDR KB908519.exe /q /n /z /b:SP2GDR KB911564.exe /q /n /z KB911927.exe /q /n /z /b:SP2GDR KB911562.exe /q /n /z /b:SP2GDR KB908531.exe /q /n /z /b:SP2GDR KB900485.exe /q /n /z /b:SP2GDR KB917953.exe /q /n /z /b:SP2GDR KB913580.exe /q /n /z /b:SP2GDR KB918439.exe /q /n /z /b:SP2GDR KB914389.exe /q /n /z /b:SP2GDR KB911280.exe /q /n /z /b:SP2GDR KB914388.exe /q /n /z /b:SP2GDR KB920683.exe /q /n /z /b:SP2GDR KB920670.exe /q /n /z /b:SP2GDR KB920872.exe /q /n /z /b:SP2GDR KB920685.exe /q /n /z /b:SP2GDR KB919007.exe /q /n /z /b:SP2GDR KB916595.exe /q /n /z /b:SP2GDR KB922582.exe /q /n /z /b:SP2GDR KB922819.exe /q /n /z /b:SP2GDR KB924191.exe /q /n /z /b:SP2GDR KB923191.exe /q /n /z /b:SP2QFE KB923414.exe /q /n /z /b:SP2GDR KB890046.exe /q /n /z KB896423.exe /q /n /z KB893803v2.exe /q /n /z [ProductCatalogsToInstall] KB938829.cat KB938828.cat KB936021.cat KB921503.cat KB920342.cat KB896344.cat basecsp.cat KB925876.cat KB900725.cat KB931836.cat KB929969.cat KB926436.cat KB926255.cat KB924270.cat KB923980.cat KB917734.cat KB932168.cat KB931261.cat KB930178.cat KB928843.cat KB928255.cat KB927802.cat KB927779.cat KB925902.cat KB924667.cat KB918118.cat KB898461.cat KB936357.cat KB935840.cat KB935839.cat KB933566.cat KB931784.cat KB930916.cat KB929123.cat KB927891.cat KB923689.cat KB920213.cat KB925398.cat KB917344.cat KB924496.cat KB885836.cat KB886185.cat KB873339.cat KB891781.cat KB887472.cat KB888302.cat KB896428.cat KB901214.cat KB890859.cat KB896358.cat KB899587.cat KB899591.cat KB893756.cat KB905414.cat KB901017.cat KB902400.cat KB905749.cat KB904706.cat KB910437.cat KB908519.cat KB911564.cat KB911927.cat KB911562.cat KB908531.cat KB900485.cat KB917953.cat KB913580.cat KB918439.cat KB914389.cat KB911280.cat KB914388.cat KB920683.cat KB920670.cat KB920872.cat KB920685.cat KB919007.cat KB916595.cat KB922582.cat KB922819.cat KB924191.cat KB923191.cat KB923414.cat KB890046.cat KB896423.cat KB893803v2_wxp.cat Prep.cmd was manually put in there by me. I know it's not the "recommended" method - but it is how I personally do my own stuff at T-13 minutes of the OS install.

Actually that depends on what you change, and how soon. A monitor I don't think counts at all. But if you change the system board or CPU - right away you have problems because the activation server thinks it's a whole different machine (essentially it is - but if you call M$ and explain what you did, they normally reset things for you - just don't try that too often [NO ONE changes system boards/CPUs all that frequently]), CD/DVD burners seem to go quite often, so that counts, but if auto-reset after I THINK something like 6 months or there abouts. Add/Remove printers/RAM, again after a certain amount of time... (They also allow some play for user trouble-shooting - like if you THINK a burner is bad, but not 100% sure, try one from a system that is know to work, just to make sure before buying another one, exc.) In short, it's not so much the amount of hardware changes, it's more what is changed, and timing of the changes - all guesstimated somehow. But if there is a problem, MS can - and usually dose, reset things for you - as long as the explanation/timing is "reasonable".

Actually, that depends on what ones. - I did a lot of playing around with that - and found that yes a lot of HotFixes are best Slipstreamed, but a few you are better off just running latter.

Glad it all worked out for you.... But just for the future - I don't think you really need the whole disk (if you already have one) - I THINK the only files you actually need are dpcdll.dl_ and pidgen.dll

That was going to be my suggestion as well. But the newer version is most likely a better one anyway. And you don't necessarily have to spend a fortune to get a big screen monitor. I have a 24" one that I got at a Computer show for under $100 - have not had any problem with it, and have had it for about 3 years now....

I'm just don't know a lot about the [unattended] section of WinNT,sif - mainly because I don't use it. Instead I use the Presetup.cmd Patch.

Not sure, but one thing you could try instead of what you have in this section of your WinNT.sif file: [Data] AutoPartition=1 MsDosInitiated=0 UnattendedInstall=Yes (Notice no quotes) Not sure it will have any effect on coping those files but...... Wait, just Saw something that looks more like it..... [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS DriverSigningPolicy=Ignore OemPnPDriversPath="drivers01_sound;drivers02_webcam;drivers03_tv;drivers04_motherboard" KeyboardLayout="United Kingdom" Info I got on OemPreinstall: Yes = Setup copies the subfolders and files contained in the \platform\$oem$ folder. No = Setup does not copy these files Tha't all I can see maybe - anyone else?

You can not delete the actual Administrator account. You can delete other accounts the have Administrator rights, but you must be in the Administrator group in order to do that! However, as was pointed out - you can login to the actual Administrator user account by hitting Ctrl-Alt-Delete twice at the Welcome screen - that will give you a "Classic" (WinNT/Win2k) login screen - Just type Administrator for the user name, and of course the password assigned to Administrator. From that point you can Re-Create any accounts that were deleted, change passwords, change user rights, exc. And I'm curious myself - especially if he might do something like that (Either deliberately, and just not realizing what he is doing), why dose your son have Administrator rights in the first place?

Those are fine to set during the OS setup (in fact preferable since the will be applied to every user without making a big production out of it. I have the same settings in the Tweak file I import while OS is being setup - some set to different values - but that's not important. The fact is YES that should hold when done while OS setup is in progress - that's when I make those settings, and they work fine for me...

Making several .reg files one is VERY easy...Just take the one that will be where the result is stored - go all the way to the end of it, one one of the other .reg files (for editing) and copy everything except the first line, and paste it in to the result file, repeat as many times as needed. as for importing them in to the registry - the command needed is regedit /s tweakfilename.reg

O.K., I have noticed that some registry tweaks (I didn't notice if any of the ones I personally know about are in there or not) will not hold until after the OS is totally setup, because the OS install over-writes them, and you have the same situation with some applications you may install after OS setup (usually that would be tweaks having to do with that application, like registration info, start THAT application in the system try, exc.) so I personally have 3 registry hack files - the first I just call Tweak.reg, and it is imported into the registry during the OS setup process (at about T-13 Minutes), the second called Post-Tweak.reg - that gets imported to the registry at first login to the OS, and contains stuff the the OS setup process will over-write (Auto Windows Updates settings, and that type of thing usually), and the last one I call Final-tweak.reg - that is THE last this thing done before my final restart in the processes done after OS setup (I have it restarting a total of 3 times, on the last restart- EVERYTHING is installed, just making sure all changes are applied basically) - it has all the settings to 3rd party applications installed after OS setup.

Well, anyway - the WinNT.sif file is the file to use to auto answer questions asked during the actual OS install. To automate the answers on the first boot (Like User names, Register with Microsoft, exc.) use the file oobeinfo.ini (Should be copied to %SystemRoot%\System32\oobe\)

I too,would love to do that.Can you give details,on how you accomplished this?Also would you be able to add and integrate all new updates that come along later?Thanks. VAN First, just so you know what you are looking at, take a partition and install the OS as it is on the disk you already have. Copy the install disk to a folder - and extract the boot image from the disk (ISO Buster works well for that). Now go to the windows upate site, but do NOT install anything yet - click the link for the info on them, and download the local install (IT) version of the updates. NOT all of them have one, worry about that later. The majority of the updates can be added to the files you just copied to the WinXP folder with the /integrate switch from the command line (Some may not integrate, others can, but shouldn't because it messes things up {Like HTTP Authentication update} those just run via either cmdlines.txt or RunOnceEx. Updates that have no local file to download - to make it easier to tell what is what - check only one at a time, and have it install. DO NOT allow the system to restart yet! - First copy the install files somewhere, they will be in a sub-folder under %SystemRoot%\SoftwareDistribution (Usually this is C:\WINDOWS\SoftwareDistribution ) you can make your own archive with them to install (Most of the time the file to run is called UPDATE.exe in a folder called UPDATE). That's the basic idea - once you have all the updates integrated, or running somehow (at least in theory) burn the disk (I suggest on re-writable media) and test it. You need to burn a bootable disk (probably DVD) using the extracted boot image file, 4 sectors, no emulation, all ISO relaxing on, and put the files in the WinXP folder on the disk (I also added a folder called BOOT and put the boot image file in it, so you won't need to extract it again to make changes to the disk) There is a lot you can also do while you are at it - like auto answer files, add application that auto install with the OS, exc. but that is a whole different thing....

I've got LOTS of registry tweaks, AtYourService, Quick BATch file compiler, Acrobat reader, Shockwave, Firefox, Opera Browser, Bug Docter, Page File Defragmenter, AusLogics Disk Defrag, Resource Hacker, CMDOW, SENDKEY, Sun Java Run-time Environment, Properties Plus, Startup control pannel, AppScape, Folder Marker, Clean Disk Security, and ALL the "PowerToys". That's so far, I am still working on my disk.

Best solution over-all I have found to that, is just download the updates, and make your own OS install disk with all the updates integrated in to it......

I don't know if you have access to one or not. But what I have done a few times in similar cases, is install XP to a totally different hard drive - make the "Problem" drive a slave - copy any data you want to save from it - then do a clean install.. It doesn't even have to be WinXP, just any OS that will read an NTFS partition (Linux works fine too).

The only time I have had a problem with the start /wait command is if it's some sort of self-extracting archive that runs a command after extracting - in that case, it seems like it extracts the archive, then releases the process and the command issued after extracting the archive is its own independent process. Even then it depends on the type of archive. Don't recall all of them off hand - but can tell you for sure this seems to happen with self-extracting .rar archives. So what I personally do is just have self-extracting .rar archives extract to a fixed folder - but don't run any command itself after extracting - instead use the start /wait command again to actually run what you want after that archive is extracted.

The way I did it is DON'T slipstream IE7.... Instead have it copy to the hard drive during OS install - and it is installed on first OS login via RunOnceEx - restart the system and apply IE7 hotfixes via the RunOnce processes - restart again (if needed adding any other RunOnceEx processes. Works just fine......

Just the /S should work fine - however, I specify a language as well, like this: ieSpellSetup251106.exe /S /L=US