[Coco] Drivewire4 - Java problem

[Bill Pierce]

Aaron, the "no java shutdown" thing is happening on TCP, not serial port (Coco 3 still broke), so it has nothing to do with the serial port driver unless dw4/java is still monitoring the serial port even though I'm configured for TCP (????). As I said, this was working one day, then a reinstall of windows and java on the next day and now java takes a long time to exit. All versions (windows, java & dw4) are the same as the day before. Windows was also updated completely before any installs. It was also fully updated before the reinstall. This becomes really annoying when you crash dw4 while messing with "ui" cmds and need to restart the GUI. I have to wait 10-15 minutes before I can run dw4 again.
The only thing that was different was that the UAC (user account control) was on. I have only a single user set up and this is not needed. It runs your software in it's own little "shell" and protects files from being used by other users. When I noticed this was on, I also realized that none of the "original" VHDs were being updated, only the "protected" copies. Once I turned the UAC off, I uninstalled and reinstalled both java and dw4 to make sure they were properly set up as UAC screws up everything.

I have all the multiple instance cmd line options you told me about before. The problem with this seems to be if I run a TCP connection as the default instance, then no "Serial Ports" are selectable in the 2nd instance. They are greyed out.
If I run a serial port for the default instance, then I can choose "TCP" for the 2nd instance. That works.
The first configuration (TCP then serial) worked before. I think I started noticing this behavior somewhere around version 4.3.3k or 4.3.3o, so this happened recently before all the reinstalls and is dw4 related.

Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com




-----Original Message-----
From: Aaron Wolfe <aawolfe at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Sun, Sep 1, 2013 9:31 am
Subject: Re: [Coco] Drivewire4 - Java problem


This may be more an aspect of your serial driver (if using a USB serial
adapter, I would not expect any issue with "real" uarts).   Drivewire asks
the serial port to close as it is exiting.  Usually this happens instantly,
but some driver/adapter combinations seem to wait several seconds before
returning from the close request.  The UI tells the server to exit and then
exits itself without waiting, so the java process you see running could be
the server sitting there waiting for the close call to finish.   If
possible try getting the most recent driver, might fix it.

> Multiple instances of DW4 are not happening either. Before, I could run