Registax-6 hick-up?

[Dirty Harris]

Hi Guylain, this may not be the place to submit this question, but I'd like to get the forums input about an issue. I have over the years used Rgistax6 for processing my videos from my DSLR and BYE. Also used AutoStakkert-2 as well. A short while back we had a computer crash, no real biggie as almost everything was backed up, except Registax6 & AutoStakkert 2. But since they're free downloads we simply downloaded them both onto new computer (h/p intel CORE i5 7th Gen) long story short, everything is back up and running. However, when I use Registax6 or AutoStakkert-2 a pop-up screen comes on at the start saying "Unable to write to program files (x86)" both programs continue to process without any problems, so whatever it is doesn't seem to affect processing, but I've never had this happen before!! I contacted "Corland Berrevoets, at Registax6" he said there have been a few reports of similar events, but not an epidemic, just a few isolated cases. He suggested to run the program as "Administrator" which we did, and it helped at first, but occasionally the pop-up returns. I've chosen to ignore it like your "Check Engine Light" on your dash until something manifests itself. I realize this is more a computer or program issue and nothing to do with BYE, but my curiosity is this, has anyone else out there experienced any similar issues with Registax6 after a recent download? Thanks again, regards, and clear skies your way, Dirty Harris, Colo. USA.

[s3igell]

This is a common indication that Windows has some problem with the User File Privileges in the Program Files (x86) directory, or as likely a problem with the routine that an Older Program (Registax 6 was last updated in 2011) is using to access Files stored in those directories.  Over the years and versions of Windows, Microsoft has changed their rules on where and how Access to certain Directories is Allowed / Controlled: Program Files is more restricted from use to store User Data, ProgramData directory was added as alternative, User AppData was also added as an alternative, and rules related to Registry usage were changed.  That's a lot of changes pursued by Microsoft in their efforts to keep Windows as Safe and Secure as possible, while maintaining as much Backwards Compatability as possible.

Unfortunately, Older and Unsupported programs such as RegiStax6 and AutoStakkert2 are showing their age and running afoul of these issues.  Workarounds such as "Run-As Administrator" will sometimes work, but not always.

In your case, the most likely effect is that certain settings you choose in RegiStax6 will not be retained across execution instances, and you'll simply have to add to your workflow to check/set those settings every time you use the program.

For better or worse, this is the reality we live in as we pursue a hobby which is heavily dependent upon Freeware and Shareware and Open-Source Software, where Developers eventually move on with their lives and interests and are no longer available to actively support the products which the community has come to count on.  This is one reason why a healthy set of Commercial Programs - such as BackyardEOS/Nikon - are important to our hobby, as it helps to retain the attention and talent of the Developers who contribute to our hobby.

[admin]

Another options, is to try and copy the installation folder outside the Program File folder to something like "C:\RegiStax6" and try to run the program from there.  These older software may work just fine like that and this may solve your issue. 

[Dirty Harris]

Thanks  "s3igell" and Guylain too! This forum is the greatest! Yeah, the answers you've given are spot-on and logical. Its as though the pathways that we've used for years and years are now being blocked or have become corroded somehow. And Guylain I'll try running the program outside the usual pathway and just see if that helps? Thanks again for the prompt reply, best regards, and clear skies your way, Dirty Harris Colo. USA.

[AaronSmall]

Dirty Harris,

One thing I did after a recent HD crash was to set up a separate directory for these programs that seem to have permission issues or that just start from simple directory (AS!, FireCapture, Registax, etc.).  This is placed under my main user directory and called 'Programs' (I prefer that term over the newer 'apps').  This keeps the permissions and the main (c:/) directory structure clean.  It also allows for later transfer and/or backups to get settings files, etc.

BTW, solid state harddrive was the best investment ever.  Many times faster. 

Aaron

[Dirty Harris]

Quote

Thanks Aaron for the info. may just do that, upgrade the HD on this h/p laptop as well as download or copy to some other folder/file than C:\ program files (x86).