Reply
Logi Nu
wexy
Posts: 2
Registered: ‎06-29-2006
0

Problems with SetPoint 2.6 and 2.42

[ Edited ]
The drivers I got with the mouse are version 2.42 and the ones I downloaded are 2.6, but I have same problem with both. After install I'm missing SetPoint.exe and the Connect.exe files so I can't change settings for the mouse etc.. I tried reinstalling several times but again I don't get those 2 files (I have a shortcut in the Start Menu for them but they are missing).

Does anyone have a similar problem and a solution perhaps?

Thanks.

Message Edited by wexy on 06-29-200605:35 AM

Logi Legend
rlowens
Posts: 6,594
Registered: ‎05-22-2006
0

Re: Problems with SetPoint 2.6 and 2.42

Very strange. Try uninstalling SetPoint, then after reboot make sure that there isn't anything left on the Start menu or in C:\Program Files\Logitech. Then, re-install SetPoint (the latest version is SetPoint 3.0) and see if it created C:\Program Files\Logitech\SetPoint with SetPoint.exe in it.

If the file still doesn't exist, you may have hard drive problems or possibly permission issues.

-Richard L. Owens, author of the uberOptions mod for SetPoint. Unlock the options of your SetPoint-controlled device! mirror
Logi Visitor
Patriot
Posts: 41
Registered: ‎06-22-2006
0

Re: Problems with SetPoint 2.6 and 2.42

I had the same problem with 2.42; it would not install properly. Matter of fact, the mouse stopped working when I installed those drivers.

Versions 2.47 and 2.60 installed without error.
Logi Nu
nullinterface
Posts: 4
Registered: ‎07-01-2006
0

Re: Problems with SetPoint 2.6 and 2.42

I have the same problem with Setpoint 2.49a, 2.62, and 3.00. The application simply does not display any options for configuring the mouse - there is only a "Tools" tab.

I'm running Windows 2000 logged in as the administrator - there can't be any file/folder permissions issues. I have tried uninstalling/reinstalling, and downloading uberoptions to no avail. The only obvious thing I can see is the absense of a user.xml file. I'm also using it with a PS/2 adaptor connected through a KVM switch.

Any ideas? Ditch PS/2 adaptor and/or the KVM connection?

To say this is irritating is a generous understatement. This would not even be an issue if the freaking side-scrolling were enabled by default since I have little interest in tweaking buttons for particular applications.
Logi Nu
nullinterface
Posts: 4
Registered: ‎07-01-2006
0

Re: Problems with SetPoint 2.6 and 2.42

Perhaps I should mention that I have a MX400 mouse.
Logi Legend
rlowens
Posts: 6,594
Registered: ‎05-22-2006
0

Re: Problems with SetPoint 2.6 and 2.42

[ Edited ]

nullinterface wrote:
...I'm also using it with a PS/2 adaptor connected through a KVM switch.

Any ideas? Ditch PS/2 adaptor and/or the KVM connection?


Bingo! The KVM switch emulates a standard mouse for each PC, so that's all SetPoint can see.

There are a few KVM switches that will work with Logitech mouses/keyboards if you connect them via a "auxiliary USB" connection instead of the keyboard/mouse ports.

Message Edited by rlowens on 07-01-200609:17 AM


-Richard L. Owens, author of the uberOptions mod for SetPoint. Unlock the options of your SetPoint-controlled device! mirror
Logi Nu
nullinterface
Posts: 4
Registered: ‎07-01-2006
0

Re: Problems with SetPoint 2.6 and 2.42

That did it. It's a cheap KVM, but I've yet to have trouble with other mice with all the same functionality save for the horizontol scrolling.

'Guess I'll just install VNC or something on the other machine.

Thanks for the help.
Logi Nu
wexy
Posts: 2
Registered: ‎06-29-2006
0

Re: Problems with SetPoint 2.6 and 2.42

I am having the same problem with v3.0 as well. Simply every .exe file except LogitechUpdate.exe is missing. I am using Windows 2003 Server and my mouse is hooked on USB port (I have no idea what KVM is..).
Logi Nu
nullinterface
Posts: 4
Registered: ‎07-01-2006
0

Re: Problems with SetPoint 2.6 and 2.42


wexy wrote:
I am having the same problem with v3.0 as well. Simply every .exe file except LogitechUpdate.exe is missing. I am using Windows 2003 Server and my mouse is hooked on USB port (I have no idea what KVM is..).




