Cee-Kay

Thank you for the offer it's much appreciated, as soon as I make the download availabile, everyone is certainly welcome to test the heck out of it. Obviously, I hope the installer to be as error-free and possibile, but having as many testers as possibile would certainly help speed up the process of ironing out any bugs that may still exist.

I'm currently working on a modified MSI installer, which will allow the newer LiveUpdate files (2.5) to be used instead of the older LU files included with the actual product. Upon completion of the installer, I will test it as much as possibile before releasing it -- in the meantime if anyone wouldn't mind testing my installer once I release it, that would be a great help, just incase I've missed anything out (e.g. a customised install, installation on a server, etc). EDIT: I have now finished work on my modified MSI installer and I am currently in the process of creating a guide for integrating LiveUpdate v2.5 into the SAV V9.0 install source. Updates will follow...

By the looks of it, you are receiving that error message because the exact filename of the patch file hasn't been specified. Upon looking at the extracted patch file, I have discovered an extra space at the end of the file name (just before the .MSP extension). Therefore, you can either rename the file and remove the extra space (meaning the command you entered on the Screenshot would work) alternatively enter the command, which I put in my previous post. You should then find the patch works ok.

Adding to prathapml's solution... When creating the SFX Archive using WinRAR enable the option 'Create solid archive' as well as setting the 'Compression method' to Best. This will reduce the file size as much as possibile, without removing any files. To configure the SFX options (assuming the Create SFX Option is enabled): Goto the Advanced tab > SFX Options... Here is a quick discription of the functions you may need: General: Specify a program to be run before and/or after extraction e.g. "Setup.exe /silent /noreboot /no_ui /sn=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX /write_sn" (Recommended). Modes: Allows extraction to a temporary folder (Recommended) Allows you control the level of Silent-ness (If there's such a word ) (Recommeded). Text and icon: Customize the SFX icon.

Don't be silly, were all here to help one another out. In order for us to make the appropiate suggestions, can I confirm what stages you have already completed: You copied the contents of the CD to "C:\Documents and ettings\jfmccord\Desktop\SAV Corporate Edition 9.0" From there you created an admin install point using "Setup.exe /A". In the install point itself, you extracted the newer Virus Definitions files to "C:\Documents and Settings\jfmccord\Desktop\New Install\program files\Symantec AntiVirus\Virus Defs" replacing the existing files and are stuck at the part of integrating the patch? If it's just the patch stage, you have done most of the hard work, you simply need to extract the patch from the zip file to the root of your install point, in your case it seems to be "..\New Install" in that folder you should have 7 sub-directories and the installer itself with a .MSI extension as far as I can remember it's called "Symantec AntiVirus.msi". Now all you have left to do is navigate to the root of your install point and run the command kindly provided by prathapml which is as follows: msiexec /p "SAVCE_9.0.0.1400_AllWin_EN .msp" /a "Symantec AntiVirus.msi" /QB Braking the command down, the first filename is the name of the patch file, with an .MSP extension. The second of course is the filename of the MSI installer mentioned earlier. Note: Although there is a space between EN and .msp the above command does work provided the correct filenames are mentioned. If you have not renamed any of the above files the command will work fine, if not simply replace the filename with the ones that you are using. I hope this solves your problem.

Thanks in advance for the guide Felix, having just finished following your guide, it certainly looks like you've spent a lot of time and effort creating it. I'll post again with my findings after running my next unattended install, but im pretty confident that everything will work as planned; thanks again.

Unfortunately people reported problems with that method so I removed the file from my FTP server. I'm currently working on a alternative solution.

Thanks for the words of advice, however the solution that I posted worked twice for me on a clean installation of Windows. Sorry if this didn't work for you, at least I suggested a possibile solution! It is easy to be judgemental and negative, perhaps Ill just spectate in future, and leave the forum to you guys.

I have a custom-made AutoIt script if anyone is interested?

EDIT: Please view my latest post on page 9, where you can download the modified MSI installer for integrating LiveUpdate v2.5 Thanks.

Hey Alanoll... Had a few problems with some options not installing when they should of, but changing the MSI for your latest release solved all my problems! A big thanks for all the effort you made in putting this useful installer together.

Just a quick suggestion -- I'm not sure how practical it is or the limitation(s) of not using an access database file, but you may be able to contain the database in an alternative format for example a flat-file like a .CSV file (Comma Seperated Values) .XML or a .TXT file perhaps? Obviously, it's just a suggestion and an idea that came off the top of my head, but it may help get around the problem or spark an alternative solution.

Just a quick message eagle00789, I think it's a great idea that you created this utility, so well done for the progress you've made so far! (I wish I was more programmer than technical support, then I might of been able to help in some way) Anyway back to the subject... I received the following error when choosing the option to add from the database (A screenshot of the error is included). Best of luck with your project.

Boy that is some list in deed! Way to go MS for putting peeps off in installing their 'baby' project, which has cost them so much human resources and money to put together. It's rather off putting considering i'm putting my finishing touches to my slipstreamed XP SP2 CD. What does everyone else think?

576/288 for me, although I'm supposed to connect at 512/256

I don't know if this helps, but I always install Nero from the latest update without installing v6 and then applying the update seperately, and it works fine for me. I haven't tried it on SP2 RTM, since I don't have a copy as of yet but I don't experience any problems on the copy of SP2 RC2 im currently running

Thanks mate, much appreciated

An alternative method to delete the pesky Alcohol shortcut (and others like it) would be: Del "%systemdrive%\Documents and Settings\All Users\Desktop\Alcohol 120*.lnk" This was the first workaround I thought of, since all my shortcuts were getting deleted as expected, except Alcohol 120%. This method works for all the usual commands (as far as I know) including copying, moving, renaming etc. as you can use the '*' to represent where the filename differs. For example to delete Filename001.txt, Filename002.doc and Filename003.jpg you could use... Del "[File Path]\Filename***.***" This would delete all three forementioned filenames in one hit. I hope you guys find this information useful.

[Display] BitsPerPel=32 Xresolution=1024 YResolution=768 Vrefresh=85 Seems to me that including those commands in 'Winnt.sif' doesn't always work for some people. I play it safe and use both methods just to be doubly sure, if the 'Winnt.sif' method doesn't work then I know the 2nd option will.

Seems ok to me, just ensure that the program is in \$OEM$\... not \$OEM\... as you had previously typed, if it was a typo I apologise Your command will work fine -- the only reason I put it in prepare.cmd is because I have other commands to be carried out (e.g. deleting shortcuts) before installing my applications, it also helps keep things neat and tidy.

If you add the following into your 'Winnt.sif' this should help you... [UserData] ComputerName=* According to the Setup Manager, (a wizard-based program for creating answer files) this does the following... Of course it is reffering to what you put in on a previous page of that wizard, but it also rings true for when you are setting up/installing Windows. I hope this helps you

Since I had a similar problem, with the menu being too big this may help you... Goto http://unattended.msfn.org/xp/downloads.htm and download the bottom utility named 'Video Resolution Changer'. Follow the instructions on that page and copy the exe to the ..\$OEM$\$$\System32 folder Copy the usage command on the page and include it in one of your batch files, I recommend you include it in Prepare.cmd Now what will happen (fingers crossed!) is when Windows starts it will display the menu, run all the commands in Prepare.cmd and change your screen resolution to whatever you changed the usage command to. Sorted (I appologise if you did actually want it in two windows etc, but this method worked ok for me!)

Thanks, I understand enough to of your script to see how AutoIT interacts with certain objects. I tried that for the screens preceeding the 'Install' button and I did notice a slight delay, however the script seems to close when it reaches the screen with the 'Install' button (this happens both when I use the Sleep command and when I don't) Using the AutoIT Spy it lists the 'Install' button as: Class: TButton7 Text: Next > Despite the caption being 'Install' would/does this make any difference or am I missing some commands from my script as you said your script is not complete?

Thanks ZoSTeR for the script I had never heard of AutoIT before finding this thread! Most of the script works fine, but I seem to experiencing problems with the 'Install' button Despite copying your script and configuring the specific options, I can't get it to automatically click the 'Install' button -- is this by design? I would also like to configure the plug-ins settings, I take it I am able to do this just like the other checkbox options as per your script?