Geej

Thanks. Suggest to add it to your 1st post.

updated to v3.6.0.0 INF now includes [DefaultInstall] section to perform live/normal installation. Please uninstall any existing version first, reboot if prompt. Then install this one by right-click the inf, select 'install'.

I try to update as long as I can as my host PC is still XP. If one day my host PC change to Win 7, I will stop updating it. Updated to 5.4.4.1128 Includes ReplaceDriveletter.vbs which will determine at install time if actual drive is indeed pointing to C: as the content of existing UpdaterInfo.xml & skin.css are pointing to C: If not C:, then ReplaceDriveletter.vbs will replace the 2 files with actual drive letter. If C:, then script will not edit the 2 files and simply exit.

Good catch. Thanks

updated to 5.4.4.1023 Does anyone still need this? I would like to call it a day if nobody need it.

Auslogics Disk Defrag Free (v4.2.1.0) Auslogics Disk Defrag is a compact and fast defragmentation tool that supports both FAT 16/32, and NTFS file systems. It's supplied with advanced disk optimization techniques, which will remedy your system sluggishness and crashes caused by disk fragmentation. Disk fragmentation leads to system slowdowns, PC crashes, slow startups and shutdowns. Auslogics Disk Defrag is designed for fast defragmentation of modern hard disks. Free version Features: -Ultra Fast Defragmentation Engine -Thorough Free Space Consolidation -Special algorithms for VSS-enabled drives (Shadow Copy) -Single File or Folder Defragmentation -Disk Error Check and Repair -Advanced Scheduling Options (including ability to create multiple tasks) -Customizable Disk Map Appearance -Automatic Power Saving for Laptops -No Auslogics Toolbar and Ask.com components. -Auslogics Disk Defrag on Explorer Context Menu Enabled -Uninstallable via Control Panel/Programs and Features AuslogicsDiskDefrag4210x86_ENU.WA Size: 5.01 Mb (5,252,669 bytes) MD5: CB8152CC35D9E4AB17E0297D7160887E Build for x86 only. ENU only INF includes [DefaultInstall] section to perform normal installation. Please uninstall any existing version first, reboot if prompt. Then install this one by right-click the inf, select 'install'.

Using WinToolkit150-1_Test36 I stumbled leftover files/folders from WinToolkit in the slipstreamed os. Still left in the slipstreamed OS (x86): A) Files: 1) C:\Windows\System32\WinToolkit_RunOnceLog.txt Rather keep 2) C:\Windows\WinToolkitDrivers.txt Rather keep 3) C:\Windows\System32\WinToolkitRunOnce.exe 4) C:\Windows\System32\UTH.exe B ) Folder: 1) C:\Windows\WinToolkit\Addons Let's WinToolkit know what addons are integrated i) Should WTK perform/schedule a cleanup or does it serve some purpose by leaving it there? ii) If it is there for log purpose, can they be moved to 1 common location/folder? Done iii) In all cases, even if it is there for a purpose (I assume it is generally use for post review/debug only), can you let user have a choice whether user wish to keep these logs/folder or clean up everything? (I would prefer all cleaned up ) NO Your thought...

Just my thought... Try running inf in RunOnce which support REG_EXPAND_SZ and you can use variable instead of hardcode path like C:\PROGRAM FILES. E.g In case of dual boot OS, something the OS might not install to C: drive. It could be D or E drive. In Everything Search Engine, post 11, I have a simple batch to create RunOnce key using REG_EXPAND_SZ variable.

Updated to v2.11.560

U are running on a Win7 host while running nlite? Just a thought... I think this is one of the issue. Exact problem, I don't know

Info Universal Silent Switch Finder is a small and easy to use application that will find and activate the silent installer command on various application. The application has a simple interface that will easily guide you through the whole process. Package as "Send To" style. Uninstallable UniversalSilentSwitchFinder1500.WA Size: 715.69 Kb (732,863 bytes) MD5: 95294F8CD92832707C80E5270124AD63

