Incroyable HULK

that's it? Cool! I wanna try this So there is a broadcast on the network from the RIS server...

Looks like a fine tutorial to me but there is one important step missing: How do you launch the installation on the client???

First off, take a look at the Guide: http://unattended.msfn.org/xp/applications.htm http://unattended.msfn.org/xp/applications/innosetup.htm http://unattended.msfn.org/xp/applications/installshield.htm http://unattended.msfn.org/xp/applications/nsis.htm http://unattended.msfn.org/xp/applications/wininstall.htm http://unattended.msfn.org/xp/applications/wise.htm Then ask for the rest in the Application Switches forum or in this section...

I think they are having a mature conversation... I've seen worse recently

Conclusion added! B) THANK'S TO EVERYONE WHO PARTICIPATED

Thanks for the input. I think EasyBoot is displaying this text also when it cannot find the boot sector... I think the troubleshooting for this error is about the same, no matter where it is comming from. Anyway, I was just pointing the Attitude of the member, not the content

@un4given1 Since you have experimented a lot, can you tell me if it is simple to switch from an Unattended CD to a RIS method?

http://unattended.msfn.org/xp/reference.htm

@ankap thanks but your utility has to be present on the hard drive to be launched from GuiRunOnce. This is what I wanted to bypass... being able to launch my RunOnceEx.cmd on my CD directly from GuiRunOnce. For now this is what I am doing: 1) GuiRunOnce is launching Lancement.exe in my %windir%\Temp\ folder 2) Lancement.exe (.cmd converted) is scanning for the %CDROM% and then launching Installation.exe 3) Installation.exe (my RunOnceEx.cmd converted) is starting my applications installation 4) Installation.exe is launching Nettoyage.exe (cleanup.cmd converted) also located on my %CDROM%

Thank you guys for all your efforts! The only problem I have is that my .cmd will be converted to .exe and I cannot have any external file dependency... Anyway, I trully appreciate all your efforts! Thank's again

Thank you guys. Just to keep you informed, here is the latest developpement. I've been using kill.exe (same as taskkill but for Win2000) to remove Lancement.exe from the active process. This was a BAD idea. Since it was launched from GuiRunOnce in my winnt.sif, as soon as I killed this process, the desktop would load while my RunOnceEx was running... I also had another mixed issue with Adobe Reader 7 (read HERE) Then I tought it was because I converted my .cmd to .exe I wasn't able to delete my Install folder. It turns out that even with batch files the same will happen. From my understanding, if you are launching a batch file from %systemdrive%\Install\ the stuff is executed by Windows at that location. This is why I can't delete my Install folder properly. My Workaround for this is that I have changed the location of my Install folder. From now on, it is located inside %windir%\Temp\ so I don't mind if it stay there... Here is my event timeline: 1) GuiRunOnce is launching Lancement.exe in my %windir%\Temp\ folder 2) Lancement.exe (.cmd converted) is scanning for the %CDROM% and then launching Installation.exe 3) Installation.exe (my RunOnceEx.cmd converted) is starting my applications installation 4) Installation.exe is launching Nettoyage.exe (cleanup.cmd converted) also located on my %CDROM% Keep in mind that Windows is executing all theses .exe in my %windir%\Temp\Install so this is why I am not able to delete properly...

Great! Already 6 criticals update since SP2...

Interesting. Personnaly, I've joined the forum a bit less than a year ago. I didn't became an "active" member until this summer tought. Before I started posting, I've been reading a lot, experiencing, gaining knowledge and testing and I am quite satisfied with what I have accomplish so far. Speaking about the forum, I often see annoying things. First off, bad syntax. Even native English fellowmates are making a lot of mistakes, mispell words, use abbreviations making it difficult for other to read and understand. Second, bad formating. Everybody could use a little common sense to use appropriate bold, italic, colors, etc. Use the tools to make it easier to understand. Third, Provide enought details, add some screenshot. People are posting without reading what they have written. Often I am reading a post and until someone with more experience (like Alanoll or prathapml) is guessing what the question is, I won't fully understand what they are asking. Also, I have noticed some growing tension between certains members... I am not going to give names. Even myself had some difficulties while helping other, just take a look at this one: http://www.msfn.org/board/index.php?showtopic=34499 Well, that's my two cents.

Well, this is how MSFN is getting new members every days...

Really good! High Polygon count!

Nice guide but just for the records I'd like to warn everybody about modifying their I386 distribution folder. Many times, people come around and complain about trouble they have with their Unattended Setup. Messing up with the files in your I386 distribution folder WILL make troubleshooting harder. For instance: - Replacing or "updating" files (inf, dll, compressed cab, etc.) - Adding new files - Removing files for space saving (drivers, etc.) Please use extreme caution when doing this and keep a log of the changes you have made Only exception: svcpack folder svcpack.inf winnt.sif bootfix.bin (press any key to boot from cd...) LANG folder (remove if not needed) WIN9XMIG, WIN9XUPG and WINNTUPG (remove if not needed) You'll never know what could happen later and you should always keep your I386 distribution folder as genuine as possible.

It all depends on the code you are using to get your CD-ROM drive letter... In my example, I have to put %CDROM%\

No problem! Have you ever took a look at thoses files? Just change the extention to .txt and open them to reveal their mystical secret

Just a warning concerning the above method I mentionned, I had problems with MSN Messenger 6.2 and Symantec Antivirus Client 8.1 if I ran Acrobat Reader Installer silently straight with the original .exe BEFORE theses...

/passive /norestart /quiet

Odd... my install folder is still there even if it is empty now (I used kill.exe for Win2000 to terminate the Lancement.exe process) If I restart my cleanup.cmd again (2nd time) now it will be deleted Here is my cleanup.cmd: RD /S /Q "%AllUsersProfile%\Menu D‚marrer\Programmes\DivX" DEL "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\Ad-Aware SE Personal.lnk" DEL "%UserProfile%\Bureau\Connexion … Internet.lnk" DEL "%AllUsersProfile%\Menu D‚marrer\Programmes\D,marrage\Lancement rapide d'Adobe Reader.lnk" DEL "%AllUsersProfile%\Bureau\Adobe Reader 7.0.lnk" DEL "%AllUsersProfile%\Bureau\DivX Movies.lnk" DEL "%AllUsersProfile%\Bureau\DivX Player.lnk" DEL "%windir%\PnPdrvrs.exe" RD /S /Q "%windir%\PnPdrvrs\" RD /S /Q "%systemdrive%\í\" RD /S /Q "%systemdrive%\Intel\" RD /S /Q "%systemdrive%\install"

During my cleanup phase of my setup I have this last command: RD /S /Q "%systemdrive%\install\" Everything inside this folder get deleted properly EXCEPT for one file named Lancement.exe. I beleive it is not deleted because Windows think it is still in use. Is there a way to Force Delete this directory? EDIT: or maybe a way to force delete the file %systemdrive%\install\Lancement.exe

I turn out that the Hotfixe 823353 is messing up the IE6 entries in RunOnceEx and this was the reason of the HANG for me. When installing IE6, theses entry are added in RunOnceEx: Navigation Services Internet Tools System Services You must let them run BEFORE installing KB823353 otherwise it will halt @Bilou_Gateux Isn't it simpler to add these 2 exe in your $OEM$\$$\SYSTEM32 folder? This way you don't have to mess with the I386 source folder.

I was asked to put the year after the name of our departement in most of my creations... paperwork, etc.. It is just a standard format

Yeah... Sorry I omitted to mention I am using this wonderfull command: rundll32.exe iernonce.dll,RunOnceExProcess and you are right. If I don't use this command, the key will get executed at next reboot