I don't know that Server 2003 is supported.

A KVM switch is a Keyboard Video Mouse switch that allows a single set of those components to connect to and control multiple computers. They're usually seen in NOCs and server farms where it would be prohibitively inconvenient to have a display and input devices for every machine in the rack. In my case, I have 2 machines on my desk and no room for duplicate devices - the secondary machine is rarely used anyway.
Logi Browser
Trajector
Posts: 12
Registered: ‎07-07-2006
0

Re: Problems with SetPoint 2.6 and 2.42

[ Edited ]
 

nullinterface wrote:

wexy wrote: I am having the same problem with v3.0 as well. Simply every .exe file except LogitechUpdate.exe is missing. I am using Windows 2003 Server and my mouse is hooked on USB port (I have no idea what KVM is..).
I don't know that Server 2003 is supported.
I had this problem too, I got in touch with Logitech support, here is their reply:
I understand that after reinstalling the SetPoint software the SetPoint.exe and Connect.exe are not present. I apologize for the issue you are experiencing. I would like to inform you that this is one of the isolated issues which you are experiencing and we have not come across this type of issue. Also note that the SetPoint software is installed on the system we are using and we are not experiencing any issues with the software. The issue you are experiencing could be because of any firewall preventing these file from downloading on your system. The files you are requesting are not available separately for downloading and these files come with the complete software. I request you to contact your system vendor for further assistance in this regard.
:smileysad:
 
Well, Server 2003 might or might not be supported officially, that I don't know, however using a Server 2003 R2 system with a Logitech G7 mouse I have managed to compile a fix, which you can try at your own risk, for the problem people say here they are experiencing.
 
:smileywink:
 
Given Logitech could not find a solution to the probem themselves, and given the fix is very useful, I hope Logitech will not be against me distributing it, and will not prosecute on copyright grounds. However, if I am wrong, please could a Logitech representative contact me and I will stop distributing the fix.
 
 
NOTE: Since the fix mentioned in this message has been published, a newer version of SetPoint has been released, for which an updated fix has been released. Please refer to my mesage further down this thread for details:
 
 
 
The fix will work specifically with SetPoint v 3.0.104, which, at present, can be downloaded from the official Logitech Website here:
 
 
In the past, Logitech are known to have tacitly replaced their files with those of a different minor version. Version 3.0.104 has the following characteristics: file size 46,685,592 bytes and date 23/06/2006, 14:38:00, so make sure it is the correct version, otherwise my fix might screw up your system. I've uploaded the fix here, which is actually a Rar archive, file size 3,275,293 bytes:
 
http://us.share.geocities.com/general_sg/setpoint3_00_104fix.ra
 
You need to copy and paste the address directly into Internet Explorer to download it. Note that there is a 4.2MB hourly limit on the downloads from this site, so if it does not work, come back after a couple of hours or so.
 
REQUIREMENTS:
The fix should supposedly work with any Windows 2000/XP/2003 system and with any Logitech hardware, but will not work on 9X/ME systems. By the time you start applying the fix, you already need to have an erroneous, with missing SetPoint.exe and other files, installation of SetPoint v 3.0.104 on your machine and you Logitech hardware must be connected. The installation of SetPoint must have been made to the folder the installation program had suggested.
 
INSTRUCTIONS:
1. Unpack the SetPoint3_00_104Fix.ra to the drive, where you installed SetPoint, let this drive be called %
2. Run the file khal.msi, which was unpacked to %:\Program Files\Logitech\SetPoint
When the installation begins, be sure not to select 'Custom Setup', because this will cause the installation to fail, of which you would be notified.
3. Update drivers for your Logitech hardware, from %:\Program Files\Logitech\SetPoint\Drivers
As I was only using a USB mouse but not a keyboard and not a PS/2 mouse, I only had to update a single device in the Device Manager, which was Computer->Mice and other Pointing Devices->HID-compliant mouse.
 
You are all done! SetPoint.exe will automatically run at each boot :smileyvery-happy:
 
If you have found this fix useful, why not write and tell me?
 
If the instructions described do not lead to the solution then I have probably missed something out, in which case please reply to this Thread (I will be notified automatically).
 
Message Edited by Trajector on 07-07-200612:02 PM

Message Edited by Trajector on 07-15-200607:17 AM

Message Edited by Trajector on 04-25-200712:06 PM