What Does the OQO Manager Manage?

[Guest]

[fixup]

I don't have any of your problems neither

For the slow mouse, you may try to change the driver from "OQO PS/2 Mouse" to "PS/2 Compatible Mouse". Just a guess: the OQO driver might connect it to other "enhancements" which, as always, usually mean poor performance. It may also fix your keyboard problem as the driver also control the keyboard port.

I've been using the general PS/2 mouse driver without any issue. I never run oqomanager.exe.

It is hard for me to trust system-level software that are not made by MS. System-level programming is not something most software engineers can do well.  The worst system-level software I've seen so far are those from Symantec, anti-virus, anti-spyware, Internet security,  undelete, backup, etc. If you want an efficient and reliable computer, remove all such system-level stuff.

I don't understand why oqo waste money and time to develop such "enhancements" that are not necessary and actually cause more troubles, especially while OQO models are struggling with Vista with relatively low performance CPU, inadequate memory and excessive heat. The only necessary function is brightness control; all other things are already handled very well by Windows. I'm grateful that the oqo engineers put some key keys such as keyboard backlight into BIOS. The engineers who customized Windows installation also did a fantastic job. OQO is so far the cleanest and best configured Windows out of box, among all the computers I have bought for all these years. They show file extensions, for example, and installed Firefox and AdBlock+, solute to you! My only suggestion is: don't install Acrobat and QT; instead, install the alternatives.

[nivenh]

My biggest complaints about the system:
- keyboard dead problem mentioned in other threads (requires USB kb to recover).

Is this happening with the latest OQO Manager?  This should've been resolved in the latest build.

- mouse drift that requires me to pop back into standby and out again.

I've seen this here in the past on occasion, but I don't have to resort to standby to make it stop.  Typically if i just take my finger off of it for a second it will self-correct itself.  If you contact our technical support number, they can probably help you out with this one.

- ridiculously slow mouse response under heavy system load.

Are you on Vista or XP?  If you press CTRL-ALT-SHIFT-ESC, that will stop OQO Manager (and you'll have to manually relaunch it), but it will tell you if OQO Manager is playing a part in this problem.  If it is or appears to be let me know and i'll make sure it gets addressed.

Nivenh, thanks for your hard work.  I'm looking forward to the next release.

No problem!!  Thanks for your feedback!!  Let me know the outcome on those issues when you get a chance, and I'll figure out what needs to happen on my end.

[dlach]

I had the Kb dead problem very soon after I got my OQO and I believe the first thing I did when I got it was install the latest SW.   Unfortunately I can't say for sure.  But there are other threads in the forum on this topic and this is the first time I've heard that anyone thought it fixed.

I will try your suggestion re: mouse drift.  I'll also try killing the OQO manager the next time the mouse stops responding, I am running XP.



 

[Dave P]

I was just curious. I didn't mean to start a war.

As one who has been programming longer than most of the people on this board have been alive, I want to remind you that anytime you get two programmers together you will get at least three solutions, all of them less than optimal.

The last perfect program was IEFBR14. It has been run millions (probably billions) of times and has never failed and has never used a single extra bit of processing overhead.

All other programs, OQO Manager included, have their strengths and weaknesses. I recommend a Zen approach. Appreciate programs when they work and accept them when they don't. The alternative, the Hulk approach, results in too many broken motherboards.

nivenh, as dlach said, thanks for your efforts.

fixup, thank you as well for your comments.

Dave

P.S. For you youngsters, IEFBR14 was a mainframe program consisting of one machine language instruction - a NOP (no operation). It was used primarily in batch jobs; what would be roughly equivalent to job scripts or scheduled jobs on a PC.

[fixup]

I agree, NOP is always the best. I have been living without oqomanager.exe. The only time I need it is to adjust brightness which is the only function I have not found an alternative method.