Incroyable HULK

1) Let me say it again (3rd time ) 2) About Media Player, It would be too much trouble listing all the exceptions for IE6, Media Player and DirectX if you choose NOT to upgrade theses. It is up to you to do the searching and beside I don't think there is any issues when installing updates even when they are not needed... -------------------------------------------------------------------------------------- MS WINDOWS 2000 PRO SP4 - (31) WITH Internet Explorer 6 & Windows Media Player 9 & DirectX 9.0c installed 3) Welcome to the Forum!

What the ?.....? ... ?

I think you can do it with AutoIT... you just have to specify the icon you want for your package.

Yes you can extract VMware drivers in the ISO you will find installed in the WMware Program folder: Program Files\VMware\VMware Workstation\windows.iso Open the ISO file and extract the drivers you will find here: CD\program files\VMware\VMware Tools\Drivers Thanks to prathapml for pointing that out to me!

Since you are not looking for a Multiboot CD, all you have to do is follow the guide: http://unattended.msfn.org/

This has already been discussed here: http://www.msfn.org/board/index.php?showtopic=30179&st=10 and http://www.msfn.org/board/index.php?showto...unOnceExProcess PLEASE USE THE CODE TAG WHEN POSTING CODE!

REMOVE THIS: start /wait rundll32.exe iernonce.dll,RunOnceExProcess this is launching the RunOnceEx process immediatly!

Frankly, I think it is a too long shot. I would suggest you use EasyBoot because anyway, you might wanna add some other stuff to boot from your CD one of theses days...

I don't know where you could insert this one without going for a third party utility... the relationship of the boot sequence is the following in Microsoft products: boot.bin - setupldr.bin - bootfix.bin When we are working our Multiboot CD, we have to HEX EDIT the boot.bin and setupldr.bin because we are changing the folder structure (change i386 to XPEN for example...)

This will mostly happen when there is no proper display driver installed for your video card (when you have the default Microsoft Video Card driver...) So in order to work, you have to provide the correct driver for your video card using the Unattended Guide... $OEM$ folder + entries in winnt.sif

Bootfix.bin is the file you have to remove if you don't want setup to ask: Press any key to boot from CD... What you are asking is the opposite. I would recommend you use EasyBoot because it has the ability to build a boot menu but also to add a timer function so if nothing is done (no mouse movement, or keystroke) it will automaticaly go to the option you have defined (mostly used to continue the boot sequence to the hard drive...) You can get a trial version on the website http://www.ezbsystems.com

Or... even better you can build a multiboot CD and add a second boot folder without a winnt.sif so you can do a "regular" installation when you need it!

I've seen somewhere that qchain.exe is no longer required for Windows XP SP2...

Yep! I beleive you got the optimise option turned on with the smallest ISO...

As long as you use the /integrate: option, you don't have to do anything else... that's the purpose of this switche

mostly just "put" the hotfixe in the right place and add the correct entry under svcpack.inf. I you want an"integration" of the hotfixes in your distribution, you'll have to use some utilities...

If you use the /integrate: switch you will notice that the KBxxx.exe get copied over to the svcpack folder (inside I386) so you can execute the exe anywhere you want on your computer. You'll have to do this command on your distribution folder. I wouldn't recommend you do this on the ISO

OK! got it now! I turn out that the Hotfixe 823353 is messing up the IE6 entries in RunOnceEx !!! I had to build a lot of simulations to isolate this one! IE6 is NOT the cause of the RunOnceEx hang So here is my current working method (keep in mind it is for Win2000 SP4): cmdlines.txt [Commands] ".\GDITool.cmd" ".\ie6.bat" ".\wmp.bat" ".\Hotfixes.cmd" ".\RunOnceEx.cmd" GDITool.cmd is a simple registry entry for the annoying KB873374 IE6, WMP and the Hotfixes could also be done with svcpack.inf Remember you have to put REG.EXE in SYSTEM32 in order to use RunOnceEx.cmd: cmdow @ /HID @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Your Title" /f REG ADD %KEY%\zz01 /VE /D "Installation de DirectX 9.0c" /f REG ADD %KEY%\zz01 /V 1 /D "%systemdrive%\install\Applications\directx\dxsetup.exe /silent" /f Your Software... REG ADD %KEY%\zz10 /VE /D "Microsoft Hotfixes" /f REG ADD %KEY%\zz10 /V 1 /D "%systemdrive%\install\hotfixes\KB814078.exe /Q:A /R:N" /f REG ADD %KEY%\zz10 /V 2 /D "%systemdrive%\install\hotfixes\KB823353.exe /Q:A /R:N" /f REG ADD %KEY%\zz11 /VE /D "Computer will Reboot in 2 minutes/f REG ADD %KEY%\zz11 /V 1 /D "%systemdrive%\install\cleanup.cmd" /f EXIT KB814078 and KB823353 are the only Hotfixes that must be done here. Also I am using zz01 to zz11 just to make sure that the stuff IE6 is adding to RunOnceEx is Executed First. So now I have to find a solution to the QuickTime error... and something to replace this ugly shutdown.exe

@DLF I agree with that... If you are like me, you don't like to depend on utilities to get the job done Not that I don't like all thoses utilities available around but I prefer to know everything that is happening in my Unattended Setup and I don't want to mess with the I386 folder unless absolutely necessary. Anyway, your request is propably under way right now. If you look at the Sticky, there is a topic regarding the complete rewriting of the guide...

Well for now you can use my Sticky: Sticky: HOTFIXES: Win2000 SP4 – WinXP SP1 – WinXP SP2

the $OEM$ folder ALWAYS get copied over from the CD to the Hard drive if you have specified this in you Winnt.sif: [Unattended] OemPreinstall=Yes Even if you are not going Unattended and you have the $OEM$ folder parallel to your I386 folder, cmdlines.txt (at the root of $OEM$) will get parsed! (even if the files aren't copied over to the hard drive)

I wasn't on the forum after 5:00PM (Christmas Party) but I'm glad you finally made it according to my reading in this topic: HERE BUT THIS IS ALL YOUR FAULT BUDDY! If you have followed the instruction to the letter it would have worked a lot easier for you and NEVER BLAME OTHERS FOR YOUR FAILURE! I think I would be appropriate for you to EXCUSE YOURSELF I had enough, this will be reported to the forum admin...

@sdennis91 Sorry to tell you this but I warned you about this in the topic you posted yesterday! And as Alanoll said, everything is detailled in the guide... Go see what I think about your attitude in your original post HERE

It seems to me that you are giving up too fast! Please provide us more details and only go one step at a time then test every step to make sure everything is working fine. We'll help you if you provide enough details... P.S. I always use EasyBoot to edit my .BIN files and it works like a charm

2 more things, If you want to go Unattended, you'll have to move your Winnt.sif inside I386 to your newly created boot folder. Next, if you have some problems during the Windows Installation I suggest you use this method to obtain you boot folder: http://flyakite.msfnhosting.com/xpprosp1.htm This one saved me because my installation are in French and Setup was complaining about missing files. But if you are using an English version, the method used in EasyBoot (wxp.bat) should work perfectly to provide your boot folder EDIT: This is a Real Crash Course!!!