Nanaki

Sure, just link to this topic for updates and suggestions.

You can protect compiled au3-scripts by a passphrase. Try guessing it.

I love these changelogs, I never know what the hell is new.

Actually, it's *DRIVE* and it's included in the latest version 0.8.2. I threw it online after you said it worked fine. 0.9 will be focused on working with multiple drives. You guys can always suggest stuff that make CDswitch work along better with your project.

Try leaving it empty or putting double quotes.

Try: <execute display="Windows Messenger 5.1"> <program>%SYSTEMDRIVE%\Install\Applications\messenger.msi</program> <arguments>/qb-</arguments> </execute>

Alright, a couple of quick notes (don't have a lot of time now, sorry): 1. Try placing CDswitch into the system32 folder of $OEM$. This way you can refer to it by simply typing "cdswitch PARAMETERS". You know open it from a disc being injected, I don't know if it has influence on the whole process, but it could be. It seems to work fine, so first try the other notes. 2. The drive label refreshing too late (if it occurs) shouldn't be a problem. If CDswitch detect the old label, it should eject the drive, and not continue. 3. Try referring EXPLICITLY to the file you want to run, like this (wpi.cmd is in the root directory of the CD-ROM I believe?): %CDROM%\Apps\Misc\cdswitch.exe xpsp2_apps d: /r:*DRIVE*\wpi.cmd /k /rw Or replace *DRIVE* by %CDROM% if you're not using the latest version (0.8.2). 4. If the above works, it may very well be your AutoRun kicks in. Use the "/d" parameter to disable that if it happens. 5. Note I shortened your "/k" parameter value. If you use it without providing a value, it will write to "C:\CDswitch.txt", so providing a value isn't necessary. Now I gotta go until Sunday/Monday, so I'll hope the above (well, number 3) works. If not, I'll continue my help later on.

Lol, I've completly lost it. When CDswitch continues, it means that the correct disc is present, otherwise it won't continue. Maybe it can't find the file you supplied with the "/r"-parameter. Use the logging again to detect if it can find it or not. We'll fix this problem, but first I got to understand it.

What is not running? You're not specifying anything what should be run. CDswitch is doing exactly what it's supposed to do. :/

@totoymola: tnx, I will! @oioldman: sounds as normal behaviour to me. I don't have enough information tho. How are you installing? RunOnceEx/batchfiles/XPlode/...? When are you installing? T-12? GuiRunOnce? RunOnceEx? How are you using CDswitch? One batchfile/... per disc or one batchfile for all discs? Try manually running that autorun-file with "/r". Also, try using "/rw", this will make sure CDswitch won't exit when launching the autorun-file, but just wait hidden. In this way, the original RunOnceEx/whatever won't detect that CDswitch exits, causing it to continue and exiting.

I cracked Notepad, anyone want it?

Well, there are basically four big BIOS-distributors, so why not?

First, say the CD-drive you will be using is D:. I'll use that to make this example. 1. On your first disc, create a file called "CD.txt" on the root of the disc. 2. At the top of your batchfile, put this line of code: 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:\CD.txt SET CDROM=%%i: Now, the variable %CDROM% in that batchfile will be replaced by "D:". 3. Install your software as normally, referring to the CD-drive now: echo Installing something from disc one... start /wait %CDROM%\Applications\setup.exe /s 4. Now, when you have installed all the software from disc one, use CDswitch to switch to disc two. In Nero you can can choose the label of the disc, make sure it's different from the one from disc one. I'm gonna use "Disc_Two" for this example. Put this line in your code: echo Switching discs start /wait cdswitch Disc_Two %CDROM% 5. Now you can choose. Or you either continue this batchfile, or you launch a new one with the "/r"-parameter. I'm gonna explain the second one. 6. Instead of the previous cdswitch code, add the "/r" parameter. In this way, you can keep a batchfile per disc, making it easy to maintain your installations. Change the above code to this: echo Switching discs start /wait cdswitch Disc_Two %CDROM% /r:%CDROM%\Applications\Install.cmd Now "D:\Applications\Install.cmd" from the second disc will be launched. 7. In this new batchfile, simply do the same as you did before. First detect the drive, then start your installations, now from disc two: 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:\CD.txt SET CDROM=%%i: echo Installing something from disc two... start /wait %CDROM%\Applications\setup.exe /QN echo Installing something from disc two... start /wait %CDROM%\Applications\setup2.exe -S

Maybe flash your BIOS to the latest version?

Wow, I didn't even know I explained that in the helpfile. No, just place CD.txt on the root of the first cd. Then with the supplied command you can assign the drive letter of the drive containing the disc containing CD.txt (still following?) to the variable %CDROM%, from which you use it in your batchfile to install the apps.

What do you see when you turn on the system? ot: you live in one hell of a town. ^^

Well, oioldman explained the most part. You're using batchfiles, so this should be easy enough to figure out. 1. Make sure you're installing FROM CD, and you are not using the $OEM$-folders to first copy the installers to the harddrive. 2. Make sure cdswitch.exe is in $OEM$\$$\system32 3. When you do this you are probably using the %CDROM% variable, so now just forward it to CDswitch: cdswitch LABEL_OF_SECOND_DISC %CDROM% 4. Now, when the correct disc is inserted, your batchfile will read from the second disc instead of the first. 5. Check out the helpfile or the parameter generator for more help. Could you be more specific what the problem is? I'm gonna do a routine-answer here: 1. Try to create a log-file. However, this feature isn't worth a lot right now, but maybe it gives some useful information. 2. Check the %ERRORLEVEL%-variable after executing CDswitch, it will tell you why CDswitch exited (look up the corresponding code in the helpfile). 3. Use the new version 0.8.2 which I'm about to upload, it fixes some problems with drives ejecting when they shouldn't. Works for me, sorry. I'm about to upload a new version anyway, so wait a few secs to try again. EDIT= it's online. This 0.8-update solves the problems with drives ejecting when they shouldn't, or drives making funny sounds, ... A HUGE THANKS to MOONLIGHT SONATA for all his patient testing and help! I also label this the first "stable" release, as I don't think a lot or any bugs are left. A new feature is the variable *DRIVE*, for use with the "/r"-parameter. It simply fills in the detected drive, to make it easier to refer to it. cdswitch Disc_One /g:Disc_Two /r:*DRIVE*\install.cmd will launch "F:\install.cmd" when the detect drive is F:. You can download it in the first post. When it gives a file not found error, refresh your cache. Tnx.

I repeat everything the others said and add "you rock".

I hate applications that don't use the native windows-titlebar.

First, could you post a log-file, those things are _really_ handy. include_Items.xml: Add the "<items>" tag I inserted please note the highlighted entry should be "program". This is in ALL your program tags, so you need to do a find-and-replace. Highlighted entry should be "from". Empty entry, remove it. Should be "from". Twice to be replaced to desc=" same same what the? I can't correct more without a log-file. The other two files seem correct.

Couldn't care less about it. I wanna go back to the good old days, with ICQ 1999b or whatever the version then was.

You have 900MB cd's... R1> Before the setup even starts. Check this. R2> As far as I know, I created my 7zip .exes by doing a COPY-command of the 7z-archive and the sfx-file. It's always there. Otherwise, how about just keeping the .7z-archive, and then extracting it manually with the command line tools. R3> Maybe try asking in nLite-forum. R4> I'll check into it when I have some time. Don't like rebooting. edit=Not possible I'm afraid, the webpage you found has nothing to do with Safe Mode. I was also unable to change anything in Safe Mode.

1. No idea, but I always extract my drivers before windows setup starts, by the use of presetup.cmd. 2. Yes it's possible. You should look for a thread explaining custom 7zip sfx modules. It involves reshacking the sfx-module I think, not sure tho. 3. This is gonna require a lot of research. Stuff like drivers you can add yourself, and Windows Media Player, Interner Explorer... have an installer. Maybe by checking what files were removed, extracting all of them and copying them over to the /system32 directory manually. This would still give some problems tho. 4. You should be able to set a wallpaper in there, check the change in the registry (like with an app like Regshot) and then apply it in your uA installation. 5. "topng" can do this I think. 6. Ask in the nLite-forum, I have no idea about this. Additional notes: why these space-free-measures? I have an nLited Windows, also containing all driver packs and some extra apps, all crammed on one disc. Other apps I keep on a second disc. I didn't even nLite it much.

- Check the examples - Read the documentation - Search this forum You're all set.

By Paul Thurrott, thé Windows-guy. :/