April 2004 - Wine-Devel - list.winehq.org

RegEdit problems

by Krzysztof Foltman

During deployment of some Linux desktop setup I had a major problem with WINE's regedit. First, I don't seem to be able to edit the (default) values of the keys (if they don't exist already ?). Second, the Modify dialog has Cancel as its default button. Third, there is no Find function. There are also some weird error messages in unexpected places. Is anybody working on it, or should I try it ? Using native regedit is not an option, as our goal is to avoid being a BSA victim completely. Krzysztof (who can't continue the RichEdit before getting the damn desktop to work)

April 29, 2004

how can i solve this problem???

by Falcifer

fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,2)-stub! fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,3)-stub! fixme:hook:NotifyWinEvent (32774,0x20049,-4,1)-stub! X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 73 (X_GetImage) Serial number of failed request: 21212 Current serial number in output stream: 21212 fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,2)-stub! fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,3)-stub! fixme:hook:NotifyWinEvent (32774,0x20049,-4,1)-stub! X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 73 (X_GetImage) Serial number of failed request: 21212 Current serial number in output stream: 21212 ----------------------------------------------------------------------------------- Any clue?? Its very important cause if i can run this corporative application in Linux all the firm will migrate gradually to Linux. Thanks

April 29, 2004

Re: CVS Invalid path for c:\\Windows

by Alexandre Julliard

"Brett I. Holcomb" <brettholcomb(a)charter.net> writes: > Yes. I just did again and it doesn't work. Same error. Something got > broken again I guess. Path entries from the config file are no longer used. Check the contents of your ~/.wine/dosdevices directory. -- Alexandre Julliard julliard(a)winehq.org

April 29, 2004

Re: CVS Invalid path for c:\\Windows

by Brett I. Holcomb

Yes. I just did again and it doesn't work. Same error. Something got broken again I guess. On Wed, 28 Apr 2004, Duane Clark wrote: > Brett I. Holcomb wrote: > > I installed from CVS today and when I start wine I get the error below. > > This happens even with the standard config file that it creates. I've > > check both my and the config file and can't find any errors. I'm > > including the c drive part of the config file. > > > > Any ideas why this is telling me this? > > > > Thanks. > > > > Error: > > > > Invalid path L"c:\\Windows" for L"windows" directory: does not exist. > > Perhaps you have not properly edited your Wine configuration file > > (/home/brett/.wine-cvs/config) > > > > Config file excerptL > > > > [Drive C] > > "Path" = "fake_windows" > > "Type" = "hd" > > "Label" = "MS-DOS" > > "Filesystem" = "win95" > > > > Have you tried an absolute path: > "Path" = "/path/to/fake_windows" > > -- Brett I. Holcomb

April 29, 2004

[PATCH] Exception c0000005 opening JPEG files in FoxPro

by Sergio López

Hello, When Visual FoxPro (tested with versions 6 and 7, wine-20040408) tries to open a JPEG file, it crash showing a c0000005 exception. The backtrace of winedbg shows the following API calls: 0 0x407c0e1d (CURSORICON_SimulateLoadingFromResourceW+0x8d(filename=0x403e63b0, fCursor=0x1, res=0x4074a208, ptr=0x4074a20c) [cursoricon.c:512] in USER32.DLL) (ebp=4074a1d0) 1 0x407c1d0d (CURSORICON_Load+0x28d(hInstance=0x0, name=0x403e63b0, width=0x20, height=0x20, colors=0x1, fCursor=0x1, loadflags=0x50) [cursoricon.c:799] in USER32.DLL) (ebp=4074a21c) 2 0x407c4ba0 (LoadImageW+0xb0(hinst=0x0, name=0x403e63b0, type=0x2, desiredx=0x20, desiredy=0x20, loadflags=0x50) [cursoricon.c:2133] in USER32.DLL) (ebp=4074a258) 3 0x407c4a8f (LoadImageA+0x14f(hinst=0x0, name=0x4074a370, type=0x2, desiredx=0x0, desiredy=0x0, loadflags=0x50) [cursoricon.c:2074] in USER32.DLL) (ebp=4074a334) 4 0x407c39b5 (LoadCursorFromFileA+0x45(name=0x4074a370) [cursoricon.c:1649] in USER32.DLL) (ebp=4074a358) 5 0x0053b8c5 (vfp7.exe.EntryPoint+0x13a8c5 in vfp7.exe) (ebp=4074a5e8) 6 0x00490d4b (vfp7.exe.EntryPoint+0x8fd4b in vfp7.exe) (ebp=4074a78c) 7 0x004abd03 (vfp7.exe.EntryPoint+0xaad03 in vfp7.exe) (ebp=4074a928) 8 0x00436a8d (vfp7.exe.EntryPoint+0x35a8d in vfp7.exe) (ebp=0000002b) The last function (CURSORICON_Simulate...) has a bug that makes the exception when the opened file isn't in RIFF format. Returning with fail when the file is in other format avoids the exception, and Visual FoxPro continue the execution loading correctly the image. Best regards, -- Sergio López koro(a)menteslibres.org

