topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Tuesday April 23, 2024, 5:44 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ExodusDev [ switch to compact view ]

Pages: [1]
1
Mini-Reviews by Members / Re: WhyReboot?
« on: December 22, 2006, 10:20 AM »
How about adding something to the program that warns,

"Warning:  You've managed to get a ton of programs hanging in memory that probably shouldn't be there and eating memory and disk cache.  Your computer will keep getting slower until you do a restart!"

But seriously, any way to add something that could check for the issues that cause this type of slowdown? 
Maybe a baseline at startup, and then warn when some limit is reached?
<snip>
Am I being silly? :-\

No, I don't think you are being silly in wanting something like this.  I'm not sure it fits the 'mission' of WhyReboot - that is, to tell you if an installer really did do something that justifies a reboot.  (Perhaps I mis-named WhyReboot...)  Anyway, I'll consider the feature request.

In my experience, there's no need for an external utility to tell me that there are too many apps running - I just hit ctrl-shift-esc to bring up the task manager, look at the process list (configured to show the VM size and other memory items - see attached screen snapshot).  Then, from that view, you can terminate apps that are taking up too much memory. 
taskman-process.jpg

This is another subject that I've written about - the sheer arrogance of software providers adding junk to your startup lists and taskbar tray thus bringing even the most powerful machines to a crawl.  I've written a simple command line utility (XP or Windows 2003 server only at present) that scans the system tray and tells you what's running there, and the name/location of the .exe file behind it. 
system-tray-icons.png
More later...




2
Mini-Reviews by Members / Re: WhyReboot?
« on: December 21, 2006, 11:26 AM »
Michael!

Great to see you stop by - I should have updated this post when I saw that WhyReboot? was being updated recently.

Thanks for a great program, it really is a must have little tool.  :Thmbsup:
Thanks for the kind words.

I know I've not done anything substantial with WhyReboot for quite some time... its interesting, it was flying 'under the radar' (this site, and about ten others, had linked to it) for a few years, then, all of a sudden in January '06, we got tons of sites linking in - mainly due to digg.com and LifeHacker.com listings, among others.  My old site got hammered for a few days (see attached chart at end of this post, or click here to go to alexa.com.)

In any case, I appreciate your feedback, I take pride in making useful stuff, so it's always nice to know that people find WhyReboot useful.

3
Mini-Reviews by Members / Re: WhyReboot?
« on: December 21, 2006, 12:04 AM »
yeah it reports a couple more registry things...

but it brings up a reasonable point - whyreboot? hasn't been updated in over 2 years and it's a very simple program..
i wonder if a good coding snack might not be to implement this and look for any other registry keys or files that might be useful to see.
not sure there is anything to update but could if so it would make a good coding snack.

As the author of WhyReboot, I wanted to drop in and say "hi", and address this issue.

First, I've just updated WhyReboot - it's now available on my new site, http://exodusdev.com/products/whyreboot (please update your links, and please avoid linking directly to the downloadable file, because the name/location of the file may change as I update versions, etc.)

The recent updates are cosmetic, but I will be looking at improving the program's functionality if it makes sense.

I've done little with WhyReboot because it fulfills its purpose -- to tell you about pending file operations that are scheduled to happen after a reboot.  The methods used by Windows to control pending file operations have not changed as far as I know.  So, no need to update WhyReboot.

It might be possible to expand the scope of WhyReboot, to include other configuration changes that take place after a reboot, but I'm not sure that adds much value.

Anyway, feel free to visit our new site (http://exodusdev.com) and we plan on adding a forum for WhyReboot-related topics and other issues. 

Regards,

Michael Curry
http://exodusdev.com

Pages: [1]