[BUG] Portable installation is broken in v8.0

[ayuanx]

---------------------------
FreeFileSync - An exception occurred
---------------------------
Installation files are corrupt. Please reinstall FreeFileSync.

Cannot open file "B:\abc\install.dat".

Error Code 2: The system cannot find the file specified. (CreateFile)
---------------------------
OK
---------------------------

[grad]

I'm getting a similar error. I have FreeFileSync portable installation installed into the Dropbox folder. On the computer it was 'installed' on it works fine, but on another computer Dropbox syncs to, I'm getting the following error when starting the application:

---------------------------
FreeFileSync - An exception occurred
---------------------------
Installation files are corrupt. Please reinstall FreeFileSync.

Consistency check failed for "C:\Dropbox\FreeFileSync\install.dat".
---------------------------
OK
---------------------------

[smaragdus]

The same error here, please see the screen-shot:

FreeFileSync 8.0 - 2016-03-17 - error - 001.png (8.42 KiB) Viewed 18978 times

I have been using FreeFileSync for years and I get such an error for the first time. I am going back to FreeFileSync version 7.9 which runs fine. I hope the problem will be fixed soon.

[radek]

Added in version 8.0, among others:
"Automatically check consistency of FreeFileSync installation".

[Zenju]

This is related to the installation consistency checks that are now included. FreeFileSync will test during startup if any data corruption occured to the installed files.

Portable usage should still continue to work if you install on an USB stick directly and move it between different computers, or if you move it to the USB stick manually via Explorer. But it may not work if the copying is done via Dropbox, in which case it needs to be installed on the other PC, too (either locally or portably).

[Seb_lau]

I've just reverted as well, having had the same issue using SyncThing.
This was a very stupid "feature" to make mandatory (no option to disable or continue despite this check?)
The whole point of using portable installs (for me) is so I DON'T have to manually install/copy/move a USB for every machine..

[ayuanx]

This is related to the installation consistency checks that are now included. FreeFileSync will test during startup if any data corruption occured to the installed files.

Portable usage should still continue to work if you install on an USB stick directly and move it between different computers, or if you move it to the USB stick manually via Explorer. But it may not work if the copying is done via Dropbox, in which case it needs to be installed on the other PC, too (either locally or portably).

No, unfortunately that's not the case here.
Any fresh installation selecting portable checkbox won't have "install.dat" file.
You may test it yourself. (Make sure you don't have any existing installation on the computer).

[radek]

Any fresh installation selecting portable checkbox won't have "install.dat" file.
You may test it yourself. (Make sure you don't have any existing installation on the computer).

Meaning we can only make a portable installation 1) on a USB drive and and 2) only if it's not installed on the hard drive?

[Zenju]

