9 replies to this topic

[Random]

lately I get a lot of those, even though everything seems to be working fine, is that any thing to worry about?

cheers

[doh123]

you'll need to be much more descriptive about what you mean

[Random]

Everytime i test run a wine-wrapper, the first line of the log says "user.reg is not a valid registry file".
In a topic in winehq someone suggested it might be caused by a broken wine-prefix, so I temporarily renamed the /.wine folder, but still got the same error.
Is it something I should ignore or does it affect the wine-registry?

[doh123]

~/.wine is the default wineprefix for normal wine.

Wineprefix in a wineskin wrapper is the Contents/Resources folder... but you never want to delete that.  If you want to remake it from scratch, you use the Wineskin.app -> Advanced -> Tools tab -> Rebuild Wrapper button, but you'll lose everything you've done with Wine in that wrapper..everything installed, etc... it'll trash the three .reg files (including user.reg) and all of drive_c and rebuild it.

[Random]

huh weird, cause I tried that on a fresh wrapper (still got the error).

Is it possible that the user.reg template (if there is one) is corrupted? Cause I get the error in new every wrapper since it came up.

[doh123]

weirdo, on 22 August 2012 - 02:56 PM, said:

huh weird, cause I tried that on a fresh wrapper (still got the error).

Is it possible that the user.reg template (if there is one) is corrupted? Cause I get the error in new every wrapper since it came up.

there is no template... its generated from scratch when the wineprefix is built on creation or rebuild.  Wineskin also edits this file for certain settings that need to be done... but I've never seen that error before, or heard anyone say they got it.

[Random]

(btw the message disappeared when I rolled back to 2.5.4)

[doh123]

I still need to know how to reproduce this problem to be able to do anything about it.

[Random]

Unfortunately I'm not really sure, I remember having had a regedit crash on one wrapper while importing several .reg files of which one might have been
wrongly formatted - the weird thing is though, that from then on it happened in all newly created wrappers - I decided to roll back to 2.5.4 when on some wrappers
general settings that were supposed to be stored in the registry were reset every time I opened them, along with the above debug message in the log.

I just found a wrapper where it still persisted (2.5.6) - updated to 2.5.7 -> same message - rebuild wrapper -> same message - deleted user.reg -> fixed.

I pasted you the faulty user.reg, but if I'm the only one who had this problem it's probably neglectable.

http://pastebin.com/vaqVdN7s

[Random]

(Hm, weird, I just tried again with another wrapper,
and none of the above steps solved it [just deleting, updating and deleting, rebuilding and deleting], - a freshly created 2.5.7 wrapper
is fine though)