September 15th, 2004, 11:09 AM
Global Caché driver problem?
since the release of 220.127.116.11 I am using Global Caché as my main IR transmitter. About at that time the problem began, that from time to time - about every 2-3 days- the network card in my PPC stopped working. This had never happened before, so I am pretty sure, it is connected to NR and GC.
When this happens, I have to pull the Network card, wait for the drivers to unload and plug it in again. Alternatively I can reset my PPC.
Is there anybody else who is using the GC and is experiencing the same problems?
I have to add, that I am using the same network card for months now without any problems before and didn't change anything except switching from DirectIR to GlobalCaché.
Could it be there is a leak somewhere in the GC driver that could cause this?
BTW. The "hang" issue is still there in 18.104.22.168 .in case there should be a change.
September 15th, 2004, 01:52 PM
As you know, I use also GC but jointly with the usb-uirt.
I do not have this kind of problem with my network CompactFlash card.
September 18th, 2004, 08:57 AM
I'll take a look, Wilhelm. This sounds weird that it would lock up your network card, but I guess anything is possible.
If you were to stop NetRemote and start again every day, does it go away? I'm not saying this is a solution, I'm just wondering.
September 18th, 2004, 10:21 AM
This will take me at least a week to test, but I will try.
September 20th, 2004, 09:47 AM
I can tell you, that stopping and starting NR has no effect on the WLan-Card.
Nevertheless that doesn't say anything, does it?
The problem with forgotten stop commands to the GC gets more and more annoying every day. Sometime NR stops sending completely, but then stopping and starting NR makes it working again. You have to use GC in productive mode, to get all of it's flaws. So there are two symptoms here. One is, that the card stops working completely, and one that NR stops sending codes to the GC.
I beg you, please look into the GC plugin source again! Since I cannot reproduce the problem exactly, I cannot give you a log or anything.
The problem with the first code not getting sent after a long pause also is still there. I just got accustomed to the fact, that I have to press the first button twice..... But this doesn't help with macros, because they get sent leaving the first code out. So it's not the input, but the output that gets screwed up. (with DirectIR it works anyway...)
I really hope you will fix this soon.
September 23rd, 2004, 07:58 AM
I'm looking into this to see what could be the issue. I do not use my GC fulltime, but will set it up to try so for a week and see what I dig up.