big poppa pump

http://unattended.msfn.org/

****! I was cutting up some okra for frying when I was typing this message!!! I meant ORCA!!!

Try using wininstall or okra to edit the installer.

I had the same problem with SAV 10. I think its the spyware scan engine with this version. I was surprised when I did my unattended install and found that DAP was not installed. I finally realized that SAV was cleaning out the entire DAP directory in Program Files the moment it is installed. FTM, I have got rid of SAV10 and sticking with SAV 9. Too many things wrong with SAV 10 if you ask me.

what????

Brilliant first post!!!

Search the forums for silent installations of msi based programs!!!

And none of them are going to have one till the time nvidia releases an official set of drivrs for the x64 edition. However......there are other ways around!!!

None of these beta drivers are going to work since none of them are whql and have a valid cat file. XP64 already comes with built in support for nvidia nforce3 support. These drivers will be given preference no matter which beta drives you use. The only way to get around this and do a proper install is to either have drivers that are whql'd or hack files in x64 that disables the built-in nforce3 support and thus the installation starts looking for the drivers at an alternative location.

Search google for a program called filedisk!

Finally slipstreamed all drivers and typing this off a successful installation of an unattended xp64 cd on a raid 0 partition. Mobo is MSI Neo2 NF3 and I used exactly the same method as I did for my earlier 32bit installations.

This method is not going to work unless the update.ver file in the update directory which has the md5 checksum for the shell32.dll files is edited. Anyway I solved this problem and I already have kb890047 installed on my computer with the hacked shell32.dll file. I opened the update.ver file in the update directory using notedpad and deleted the last 2 lines which tells update.exe the md5 checksum for the shell32.dll files. Replaced the shell32.dll file in both the sp2gdr and sp2qfe with the modified shell32.dll file. My size of my file increased from 8.05mb to 28.8mb after all the hacking and modifications to it. Ran modifype on this file. Ran update.exe from the hotfix/update folder and the update installed without a hitch and then rebooted and checked windows update. WU shows the hotfix already installed on my system. BTW it took me less than 5 minutes to hack shell32.dll, not really a pain in the a$$. I used Restorator 2004 and mass copied the entire AVI, BMP, and icon resources from my old file to the new one.

And thats exactly what he was talking about. Removing programs from windows startup is basically deleting entries from your registry. For that matter a simple search in google will tell you how to delete registry keys with a registry file. The registry file is applied the same way as all other registry file in the unattended method.

WOW! Talk about PMS!

No Way, I want results... After 4 days searching this forum... You wasting my time... Please No time waster's <{POST_SNAPBACK}> Stop wasting our time instead. If you want results search and you will have it! This topic has been covered numerous times in this forum.

It can be done. I use total commander XP if I want to change all file names to lowercase or upcase!

Video drivers will not be installed in Virtual PC!

Search the forums! There are previous topics existing on printer installs.

Search! It's already been posted.

Leave it alone and the message will disappear after 30 seconds. I have learnt to live with it. This is basically something to do with SP2.

People will help. But in order to help you, you have to help yourself first. You need to know and comprehed the basic commandments of the UA CD before doing anything at all. And you think all the people who have done their UA cd havent done that. I myself have spent over 100 actual cds and prolly 4 times that number in rebuilding and installing windows on virtual pc. This is not something that you are going to do or finish overnight on a week. Some of us have been working and improving our UA for over a year now. I myself started over a year back and am still working on it, adding stuff, removing entries, enhancements etc.... The only way you are going to learn properly is by doing numerous installations (what you call wasting time) and learning from your mistakes.

I cant do that. it takes half an hour to put it back to together and then 2 stupied hours to reinstall. but i think i am starting to understand I put the code in my .sif file? If so where in that file do i put it? You cant expect everything to be handed over to you in a silver platter. Read and try to understand! If you cant then read it again. You have to get the basics right before you do anything else.

For F*** sake! Its not a directory. Its a registry key!

The instructions posted over there cant get any simpler that that. You need to put more effort from your part to get what you want. You just cant expect everything to be spoon-fed to you. Read some additional topics posted in here and familiarize yourself with the driver integration process. Try it on your own, see what happens, see what works and what doesn't. Once you know what works and what doesnt, post your questions about the parts that dont work and how exactly it doesnt work.