jbm

is si3112r.sy_ in the i386 folder of your CD?

I go to windows update, find what it says I need. Then use administator options to download the updates and save them so I don't have to download them again. I'll give WUtools a try

I put mine in the $OEM$ folder and call it fropm cmdlines.txt [COMMANDS] "regedit /S myregtweaks.reg" This way the tweaks get applied to all users.

; Remove My Pictures / My Music / Recent Docs from Start Menu [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\explorer] "NoSMConfigurePrograms"=dword:00000001

You could use the search function. Maybe some of these posts will help http://www.msfn.org/board/index.php?act=Se...e=%2BICFGNT.DLL

to boot from the Nvidia controller in SATA mode you have to enable the Nforce RAID controller then disable RAID on each drive in the BIOS you don't want to use in RAID mode. I've had no problems integrating the drivr packs using both methods 1 and 2 haven't tried 3 yet. I'm not using them now because I wanted to learn how to do somethings myself. If you haven't read this tutorial http://www.uawiki.org/doku.php?id=wxp:ua:d...rpacks:tutorial it help me.

Thanks everyone for your help. Found some AMD 754 Palmero core CPU's at Newegg, but I think I'll wait for when I upgrade my graphics card and have to buy a new MB with PCI-express. Plus I don't know what the difference would be going from a 1MB cache to a 256KB one.

Anyone know if it's possible run a 64bit guest OS on vmware with any AMD 754 pin CPU? When I try to create a virtual machine to do this I get a message saying 64-bit guest is not supported on this host. Vmware FAQ says CPU must be rev D or later or all CPUs build using 90nm will support it. I don't think AMD released any 754 pin CPUs using the 90nm proccess but I don't know about Rev D. And I am running XP x64 and vmware workstation 5.5

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "ClassicViewState"=dword:00000001

The only way I noticed the space is I made a reg file of your post and merged it in my registry. When I looked in the resistry it was plain as day. The hardware on Vmware and Virtual CP is emulated so it doesn't use the drivers for your actual hardware.

In the guide for multiboot CD/DVDs http://flyakite.msfnhosting.com/ under XP PRO SP1 is a link to the CD boot file. PRO1.DAT Have you tried www.bootdisks.org I don't know how to extract itfrom the CD without using some kind of tool.

It appears you have a space at the end of the following line. FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\WIN51IP.SP2 SET CDROM=%%i: And I wasn't able to set my display resolution with winnt.sif until I installed a WHQL driver. I couldn't even get it to work with the Microsoft driver on the CD. But it's been awhile so it may have been something I was doing wrong at the time.

@Bezalel Thanks this fixed it for me DrvPath = Mid(Subfolder.Path,Len(SysDrvFldr),StrLenth + 1)

When I run the script I get OemPnPDriversPath=";;;;;;;;;;;;nXP;;;;;;;;;;;;;XP;XP\DATA;;;;;;;;;;;;;;;;;"

I guess it depend on how you install your programs, but I have it in $OEM$\$1\install and call it from runonceex with REG ADD %KEY%\295 /VE /D "Copy XP Source" /f REG ADD %KEY%\295 /V 1 /D "hidec /w %SystemDrive%\install\source.cmd" /f I'm not sure but I think you should be able to put it in $OEM$ and call it in cmdlines.txt with [commands] "source.cmd"

@Sonic Thanks for you input. I use /dudisable because I want to disable dynamic updates and /unattend because I don't want to be prompted. As for removing 'md %systemroot%\Source\i386' and replacing it with 'xcopy /Y /E /H %CDROM%\i386 %systemroot%\Source\i386\ /S' how much time will I save? I got this batch from this forum a while ago and it's worked ok for me.

Here's what I use. I also install the recovery console, just remove the REM if you want to do that also. source.cmd cmdow @ /HID REM @ECHO OFF REM for %%i in (D: E: F: G: H: I: J: K: L: M: N: O: P: Q: R: S: T: U: V: X: Y: Z:) do if exist %%i\WIN51 set CDROM=%%i REM ECHO Please wait, Recovery Console is being installed locally. REM %CDROM%\i386\winnt32.exe /dudisable /cmdcons /unattend md %systemroot%\Source\i386 ECHO Please wait, source files are being copied. This may take several minutes. xcopy /Y /E /H %CDROM%\i386\*.* %systemroot%\Source\i386\ xcopy /Y /E /F /C /R /H %CDROM%\i386\*.sys %systemdrive%\cmdcons\ ECHO Adding registry entries. regedit /S %SystemDrive\install\source.reg ECHO Done. EXIT source.reg REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /v "SourcePath" /t REG_SZ /d "%systemroot%\Source\" /f REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /v "ServicePackSourcePath" /t REG_SZ /d "%systemroot%\Source\" /f

you can use variables in the registry. If you want to use %systemroot% just put %%systemroot%% in your reg file. And besides when you import a .reg file with %systemroot% it will be replaced with c:\windows in the registry, or what ever your path to windows is.

Then you should post a copy of your winnt.sif minus your CD key.

Including the lines below in your winnt.sif file will cause setup to delete all the partitions on the C: drive and create a new partition and format it as NTFS. If you have partitons on this drive you want to keep then don't use this. [unattended] Repartition = Yes I always choose to manually partiton, just to be safe. On my computer if I have an external USB2 or Firewire drive hooked up setup wants to make it my C drive.

What dows it tell you when you enter set in a command window?

I use the same boot image for both CDs(650MB) and DVDs(4500MB) without any problems.

Here's what I have in my winnt.sif, you'll have to adapt it to your drivers. [Data] OemDrivers=OemInfFiles [OemInfFiles] OemDriverFlags=1 OemDriverPathName="\DRIVERS\005HD" OemInfName="fasttx2k.inf","NVATABUS.INF","NVRAID.INF","s150tx2k.inf","Si3112r.inf","SI3114R.INF","ulsata2.inf","VIAPIDE.INF","VIASRAID.INF"

Only OEMs who have built more than 1000 computers in the previous 12 months can produce these CDs Ah, thought it was something like that. only 995 to go

I haven't used nlite myself to integrate hotfixes. Only know from reading other posts. So hopfully someone else will step in if you need more help. Did you try the windows update site after the install to see what it said you still needed. Because I believe if nlite integrates them into the install they won't show up in add remove programs.