View Single Post
Old 12-26-2014, 11:39 AM   #50
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,742
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by AlanHK View Post
It would be too simple to use the same folder the program is in.
Like Unix, Like DOS. Where you can find and back them up and fix them when they screw up.
Actually, lots of unix/linux programs store user data in hidden subdirectories (or hidden files) in the user's home directory. Global configuration might be in /etc, But user-specific stuff will typically be in .local or .config under ~/. Separate, user-writeable data directories for individual programs are fairly common practice on all platforms nowadays.

Also keep in mind that Sigil 0.6.x will use the same data directory and hence, same Sigil.INI, as 0.8.2. Probably not a good idea to have two different programs writing to the same file/directory. I'd uninstall both versions, delete the 'sigil-ebook' directory from Local Settings\Application Data and the reinstall 0.8.2 (and ONLY 0.8.2). Then if the problem continues, backup the Sigil.INI file and start removing entries from it (one at a time) and trying to start Sigil each time. That way you can track down which INI setting is preventing Sigil from starting.

You can try tracking down/removing Sigil registry entries before reinstalling, but like someone already mentioned, there's really no Sigil registry entries of any consequence that would likely cause issues like this.

Last edited by DiapDealer; 12-26-2014 at 11:42 AM.
DiapDealer is offline   Reply With Quote