Incroyable HULK

EDIT: we want names!

Humm a little extremist... but worth considering

@mrmark75 Even in a corporate invironement, I'm p*ssed off by the fact you cannot go to office update anymore... I've tried everything, there is some setting in the MST file but it didn't work. My solution for now is to use the regular content of the CD, make an MST file and then use a batch file to launch the installation of Office 2003 Unattended and SP1 right after. It runs just like a Hotfixe SP1.exe /Q:A /R:N

I think he is implying that for each Driver set, you don't need to specify the SubFolder if there is... If you want to test from VMware, just grab the drivers from my previous post: http://www.msfn.org/board/index.php?showtopic=36724 and don't specify the SubFolders...

Hum... it's worth a try. Have you checked if the same stuff apply for Windows XP SP1? I doubt everybody would have missed that for over 2 years...

From what I read, it doesn't sound like that. This will result in: You have to specify: No?

Same stuff. Just follow the guide http://unattended.msfn.org/ The only difference is the number of Critical Hotfixes required for SP1 (around 30) Only if you want to. There is some option about that in the winnt.sif file. Just follow the guide http://unattended.msfn.org/xp/reference.htm I'm not sure I fully understand your question but Windows installation is looking into \$OEM$\$1\Drivers\ and if it cannot find a suitable drivers, it will do just as usual (unknown device or Microsoft .cab drivers) Guess what? Just follow the guide http://unattended.msfn.org/xp/examples.htmNow, are you gonna take a look at the guide BEFORE posting anything else?

For DirectX 9.0c, you have to download this version: http://www.microsoft.com/downloads/details...&DisplayLang=en For KB8324873 you must use the following syntax in svcpack.inf: "KB832483.exe /C:""dahotfix.exe /q /n"" /q:a" otherwise you can install from RunOnceEx but the syntax is a bit different...

I am using the date present on the Download page of the Microsoft Website... perhaps I didn't notice some of them were from 2003.

So if I understand correctly, you just renamed you winnt.sif to anything as long as the extension is .txt ? So I can rename to linux.txt and it will work? EDIT: there is already 3 .txt files in the i386 folder. EULA.TXT, SETUPACC.TXT and UNATTEND.TXT which already contain some tags!

There is a little "bonus" with my method. You can boot directly in the Full or Safe mode (1 floppy image each) without having another menu before (Acronis menu) With EasyBoot, you can put the Floppy images files where you want on your cd, just use the following to navigate to the folder you want with this command: cd /;cd EZBOOT;cd UTIL;cd DISK;run ACRONIS.IMG

I use a combination of both for our organisation (500 to 1000 users)

You can also build some Floppy Image of your Acronis Product Here is my current method: 1) Start Acronis Media Builder and insert your first empty floppy. Let the media builder finish the first diskette and copy the files from the floppy drive to a temporary folder named SOURCE. The thing you will notice is that Windows still have those files in memory so there is no actual reading of the floppy! Ultra reliable and fast! 2) Do the same for the rest of the floppy required for you Acronis product. 3) Use EasyBoot to create a floppy image of the FIRST diskette 4) Use EasyBoot to create a floppy image to the size required by the number of diskettes and use the floppy image you created at step 3 as the SEED image. 5) Open this new oversized floppy image (empty) with WinImage 6) use the INJECT option and add all the files from the SOURCE folder 7) save that's it! No more tampering with diskettes. So far I've created all the floppy image for Disk Director Suite 9 and True Image 8 Corporate Workstation (total 6 images) without a hitch! P.S. I think this technique will also work with any utility which create boot diskettes like Hard Disk Drive Diagnostic, etc...

It seems possible to get the drivers for MS Virtual PC 2004 as well but I'm not sure which files are required. They are located here: Program Files\Microsoft Virtual PC\Virtual Machine Additions\VMAdditions.iso

There is a new feature which looks promising... Capture Movie! VMware can generate a video of the virtual machine! Perfect for teaching purpose and for newbies purpose The only thing is that they introduced a new codec (VMnc) for this... so I'll have to convert the AVI to something else.

yeah, I've tried and this is what I get:

I just started a new topic where you can download the drivers: http://www.msfn.org/board/index.php?showtopic=36724

Since a lot of us are using VMware workstation to test their unattended installation, I am providing the necessary drivers for the "virtual" hardware. The benefit is that you can test the driver installation process and your virtual machine is fully functionnal upon completion. Just download, extract to your $OEM$\$1\Drivers folder and add the following to your winnt.sif [Unattended] OemPnPDriversPath="Drivers\VMware\hgfs\win2k;Drivers\VMware\memctl;Drivers\VMware\mouse; Drivers\VMware\scsi;Drivers\VMware\video;Drivers\VMware\vmxnet" EDIT: I had to break the code in 2 lines so make sure there is no space or line break in your code You can also put all the drivers files in the VMware directory and just add this to winnt.sif: [Unattended] OemPnPDriversPath="Drivers\VMware" I must thank prathapml for giving me this tip! VMware.exe

This is happening because you don't have the video driver installed. You can add the VMware drivers to your Unattended CD just as regular one Extract the 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!

Yes, if you followed the "official" guide, the RunOnceEx process will be executed at the second reboot of the installation process (also known as first Logon) just before you get to the desktop. The RunOnceEx process is designed to add the execution key and they get executed after a reboot. In the guide, cmdlines.txt is calling your RunOnceEx.cmd at stage T-12 so the entry get parsed and at the next reboot they get executed. If you want to execute the RunOnceEx process right away without any reboot, just add this line at the bottom of you command file: rundll32.exe iernonce.dll,RunOnceExProcess

One way of doing it is to go into Display Property where you can ajust the Wallpaper, Screensaver, etc. Return to the Theme tab and select Save as... Next, put this custom .theme file in $OEM$\$$\Resources\Themes Also, add your background image in $OEM$\$$\Web\Wallpaper Next you'll add this to your Winnt.sif [Shell] CustomDefaultThemeFile="%WinDir%\Resources\Themes\xxx.theme"

Yes, you have to remove BOOTFIX.BIN if you don't want to have to press a key

I'm not into it right now me either but I am planning to dig that in the next week or so... The thing that I find interesting with Webmedic suggestion is that you can run the services on a Linux/Unix machine.

Yes, but you'll have to wait to the first reboot to change that the boot sequence in the BIOS... OR If you don't have anything on the Hard Drive, you could put the Hard Drive First and CD-ROM as second so the first time it would boot on the CD-ROM and after the first reboot of the installation it would go on the hard drive... OR In modern BIOS, you can hit a key during the post (like F11 on MSI) and it will bring a small menu letting you choose from wich device you want to boot. The fun thing is that this is only temporary, nothing is changed in the BIOS so the next time you boot, it will use the BIOS setting unless you hit F11 again...

This is an interesting question. I've run into some old but also newer computer which didn't want to boot from a CD... I am looking into it and I'll get back to you if I find something...