DisabledTrucker

I have a question that I don't quite think has been asked/answered here, what is the determining factor for using WinNT.sif, WinNT32.sif, and Unattended.txt? I understand that were supposed to use WinNT.sif from a CD, but why can't one just use Unattended.txt instead? What would one need to do differently to be able to use the WinNT32.sif or Unattended.txt file from a CD or is this even possible? Pro's and Con's of using each technique would be a plus. There being several different ways of doing an unattended install being discussed here, it would be nice if someone could better explain somewhere or point me to where it's already explained in what to look for for the differences between the different installations. I ask this because I am having problems with my unattended disk and I believe that it has to be something that I am doing that can only be done while doing it a certain way. The ref.chm doesn't seem to be of much help on this, because what I am asking seems to be beyond the scope of what is included in that guide. Yes, it tells some of the differences between Unattended and Sysprep, what I am looking for is the difference in using the different forms of Unattended.txt and what the pro's and con's are between using these different ways. Also, on somewhat related question, what would happen if I used winnt.sif: [Data] ... MsDosInitiated="1" ... Instead of winnt.sif: [Data] ... MsDosInitiated="0" ...on my UXPCD? ~Lost on cloud UXPCD9~

Wow, only been out two whole days and already 5 pages of replies, great work there Ryan, keep it up. Noticed you have released the newer version already will try it out next week.

