Problem Description:

Several of our customers have recently reported sightings of files being created on their Windows XP (SP2) "Desktop" while they are uploading files to Punch WebGroups. These files have "gibberish" names (for instance "909e889v"), as pictured:

"Gibberish" files on desktop

Investigation Underway:

We have tracked this issue down to the Microsoft implementation of the Java VM, which relies upon a local "cache" for our Java Applets to operate. Technically, this cache mechanism involves reading and writing object data into a Microsoft VM for Java specified location buried within the all-powerful (and much-feared) "windows" directory (typically located at C:\windows\). A recent Microsoft issued security patch prohibits programs from automated actions within this windows directory; this prohibition apparently includes even their own implementation of the Java Virtual Machine.

Solution:

The work around at this time involves switching your browser settings from relying upon the Microsoft VM for Java to using the more current Sun VM (which you can download from http://www.java.com/download/).

What to do:

1. Go to the Internet Explorer "Tools" Menu and select "Internet Options"
2. Select the "Advanced" Tab
3. Scroll the settings until you see reference to "Java (Sun)" - be sure it is selected/checked, and that anything under "Microsoft VM" is de-selected/un-checked., as pictured below:
   JAVA Settings in Internet Explorer

More information:

Customer Comment: "Previously I have been instructed that Punch WebGroups only supported the Microsoft VM for Java. Now Punch WebGroups only supports Sun's Java! What's going on?"

For many of our long-time customers, this Sun VM requirement is a reversal from the position we have taken regarding Java Virtual Machine vendor preference over the last 5 years. We have recently made several changes to how our applets are invoked within Internet Explorer, which allows our Java Applets to successfully rely upon the Sun VM (version 5 or later). We finally decided to make this change as we approach Microsoft's declared "end of life" date for the MSJVM which is December 31, 2007 (reference: http://www.microsoft.com/mscorp/java/).