Quote:
Originally Posted by hellonurse
That's involved, but at least you had a reason to do that. I just run the program a couple of times without installing anything and then saw all those .azw, .pobi and .kobo, together with Windows going, like, "I was told there's a new program for your .chm's and .pdf's, which one do you want?" Anyway, I don't really care as long as there's a way to prevent that.
What I still don't get is the Unix-inspired logic of using CALIBRE_NO_DEFAULT_PROGRAMS and other settings *only* as environment variables. It's not even that it feels a bit wierd on Windows, like, PROCESSOR_ARCHITECTURE=AMD64, NUMBER_OF_PROCESSORS=4, CALIBRE_NO_DEFAULT_PROGRAMS=1. It's more that it seems reasonable for the program to also be able to look for settings in some kind of 'calibre.ini' file under 'AppData\Roaming\calibre' (normal mode), 'Calibre\app\resources' (portable mode) or something along those lines. Also, in the portable mode, it could be used to eliminate the "if you want to run calibre in portable mode, use calibre-portable.exe" requirement.
|
For the Unix inspired logic? Perhaps you have not noticed that calibre is multi-platform? It runs on Windows, Linux and Mac OSX.
Why do you keep complaining that the non-portable version of calibre does not behave like a portable app? Did I miss the memo that said unpacking an non-portable installer and running executables directly is how to generate a portable mode application? There are reasons that calibre has a Windows x64, Windows x86 and portable installer. So quit trying to claim that the non-portable version of calibre should behave the same as the portable version.
If you want to continue to use calibre in a non-standard mode, depend on yourself for tech support.