I've tried using Bâshrat the Sneaky's driver packs, the problem lies in the the included Realtek drivers that are included with it, (so I don't use them because they are incompatible with my system,) as well as his instructions I have tried, only to recieve an error that it's either looking for some line 1787 in txtsetup.oem, or it will give an error that the drives cannot be found, either way it's not working. So I give up on that as well. I have tried it all kinds of different ways and still am not able to get the drivers to work. From what I have read there are basically 4 different methods, I have tried them all and all variations of those directions and still cannot get them to work. Well the one where you run the installer and grab the two files and incorporate them then put the drivers in three different places, modifing the txtsetup.oem files for each place differently, but I need the entire cd, not just what is copied over, so I haven't tried that way. Nothing seems to be working correctly, not sure if I am having syntax errors, or what. Yes, I use drivers for another motherboard, but the ones for my motherboard are the same drivers, just the one I use are newer versions and are better. As far as using nLite, I attempted using it but unfortunately I couldn't get it to work correctly, so I gave up, besides I wanted to be able to do this by hand so I know what everything is and where it's putting it, so I can make customizations if needed, either now or in the future. I should probably mention both my system's spec's as well as the fact that I am trying to use XP Pro SP-2 to do this on. System contains:[code]Chaintech 7NJS Zenith motherboard (P.O.S. I know but I still use it none the less, waiting till next year to upgrade to 64-bit.) XP 2100+ (both o/c'd to 2600+ and non-o/c'd) 1GB PC 3200 Kingston HyperX 512MBx2 matched, running at 5-2-2-2-1@1.7v (min volts on 7NJS, wont go lower.) also tried 512MB of PC 2700 Crucial retail memory, using std settings. (Original purchased memory that Crucial reports works with the board, el-cheapo version, but otherwise good memory, only replaced to be able to o/c the 2100+, also running at 1.7volts, 5-2-2-2-1 settings.) Doesn't seem to be memory related. 2-Hitachi Deskstar 7K250 120GB Sata drives in raid 0, using SATA power cables. (No problems reported by any utilities provided by Hitachi, tried even just one drive at a time, but they are normally used as a raid 0. In fact they were still working just fine prior to reinstalling, where I attempted to do this upgrade. They are accessble just fine when not using the unattended, but F-6 way of installing the drivers.) Plextor 708-A/SW-BL, (even used old HP branded DVD Rom and CD-RW to install but they gave up the ghost, so replaced them with the trusty Plexy, which works on both systems the one I am on now is different in it's using an Asus A7N266-VM/AA with a XP 1700+ no o/c's with 512 MB of Crucial PC 2700 memory, (yes I have two matched sticks of this memory as well.) I replaced the Plexy in this one which is used in the other one now with a Optorite DD-0405 and WD1000JB and 1600JB hdds Also only uses on-board audio/video, no cards, lan is reached via Linksys WUSB-11. Power provided by PC P&C TC-510-ATX. Case is old HP Pavilion xt963. Yes it all fits but it's tight, cooling is standard air cooling provided by AMD and HP.) Creative Audigy 2 Platinum ATI AIW 9000 Pro Linksys WMP-11 for networking Antec TruePower 550. Case is Lian-Li PC-82COM Cooling via 5 Lian-Li fans and a CoolerMaster Aero 7+[/code] I should also mention this: [url="http://support.microsoft.com/default.aspx?scid=kb;en-us;816299"]HOW TO: Create an Unattended Installation of Third-Party Mass Storage Drivers in Windows Server 2003[/url] (*NOTE*- *From above HOW TO* - This procedure cannot be used in conjunction with a Winnt.sif file when starting up from a CD for installation, should be kept in mind when reading, and could also apply to XP w-w/o SP-1 or 2, though I'm not sure, becuase the 2K one, (mentioned in the article,) is what is said to work in both 2K and XP, but there is not a specific entry for XP and there is no reference in the 2K article that mentions this note, neither of them mention XP.) If anyone can find XP specific instructions please report back, as I have searched the M$ website and cannot find it.

I've considered using this method: [url="http://www.msfn.org/board/index.php?showtopic=10877&hl=Pure+Chrome"]XP Basic CD Unattended SATA/RAID Install , How to avoid hitting F6 for CD Install. [/url], but I don't particualarly want it set up this way as I need for the entire CD to be there for other computers I may use this on. All I want is to be able to slipstream the mass storage drivers and have them work when installing to my other system. I have even tried using that method and sort of integrating it into the regular UXPCD that I am trying to make, but that doesn't work either. I am about to give up on getting these things to work correctly, and just hope that my floppy drives will hold up until M$ gets off their a$$es and does away with the floppy drive altogether for installations, and fixes their unattended files.

Ok, as I have mentioned in other threads, I have a Chaintech 7NJS Zenith, which will also use the MSI drivers, much the same as other boards, the MSI ones are just better. I have done all kinds of different ways of doing these drivers, (including but not limited to putting the driver entries into the Txtsetup.sif file, which is what I am trying to avoid here, even it does not work that way.) Now from what I have gathered from reading M$ own documents, you have to put your files in a couple places: [code]$OEM$\Textmode\ (copy all files here from driver folder, remove them from any WinXP folder, but not subfolders within the WinXP folder, you will need those in your textmode folder, (replace folder name for your O/S.)) ie: $OEM$\Textmode\raidtool is fine but $OEM$\Textmode\WinXP\raidtool isn't. $OEM$\Inf (copy *.inf files here) $OEM$\$$\System32\ (copy any other files here not listed elsewhere from Textmode folder, such as *.exe, *.nvu, etc.) $OEM$\$$\System32\dllcache (make hidden and copy *.dll files in here) $OEM$\$$\System32\Drivers (copy *.sys files here) Remove any *.txt files as they shouldn't be needed especially readme's.[/code] Now make sure you dont include any internal folders from your driver set. For example if your download includes a WinXP folder pull out the files from that folder and put them all into your Textmode folder, your going to edit your Txtsetup.oem file to make it work correctly. If you have a Disk1 file without an extension, or a disk1.tag file, or something to that sort, make sure it's in the Textmode folder. Now place your Txtsetup.oem file there as well, then open it cause you need to make sure it reads similar to:[code];textsetup.oem [Disks] ;includes settings for NVRaid, NVATA, as well as Promise Fasttrak 376 from MSI. ;For NTFS use (WinNT32.sif):    d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\Textmode\ ;For Fat use (WinNT.sif):    d2 = "NVIDIA RAID DRIVER (SCSI)",\disk1,.\Textmode\    d3 = "Promise FastTrak 376/378 Driver Diskette",\fasttx2k,\Textmode\    d4 = "Promise FastTrak 376/378 Driver Diskette",\fasttx2k,.\Textmode\    d5 = "Promise SATA378 Driver Diskette", \ulsata,\Textmode\    d6 = "Promise SATA378 Driver Diskette", \ulsata,.\Textmode\ [Defaults]    scsi = RAIDCLASS    scsi = FastTrak_TX2K_xp [scsi]     RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)"     BUSDRV = "NVIDIA NForce Storage Controller (required)"     UlSata_xp   = "WinXP Promise SATA378 (tm) Controller", UlSata     FastTrak_TX2K_xp   = "WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k [Files.scsi.RAIDCLASS]     driver  = d1,nvraid.sys,RAIDCLASS     inf     = d1,nvraid.inf     dll     = d1,nvraidco.dll     catalog = d1,nvraid.cat     driver  = d2,nvraid.sys,RAIDCLASS     inf     = d2,nvraid.inf     dll     = d2,nvraidco.dll     catalog = d2,nvraid.cat [Files.scsi.BUSDRV]     driver = d1,nvatabus.sys,BUSDRV     inf    = d1, nvatabus.inf     dll    = d1,idecoi.dll     catalog = d1, nvata.cat     driver = d2,nvatabus.sys,BUSDRV     inf    = d2, nvatabus.inf     dll    = d2,idecoi.dll     catalog = d2, nvata.cat [Files.scsi.FastTrak_TX2K_xp]     driver = d3, fasttx2k.sys, fasttx2k     dll    = d3, ptipbmf.dll     inf    = d3, fasttx2k.inf     catalog= d3, fasttx2k.cat     driver = d4, fasttx2k.sys, fasttx2k     dll    = d4, ptipbmf.dll     inf    = d4, fasttx2k.inf     catalog= d4, fasttx2k.cat [Files.scsi.UlSata_xp]     driver = d5, UlSata.sys, UlSata     dll    = d5, ptipbm.dll     inf    = d5, UlSata.inf     catalog= d5, UlSata.cat     driver = d6, UlSata.sys, UlSata     dll    = d6, ptipbm.dll     inf    = d6, UlSata.inf     catalog= d6, UlSata.cat [Config.RAIDCLASS] [Config.BUSDRV] [Config.UlSata]    value = "", Tag, REG_DWORD, 1 [Config.fasttx2k]    value = "", Tag, REG_DWORD, 1 [HardwareIds.scsi.RAIDCLASS]    id = "GenNvRaidDisk","nvraid"    id = "*_NVRAIDBUS","nvraid" [HardwareIds.scsi.BUSDRV]    id = "PCI\VEN_10DE&DEV_008E", "nvatabus"    id = "PCI\VEN_10DE&DEV_0085", "nvatabus"    id = "PCI\VEN_10DE&DEV_00D5", "nvatabus"    id = "PCI\VEN_10DE&DEV_00EE", "nvatabus"    id = "PCI\VEN_10DE&DEV_00E3", "nvatabus"    id = "PCI\VEN_10DE&DEV_00E5", "nvatabus"    id = "PCI\VEN_10DE&DEV_0035", "nvatabus"    id = "PCI\VEN_10DE&DEV_0036", "nvatabus"    id = "PCI\VEN_10DE&DEV_003E", "nvatabus"    id = "PCI\VEN_10DE&DEV_0053", "nvatabus"    id = "PCI\VEN_10DE&DEV_0054", "nvatabus"    id = "PCI\VEN_10DE&DEV_0055", "nvatabus" [HardwareIds.scsi.FastTrak_TX2K_xp]    id="PCI\VEN_105A&DEV_3376", "fasttx2k"    id="PCI\VEN_105A&DEV_3373", "fasttx2k" [HardwareIds.scsi.UlSata_xp]    id = "PCI\VEN_105A&DEV_3373","UlSata"[/code]Now make sure in your WinNT.sif file you have:[code];SetupMgrTag [Data]    AutoPartition=No    MsDosInitiated="0"    UnattendedInstall="Yes" [Unattended]    DriverSigningPolicy=Ignore    NonDriverSigningPolicy=Ignore    DUStopOnError=Yes    Filesystem=*    ForceHALDetection=Yes    KeyboardLayout=US    OverwriteOemFilesOnUpgrade=No    OemFilesPath=".\$OEM$\"    OemPnPDriversPath="PNPDriver";"PNPDriver\AudioDrv";"PNPDriver\AudioUtl";"PNPDriver\Display";"PNPDriver\Ethernet";"PNPDriver\GART";"PNPDriver\MemCtl";"PNPDriver\Modem";"PNPDriver\Mouse";"PNPDriver\Printer";"PNPDriver\SMBus";"PNPDriver\UPS";"PNPDriver\Video" ;Only need OemPnPDriversPath, if you have PNP Drivers set up to install, if you want to have the stuff you copy to the hard drive using the $OEM$ folder, you can place that in i386 and make the above path: ".\i386\$OEM$\" without the quotes, and when the O/S is done installing it's supposed to remove the folders for you, though not even that way worked when trying to install these drivers.    OemSkipEula=Yes    OemPreinstall=Yes    OEMSkipWelcome=1    TargetPath=\WINDOWS    Unattendmode=ProvideDefault ;In case later I need to change settings for different computer, can be several different settings, FullyUnattended is most used in forum, others are DefaultHide (default setting), GuiAttended, and ReadOnly.    UnattendSwitch=Yes    WaitForReboot=No ...Only Neccessary lines listed here... [MassStorageDrivers]    "NVIDIA RAID CLASS DRIVER (required)"=OEM    "NVIDIA NForce Storage Controller (required)"=OEM    "WinXP   Promise SATA378 (tm) Controller"=OEM    "WinXP   Promise FastTrak 376/378 (tm) Controller"=OEM    "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"=RETAIL [OEMBootFiles]    txtsetup.oem    nvraid.sys    nvraidco.dll    NvAtaBus.sys    idecoi.dll    ulsata.sys    ptipbm.dll    fasttx2k.sys    ptipbmf.dll    nvraid.inf    nvatabus.inf    ULSata.inf    Fasttx2k.inf    nvata.cat    nvraid.cat    fasttx2k.cat    ulsata.cat[/code] I have also figured out that you need to set up all your drivers, other files, and anything else your adding to your UXPCD prior to doing your WinNT.sif file from SetupManager, this will give you all the $Restore$ files you will need to make and in them it will automatically rename all the files and paths that you will need to go back and rename so they will be recognized on the CD. Once you have opened each of those files and noted what names in the folder they are in need changing and change those names, you are ready to burn your CD, if you do not do this step, Windows XP will miss a lot of the files, or your CD writer program will attempt to rename them incorrectly, prior to burning the files. (Roxio version 6 was severly bad about doing this, even with a regular WinXP disk, after you already clicked the "Burn" button, and if you cancelled it wouldn't let you burn the disk. If you didn't change the names and add the $Restore$ file with the names inserted in them in the proper folders, XP wouldn't find them later!) Now according to M$'s obscure instructions on this, under Windows XP, it should work, but to this point I keep getting that dreaded error 18 in line 1747 error, which is driving me up the friggen wall... I should also mention that I have tested these drivers and they work perfectly when using them through F-6, although the only one which loads is the Fasttrak at this point. The NForce, I have never tried to do prior to loading the operating system before, but the fasttrak should be the one which takes as it's necessary for the SATA drives to be recognized with my motherboard. Alas, to my dismay, none of these drivers either take nor will work when trying to do this through unattended. Yes, I have tried every way mentioned so far in these threads, but I still haven't gotten them to work.

