wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

starcraft don't work well , please fix the problem
by centi_riccardo＠libero.it 17 Mar '02

17 Mar '02

Starcraft (blizzard game) don't work well on wine . I see a black screen and nothing other . It's a problem only of the lastest wine releases ........

1 0

WineConf streaming
by Eric Pouech 16 Mar '02

16 Mar '02

if someone reads his mail, I'm tryin to follow up the conf with the lpbn streaming but the sound is awful (R/N ratio horrible) so, if you could pass the info (and try to fix it) TIA A+

5 7

starcraft don't work in the last wine releases
by centi_riccardo＠libero.it 16 Mar '02

16 Mar '02

Starcraft don't work well in the last wine releases . I see a black screen while the game is running in backgroung (I can hear music and sounds work well ) . I have a slackware 8.0 Xfree 4.2.0 kernel 2.4.18 (slackware - current) . Please somebody send a patch to resolve this problem .........

1 0

Visual FoxPro and "GDI Regressions"
by Rick Romero 15 Mar '02

15 Mar '02

- Previously posted to wine-users (but with LESS info, worded worse :) As much as I think I won't be able to accomplish anything, I keep trying, and I've come across something interesting.. I'm testing my regression by doing the following: - Start the app - Press CTRL-V to paste text into the Command Window (which is the active 'MDI' window - but not really MDI - by default) - Switch to another virtual desktop - Switch back to Foxpro Desktop (That makes the Command Window 'look' active, by becoming blue instead of grey) - Click on the text that has been pasted. All builds after 5/10/01 will have the problem. The text will highlight as I move the mouse, as if I was still holding the mouse button down. This behavior is the same on scrollbars also. I normally run FoxPro with: wine /mnt/windows/DevStudio/vfp/vfp.exe Trying to discern some useful information, I've been playing with debugmsg. I've noticed if I do: wine --debugmsg +scroll,+event,+toolbar,+gdi,+heap /mnt/windows/DevStu dio/vfp/vfp.exe Clicking works as it should.. Scrollbars take two clicks before the ButtonRelease isn't acknoledged, but the text highlighting doesn't occur. I can click and move around normally. If I attempt to highlight text, (holding down the button) the ButtonRelease then is ignored as before.. If I cut out some of the debug info: wine --debugmsg +scroll,+event,+toolbar /mnt/windows/DevStu dio/vfp/vfp.exe We're back to normal (non-working normal). It seems like there is some timing issue that the (almost extreme) slowness from printing the debugging info is overcoming..(it's just going to stdout) Is there a click/release timer that could be increased? I've posted a small application at http://www.havokmon.com/stuff/vfp5test.zip . It uncompresses to a setup.exe and files, which includes the VFP5 Runtime, and a test.exe application that just opens a MDI window. The above test works on this application. http://www.havokmon.com/stuff/vfp5test.txt has more information on setup and installation with Wine (because it's not 100%). Hopefully everyone won't be too WineConf'd out next week :) Thanks, Rick

1 0

Borland C 5 - 16bits
by lists＠vmn.com.br 14 Mar '02

14 Mar '02

Hi, I am trying to run a point of sale app with the following structure: i) 16 bit ii) written in Borland C 5 iii)uses DDE iv) The app is broken into some 4 or 5 EXE and DLL files that communicate with the windows POST MESSAGE function. Two apps communicate through DDE. Does anyone have experience with applications written with Borland C in wine? It seems that 16 bit Apps written in Borland C are not working as in win98. The thing is I have tried about 30 apps. Everything written in Visual C (16 and 32 bits) works. Almost all apps written in Borland 32 bits, including OWL and BWCC apps work. This is a quite impressive showing for wine. 16 bit Apps written in Borland C seem to perform poorly. Running the apps with --debugmsg warn+all shows consistent problems with GDI: use of invalid pointers HEAP: adressing attempts of invalid addresses Furthermore, it seems that the apps are not correctly sharing the processor. For the program to run it is necessary to click in all the windows and therefore allocate processor time by giving focus. Does anyone have experience with Borland C 16 bit apps. Is your experience consistent with this report? I certainly would appreciate any pointers. Thanks, Miguel Feitosa p.S : Eric -> I have changed the Apps to not use DDE. I am going to do a couple more days of testing. Then I will roll back the app to the original state and generate some traces for DDE. ------------------------------------------------- This mail sent through IMP: webmail.vmn.com.br

