FreeCommander Forum

I recently updated FreeCommander to 2008.06c and I run it portably, from a USB flash drive.

Three times now on WinXP SP3 and at least once on Vista Home Edition, I've randomly received "error reading registry" errors. That's the entire text of the error message.

Each time, I had just succeeded in opening files (of any kind, it appears to make no difference) then suddenly the error pops up for no apparent reason, and I can't open anything further in FreeCommander until I re-launch it. Files open just fine from Windows Explorer or from File> Open in a running program.

But why is this error even occurring? Does FreeCommander use the registry while running, and just clean up after itself when closed? (Closing also sometimes generates "memory could not be read" errors. Next time that happens I'll try to remember to take a screenshot.)

I haven't seen anyone else reporting such errors, and I'm not sure what to do to try and debug it, or what additional information might be useful.

Any thoughts?

I've tried replacing the software, but that didn't help. I'm seeing this problem daily and there appears to be no discernible pattern. It's very frustrating, because I'll be going along hard at work, and all of a sudden am interrupted by FreeCommander's inability to locate or open any files. I like FreeCommander -- a lot! it's amazingly powerful -- but it has become difficult to use because I can't rely on it. Why registry errors?

I'd be grateful for suggestions on how to track down the problem, but please keep in mind I run FreeCommander portably and am using my employer's computer.

FreeCommander do not use the registry directly. All settings are saved in the freecommander.ini. How you open the files: double click, enter key, open from context menu? Have you admin rights?

Marek wrote:FreeCommander do not use the registry directly.

That's what I thought... which is why this is such a puzzle.

Marek wrote:How you open the files: double click, enter key, open from context menu?

Just double-click (unless I want to choose a different program to open the file... but since I don't do that very often, I'm not sure if it happens with that method).

Once I get the error, I can't open any files. Sometimes I have to close and re-open FreeCommander a few times before it will start working again.

Marek wrote:Have you admin rights?

Yes, on both XP and Vista.