I did find this while looking over the OEM Microsoft Windows Preinstallation Reference, not sure how much help it will be in future attempts, but here's what it says: ****NOTE THE IMPORTANT SECTION**** [OEMBootFiles] Answer File = Unattend.txt The [OEMBootFiles] section contains entries for specifying OEM-supplied boot files. This entry is valid only if you set OemPreinstall to Yes and you place the files listed here in the \$OEM$\Textmode folder of the OEM’s distribution share point. This section is required if you use the ComputerType entry in either the [Unattended] or [MassStorageDrivers] sections of Unattend.txt. Important Add driver entries only to the [MassStorageDrivers] and [OEMBootFiles] sections for bootable mass-storage devices. Do not include secondary mass-storage devices. Instead, add the drivers for secondary mass-storage devices to the folder specified by the OemPnPDriversPath entry in your unattended Setup answer file. Including drivers for non-bootable mass-storage devices in the [MassStorageDrivers] or [OEMBootFiles] sections causes an error during Setup. HAL_file_name Maps to a hardware abstraction layer (HAL) description in the ComputerType entry of the [Unattended] section of the Unattend.txt file. SCSI_driver_file_name Maps to a mass-storage device driver description defined in the [MassStorageDrivers] section of the Unattend.txt file. You can list multiple instances of SCSI_driver_file_name in the [OEMBootFiles] section. TxtSetup.oem This file contains descriptions of all the OEM-supplied drivers listed in this section and includes instructions on how to install them. This file must exist if the Unattend.txt file contains an [OEMBootFiles] section. If your mass-storage device is a Plug and Play device, verify that a Hardware Identification section and a reference to the catalog file for the driver (<Driver>.cat) exist in the Txtsetup.oem file. If the Hardware Identification section does not exist, you must add [HardwareIds.scsi.yyyyy] to the Txtsetup.oem file and verify that the following information is included: id = xxxxx, yyyyy where xxxxx represents the device ID, and yyyyy represents the service associated with the device. For more information about Txtsetup.oem, see the Microsoft Driver Development Kit (DDK), which you can order from the Microsoft DDK Web site (http://www.microsoft.com/ddk/). You can also read the DDK documentation in the MSDN Library (http://msdn.microsoft.com/library/): Select Windows Development, then Driver Development Kit.

