WPI and AutoIt

[kornboy82]

Now I just want to ask something.

I work as a computer tech for 52 first school. The secretary of each schools once used an application that was connected to a server named CAPEDPRG.

Now they don't use this software again. The server was deleted but every secretary computer remains with all the registry entries that points to this server. The computer can have like 5 registry to that server or 30 registry to that server. These registry keys slows down the computer because it search for the deleted server.

Do you know a method I can use in AutoIt to search the registry and delete all the keys containing the CAPEDPRG word as an other account (without closing the secretary session) and without writing each possible keys in a registry file or on a single line ?

I know it's a little out of the topic but help is really appreciated.

Thanks

[chaoticyeshua]

Hmmmm... I'm not really sure of a way to search the registry, but I do know that you can delete registry keys using the "RegDelete()" function; so if you know at least some of the keys then you can automate the deletion of them using AutoIT fairly easily. Beyond that, I wouldn't be of any help to you because that's as far as I've ever gone with it, and I can't really seem to find anything that would be of use to you. You might try running CCleaner on them. It's a fairly good registry cleaner, although I don't know if it will find the keys you're needing to delete.

But, here's an example usage of RegDelete() just in case, maybe this will help at least a little:

RegDelete("HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager","PendingFileRenameOperations.bak")

[Kelsenellenelvian]

nm

Edited April 30, 2009 by Kelsenellenelvian

[AlBundy33]

start install\ScriptGoogleStartup.exe
start install\WindowsTweaks\IEHomePage.reg

I think both commands cannot work because if WPI starts you cmd-file the working-directory is not the script-directory.

You can put the following command to your script to change into the script-directory:

pushd "%~dp0"

The second one can also not work because you will see a message-box.

To avoid this you can use

regedit /s install\WindowsTweaks\IEHomePage.reg

or

reg import install\WindowsTweaks\IEHomePage.reg

Your working script should look like this:

START /WAIT "%~dp0install\ScriptGoogleStartup.exe"
regedit /s "%~dp0install\WindowsTweaks\IEHomePage.reg"

Al

[bobbintb]

Hi there,

I used WPI for a long time since the begin of it's developpement.

Today, I started using it with some AutoIt scripts to automate my installations and settings.

So I tried simple install, it works perfectly. I use WPI to launch my AutoIt scripts for simple installation like Office 2003 or an Antivirus software and my AutoIt script (converted into an exe) do the rest like launching all the setup.exe in each apps folders.

Here comes my problem...

I started to include Registry Tweaks into my AutoIt scripts. When I launch the script manually by double-clicking on the exe, the script goes perfectly. When I ask WPI to launch the script I see the registry tweak start and then... it says that I don't have administrator rights to install the reg file or it's corrupted...

I don't understand a thing... Does Windows Vista detects if the script is launch manually or by an application ?

Also, another problem I found is when I start a setup that needs other files in the same folder to advance, suddenly, an error popup and says that the setup can't find the other files. When I run manually the AutoIt script again, everything goes perfectly. It seems like the PATH or something is messed up. I tryed many things like asking my AutoIt script to launch a batch file, that didn't work. Asking WPI to launch a batch file that starts my AutoIt script too gets some errors. Is WPI started as an administrator when you launch it ? I disabled the user control and my account IS administrator of my computer...

I don't understand why... And is there a known PATH problem with WPI and Vista ?

Is some of you uses AutoIt combined with WPI and has runned into that type of error and found a solution, can you give me a clue ? Thanks.

can you post a sample of the script? im not so sure about the registry issue so a look at the code may help. the problem with the second is a directory issue. ive had it before. since WPI runs the script from a different directory, the working directory changes. are you using "Run" or "ShellExecute" because ive had this issue with ShellExecute and "Run" seems to work differently.