Aaron

duh. lol

That's because your MsDosInititated is spelt wrong.

Good luck then vipersnake

Add to [Data]: MsDosInitiated="0"

In formatting and backup scenarios I had in the past, I've found that restoring the MyIE2 folder back in Program Files does the job fine. Plus, you get all your favourite configs with it as well. So, place all your MyIE2 files in: C:\XPCD\$OEM$\$Progs\MyIE2 And the shortcut to it to: C:\XPCD\$OEM$\$Docs\All Users\Start Menu\Programs\MyIE2\ Your MyIE2 files will be in C:\Program Files\MyIE2\ and your shortcut will be in the start menu automatically during windows setup. Easy enough!

HMTCDWizard_enu.exe /qb (or /qn)

Brilliant, this pretty much solves everything then! I'll throw in cmdow.exe to hide the command window from the end-user when its adding all those entries (creating a cd for a friend of mine )

hmm.... interesting! So you run this from cmdlines?

This is kind of confusing RunOnceEx doesn't like any variable at all (even tried %homedrive%\install\) Doing an IF EXIST and SET command for %hdd% sets it to C:\, but only in the active command window. %hdd% won't work if run from anywhere else. Pretty much useless when the first runonceex key is set_variables.cmd (which is in system32) and the command window closes thus losing the variable. Giving me a headache this is!

I'm gonna give it ago in a sec

Have you found out yet? From what I understand, the %systemdrive% variable doesn't exist during the RunOnceEx stage, right? I've thought about making a first RunOnceEx entry to use one of those scripts that some members have used to find their CD-ROM drive letter and set the variable. I'll have to find the code, but its something like: IF EXIST C:\Install\confirm.txt SET %SYSTEMDRIVE% C:\ IF EXIST D:\Install\confirm.txt SET %SYSTEMDRIVE% D:\ IF EXIST E:\Install\confirm.txt SET %SYSTEMDRIVE% E:\ which would go into those numbered entries in the registry file: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnceEx\001] "1"="IF EXIST C:\Install\confirm.txt SET %SYSTEMDRIVE% C:\" "2"="another one" "3"="and so on" @="Finding location of files..." Just a theory though. (confirm.txt is just a blank txt file to confirm its existance in the Install folder)

No reason, its how Spheris explained it Sorry I can't offer any more help on the VIA chipset drivers as I haven't used them unattended.

That's true, I'm sure 000_VIA, and 001_Nvidia should be fine.

No, you should number your folders before the names, like: OemPnPDriversPath="Drivers\000_VIA\WinXP;Drivers\001_VIA\Inf\WinXP;Drivers\002_VIA\IDEWinXP;Drivers\003_VIA\AGP;Drivers\004_NVidia4523" Device Manager in Windows should be able to show if the VIA drivers are installed, e.g. the IDE controller

yep, looks OK to me Mind you, I haven't tested an unattended install on my AMD machine with the VIA chipset, its a dedicated win2k3 server now and doesn't need an unattended CD.

Discussion of cracking Operating Systems isn't allowed on MSFN. Thread Closed

I've no idea what HighMAT does, but have heard of it. Personally I don't use the inbuilt cd-burning feature as its somewhat limited

where?

Because it only has a fixed update.exe file - nothing is added. If your old version of 824141 installs fine on your PC, and doesn't suffer from any of the symptoms on http://support.microsoft.com/?kbid=830846 then there's no problem.

I got annoyed by that problem too. I'll explain this briefly, but will be doing a proper guide on site soon. Create a cmdlines.txt file which has: [COMMANDS] "REGEDIT /S regtweaks.reg" Save cmdlines.txt in the root of the $OEM$ folder. And put regtweaks.reg alongside it C:\XPCD\$OEM$\cmdlines.txt C:\XPCD\$OEM$\regtweaks.reg Any HKEY Current User tweaks applied from this area will get mapped as Default, so any new user you create afterwards will automatically obtain your custom HKEY Current User tweaks. Good isn't it? By the way, cmdlines.txt runs at the T-13 minutes stage of Windows XP Setup.

Yes, you only have to slipstream the newest winwordff.msp OWC10.MSI is only for slipstreaming the service pack into, all other updates should be used on proplus.msi

Yes you're right, the filesize has changed to include this fix: http://support.microsoft.com/?kbid=830846

Nothing does anyway

Best way to find out is to install Office XP with SP2, then take note of the updates listed on officeupdate.microsoft.com Or, go here: http://www.microsoft.com/office/ork/2003/a.../xp/default.htm Grab the top three updates, I believe the new Word and Excel patches supersedes the older ones in the list you pasted.

http://b0r3d.msfnhosting.com/ Make sure you have the latest version of WinRAR if you're having trouble extracting. b0r3d should be using standard zip compression to ensure cross-compatibility though...