Re: OT-- should I defrag???

Sadly, I predict that Microsoft will either kill off any versions of the
SysInternals tools for future Windows releases, or put a pretty retail cover on
them and sell them in a cheap cardboard box as part of some Admin toolkit.
They'll also mess them up by making it impossible to run them with older
versions of Windows. This is how the borg assimilates. It's been done in the
past. The best one can hope for is that all the Sysinternals programs will find
their way into a full Windows release some day. This is a fool's dream, because
Microsoft's long time tendency is to take away access to the internals of the
system for the unwashed public.

Your defense is to download all the Sysinternals tools while you still can do so
for free. Maybe some ftp site will archive copies of them for downloading.

I can't accuse Russinovich of selling out. He made a business deal in his own
self-interest. I would, too, given an opportunity... Ben Myers

On Tue, 08 May 2007 04:32:56 -0500, Journey <rainbow@xxxxxxxxx> wrote:

On Mon, 07 May 2007 22:30:07 -0700, Nicholas Andrade
<sdnick484@xxxxxxxxxxxxxxxx> wrote:

Ben Myers wrote:

CCleaner, which is a politically correct name for Crap Cleaner, does a far more
thorough job, removing useless files and getting rid of the obsolete entries in
the Windows registry. Then, Microsoft's own PageFileDefrag defragments the
registry files, but you better get this one before it disappears from the
Microsoft web site, fully assimilated by the MicroBorg. Microsoft bought Mark
Russinovich and SysInternals, the original developers of PageFileDefrag and a
host of other useful little Windows tools.



Sysinternals was great, and I hope MS doesn't ruin it. Another great
defrag tool they offered is Contig [1] which lets you target single
files for defragging. My favorite tools by them are TCPView (basically
a live GUI for netstat) and Process Explorer (Taskman on crack). Some
of their CLI utitilies are good, and with a proper PATH set can make MS'
DOS prompt actually useful (esp. when combined with Cygwin).

[1] http://www.microsoft.com/technet/sysinternals/utilities/contig.mspx

I use a variety of Sysinternals tools, the most recent is PSTools. I
use it to kill processes after Windows starts up. It's probably more
efficient to stop processes from running using msconfig or another
tool, but I like to see what processes run on default. I also like to
better document what a process does and I can do that in a .bat file
which uses PSTools to kill processes. In all my code a goal is to be
self documenting. I can also kill different sets of processes. I can
also kill processes that don't want to die multiple times, such as AOL
processes, which won't be an issue once I get rid of my P4.

I have never used the defrag tools but don't know if they are Vista
compatible.

I predict that MS is going to ruin the Sysinternals. Maybe they saw
it as potential competition and wanted control over the utilities
rather than have a "rogue group" develop their own. By assimilating
them (Ben is brainwashing me) MS can let them fade. Hopefully this
won't hold true.
.

Relevant Pages

  • Re: Matching window handles and open file handles
    ... >> apparent to me. ... > It uses undocumented parts of Windows and obviously they don't want us to ... Obviously Microsoft does not want to tell us either. ... Sysinternals also has a product called "Handle" that does pretty much what I was trying to do. ...
    (microsoft.public.vb.winapi)
  • Re: Cant kill some processes
    ... "The Sysinternals web site was created in 1996 by Mark Russinovich and Bryce Cogswell to host their advanced system utilities and technical information. ... Microsoft acquired Sysinternals in July, ... and over again just to use the internet. ... Why can't I kill a process in task manager as easily as it is in XP??? ...
    (microsoft.public.windows.vista.general)
  • Re: "the worm" patch
    ... have to kill msblast.exe again. ... Now relax and try to get the update to install. ... Kent W. England, Microsoft MVP for Windows ...
    (microsoft.public.security)
  • Re: Should Bill kill Windows?
    ... The best thing Microsoft could do for themselves, at this point, is to ... kill of Windows, and write something new. ... Windows into a Classic-like virtual machine for backwards compatibility. ... recover even from a mistake that wastes six years of development time. ...
    (comp.sys.mac.advocacy)
  • Re: Should Bill kill Windows?
    ... The best thing Microsoft could do for themselves, at this point, is to ... kill of Windows, and write something new. ... Windows into a Classic-like virtual machine for backwards compatibility. ... recover even from a mistake that wastes six years of development time. ...
    (comp.sys.mac.advocacy)