weerzoetermeer schrijft:
Ik heb van dit soort problemen nog nooit gehoord. Hier werkt het al jaren zonder enkel probleem. Ik zou als ik jou was de maker van de software even een e-mail sturen. Wellicht heeft hij een oplossing?
Gr.
Thierry
Dit moet een oplossing zijn volgens de maker:
Ga het morgen eens proberen,maar post het ook hier mocht iemand het ook ooit krijgen:
Blue screen of death is usually caused by drivers. In this case, I think it's probably the N8VBvCOM driver that is causing the problem.
First, if you were using WeatherLink before, and had the USB connection option selected for the communication setup (instead of using the serial option via the Davis USB to Serial driver), that might also be a problem. WeatherLink puts the data logger into a special mode called USB Express. Once put in that mode, you can't use the USB to Serial driver anymore unless you run a little utility program to turn off USB Express mode in the data logger. Davis includes this utility program with WeatherLink, or you can download it from the Davis website.
Try uninstalling N8VBvCOM, and just install VirtualVP. In the Communication setup, turn off the 4 virtual consoles that use virtual COM Ports (the first 4 that use COM16-COM19). Turn on the 4 virtual consoles that use TCP/IP. After that, see if you can run VirtualVP and have it connect successfully with your weather station. You can also download the VPLive program from the SoftWx website, and have it connect to VirtualVP via TCP/IP to see if that works too. If you still get BSOD at this point, stop and email me a note of what you tried and what happened.
If this test runs successfully, then we can assume the problem is the N8VBvCOM driver. There is another driver like that which will also work with VirtualVP. It is called com0com. You can get it here:
http://sourceforge.net/projects/com0com/ . It is quite good, and I'm thinking of changing my documentation to recommend it instead of N8VBvCOM. Make sure you get the right version (32 bit or 64 bit) depending on your operating system. Let me know if this works or not. There is another driver we can try too, but I'll wait to see if this works for you before I describe that.
I get almost no reports of BSOD. I think in the past 3 years there has only been one other person that reported this. So I'm pretty confident we can get things running for you once we find the problem.
Steve
SoftWx
