Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ANNOUNCE: Windows Inspection Tool Set 2.0.1 Beta

3 views
Skip to first unread message

pal...@yahoo.com

unread,
Feb 26, 2007, 9:06:50 AM2/26/07
to
Windows Inspection Tool Set (WiTS) 2.0 Beta has been released.
The release is supported on Windows 2000, XP and 2003.

See http://wits.magicsplat.com for details and downloads.
See https://sourceforge.net/project/screenshots.php?group_id=90123
for a sample screen shot.

Changes since the 1.1 release
----------------------------------

* New event monitor - track in real time
process start/exits, network connections,
new logons, system resources and more
* New view for kernel drivers
* Configurable list views with selectable columns
* Significantly improved performance
* and more...

See http://wits.magicsplat.com/versionhistory.html for
a complete list of changes.

If you are upgrading from an earlier release, please
uninstall it before installing the new version.

What is WiTS?
-------------

WiTS provides you with cross-linked, filtered views of a
Windows system. These views include customizable list views
with optional filtering and sorting capabilities, and
detailed property page views for individual objects. Where
applicable, views are linked to allow for easy navigation
between related objects.

In addition to viewing properties, WiTS provides tools for
some common tasks related to these components.

WiTS also includes a configurable event monitor that can notify
you of various events like new network connections, process
starts and exits, service state changes, system resource
exhaustion and more.

WiTS starts up automatically and installs itself into the
system tray in the taskbar. In addition, it can be
configured with hotkey support for quick access to various
views.

Currently supported object types include:

* Operating system and hardware
* Processes
* Services
* Users
* Groups
* Logon sessions
* Drives and volumes
* Local and remote shares
* Network interfaces
* Network connections
* Printers
* Loaded modules
* Drivers

Jeff Godfrey

unread,
Feb 26, 2007, 2:07:06 PM2/26/07
to
<pal...@yahoo.com> wrote in message
news:1172498810.5...@q2g2000cwa.googlegroups.com...

> Windows Inspection Tool Set (WiTS) 2.0 Beta has been released.
> The release is supported on Windows 2000, XP and 2003.

Ashok,

It's been quite a while since I last looked at WiTS. I just installed
the latest release and it looks *really* nice. It's vastly improved
over what I saw previously. Thanks for what appears to be a great
utility program (and for the twapi package the powers it). Question -
is there somewhere I can grab the latest WiTS sources via http/ftp? I
switch from CVS to SVN about a year ago and no longer have a running
CVS client.

Thanks for any pointers.

Jeff


pal...@yahoo.com

unread,
Feb 26, 2007, 7:42:30 PM2/26/07
to
I'll look at making a zipfile or something available.
But in the meanwhile you can open a WiTS Console (Tools and Options
menu in main window), and type

file copy [info nameofexecutable] DIRECTORY

- that should copy all sources into DIRECTORY.
WiTS.exe is just a Starpack

/Ashok

On Feb 27, 12:07 am, "Jeff Godfrey" <jeff_godf...@pobox.com> wrote:
> <palm...@yahoo.com> wrote in message

Jeff Godfrey

unread,
Feb 26, 2007, 8:06:26 PM2/26/07
to
----- Original Message -----
From: <pal...@yahoo.com>
Newsgroups: comp.lang.tcl
Sent: Monday, February 26, 2007 6:42 PM
Subject: Re: ANNOUNCE: Windows Inspection Tool Set 2.0.1 Beta


> I'll look at making a zipfile or something available.
> But in the meanwhile you can open a WiTS Console (Tools and Options
> menu in main window), and type
>
> file copy [info nameofexecutable] DIRECTORY
>
> - that should copy all sources into DIRECTORY.
> WiTS.exe is just a Starpack

Thanks. The above is all I really need. I had originally assumed
that WiTS was packaged as a standard Starpack and had attempted to
mount it using the "VFS Explorer" tool provided with Tcl Dev Kit (my
raw sdx skills are a bit rusty after having acquired Tcl Dev Kit a
while back). For some reason I couldn't get the EXE to properly
mount, and therefore assumed that you had done something a little
different. Now, after having read your above response, I just tried
to mount it again. This time, all went as expected and I can navigate
the source just fine. I'm not sure what happened the first time.

Anyway, thanks.

Jeff


0 new messages