wine-devel March 2002

wine-devel@winehq.org

103 participants
202 discussions

DDE Problems and Thread Execution Order in win16 - win3.1
by list＠vmn.com.br 02 Mar '02

02 Mar '02

Hi, I am trying to run a 16bit windows app on wine. The app is broken down into about 5 diferent EXE files. The init sequence is something like: --- PDV.EXE -> starts up and calls DISP.EXE -> DISP and PDV communicate through DDE BD2.EXE -> runs ctree, a dbf database ... (other apps get spawned by PDV.EXE) If above sequence is successfull - PDV's User Interface get's completely built PDV is ready for user interaction. --- PDV has 2 windows and DISP has one. All the other apps run minimized. I can't get the APP to finish this init sequence. It either hangs with a lot of err:ntdll:RtlpWaitForCriticalSection section 0x4010030c "syslevel.c: Win16Mutex" wait timed out, retrying (60 sec) fs=0897 errors and/or crashes with an exception. The app runs fine untill it get's to the point where it spawns a second EXE. It seems to me that the execution of these processess is not happening in the same order in win98 and in wine. Could this be the case? I read all I could find in the mailing lists and the manual on this issue, specially wine-devel manual. A good example to demonstrate this is the sequence where PDV.EXE calls DISP.EXE and then tries to set up DDE. The code in the APP is: 1. Run PDV.EXE 2. PDV.EXE Calls DISP.EXE - DISP initializes 3. Set up DDE The code being run by wine is 1. Run PDV.EXE 2. PDV.EXE Calls DISP.EXE - Disp starts initializing and control is returned to PDV.EXE 3. PDV.EXE thinks DISP.EXE is initialized and tries to set up DDE. The call fails 4. DISP.EXE finishes initializing , does not receive a DDEConnect and just sit's there with no work to do. The sequence where PDV.EXE calls BD.EXE is similar. It seems that BD.EXE is not getting enough processor time to finish it's init sequence, and so my app hangs during the init sequence. I don't know how to test this. I have access to the source of these apps. If I compile them with debugging info, will I be able to see them in winedbg? Is there a call in win16 to yield the app's execution? Maybe if I called this often in my PDV.EXE code, things would work out? I have been at it for about two days and would certainly appreciate an insight. Please help me out ! Thanks, Miguel --- I would like to note that the app was not drawing it's windows correctly - the windows where gray. I thought this was due to the same problem as the init sequence but when I set winLook=win31 in the .wine/config file, this problem is solved. ------------------------------------------------- This mail sent through IMP: webmail.vmn.com.br

1 0

update on bug #11 and #435, newbie questions
by jasonp 02 Mar '02

02 Mar '02

I'm new to Wine development and was checking out bug #11 (from "tasklet" meta-bug #406) I added some comments for it. It seems beyond the scope of a beginner type bug. See bug for details. Also, the latest build was having problems getting configure to recognize freetype which was already reported as #435. It has some more details now. Something else I came across: the most recent tarfile for CVS dirs, "wine-cvsdirs-20011226.tar.gz", is missing the directory for "wine/dlls/crypt32/CVS" Should this be reported as a bug? I was going to look at bug #323 (close stdout/stderr for wineclipsrv, ie. run as daemon) Any suggestions or comments for that? Wouldn't the system call daemon() take care of it pretty easily? Jason Phillips

2 1

Re: Question about ToolbarWindowProc
by Guy L. Albertelli 02 Mar '02

02 Mar '02

----- Original Message ----- From: "Guy L. Albertelli" <galberte(a)neo.lrun.com> To: "Jeremy Shaw" <jeremy(a)lindows.com>; "Wine Devel" <wine-devel(a)winehq.com> Sent: Wednesday, February 27, 2002 9:20 PM Subject: Re: Question about ToolbarWindowProc [snip] > case 0x0463: > { > LPDWORD hoho = (LPDWORD)lParam; > ERR("[0463] lParam 0x%08lx -> 0x%08lx 0x%08lx\n", > lParam, *hoho, *(hoho+1)); > /* guess - level 1 */ > if (!*(hoho+1)) { > *(hoho+1) = *hoho; /* set second word to first */ > } > return 0; /* really should be 1 */ > } > After more thought (this is still supposition), I think that lParam is a LPSIZE. Also that the code (at least partially) could be: case 0x0463: { LPSIZE hoho = (LPDWORD)lParam; ERR("[0463] lParam 0x%08lx -> 0x%08lx 0x%08lx\n", lParam, hoho->cx, hoho->cy); /* guess - level 2 */ if (!hoho->cy) { hoho->cy = infoPtr->rcBound.bottom - infoPtr->rcBound.top; } return 1; } Note that there has to be some difference between [0463] and TB_GETMAXSIZE. Also I have seen some of the values being -1 or other small values. Making the changes to spy.c and seeing what the natvie control does will be the key. Guy

2 2

Update: Agenda for wineconf 2002
by Michael Robertson 01 Mar '02

01 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 shuttles will be provided to our dinner spot. 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. 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 3 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. There will be a series of more advanced topics as well. Future of wine - These will be talks focusing on looking forward to technology and business issues confronting wine. Alexandre's keynote will set the tone and provide a roadmap for many of the discussions. The specific times for the speakers below have not been set other than Alexandre's keynote which naturally will start the conference. Here's the working list. If you see your name below and don't like the topic, let me know that people have requested we're happy to change it. If you don't see your name below, let me know and we'll do our best to accomodate you! -- MR Business Talks ----------------- 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] Crossover Strategy [Codeweavers/???] Macadamian - Making It As A Software House [Hatheway] Developer Funding, Who Pays The Rent [???] Wine Technology -------------------- Approaches to debug a random windows program different approach [Weigand] Development Model [AJ] NORM - The secret weapon [Codeweavers/???] Making Fonts Not Look Like Crap [Davies] Regression Testing [???] How To Improve The Debugger [Meissner] Maximizing performance of WINE [???] Package streamlining of WINE [???] DirectX [Kaaven] WINE as a porting tool [Jacques] API Standardization [???] Future of Wine ---------------- AJ - Wine Keynote to open the conference 9am on Friday. WINE's "Most Wanted": Features To Make WINE Great [???]

1 0

Mouse and keyboard events in DGA2 mode
by J. Christopher Pereira 01 Mar '02

01 Mar '02

Hi to all: I'm new here. Please don't bite me :-) Since some time ago, the mouse & keyboard events processing in DGA2 mode is broken in the CVS. I spent some time doing regresion tests and noticed that 20010131 and 20010216 works great (mouse + kb + dga2, same system), so I guess it's an old known bug (?) Any idea/help? dlls/x11drv/dga2.c?

2 1

Re: Shlwapi UNC problems with IE6 (fwd, try again)
by Alexandre Julliard 01 Mar '02

01 Mar '02

lawson_whitney(a)juno.com writes: > ChangeLog: > dlls/shlwapi/path.c: > Lawson Whitney <lawson_whitney(a)juno.com> > Protect PathIsUNCServerShare from bad lpszPath. Windows doesn't seem to do this. The bad pointer probably comes from an earlier bug. -- Alexandre Julliard julliard(a)winehq.com

3 2

Oops! Sorry about the mis-send concerning the wineconf agenda
by Michael Robertson 01 Mar '02

01 Mar '02

I accidentally sent an incomplete message to the list. I apologize. I'd like to blame kmail, but its user error. Later today will be an updated revision of the agenda for wineconf. The event is coming together great! -- MR

1 0

Update: Agenda for wineconf 2002
by Michael Robertson 01 Mar '02

01 Mar '02

There are 3 areas that we'll be focusing on: Business issues - - Basic wine expertise - Future of wine Business Talks A 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] Crossover Strategy [Codeweavers/???] Macadamian - Making It As A Software House [Macadamian] How to debug a random windows program different approach

1 0

newBie Question:RtlpWaitForCriticalSection
by list＠vmn.com.br 01 Mar '02

01 Mar '02

err:ntdll:RtlpWaitForCriticalSection section 0x4010030c "syslevel.c: Win16Mutex" wait timed out, retrying (60 sec) fs=0897 What does this error mean? This looks like a timer to me, that is, if a certain amount of execution does not happen then this error is printed. The amount of execution is measured by two flags in wine builtin code. Is this correct? My App is generating a lot of these.... Thanks, Miguel ------------------------------------------------- This mail sent through IMP: webmail.vmn.com.br

1 0

Re: DDE problems on 16bit Apps
by Eric Pouech 01 Mar '02

01 Mar '02

> if (ShellExecute(hWnd, "open", > PDVROT_szDisplay, "", > PDVROT_szPDVPath, SW_SHOWNORMAL) <= (HINSTANCE) 32) > { > HandleOutput("ERROR: DISPLAY PDV."); > return; > } > WaitAppActivate(DISPLAYTITLE); > if (DdeInitialize((LPDWORD) & idInst, > (PFNCALLBACK) DDECallback, APPCMD_CLIENTONLY, 0L)) > { > HandleOutput("ERROR failed to init DDE DISPLAY PDV."); > return; > } the issue is here above. the trace shows that the child program initializes itself after the parent tries to connect whereas here, the parent seems to wait for the app to be up and running before it goes further what does your WaitAppActivate function do ? (PS: I'll be away from my PC for more than one week starting now. so, I'll likely be very unresponsible in that time frame) A+ --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) The future will be better tomorrow, Vice President Dan Quayle ____________________________________________________________ Faites un voeu et puis Voila ! www.voila.fr Avec Voila Mail, consultez vos e-mails sur votre mobile Wap.

1 0

Jump to page:

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 March 2002