IPNetMonitor 2.4.2 conflicts with Virtual PC 4

It appears that IPNetMonitor 2.4.2 prevents Virtual PC from running, at least in some circumstances. Aaron Shepard writes:

"IPNetMonitor 2.4.2 on installation places an OTModl$Proxy extension in the System Folder and modifies a resource in the TCP/IP Preferences file. After installation, the ReadMe file tells you that this has been done and warns that the only way to remove the resource is to use the original installer to uninstall, or use ResEdit to change the file back. This modification prevented Virtual PC 4.0.2 from running on my G4 Yikes with OS 9.0 and Open Transport 2.6. Attempts to launch gave an "out-of-memory" message, no matter how much memory was given to Virtual PC. Uninstalling IPNetMonitor with the supplied installer solved the problem.

Tech support at Sustainable Softworks says the incompatibility may be due to a bug in 2.4.2 that was corrected in 2.4.5, which correctly synchronizes the Network Setup database with the TCP/IP prefs. I leave it to others to test this theory."

Note: the most recent version of IPNetMonitor is 2.5c8.

Update: Several users report that they have successfully used VPC with IPNetMonitor 2.4.5 and later. Evidently the problem has been fixed.