Windows/Microsoft Pagefile

THe temporary version will shortly be removed.

Latest version is now 2.1.0.0.

 

Sorry, Howard, but I was not around and I simply missed this testing build...

 

That's OK.

It was the same as 2.1.0.0.

 

I now know why you got that message.
it was due to the WMI class Win32_PageFileUsage not being set up properly.
I now have code that should detect this.

 

It has come to my attention that a number of web sites around this planet have copied various versions of PageFileUsageMonitor to their own web sites. Only the latest version should be used, and you can only be assured of getting the latest version by downloading from my web site.

In addition, at least two of those files have all numeric names, which makes them suspect as I have never released such filenames..

 

@ Howard Kaikow, thanks for the updates and useful warnings download about.

Really good to set the suitable PageFile'size!

 

I don't want to annoy you unwisely anymore with my particular problem, but only want to report that, unfortunately, I cannot get anything else that the error '70' message on this heavily tweaked system snapshot, at least until I first point the exact setting I will have to reset.

And this new version is working just great on my other snapshots.

 

Are you using version 2.1.0.0?
What does the error 70 message look like?

I suggest asking how to fix WMI in the MSFT newsgroup

microsoft.public.windowsxp.WMI

You'll likely get a quick answer.

 

Except in unusual circumstances, I will not download software other than from the author's web site. Better to get from the horse's front end, as you know what comes out of a horse's back end.

 

Yes.

Thanks for the tip, I should give this a try shortly...

 

Version 2.1.0.2 should give a better message than the one seen by runebabine.
Will not solve ruinebabine's problem, but should be more informative.

 

Version 2.2.0.0:

1. Perhaps not visible, but prog is much faster internally.

2. Added more tests. Prog now:

a. Tests whether WinMgmt is installed.
b. Whether WinMgmt can be accessed.
c. Whether Win32_PageFileUsage and Win32_PageFileSetting classes of WinMgmt can be accessed.

I'm curious as to what these will report on ruinebabine's system.

 

Hehe, guess what Howard?
My pc beats you again...

And me that I bought a freshly new jar of crunchy peanut butter, just for you!

 

Version 2.2.0.1, even faster.

Heck, I waited almost 8 hours since last version.

Main reason was to modify the code so it will be easier to change in the future, or if on Lost, as well in the past.

 

I do not get a "peanut" taste, not from raw peanuts in doctor's office, nor peanut coated M & Ms, nor the natural creamy peanut butter I bought at Costco.

My taste buds must be dead.
I'll talk to a doctor about this on Monday.

 

Hey! I got a new One! 'got a new One!!
Look, lookadat One, mom...

​

​

 

That error message is being issued my the OS due to
your broken WMI installation.

I'll see whether I can add code to trap that error.
Note: Not all errors are trappable by programs.

 

Could you run http://www.standards.com/msgPageFileUsageMonitor.exe.

The prog will issue a series of messages.

The messages would be, if there are no errors:

"Checking if Winmgmt Service is installed"
"Testing if prog can get Winmgmt object."
"Testing if prog can get Winmgmt service."
"Testing if prog can use Winmgmt service."
"Testing if prog can get Win32_PageFileUsage class."
"Testing if prog can get Win32_PageFileSetting class."

Please let me know the last message issued prior to an error message issued by the OS or my code.

 

I received each and all 6 of them, in the correct chronological order.

Here is the last one...


...before I finally receive my usual
error message:
​

EDIT: Some other concomitant info there too.

 

Good, that's what I expected.
I've added 2 more messages to msgPageFileUsageMoniitor.exe as follows:

"Checking if Winmgmt Service is installed"
"Testing if prog can get Winmgmt object."
"Testing if prog can get Winmgmt service."
"Testing if prog can use Winmgmt service."
"Testing if prog can get Win32_PageFileUsage class."
"Win32_PageFileUsage count is " & objWin32_PageFileUsage.Count
"Testing if prog can get Win32_PageFileSetting class."
"Win32_PageFileSetting count is " & objWin32_PageFileSetting.Count

objWin32_PageFileUsage.Count should be the count of the number of page files you have.

objWin32_PageFileSetting.Count should be the count of the number of page files for which you have specified the limits. I am guessing that this the query that is failing due to Permission Denied.

EDIT: Some other concomitant info there too.[/QUOTE]

Do not see how that thread is related to this thread, unless you have improper file permissions.

 

Do not see how that thread is related to this thread, unless you have improper file permissions.[/QUOTE]

In case error is caued by accessing the log file, I've added a check to msgPageFileUsageMoniitor.exe.

I guess that this might cause a problem if the file's permissions/access rights got set in one snapshot and were not valid in your misbehaving snapshot.

 

In case error is caued by accessing the log file, I've added a check to msgPageFileUsageMoniitor.exe.

I guess that this might cause a problem if the file's permissions/access rights got set in one snapshot and were not valid in your misbehaving snapshot.[/QUOTE]

I just tested by making the file read-only.
This caused the error 75.

Perhaps, that is all that is stopping yoy from running the program?

One way to test is to delete the log file BEFORE you run the program.

 

I got those first 5 right:

...then fellows this last one:

I cannot go that far enough to experiment those other ones.

 

No, get same result that in my last post.

No, I always delete the empty log file now before to run your last debugger, and it changes nothing. By the way the last 2 debuggers errors made it aborting too shortly to even have the occasion to try to produce a log file...

 

That means that the failure is occurring on the query of the Win32_PageFileUsage class.

Last time, problem occcurred on querying the Win32_PageFileSetting class.

At least this time, my prog was able to intercept the error message.

You need to fix your WMI. Until then running PageFileUsageMonitor will just produce errors.