I would like to mention first to grab this, it will help tremendously:Add Mass Storage Drivers Then read: How to Add OEM Plug and Play Drivers to Windows Installations, Adding Third-Party or Updated Driver During Windows Setup, Error Message: Illegal or Missing File Types Specified in Section Files.SCSI.Name, How To Unattended Installation of Third Party Mass Storage Drivers in Windows NT and Windows 2000, HOW TO: Create an Unattended Installation of Third-Party Mass Storage Drivers in Windows Server 2003 (*NOTE*- *From above HOW TO* - This procedure cannot be used in conjunction with a Winnt.sif file when starting up from a CD for installation, should be kept in mind when reading, and could also apply to XP w-w/o SP-1 or 2, though I'm not sure, becuase previous one is what is said to work in both 2K and XP, but there is not a specific entry for XP and there is no reference in that article that mentions this note. ). Also of good read, though some may not still work in 2K, XP, or 2K3: HOWTO: Unattended Setup Parameters for Unattend.txt File HTH in working out the problems with unattended installations of SATA-SCSI drivers. For those who have problems with the NVraid, please read this: nvraid.pdf from ABIT-USA

Add Mass Storage Drivers to a Windows XP Configuration Set SUMMARY This article describes the ScsiCfgSet.exe file that contains the required directory structure, driver files (placeholders), and configuration file modifications that you must have to preinstall third party mass storage drivers by means of the Microsoft Windows OPK tools. The ScsiCfgSet.exe self-extracting executable file is a subset of a Microsoft Windows XP Configuration Set. The information that is described in this article is a sample and cannot be used directly as a Configuration Set. Use this information as a guide to create or to modify an existing Configuration Set or a new Configuration Set. The ScsiCfgSet.exe file runs on x86 platforms. MORE INFORMATION The following file is available for download from the Microsoft Download Center: Download ScsiCfgSet.exe now

NVraid doesn't work on all motherboards, unless you have a NForce3, (then it's up to the manufacturer,) it's more than likely not going to work as it's part of that driver set. NForce3 currently is only available to 64-bit mobo's. I do know for a fact it doesn't work on my Chaintech 7NJS Zenith Mobo nor does it work on my Asus A7N266-VM/AA HTH. @Bâshrat the Sneaky :

