BackyardEOS or EOS utility will not connect

[astronut80920]

I just purchased BackyardEOS premium today after running the trial to evaluate.  Now when I start Backyard EOS, it will not connect and neither will EOS Utility.  Both worked fine in the trial after I resolved the problem with the MTP USB device driver (I had to download and install it).  The error I am getting when I check the device driver is this: "Insufficient system resources exist to complete API".  I am using an ASUS 10" 2-in-0ne laptop.  Windows also tells me I already have the correct driver installed.  I have BackyardOS installed on the 500GB SSD drive D:, not the C: drive.  The C: drive has only about 250MB available so I install programs on D: instead.  The Trial ran just fine in this configuration so I am at a loss to figure out why the purchased premium version does not, obviously it's a Windows problem.  How do I fix this driver problem.  Do I have to search and eliminate other programs to regain resources in order for this to work?  I am not a technical guru.   I really don't want to ask for a refund, I like the program.  Please help.

 

Thanks,

 

Jim Lawrence 

[astroman133]

Jim,

 

As you surmised, the issue has nothing to do with BYE. This is borne out by the fact that the EOS Utility does not connect with the camera either. Also, the Trial and Premium versions are running the exact same software. Only the license code is different.

 

So something else changed on the system around the same time as you switched from the Trial to the permanent license. Are you using the same installation of BYE, with only a license change, or did you uninstall and re-install BYE? Was it originally installed on the D: drive?

 

You said that Windows has "the correct driver installed". I don't know how you came to that conclusion, but I would double-check.  Is the camera listed in the Windows Device Manager after the camera is plugged into the PC and powered on? The "Insufficient system resources..." message indicates that there is a resource constraint that may be preventing the driver from loading. The issue could be due to lack of free space on the C: drive...250MB is not very much!

[astronut80920]

Rick,

 

I did not uninstall the trial version.  I simply installed the premium version on drive D:, same one where the trial version is still installed.  I did not delete the trial, assuming the premium version would overwrite it, maybe that was a mistakee.  Windows said the correct driver is installed when I went into Control panel/portable devices to check the MTP driver.  The camera is listed in the device manager.  I agree about the C: drive space.  I am currently checking that now.  It is weird that many times I will see about 2 GB on the C: drive and as I use the laptop, I check drive space and it slowly shows less and less space as I work,so I go in and try to clean up so it gets more space, but always does down in space, I don't know why.  Because of the lack of C: space is why I install programs on the 500GB D; drive as  much as possible.

[astronut80920]

Problem resolved on it's own, and that's scarry because problems that "self fix" for no apparent reason  sometimes tend to reappear later.  I guess we'll just have to wait and see.  What I did was uninstall and reinstall BYE.  First startup try didn't work.  Then another problem appeared, my network decided to disconnect, and I couldn't reconnect so I shut down the laptop and reconnected. Then, strangely enough, EOS Utility started and so did BYE with no indication why.

[admin]

If EOS Utility was not connecting then the issue was between the camera and Windows. Nothing related to BYE trial or purchase keys. So my guess is that you had a driver issue. Probaly the MTP driver and a reboot probably fixed it.

[astroman133]

You did not need to re-install BYE to go from the Trial version to the Premium version, you only need to start BYE (the trial version) and apply the permanent Premium license, replacing the trial license.

 

In any case, it is working now so the point is moot. I just mentioned it for anyone else who may read this thread.