Thu Feb 02, 2017 9:48 pm Post
Tue Mar 21, 2017 1:55 pm Post
Tue Mar 21, 2017 10:05 pm Post
Wed Mar 22, 2017 12:26 am Post
cpm5280 wrote:Response to this issue so disappointing. Making new user profiles is hardly something anyone should have to do, and more than visiting forums every few weeks to check on solutions is.
Seems to have dropped off the radar. We're nearly six months after last update, and I'm writing in Notepad when on my desktop machine.
Sun Apr 23, 2017 9:20 pm Post
glosfor wrote:If you are feeling brave, you can attempt a test. Note that this test is ONLY useful if you have run "Scrivener.exe --log" and seen repeated "RegEnumValue failed" errors getting logged. Do NOT attempt this test for any other Scrivener problem, as there is a risk that this will cause problems with products other than Scrivener.
It should probably go without saying, but I'm going to say it anyway: When making changes to your system that are proposed by anonymous guys on the internet, use at your own risk.
glosfor wrote:1) If you don't already know, figure out whether you are running 32bit or 64bit Windows.
2) Launch RegEdit (if you don't already know how, this test may not be something you should try).
3a) If you are running 64bit Windows, look for HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID
3b) If you are running 32bit Windows, look for HKEY_CURRENT_USER\Software\Classes\CLSID
4) Make ABSOLUTELY CERTAIN you are looking at "HKEY_CURRENT_USER", not "HKEY_LOCAL_MACHINE". Editing HKEY_LOCAL_MACHINE (or some other key that is "kinda like" what I list here) would be VERY, VERY BAD (like "trash your computer" bad). If you are at all unsure (or cannot find the EXACT key described), do not proceed.
5) Use Edit/Rename to rename the CLSID key to ScrivenerTest.
6) Try to launch Scrivener.
7) Whether the launch succeeds or fails, immediately return to RegEdit and rename the ScrivenerTest key back to CLSID before doing anything else. Be careful you don't add a space after CLSID (easy to do if using copy/paste).
glosfor wrote:Let me emphasize this: Even though this might fix your Scrivener problem, do NOT leave this key renamed. There's no way to know what all is using that key. But whoever it is, they will be unhappy if it is missing, and there's no telling what bad things might happen as a result.
glosfor wrote:If you attempt this test, here are the things to report:
1) Did you run the "Scrivener --log" test and see the "RegEnumValue failed" message?
2) Did your computer have the exact CLSID key described in steps 3a/b?
3) Did Scrivener successfully launch after you renamed the key?
4) What version of Windows (7? 10?) are you running? 64bit or 32bit?
5) Are you (like me) running any of the Tortoise* tools for software version control (TortoiseSvn, TortoiseCvs, TortoiseGit, etc)?
glosfor wrote:What this will tell us:
The problem here probably isn't due to any of the programs that use that registry key (although it might be, which is why I'm asking about Tortoise). Collecting a list of installed programs we have in common might be interesting.
But mostly what I expect to learn is that everyone who is getting this QSettings message has this key. The key is not always created (or needed), which is why creating a new profile works for some people: The new profile doesn't have this key.
However if (as I expect) renaming this key solves the problem for people, then L&L will have an easy fix they can apply to their software (fixing their copy of the QT toolkit as I described at the top of this thread). If the L&L people are uncomfortable making the change, I can post a corrected copy of the childKeysOrGroups routine (but you'll still have to rebuild the QT library yourselves).
Unfortunately I can no longer run this test myself, since Scrivener is no longer failing to launch on my machine. Darn the luck...
Mon Apr 24, 2017 1:00 am Post
Tue Apr 25, 2017 8:52 am Post
glosfor wrote:You say that scrivener is creating a registry key for Rnvrcs.dll. I'm seeing that too. However what I don't see is a file named Rnvrcs.dll anywhere on my computer. Googling for this file and the associated clsid all seem to relate to malware.
Do you actually have an rnvrcs.dll file?
Sat Jun 24, 2017 11:32 am Post
In total there are 4 users online :: 0 registered, 0 hidden and 4 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 4 guests