1 0

aRts audio driver support
by Chris Morgan 14 Mar '02

14 Mar '02

*dlls/winmm/winearts, arts.c, arts.h, audio.c, mixer.c, mmaux.c, winearts.drv.spec, Makefile.in: Chris Morgan <cmorgan(a)alum.wpi.edu> Added aRts driver to wine *configure, configure.ac, dlls/Makefile.in, include/config.h.in, dlls/dsound/dsound_main.c, documentation/samples/config: Chris Morgan <cmorgan(a)alum.wpi.edu> Changes for aRts driver, added commented out entry to WinMM section of sample config file, added configure time checks for artsc support. One question I had was what to do about EXTRADEFS entry in dlls/winmm/winearts/Makefile.in? Is this ok or does it have to be a configure detected thing? Any comments about this patch are more than welcome. Thanks, Chris

2 1

fix for crash in snoop
by michael cardenas 14 Mar '02

14 Mar '02

I can submit my previous patch for snoop also. It removes functionality but fixes the crash. Should I submit it? ------------------------------------------------------- Changelog: - this patch should get rid of the remaining crashes in snoop. It fixes SNOOP_GetProcAddress. ------------------------------------------------------- COPYRIGHT: All original work contained in this email is released under the terms of the old Wine license (LICENSE.OLD in the distribution). This means that any new functions I have created can be incorporated into a non LGPL Wine fork, for example. Any future patches I submit can be considered to be release under the old Wine license.

1 0

Re: Segmentation fault (core dumped) with cvs update
by Tony Lambregts 14 Mar '02

14 Mar '02

> I have upgraded my internet access recently and have decided to stay > current with the cvs instead of waiting for each new snapshot. I however > have run into a snag > > I downloaded the latest snapshot from ibiblio.org (Wine-200202.28.tar.gz) > and the latest cvsdirs from ftp.winehq.com/pub/wine > (wine-cvsdirs-20020228.tar.gz) > > After following the steps to get a CVS sandbox I now have a local copy > of the wine located at /usr/local/src/wine. > > When I cd to this directory an try to update my copy i get the following: > > [root@tony wine]# cvs u -v > > Concurrent Versions System (CVS) 1.10.5 (client/server) > > Copyright (c) 1989-1998 Brian Berliner, david d `zoo' zuhn, > Jeff Polk, and other authors > > CVS may be copied only under the terms of the GNU General Public License, > a copy of which can be found with the CVS distribution kit. > > Specify the --help option for further information about CVS > > [root@tony wine]# cvs update -PAd > Segmentation fault (core dumped) > > Any help or suggestions would be appreciated > > Tony Lambregts > Ok just to follow up. I upgraded my version of cvs and life is good. Tony Lambregts

1 0

Re: [Fwd: Re: Oh yeah, the docu...]
by Tony Lambregts 14 Mar '02

14 Mar '02

> On Wed, Feb 20, 2002 at 09:40:43AM -0700, Tony Lambregts wrote: >> Tony Lambregts wrote: [Snip] >>> Ok so its just the online doc thats not up to date. Thanks. >>> >>> http://www.winehq.com/Docs/wine-user/configuring.shtml >>> >>> also looks like the the following are also not up to date. >>> >>> http://www.winehq.com/Docs/winedoc-sgml.tgz >>> http://www.winehq.com/Docs/winedoc-pdf.tgz VERY OLD >>> http://www.winehq.com/Docs/winedoc-ps.tgz VERY OLD >>> >>> and I would suspect that these too. (did not actually download) >>> >>> http://www.winehq.com/Docs/wine-set-html.tgz >>> http://www.winehq.com/Docs/winedoc-html.tgz >> [snip] >>> Since my last post on usenet I did download these and they are >>> out of >> date too. IMHO www.winehq.com/Docs should be updated at each >> snapshot. > Yeah, like I was really dying for finally seeing this being done. > > This time I yelled yet again, and Jeremy White muttered some Holy > Promise to make it finally work. (which, on hindsight, is a > relatively cheap promise due to Codeweavers having to go through > the trouble of revamping the whole winehq.com domain anyway due to > Corel's unfortunate demise ;-) > > Anyway, I'll be *really* glad once this finally gets done in a nice > solid timely cronjob. > > -- Andreas Mohr Stauferstr. 6, D-71272 > Renningen, Germany Tel. +49 7159 800604 > http://home.nexgo.de/andi.mohr/ > After checking winehq.com today I see that the online documentation is still not current. I also downloaded the sgml, pdf, and both htmls. They are still out of date. Now I realize that the staff at codeweavers are busy people but I would really like to see these up to date. Could I have some indication as to when this will done. Tony Lambregts Ps: I miss the network news service very much and want it to come back.

