New release! Port Explorer v2.100

v2.100 of the premier port-to-process mapper is now available, please help us spread the word
http://www.diamondcs.com.au/portexplorer/

New changes/additions are described in the helpfile, mostly user-requested features, various enhancements and several bug fixes which we've been working on mainly over the last few months. Needless to say this is a 100% FREE update! If you have a previous version of Port Explorer installed then you must uninstall and reboot your computer before installing this new version.

Thanks to everyone who contributed ideas and suggestions, and thanks to the beta testers who provided valuable feedback over the final stages

ps. The website has been updated to reflect the new version but there are some things such as screenshots which havent been updated because we'll be releasing a new diamondcs.com.au website very soon, complete with several new free tools

 

Got it installed here and Works Great as Usual!!

Thanks DiamondCS and looking forword to the new Products!!

Cheers,

 

Excellent!!!!

I just did.

 

Sweet!

 

Working fine thanks. Note: If you’re using an AMD 64 with DEP switched on for all progs, you have to turn it off for port explorer by adding the PE .exe to the ignore list, else PE will fail to start.

 

Hrm, the driver in the new version seems to cause my system to hard lock. Sometimes during boot up, sometimes after. Uninstalling remedies the problem. This didn't happen in the 'beta'..

 

No lock up here or with the beta!! XP Pro SP2

HTH,

 

Anyone care to post a list of changes in the new version because I want to see whether it's worth installing and rebooting twice for. To get to the changes I have to read the help file which means I have to install it and I want to know beforehand so if someone can post the changes I'll have a look to see if it's worth 2 reboots or not.

Thanks

Dave

 

I also just noticed that there is a some type of conflict with a packet sniffer that I use on occasion - NetworkActiv PIACTFM. With the new version of PE installed it simply won't work. Start it listening and it immediately goes to a stopped state. Happens after the PE 2.100 install. Remove PE 2.100 and all is well. This application worked fine with all earlier versions of PE. No idea whether this behavior occurs with other packet sniffers.

Blue

 

It seems this new version causes more problems than it resolves so I better not touch it. The previous version works fine so unless there's really good reason I see no purpose in upgrading.

Dave

 

Perhaps you can post the changelog for those of us who don't want to upgrade in order to find out what's new?

 

From the Help File!!

Cheers,
--------------------------------------------------------------------------------
What's New in Port Explorer
v2.100 September 28, 2005

Improved/cleaner directory structure.
Windows have improved size/re-sizing/size-remembering code.
User settings (window size etc.) now saved to HKEY_CURRENT_USER in the registry so that they're remembered on limited accounts.
Close minimizes when minimize to systray is enabled.
Exit while main window is maximized now scales the splitter in main to be correct for next start.
Main maximize / restore scales location of splitter.
Splitter between PD list and PD contents added to Socketspy.
Socketspy numberings starts at 1 instead of 0.
Logs are now stored into log subdirectory by default.
Slightly altered and improved logfile output order.
More consistant packet numbering between windowlog and filelog.
Logging of specific (chosen) tab(s) from main list.
Windowlog etc. shows correct filepath associated with PID in cases where the PID didn't exist by the time winlog etc. read it.
Added 'spy all' feature to socketspy.
Winlog shows packet was spied on.
Process history logs.
Auto restart after correct key entry.
NEW TABS
Closing Down
Process Log
And LOTS of tweaks, user requested improvements and small bug fixes.

 

Thank you for the changelog T.Helix; most helpful for posting the update on the other forums!

 

The hard locking of my system turned out to be bad memory, which I didn't expect from 6 month old Kingston RAM. It's definitely not bug-free, though.. the log window still acts weird on my system. I don't understand why there wasn't a 2nd beta release before going final, just to be sure of things.

 

Notok,

All problems submitted to us during the beta test were fixed. We've actually only had a couple of users email us since the non-beta release saying there are problems so although a few people in this thread have experienced problems the vast majority of users haven't reported any problems at all, we have had a lot of positive feedback though so we're not too far off. Having said that clearly it's not quite perfect just yet and there are also some new features we'd like to add when we get some more time, but most people should get a much better experience from this new version.

Judging from the overwhelming positive feedback we've received and the very few problem reports this build seems more than stable enough for now - certainly more stable than previous builds, so we're concentrating on releasing an update of ProcessGuard before coming back for another round with Port Explorer. We hope to release a beta update for ProcessGuard in the next week or two, although one of the current hurdles is reverse engineering the completely undocumented NtCreateThreadEx function so we can add support for Microsoft's new Vista operating system (codename Longhorn) ... this is not fun, but a worthy challenge as it has never been done before

Anyway I better get back to work, thanks for all the feedback guys it's very much appreciated

 

Is there gonna be an update to the help file soon? I wanted to read more about the new Process Logs and the various features under the Settings menu relating to it.

And also how Tab Logging and Process Logging differs from the previous Log features.

(Edited to add email notification for thread.)

 

Wayne,

I do like the latest version. Seems to be working great. Thanks!

By the way, regarding the sticky entitled "Socket Spy Not Showing Up" that was posted in Oct 2003, has this issue been addressed in the latest release? I have not experienced this problem, but since this thread containing a single post was still so prominently displayed, I was curious if it had been fixed.

 

Excellent upgrade.

Cheers CDS.