intellimouse

That would be wonderful!

I can't believe my life is so boring and sad, but I spent most of today solving this. This problem affects all Windows XP SP3 machines I have access to - it didn't want to install the Batch Processor on any of them. However, it installed onto Windows 7 without any problems. So I went on to compare the ProcMon output of the successful and unsuccessful cases. I managed to trace the problem to certain registry keys. It looks like shell32.dll couldn't get the runas command (cmd.exe command path and parameters) from either of these registry keys: HKCU\Software\Classes\batfile\shell\runas HKCU\Software\Classes\Unknown\shell\runas HKCU\Software\Classes\*\shell\runas HKCR\batfile\shell\runas HKCR\Unknown\shell\runas HKCR\*\shell\runas None of these keys contain the runas command in XP SP3, but one of them does in Win7 (and I assume Vista), where the installation was successful: HKCR\batfile\shell\runas\command\(Default) Type: REG_EXPAND_SZ Length: 82 Data: %SystemRoot%\System32\cmd.exe /C "%1" %* So I figured creating the key in XP will solve the problem. To make sure I used the correct path on my system, I checked and found that XP does have a runas command, but in a different place: HKLM\SOFTWARE\Classes\batfile\shell\runas\command. The data type here is REG_SZ instead of REG_EXPAND_SZ, but I hoped it wouldn't make a difference - the data string was the same. So I manually added runas\command into the already existing HKCR\batfile\shell, entered %SystemRoot%\System32\cmd.exe /C "%1" %* into the (Default) value's data field, then restared Windows. It still didn't work, because after successfully finding the cmd path, now it went looking for the non-existent HKCR\batfile\shell\runas\ddeexec. On Win7 it did nothing like this, so I figured the data type may be significant. In Windows XP you cannot create a (Default) value of the REG_EXPAND_SZ type from the regedit UI . You need to create the key by using a .reg file. The string needs to be in hex, using hex(2) as the type (credits to DentArthurDent: http://forum.piriform.com/lofiversion/i ... 12205.html). So I deleted the runas key I created before, and used this script to add the same as before, but using REG_EXPAND_SZ instead of REG_SZ: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\batfile\shell\runas] [HKEY_CLASSES_ROOT\batfile\shell\runas\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\ 00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,63,00,\ 6d,00,64,00,2e,00,65,00,78,00,65,00,20,00,2f,00,43,00,20,00,22,00,25,00,31,\ 00,22,00,20,00,25,00,2a,00,00,00 (This is not guaranteed to work on your machine, and I take no responsibility if you break your registry. Also, I can't attach a .reg file to this post, so if you want to use this, you need to create the .reg file for yourself. Remember to leave a blank line at the end!) After a restart, I could install the Batch Processor! :wink: It was still weird though, because it asked for Administrator credentials even though I was using an admin account. :?: I've got one question though - how do I set the output format? It uses PNG for me, but I'd like to use JPG (or whatever the original format is). I couldn't find a way to set a default format. Thanks!

Thanks Simon and pyro, I'm using XP SP3. I Just mentioned Win7 in case you wanted me to test the plugin on it. I've already tried running as the main "Administrator" admin, as well logging in to a custom admin account that I created, and doing it from there. (I also uninstalled and reinstalled PdN.) I don't think it should make a difference which admin I use - I think all standard admins should have full access to all files in Windows. First I thought it could be an issue of file ownership, but I discarded this idea after trying all admin accounts I have. I searched around for possible culprits in Group Policy settings. But, after all, if the user (admin) could install Paint.NET and everything else on my system (including Windows Updates), surely it must have all necessary permits and settings to install anything. :? I actually doubt whether this really is a problem with permissions. As far as I know, every Windows process carries a user access token, and all processes started by the first process inherit that token. After running Paint.NET as Administrator, I checked task manager, and the owner of the process was Administrator all right. I use this account to install things all the time, so I know it has the permits. For ScriptLab (or the Batch Processor installer) NOT to have the permits, it would probably have to start a new process, and/or use the credentials of a non-admin user. I'm not sure how this could work though - I don't understand how the plugins are fired from PdN. I'm happy to try anything you suggest... Thanks!

Thanks for the awesome plugin Pyro! Finally a solution to use PdN's superb Auto Levels on multiple images. Unfortunately I get an error message when trying to install ScriptLab Batch Processor by pressing the Batch Processor button at the bottom of the ScriptLab window. A messagebox is displayed: Title: ScriptLab Msg: ScriptLab Batch Processor could not be installed. Try again logged into Windows as an Administrator. (This will only need to be done once.) This comes up while I am logged in as an admin. I got the same problem on a virtual machine as well as my physical PC, both running XP SP3. I used the same user account for installing PdN and trying to use the plugin. I've got .NET 2.0 SP2, 3.0 SP2, and 3.5 SP1 installed. I am using PdN v3.36 Final Release. pyrochild.effects.common.dll v2.5.3298.19513 ScriptLab.dll v2.4.3284.31448 Any ideas what could be wrong, or any workarounds I should try? If no-one can think of anything... I know old versions are not recommended, but maybe I could have a go at ScriptLab 2.2, possibly on a previous version of PdN? (I couldn't try this because I couldn't find ScriptLab 2.2.) I also have a Windows 7 (public beta 1) installation, I could try installing on that if you want me to. I haven't tried because it's a beta OS so the results may not mean anything. Many thanks for your help!