5.41 using 20% of CPU

[JARUZ]

There seems to be something wrong with Powerdesk 5.41. When active it uses almost 20% CPU on a Pentium II 333@400. The drivers work just fine if you deactivate Powerdesk.


Juan Antonio

[AVB]

Try to find in Registry the "MGABG.EXE" and delete this entry.

[Spire]

I have PowerDesk version 5.41.008 installed for my G400DH, and I have no such file on my system. My Registry contains no references to it either.

So what is this mysterious MGABG.EXE?

[Angel2167882]

I got the same situation... using CPUIdle, it show 80% idle instead of 99% with my old driver (5.25).

I don't understand Matrox to release driver that are suppose to be faster because the driver itself eat up all the CPU ressource!

BTW, I got a Marvel G200-TV 16MB w/DVD Add-on (witch is there only to look at :-( on an VIA Super7 platform using a K6-III.

[jediphoenix]

Thats funny I have a K6-2 450 128 meg sdram and G400 32 SH and idle running 5.41's I have 96% system, 96% user and 98% GDI, when i disable pdesk.exe I get 98% system and 98% user. Maybe its just the g200 users?

------------------
***TRUST IN YOUR TECHNOLUST***

[Spire]

jediphoenix,

We're talking about CPU idle time, not Windows system resources.

CPU idle time is the average amount of time that your processor spends doing absolutely nothing. It's usually expressed as a percentage of the actual elapsed time (thus, the term "idle time" is actually a misnomer). The more CPU-hungry background processes you have running, the lower your CPU idle time will be.

To obtain a measurement your computer's CPU idle time, you can use System Monitor, which comes with Windows. The item to add is Kernel: Processor Usage (%). Subtract the Processor Usage (%) figure from 100% to get the idle percentage.

[Alec]

Hi, guys!

CPUIdle reports a 99/98% idle processor on my system.
I guess the problem might not be a direct consequence of PD 5.41.

Someone?

------------------
Intel Celeron 433, G200 8Mb AGP, Intel Atlanta 440LX, Soundblaster PCI 128, 96 Megs SDram, 4.3 WD Caviar HD, AOC 5VLR monitor 15".

Remember folks:
"Computers are useless. They can only give you answers"
Pablo Picasso

[Neil]

I heard about this before I loaded the 5.41 drivers. So, I am using the 5.30 powerdesk with the 5.41 drivers.
1) I unzipped 5.41 into a directory, and unzipped the 5.30 in another.
2) I coped all the pd*.* files from 5.30 into 5.41.
3) I installed from this custom 5.41 directory. no problems at all.

[Angel2167882]

After a couple of seeking here and there, I think the 5.41 CPU eating problem occurs only on couple on machine.

The fact I would like to know here:

WHO ARE THOSE HERE THAT GOT LOGITECH MOUSE (with mouseware)???

I think maybe the problem is in cunjuction with Logitech driver... Any advise?

[Spire]

I'm using a Logitech Cordless Wheel Mouse, but I don't have Mouseware installed. (I'm using the stock Windows driver.)

So there just might be something to this Mouseware angle -- though not with the Logitech hardware itself.

[Snake-Eyes]

I don't know if MouseWare is causing problems for others, but I also have the Logitech MouseMan Cordless 3 button scroll mouse, and I'm use mouseware, with no problems (that I can attribute to this software, anyhow).

------------------
Ace

[Simone Arinci]

I have the following strange problem with latest powerdesk 5.41: my logitech mouse (a serial device) started to work bad and use of pointer is difficult. Everything goes fine if i kill PDesk using Ctrl+Alt+Del.

Any other with the same problem ?

[anid]

Good catch Angel. I never noticed or thought about that. But yeah, I was having problems with 5.41 originally myself, never looked at the CPU time it was eating, but it was a lot as the stuttering was very bad anytime DirectX would initialize. I'm using a Logitech wheelmouse on Win98 - don't have any of the mouseware loaded, just the native Win98 support for the wheel. There are 2 fixes available, one that I came up with and one that rylan caught. Mine is going to the registry key HKEY_LOCAL_MACHINE\Software\Matrox\PowerDesk\Versi on5\CurrentSettings and setting the value "PDEnable" to "00 00 00 00". This supposedly disables PDesk, but has no affect on the software what so ever. Rylan's fix was to replace al the pd*.* files in the 5.41 with the versions from 5.25. However, I have found that the problem file is pdkernel.dll (uninstalled is pdkernel.dl_). Replacing just pdesk.exe with the 5.25 version still gives stuttering, replacing pdkernel as well gets rid of the problem.

------------------
I say "Here's a monkey wrench... If you bop me over the head with it long enough I might wake up for a second."

[Simone Arinci]

Sorry for this question, but what is the utility of Pdesk ? Why it must be running like a "service" in Windows 98. I tried to kill it and everything seems to work fine without this task!
If it's use is not essential i'll disable using the key Pdenable how described in previous post.
Thanks to everyone investigating this issue...

[anid]

Simone, I have been trying to figure that one out myself. If you use the desktop navigator or quickdesk, you also need pdesk running, but I know no one (gamers, anyway) that uses these utilities - who wants extra stuff running in the background and eating resources? With Pdesk disabled all the functions still work - all the extra tabs in the advanced display settings, custom monitor profiles, save / restore icons, etc.

------------------
I say "Here's a monkey wrench... If you bop me over the head with it long enough I might wake up for a second."