No, unfortunately that's not the case here.
Any fresh installation selecting portable checkbox won't have "install.dat" file.
You may test it yourself. (Make sure you don't have any existing installation on the computer).

When you close the FFS installation dialog, the file will be created (irrespective of portable/local installation type).

[ayuanx]

No, unfortunately that's not the case here.
Any fresh installation selecting portable checkbox won't have "install.dat" file.
You may test it yourself. (Make sure you don't have any existing installation on the computer).

When you close the FFS installation dialog, the file will be created (irrespective of portable/local installation type).

Come on, we are not idiots.
You just secretly updated the installation file a minute ago and refuse to admit it.
You think no one will notice but you forget that other sites have fetched the file before your secret update.

‎Original signing time: Wednesday, ‎16 ‎March, ‎2016 07:09:32
Updated signing time: ‎Friday, ‎18 ‎March, ‎2016 06:49:22

[ayuanx]

Just for the record, I don't know what you are trying to hide, but apparently you secretly added some code to record (or collect?) user's information. What exactly it is for, we have no idea yet.
Because for this part of the code, you deliberately hid it and did not put into the source code you provided.

I suppose 99.99% of people won't notice since few people would bother to read the source code.
I reckon I wouldn't normally, but this time you made me do that.

I am aware you might secretly change the source code file again.
FreeFileSync_8.0_Source.zip 2.83 MB (2,976,767 bytes)
I hope you intentions are good.

[zlhnxqgf]

Just for the record, I don't know what you are trying to hide, but apparently you secretly added some code to record (or collect?) user's information. What exactly it is for, we have no idea yet.
Because for this part of the code, you deliberately hid it and did not put into the source code you provided.

Can you provide some details? I would like to check it myself.

Portable usage should still continue to work if you install on an USB stick directly and move it between different computers, or if you move it to the USB stick manually via Explorer. But it may not work if the copying is done via Dropbox, in which case it needs to be installed on the other PC, too (either locally or portably).

Are you serious? Why do you want to ruin your reputation with such changes?

[Zenju]

updated the installation file a minute ago and refuse to admit it.

record (or collect?) user's information

Jesus, ayuanx... yes, the 8.0 release was updated (twice!) to fix small showstopper bugs during the installation. These bugfixes don't affect users who have already installed 8.0 with success, so there is no need for a 8.1 update. Why these trivial upates make you throw wild accusations is beyone me. Please don't troll and keep the discussion based on facts.

[ayuanx]

updated the installation file a minute ago and refuse to admit it.

record (or collect?) user's information

Jesus, ayuanx... yes, the 8.0 release was updated (twice!) to fix small showstopper bugs during the installation. These bugfixes don't affect users who have already installed 8.0 with success, so there is no need for a 8.1 update. Why these trivial upates make you throw wild accusations is beyone me. Please don't troll and keep the discussion based on facts.

Like I said, I hope your intentions are good. But I couldn't find the part handling this "install.dat" in source code, which caused this installation failure in the first place.

[Zenju]

But I couldn't find the part handling this "install.dat" in source code

This part is handled in the installer, which is not open source. As for the installation failure, is this still reproducible? If yes, I'd like to analyze what's going on.

[ayuanx]

But I couldn't find the part handling this "install.dat" in source code

This part is handled in the installer, which is not open source. As for the installation failure, is this still reproducible? If yes, I'd like to analyze what's going on.

No. The creation part could be in installer. But the read and verification part is in "FreeFileSync_XXX.exe".
I could read the assembly, but I don't want to spend time on it when there is supposed to be open source code ....

[zlhnxqgf]

But I couldn't find the part handling this "install.dat" in source code

This part is handled in the installer, which is not open source. As for the installation failure, is this still reproducible? If yes, I'd like to analyze what's going on.

But FFS complains if the file is missing or its consistency check fails so where to find these checks in the source code?
Would you please explain to us why you added them even though the portable usage is crippled now?

[zlhnxqgf]

No comment on the checks and source code? Are these questions inappropriate or just tiring?

[ninj_marx4]

FreeFileSync is a great tool no doubt but i have to agree with zlhnxqgf & ayuanx. If you want to keep your good reputation please keep things open source.
And the silent updating of a version is really annoying. Now there is a 3rd Version of 8.0 signed on 20 March. That's just confusing for everyone.

Hope you can fix this Zenju and still kudos for your great tool!

[andreiv]

I can confirm this issue. I keep FreeFileSync on my Dropbox and use it on 3 computers. It works on one of them (the one I installed it on) but it fails with the error mentioned here on the other 2.

[Zenju]

As always, nothing is cast in stone, but the current 8.0 design is to only allow installations via the official installer with some leeway for the portable version. To clarify this, it's still possible to install FreeFileSync portably on an USB stick, carry it to another computer and use it there, or move it locally from one location to another. But it won't be possible to simply copy the files from one PC to another without an installation. This was done to leverage the importance of the FreeFileSync installer with it's single(!) and optional(!) advertisement, which is still the backbone of the project's financing.

I think I've also written this somewhere in the FAQs but with the number of users that FreeFileSync has, it has turned into something more than a hobby. So the time needed, not only for development, but also the tons of project management work done behind the covers, has to make at least some economical sense. Currently this means having the ad in the installer (but also donations; thanks so much to those who donated!) even despite the controversies about it (althout most of them originate from thinking principle rather than actual issues: come one, is clicking the decline button really that difficult?). As an alternative there now is also a version without advertisements for everyone who donates. Maybe this could be the best solution in the long run as everyone can choose for himself what FFS is worth to him, while avoiding the conundrum of coming up with a price for a tool that has *free* in its name...

I'm sorry for the silent bug-fixes, but these are a last resort in case of show-stopper bugs that only affect a small number of users. If they didn't affect only a small number of users it would naturally be resolved via a completely new release. If it wasn't a show-stopper bug, users could wait until the next update has arrived. But if the problem is a rare installer-bug as there were unfortunately a few with the 8.0 release, it doesn't make sense to have the majority of users reinstall when the issue doesn't concern them. Not fixing the bug is also bad since it leads to a lot of needless support requests about an issue already solved. It's a compromise for this particular case.

[ninj_marx4]

Thank you very much for your explanation! I accept your reasons and hope you keep up the good work!

[zlhnxqgf]

It all makes sense, thanks for the honest answer! I guess a clear statement on the ad-bundled setup would have been better in first place than just "Automatically check consistency of FreeFileSync installation" as a reason.
Too bad it's unusable as a portable app in cloud storage then, so I'll just stay with 7.9 for now.

[FileHoarder]

I have donated early on - and also recommended the software to others who told me they donated. Then had to cope with tons of aggravation because of your malicious practice to include crapware WITHOUT stating this up front - as other more honest developers usually do. This gave your product a very bad reputation over the many years you've been doing this.

So here are my questions:
- what is the minimum donation to qualify for the safe version?
- are previous donors not eligible for the safe version?
- for how many future updates does a donation guarantee access to the safe version?

[zlhnxqgf]

So here are my questions:
- what is the minimum donation to qualify for the safe version?
- are previous donors not eligible for the safe version?
- for how many future updates does a donation guarantee access to the safe version?

will I need to make another donation every time I want to get a new version?

Yes, you will have to donate again for the 8.0 release. But the good news is you can still choose the price yourself.

[fred_be]

I especially registered an account to say that

- I use FFS on a computer where I have limited OS permissions, and CANNOT run an installer.
- I typically install FFS update on my personal pc in portable mode, then move the files over to the target computer

I'd be disappointed if that is no longer possible.
I haven't tried 8.0 yet, but from this discussion, it sounds like this is no longer allowed usage. That would be a shame :-/

thanks very much for the useful software.
regards

ps: does the donate-no-ads version have the same restriction?

[ektorbarajas]

Hi.

I also use it the same way as fred_be

can this be fixed?

For now I have to stay with version 7.0

[_svobodniy_]

As always, nothing is fixed in stone, but the current 8.0 design is to only allow installations via the official installer with some leeway for the portable version. To clarify this, it's still possible to install FreeFileSync portably on an USB stick, carry it to another computer and use it there, or move it locally from one location to another. But it won't be possible to simply copy the files from one PC to another without an installation. This was done to leverage the importance of the FreeFileSync installer with it's single(!) and optional(!) advertisement, which is still the backbone of the project's financing.

- I use FFS on a computer where I have limited OS permissions, and CANNOT run an installer.
- I typically install FFS update on my personal pc in portable mode, then move the files over to the target computer

I use it in the same way. So, I returned to FFS v7.9...

[FileSyncExpert]

I also changed back to Version 7.9
No more Updates with this Restrictions...

[ektorbarajas]

Will this annoying issue be fixed for version 8.1 ?