You can replicate like this. Download an .WA addon and open it using WTK. Then follow the steps in the below image (Same issue on v.1.4.0.77 & beta_test19) Hope that makes sense...

bump Just to feedback the 'remove' button still does not work in Addon Maker tab ('file' sub-tab) (version tested is beta) I have not to tested Folder sub-tab or reg sub-tab. But I doubt it is resolved. Is it resolve? If yes, which version of WTK?

I'm glad members chips in to help... thanks for the great effort. :prop:

Yes exporting the task from Task scheduler and give a same say Everything64.xml Then RunPostSetupCommands change to cmd /c schtasks /Create /XML %10%\Everything64.xml /TN Everything where %10% is %windir% If unsure, see schtasks /Create /? for more information. you could also modify the xml command to <Exec> <Command>"%ProgramFiles(x86)%\Everything\Everything.exe -startup"</Command> </Exec>

Thanks for your hardwork. Keep it up.

Hi dotfusion Try testing the batch file first (see my post Side Test in post #31) . If it works, then manual retest the whole package again. (Ensure no orphan entry in Task secheduler) If it doesn't work, try myselfidem recent post. I think he can help you better in x64 issue. (In the worst case, you can try xml method instead of batch method.) Regards

Hi, dotfusion I don't have x64 OS to test. I change slightly the WA package, hopefully can fit x64 with WinToolkit Please manual test the package on VM first. On an existing Win7 x64 VM with UAC ON, remove/uninstall Everything Search Engine so we can start as fresh install. If you have Task scheduler set for Everything, remove/delete as well. Open this .WA package with Win Toolkit->Addon Maker->Open It will be generally mounted/extracted to C:\winToolkit_TEMP\AddonC Copy the whole program folder of 'Everything' within AddonC to C:\Program Files (x86) Copy Everything_Schedule.bat to C:\windows Copy Evthing.inf to C:\Windows\inf Double click ROEveryThing.reg to add to RunOnce key. Save back the .WA package before quitting Addon Maker & then quit WinToolkit. Reboot pc. After reboot, Everything System tray icon should appear. (side test: Test the batch file to see if it works in win7x64. Run the batch with "Run as administrator" if you have UAC On. Then check whether the task is added to Task Scheduler by Start->run->taskschd.msc (enter) Click "Task Scheduler Library" and wait a while for task to be loaded.. In 'Name' column, there should be "Everything" listed. This is the TaskName (TN). Should be 'Ready" Status. Hence the batch file will work on x64. Then Delete the task manually.) Will host for 3 days. Everything Search Engine_1.2.1.452_x64_Test_UAC_ON_RunOnce.WA Size: 445.39 Kb (456,081 bytes) MD5: 240DB053A15D4452DCB728CC4F3E20D0 Regards

Many thanks, able to launch now.

CPU is dualcore Intel Pentium E2180. No progress bar appears. It didn't have a chance to show me progress bar. When I double click to run, wintoolkit seems to run for 2 sec in the background w/o any progress or dialog, then the error message came. Additional info: The same beta is run on VM Win7x86 and it can run the first time. I close the program and relaunch the beta. Now it tell me "DISM could not be found in 'C:\Windows\System32' and Win Toolkit depends on it! Would you like to download it now?" with Yes/No button for me to click. I clicked No which winToolkit then self-exit. I wait a while, then relaunch Win Toolkit. Now it can launch normally.

No log generated

I got this error the moment I launch WinToolkit (new beta). I even reboot first, then try again. Still got this error. I got no such problem with v.77 I'm running under XPx86

Okay, if x64 is so complicated, just default to %systemdrive% as I suggested earlier. Alternatively, don't change anything for x64. Just change for x86 first. Rather than leaving it status quo, frankly, I see no harm implementing it first. If there is any adverse effect, we can always revert back. Again said earlier, 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. It's all about improving productivity. (E.g Currently if it takes 10 clicks to do a specific task, but now I only need 9 clicks to do the same task. You save 1 click per task.)

Ha ha, sure. Not a big problem. Will wait. I still have workaround despite this little flaw. Thanks