Alanoll

it you went with your original idea of having a seperate CMD file....you could do it like so.... HKLM,"%RunOnceEx%\BBinstall",1,,"%11%\xcopy.cmd %01%" then in xcopy.cmd xcopy.exe %1\install %SYSTEMROOT%\install\ /S /C /Q /H /Y (I took a guess at %24%, I forgot all the DIRIDs at the moment.) but basically I passed %01% to the xcopy.cmd, and %1 in the CMD file is the first argument, where %2 would be the second, if there is one. Each argument is seperated by spaces, so you may need quotes if there are spaces in the path.

I still kinda like mine....and in theory it's solid. In theory atleast. What exactly are you trying to do, and I can try again...

Your code has the problem that mine has a way to get around. Yours will ONLY work if you have BOTH CDs in at CMDLINES.TXT otherwise, as you said before it will just skip over Office. In yours, even though you set %OFFICE%, you won't be able to change CDs. RunOnceEX and all variables are expanded at the time of importing. If the variable is supposed to change, RunOnceEX does NOT take this into account, as the CMDLINE expands the variables before importing into the registry so they get inported as D:\setup.exe or whatever, NOT %OFFICE%\setup.exe Your for statements are fine (though C: really shouldn't be neccesary ) All your's does is stall for 30 seconds, then runs Office setup IF the CD was in the CDROM when RunOnceEX was executed and the CDROM hasn't changed. This negates being able to change CDs but rather the CDs HAVE TO STAY IN THE DRIVE. However..... If you were to do something like I did, and call a batch file (inplace of the Office setups and sleep) THEN find teh Office CDROM, THEN EXECUTE from the same batch it will work (even if the CDROM is NOT in the drive when RunOnceEX is) and just to reiterate how RunOnceEX works. All that is happening when RunOnceEX.cmd is executed, is the %VALUE% is getting expanded to whatever is assigned to it (D: or whatever) and THEN imported into the registry as fixed strings. Upon restart is when the actual actions governed by the entries is executed.

if you look here... http://unattended.msfn.org/xp/runonceex_cd.htm Just pay attention to the part with the IF EXISTs in it. If you're using a batch file, that will eliminate the problem of the letter changing per computer, as it searches for a file on your CD and then assigns the variable to the letter if found the file on. If you use any other way, shouldn't be too hard to get the right variable path. As for the optomize.... pretty much, in your folder structure you have the exact same file twice. Using CDIMAGE or a modifed MKISOFS, you can have it so the file itself is written to the image only ONCE but appears to be in both places. If you know anything about programing, think of it as a reference pointer

most likely typos.... REG ADD %KEY%\018 /VE /D "Microsoft Office 2003" /f REG ADD %KEY%\018 /V 1 /D "%XPCD%\install\changecd.cmd" /f REG ADD %KEY%\018 /V 2 /D "%XPCD%\install\Office\setup.exe TRANSFORMS=\"%XPCD%\Install\Office\office.mst\" /qn" /f REG ADD %KEY%\018 /V 3 /D "%XPCD%\install\changecd.cmd" /f but like I said, I didn't test this

