July 2002 - Wine-Devel - list.winehq.org

Re: newbie question

by Vincent Béron

Le mer 10/07/2002 à 02:36, Michael Cardenas a écrit : > Preetham wrote: > > > Thanx bill. But what i want to know is where exactly is this > > call(CreateBitmap will eventually result in calls into probably X11 > > code) done. I have looked into the documentation in winehq.com, i get > > a fair idea of how it is done, however when i look into the source > > code, im unable to understand much. > > What i want to know is, this program that loads the windows exe and > > which runs them, where is this program located. The code for wine is a bit scattered all over the place. The main executable (wine) is built in miscemu, but some source from elsewhere in the tree is used. > > Also, the code where CreateBitmap is mapped into the Xlib, where is > > this code. > > I am looking at some kind of low level documentation, or atleast a > > place where i could start. > > Thanks, > > Preetham > > [snip] > > ... > > > You could start by going to your wine source dir and typing this: > > find . -name *.c | grep CreateBitmap > > or > > find . -name *.spec | grep CreateBitmap tools/findfunc fills exactly that need. Usage: ./findfunc FUNCTION > -- > michael cardenas > lead windows compatibility engineer > lindows.com > . > hyperpoem.net > . > "Be the change you want to see in the world" > -Mahatma Gandhi > Vincent

July 10, 2002

Re: newbie question

by Preetham

Thanx bill. But what i want to know is where exactly is this call(CreateBitmap will eventually result in calls into probably X11 code) done. I have looked into the documentation in winehq.com, i get a fair idea of how it is done, however when i look into the source code, im unable to understand much. What i want to know is, this program that loads the windows exe and which runs them, where is this program located. Also, the code where CreateBitmap is mapped into the Xlib, where is this code. I am looking at some kind of low level documentation, or atleast a place where i could start. Thanks, Preetham ----- Original Message ----- From: Medland, Bill To: Wine devel (E-mail) Sent: Tuesday, July 09, 2002 4:10 PM Subject: RE: newbie question (BTW HTML email is generally sort of frowned on here) Unix doesn't run windows programs. I suggest you actually read some of the documentation at www.winehq.com, especially the Winelib stuff. Basically wine is a Unix program that understands the structure of Windows DLLS and exes. Wine itself runs, loads the dlls and exes into memory and executes them. Some DLLS are replaced by plug-compatible unix so's that interface to the lower levels. So CreateBitmap will eventually result in calls into probably X11 code. Bill -----Original Message----- From: Preetham [mailto:preetham(a)student.utdallas.edu] Sent: Tuesday, July 09, 2002 5:24 PM To: wine-devel(a)winehq.com Subject: newbie question Hi all: I have a very elementary question. How does the Winodws program run in Unix. For example, i write a program where i call the CreateBitmap() method, what happens. How is a dll called in the unix environment. From what i know, unix dlls are .so files. From the wingdi.h file in the wine\include directory, how does the unix OS know how to resolve the WINAPI call. If i am right, windows dll's are implemented in unix, how is this done. I'm kinda flustered at the moment, would appreciate the help Thanks, Preetham.

July 10, 2002

Re: warcraft 3

by Sylvain Petreolle

> Using wine using opengl (compiled from cvs), start using wine > path/War3.exe -- -opengl : > > fixme:dsound:IDirectSoundImpl_SetCooperativeLevel > (0x403aad78,00010023,2):stub > fixme:win32:CreateIoCompletionPort (ffffffff, 0000, 00000000, > 00000000): > stub. > > then it seems to start fullscreen but does not display anything, so > that > i must kill it. > > > any ideas ? > ps -ef |grep wine to see if it has gone to debugger (winedbg). if so, you should put "Desktop" = "640x480" or so to see what happened. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

July 10, 2002

Re: newbie question

by Michael Cardenas

Preetham wrote: > Hi all: > > I have a very elementary question. How does the Winodws program run > in Unix. For example, i write a program where i call the > CreateBitmap() method, what happens. How is a dll called in the unix > environment. From what i know, unix dlls are .so files. From the > wingdi.h file in the wine\include directory, how does the unix OS know > how to resolve the WINAPI call. If i am right, windows dll's are > implemented in unix, how is this done. > I'm kinda flustered at the moment, would appreciate the help > Thanks, > Preetham. > Did you look at some of the documentation like developers-hints ? or winehq.com ? the spec files are what map windows functions to unix functions. the loader can load both windows dlls and linux so's. -- michael cardenas lead windows compatibility engineer lindows.com . hyperpoem.net . "Be the change you want to see in the world" -Mahatma Gandhi

July 10, 2002

newbie question

by Preetham

Hi all: I have a very elementary question. How does the Winodws program run in Unix. For example, i write a program where i call the CreateBitmap() method, what happens. How is a dll called in the unix environment. From what i know, unix dlls are .so files. From the wingdi.h file in the wine\include directory, how does the unix OS know how to resolve the WINAPI call. If i am right, windows dll's are implemented in unix, how is this done. I'm kinda flustered at the moment, would appreciate the help Thanks, Preetham.

July 10, 2002

Re: Debugger

by Francois Gouget

On Thu, 11 Jul 2002, Max wrote: > thanx !!! > I'll try it just now... > Btw, two more questions, if you can answer :-) > > 1 - When I try the commands --debugmsg inside winedbg, I get 'parse error' > everytimes; the command appears in help, but doesn't work for me... > is it a known issue, or I make some mistake ? --debugmsg is not a command. It's a command line option. what you want to do is probably along the lines of 'set + relay' or something like that. Search for "debug messages" in documentation/debugger.sgml -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY

July 9, 2002

RE: newbie question

by Medland, Bill

(BTW HTML email is generally sort of frowned on here) Unix doesn't run windows programs. I suggest you actually read some of the documentation at www.winehq.com <http://www.winehq.com> , especially the Winelib stuff. Basically wine is a Unix program that understands the structure of Windows DLLS and exes. Wine itself runs, loads the dlls and exes into memory and executes them. Some DLLS are replaced by plug-compatible unix so's that interface to the lower levels. So CreateBitmap will eventually result in calls into probably X11 code. Bill -----Original Message----- From: Preetham [mailto:preetham(a)student.utdallas.edu] Sent: Tuesday, July 09, 2002 5:24 PM To: wine-devel(a)winehq.com Subject: newbie question Hi all: I have a very elementary question. How does the Winodws program run in Unix. For example, i write a program where i call the CreateBitmap() method, what happens. How is a dll called in the unix environment. From what i know, unix dlls are .so files. From the wingdi.h file in the wine\include directory, how does the unix OS know how to resolve the WINAPI call. If i am right, windows dll's are implemented in unix, how is this done. I'm kinda flustered at the moment, would appreciate the help Thanks, Preetham.

July 9, 2002

Re: PSDRV question

by Huw D M Davies

On Tue, Jul 09, 2002 at 04:45:56PM -0400, Carl Sopchak wrote: > I've been trying to get Quicken 2000 Deluxe running in wine. After I figured > out that it wasn't finding a DLL for the internet connection (and got that > fixed), I started testing the second-most important function of Quicken that > I need: check printing. > > All went well until I tried to print a sample check (to verify alignment), at > which point Wine crashed into winedbg. I figured out why: When reading the > ppd file, it sets up an *InputSlot for ManualFeed (even though it's not > really an InputSlot, but most Win programs treat it as one...). The problem > was that, in ppd.c, a Name wasn't given to the slot (but a FullName was), so > when ps.c tried to output the header for the InputSlot it crashed (since > strlen(NULL) causes a crash). > > I hacked the AddSlot call to name the slot "Manual", and this seems to work > OK. The question that I have is, is this the way that it should REALLY get > fixed (does the name matter?), or should something else be done? > > I'd be happy to correct my hack, if necessary. In either case, I can post the > patch to sourceforge, once I know "the right way" this should be handled. > > Thanks for the help, I'd suggest calling PSDRV_AddSlot with both Name and FullName set to "Manual Feed" Huw.

July 9, 2002

Re: warcraft 3

by Nix N. Nix

On Mon, 2002-07-08 at 13:54, Jesse Allen wrote: > Hi, > > Here's how to get Warcraft 3 running under wine: > > 1. Use the latest wine cvs. Only that will work. > > 2. Mount the CD, and run install.exe on the CD with the winver set to > win98 under config. (even though 95/98 are exactly the same when playing > the game--i hate that) You should disable the ide-scsi thing because it > seems to cause problems =( ~/.wine/config: ... [Version] "Windows" = "win2k" ... Doesn't work. In fact, this doesn't help, irrespective of the version I set it to. Where else can I set the Windoze version ? I managed to get War3 to work using winex: http://www.transgaming.com/showthread.php?msg=11638&forum=6&thread=11638 Hope this helps, and thanks for the help.

July 9, 2002

RE: Debugger

by Medland, Bill

> -----Original Message----- > From: Max [mailto:max(a)veneto.com] > Sent: Wednesday, July 10, 2002 3:21 PM > To: wine-devel(a)winehq.com > Subject: Re: Debugger > > > thanx !!! > I'll try it just now... > Btw, two more questions, if you can answer :-) > SNIP > 2 - Starting an app, while loading dll's and symbols, > winedbg starts showing garbage like this : > > No debug information in 32bit DLL > 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40b55000) > Loaded debug information from ELF > '/usr/local/lib/wine/x11drv.dll.so' (0x40b45000) > failure on > type_info:T(3,1)=s8__name:/1(3,2)=*(0,2),0,32;.vf(3,1):(3,3)=* > (0,23),32;type_info::(3,4)=#(3,1),(0,21),(3,5)=*(3,1),(0,1),(0,21);:qq > > _._9type_info;2A*2;(3,1);;operator=::(3,6)=##(3,7)=&(3,1);:__a > s__9type_infoRC9type_info;0A.;type_info::(3,8)=##(3,5);:RC9type_info; > > 0A.(3,9)=##(3,5);:PCc;1A.;before::(3,10)=##(0,12);:RC9type_inf > o;2B.;name::(3,11)=##(3,2);:;2B.; > > operator==::(3,10):__eq__C9type_infoRC9type_info;2B.;operator! > =::(3,10):__ne__C9type_infoRC9type_info;2B.;; > ~%(3,1); at /1(3,2)=*(0,2),0,32;.vf(3,1):(3,3)=*( > ..............<MORE>................. > Loaded debug information from ELF > '/usr/local/lib/wine/x11drv.dll.so' (0x40b45000) > ..............<MUCH MORE>................. > Unknown type '&' > failure on arg:p(0,25)=&(3,1) at (3,1) > Nothing has been defined <> > failure on bl:p(0,26)=*(2,17) at > ..............<MUCH MUCH MORE>................. > > Is it a known bug or... ? Known issue. The debugger doesn't yet know how to handle the extended information available about C++ classes. (If it really cheeses you I have a patch that basically replaces the detailed garbage with "we don't understand") Bill

July 9, 2002