Alanoll

you should add zero's to the /v 1 values. so /v 001 /v 002 /v 003

are both Regtweaks.reg and RunOnceEX.cmd in $OEM$? is cmdlines.txt in $OEM$? as stated before, the syntax's are wrong. cmdow @ /HID @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\001 /VE /D "Preparing Installation..." /f REG ADD %KEY%\002 /VE /D "Adobe Reader 6" /f REG ADD %KEY%\002 /V 1 /D "%systemdrive%\install\adobe123.exe /qn" /f REG ADD %KEY%\005 /VE /D "AD Aware 6" /f REG ADD %KEY%\005 /V 1 /D "%systemdrive%\install\aaw61234.exe /qn" /f REG ADD %KEY%\006 /VE /D "Winzip 9.0" /f REG ADD %KEY%\006 /V 1 /D "%systemdrive%\install\winzip90.exe /qn" /f and not every application uses /qn. As stated before, search for the correct ones. I fixed the code above to remove the invalid syntax. PAUSE does not work in cmdlines.txt just for reference. And when do you check for the keys? When you see the desktop? If so, you won't see them if they did work. They delete themselves when run. Presss <CTRL><F10> during setup at about T-10 or so, and type REGEDIT, then look for the keys.

you do of course have OEMPreInstall=YES and only one entry of OEMPreInstall right? In your winnt.sif

you have IE and IE6GO in the right place, but if you had actualy run XPCreate before asking questions, it would answer quite a few of them. the PRE folder gets the appropriate fixes. You don't use CMDLINES.TXT as for DX9, it's also on the website.... SVC-PRE DX9NTOPK.EXE (DirectX 9b OEM Preinstallation Kit Version) 11,751,280 Bytes IE6.EXE (Packaged IE6 SP1 Installer) IE6GO.EXE (IE6.EXE Helper) 64,000 Bytes That's from the Current Hotfixes page on the XPCREATE website. DX9NTOPK.EXE is DX9. Just download it off of unattended.msfn.org

i haven't had any problems? how can I reproduce it? I should point out, I don't have the file gen_ml.dll. So umm....yeah....

could it be that the archive is deleting the files after it extracts them? I know some of em have that option, maybe an accident?

read the website.....it tells where you they go.

once all your hotfixes are in their right folders, OPEN XPCREATE.INI, and on the line that says SOURCE, put the drive letter and colon to your XP CD (Original one), then just double click XPCREATE.CMD, it does the rest. As for the number of corners....millions. They're just really really small.

http://www.msfn.org/board/index.php?showtopic=18715

no...for what he wants, the 001 is right. It's not being over written as he is making 1,2,3,4,5,6 inside of it.

yeah..umm....ok...... use CODE tags when posting code. Second, is that how Administrators is spelt on YOUR version of XP? If not, make it so it is. And DefaultPassword, just put "" not "*" if you don't want one. Same for the like that creates your user. Just leave it out if you don't want a password.

No. It's been repeated several times. Start from a fresh source each time your build with XPCreate. DOn't use one that XPCreate has already done. You'll end up with a messy DOSNET.INF and TXTSETUP.SIF file that could cause problems. It's safer to start from scratch, and only takes maybe another 20-30 minutes (which it would anyway) and then just copy in your $OEM$ folder. What you should do, is copy the source of your original disk on to the harddrive, have XPCREATE use that as SOURCE, and then jsut rerun XPCREATE off that, instead of an already modified one.

that is wierd. I have SP1a, and don't include ANY java updates, and I don't have it showing up on WU.

do you also add the JAVA VM through another file? or are you sure that you truly have the SP1a and not SP1?

maybe it's just me, but no one bothers to search. I've posted before why a few will show up after reducing source. They rely on components. I've also posted in the nLite thread why WU thinks they aren't there, while MBSA thinks they are. I suggest, XPCREATE then REDUCE. That way you have an updated source, and then it's removed. If the component is removed by REDUCE, then it won't get updated. But if removed first, XPCREATE doesn't know that, so it adds the files back, and then they are registered during setup and errors can arise depending on what it is.

WTF! What about %Sourcepath% not being available outside XPLODE do you not understand? techinially, you don't even need that file. "..\Xplode\Xplode.exe"Judging from your paths right here, IF XPlode.exe is located in a folder called XPLODE in the same folder that $OEM$ and I386 are in (all three are in the same place, not in eachother) then this should work. I'm not guarenteeing anything about the applications as that's your mess. Word of advice, keep it simple. You went from one idea to another, without ever getting one working. Then you assumed something worked, complained that it didn't, but never bothered to read the documentation. ALOT of your answers require common sense and reading the documention CHM and this forum. I should point out, your image link is broken. That starts it from CMDLINES.TXT. Just add the arguments to that. If the XML file is called XPLODE.XML then, the /xml: isn't needed either.

@nlite and grimsage It's not nLite's fault that the hotfixes are being reported missing. It's because of the componants you're selecting that are making them appear. I was refering to the logs created by the HOTFIX's. They're in Windows direcotry or System32, one of the two. @Markymoo The Java update it not listed on the XPCREATE website, simply because officially it's not longer supported. The list maintained there is for use with SP1a, and since Java isn't in it, the fix isn't added. The site deals with the latest hotfixes, not where legacy ones should go.

whoever said ANYTHIGN about using SetupParams? I know I didn't. You can use it all you want, but for what you want, It's not needed. Just used the method above.

you should use CMDLINES.TXT Like the linked document tells you to do.

uh oh Mac! See what happens when you give into people before it's ready? I'll test it when i get home, I may even make a patch file for it, if I'm lazy enough.

how many times must I say this..... %SOURCEPATH% is not defined EXCEPT THROUGH XPLODE. So your line won't work. SetupParams requires XPlode to be on HDD. READ the linked post in my signature about getting it started, FOLLOW IT EXACTLY.

well, in your last post, I can tell you EXACTLY whats wrong. XPLODE does NOT work with SP2 yet.

have you gotten the log file going yet?

I don't think there realy is any difference. CMD are typically found more on NT machines, while BATs are DOS/9x machines. It could jsut be Microsoft trying to get away from DOS. The commands work in both, and XP can run both, but 98 can't run CMD unless you rename it to BAT EDIT:: Just found this

the code is a BATCH file. just copy and past into Notepad, and save as a CMD or BAT file.