I think I got everything you wanted, sorta. RunOnceEX.cmd REM CMDOW @ /HID CLS TITLE Importing RunOnceEX Entries IF EXIST D:\CD1.txt set XPCD=D: IF EXIST E:\CD2.txt set XPCD=E: IF EXIST F:\CD3.txt set XPCD=F: IF EXIST G:\CD4.txt set XPCD=G: IF EXIST H:\CD5.txt set XPCD=H: IF EXIST I:\CD6.txt set XPCD=I: IF EXIST J:\CD7.txt set XPCD=J: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\005 /VE /D "Adobe Reader 6" /f REG ADD %KEY%\005 /V 1 /D "%XPCD%\install\AdobeReader6\AR6.msi /qn" /f REG ADD %KEY%\010 /VE /D "Alcohol 120" /f REG ADD %KEY%\010 /V 1 /D "%XPCD%\install\alcohol\setup.exe /qn" /f REG ADD %KEY%\010 /V 2 /D "REGEDIT /S %XPCD%\install\alcohol\register.reg" /f REG ADD %KEY%\015 /VE /D "Diskeeper 8" /f REG ADD %KEY%\015 /V 1 /D "%XPCD%\install\DiskeeperPro_8.0.459.exe /s /v/qn" /f REG ADD %KEY%\018 /VE /D "Microsoft Office 2003" /f REG ADD %KEY%\018 /V 2 /D "%XPCD%\install\changecd.cmd" /f REG ADD %KEY%\018 /V 1 /D "%XPCD%\install\Office\setup.exe TRANSFORMS=\"%XPCD%\Install\Office\office.mst\" /qn" /f REG ADD %KEY%\018 /V 3 /D "%XPCD%\install\changecd.cmd" /f REG ADD %KEY%\020 /VE /D "DU Meter 3" /f REG ADD %KEY%\020 /V 1 /D "%XPCD%\install\dumeter3.exe /VERYSILENT /SP-" /f REG ADD %KEY%\025 /VE /D "IsoBuster 1.5" /f REG ADD %KEY%\025 /V 1 /D "%XPCD%\install\IsoBuster1.5.exe /VERYSILENT /SP-" /f REG ADD %KEY%\025 /V 2 /D "taskkill /F /IM isobuster.exe" /f REG ADD %KEY%\030 /VE /D "Kerio Personal Firewall 2.1.5" /f REG ADD %KEY%\030 /V 1 /D "%XPCD%\install\KPF\Setup.exe -s" /f REG ADD %KEY%\035 /VE /D "MDAC 2.7 SP1 Hotfix" /f REG ADD %KEY%\035 /V 1 /D "%XPCD%\install\mdac\mdac.cmd" /f REG ADD %KEY%\040 /VE /D "MSN Messenger 6.1" /f REG ADD %KEY%\040 /V 1 /D "%XPCD%\install\MSN_Messenger_6.1.0202.msi /qn" /f REG ADD %KEY%\045 /VE /D "Nero Burning ROM 5.5" /f REG ADD %KEY%\045 /V 1 /D "REGEDIT /S %XPCD%\install\nero\register.reg" /f REG ADD %KEY%\045 /V 2 /D "%XPCD%\install\Nero\Nero551054.exe /silent /noreboot" /f REG ADD %KEY%\050 /VE /D "Importing Registry Tweaks" /f REG ADD %KEY%\050 /V 1 /D "REGEDIT /S %XPCD%\install\regtweaks.reg" /f REG ADD %KEY%\055 /VE /D "Cleaning Up and Rebooting" /f REG ADD %KEY%\055 /V 1 /D "%XPCD%\install\cleanup.cmd" /f EXIT changecd.cmd CMDOW @ /HID CLS TITLE Changing CD IF EXIST D:\CD1.txt set XPCD=D: IF EXIST E:\CD2.txt set XPCD=E: IF EXIST F:\CD3.txt set XPCD=F: IF EXIST G:\CD4.txt set XPCD=G: IF EXIST H:\CD5.txt set XPCD=H: IF EXIST I:\CD6.txt set XPCD=I: IF EXIST J:\CD7.txt set XPCD=J: COPY /Y %XPCD%\Install\cd_prompt.vbs C:\cd_prompt.vbs CDR.EXE open %XPCD% start /wait wscript C:\cd_prompt.vbs CDR.EXE close %XPCD% DEL /Q /F C:\cd_prompt.vbs EXIT cd_prompt.vbs MsgBox "Please insert CD2. When the drive is done flashing, press OK" , vbOKOnly, "Please Replace CD" So here's what it does....theoretically anyway (haven't tested) RunOnceEX.CMD imports the neccesary entries. Upon restart RunOnceEX will run... when it gets to the Office 2003 (can be any program realy), changecd.cmd will run in the background, and all you should see is a prompt saying "Please insert CD2. When the drive is done flashing, press OK", while at the same time, the CD rom drive %XPCD% should eject to replace the CD. (Note, I didn't code this to allow for more then one CDROM in use, if you have more then one, then you could just add more IF EXIST at the begining of RunOnceEX.cmd to check for a file on the second CD and change the variable accordingly) When you press OK on the prompt, the CDROM should reinsert. and Office will install. Then changecd.cmd runs again, to get the original CD back (can be left out if the rest of your RunOnce is from second CD, or it's the last entry. Just keep track if you need the original CD) Did I leave anythign out? CDR.EXE can be found form teh download section of the Unattend site.

well, I personally want to put the blame on CDIMAGE The only time I dont'g et the error is when I don't tell it to optomize the CDIMAGE (mine are usually over 2 gig)

you could right in your VBScript file that ejects the CD MsgBox "Please Eject CD. When finished Press OK.",vbOKOnly,"Eject CD!" (i'm not sure of the entire syntax, but that's the general IDEA.) I'll be writing up some sample code if no one gets to it before me.

i should point out, you you're going to either switch the CD 4 times, or some hefty tidbits. but on a more technical side....let me write up some code for you to test with.

Ever run setup from windows? Also one is digitally sign, and the other isn't. It could just be another attempt to limit modifications to their install.

Well, since you say CDIMAGE creates the problem (and since I vaguely remember posting in the thread you linked to ) Have you tried using mkisofs ? nLite uses a modified version I believe to create the same effect CDIMAGE does. Could be worth a shot I'm surprised no one every noticed the relationship with the switch taht actually LETS you build an iso past 650mb. lol. Oh well.