April 29, 2004

Re: CVS Invalid path for c:\\Windows

by Duane Clark

Brett I. Holcomb wrote: > I installed from CVS today and when I start wine I get the error below. > This happens even with the standard config file that it creates. I've > check both my and the config file and can't find any errors. I'm > including the c drive part of the config file. > > Any ideas why this is telling me this? > > Thanks. > > Error: > > Invalid path L"c:\\Windows" for L"windows" directory: does not exist. > Perhaps you have not properly edited your Wine configuration file > (/home/brett/.wine-cvs/config) > > Config file excerptL > > [Drive C] > "Path" = "fake_windows" > "Type" = "hd" > "Label" = "MS-DOS" > "Filesystem" = "win95" > Have you tried an absolute path: "Path" = "/path/to/fake_windows"

April 29, 2004

Re: CVS Invalid path for c:\\Windows

by Brett I. Holcomb

Any ideas on this. I just tried a new CVS build tonight and same thing. I have my config file set up correctly - it's been working until I tried the CVS on Sunday. Even a config file generated by wine-cvs doesn't work - it chokes. Thanks. On Sun, 25 Apr 2004, Brett I. Holcomb wrote: > I installed from CVS today and when I start wine I get the error below. > This happens even with the standard config file that it creates. I've > check both my and the config file and can't find any errors. I'm > including the c drive part of the config file. > > Any ideas why this is telling me this? > > Thanks. > > Error: > > Invalid path L"c:\\Windows" for L"windows" directory: does not exist. > Perhaps you have not properly edited your Wine configuration file > (/home/brett/.wine-cvs/config) > > Config file excerptL > > [Drive C] > "Path" = "fake_windows" > "Type" = "hd" > "Label" = "MS-DOS" > "Filesystem" = "win95" > > -- Brett I. Holcomb

April 29, 2004

Re: SetCalendarInfoA and SetCalendarInfoW implementations

by Vincent Béron

Le mer 28/04/2004 à 16:38, Wililam a écrit : > I have implemented the SetCalendarInfoA and SetCalendarInfoW API > functions in dlls/kernel/time.c. I am aware that you generally do not like it > when more than 1 thing is changed, but SetCalendarInfoA is not much more than > a > call to SetCalendarInfoW. I am also curious as to why both functions were > listed > as stdcalls rather than stubs when they were both stubs in the source file. There are two levels of stubs: "real stubs", and dummy functions. stub is used in a spec file when there's no implementation whatsoever of a given function, not even a dummy one. If an app tries to use that function, it results in a segmentation fault (and usually a crash to the debugger). In the case of SetCalendarInfo{A,W}, some dummy function existed, so they were callable by an app without it crashing (hence the stdcall declaration). Of course it wouldn't actually do much, that's what your implementation is for. The "stub" in the FIXME is to remind people that some function is not really there, although it's been called. The line is difficult to draw between the two types of stub: some apps will crash with a real stub and need a dummy one, some other ones will crash with a dummy one and will route around real stubs. Usually it's done on a case by case basis. > > I have enclosed the patch for the file against the latest source package. > > Here is the ChangeLog entry (I didn't patch the ChangeLog file): Alexandre commits all the changelog entries to the ChangeLog file when there's a release. Your way to specify the changelog is the correct one. Vincent

April 28, 2004

Re: d3d8 CVS doesn't compile

by Steven Edwards

Hello, --- Alexandre Julliard <julliard(a)winehq.org> wrote: > That seems really overkill. It's OK to define some symbols ourselves > when they have well-known values, but I don't think shipping the full > headers is really necessary; and I don't see how it would solve > issues > like the above anyway. There should only be three headers. In mingw w32api they ship glext.h,gl.h and glu.h in a GL subdirectory. Is anything else needed for Wine? Thanks Steven __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

April 28, 2004

Re: RFH: winetest testing

by Eric Pouech

> The output redirection didn't work from a GUI app: the libc > streams weren't initialized and thus the output disappeared. > Wouldn't DETACHED_PROCESS result the same? It's not crucial > for winetest itself, but making it a console app helped > debugging tremendously. I think the stream (handle) point of view worked, but somehow msvcrt doesn't initialize stdin/err/out when the app is in GUI mode. It may work if the app would close 0,1,2 and reopen them on standard handles > In short, I've got the impression that things are working > out now (by using some black magic -- ie. winetest being a > CUI -- which I don't understand), so maybe we could simply > leave it for now. Or do I miss serious issues? the only point is that we don't have a consistent basis across platforms were we start the tests from: - all tests programs are CUI exec - but, we don't know if it's attached to a console or not - if attached to a console, we don't know whether other processes are outputting to the same console (which could impact the tests...) - ... A+

April 28, 2004