Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  1. Thanks, Guylain, the license did work again. However, I ran into a catch-22 issue, and had to give up. The problem is that for some reason, the first time I connect the camera, and launch the app, the app always gives an error when connecting. However, if I quit and re-launch the app, it connects fine (probably because of the old drivers for the old camera; I know it is probably a support nightmare for you). So, when I activate inside the house, then go out and connect to the camera (which is mounted on the scope), it won't work. Then, if I quit and re-launch the app, it says it needs the internet connection to use the trial license, so I have to disconnect from camera to come back into the house. I discovered a different strategy to get things to work for me for now, just using the interval timer function in the EOS utility software. I am going to go that route for now; however, I know in the long run I am going to need something like your software, so at that time I may come back and take this up again. In the meantime, please feel free to de-activate my trial license for now. Sorry for the bother, and hope to get back here sometime in the future! Who knows, maybe even sometime soon, if I get frustrated with the EOS utility (which is not purpose made for astro use).
  2. Ah, I see. And, it will not have some limit on the number of re-validations?
  3. Hi Guylain, Looks like we posted at the same time. Will I not have the same problem with the paid version?
  4. Thanks S3igell & Astroman. Couple of points: 1. The license re-validation happens every time, even when I have internet access (on the bench). Am I to understand correctly that with a paid license, it would not happen? Can the developer assure me on that? The error that it gives is something like "Invalid fingerprint fount. Need to re-validate", or something like that, which leads me to believe it is not just routine revalidation. I am worried that the same thing may happen even with the paid version, which would make it rather useless for me. 2. My configured path for saving captures is a shared folder between the VM and the Host. Both have full access to the folder. Is this likely to cause a problem? The thing I am precisely trying to check is if I can capture using the 32-bit VM and process it in the host using SharpCap. This is essential to my use case.
  5. Hi, as mentioned in another thread, I am trying to make BackyardEOS work in a Virtual Machine to get 32-bit functionality. I installed it in Windows Vista 32-bit. Everything seemed to go fine. My trial license worked, and I was trying to get everything to work with my old camera. However, I have encountered the following problems with respect to License validation. 1. Whenever I restart my VirtualBox, the license has to get re-validated. This is a big pain, since I am usually in a place in my backyard where the WiFi doesn't reach. So, I have to unplug everything, and come back into the house to get the license validated. 2. After a few iterations of this, now, the license will not validate at all. I get the error: Unexpected character encountered while parsing value: <.Path", line 0, position 0. I tried uninstalling and re-installing BYE. No help at all. Weird thing is, it was working fine for a while (albeit with problem #1), and now it won't work at all. My BYE version is 3.1.17.
  6. Hi admin, Let's say for argument's sake that I was using Win10-32 bit natively on my machine. Would BYE then work without need for additional drivers? Hi astroman133, I cannot figure out a way to get at the Canon archives, they make it impossible to find. Where could I get an older version of the EOS utility? I already installed the oldest version I could find on their site, and it does not help.
  7. Hi, I downloaded the trial version, and am trying to connect my Canon 350D (which I have modified for Astro purposes, with IR Cut filter removed, hence the interest in using the old camera). I have Win 10 64-bit. I understand that the camera won't work under 64-bit. So, I installed a Virtualbox inside Windows, and installed Win10-32bit in the Virtualbox as the guest OS. Then I installed the BYE inside the Windows-32bit. Then, I made sure that the USB port was passed through to the Virtual machine. The 32-bit OS does say that the Canon camera is visible in the Device Manager. However, it does have a Yellow triangle saying there are no Device Drivers installed. Also, BYE does not still connect, and gives the same connection failure box as it did with the 64-bit Host machine. Is there a way to make this work, or am I out of luck? Do I need to install some drivers. If so, where do I get them? Needless to say, I have no original disks for this old camera!
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use