His may not be, but mine is. I don't know if the PowerNow! is working or not, because I don't have a laptop nor do I use mobile processors. I do know that programs report it as working though.

I like and use WMP9, but I don't like and wont use WMP10, if they continue down the DRM integration path, I will start using another format altogether and rip WMP from my system!!!

I understand your busy and all, but are you still going to do the WLAN one or no?

Thanks for clarifying it for me prathapml.

I would like to pick up some vb in the future, but until I can get past this seizure problem I am having, I have enough trouble just doing what I can. Thanks for the last post though, if I can figure out how to implement it, I may. @eNuffSaid That's why I just install the entire thing then remove what I don't want later, it's too much hassle trying to figure out what the key is.

For the problem your having with the text, you may want to try an x/y variable and use the -1 or whatever it would be, or subtract that number from the variable, I believe that's what may be required.

That works for me sort of, I don't use C:\\, I use %%systemroot%% instead and it comes out like: [HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Desktop\General] "BackupWallpaper"="%%SystemDrive%%\\windows\\web\\wallpaper\\RoyalBliss.jpg" "Wallpaper"="%%SystemDrive%%\\windows\\web\\wallpaper\\RoyalBliss.jpg" And yes, jpegs work for me, I don't have to convert them to bit maps. This tweak is for all desktops, if you want to make it for only one user, use HKCU instead. @Kishiro It would be best if you made a .REG file and attached it to the board than post the long code.