1 0

Has CVS access changed?
by Duane Clark 13 Mar '02

13 Mar '02

I just noticed that the patch I submitted is against an old version of CVS, even though I did the "cvs diff" today (3/13). Did I miss a change to the CVS configuration, perhaps in the move to the new server? I currently have .cvspass with :pserver:cvs@cvs.winehq.com:/home/wine Ah<Z

1 0

Re: Bug: fgets always reads from stdin
by Andriy Palamarchuk 13 Mar '02

13 Mar '02

Lawson, thank you very much for the help. lawson_whitney(a)juno.com wrote: > On Mon, 11 Mar 2002, Andriy Palamarchuk wrote: > > >>I'm trying to use function fgets, but it always reads >>from standard input. >> >> > I can't duplicate your results. [... skipped ...] As I found out I tried to feed 2 files to winemaker with -sym switches. Probably one of the files then was linked to Linux "fopen" function and returned FILE structure of incorrect format. Sorry to take your time. Andriy Palamarchuk __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/

1 0

Re: Toolbar ReleaseCapture changes
by Duane Clark 13 Mar '02

13 Mar '02

These are comments about the patch that I submitted. Since it is a fairly significant change, and I don't yet have much of a track record (and am admittedly not a programmer by training or profession) I thought some detailed comments were in order. I have two applications, Xilinx fpga_editor and Actel designer, where the toolbars did not work. They were drawn fine, tooltips worked, and when clicked, they put messages into the status bar indicating what they were supposed to do. But the actual actions were never performed. Tracing the apps, I found that what was happening was that upon LBUTTONUP, the applications for whatever reason explicitly called ReleaseCapture() before TOOLBAR_LButtonUp() was executed. This caused TOOLBAR_LButtonUp() to be called with infoPtr->bCaptured == 0 and infoPtr->nButtonDown == -1, as would be expected. However, this also caused almost all of the code in the routine to be skipped, since most of it is contained within the large if(){} section. So I got ControlSpy and figured out how to get that to compile and run (under Borland C++Builder), and was able to modify it to explicitly call ReleaseCapture() before the TOOLBAR_LButtonUp(). This I did in the routine GetMsgProc() in ControlSpy, by testing for the correct hwnd and message before explicitely calling ReleaseCapture. I kind of expected CallWndProc() to be the right place, but it did not seem to be, and I really don't understand it well enough yet to know why. In any case, running this modified version (and the original version to compare results) under WinNT, I saw that the when ReleaseCapture is explicitely called before TOOLBAR_LButtonUp(), that all the same messages and notifications are still generated, with the exception that WM_CAPTURECHANGED does not get sent. And that is as expected, since it was already sent by the explicit call to ReleaseCapture(). So the patch modifies TOOLBAR_LButtonUp() to duplicate this behavior. It fixes both of the apps that were having the toolbar problem, and in the case of fpga_editor, it supports rebar and the toolbar continues to work. And I have tested it on a half dozen other apps, and all seem to be working fine.

1 0

wineconf: Call for meeting in the reception of respective hotel a t 7:30
by Patrik Stridvall 13 Mar '02

13 Mar '02

> -----Original Message----- > From: Dimitrie O. Paun [mailto:dpaun@rogers.com] [snip] > How do you plan on getting to the conference? Taxi, I guess, > in my case. Yes. > Maybe we should post to the list, I already did that, no reply. Trying again. :-) It seems that I was wrong earlier the last message from Cheryl Schwarzman said: "On Friday, a continental breakfast will be served complete with juice, coffee and muffins at 8:15." > and compile a list of > people with the > hotels they are staying at... I don't think we need to do anything that complicated. Why not just say that everybody regardless of hotel meet in or near the reception at 7:30 waiting there until 7:45 for people to show up. Identifing other people should be easy: Just ask anybody standing in or near the reception whether they are going to wineconf. Then we order enough taxis (or cabs I think people call then in the US) to carry us all to the conference. This would give us 30 minuter to wait for cabs and get to the conference which according to Michael Robertsson is 10 minutes away at least at the hotel I'm staying. I guess most other hotels is pretty close as well. The simple strategy is often the best.

