(Subject was: wineinstall problems at creation of config-files)
Ok, today I got less lazy and found function of interest:
/usr/src/wine-cvs/wine/server/registry.c:1114:fprintf( stderr, Line %d: %s
'%s'\n, info-line, err, info-buffer );
Function name seems to be file_read_error.
Plainly
On Friday 30 April 2004 13:31, Saulius Krasuckas wrote:
(Subject was: wineinstall problems at creation of config-files)
Ok, today I got less lazy and found function of interest:
/usr/src/wine-cvs/wine/server/registry.c:1114:fprintf( stderr, Line %d:
%s '%s'\n, info-line, err, info-buffer
On Fri, 30 Apr 2004, hatky wrote:
basicly he says this patch is the problem:
http://cvs.winehq.org/patch.py?id=12187
sounds right by what the patch is about, didn't try reversing it yet
Hm, maybe.
Though I finally figured out on how to debug wineserver:
[EMAIL PROTECTED] s2]$ gdb -q --args
On Friday 30 April 2004 06:31 am, Saulius Krasuckas wrote:
(Subject was: wineinstall problems at creation of config-files)
Ok, today I got less lazy and found function of interest:
/usr/src/wine-cvs/wine/server/registry.c:1114:fprintf( stderr, Line %d: %s
'%s'\n, info-line, err,
I was having this problem too, I just stuck
[HKLM\\Machine\\Software\\Wine\\Wine\\Config]
at the top of my config file and that seemed to fix it
Oh, 1,000 10x my lord
Can someone patch the installed config to have this?
--
Hatky,
Worshiper of wine (http://www.winehq.org/),
Impossible is
I was having this problem too, I just stuck
[HKLM\\Machine\\Software\\Wine\\Wine\\Config]
at the top of my config file and that seemed to fix it
:(,
now I get just the segfault ...
--
Hatky,
Worshiper of wine (http://www.winehq.org/),
Impossible is only an opinion.