Thanks, but I tried that just before you mentioned it and now I get another error about txtmode.oem in some obscure line which doesn't exist, 1747 or something to that effect. That error will pop up about 5-6 times before it goes away, (by hitting my "any" key,) and then when I get to the point that Windows XP is supposed to find my drives, it wont find them. I do have two different txtsetup.oem's but they are in two different folders one for the Nvidia raid controller and one for the Promise 376 driver, neither are working correctly. I should mention too, that I'm installing from i386\$OEM$\txtmode which is supposed to be where xp automatically looks for the drivers.

I do txtmode from cd, using the structure: i386\$OEM$\txtmode My problem has been lately that my entries in WinNT.sif aren't working correctly. This is what I have in there: [MassStorageDrivers];219 "WinXP Promise FastTrak 376/378 (tm) Controller","fasttx2k"="OEM" "WinXP Promise SATA378 (tm) Controller","UlSata"="OEM" "NVIDIA RAID CLASS DRIVER","nvraid"="OEM" "NVIDIA NForce Storage Controller","nvatabus"="OEM" "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"="OEM" The ";219" is the line number, I keep getting an error which says there is an error in WinNT.sif on line 220, but this is what I was told would work, so far I haven't had any luck with this. What I have tried so far: With and with out ", fasttx2k", with and without the enclosed quotes, with and without "="OEM"", with and without the enclosed quotes, nothing seems to be working correctly. I can't find my original WinNT.sif where it worked under SP-1, but this isn't working in SP-2 at all. I should also mention that I have never had a problem before using this method of installing from txtmode until now, as I mentioned I have used this method in the past. I do know that this: "WinXP Promise FastTrak 376/378 Controller" has to be like this but the rest I am still unsure of.