1 0

The memory model
by Duane Clark 12 Mar '02

12 Mar '02

Over on comp.arch.fpga, there has been a discussion (in the thread "exceeding 2GB limits in xilinx") about the memory models of Windoze versus Linux, and whether running a Windows program under wine would impose the Windows memory model on an application. This all comes about because the newest Xilinx software says that to use their newest large devices, a computer needs a minimum of 3GB to run place and route! Apparently Windows allocates 2GB to user space and Linux allocates 3GB (just repeating what has been said by others there). It was mentioned that perhaps running the tools under Linux/wine might allow the tools to have access to the full 3GB available under Linux. In any case, this made me curious, and I was hoping some of the more knowledgable people here might be able to explain how this works under wine. Thanks, Duane

4 3

[wine-devel] WINE with Trad. Chinese input (XCin) Q2
by leanne 12 Mar '02

12 Mar '02

Dear all, My second question is about include/wnd.h The i18n35.udiff patch got the following segment: ~~~~~~~~~~~~~~~~~~~ --- 000928/include/win.h.org Fri Sep 15 05:42:53 2000 +++ 000928/include/win.h Mon Oct 2 12:16:03 2000 @@ -133,6 +133,9 @@ BOOL (*pSetHostAttr)(WND *, INT haKey, INT value); BOOL (*pIsSelfClipping)(WND *); void (*pSetWindowRgn)(WND *, const HRGN); + void (*pHideCaret)(WND *); + void (*pSetCaretPos)(WND *, INT, INT); + void (*pShowCaret)(WND *); } WND_DRIVER; extern WND_DRIVER *WND_Driver; ~~~~~~~~~~~~~~~~~~~ We cannot patch into the latest version of WINE because it does not have the following struct "tagWND_DRIVER" which is valid in 2000-09-09 release. If we do not patch it, any harm? Many thanks!! include/wnd.h (wine 2000-09-09 release) ============================================= typedef struct tagWND_DRIVER { void (*pInitialize)(WND *); void (*pFinalize)(WND *); BOOL (*pCreateDesktopWindow)(WND *, struct tagCLASS *, BOOL); BOOL (*pCreateWindow)(WND *, struct tagCLASS *, CREATESTRUCTA *, BOOL); BOOL (*pDestroyWindow)(WND *); WND* (*pSetParent)(WND *, WND *); void (*pForceWindowRaise)(WND *); void (*pSetWindowPos)(WND *, const WINDOWPOS *, BOOL); void (*pSetText)(WND *, LPCWSTR); void (*pSetFocus)(WND *); void (*pPreSizeMove)(WND *); void (*pPostSizeMove)(WND *); void (*pSurfaceCopy)(WND *, HDC, INT, INT, const RECT *, BOOL); void (*pSetDrawable)(WND *, HDC, WORD, BOOL); BOOL (*pSetHostAttr)(WND *, INT haKey, INT value); BOOL (*pIsSelfClipping)(WND *); void (*pSetWindowRgn)(WND *, const HRGN); } WND_DRIVER; extern WND_DRIVER *WND_Driver; ============================================= Cheers, Leanne Tsang

1 0

Re: More Shlwapi ordinal routines - updated
by Jürgen Schmied 12 Mar '02

12 Mar '02

Hello! I saw your patch today and noticed you are really doing W<-->A conversion for the version* functions. Is there a special reason for this? The A<-->W conversion in shlwapi is only for systems lacking the W-functions like win95 so it's not nessesary to do this for us. It's enough to just forward the entry points to the W-functions in the version.dll. Ciao Juergen -- just done a cvs update on my box after more than a year ;-) --- juergen.schmied(a)debitel.net

2 1

Only fixup borland imports once
by Uwe Bonnes 12 Mar '02

12 Mar '02

