Posted by Vince on 10/4/2009, 7:36 pm
68.144.14.16
Over the last year I've soured on Logitech stuff. I bought a webcam that proved to be $10 more and inferior in quality to another in-store brand of webcam to be bought at the Canadian store, Futureshop.
I bought a Logitech sound system that was shrill and broke up on any application of volume to the bass.
I brought both items back.
The other day my brother bought a wireless Logitech mouse. Believe it or not, Logitech has now gotten so cheap they don't even include a CD with the drivers or program to run it; users are expected to find that stuff on their website. (Like how many average users would know what to find?)
So he downloaded the program and then couldn't install it. It hung at one point and he couldn't go any further. I too, attempted to install it and it was a total no-go.
Well but ........ he DID manage to install it to a system on a separate drive! What's the deal?
Well, he UN-installed an older version of Setpoint on his main drive, in an effort to clear any conflicts that might exist between Setpoint programs. (He had previously run an older Logitech mouse but the battery died eh? So now he's trying to get this NEW mouse to work).
Ok ........ he has TWO operating systems on this main drive. He has Vista on one partition and XP on the next partition. Well ........ when he uninstalled the Setpoint program on XP, guess what happened? It destroyed his Setpoint program in Vista as well!
I can't believe the sloppiness that now exists in programming. It seems as if programmers have completely forgotten about divisions existing at partitions.
I had exactly the same problem with my Logitech wireless mouse and Setpoint programs on 2 XP systems running on master and slave drive: they cross-threaded with each other.
And ........ XP service pack 3 has the same sort of bewilderment. If more than ONE system exist within the box -even if they're on completely different hard drives- service pack 3 will often cross connect files and install to wrong partitions etc. It's quite infuriating.
I think this may be as a result of Vista's identifying much stuff purely by name instead of by address. Can you IMAGINE trying to remember names like ......{0A780733-8299-4B8B-B576-11314BBBAA1F} ? That's how Vista goes about finding files now.
-Vince
Message Thread:
« Back to thread
