WXforum.net
Weather Software => VP Tools (Virtual VP, VP Live, and VP Tools) => Topic started by: Blizzard on June 27, 2016, 01:29:22 AM
-
Hi,
I've been using VVP on Vista to run simultaneously VWS and WL 5.9. Everything is working fine. Just got a brand new more powerful computer equipped with windows 10. Will it work if I use the latest versions of these suftwares? I'm keeping my old PC as a backup while I work on the new one. Other tools than VVP would work better considering it is old. Thanks for your help.
-
I would recommend switching to all IP communications between VVP and the other software. As long as you leave your console firmware on the older non V3, it should continue to work.
The biggest issue you would run into is the virtual COM port function no longer works unless you buy some new ones that are compatible with Windows 10.
-
If I understand well, the way I'm set up under Vista would work Windows 10 ? See screen shot [ You are not allowed to view attachments ]
-
It looks like you are only using IP coms, so you should be able to replicate it on the new PC. The only thing you might need to do is turn your UAC off, and setup VVP to run as administrator all the time.
I think that should be it. Mind you, I'm still running Windows 8.1, so I haven't personally tested it on Win10.
-
Super! What's UAC ? As for running VVP as administrator, I should figure it out...
Tx
-
User Access Control.
http://winaero.com/blog/how-to-turn-off-and-disable-uac-in-windows-10/
http://www.cnet.com/how-to/always-run-a-program-in-administrator-mode-in-windows-10/
-
What software is better to use than VVP these days?
-
We installed Win10 here. VVP works great as long as I started with Run as administrator.
I have it on TCP/IP and have had no issues.
My computer is imaged with school software and school permissions.
-
Bunty, if you're referring to software to "split" the Davis signal out so that other software can simultaneously access it, there isn't anything.
-
Kind of surprising that no one has jumped in where Steve left off with their own software fully compatible with the newer equipment. By that I figure it must be pretty complicated and time consuming to code and get it to work and work reliably running 24/7. :-(
I have to wonder if maybe out of all the Davis users if there are at least a handful of people out there running their own home brew program that just don't want the headache of supporting users if they were to make their software available to the public.
-
Kind of surprising that no one has jumped in where Steve left off with their own software fully compatible with the newer equipment. By that I figure it must be pretty complicated and time consuming to code and get it to work and work reliably running 24/7. :-(
I have to wonder if maybe out of all the Davis users if there are at least a handful of people out there running their own home brew program that just don't want the headache of supporting users if they were to make their software available to the public.
Would you blame them? Especially if they provided it for free.
-
Ideally, it would be nice if Davis just made the IP logger such that it would accept multiple connections.
-
Ideally, it would be nice if Davis just made the IP logger such that it would accept multiple connections.
Is that even notionally possible? AFAIK Davis have never disclosed what's inside an IP logger but I'm not sure that it's even got its own microcontroller, let alone the microprocessor and operating system that it would presumably need to function effectively as a multi-client data server, ie to have the intelligence to buffer and update the weather data and then to service multiple 'simultaneous' incoming requests for that data.
-
I would guess they'd more likely have to do it internal to the console (perhaps cheaper to do by adding additional functions to the processor already in there) as well as redesign the logger to carry the additional traffic. :-k
-
I would guess they'd more likely have to do it internal to the console (perhaps cheaper to do by adding additional functions to the processor already in there) as well as redesign the logger to carry the additional traffic. :-k
That may well be what happens already with the IP logger. But I get the impression that the console CPU and associated resources like RAM are already pretty much maxed out so that would require a major redesign of the console. I can't see that happening with VP2, but who knows what son-of-VP2, if and when that eventually appears, will look like (though I suspect that its architecture will be different from a super-WLIP).