Changelog: loader/pe_image.c: PE_fixup_imports Only fixup Borland imports once. Some remarks in winnt.h make it resonable to use pe_imp->TimeDateStamp as marker This make the quicklogic suite crash later, after doing some real work. The dll causing the problems is netbios.dll from win95 osr2. Attention: I used diff -uw ,as I have heavily indented my code. -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Free Software: If you contribute nothing, expect nothing -- Index: wine/loader/pe_image.c =================================================================== RCS file: /home/wine/wine/loader/pe_image.c,v retrieving revision 1.106 diff -u -w -r1.106 pe_image.c --- wine/loader/pe_image.c 2002/03/10 00:18:34 1.106 +++ wine/loader/pe_image.c 2002/03/12 00:01:45 @@ -344,6 +344,8 @@ } } else { /* Borland style */ TRACE("Borland style imports used\n"); + if (pe_imp->TimeDateStamp != -1) + { thunk_list = (PIMAGE_THUNK_DATA) RVA(pe_imp->FirstThunk); while (thunk_list->u1.Ordinal) { if (IMAGE_SNAP_BY_ORDINAL(thunk_list->u1.Ordinal)) { @@ -374,6 +376,8 @@ } thunk_list++; } + pe_imp->TimeDateStamp = -1; + } } } return 0;

1 0

RE: wineconf: Transport from the hotels to the conferance
by Patrik Stridvall 11 Mar '02

11 Mar '02

> Attendees are responsible for getting their persons from the hotel to > conference. Hopefully, it's a short cab ride or walk for > most. OK. I thought so. Just checking. > Coordinating > so that you carpool isn't such a bad idea. > > Conference starts at 9am. Feel free to show up at 8am for > coffee, juice and > donuts. And to help setup stuff. :^) > > It should take no longer than 10 minutes to get from Homestead to the > conference center. OK. So since the conferance is not providing REAL breakfast. How about for people at Homestead: 7.00 AM: Breakfast (at whatever place the hotel serves breakfast) 7.30 AM: Meeting for coordinating transport (at or near the hotel reception) Sounds good? PS. Everybody living at Homestead need not answer just to say yes. It is enough if a few do so the rest know that a least a few have agreed on when to meet.

1 0

Agenda for wineconf
by Michael Robertson 11 Mar '02

11 Mar '02

