Aaron

That's a good idea, but I won't be using this since not everyone uses WinISO or an ISO editing utility. This does give me an idea though. I could create a page illustrating the directory layout and explain what each function does, and where the files are supposed to go in. This should hopefully clear up some confusion that some users were having. Might use Visio to create the layout then screenshot it

Webmedic might do his own guide on the 2 CD method Do you know the thread link to where this is explained in full detail? Is this a tedious task to do, or is webmedic's solution better? I'm afraid I test anything to do with Nvidia, as I don't own one of their graphics cards.

The Unattended XP CD Site is due for a big update on what we've learnt in the forums for the past 3 months or so. Today I'll be doing mostly note-taking to see what I can add/update to the site. I've lost track of what's been happening in the forums and haven't had a chance to try everything as I've been very busy. So it would be appreciated if you could post the new things you've learnt, and the link to the thread (only if they are proven to be 100% working when tested by other people) So far, I'm planning to: Create an Office 2003 Professional Unattended guide Add the UXTHEME.DL_ and SFC_OS.DL_ files (I will need more information on how SFC_OS.DL_ should be used first.) Link to b0r3d's winntbbu.dll guide thread Link to Custom XP Setup screens thread Link to webmedic's INF and MassStorageDrivers install guide (when he gets the chance to make one!) New Guide on Autologon based on webmedic's solution Hotfix section to get an overhaul based on webmedic/spheris's solution Link to Buster/Nephilim's XP-ES App, and b0r3d's Winnt.sif app And mostly all the tidbits such as removing LANG folder, more winnt.sif values such as PROFILESDIR and the other types of $$ folders which are used in the $OEM$ folders and the like (I've forgotten most of them ) Anything else I've missed out on? *Edit* Add 2 CD Installation guide Add Debugging page Add more registry tweaks (popular ones only) Add vbscripts (e.g. Quicklaunch toolbar) Add Directory Structure page Change Drivers page to use numbering (drivers\000;drivers\001 etc)

I've honestly no idea. When I started this project back in June, I used to use ProvideDefault and was baffled for days and days on why [Components] and [Display] never took effect. Changing to FullUnattended fixed everything

You can either use UnattendSwitch="no" in [unattended] so you can create a user manually and run your batch logged in as that user or, use webmedic's guides on creating a user using cmdlines.txt

If possible, see if you can tell the app to fetch the idle time value from the ini file provided, allowing the user to easily change the timeout.

Check if Print Spooler is enabled in Services Start > Run > Services.msc

Count me in as a LiteOn supporter too! Got 2 LiteOn CD-RW drives still going strong, and my Plextor and Yamaha CD-RW drives are dead

Its because you're using an ECHO command in your sysprep.exe line. ECHO is only used for making a line spacing in the Command Prompt window, or for commenting on what's currently in progress. echo start /wait %systemdrive%\oem\sysprep.exe should be start /wait %systemdrive%\oem\sysprep.exe

UnattendMode=ProvideDefault should be UnattendMode=FullUnattended [Components] and some other sections never take effect when its on ProvideDefault

Ok thanks for your help

?... But they have to be renamed though, and all on one line? I'm getting confused OemPnPDriversPath="Drivers\000;Drivers\001;Drivers\002\2KXP_INF;Drivers\002;Drivers\003;Drivers\004;Drivers\005;Drivers\006" and so on? btw, where's 005, 006 and 007 in your example?

Mine seems to be different from yours, but I'll paste it anyway as this is for MPEG movie formats too: ;Disables Preview of Movie file formats (allowing you to move/rename/delete without errors) [-HKEY_CLASSES_ROOT\.avi\ShellEx] [-HKEY_CLASSES_ROOT\.mpg\ShellEx] [-HKEY_CLASSES_ROOT\.mpe\ShellEx] [-HKEY_CLASSES_ROOT\.mpeg\ShellEx]

What I would gain from it is learning what hex value controls the digital signature. It appears it can be disabled completely in the file, and by learning that we can apply it to other files we want to replace too.

So when I use something like this: OemPnPDriversPath="Drivers\000;Drivers\001;Drivers\catalyst3_7\002" It will install the Intel drivers, followed by the gigabit lan driver, then the catalyst? Also, should Drivers\catalyst3_7\002 be Drivers\003\2KXP_INF instead?

You no that sign you got there that My IP Address. You're the only one seeing it, nobody else. I see my own IP in that sign too, its just a generated GD image.

Did it tell you what value was changed at what offset? I would like to try hex-editing vorte[x]'s hacked uxtheme.dll file to force Setup to allow this to go through.

It's not released because its undergoing beta tests to make sure there's nothing wrong.

miso's uxtheme.dll needs to be hex-compared with vorte[x]'s hacked uxtheme.dll to see the slight different. (Vorte[x] was the source of the hacked uxtheme files for XP and XP SP1)

You are right, it seems miso1391's hacked UXTHEME.DL_ was made using LZX compression at a value of 21, and the byte size matches my created UXTHEME.DL_ (using cabpack) with miso1931's. Further tests shows that compressing UXTheme.dll with Windows XP's built-in makecab utility will cause setup to halt. Also, I'm testing the modified notepad.exe with LZX compression, to see if it actually copies to three different folders rather than one (not important, but willing to see the difference ) Edit: no difference on notepad.exe whether its compressed with Windows XP's Makecab or Cabpack's LZX compression. I've noticed that miso1931's uxtheme.dll md5 sum is different to a hacked copy that I've had since SP1 came out, even though they carry the same byte size. The answer lies in that file rather than the compression used.

We will have to wait for the release notes for any information on whether this will be slipstream'able or not. The Windows 2000 SP2 Security Rollup Package has the update.exe file (which is used for slipstreaming), so its possible that the same will apply for XP SP1's Security Rollup Package

Well I was just wondering, because DriverSigningPolicy=Ignore doesn't work for some people who use drivers that aren't WHQL certified. for the ATI Control Panel, I install them via a silent installsheild installtion using an ISS file in GuiRunOnce. For the Catalysts, I wasn't aware there was "Drivers" directory seperating the main extracted files and the 2KXP_INF folder. But then I'm only looking at the extracted 3.6 drivers, 3.7's directory structure might be different, which I haven't checked yet.

I don't know why you're trying to install the Control Panel using that, the extracted files don't contain any INF files. Where did OemSigningPolicy=Ignore come from? Is this different to DriverSigningPolicy=Ignore in some way?

Here's the setuperr.log I got when I used the hacked UXTHEME.DL_ and Metapad compressed into NOTEPAD.EX_: Error: D:\i386\NOTEPAD.EX_ was not copied to C:\WINDOWS\NOTEPAD.EXE because of the following error: No signature was present in the subject. *** Error: Setup detected that the system file named [c:\windows\system32\uxtheme.dll] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. *** Still works fine though, Setup did not abort or show any screens to say one of the files failed to copy. Even if it did, it may have automatically proceeded. Notepad isn't present in the Windows or dllcache folder but its in System32.

What's special about Cabpack that allows Windows Setup to continue without error? Or did you make extra modifications to the UXTheme.dll file itself to bypass the Digital Signature?