Bit by the Tcl/Tk socket bug

Recently I bought a Dell Axim wireless with the intention of turning
it into a custom remote control for my home automation system.  I
already had written a server (in Tcl/Tk) which controls the system and
a client (also in Tcl/Tk) which runs on various PC's around the house.
 Using the Tcl/Tk 8.4.4 binaries for WinCE ARM that Jeff Hobbs created
a couple of years ago, I was able to port a version of the client to
the Axim and had it up and running in a couple of days.  The client
works by opening a socket, sending a command to the server, receiving
the reply and then closing the socket whenever there is a request from
user input.  Works great - once.  Unfortunately, after the socket
transaction, the program aborts after displaying a messagebox of "tcl:
select: 10022".  After some Googling, I learned that others have also
seen this problem (even described in the Wiki), but I haven't found
where anyone has a solution.  Obviously, sockets are an integral part
of the program - without reliable socket communication the program is
useless.  I have spent the last few days looking at alternative
approches to writing the client and the best I have found so far is
eMbedded Visual C++.  Since I've never used that before, it will
probably take me at least a couple of months to get up to speed and
duplicate what I did in a couple days with Tcl/Tk.  Does anyone have
any thoughts on a solution that either fixes the Tcl/Tk socket problem
or offers an easier programming solution than wading into the Visual
C++ approach?

Thanks,
Dave





------------------------ Yahoo! Groups Sponsor --------------------~--> 
Most low income households are not online. Help bridge the digital divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->