Geej

I have been using this feature and I noticed that if I tried to edit an existing .WA addon by removing some shortcut/files, the shortcut and files still remain in the .WA package Just wondering if problem has been fixed. Best regards

Perhaps we can look at it like this. If os-arch is x86, then as per my suggestion If os-arch is x64, then default to %systemdrive% (so that user can decide further which folder they want to work with) The main idea is to put a commonly-used default folder path where user is most likely to use it most of the time when creating program addon. By putting a default folder path will still enable user to change if they wish to. I am not suggesting fixing the location without the ability to change by the user. If any x64 user has different opinion of the location, then give feedback. Regards

Just 2 small suggestions for your consideration.

What I find missing is the meaning of the color code (Green, yellow, red)? Perhaps you could add legend to make it more meaningful. I wonder if someone "select all the green items" for removal, it won't break the install? since Green is "safe to remove".

Updated .WA package - Thanks to myselfidem for the batch file, Everything_Schedule.bat (localised) making Everything Search Engine able to launch it as a startup application even with UAC set to default. - Once your install gets to the desktop, a manual reboot is necessary - During uninstall, it will also end + delete the scheduled task.

Thanks myselfidem for taking the effort to further test using batch script instead of xml. I will test your version just to gain more insight... The sfx version you use is 1.4.3.2367 which has description : 7z Setup SFX (x86) I have 1.5.0.2478 which has same description : 7z Setup SFX (x86) May I ask if those version also will work on x64? Or is there x64 module? I just done testing with xml via inf, looks good. Only need to futher test uninstall routine. Best regards

Work with win7x84? (OS with x86 & x64 or was it a typo error? ). I hope you mean x64. Not really sure as I never build x64 inf to test. I took a quick look at Onepiece Haozip addon Below are for x64. You need these sections: [DefaultInstall.ntamd64] -This section is called When you right-click inf, select "install" from context menu. Try to get this part right during testing. This part is for normal install. Majority of the directives use here is same as [Haozip.ntamd64] below which is use by OC Components. [sourceDisksNames.amd64] [sourceDisksFiles.amd64] [Haozip.ntamd64] -Very similar to DefaultInstall.ntamd64 but use in actual setup. also remove @Haozip.inf from copyfiles. Do download a few more x64 addon to compare. Also doing some simple, light program addon first to familiarize with inf structure. A native program that run on x64 can use dirid 16422 but a 32-bit compatible program running on x64 is likely to install on 16426. If unsure which number to use, always run the program installer to verify. Sorry, can't advise much... Maybe you can ask Onepiece further. Italian forum has 2 pinned topics which is informative fir making inf. They might help you further... regards

Just a small word of caution. The registry entries might not be 100% suitable for win7x64.

Thanks mooms for the upload in #19. I will do my own test with UAC set to default. (I manual run on the VM works, so I think should work unattendedly too) I personally would like to adapt your xml into my inf and see If it could be launch using postsetupcommand (for my personal build) Can I ask how you create the xml? Did you use the Task Scheduler's GUI to create it, then export the xml file? Do you know what would be the command if using schtasks.exe on the command line? Many thanks to you guys. With win7, learn something new always ...

Reaper, thanks for the tips. I coincidently also add a "A" at the end of folder (only that I use bigcap A) And thanks to Legolash2o for looking into delete issue.

Do you mind add a simple total runtime into the log when All-In-One-Integrator finished the task? I usually run it before going to sleep. Hence I would like to know how long it takes to run.... Or is there already an info somewhere and I have missed it (when I wake up so that I can retrieve it)? Regards

Thank you mooms for the 2 uploads. I will study them... Maybe I will keep UAC in future if this is feasible, just like you do. (also thanks myselfidem for the tips, you are also very resourceful.)