Below is an up to date agenda for wineconf 2002. Things are coming together great and it should be a information filled event. Thanks to all the attendees who are going to make this event worthwhile through their valuable presentations. Be sure and get that haircut before coming because my sources tell me there will be 3 video cameras capturing this event for later broadcasting. We have two full days planned (March 15th-16th). The sessions will go from 9-5 on both Friday and Saturday. I think all of the international attendees are coming in on Thurs, so they'll be rested up to start at 9am Friday morning. Both days, breakfast pastries will be provided at the conference premises along with lunch. Dinners will be within walking distance on Friday and Saturday. We're also planning on providing transportation from the airport to hotels on Thurs for our out of town guests. So a rental cars may not be necessary unless you're planning on extra activities on Sunday that aren't part of the conference. As for the conference sessions, the attendees are the speakers, so we're asking those in attendance to prepare a 30-45 minute presentation meant to educate and inform as well as spur on discussion. If you don't see your name on the list below, please send me a topic you would like to give a presenation on. I've heard from nearly everyone. We have a great conference venue lined up which will have plenty of meeting rooms and state of the art presentation capabilities along with internet access. To give a presentation, you can either bring a laptop to plug into the video projection system or you can email to me your presentation and I will insure that it is on a computer plugged into the projection system for your presentation. There are 2 areas that we'll be focusing on: Business issues - This will be a combination of presentation from companies talking about their business experience with WINE as well as talks on the non-technical issues facing WINE. Wine Technology - There will be some advanced topics as well as some more general overviews. Since (http://www.lpbn.org) will be on hand to shoot video of all the session, our goal is to have a video series that those newer to wine can view at anytime via the net to get up to speed. Alexandre's keynote will set the tone and provide a roadmap for many of the discussions. Alexandre's keynote will kickoff the conference. NOTE: Presentations listed below with a * designate a Friday presentation. If there's no asteric, then the presentation will be on Saturday. For maximum diversity, we will be alternating between technology presentations and business. There will be two technology presentations and then one on a business topic. Repeat. Wine Technology -------------------- WINE Past, Present and Future [Julliard]* Supporting Drag and Drop between Wine and non-Wine windows [Weigland]* How To Make Fonts Look Great In Wine [Davies]* Package streamlining of WINE [Meissner]* DirectX [Kaaven]* IActiveScript, or how jscript.dll was reimplemented using the Mozilla JScript engine, lots of glue, and a little bit of luck". [Hatheway]* Beyond Trial And Error, Alternative Ways To Insure Quality Code [Stridvall] A Howto For Regression Testing [Gouget] Winedoc and Automated Verification [Paun] Wine/Windows bootup handling and documentation/end user representation [Mohr] Package streamlining of WINE [Meissner] TBD [Czekalla] Business Talks ----------------- Macadamian - Making It As A Software House [Boulanger]* An Unique Commercial Application for WINE [Cadlink Technology/Hawkes]* Gaming and Beyond [Transgaming/State]* ReactOS - Where it's at, where it's going [ReactOS/Filby] Corel, A Look Back [Xandros/Tranter] Lindows.com And WINE [Robertson]

6 8

Fwd: Re: Rewrite of Notepad using NLS
by Sylvain Petreolle 11 Mar '02

11 Mar '02

> > > > Unified (diff -u) diff please. > > > > -- > > Dmitry. > > I made : [notepad] cvs diff >$HOME/patches/patch.diff [notepad] diff -u /dev/null notepad_res.h >>$HOME/patches/patch.diff What am I missing ? ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 2

wineconf: Transport from the hotels to the conferance
by Patrik Stridvall 11 Mar '02

11 Mar '02

> We have two full days planned (March 15th-16th). The sessions > will go from > 9-5 on both Friday and Saturday. I think all of the > international attendees > are coming in on Thurs, so they'll be rested up to start at > 9am Friday > morning. Both days, breakfast pastries will be provided at > the conference > premises along with lunch. Dinners will be within walking > distance on Friday > and Saturday. > > We're also planning on providing transportation from the > airport to hotels on > Thurs for our out of town guests. OK. There is a few small details left that need clarification. How and when will we get from our hotels to the the conferance? Personally I have booked room at the recommended hotel: Homestead San Diego Mira Mesa So will somebody pick us up at our hotels? Since we have booked hotel ourselves you are not likely to know were we are but still... Anyway, taking a taxi or a cab (or whatever you call it the US) will not be that hard. However, since I guess more than people than I have booked at the recommended hotel "Homestead San Diego Mira Mesa" perhaps we that should agree on some time to meet at some appropriate place at the hotel? What about 7.00 AM in or near the reception? Is that to early or to late? Since the sessions begin at 9.00 AM and some sort of breakfast in served at the conferance getting there early might not be a bad idea. BTW. How early can we arrive at the conferance?

2 1

Re: Rewrite of Notepad using NLS
by Dmitry Timoshkov 11 Mar '02

11 Mar '02

"Sylvain Petreolle" <spetreolle(a)yahoo.fr> wrote: > Notepad now uses NLS. > > Please remove notepad.rc, that defined > old macro system for language resources. Unified (diff -u) diff please. -- Dmitry.

1 0

Re: Rewrite of Notepad using NLS
by Dimitrie O. Paun 11 Mar '02

11 Mar '02

On March 10, 2002 07:20 pm, you wrote: > Notepad now uses NLS. > > Please remove notepad.rc, that defined > old macro system for language resources. Cool. But can you please submit the diff in diff -u format? Thanks, Dimi.

1 0

Bug: fgets always reads from stdin
by Andriy Palamarchuk 11 Mar '02

11 Mar '02

I'm trying to use function fgets, but it always reads from standard input. Here is the test code: { FILE *reg_file = fopen("1.txt", "r"); if (!reg_file) { perror(""); printf("Can't open file \"%s\"\n", "1.txt"); exit(1); } { char buf[100]; while (fgets(buf, 100, reg_file)) { printf("%s", buf); } exit(1); } } The same code works correctly when compiled without Wine. One starange thing here that I do not see call to function fopen in the log. End of the log for the test application, called with --debugmsg +all, critical sections call are removed (note, the mail client wrapped the lines) 0806eff8:Call kernel32.GetCommandLineA() ret=40021019 0806eff8:Ret kernel32.GetCommandLineA() retval=40350358 ret=40021019 0806eff8:Call kernel32.GetStartupInfoA(405a6e4c) ret=40021039 0806eff8:Ret kernel32.GetStartupInfoA() retval=400c6934 ret=40021039 0806eff8:Call ntdll.__wine_get_main_args(40024ea4) ret=40021053 0806eff8:Ret ntdll.__wine_get_main_args() retval=00000001 ret=40021053 0806eff8:Call kernel32.GetModuleHandleA(00000000) ret=4002106a 0806eff8:Ret kernel32.GetModuleHandleA() retval=40020000 ret=4002106a 0806eff8:Call msvcrt.fgets(405a6db4 "\344\307\016@",00000064,08050f70) ret=4001e21b 0806eff8:trace:msvcrt:MSVCRT_fgets :file(0x8050f70) fd (0) str (0x405a6db4) len (100) 0806eff8:Call kernel32.ReadFile(00000004,405a6bbf,00000001,405a6b98,00000000) ret=406878e6 0806eff8:trace:file:ReadFile 4 0x405a6bbf 1 0x405a6b98 (nil) 0806eff8: get_handle_fd( handle=4, access=80000000 ) 0806eff8: *fd* 4 -> 8 0806eff8: get_handle_fd() = 0 { fd=-1, type=1, flags=0 } 0806eff8: set_handle_info( handle=4, flags=0, mask=0, fd=10 ) 0806eff8: set_handle_info() = 0 { old_flags=1, cur_fd=10 } #here I entered line with character W 0806eff8:Ret kernel32.ReadFile() retval=00000001 ret=406878e6 0806eff8:Call kernel32.ReadFile(00000004,405a6bbf,00000001,405a6b98,00000000) ret=406878e6 0806eff8:trace:file:ReadFile 4 0x405a6bbf 1 0x405a6b98 (nil) 0806eff8: get_handle_fd( handle=4, access=80000000 ) 0806eff8: get_handle_fd() = 0 { fd=10, type=1, flags=0 } 0806eff8:Ret kernel32.ReadFile() retval=00000001 ret=406878e6 0806eff8:trace:msvcrt:MSVCRT_fgets :got 'W ' 0806eff8:Ret msvcrt.fgets() retval=405a6db4 ret=4001e21b 0806eff8:Call kernel32.WriteFile(00000008,405a646c,00000002,405a6428,00000000) ret=4068818b 0806eff8:trace:file:WriteFile 8 0x405a646c 2 0x405a6428 (nil) 0806eff8: get_handle_fd( handle=8, access=40000000 ) 0806eff8: *fd* 8 -> 9 0806eff8: get_handle_fd() = 0 { fd=-1, type=1, flags=0 } 0806eff8: set_handle_info( handle=8, flags=0, mask=0, fd=11 ) 0806eff8: set_handle_info() = 0 { old_flags=1, cur_fd=11 } 0806eff8:Ret kernel32.WriteFile() retval=00000001 ret=4068818b 0806eff8:Call msvcrt.fgets(405a6db4 "W\n",00000064,08050f70) ret=4001e21b 0806eff8:trace:msvcrt:MSVCRT_fgets :file(0x8050f70) fd (0) str (0x405a6db4) len (100) 0806eff8:Call kernel32.ReadFile(00000004,405a6bbf,00000001,405a6b98,00000000) ret=406878e6 0806eff8:trace:file:ReadFile 4 0x405a6bbf 1 0x405a6b98 (nil) 0806eff8: get_handle_fd( handle=4, access=80000000 ) 0806eff8: get_handle_fd() = 0 { fd=10, type=1, flags=0 } #here I entered ^D to close stdin 0806eff8:Ret kernel32.ReadFile() retval=00000001 ret=406878e6 0806eff8:trace:msvcrt:_read :EOF 0806eff8:trace:msvcrt:MSVCRT_fgets :nothing read 0806eff8:Ret msvcrt.fgets() retval=00000000 ret=4001e21b 0806eff8:Call msvcrt.exit(00000001) ret=4001e229 0806eff8:trace:msvcrt:MSVCRT_exit (1) 0806eff8:trace:msvcrt:_lock (13) 0806eff8:trace:msvcrt:_lock (17) 0806eff8:trace:msvcrt:_lock : creating lock #13 0806eff8:trace:msvcrt:_unlock (17) 0806eff8:trace:msvcrt:__MSVCRT__call_atexit 0 atext functions to call 0806eff8:trace:msvcrt:_unlock (13) 0806eff8:Call kernel32.ExitProcess(00000001) ret=40686022 0806eff8:trace:module:MODULE_InitDLL (regedit,PROCESS_DETACH,0x1) - CALL 0806eff8:trace:module:MODULE_InitDLL (0x403509b0,PROCESS_DETACH,0x1) - RETURN 1 0806eff8:trace:module:MODULE_InitDLL (msvcrt.dll,PROCESS_DETACH,0x1) - CALL 0806eff8:Call PE DLL (proc=0x4068b1c0,module=4067c000,type=0,res=0x1) 0806eff8:trace:msvcrt:MSVCRT_Init (0x4067c000, DLL_PROCESS_DETACH, 0x1) pid(134659496), tid(134672376), tls(0) 0806eff8:trace:msvcrt:msvcrt_free_mt_locks : uninitializing all mtlocks 0806eff8:trace:msvcrt:_fcloseall :closed (0) handles 0806eff8:trace:msvcrt:msvcrt_free_console :Closing console handles 0806eff8:Call kernel32.CloseHandle(00000004) ret=406810d3 0806eff8: close_handle( handle=4 ) 0806eff8: close_handle() = 0 { fd=10 } 0806eff8:Ret kernel32.CloseHandle() retval=00000001 ret=406810d3 0806eff8:Call kernel32.CloseHandle(ffffffff) ret=406810de 0806eff8: close_handle( handle=-1 ) 0806eff8: close_handle() = INVALID_HANDLE { fd=0 } 0806eff8:Ret kernel32.CloseHandle() retval=00000000 ret=406810de 0806eff8:Call kernel32.FreeEnvironmentStringsA(403504b0) ret=406832ef 0806eff8:Ret kernel32.FreeEnvironmentStringsA() retval=00000001 ret=406832ef 0806eff8:Call kernel32.FreeEnvironmentStringsW(403513d0) ret=406832fa 0806eff8:trace:heap:RtlFreeHeap (40350000,00000002,403513d0): returning TRUE 0806eff8:Ret kernel32.FreeEnvironmentStringsW() retval=00000001 ret=406832fa 0806eff8:Call kernel32.TlsFree(00000000) ret=4068b545 0806eff8:Ret kernel32.TlsFree() retval=00000001 ret=4068b545 0806eff8:trace:msvcrt:MSVCRT_Init finished process free 0806eff8:Ret PE DLL (proc=0x4068b1c0,module=4067c000,type=0,res=0x1) retval=1 0806eff8:trace:module:MODULE_InitDLL (0x40350d1c,PROCESS_DETACH,0x1) - RETURN 1 0806eff8:trace:module:MODULE_InitDLL (advapi32.dll,PROCESS_DETACH,0x1) - CALL 0806eff8:trace:module:MODULE_InitDLL (0x40350bf0,PROCESS_DETACH,0x1) - RETURN 1 0806eff8:trace:module:MODULE_InitDLL (kernel32.dll,PROCESS_DETACH,0x1) - CALL 0806eff8:Call PE DLL (proc=0x406247fc,module=40615000,type=0,res=0x1) 0806eff8:Ret PE DLL (proc=0x406247fc,module=40615000,type=0,res=0x1) retval=1 0806eff8:trace:module:MODULE_InitDLL (0x40350e2c,PROCESS_DETACH,0x1) - RETURN 1 0806eff8:trace:module:MODULE_InitDLL (ntdll.dll,PROCESS_DETACH,0x1) - CALL 0806eff8:trace:module:MODULE_InitDLL (0x403508ac,PROCESS_DETACH,0x1) - RETURN 1 0806eff8: terminate_process( handle=-1, exit_code=1 ) 0806eff8: terminate_process() = 0 { self=1 } 0806eff8: *killed* exit_code=1 /home/apalamarchuk/.wine/user.reg: saving key \\User\\apalamarchuk /home/apalamarchuk/.wine/system.reg: saving key \\Machine /home/apalamarchuk/.wine/userdef.reg: saving key \\User\\.Default Server: exiting (pid=9451) The bug, probably, is very simple and somebody can give me a clue basing on the trace. I have fresh CVS Wine. Thanks, Andriy Palamarchuk __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/

2 2

Re: Wine release 20020310
by Matthew Toseland 11 Mar '02

11 Mar '02

On Sun, Mar 10, 2002 at 01:05:48PM -0800, Alexandre Julliard wrote: > This is release 20020310 of Wine, a free implementation of Windows on > Unix. This is still a developers only release. There are many bugs > and unimplemented features. Most applications still do not work > correctly. > > Patches should be submitted to "wine-patches(a)winehq.com". Please > don't forget to include a ChangeLog entry. > > This release is identical to the previous one (release 20020228), > except that the license has changed: Wine is now distributed under the > terms of the GNU Lesser General Public License. All code submitted to > me or to the wine-patches list from now on will be assumed to be > released under the LGPL too. Cool!

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel