Alanoll

no...that pack is just the DAT file which is the boot sector and CDIMAGE which is universal for all. The only difference between the packs is I believe the label that is used for the CD. and the DAT file is the same as for 2003 and 2000. I don't believe it's the ISO. Especially since you're running the programs from a non-CD source (right? i think you said that before) have you tried the Acrobat command outside of the batch file? Or extracted it and gotten the inner MSI so there aren't nested switches?

post your CMDLINES.TXT file as well..... CMDLINES.TXT is in your $OEM$ folder? Acrobat worked fine with that exact same command at GUIRunOnce?

I personally change it to the date I actually make it. That way I have some reference for which is newer then the others....

I've never really check what services are running or not. But my reason for not liking Autopatcher is just because it was made by someone else. Sure it's just a compilation of numerus hotfixes and it saves time getting them one at a time, but why use that program to install the hotfix when I can do it myself in SVCPACK.INF like Microsoft suggests. It could just be that Autopatcher can't run at that point because somethign is loaded that it depends upon. Always possible. If you still want it move to the Apps Switches forum, let me know....

have you searched? do you have the standalone version? the one that requires the Serial? You may then need to use InstallRite or something similar

wow..... that's alot of tweaks.... what I suggest is to break it down into sections. comment out line by line, which is easier in INFs are you can comment one line and a whole chunck is out of the process. Also, the AddReg should be: AddReg = Section1, Section2, Section3, Section4

T-9 would be the easy thing. You just change it in the WINNT.SIF file..... but T-12 would be harder. As it is run from CMDLINES.TXT. You'll need to determine a single file that copied during install the designate it...... what you could do as each boot folder requires a seperate txtsetup.sif, you could ADD a file like the WIN51 but each is unique to each boot folder, and in CMDLINES.TXT you have a batch file that then looks for that file and runs the appropriate XPLODE with corresponding XML file from there.

yes, the line breaks are fine.... HKCR,"CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\services",,,0x00000001 looks wrong.... you have perhaps an extra comma judging from your original reg file.... HKCR,"CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\services",,,0x00000001,53,00,65,00,72,00,76,00,69,00,63,00,65,00,73,00,00,00,SuppressionPolicy,4000003c HKCR,"CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\services\command",0x00000001,25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00, 6d,00,33,00,32,00,5c,00,6d,00,6d,00,63,00,2e,00,65,00,78,00,65,00,20,00,2f,00,73,00,20,00,25,00,53,0 0,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d ,00,33,00,32,00,5c,00,73,00,65,00,72,00,76,00,69,00,63,00,65,00,73,00,2e,00,6d,00,73, 00,63,00,20,00,2f,00,73,00,00,00 should probally be HKCR,"CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\services",,0x00000001,53,00,65,00,72,00,76,00,69,00,63,00,65,00,73,00,00,00 HKCR,"CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\services",SuppressionPolicy,0x00010001,0x4000003c HKCR,"CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\services\command",,0x00000001,25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00 ,6d,00,33,00,32,00,5c,00,6d,00,6d,00,63,00,2e,00,65,00,78,00,65,00,20,00,2f,00,73,00,20,00,25,00,53, 00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6 d,00,33,00,32,00,5c,00,73,00,65,00,72,00,76,00,69,00,63,00,65,00,73,00,2e,00,6d,00,73, 00,63,00,20,00,2f,00,73,00,00,00 HKLM,"PATH\TO\KEY",,0x00010001,0x00000001 create a DEFAULT value of 0x00000001 as a DWORD. It would be like @=dword:0x00000001 Also, those seperated lines of numbers are not the same in a INF file. IT'S ONELONG STRING. It may take a couple of lines, but there are no line breaks.

well, obviously he's using the latest XPCREATE. First runthrough, jsut execute it without changing any functions on downloading. Let it create the base disc. Then after teh first time (it will have downloaded all the hotfixes) open up the INI file, and change DLAUTO=YES to NO and then delete away.

**Disclaimer** I here by acknoledge this may be considered rednecky, but it is not meant to be serious or to hurt someone. because they be ignant in the matter But truly, GM is right. You should either try their forum since it is THEIR software, or try removing the /nolog switch and look at the log. They I may laugh when someone over there tells you the same thing

Most code box's I just skim for serials and what not. If i actually post in the thread, I glanced at it. now quote boxes on the other hand.....read those everytime. It's great when someone edit's their post, but someone has already snagged it for a quote.... Thanks go to enuffsaid. I'm also interested where you pulled those out from? The air, your hair, your ... ? lol As long as they work, who cares.

well, just because I don't use AutoPatcher I don't know exactly waht's wrong, but if you got 20 minutes or so, run the install again, but remove the /nolog and see if the log says anything. They are quite helpful in some cases.

you could, if you declare it in the STRINGS section of the INF. also keep in mind, if DWORD is equal to 0x00010001, you could short hand it to 0x10001 and for strings, it's just ,, or ,0, or ,0x00000000

[DefaultInstall] AddReg = RegTweaks [RegTweaks] HKCU,"Software\Microsoft\Internet Explorer\Main","NoUpdateCheck",0x001001,0x00000001 Just di d that rom memory. What might not work is the 0x0001001 and that's just because it might be the wrong value (i forget what is dword)

you may have missed this post... but surely you saw it when he posted it in the XPCREATE forum. It's in the DX9 hotfix thread in there near the end. He posted about it

INI files are usually just used to declare variables and what not. INF files are usually considered installation file. They're like batch files, but are run under a different context.

i believe there is an option in your Winnt.sif that determines upgrade...... let me go look, and I'll check back search for NTUpgrade in the ref.chm file. It might pertain even though it says it's for .NET.

try removing the cmdow command at the begging so you actually see the batch. Then put a pause after the change CD2 and CD3 prompts line in the batch. Perhaps it's giving you an error and you're not seeing it.

what kind of INI files? it's basically just [KEY] Value= and that's all there is to an INI. Now do you mean INF? If so, Microsoft has some EXCELLENT documentation on the subject. It's in their DDK section though

I saw a post awhile back about determining Video card or some drivers or something. It might pertain to this, as XP will notice if it's a CDR/DVD drive (the different Icons) and it should save it somewhere. That would be my best guess. I think GreenMachine posted a link to somewhere. I know a few others did too.

i believe the file is ntfs.sys I would recommend starting from scratch and not undoing all the damage you've done to your Unattended CD, and start over. It's ALOT easier to troubleshoot.

could you post what you have tried? Regtweak maybe. It could just be a typo and you're not seeing it. I've done it a few times, and it's a real pain when that happens.

don't worry, it's just a little reminder for future posts. I already changed it. It's all good. It's just made to make the board look all perty and all clearly shows what's code and what isn't. Not to say youre dash's didn't do that, but gotta admit, the white box does it abit more

why would a GUI be neccesary? I personally got more confused on the old green one then the new one. It's just put the files where they go, double click.....and you're done. As for drivers, sure....if you use OEMPnPDriversPath you could add files to FILESCD and such. But not the like of the RAID/SATA drivers.

dude, I'm a MOD. So in part yes and no. And as for a resolution, I told you the only resolution that I have seen... as more negative answer, somehow your files got corrupted. Also, the file format of the disc might also have something to do with it, as it comes close to exceeding ISO-9660 specs. CDIMAGE might create the image wrong on times. Try without the -o or any optomization switches.