So I updated to V2.50 (latest) - I had bought the upgrade quite a while ago, but had (been lazy) not installed. Restarted StrikeLink and in a few minutes, all was well asġ1:10 AM Found that my old GRLevel3 V1 would no longer work after 15-June due to a change in the NWS urls, Used GPSInfo to 'talk' to the new GPS, and it was working fine. I unplugged the old BU-353 from the system, and plugged in the new one. only the hardware replace will get StrikeLink GPS to work again.ġ0:30 AM The BU-353S4 GPS arrived. #ACROSYNC THROUGH WINDOWS INSTALL#If you install a 3.3x version of the driver it will get autoupdated to the 3.6 version which won't work. It uses Prolific PL-2303HXA chip which has beenĮOL-ed by Prolific, so the current Prolific drivers don't work in Win10 with that chipset. The new seems to cap it at 64MB for now, and fling 2.35 service runs about 2hrs before getting zappedĢ:34 PM Bad news discovered about the BU-353 GPS receiver for Boltek/NexStorm/StrikeStar. Had to fix my to use a wmic command instead of the SystemTools pslist command to get the info. Seems to be running, but is eating non-pageable memoryĪt a rapid rate. continue to have it submit data to WeatherBug and WOW since theyġ2:32 PM Adjusted fling to have minimum uploads. Turn off Cumulus uploads for files and realtime. Pruned back the uploads toĪutomatic for WeatherLink and Wasp2, and scheduled every 5 minutes for GRLevel3 and meteohub. #ACROSYNC THROUGH WINDOWS HOW TO#Have to rethink how to get the diverse set of stuff uploaded. 'may' offer scheduled uploads at intervals less than 1 hour.ħ:21 AM Fling 2.35 seems to work for a while, then holds on to the ports and starts 1and1 denying connections.ĭouble sigh. The Acrosync author said the next version (1.6) would remove the modal dialog for errors and Would loved to have used the rsync with Acrosync (a Windows rsync wrapper using ssh),īut it has a modal dialog box on error (stopping all uploads), and only hourly upload capability. We'll see if it works without constipating the FTPĬhannels with 1and1 (and doesn't have the memory leak issue). Couldn't get an answer from 1and1 on what constitutes 'excessive'īut it seems that somewhere between 6 and 8 connections is likely to set off their auto-block.Ħ:50 AM Paid the $49 to upgrade Fling to 2.35 version. So ties up all available ftp ports to 1and1 and stops uploading as 1and1 blocks ImageSalsa 2 is very old, and unlikely to ever be updated.Ħ:58 PM bad problems with fling 2.24 - seems to leave passive ports in time_wait status The native FTP just stalls out, so 'FTP Push' can no longer be used. Putting the netcam-thumb.jpg in the WeatherLink webfiles directory and Fling uploads it every 15 seconds. renamed c:\vws\WININET.DLL to old-WININET.DLL due to non-start of VWS.ġ0:59 AM ImageSalsa set to run in Win7 Compatibility mode - only copy file, no ftp. #ACROSYNC THROUGH WINDOWS .EXE#exe and now runs.ġ0:51 AM VWS set to run in Win7 Compatibility mode. Will try upgrade later.ġ0:47 AM VirtualVP didn't run. but runs in compatibility WIN-XP settings. GPS for Boltek/NexStorm/StrikeStar non operational.ġ0:40 AM Fling 2.24 has issue. (several reboots, some anxious nail-biting watching the progress meter)ġ0:35 AM - Prolific driver non-functional. Silly me, I thought I'd let Windows 10 bake long enough to safely update my 4GB/Core-i5 Win7-Pro weather station system to Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |