The HB server wasn't running when the second error message occured. I don't think that I closed it manually.
Please suggest a tracing method to find out what's wrong in my configuration.
I started the tracing because after some time of using HB (an hour or so), the computer hangs, and requires a cold reboot. At first, I suspected the PC hardware and installed on a different PC, but the same problem occured.
The send error is from a network connection failure. It is unrelated to you USB-UIRT problems. The actual error indicates that the connection was reset by the other system, which isn't really a situation that would occur normally. Maybe it's something with the network, or the 802.11 card(s) going into power save mode (or something like that) ?? You can enable the socket level tracking by selecting the "client" and "server" socket checkboxes on the Tracking Profiles dialog (From the main menu, Settings/Tracing). This may generate a lot of noise, but maybe something will surface.
You can enable tracing for the USB-UIRT from the Hardware Interface screen by clicking on the "Hardware Module Type" button and selecting the 'Enabled' checkbox. If it just stops responding, I'm not sure there will be any data in the trace to indicate the problem, but it's a good place to start. When you say stops responding, do you mean that it will no longer receive IR to decode, or no longer send IR?
Not much. I know there's a gremlin that shows on some systems (mostly Win98) when the client is exiting and closing the connection. I've never been able to duplicate it here, but that may be what you're seeing. Not sure about the panel change problem. That's a new one.
I also don't understand how the client and server can be having comm problems if they are on the same machine. For the SWRemote, is it using 127.0.0.1 for the IP or the actual machines IP address?
For the SWRemote, is it using 127.0.0.1 for the IP or the actual machines IP address?
I used the actual IP address with "software remote" (not the "local software remote") because using the local address 127.0.0.1 with the "local software remote" didn't work. I didn't spend time to find what is wrong with the local address.
Now that you mentioned it, I made further tests and came up with this:
The software remote name that I use is different from the default "Local Remote". Although I changed the software remote name in the configuration of the "local software remote", it was still looking for the default name. So I created a new software remote, named it "Local Remote", and now the "local software remote" loads successfully.
I'm not sure whether this issue is related to the other problems that I experience.