Only thing I can find on user account pics is this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Hints] @="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Hints\User1] @="" "PictureSource"="C:\\Documents and Settings\\All Users\\Application Data\\Microsoft\\User Account Pictures\\Default Pictures\\palm tree.bmp" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Hints\User2] @="" "PictureSource"="C:\\Documents and Settings\\All Users\\Application Data\\Microsoft\\User Account Pictures\\Default Pictures\\astronaut.bmp" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Hints\User3] @="" "PictureSource"="C:\\Documents and Settings\\All Users\\Application Data\\Microsoft\\User Account Pictures\\Default Pictures\\skater.bmp" It may not be a registry entry, some of the themes will remove the user account pic, which is where I think it's at, in shell32.dll the information for placing the pic itself. HTH

What I did when I was running XP-SP1 was install it after everything else was installed, through Device Manager, just open the properties up for the processor and install it from the download from M$, then when you reboot it will work just fine. With XP-SP-2 this patch is already included in it, so you don't have to do anything, just slipstream SP-2 over your FPP of XP-SP1 and it will work out ok, you don't have to do anything. I have both an original XP-2002 disk as well as a XP-SP1 disk from M$ (Boxed version,) and both slipstream just fine to SP-2, it's when you take an original XP disk and slipstream it to SP-1 then slipstream it again to SP-2 that there are problems with it. The SP-2 disk I installed this system on was from the SP-1 pre-integrated CD and I haven't had any problems as of yet with the system. It even used the correct AMD driver for the processor, I would have to mention when I set this system up, I used a UXPCD with all my drivers integrated, so everything was ready when I booted. When I did it with the SP-1 slipstream in the past, I integrated the AMD patch into the installation, by putting the drivers in the $OEM$\$\Drivers and just made a call to it in the WinNT.sif file, it worked just fine to install it that way, as Windows XP when installing will look there for it while installing drivers. You need to make sure you have the proper entries in the WinNT.sif to make sure it's looking for the drivers: [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore DUStopOnError=Yes Filesystem=* OverwriteOemFilesOnUpgrade=No OemFilesPath="Drivers\AMD";this is an example I put them in i386\$OEM$\$1\Drivers so my path is .\$OEM$ which takes care of all of them, I don't need to specify each specific driver folder. OemSkipEula=Yes OemPreinstall=Yes Unattendmode=ProvideDefault;can say "unattended" for full unattend. UnattendSwitch=YesHTH. Unless your using a Mobile XP processor you shouldn't notice any slow downs in speeds, if you do just turn off the feature through the power options control panel.

No thats how many programs you allow on your list in the startmenu. RT click start select Properties Customize Number of programs ---> Yours is 4 by that line I do want to make a note, that more of you are using ones for just the HKCU, if you look in your registry you may find it in HKLM as well, if your wanting that to be a default setting for all users use the HKLM setting instead as it has presidence over the HKCU. If not, it's trial and error as to what will work and what wont for default values in HKLM that works also in HKCU, though most will. *EDIT* See attached CustomShellMenu.reg for the correct entries in the regirstry for these settings, note also I took out the ones for the cascade as there is a setting in that line which allows for it, but the ones which were being called were not the correct ones for XP w/SP2. Start_AutoCascade=dword:00000000 is the setting for the Start Menu cascading, the rest are done with # switches like for MyDocs would be dword:00000002 (2) instead of dword:00000001 (1) CustomShellSettings.REG

