Login with username and password (forgot your password?)

I'm posting to confirm the 2.105.1 zip file does not overwrite my customized ConfigDir.ini.

Thanks for the change!

I suggest that the ConfigDir.ini in the FindAndRunRobot.zip file be renamed to ConfigDir_Portable.ini. I'm making this suggestion because I don't want the ConfigDir.ini from the ZIP file to overwrite my custom settings in my ConfigDir.ini.

In the new portable zip of FARR, http://www.donationcoder....ndAndRunRobotPortable.zip, there's a ConfigDir.ini that sets the following variables:

PORTABLE=TRUE
CONFIGDIR=.

To prevent this ConfigDir.ini from overwriting my ConfigDir.ini, I first rename my ConfigDir.ini, extract the ZIP, and then restore my original ConfgiDir.ini. In my ConfigDir.ini, I don't set PORTABLE, and I assign CONFIGDIR to a different location than ".".

If other folks are also trying to maintain their own ConfigDir.ini while using the ZIP file, then this request is probably worthwhile. If I'm the only one running into this, then it's probably not worth the change.

Sorry to hear about the code loss. 

LineByter has been very useful in scanning and filtering the error logs from my Visual Studio builds. I'm overdue in paying for it, so I'll be sure to do that soon. I'm looking forward to the new version.

All the icons look great. Here's a variation on the camera idea from lanux128: how about having the mascot (Cody) with a camera? The timed icon could add the clock from the second icon set.

I noticed the review mention v1.0.2.1 but the download link on the webpage (http://www.codebyter.com/linebyter/) mentioned 1.0.1.16. Am I misreading some information?

Just wanted to drop a note that I updated to 2.12.03 using DcUpdater and am once again impressed. I was already impressed by the responsiveness and care taken with the IE UserAgent fix and the toggle for the ShellExecute behavior. Then I saw the pretty new option tree. Just lovely! And as I lurk and read various posts, I know I'm barely scratching the surface of what FARR can do.

I'm open to running a version with some additional logging if the resulting data will be helpful.

Here's my experiment. I created a batch file named "xyz.cmd" in the same directory as "cmd32.cmd". The file "xyz.cmd" contains just one line which is: calc.exe

With the 2.10.01 quickdoclauncher.exe, I enter xyz.cmd and the FARR windows closes without the calculator launching.

With the quickdoclauncher.exe from reply #3, I see a command window titled, "E:\WINDOWS\system32\cmd.exe", on my desktop. That command window is showing one command: calc.exe. And the Windows calculator has launched. I close the calculator and it and command window that launched it disappear.

Sorry for omitting more details.

1. I restored the quickdoclauncher.exe from the 2.10.01 installation.
2. I type in "cmd32" and FARR lists it as match #1, cmd32.cmd.
3. I press return and there's a very, very brief hourglass before the normal cursor appears.

The FARR window is gone. No new command window show up. No errors that I can see.

I'll experiment a bit to see if I can confirm whether the batch file ran or not.

Here's another data point. I used to be able to enter "cmd32" and FARR would run the cmd32.cmd batch file located in a directory that I had specified as a search folder.  It worked on 2.07.01. With 2.10.01, entering cmd32 no longer launches the script. I replaced the quickdoclauncher.exe with the one from reply #3 and it's working again.  Here's what the cmd32.cmd script does:

@if exist "%windir%\SysWow64\cmd.exe" (
    start "cmd32" "%windir%\SysWow64\cmd.exe" %*
) else (
    start "cmd32" "%windir%\System32\cmd.exe" %*
)

Thanks for the quick turnaround and fix.

I've updated to 2.10.01 and my IE user-agent looks like it's back to normal. It no longer contains that "bsalsa.com" text and my registry key no longer contains that "User-agent:" key under "PostPlatform".

I am noticing another different behavior with 2.10.01, which I'll note in a separate thread.

I'm still seeing the registry entry after starting up FARR after the install. FARR reports that it is version 2.08.02.

Hi,

I think something in the latest stable FARR release (2.07.01) is modifying the IE user-agent setting in the registry.  I recently updated to FARR 2.07.01 and noticed the following behavior.

When the new version starts up, it adds to the following registry key:
     HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent\Post Platform
With this key:
     User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; http://bsalsa.com) ( EmbeddedWB http://bsalsa.com/)
Website www.useragentstring.com reports that my IE user agent is:
     Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; http://bsalsa.com) ( EmbeddedWB http://bsalsa.com/); .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; MS-RTC LM 8; .NET CLR 3.5.21022)
I noticed this behavior as a result of diagnosing some IE connection problems with my intrusion detection software.  It didn't like the much longer user-agent string from IE.  I'm not posting about the intrusion detection software, though.

The following portion of the string looks peculiar:
     User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;

On another computer, I installed an older FARR version, 2.0.0.145, for comparison.  After the install and after launching FARR, I do not see the registry change.  Website www.useragentstring.com reports the user agent is:
     Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)

