No it didn’t, sorry I wasn’t clear.
What’s strange, is I haven’t really changed my configuration since everything was working last winter. Other than an occasional WD & Win10 update. I just plugged in the sensor and attempted to start cronlazersnow. and was baffled when it wouldn’t run. Which I now believe was due to that version of cronlazersnow not able to handle the error I’m getting.
Also, all of the Porcupine util’s work with no errors/problems.
And WD may actually be working without cronlazersnow showing it. Ive been busy with visiting relatives so I haven’t paid close attention. But it looks like cronlazersnow starts LRTimeLog which appears to be feeding the measurements to WD’s snow input screen.
I’m not sure if cronlazersnow.exe can run standalone (including AtUsbHid.dll) without a WD installation, but I tried it on another Win10 PC and got the same symptoms; cronlazersnow runs posting the error, but when started, runs LRTimeLog like it should.
I’m hoping to be able to spend more time with it tomorrow.
Dennis