cronlazersnow.exe won't run

Dennis, I’m just grasping at straws but is your LRDemo program set on “centimeters” and set to read “continuously”? If this doesn’t resolve your problem maybe MikeyM or some other cronlazersnow user can chime in with some ideas for you to try.

Good luck!

Brian; Yes I have rebooted the PC, even tried cronlazersnow along with AtUsbHid.dll and LRTimeLog.exe in the same folder on another computer, not sure if that is a valid test. But got the same results, error in cronlazersnow.

Jeff; For me LrDemo starts up in Single Measurement Mode and that setting is not “saved” unless “Save to Rangefinder” is pressed. I was hesitant to write to the rangefinders nonvolatile memory, however being desperate, I saved the Continuous Measurement Mode. But it didn’t help.

Note; I have also written to Richard at Porcupine Labs asking for help.

Thanks,
Dennis

Dennis, I’m running out of ideas. My cronlazersnow is running fine with the Windows 7-64 OS. I’m running WD Version 10.37S81

Maybe share this forum link with Richard at Porcupine Electronics.

Good luck!

maybe try a different USB port

That was the very first thing I tried before even coming here for help.

Dennis

Dennis,

In your WD folder there should be a file called “AtUsbHid.dll”. What is the date/time of this file and what is the size of the file? Mine and MikeyM’s is dated 6/20/14, 10:22 pm and is 72 KB in size.

Jeff,

Yes that is what I have also,

Dennis

I wonder if has something to do with a Windows 10 update that has occurred since last season … I’m running out of ideas. #-o

I received a reply from Richard of Porcupine Labs.

From the relative lengthy description of my situation I sent, he does not feel there is anything wrong with my LR4 rangefinder. Quite frankly, I have to agree with him as all his utilities run and work properly.

Although Jeff’s suggestion to send a link to this forum was a good one, I did not as I had already sent my email. And I’m not sure it would help as Richard would have no idea as to the internal workings of cronlazersnow, which is primarily what this discussion is about.

Dennis

there might be another way
where the LRTimelog.exe is run to output the data to a file (which WD reaeds in) instead of to the console
if you run that program from a command DOS prompt and use
LTTimelog.exe → outfile.txt

I just got out an old laptop that I haven’t updated Windows 10 since May of 2018 and cronlazersnow runs properly.

It is Windows 10 Version 1709 Build 16299.125.

I cannot use this laptop as my as my Weather PC but I can use it to test cronlazersnow.

My thought is to now update this laptop to the current version of Windows 10 to confirm my cronlazersnow issue is due to an update. Is there information I should gather to assist troubleshooting before doing the update?

Dennis


I can now confirm, my issue with cronlazersnow occurs after the Windows 10 October 2018 Update, version 1809, is applied.

With version 1803 and prior cronlazersnow works fine. After updating to version 1809 cronlazersnow errors trying to open the USB LR4 rangefinder.

Dennis


there might be another way where the LRTimelog.exe is run to output the data to a file (which WD reaeds in) instead of to the console if you run that program from a command DOS prompt and use LTTimelog.exe -> outfile.txt

Brian,

I guess I was hoping that now that you know there is a problem between your cronlazersnow and the current version of Windows 10, that you might be able figure out how to fix/update cronlazersnow.

In response to your “there might be another way”, I don’t understand how to pursue this.

  • How do I get WD to input outfile.txt especially since it’s output is formated differently.
  • It’s my understanding, that a file from a programs redirected output remains open by the OS until the program ends, so this output file is unavailable until LRTimeLog is ended. So I would have to start/stop LRTimeLog for every reading.
  • LRTimeLog creates its on log file however this, also, is not available until LRTimeLog ends.

Please attempt to update cronlazersnow to be compatible with Windows 10.

Dennis

Please attempt to update cronlazersnow to be compatible with Windows 10.

Windows has made breaking change
I can’t actually perform miracles

what was working, was the ability to be able to share the usb connection, i.e cronlazersnow was piggy backing on the LRTtimelog incoming data flow
windows has it looks like stopped that USB sharing ability
by the looks
and there is not much I can do about that
there might be some setting somewhere in windows (USB settings or similar) that can be tweaked
maybe google?

Is the interface HID or serial?

Niko

It’s HID

MikeyM

I thought Microsoft had pulled 1809 due to lots of problems my laptop still has 1803 on it

Does the order in which the programs are started make any difference ?

You are right - and according to Microsoft the only people to have had problems were those who had “requested” the update before it was offered to them. Moral: never, EVER, select “Check for updates” in Windows Update.

However, I just found this: “On November 13, 2018, we will begin the re-release of the Windows 10 October Update (version 1809), Windows Server 2019, and Windows Server, version 1809. We encourage you to wait until the feature update is offered to your device automatically.”

Here we go again. . .