The list of plugins in the Plugin Manager is empty, so I don't think it's from any plugin.

Here are my thoughts ...

• The HTTP User-agent header field is in the registry key name. That looks incorrect.
• I searched for "bsalsa.com" on the Internet and see mention of it as an embeddable web browser.  Is this thing the new embedded browser mentioned in the latest release of FARR?

Cool. Thanks for helping narrow down the problem, which makes it easier to work around.

Thanks for pointing me in the right direction. I checked Clipboard Help+Spell (Screenshot Captor) after login and each time (with one exception), I observe the problem. On one occasion, a window appeared on the desktop for Screenshot Captor.  I double clicked the title bar, and a rather large blank (white background only) window appeared. So in each of these cases, I stopped both programs. I restart each one, wait for them to minimize to the system tray, and opened them up---they were functional. So it does appear that the problems I see are occurring from the time the start up after logging in.

After restarting the programs after login, I have not seen the problem recur. When I double click the system tray icons, the window opens up and I can select text from the clippings (and images from Screenshot Captor).

I tried logging out and then loggin in, and saw the same results.

Correct. I exit the program (I right click on the system tray icon, select exit, and then start them back up).

I'll have to keep an eye out for the second condition---whether the programs re-enter this odd state.

Hi ... Just checking in to see if anyone has thoughts on this problem. I'm still running into it, and finally have some breathing room to post this message to the forums. So far, I've pinned both CHS and ScreenCaptor to my Start menu so that when I encounter this problem, I exit them and can quickly start them back up. It's nice to have the contents persistent on disk. I still don't have any further ideas on diagnosing this problem to provide further information about it.

Just a quick note that I haven't seen that "bad image" alert is over a week. Thanks for all the help!

After typing the letter el ("l") in "cpanel", I see nine matching entries and no "bad image" alerts. The matching entries are:

Fonts (cpanel).lnk
Mouse (cpanel).lnk
Speech (cpanel).lnk
System (cpanel).lnk
Display (cpanel).lnk
Keyboard (cpanel).lnk
Add Hardware (cpanel).lnk
Date and Time (cpanel).lnk
Power Options (cpanel).lnk

So it looks like those shortcuts to netsetup.cpl are the only problematic ones for my installation.

Out of curiosity, I used the strings utility from SysInternals and found C:\WINDOWS in all of the control panel shortcuts (the okay ones as well as the ones pointing to "bad image").  See the command output below (D> is the command prompt):

 D> E:\SysInternals\Strings\strings.exe -s -q "E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)" | findstr /c:"C:\WINDOWS"
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Accessibility Options (cpanel).lnk: C:\WINDOWS\system32\access.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Add Hardware (cpanel).lnk: C:\WINDOWS\system32\hdwwiz.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Add or Remove Programs (cpanel).lnk: C:\WINDOWS\system32\appwiz.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Automatic Updates (cpanel).lnk: C:\WINDOWS\system32\wuaucpl.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Date and Time (cpanel).lnk: C:\WINDOWS\system32\timedate.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Display (cpanel).lnk: C:\WINDOWS\system32\desk.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Fonts (cpanel).lnk: C:\WINDOWS\Fonts
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Game Controllers (cpanel).lnk: C:\WINDOWS\system32\joy.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Internet Options (cpanel).lnk: C:\WINDOWS\system32\inetcpl.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Keyboard (cpanel).lnk: C:\WINDOWS\system32\main.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Mouse (cpanel).lnk: C:\WINDOWS\system32\main.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Phone and Modem Options (cpanel).lnk: C:\WINDOWS\system32\telephon.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Power Options (cpanel).lnk: C:\WINDOWS\system32\powercfg.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Regional and Language Options (cpanel).lnk: C:\WINDOWS\system32\intl.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Security Center (cpanel).lnk: C:\WINDOWS\system32\wscui.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Sounds and Audio Devices (cpanel).lnk: C:\WINDOWS\system32\mmsys.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\System (cpanel).lnk: C:\WINDOWS\system32\sysdm.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\User Accounts (cpanel).lnk: C:\WINDOWS\system32\nusrmgr.cpl
E:\Program Files\FindAndRunRobot\Scripts\Control Panel (cpanel)\Windows Firewall (cpanel).lnk: C:\WINDOWS\system32\firewall.cpl

 D> E:\SysInternals\Strings\strings.exe -s -q "E:\Program Files\FindAndRunRobot.Scripts.Control Panel (cpanel).DISABLED" | findstr /c:"C:\WINDOWS"
