Is batmeter.dll needed for a desktop system?

[Guest 98 Guy]

I notice that batmeter.dll is a process module loaded by systray.

 

Does it perform any useful or needed function for a desktop system?

 

Tangent: Is there a list of processes that systray is configured to

load? Batmeter.dll is not mentioned anywhere in the registry.

[Guest legg]

Re: Is batmeter.dll needed for a desktop system?

 

On Wed, 21 Nov 2007 21:25:20 -0500, 98 Guy <98@Guy.com> wrote:

>I notice that batmeter.dll is a process module loaded by systray.

>

>Does it perform any useful or needed function for a desktop system?

>

>Tangent: Is there a list of processes that systray is configured to

>load? Batmeter.dll is not mentioned anywhere in the registry.

 

I think that IPMI- SMB-ACPI was heavily packaged to serve all

flavours, while actually managing to bury battery management beyond

user access.

 

It could have been something that UPS users could fiddle with in a

desk-top or allow battery simulators to function. There would always

have to be something operating in the hardware background just to say

battery; Y or N.

 

I don't think there are functional freeware tools remaining, since the

formation of 'interest groups' and 'alliances' before Y2K. The legacy

tools from Intel's IAL initiative are barely functional in the

original W98 system they targeted.

 

RL

[Guest glee]

Re: Is batmeter.dll needed for a desktop system?

 

Windows 95/98/Me System Tray Icons

http://support.microsoft.com/?kbid=128129

 

Systray doesn't explicitly need to be loaded separately for the icons mentioned to

be displayed in the tray. AFAIR systray is loaded anyway when one of those icons is

loaded....it's been years since I played with systray and I no longer have any notes

on it.

 

Windows seems to think batmeter.dll (Battery Meter) is needed, as it is a loaded

32-bit module (according to msinfo32) on every Win98 desktop I have looked at. I

can't delete it from Windows (obviously) because it is loaded, in use.

 

Whether it is actually required for other functions to work....I don't know. Rename

it from a DOS boot and see what if anything happens. I'm guessing Windows might

complain about something at boot if it is looking to load it automatically. Let us

know.....

--

Glen Ventura, MS MVP Shell/User, A+

 

 

"98 Guy" <98@Guy.com> wrote in message news:4744E890.B4CB6770@Guy.com...

>I notice that batmeter.dll is a process module loaded by systray.

>

> Does it perform any useful or needed function for a desktop system?

>

> Tangent: Is there a list of processes that systray is configured to

> load? Batmeter.dll is not mentioned anywhere in the registry.

[Guest Franc Zabkar]

Re: Is batmeter.dll needed for a desktop system?

 

On Wed, 21 Nov 2007 21:25:20 -0500, 98 Guy <98@Guy.com> put finger to

keyboard and composed:

>I notice that batmeter.dll is a process module loaded by systray.

>

>Does it perform any useful or needed function for a desktop system?

>

>Tangent: Is there a list of processes that systray is configured to

>load? Batmeter.dll is not mentioned anywhere in the registry.

 

Dependency Walker and Msinfo32 suggest that Systray is configured to

load ...

 

batmeter.dll

powrprof.dll

setupapi.dll

winspool.drv

lz32.dll

winmm.dll

 

- Franc Zabkar

--

Please remove one 'i' from my address when replying by email.

[Guest Franc Zabkar]

Re: Is batmeter.dll needed for a desktop system?

 

On Thu, 22 Nov 2007 10:53:49 -0500, "glee" <glee29@spamindspring.com>

put finger to keyboard and composed:

>Windows 95/98/Me System Tray Icons

>http://support.microsoft.com/?kbid=128129

 

According to the above article:

 

====================================================================

The following icons provided by Systray.exe may appear on the taskbar:

 

Battery Meter

PC Card Status

Volume Control

Quickres

Task Scheduler

====================================================================

 

If I r-click any desktop shortcut, select Properties -> Shortcut ->

Change Icon, and then browse to windows\system\systray.exe, I see a

list of icons including battery, PC card, volume, muted volume, and

USB symbol. There are no Quickres or Task Scheduler icons. Instead the

Quickres icon appears to be associated with the desk.cpl Control Panel

applet. I suspect that the Task Scheduler icon is associated with

mstask.dll, but I haven't tried this.

 

- Franc Zabkar

--

Please remove one 'i' from my address when replying by email.

[Guest 98 Guy]

Re: Is batmeter.dll needed for a desktop system?

 

Franc Zabkar wrote:

> Dependency Walker and Msinfo32 suggest that Systray is configured

> to load ...

>

> batmeter.dll

> powrprof.dll

> setupapi.dll

> winspool.drv

> lz32.dll

> winmm.dll

 

Based on what CCtask is telling me, I would venture to guess that

Systray (on my system) is also soley responsible for loading (and/or

using):

 

WMI.DLL

USBUI.DLL

 

Also according to cctask, powrprof.dll is showing a process count of 2

and setupapi.dll is showing 3 (which, if I'm correct, means either

that systray is running 2 or 3 instances of them, or something else

other than systray is also using them).

 