Updated with .lng / .ini support as requested by mooms (Actually I forgot to include .lng file... ) @mooms, to bypass UAC at Everything start, try adjust/add your Autounattend.xml with this <settings pass="offlineServicing"> <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[url="http://schemas.microsoft.com/WMIConfig/2002/State"]http://schemas.micro...fig/2002/State"[/url] xmlns:xsi="[url="http://www.w3.org/2001/XMLSchema-instance%22>"]http://www.w3.org/20...hema-instance">[/url] <EnableLUA>false</EnableLUA> </component> </settings> I use a simple batch to export the RO key in .reg. (I also use nircmd.exe to help me open up the key in registry for visual inspection.) Need to enter value for Set infname= and set appname= before running the batch code. @Echo off Title Export a RunOnce key for inf installation Set infname= set appname= Echo This script writes a reg_expand_sz to RunOnce Echo then export the key in .reg format Echo Note: Only main key can be exported. Echo Export Individual key is impossible Echo Please set the appname inside this script first. pause cls echo. echo Info: echo infname is %infname% echo appname is %appname% pause REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /v !%appname% /t REG_EXPAND_SZ /d "rundll32 advpack.dll,LaunchINFSection %%windir%%\inf\%infname%.inf,Install" /f reg export HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce RO%appname%.reg echo. Echo Inspect visually the RunOnce entry before deleting in next step nircmd regedit "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" Echo Will delete %appname% key next. Otherwise close console box. pause reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /v !%appname% /f So I presume we are can go wild with RunOnce method since not many people know this method. In fact I just discovered it recently too. RunOnce key with ! explained Edit: Additional info RunOnce support REG_EXPAND_SZ but RunOnceEx doesn't.

I don't have x64 os. Sorry. Try to edit manually the addon to fit x64. Think change the inf dirid from 16422 to 16426 Also use toolkit to edit the copied location to %programfiles (x86)% Dun know any more registry entry need to add or not. Regards

Everything Search Engine 1.3.3.658b (with .lng support) For x86/x64. Localised language support for French/German/Spanish. # Small installation file # Clean and simple user interface # Quick file indexing # Quick searching # Minimal resource usage # Share files with others easily # Real-time updating Everything will only locate files and folders on local NTFS volumes. Everything requires administrative privileges for low level read access to volumes. Configure to run as services. Auto Startup item (even with UAC on). Uninstallable: Yes EverythingSearchEngine_1.3.3.658b_dual.WA Size: 930.14 Kb (952,467 bytes) MD5: C5944153126EC477E3BB7751689C00F9 Tested on VM win7 x86 only. Thanks to mooms, myselfidem & RicaNeaga for the help/testing on x64 system.

InstallWatch Pro 2.5c For x86/x64 A utility that tracks changes made to your system during the installation or removal of software or hardware. Changes tracked include additions, deletions, or modifications to files and directories, INI files, and the Registry. All information is stored in a database so that it can be accessed later to generate reports. The Registry entries can also be exported to a Reg file for later use. (Great tool for making inf addon) Uninstallable: Yes InstallWatch25c_dual.WA Size: 1.78 Mb (1,861,991 bytes) MD5: 6B09351396DAF395FFC37A09B359E109 Tested only on VM win7x86

I come across this batch for global time & date. Might be useful to someone.

bump

Updated to v3.2.1 beta build 28025

Thanks for this great tool. I have been using this feature and I noticed that if I tried to edit an existing .WA addon by removing some shortcut/files, the shortcut and files still remain in the .WA package edit: Oops, I think I post in the wrong thread... on this part. These are some limitations I observed. Same shortcut name cannot be more than 1 (such as placing same.lnk on desktop & Start menu) in the .WA Copy Folder : cannot have same folder name (eg. to program files and appdata dir) in the .WA Is the file path within the .WA shortcut always point to C:\.... What if %systemdrive% is D: during installation? Cheers

luis, HJSC, As always, appreciated VM. Just to let everyone know that previously Foxit Reader can't open pdf web address in web browser. I have now fixed it (Tested to work with IE8 & FF/Pale Moon) Some sharepoint registry entries are also added. For info only: "Version 5.4.3.0920 fixed a security issue where the insecure application loading libraries could be exploited to attack the application."

Updated to v5.4.3.0920, thanks (fix some missing registry entries)

Thanks, Reaper. A must-have program for me, whether it's XP or Win7. It also help me to understand what is needed to make this kind of addon (.WA) Cheers

loren, thanks for the appreciation. Cheers

zoulou99, thanks for the appreciation. Cheers