E:\Program Files\FindAndRunRobot.Scripts.Control Panel (cpanel).DISABLED\Network Setup Wizard (cpanel).lnk: C:\WINDOWS\system32\netsetup.cpl
E:\Program Files\FindAndRunRobot.Scripts.Control Panel (cpanel).DISABLED\Wireless Network Setup Wizard (cpanel).lnk: C:\WINDOWS\system32\netsetup.cpl

Hi,

Thanks for the tip about those shortcuts. I am no longer seeing those "bad image" messages when I typed the "wo" sequence as I described in my post on March 7. I followed the tips and ended up moving two shortcuts:

Network Setup Wizard (cpanel).lnk
Wireless Network Setup Wizard (cpanel).lnk

If either of these entries are in the "FindAndRunRobot/Scripts/Control Panel (cpanel)" directory under "E:\Program Files", then typing the "wo" sequence results in the "bad image" alert about "C:\WINDOWS\System32\netsetup.cpl". Now that I have moved both of them into another directory outside of the FARR installation directory tree, I no longer see the "bad image" alert when using the "wo" sequence.

This workaround looks very promising because I was able to reproduce the alert and verify my "wo" sequence no longer results in the alert.

FYI: I am running FARR v2.00.145. Sorry I did not mention this earlier.

Sorry, but I'm still encountering those alert messages about "bad image".

I don't know if the following information will be useful: ProcessExplorer (from SysInternals) says the alert message window is from csrss.exe, which is described as "Client Server Runtime Process".

Here's one scenario that's reproducing the error consistently.
1. I bring up FARR.
2. I type "w" and see some entries. Here's a screenshot: http://www.box.net/shared/static/69d0ob8kk0.png
3. I type "o" and the "Bad Image" alert comes up. I click OK and another one pops up. The alert pops up 7 times total. Here's a screenshot: http://www.box.net/shared/static/gmrw6x7kg4.png

And here's a screenshot of the bad image message: http://www.box.net/shared/static/mjcq3hhgkc.png

Congratulations on getting the site back up!

I think clearing my launch history may have solved the problem. I cleared the launch history. When I bring up FARR, it does not display any items. I launched Outlook, Firefox, and a batch file that launches a command window. I then clicked on the launch history tab in Options and it shows only the three items I started up. For those three invocations of FARR, I have not encountered the netsetup.cpl error.

I am doing the above remotely, connecting to my computer at work (the machine with the 32-bit and 64-bit XP). I'll be exercising FARR on that machine some more when I get back to work on Monday.

I do think it's odd that I was running into this error even though no items in my launch history (when viewing the tab and the FARR .ini file) included items from drive C:.

Thanks for all the help. If I run into it again, I'll be sure to post a message.

I'm running Windows XP SP2 32-bit.

I removed goScreen from my Startup group and rebooted the computer. After logging in, I waited for all the little apps to start up and disk activity to die down. goScreen did not start up. I double click on CHS from the System Tray and it's exhibiting the problem: the File, Edit, etc. menus don't display when I click on them, the toolbar buttons do not work, I cannot select text using the I-beam cursor. I did notice that single and double clicks on the main window's title bar (the one that displays the app name, "Clipboard Help and Spell") work---a single click brings it to the foreground, and a double click maximizes the window. And ScreenCaptor is behaving the same way---the single and double clicks on the window title bar work, but menus, buttons, etc. do not work.

So far, without goScreen running, it looks like I'm still reproducing the problem.

Another data point ... I right click on the CHS icon in the system tray, select Options and Preferences, and the Options window shows up. It, too, has the "no response" behavior. I can click on the title bar and drag it around, but clicking on the different tabs does not change to them.

Here are some thoughts on what I can provide ...

1. I do have Microsoft Visual Studio 2005 on the machine, so I could try to attach to the process and poke around.
2. I can try to record a video of this behavior using DesktopActionRecorder, in case that demonstrates the problem much more clearly than how I am describing the problem.
3. I have ProcessExplorer on this machine in case it can provide you with any information about the process.
4. I can switch my GoToMyPC account to this machine and invite you (mouser) to my computer to debug/diagnose it live.

FYI ... I used the CHS icon in the system tray to exit it. I then start it up again, and all is well---I can select text and the menus drop down when I click on them.

I've looked at E:\Program Files\FindAndRunRobot\FindAndRunRobot.ini and see no occurrences of "C:" or "c:".

I'm not sure I understand your second question about the drive letter assignments. Maybe the information below will help.

1. My 64-bit XP was installed first in drive C: and I used D: for data files. Drive E: contained Vista 64-bit.
2. I did not know about FARR yet, so it was not installed in either C: or E:.
3. I had the E: partition formatted and replaced with 32-bit XP. When I boot into 32-bit XP, WINDIR=E:\WINDOWS.
4. In 32-bit XP, my PATH variable in 32-bit XP does not contain any paths from drive C:.