prathapml

Oh well, the update doesn't have a patch within the package. Its a direct installer. Anyway, here's what you can do: 1. Start the original Acrobat 6.0.1 setup. 2. It will de-compress itself from the FEAD optimizer 3. Look in "C:\Windows\Cache" for the installer with MSI. 4. Open a command-window into that folder, and run the main MSI with the "/A" switch to make an admin-install point folder. 5. Copy away that folder safely, and install from there. 6. Download the 6.0.2 update, and start the setup, but don't click "Next". 7. Look in the folder "C:\Documents and Settings\UserName\Local Settings\Temp\_is---" to get the extracted update. 8. Now keep both the admin-install and the update in one folder. 9. SFX them to extract silently to a folder of your choice. 10.Have your unattended scripts run both (the main+update) the MSIs with the /QB switch. The total time-saved during uA setup = 2 mins. Space saved on CD = 10 MB.

A version of Acrobat Reader which already is at v6.0.2 is up here : latest That one is for non-International English versions. To have a pre-updated distribution of the new version, without having to do two installs, see this thread: Acrobat 6.0.2

Acrobat 6.0.2 having an updated installer is an ongoing process there currently. I believe the newer version of yahoo Msgr with all the same things as you mention is here: http://download.yahoo.com/dl/installs/ymsgr/ymsgr_1750.exe

You can do precisely that with AR-Speedup available for download here.The Windows-English update from 6.0.1 to 6.0.2 is here. Since there isn't a direct 6.0.2 installer for all languages yet, I'll see if I can patch the original 6.0.1 MSI with the new MSP from the update (if exists). If I succeed, I'll post the how-to here.

Downloaded the infs, let me see if I can get those working.....

Please don't just add in posts to an existing thread...... Only replies to a previous post are normally posted in a running topic (such as this). You can start a new topic and post your batch-file - that way lots more people will see it, otherwise, most will simply skip reading a thread that they've already seen.

Hey, being rude to people isn't nice you know..... @evilvoice Yup! you got one interested taker here (meeee). Please go ahead and post that.

Please post any commands or code like the above from your RunOnce into code blocks (like ). That makes it easier to see where your description ends and code starts.

Well, a slight bit of searching right there would have helped:BOCHS That one is free and open-source. BOCHS is a true emulator, so it is painfully slow - but yes, its there for those who want it. Not remotely as easy nor as powerful as the top 2 Virtual simulation apps.

Since an admin-install point has the advantage of files already being placed in the right directory structures (extracted from the single setup.exe), installs happen a bit faster as well.......

Just a suggestion - when you get the FULL installer (15 MB or so..), make an administrative install point of it. Run the installer exe with the "/A" switch, (for an administrative install) and the resulting files will be a lot bigger, but make an SFX of it - 15 MB installer ends up being 7.8 MB (with winrar, didn't try 7zip).

Here's a guide which explains in detail, step-by-step to make a multi-boot CD: http://flyakite.msfnhosting.com/

If you need to be able to use the "EXPAND" command in a recovery console, you'd put that executable (EXPAND.exe and any DLLs for it) into your appropriate boot folder. I for one, have the console version of "rar32.exe" also in my boot (or PRO1 folder, as you may better know it) so that I can extract from compressed RAR/ZIP files. I'd like to know what other items you have placed in there - basically, what are the tools that you place there for your use?

Could you please describe what needs to be edited to do so? And whether the netfx folder can be left in CMPNENTS folder to do this, or should the files in it be moved into I386?

Nero Vision Express is pretty good, and sells for a lower price - with a CD-writing software bundled.

There were reports recently that applications compiled for .NET framework 1.1 (VS.NET 2003) weren't running exactly as they should on XP with SP2, while they ran fine with SP1. But I haven't come across such a thing yet. Can anyone else confirm this? (whether you have any .NET problems on XPSP2) There's not any info of this bug existing nor being fixed in the List of fixes included in Windows XP Service Pack 2.

Thanks for the heads-up. Downloading now... This one will be of interest to those making multi-boot CDs of WXP as well, they are spared some effort now in updating the BOOT folder.

If you use unattended setup, you can't use mass-storage-drivers (SATA/RAID) from floppy. If you want to use the floppy, you can't have it unattended. The solution is to integrate text-mode drivers into the OEM list. Look here for details: RAID/SATA drivers

Nice utility you have here.... Keep up the good work.

That's cool! You found the solution. It does look like windows does not like to create a hiberfil.sys of 1 GB. Do try hibernating again after removing one module.

Just open a CMD window, and type the command "SET" to get a list of all environment variables supported. Wrap each of those variables with the "%" sign to be used wherever necessary.

Your previous config (the 1st one) will be pretty good for Doom3 - a review here says: But the second config you mention will run it well, without having to forgo any of the eye-candy Doom3 provides.

The standard way to do a backup copy of an OS CD is: 1. Make a CD-image from the CD in the drive (using UltraISO/WinISO/ISObuster/Nero/whatever). 2. Use an ISO-image editing tools to extract all files from the iso into a folder. 3. Save the boot-sector of the ISO the same way. 4. Now make any modifications you need to do, and work the same backwards, and burn the ISO-image to CD. Please note that making a copy of a CD, for other than backup purposes is not permitted under most EULAs.

Testing your drivers _is_ a bit painful if you're only testing on a Vitual Machine (VM). But you can still integrate the VM's drivers and test it that way. Your real hardware drivers will only be tested once you do it on a real machine - only then you get to find out errors with the real drivers, if any. Nothing really, which can be done about it. Try using a CD-RW for your uA testing, and a different partition, than your currently occupied one.

Thanks for finding that article Alanoll. So now I see that the keys on that page are different from the ones found in the unattend.txt we were talking about.... Probably this is a different set of keys for the same purpose as mentioned there, or these new keys replace the ones in that technet article. Would sure help if MS sent Paul Thurrott a reply sooner with regard to this.... Anybody else fetched further info?