[BM]Crusher

Radeon2.RU have a slipstream-able WDM capture driver (as well as normal Catalyst including Control Panel)... the WDM driver isn't the very latest version, but I believe it works good... all you do is extract the WDM driver to a Drivers directory and add that dir to your winnt.sif driver path list... the same with the catalyst driver they host - just extract it to a dir, put that dir in your drivers path and it installs the drivers and control panel together during PnP hardware detection... Look for these links at the top left of the page:

holy cow! someone's been busy downloading now to test it... this is great finally get rid of all those extra bits with ease! and a huge amount of flexibility you have built in! great effort top points for that one!

you can have 10 different network drivers installed if you want (i have 7)... also, it doesn't matter what you name the folders (naming them in a numerical order has no effect on what order they get installed, windows goes through the detected hardware device ID's one at a time then checks all the driver folders for a matching driver... it's not going to look at your drivers in a numerical order and try to find matching hardware in numerical order, it just doesn't make any sense to numerically name the driver folders!!!)... on my cd i have: intel inf mainboard drivers nvidia nforce mainboard drivers via 4in1 mainboard drivers nvidia forceware display drivers ati catalyst display drivers onboard ac97 audio drivers onboard cmedia audio drivers onboard creative audio drivers sb live audio drivers sb audigy audio drivers sb audigy2 audio drivers nforce audio drivers nforce lan drivers d-link 530tx lan drivers d-link 530tx+ lan drivers d-link 550 lan drivers intel pro100 lan drivers surecom lan drivers davicom lan drivers netcomm modem drivers connexant modem drivers plus many more drivers... as you can see, you can have lots of each type... windows will not install the ones it doesnt need (as it detects the hardware device id's, it searches all the INF files for a matching hardware ID, then chooses the latest version from all matching INF files)

just add 2 users then cmdow @ /HIDnet user "Username" password /addnet localgroup Administrators "Username" /addnet user "SecondUser" password /addnet localgroup Administrators "SecondUser" /addREGEDIT /S autologon.regEXITdon't change the auto-logon because you can only have one autologon anyway or, if you have 2 admins you might not want autologon at all, just remove the second last line from the above

If you already have a computer with windows installed, with the correct keyboard and regional/language settings, you can export HKCU\Control Panel\Internationaland import it via cmdlines.txt

now you got me interested, what does that qfecheck.exe do?

by the OTHER method, you mean a program called ****** ? haha just kidding anyway, any business or corporation that has a big enough network to require a network admin, should be using volume license edition already?!? we only have 10 computers on my network here, and we have volume license copies of XP (10 user license for XP Pro), and we don't even have a big enough network to require an admin

check the log file and see if they had an error... after you have run all the updates, execute QCHAIN to verify correct updating personally i like to execute the hotfixes in order through svcpack.inf... but i know the method you are using works because most people use that batch file to install their hotfixes... check the logs...

i've got a batch file that will generate the whole unattend file plus some other files.. it asks for name, organisation, admin password, computer name, workgroup, and gives options for removing lots of components one by one, plus it makes the user account and autologon files with username/password... I use it to make the unattend files when I am burning an unattend CD specific to a user/computer for them to keep (usually a modified version of their original OEM CD) ... I just thought it would be neat to have one disk I can use myself on other peoples computers that generates the unattend file per installation, rather than using my own personal copy and running sysprep after it's finished... truth be known i probably won't even find a good use for it i was just interested to see if i could use my batch file on a bootable CD I will have a look at your guide

use a batch file that creates a user account useraccounts.cmd cmdow @ /HIDnet user "Username" password /addnet localgroup Administrators "Username" /addREGEDIT /S autologon.regEXITautologon.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]"DefaultUserName"="Username""DefaultPassword"="password""AutoAdminLogon"="1"you can run the batch file from cmdlines.txt (place all 3 of these files in your $OEM$ dir) cmdlines.txt [COMMANDS]"useraccounts.cmd"

i've worked out how to use cdshell and have made a few multi-boot windows cd's and utility cd's.... a silly idea just occured to me and i dunno if it's possible so i thought i'd find out from cdshell, can it be made to run a batch file before it loads the xp boot image? i'd love a multi-boot cd that when you choose what operating sys you want to install, first it loads my custom batch file which creates a custom unattend file, then saves that custom unattend file to a ramdisk or somewhere and tells the xp boot image to use it... err, does that make any sense? or should i forget about the xp boot image? just make cdshell boot a dos prompt and autorun the unattend generator then run winnt.exe? that would work maybe? also, i've heard people mention that to run xp setup from dos, you need a fat32 partition or something? surely not!?!

double thanks for Alanoll then

