All done :-)
Download and install the new setup, still the same version. No need to uninstall the old one. I even updated the screen shot to show the balloon tip letting users know to double click on the monitor to run cleanmem.
Hope this covers it for ya :-)
http://www.pcwintech.com/cleanmem
Shane
That was sure fast! Downloading now -- anxious to give it a try. THANKS so much.
Its what I'm here for :-)
Shane
All done :-)
Download and install the new setup, still the same version. No need to uninstall the old one. I even updated the screen shot to show the balloon tip letting users know to double click on the monitor to run cleanmem.
Works great, Shane. Much better - at least for me.
I just came across a memory leak or whatever you want to call it. While I was installing the newly compiled setup, it asked me to exit CleanMem/MiniMonitor. Okay.
I right clicked on the green icon in the Notification Area and the CPU usage shot up to 50%. I had to use Task Manager to terminate the process. Any idea?
And it is much better for me now as well.
When you open task manger was it the mini monitor using the CPU?
Shane
I should ask, when you right click on the tray icon does the cpu spike, or is it when you clicked on exit?
Shane
Here is a test for v2.0.1 (If it works it will be the release)
http://www.sendspace.com/file/8xst7k
(Replace the mini monitor exe with this one)
I changed 3 things.
1. I changed the API used to pull up the Menu (I did this in case the api I had was causing the cpu spike when you open the menu.
2. Added a minimized button to all the windows.
3. Changed the shutdown process of the program. I did this in case it was causing the cpu spike. Also on one persons machine, and for some reason only his, when he would exit the mini monitor it would crash. I have him testing this one as well. Hopefully the better shut down process should shut down everything better and avoid a cpu spike or crash. I couldn't get either to happen on my system. So all I could do was look at the code that was called when this things happened.
Fingers crossed :-)
Shane
I couldn't replicate the problem again. It could possibly be some other program conflicting with CleanMem. It happened when I right clicked on the tray icon. It became unresponsive and I had to terminate Mini_Monitor.exe via Task Manager.
My PC specs: 2.4 Ghz Core2Duo and 4.0GB RAM with Windows 7 64-bit in case you are curious.
So far, so good. Nothing's going wrong. Thanks.
I couldn't replicate the problem again. It could possibly be some other program conflicting with CleanMem. It happened when I right clicked on the tray icon. It became unresponsive and I had to terminate Mini_Monitor.exe via Task Manager.
My PC specs: 2.4 Ghz Core2Duo and 4.0GB RAM with Windows 7 64-bit in case you are curious.
So far, so good. Nothing's going wrong.
Thanks.
OK, only 1 thing of code is called when you right click on the tray icon.
In VB when you show a menu and try to click away from the menu, the menu will stay till you click something on it.
To get around that I have it calling a single api before it shows the menu
SetForegroundWindow
http://msdn.microsoft.com/en-us/library/ms633539%28v=vs.85%29.aspx
What this would do is set the window to focus, so when you clicked away from the menu the menu would unload like any other.
Well since this is the only bit of code being ran when it locked up on you I decided to find another way.
the SetForegroundWindow works by the thread of the window. perhaps this has a problem on some systems?
So instead I found an old api that will set the focus by the window and not the thread
SwitchToThisWindow
http://msdn.microsoft.com/en-us/library/ms633553%28v=vs.85%29.aspx
This seems safer as it is only setting a window and not having to go for the thread like the other api.
I think I will leave it this way.
If you haven't update to 2.0.1 on the link I gave please do so. I haven't released it yet.
When you load it right click on the icon and hit exit. Then check the task manager, did it close?
The other bug my friend had was something is off on his system, I don't know what.
In my current 2.0.0 exe I have the command "End" after it is done unloading. What this says is to forcibly kill the exe now.
On mine and many others everything ends, no problems.
Yet on his he gets a crash. SO I changed the code and no longer call "End" instead I do the unload me call. Which will only close the process if everything is done and unloaded.
So hopefully I improved the shutdown of the program well enough to where everything unloads.
For me the new shut down works, just need it tested :-)
Long winded enough for ya lol
Shane
Updated and works like a charm.
On a side note, I had to disable my AV to download the file you uploaded. I know its a false-positive but I thought you should know.
Says address was blocked, have it scan the exe. Hopefully the new api isnt making the new exe look like a virus lol
I will upload it to virustotal.com now and see what it says.
Shane
Scanned the .exe It's clean.
My friend just confirmed that the new exe is no longer crashing on his system :-)
I will be getting 2.0.1 ready for release.
Man I hate doing this to people, make an update so quick. But I want the stuff working right :-)
Shane
V2.0.1 is out :-)
v2.0.1
Fixed rare crashes on some systems when trying to exit the mini monitor or open its menu.
Added minimize button to the settings windows.
Shane
CleanMem v2.0.2 Released.
http://www.pcwintech.com/cleanmem
v2.0.2
Added "Reset Window Positions" option to context menu.
Multiple GUI tweaks and fixes.
Fixed minor bug where the mini monitor wouldn't hold its startup position in some cases.
Program now remembers the screen position of the settings windows and others. The reset mini monitor position will also reset these windows as well.
Window positions are now saved under the Current User Reg keys. This has multiple benefits. If a person runs the mini monitor from a thumb drive and on multiple computers, the position will be saved on each computer instead of the ini file. This also lets different users on the same system have the monitor in different positions than the other users.
Fixed bug where the Page File information on the Memory Info Window didn't detect on Windows 7.
Page file info on the memory info window has been updated to pull better information. Such as actual current usage of the page file on the disk.
Fixed bug where the mini monitor didn't always exit & close.
Shane
CleanMem v2.0.3 is released.
On a side note,
Hope you guys dont mind me posting this here. But I just made a new program, took me only a few hours today.
Mainly because I cheated lol
I took the cleanmem mini monitor code, ripped out everything I didn't need and made this new monitor. Saved me TONs of work not having to recode all the same stuff over again.
It is a monitor to show the current read and write speed of your hard drive.
Since the drive is the bottle neck of performance, knowing when your drive is under a load is good to know.
I just finished this, no page for it yet as I want it tested. If you try it please email me any problems you have. Otherwise after a day or two to make sure nothing is broken I will release it by Sunday :-)
Give it a quick try :-)
Not bad for a few hours of work I hope.
http://www.pcwintech.com/files/setups/drive_speedometer_v1.0.0_setup.exe
Shane
bah! forgot I had hot linking disabled lol
grab the link from this post
http://forums.pcwintech.com/index.php/topic,1907.msg12184.html#msg12184
Shane
bah! forgot I had hot linking disabled lol
grab the link from this post
http://forums.pcwint...4.html#msg12184
Shane
Guessing it doesn't work on all drives yet? Always shows 0 read/write here (WinXP, Hitachi HTS541612J9SA00 hard drive)
It hooks to the performance monitor in windows. Under physical drive and uses _Total.
It shows what the current read and write speed is on the drive, so if nothing is reading or writing to it will show 0 bytes.
Try doing a defrag with the monitor open and let me know :-)
Shane