winecfg: creating new .wine-directory results in errors

snejjj · Post by **snejjj** » Tue Jan 31, 2012 12:02 pm

When I create a new .wine-directory from scratch (old one moved or deleted), winecfg generates the following output:

$ winecfg
wine: created the configuration directory '/home/jens/.wine'
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:iphlpapi:NotifyAddrChange (Handle 0xfce8fc, overlapped 0xfce8e0): stub
wine: configuration in '/home/jens/.wine' has been updated.

did I something wrong while installing wine? (did install it via package-manager some time ago) do I miss some packages or something like that?
should I file a bug about this?

Thanks for your replys!

my Wine-Version is still 1.3.37

Post by **dimesio** » Tue Jan 31, 2012 3:32 pm

That's normal terminal output when a wineprefix is created. Don't worry about it.

snejjj · Post by **snejjj** » Wed Feb 01, 2012 9:40 am

Okay thanks for your help!
just out of curiosity: if those errors are not problematic, why are they there anyway? is this some functionality not yet implemented in wine? or just some minor bug that hasnt been fixed as it doesn't pose a problem with using wine?

jjmckenzie · Post by **jjmckenzie** » Wed Feb 01, 2012 11:44 am

On Wed, Feb 1, 2012 at 7:40 AM, snejjj <[email protected]> wrote:

Okay thanks for your help!
just out of curiosity: if those errors are not problematic, why are they there anyway? is this some functionality not yet
implemented in wine? or just some minor bug that hasnt been fixed as it doesn't pose a problem with using wine?

Fixme's are just that: Something that needs to be fixed, usually
missing or partially implemented Windows functions.

There is a workaround if you don't want to see them:

WINEDEBUG=-all <Wine command>

However, if the program fails, you will only see the failure and not much else.

James

snejjj · Post by **snejjj** » Wed Feb 01, 2012 2:48 pm

There is a workaround if you don't want to see them:

WINEDEBUG=-all <Wine command>

It's not that I don't want to see those errors, it's just that I was worried about the errors that are there besides the fixmes.