MHz

Sorry about the late reply but the board did not send me an email notifying of your PM. I have replied to your PM. Logging can be done.

Hmm, I have my email down to 30MB after a cleanup. Since these emails seem important, then I would consider breaking up the database file first. You should be able to create some more folders within Outlook. Name them as suitable. Even something simple like Friends, Family, Business etc would be good but more descriptive, the better for searching purposes. Then create some message rules so mail from say a member of your family goes to your Family folder. I am currently using Windows Mail within Vista so I can at the moment relate to that. It is possible to execute the message rules on a chosen folder in the email program. The email will be moved as the conditions of the message rules state. Once your email is all moved to other folders by the message rules, then the database files will be multiple database files of a smaller size, rather then your large 1.9 GB. I would consider that your amount of mail is still too large to continue adding to, so perhaps you could make some folders with similar names on your Hard Drive somewhere and then select all mail in the select email folder and drag the mail into the corresponding folder on your Hard Drive so you will end up with <subject>.eml files in the folder. Do that with all the other email folders. If your happy with the result, then you can clean out your email folders completely within your email program and start fresh again. If your folder names were informative enough then finding old emails should not be any more differcult perhaps.

Example with 3 options ready for use. Uncomment only 1 option at a time to see the example. Opt('TrayIconDebug', 1) ; Check if "Installer Language" window appears. AdlibEnable('function') ; Run the installer. $ProcessID = Run('"' & @ScriptDir & '\CCleaner 1.41.exe"') If WinWait('CCleaner v1.41 Setup', 'Welcome to the CCleaner', 60) Then ; Option 1. Move window off the screen ;WinMove('CCleaner v1.41 Setup', 'Welcome to the CCleaner', Default, @DesktopWidth) ; Option 2. Set window transparent. ;WinSetTrans('CCleaner v1.41 Setup', 'Welcome to the CCleaner', 25) ; Option 3. Set window minimized. ;WinSetState('CCleaner v1.41 Setup', 'Welcome to the CCleaner', @SW_MINIMIZE) ; Click the Next button ControlClick('CCleaner v1.41 Setup', 'Welcome to the CCleaner', 'Button2'); Next ; Disable "Installer Language" window checking AdlibDisable() WinWait('CCleaner v1.41 Setup', 'Licence Agreement') ControlClick('CCleaner v1.41 Setup', 'Licence Agreement', 'Button2'); I Agree WinWait('CCleaner v1.41 Setup', 'Choose Install Location') ControlClick('CCleaner v1.41 Setup', 'Choose Install Location', 'Button2'); Next WinWait('CCleaner v1.41 Setup', 'Install Options') ControlClick('CCleaner v1.41 Setup', 'Install Options', 'Button2'); Install WinWait('CCleaner v1.41 Setup', 'Completing the CCleaner') ControlClick('CCleaner v1.41 Setup', 'Completing the CCleaner', 'Button2'); Finish EndIf ProcessWaitClose($ProcessID) Exit Func OnAutoItStart() ; A 2nd script instance will exit. If WinExists(@ScriptName & '_Interpreter') Then Exit AutoItWinSetTitle(@ScriptName & '_Interpreter') EndFunc Func function() ; Check for a window that may appear. If WinExists('Installer Language', 'Please select a language') Then ControlClick('Installer Language', 'Please select a language', 'Button1'); OK EndIf EndFunc Based on the lite version of CCleaner.

There is a external database viewer available that I have seen and used before on the net so you can look at your emails without opening the email program to do so. 10k emails is a lot and deleting would take forever to go through them so just copying the file to backup and delete all emails within the existing email folder should be fine. And do maintenance to shrink the file down to optimize.

AFAIK, yes. That is launching an AutoIt script from a extracted cab file will work fine. Some installers allow you to minimize the 1st window and the following windows will also be minimized. You also maybe able to move the 1st window off screen and automate from there. WinSetTrans() can also be used to make the windows transparent if you like. Using WinWait() and Control*() functions allow for very relible installs and windows do not need to be active so you can even use a full screen picture set Always on top will installations happen so it is all hidden.

Sorry. Just noticed that the cab file has a MSI inside. Installing it is hopeless if your MSI installation data in the registry is corrupt to start with. Try extracting this zip archive and run msicuu.exe. msicuu.zip Edit: I sent some feedback on the link that i previously gave you.

Use the Windows Install Cleanup Utility to fix the issue.

The author is here. The AutoIt script I created is made to be executed at cmdlines.txt or at a similar time period and will add a runonce entry in to execute from registry if a exitcode of 2 is returned from the DT install. The script is self contained to only require the DT installer alone without any other files.

You can call CMenu.exe via command line, but you would only invoke the Gui "Identify Installer". I could create a modification to a special executable to allow this, to pass a command line and to execute the path of the file with suitable switches, but you may miss out on the files that cannot be recognized though. Let me know if you want to continue with this and I may see if I can create a prototype for you to try out.

