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

Re: warcraft 3

by Jesse Allen

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 =( 3. Close the install program. Go to the directory where war3 is installed. mv the Movies folder to Movies backup. The game tries to display a movie clip on start in the retail, and it hangs wine =( 4. Download the NoCD patch for Warcraft 3 v1.00 (I don't know if 1.01 is out yet) at www.gamecopyworld.com. mv war3.exe and worldedit.exe to backup names. Copy in the patched program exe's. You may now run War3 if you wish. Warcraft 3 uses Safedisc v2. With this patch it will bypass it. Run war3 with the command "wine war3.exe -- -opengl". 5. To login battle.net, you need to bypass the exe check. With the patched version of the game, it won't work. So what I did to get it to work is moved the patched exe's to something like "war3_patched.exe" and create a symbolic link "war3.exe" that links to it. Start the game "war3.exe". To login to battle.net, open bash console. Change to the war3 directory, and reset the symbolic link to the original war3 exe, let it sleep 5 seconds, and then reset the symbolic link back to the patched version. While it's sleeping, you need to login into battle.net immediately. This is what I did to get D2 battle.net to work under wine. It should work for war3. You need to be the same version as battle.net for it to work though. (currently only 1.00 is availible for linux, and battle.net is 1.01) 6. To patch the game, you need to get the standalone patches. Set your symbolic link to the real exe's, and patch away =) The beta in contrast worked perfectly. The retail has a couple problems =(. The advantages I find running War3 under linux/wine/opengl, are higher framerates than on both real windows, and winex. And no graphics errors in comparison to winex d3d8, and no sound problems like under real windows. My three button mouse also works unlike windows. All these advantages =) Jesse

July 8, 2002

RE: Wine ODBC compatibilty

by Medland, Bill

> -----Original Message----- > From: James Juran [mailto:jamesjuran(a)alumni.psu.edu] > Sent: Friday, June 28, 2002 3:43 PM > To: Robert Damen > Cc: 'wine-devel(a)winehq.com' > Subject: Re: Wine ODBC compatibilty > > > Robert Damen wrote: > > > > Wine, > > I found this address on your website, if it is the > wrong address for > > these types of questions - Sorry!. > > > > I was wondering weather you could answer a question I have > about support for > > Microsoft Office applications. > > The question is about weather wine can emulate (or has its > own version of) > > the "ODBC Data Sources (32bit)" application found in > > c:\windows\Control Panel\ODBC Data Sources > > This application is used to set up DSN drivers for ODBC > access on Access and > > Excel. > > An example of one of the drivers that this application > handles is the MyODBC > > 3.51 windows driver. > > The "ODBC Data Sources" application in the control panel merely > manipulates registry entries. If all you need to do is set > them up, you > can do that easily with regedit. > > If you're wondering if they will work after you set them up, someone > else will have to answer that question :-) > > -- > James Juran > jamesjuran(a)alumni.psu.edu > To the best of my knowledge there is no such application, and it would be strange if there were. The WINE ODBC32 module is merely a wrapper around any suitable Linux ODBC module. For example we use unixODBC. Thus the WINE ODBC module has no real need to access the registry since all the work is being done by the Linux ODBC module. The way that the Linux ODBC module is configure depends upon which one you use. The unixODBC module, for example, uses a odbc.ini and odbcinst.ini file to store its configuration information. Although it does have a graphical configuration tool, with plugins for some database drivers, I prefer to edit the files by hand. That being said, it may be necessary to add some information to the registry for some ODBC-based applications. I do know that Crystal Reports directly accesses the registry for ODBC information rather than asking ODBC itself. HTH Bill

July 8, 2002

Re: Question about --debugmsg +snoop

by Massimo

So if I understand well there's no way now to snoop a single DLL, even putting it in ~/.wine/config ?

July 8, 2002

Borland linker and VirtualQuery

by Vassilis Virvilis

Halo, The attached patch (resurrected from) wine-users through google searching fixes indeed the borland command line tools (version 5.5.1 freely downloadable on the internet). Given that I am not familiar with the win32 API, this patch looks hackish and special cased (admitted also by its author, Gerard Patel) but still it is too useful. Since this question has never surfaced to wine-devel I would like to ask what is required for the patch to become acceptable. If it is something doable I will give it a try, otherwise I will file a report in the wine bugzilla database. Any way thanks in adavance. .Bill

July 8, 2002

malloc, heapalloc, etc

by John Lightsey

Hi all, I've been playing around with the wininet dll to get a windows app I developed running, and I've written a patch that fixes the problems with wininet that I've noticed, but it's an ugly fix and I'd like to get a little clarification about how heap memory is being used in Wine. In dlls/wininet/internet.c InternetOpenUrlA() malloc() is used to put together the HTTP host header in hostreq. The pointer is then passed to HttpAddRequestHeadersA() which creates a buffer with HeapAlloc, copies the contents pointed to by hostreq to it then frees the buffer with HeapFree. Control then passes back to InternetOpenUrlA which does not call free() on the hostreq pointer. So, my question is which is the encouraged way of doing things? HeapAlloc and HeapFree or malloc and free? Also, is the fact that free() was not called on hostreq a bug, or am I missing something? Please be gentle....I'm a Perl programmer, not a C programmer.

July 8, 2002

Re: Question about --debugmsg +snoop

by Dmitry Timoshkov

"Uwe Bonnes" <bon(a)elektron.ikp.physik.tu-darmstadt.de> wrote: > Dmitry> Try +snoop=ole32.dll > > Are you sure this still works after Alexandrs's restructuring of the debug > configuration? Of course it doesn't :-( And in the mean time it's impossible to enable snooping for a single dll. > Snooping fails when the DLL exports a variable and wine exchanges that > variable with a function call. That's a rather rare thing to happen and it's not a common way of windows programming either. But in any case you are right: snooping is a very fragile feature. > The calling process accesses this function as > a variable, and writing to it crashes. The __TRY/__ENDTRY for argument > printing seems rather robust. Unfortunately not for me (debugging huge MS Office apps). Also that exception handling block somehow influences the whole way of execution of the debugged (snooped) application: it might crash without +snoop, not crash with it, and vice versa. -- Dmitry.

July 8, 2002

Re: Debugger

by Max

hmmmm... and is it possible to have a look at your tree ? :-) Alle 22:04, lunedì 8 luglio 2002, hai scritto: > Massimo a écrit : > > Hmmm.... I fiddled a bit with winedbg and found it awful to use.... > > Maybe I'm too comfortable with visual debuggers :-) > > There's no plan to make a graphical front-end to it, for example > > extending DDD or better GVD ? > > as I wrote some time ago, I have in my tree an implementation of the GDB > remote protocol inside the wine debugger, which should let any well > behaved gdb graphical front end debug a wine program (to some extent) > A+

July 8, 2002

Re: warcraft 3

by Peter Bortas

Rizsanyi Zsolt <rizsanyi(a)myrealbox.com> writes: > On Friday 05 July 2002 01:53, Bobby Bingham wrote: > > After buying Warcraft 3, and reading on the mailing list that the beta had > > worked under wine, I decided to try the final version under wine. It > > installed fine, but won't run. Or rather, when I try to run it, it prints > > this out, and just sits there: > > > > fixme:cdrom:CDROM_GetIdeInterface CD-ROM device with major ID 11 not > > supported > > fixme:cdrom:CDROM_GetIdeInterface CD-ROM device with major ID 11 > > not supported *snip* > If it is not safedisc protected, then you can simply ignore the above > messages... Warcraft 3 is SecuROM v2 protected. -- Peter Bortas http://peter.bortas.org

July 8, 2002

Re: Question about --debugmsg +snoop

by Uwe Bonnes

>>>>> "Dmitry" == Dmitry Timoshkov <dmitry(a)baikal.ru> writes: Dmitry> "Massimo" <max(a)veneto.com> wrote: >> Is there a way to activate +snoop only for selected dll ??? Dmitry> Try +snoop=ole32.dll Are you sure this still works after Alexandrs's restructuring of the debug configuration? >> I think that would help me to find AutoCAD 2000 access violation on >> startup, isolating the dll where it happens. As stated few msg >> before, it starts up good with +snoop, but it crashes on very >> beginning without +snoop. Dmitry> Also try to disable smart arguments printing in Dmitry> relay32/snoop.c,SNOOP_PrintArg() by commenting out Dmitry> __TRY/__ENDTRY block of code. Snooping fails when the DLL exports a variable and wine exchanges that variable with a function call. The calling process accesses this function as a variable, and writing to it crashes. The __TRY/__ENDTRY for argument printing seems rather robust. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

July 8, 2002

Re: Question about --debugmsg +snoop

by Dmitry Timoshkov

"Massimo" <max(a)veneto.com> wrote: > Is there a way to activate +snoop only for selected dll ??? Try +snoop=ole32.dll > I think that would help me to find AutoCAD 2000 access violation on startup, > isolating the dll where it happens. > As stated few msg before, it starts up good with +snoop, but it crashes on very > beginning without +snoop. Also try to disable smart arguments printing in relay32/snoop.c,SNOOP_PrintArg() by commenting out __TRY/__ENDTRY block of code. -- Dmitry.

July 8, 2002