Any notice the SETUP.EXE sets a few registry entries? If you use both method, it may add a few seconds to your install, but it'd be completer. Also, some peopel complain about GART not being installed, but I've never had that proplem when using both methods. Indeed, it's an InstallShield setup. There is an ISS file already included, but I suggest your make your own with -r incase the current one has reboot set to yes. http://unattended.msfn.org/xp/applications/installshield.htm I like to use -f2 well calling my InstallShield files, just use -f2"%windir%\temp\ati.log" as it will make a log and if there are any errors, you'll get an erroccode and you can search what it means. Indeed. Any questions, look to the quote above this one Theoretically, it shouldn't install. In theory anyway. Otherwise, as prathapml suggested, you do a simple check to see if an ATI file is present, if so it installs. If not, it doesn't. @Tbone2 This originated in teh Winamp 5 msi thread, and so I gutted it from that thread. As for posts, I've made a few posts saying the same thing, but I doubt people listened But basically, you just combine all the methods. YOu would get your INF and drivers like your normally would and add it to OEMPnPDriversPath. You don't need to keep them with the setup files, you can just copy them to another folder if it's easier for you (note I said COPY not MOVE). Then with the SETUP.EXE files, create an ISS file for both Control Panel and the Drivers, then from CMDLINES.TXT install the Drivers SETUP.EXE using the typical InstallShield (linked above) method. Then from somewhere somehow at first logon install the ControlPanel.

Make a thread and I'll sticky.

well hehe good for you...maybe you can hehe share in this thread for others to know exactly what you hehe did...I think its disrespectful to those in this thread..that have helped or are still seeking anwsers...that when one finds his solution...to then run off..without explaining...so that other will have ideal to help future members....hehe He did. 5 posts above yours.

It is. I just think he doesn't want to do the "optomize" thing, simply because it'd be more trouble updating and he wants everything in one place.

Gosh's method is not service pack specific. It simply executes the Windows based install so that it parses DOSNET.INF. That's about it. SO yes, it can be used on SP2. Assuming you've properly edited that files (setupldr.bin and such) to reflect you're new boot folders (VOL1 and such) then it should work fine that way you've said it. As for not having duplicate data, are you installing from CD or HDD? If you don't want duplicate data (as much anyway) CD would do. YOu have a central folder in your Root that all your software is in. That may do ya. Otherwise that's you're only way out.

yeah, but it's a few less function calls during startup to determin what picture to show. (My word choice before was....unwise. I knew they were one kernel, but it could just be easier for Microsoft to get rid of those tags anyway)

http://unattended.msfn.org/xp/runonceex.htm that's pretty much the same thing but allows for variables. But is install.cmd in C:\install or in %CD%\$OEM$ ? (%CD% being where ever your installing from) Do you have OEMPreInstall in your Winnt.sif, and if you don't have one of those, then you should copy your programs over manually.

really and truly, is any Windows Installer installs if you it showed more then once As for teh "official" database, perhaps (I haven't opened the program yet) but not everyone uses RunOnceEX, though this will probally convert a good chunk of those batch peopel seeing as it could be easier.

OemPreinstall=No Change it to OemPreinstall=Yes] And that's why it's not working. Your files just aren't getting copied over, adn taht will fix it.

FOR /F "tokens=3 delims= " %%A IN ('REG QUERY "HKLM\SYSTEM\ControlSet001\Control\Session Manager\Environment" /v NUMBER_OF_PROCESSORS') DO SET NUMBER_OF_PROCESSORS=%%A bootcfg /copy /D "Windows XP Professional" /ID 1 if %NUMBER_OF_PROCESSORS%==2 goto DUAL REM ----For Single proc bootcfg /RAW "/Kernel=OEMKrnl.exe" /A /ID 2 goto End :DUAL REM ----For Multiprocess/Hyperthread proc bootcfg /RAW "/Kernel=dualKrnl.exe" /A /ID 2 :End bootcfg /Timeout 2 bootcfg /Default /ID 2 I've been using a modified form of that since I first wrote it back in October. The only difference being I've used WIHU/XPLODE to get the variable and then just passed it to the batch file.

Did you do what FFA did and delete the for letters and then started typing? If so, that's wrong. Should just click where you want to start changing and type.

Wich one goes to CMDLINES.TXT? The Control Panel? Don't start a new thread, I'll get this one. Have your OEMPnPDriversPath point to your Catalyst folder 2kXP or something like that. THen in CMDLINES.TXT through whatever method you use (not RunOnceEX) call the SETUP file for the Catalyst drivers, not the one that installs EVERYTHING just the one for the drivers. THen from GuiRunONce install the Control Panel.

Tips and Tweaks sounds good.

if the tweaks are in the registry file (.REG) or an INF (.INF) then yes, you use the same command call you would in a batch file (regedit.exe /S tweaks.reg for reg files). As for drivers, if depends what you're trying to do. If they have an EXE file, then you can. Anything that you can normally call from a command prompt, or a run box you can run from XPlode. But if you have the drivers in INF form, then I suggest using OEMPnPDrivers path or some other method to get windows to see the path to the INFs so it automatically looks there when it finds new hardware.