For those of you trying to figure out what is going on in the start menu, here is what my start menu looks like: September Desktops. And the attached file is my registry entries to match it. Granted you wont get the color scheme with that file but it will give you an idea of what it will look like. I erased my name from the top of the menu for the pic, so no that's not a tweak. Now for the reason that I actually replied to begin with, in the following code, there are "YES"/"NO" statements which are totally incorrect, they have to be changed to dword:00000001/00000000 respectively. ;----- ;----- Custom Shell Settings ;----- *******Previous entries in this line are correct******* [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "ShowCompColor"=dword:00000001 "DontPrettyPath"=dword:00000000 "ShowInfoTip"=dword:00000001 "HideIcons"=dword:00000000 "MapNetDrvBtn"=dword:00000001 "WebView"=dword:00000000 "Filter"=dword:00000000 "SeparateProcess"=dword:00000001 "StartMenuInit"=dword:00000002 "ListviewAlphaSelect"=dword:00000000 "ListviewShadow"=dword:00000000 "ListviewWatermark"=dword:00000000 "TaskbarAnimations"=dword:00000000 "StartButtonBalloonTip"=dword:00000002 "StartMenuAdminTools"="YES" "StartMenuFavorites"=dword:00000001 "StartMenuRun"=dword:00000001 "StartMenuChange"=dword:00000001 "CascadeControlPanel"="YES" ;----- Enable Cascading My Documents "CascadeMyDocuments"="YES" "CascadeNetworkConnections"="YES" "CascadePrinters"="NO" "StartMenuScrollPrograms"="NO" "IntelliMenus"=dword:00000000 "TaskbarSizeMove"=dword:00000001 "TaskbarGlomming"=dword:00000000 ;----- don't auto search for LAN folders/printers "NoNetCrawling"=dword:00000001 "FolderContentsInfoTip"=dword:00000001 "FriendlyTree"=dword:00000000 ;----- Show file extensions "HideFileExt"=dword:00000000 ;----- display system folder contents "WebViewBarricade"=dword:00000001 ;----- Disable thumbnail caching "DisableThumbnailCache"=dword:00000001 ;----- Show hidden files/objects "Hidden"=dword:00000001 ;----- Show protected OS files "ShowSuperHidden"=dword:00000001 "ClassicViewState"=dword:00000000 "PersistBrowsers"=dword:00000000 "ServerAdminUI"=dword:00000000 "EnableBalloonTips"=dword:00000001 "Start_ShowNetPlaces_ShouldShow"=dword:00000041 "Start_MinMFU"=dword:00000004 ;----- Show Control Panel as cascaded menu "Start_ShowControlPanel"=dword:00000002 "StartMenuFavorites"=dword:00000000 "Start_ShowHelp"=dword:00000001 "Start_ShowMyDocs"=dword:00000002 "Start_ShowMyMusic"=dword:00000000 "Start_ShowMyPics"=dword:00000000 "Start_ShowPrinters"=dword:00000000 "Start_ShowSetProgramAccessAndDefaults"=dword:00000000 "Start_ShowRecentDocs"=dword:00000002 ;----- Disable higlighting of new applications in start menu "Start_NotifyNewApps"=dword:00000000 ;----- Administrative Tools in your Start Menu "Start_AdminToolsRoot"=dword:00000000 ;----- Startmenu 1 = Large / 0 = Small Icons "Start_LargeMFUIcons"=dword:00000001 HTH. @shaokahn dont add that key at all it's not normally in the registry, could be your problem. @sleepnmojo That entry has worked just fine with my ATI AIW for the last couple years since XP was first released. @Diabolical82 Not sure what Webview is mines always been set to 1 FriendlyTree has always been set to 1 on my machine CascadeControlPanel should be in form of 00000000(1) if its a real tweak CascadeMyDocuments same as above CascadeNetworkConnections same as above CascadePrinters same as above Start_ShowNetConn should be changed to Start_ShowNetConn_ShouldShow Dont forget there are HKLM settings for these as well which also could be the culprit. StartMenu.reg

Gonna bookmark this, it's really informative, thanks folks!

Mostly I use it for the WMP features, like the MP3 conversion and the Personal DJ, the tray tool is also nice. My son though likes the games and the themes, so I use it in both systems which is why I want to just go ahead and add it all. And yet your post still has nothing to do with my post above.