winmm.dll is showing a global count of 2 and process count of 3. I

see that "TC-Active" and "TC-Monitor" is also using winmm.dll on my

system.

[Guest 98 Guy]

Re: Is batmeter.dll needed for a desktop system?

 

glee wrote:

> Windows 95/98/Me System Tray Icons

> http://support.microsoft.com/?kbid=128129

>

> Systray doesn't explicitly need to be loaded separately for

> the icons mentioned to be displayed in the tray.

 

How would one make icons appear in the tray for the following:

 

batmeter.dll

powrprof.dll

setupapi.dll

winspool.drv

lz32.dll

winmm.dll

usbui.dll

wmi.dll

 

?

 

I "see" no tray icons for any of those (unless one of them is

responsible for the volume control icon).

> Whether (batmeter.dll) it is actually required for other functions

> to work....I don't know. Rename it from a DOS boot and see what

> if anything happens. I'm guessing Windows might complain about

> something at boot if it is looking to load it automatically.

> Let us know.....

 

Windows seems to start fine, but a window does pop up saying that a

program is missing (batmeter.dll) and systray.exe is not running by

the time the desktop is ready for use (and the volume-control icon is

missing from the tray, and possibly the clock to - I might be wrong

about that).

 

Other than that, the system seemed usable.

 

I guess there is no configuration file for systray.exe, like maybe a

systray.ini file?

[Guest 98 Guy]

Re: Is batmeter.dll needed for a desktop system?

 

Franc Zabkar wrote:

> =================================================================

> The following icons provided by Systray.exe may appear on the

> taskbar:

>

> Battery Meter

> PC Card Status

> Volume Control

> Quickres

> Task Scheduler

> ==================================================================

> I suspect that the Task Scheduler icon is associated with

> mstask.dll, but I haven't tried this.

 

I think that Task Scheduler is mstask.exe, which is a completely

separate, stand-alone process that is not part of (or called from)

systray.exe the way that the other items are.

> ... then browse to windows\system\systray.exe, I see a list of

> icons including battery, PC card, volume, muted volume, and

> USB symbol.

 

Maybe the usb symbol is associated with usbui.dll.

[Guest Franc Zabkar]

Re: Is batmeter.dll needed for a desktop system?

 

On Thu, 22 Nov 2007 20:36:58 -0500, 98 Guy <98@Guy.com> put finger to

keyboard and composed:

>Franc Zabkar wrote:

>

>> Dependency Walker and Msinfo32 suggest that Systray is configured

>> to load ...

>>

>> batmeter.dll

>> powrprof.dll

>> setupapi.dll

>> winspool.drv

>> lz32.dll

>> winmm.dll

>

>Based on what CCtask is telling me, I would venture to guess that

>Systray (on my system) is also soley responsible for loading (and/or

>using):

>

>WMI.DLL

>USBUI.DLL

 

Dependency Walker shows no reference to usbui.dll or wmi.dll within

systray.exe. However, I *can* see a "usbui.dll" text string in the

body of systray.exe.

 

FWIW, wmi.dll and usbui.dll appear just prior to systray.exe in

msinfo32's list of 32-bit processes.

>Also according to cctask, powrprof.dll is showing a process count of 2

>and setupapi.dll is showing 3 (which, if I'm correct, means either

>that systray is running 2 or 3 instances of them, or something else

>other than systray is also using them).

>

>winmm.dll is showing a global count of 2 and process count of 3. I

>see that "TC-Active" and "TC-Monitor" is also using winmm.dll on my

>system.

 

- Franc Zabkar

--

Please remove one 'i' from my address when replying by email.

[Guest Franc Zabkar]

Re: Is batmeter.dll needed for a desktop system?

 

On Thu, 22 Nov 2007 21:00:42 -0500, 98 Guy <98@Guy.com> put finger to

keyboard and composed:

>Franc Zabkar wrote:

>

>> =================================================================

>> The following icons provided by Systray.exe may appear on the

>> taskbar:

>>

>> Battery Meter

>> PC Card Status

>> Volume Control

>> Quickres

>> Task Scheduler

>> ==================================================================

>

>> I suspect that the Task Scheduler icon is associated with

>> mstask.dll, but I haven't tried this.

>

>I think that Task Scheduler is mstask.exe, which is a completely

>separate, stand-alone process that is not part of (or called from)

>systray.exe the way that the other items are.

>

>> ... then browse to windows\system\systray.exe, I see a list of

>> icons including battery, PC card, volume, muted volume, and

>> USB symbol.

>

>Maybe the usb symbol is associated with usbui.dll.

 

It seems to me that the same USB symbol (hotplug icon) is embedded

within the code of systray.exe. Hence Microsoft's statement that the

above icons are "provided" by systray.exe.

 

In fact you can confirm this by using an icon extraction utility such

as IconsExtract (freeware):

http://www.nirsoft.net/utils/iconsext.html

 

- Franc Zabkar

--

Please remove one 'i' from my address when replying by email.