Solid advice? Well aren't you confident. You put down my offering with disrespect by putting down AutoIt and then boosted your own choice. I will not say anything bad about your choice as it is good choice also. You are certainly not a nice person at all. The only thing you have is a pathetic opinion as you cannot use a language that works. Go to the AutoIt forum and you will find plenty who love and support using AutoIt. There are plenty of AutoIt users at MSFN also who do not expose there use of it. They quietly use AutoIt without putting down others who use other languages like you. So you think it is fine to go around spreading your opinion and putting down others and what they use. Why don't you go down to the local police station and tell them that they suck. I am sure they will sort you out good and convince you to keep your pathetic opinions to yourself.

There is NOTHING in the unattended installation world that AutoIt cannot accomplish. You just need a willingness to learn. Thanks. @#rootworm Your words were not required and plain disrespectful.

Probably Inno Setup as latest I have of that date. Try these switches /Sp- /NoRestart /VerySilent /SuppressMsgBoxes The /VerySilent is the important switch and the others are in case of optional events set by the installation developer which I use for all Inno Setup installations.

You never mentioned whether your company needs .net 1.1. .net3 is the choice now which does .net2 and .net3 programs. Unless the dependency requires 1.1, then I would omit it and just do version 3.0.

Surely not. In the command line, you use zip sfx switches after a extracted msi. Seems like a poor setup routine to me (by the developer) but just my opinion. Perhaps I am wrong. Edit: added words within brackets.

Totally free to use. *** Link ***

Updated to version 1.4. Please see 1st post for details and the link to the download.

From memory, your path in your project should be like this. \$OEM$\$1\Install\... Double check that you have not made a typo in the path and Winnit.sif. If your using W2k then I am fairly sure that you need to put the $OEM$ folder inside the I386 folder, else it goes beside the I386 folder for XP.

IMO, Yes. The compiled AutoIt executable should function normal under the condition of extracted from an nLite add on. The macro, @ScriptDir, is the path to your compiled AutoIt executable so you can set the WorkingDir or path if needed. It will run Msiexec fine and all the rest. Even the AutoIt Gui functions should work fine around the early T13 period.

I'm not a nLite addons experienced, but if you remove the space from the path to the files and have no spaces in the filename, then you do not need the double quotes. For the 7Zip, you just need no spaces in the filename and the easiest way is to replace spaces with underscore characters. So a 7Zip config.txt would look like the below code. ;!@Install@!UTF-8! RunProgram="PrintKey2000_Setup.exe /s" ;!@InstallEnd@! This thread below may have some good tips. http://www.msfn.org/board/lofiversion/index.php/t39048.html

Don't worry too much about the links as I can Google when needed. urie is correct about the case of the characters as NSIS is case sensitive with it's switches, so uppercase is definitely needed. Identify Installer mentions about the case sensitive issue with NSIS (Nullsoft). Edit: Oops, it is a Wise Installer, overlooked that. This should work "PrintKey2000 Setup.exe" /s. Notice /s is outside of the double quotes. If you had it inside then it may not work silent.

CMenu was correct with identification. Even when you 1st start the install, you see a blue splash banner that has Wise stamped on it by both installers. If you selected Silent Install from Identify Installer menu, then it should silent install as SendToA3X has done here. Your use of /whatever switch seems a concern perhaps, but here is the AutoIt script solution to use on each of the installers shown below. RunWait('"' & @ScriptDir & '\setup.exe" /S') I do not know what you did wrong, but you did not do it right. Perhaps you got the quotes wrong or something. Both of your links do not work so I searched for them and got some lucky installers perhaps.

To copy files in a command file, then go to the command prompt window and type copy /? to get the syntax needed for you to do the commands needed. ICQ 2003, last of the good versions IMO

All the files so far that I have seen in winsxs are hardlinks. Removing winsxs may not save 1kb of space going by hdd space but may upset the updating process that the linked files elsewhere would expect. The way that Vista uses hardlinks on most of it's system files makes consideration of removing any file that is hardlinks as you need to consider it's linked counterpart and it's function elsewhere. Using NTFSLink shell extension that I use may show you the same in explorer as I see as it uses icon overlays to show you the hardlinks and junctions.

At the Inno Setup Downloads Page, you will see a QuickStart Pack. Download the ispack-5.1.11.exe installer to download the items needed. This is the easiest way to get the pascal extensions added rather then trying to do it manually. I downloaded the firewall from download.com and unpacked it for a look. You may end up missing the needed setup code for setting up the service?, etc... that is probably done through the custom pascal code. I made up a custom installer with what info was available to use and it did not work right at all, but mind you that I am testing in Vista under a Virtual Machine that the firewall does not indeed support Vista to start with. I installed the firewall from the original installer silently and ofcourse Vista complained but I continued. I saw only one window which was a complaint about OBDC. You may get different results with XPSP2 as it seems with your results. To summarize, rebuilding the installer seems differcult to have it fully functional and silent install has issues as we know. You maybe able to use Installrite, AutoIt or some other means to make installation a little more manageable.

Hello tallspruce, It may work better with the E. Yes, it will be already compiled so it makes it differcult to compile the script when you do not have the pascal source code. You also need to have the pascal extensions installed for Inno Setup to compile it.