FreeCommander Forum

There are several similar dialogs on every start here.



OK, so the numbers are from 3 to 6, I suspect my card reader, it has 4 drives without disk, but there should be no dialogs, it was OK in previous versions.

626, win Vista 32 bit.

Fixed for the next release.

Confirmed, thanks.

I never had this error before Dreamer reported it for 626. I also did not have it with 626.
I did get the error starting with 628/629 where it should have been fixed.
In my case it was for Floppy drive A: (regardless to any Floppy drive settings I tried: don't show, exclude etc. )

With the default test config there was no error.
Switching back to 626 and earlier also fixed the problem.

So it looked like some setting was causing the issue.
I started to swap in and out the various config parts from Freecommander.ini between my version and the clean test version.
I found the culprit was in the [forms] section.
I then compared the erratic [forms] section against the clean one with Winmerge and started to merge the differences from the clean to the erratic version.
As I was in a hurry to get my config working again I can't tell which setting it was exactly - I changed about 5-6 settings before it started to work again.
After that it was working with my merged old config also for 629.
I don't know if Dreamer had this error also with a clean config.?

To sum it up: I got the error only with my old config and a new 628/629 exe that could be fixed by a ini manipulation.
Just as a hint.

Strange, I don't have any error dialogs now with old ini or clean install.

I don't know if Dreamer had this error also with a clean config.?

Yes, I had that problem with old ini and clean install in 626, but it was with a card reader, floppy - A: and B: drives were disabled permanently.

If you will have any problems with this, please start a new topic.

No problem anymore after i changed something in my ini.
I just wanted to mention this as it appeared strange to me that a fix for your problem caused the very problem for me which I never had before.
No need for a new post, all peaceful now

just for documentation, this error just occurred to me as well, my fix was to just delete the old ini file and create a new one. I do have the old ini file, which throws the error, if someone wants to reproduce this issue.

br,

Martin