there should be the %systemdrive% variable, so you don't have to create your own one for that... as for the $OEM$ directory, i think only $1 and $$ work properly out of the common ones?

jah! agreements all round! xp poofy style start menu is the default.... one of your registry tweaks or your visual style is farging it up try taking out all your tweaks which affect the start menu, see if that works, then add them in one by one... . one of your tweaks is setting classis start menu style somewhere... maybe this one: "ClassicViewState"=dword:00000000???

i wouldn't recommend running any app installs through svcpack (like winamp) although you can put the media player 9 and directx9 silent installers in here wait until the first boot of windows to install any apps It doesn't look right because you are missing all the critical updates? Or are they slipstreamed? If they are slipstreamed, where is the ProductCatalogs info? don't use the "slipstream" media player or directx... you need this Media Player 9 Installer and this DirectX 9.0b Installer install your boot screen etc through cmdlines.txt, or through runonceex commands here's a sample svcpack.inf [Version]Signature="$Windows NT$"MajorVersion=5MinorVersion=1BuildNumber=2600 [setupData]CatalogSubDir="\I386\SvcPack" [ProductCatalogsToInstall] [setupHotfixesToRun]q330994.exe /Q:A /R:Njs56nen.exe /Q:A /R:Nmdac.cmdq823182.exe /Q /O /N /Zq824105.exe /Q /O /N /Zq824141.exe /Q /O /N /Zq825119.exe /Q /O /N /Zq826939.exe /Q /O /N /Zq828028.exe /Q /O /N /Zq828035.exe /Q /O /N /Zq828741.exe /Q /O /N /Zq831167.exe /Q:A /R:Nq832894.exe /Q:A /R:Nq835732.exe /Q /O /N /Zq837001.exe /Q /O /N /Zq837009.exe /Q:A /R:NWMP9MM2.exeq828026.exe /Q /O /N /Zqchain.exeDX9NTopk.exe

Mine work perfectly and I made the file myself (I don't use xp create) [Version]Signature="$Windows NT$"MajorVersion=5MinorVersion=1BuildNumber=2600 [setupData]CatalogSubDir="\I386\SvcPack" [ProductCatalogsToInstall] [setupHotfixesToRun]q330994.exe /Q:A /R:Njs56nen.exe /Q:A /R:Nmdac.cmdq823182.exe /Q /O /N /Zq824105.exe /Q /O /N /Zq824141.exe /Q /O /N /Zq825119.exe /Q /O /N /Zq826939.exe /Q /O /N /Zq828028.exe /Q /O /N /Zq828035.exe /Q /O /N /Zq828741.exe /Q /O /N /Zq831167.exe /Q:A /R:Nq832894.exe /Q:A /R:Nq835732.exe /Q /O /N /Zq837001.exe /Q /O /N /Zq837009.exe /Q:A /R:NWMP9MM2.exeq828026.exe /Q /O /N /Zqchain.exeDX9NTopk.exe

Some days, when I can't get anything to work, I wonder if it was worth waking up that day heh then I just delete everything and start from scratch! i used to do that a lot when i first started making my unattend cd

71 ?!?!?!? jesus christ!

unattend.txt is used if you boot from floppy or network.. winnt.sif is used if you boot from cdrom.. read the unattend.txt section of REF.CHM for more details

err... i meant the entire $OEM$\$1 directory like drivers, installs, sysprep, cleanup.cmd etc etc (my $1 has craploads of stuff in it, i think its 250mb or more) the others you would have to place in seperate archives too correct jrzycrim like $$ and $Progs etc...

i dunno if you can use long file names or spaces in your cmdlines.txt commands, anyone know for sure? try making a batch file (tweaks.cmd) that imports the reg tweaks, call the batch file from cmdlines.txt (this is how I used to do it)

20 including dx9, mp9 and qchain? or 20 updates? i only have 17 updates, but windows update say's im patched for all the criticals... am I missing some cool recommended updates or what?

i wasn't holding out i forgot all about that post of mine but yeah, that must have been where i read it could be done for drivers

i believe it extracts the archive first, i have seen other posts where people have compressed the entire OEM structure and not just the drivers section... test it though, i have never tested it myself

that would probably work... but what does your runonceex.cmd do? does it install the apps itself or does it set up runonceex commands? if it sets up runonceex commands, you should run it through cmdlines.txt and include the service pack and shutdown paramaters in the runonceex list.. otherwise, it will work ok... and you can put your shutdown command into the end of the service pack batch file.. same with the user deletion that can go anywhere in the batch files so long as it gets run I don't think you can put the shutdown command or user deletion command directly into winnt.sif because they have spaces