July 2003 - Wine-devel - list.winehq.org

hello i ask about cygwin
by amdxp 15 Jul '03

15 Jul '03

1 0

Re: NT Native API was (Re: Question about WINE and adding the "low-level" CD access APIs...)
by Mike Hearn 15 Jul '03

15 Jul '03

> Well if you read http://www.sysinternals.com/ntw2k/info/ntdll.shtml, you > will see several things: > 1.most of the "native APIs" that drivers and etc use are undocumented, only > a handfull are documented in the DDK. > and 2.Quite a few of the APIs could probobly "map" onto existing bits of > wine code (for example most of the Registry APIs) Yes, in fact the registry APIs are already implemented in terms of ntdll. > The way to proceed (IMHO) is this: > 1.implement something that can load the win32 device drivers somehow ... hehe :) Easier said than done, methinks. > and then 2.implement the NT Native APIs (which are actually exported by > ntdll.dll and callable by user apps BTW) one at a time (pick a simple > driver such as the secdrv.sys from safedisk and implement the calls that it > uses) then go from there. Hmm, I'm confused. ntdll exists in kernel space too? I guess I always imagined the internals of the kernel would have its own symbol fixup system, without DLLs. But perhaps not. > For example, I got a version of SafeDisk secrdv.sys from Command & Conquer > Renegade (most recent SafeDisk game I can find in my collection) with a > size of 28400 bytes and a date of 29 january 02 and it only has 15 entries > in its "exports" segment and only 3 are not documented in MSDN library > online (NtBuildNumber, KeTickCount, IofCompleteRequest) (but best I can > work out IofCompleteRequest and IoCompleteRequest are one and the same) IIRC the kernel functions use a particular naming scheme. I forget exactly what it is, but IoCompleteRequest and IofCompleteRequest are not the same, but one is a variant of the other - much like FooA and FooW are in userland Win32. > Some of these APIs needed for SafeDisk support etc may already be > implemented or may be simple to implement) Yeah, but is it any simpler than just reverse engineering and cloning the driver? Drivers aren't needed all that often. > So, emulating enough of the guts of windows to get safedisk protected > programs (and mabie other "simple" drivers) doesnt (IMHO) seem hugly difficult. Well, rather you than me brother :) -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

2 1

Re: French keyboard layout without Euro
by Dmitry Timoshkov 15 Jul '03

15 Jul '03

"Marcelo Duarte" <wine-devel(a)bol.com.br> wrote: > I used a program that wait a input and out. I pressed ALTGR 1, E (euro), > Delete (with numlock on), numlock, delete (with numlock off) and enter. > After my mail I trying to found the problem, I discovered that the keyboard > accept keys that do not are marked in the keys, like ALTGR R (® registered), > ALTGR C (© copyright) and others (in Wine or in KDE), only do not accept > Euro. The log shows that it's clearly a problem with XFree86 which can't translate EuroSign keysym to a character in your locale (pt_BR): trace:event:EVENT_ProcessEvent Got event KeyPress for hwnd 0x10022 trace:key:X11DRV_KeyEvent state = 2010 trace:key:X11DRV_KeyEvent KeyPress : keysym=20AC (EuroSign), ascii chars=0 / 0 / '' I think that by running 'xev' you could confirm that. One of the solutions is to find an existing locale in your system which supports entering of EuroSign (look for 'locale -a | grep @euro') or generate one yourself. Probably using either pt_PT or pt_PT(a)euro might help since Brazilian locale presumably is not supposed to support the Euro sign. -- Dmitry.

1 0

[Bug 1592] Unhandled exception(?) in IDirectSoundImpl_Release
by Dustin Navea 15 Jul '03

15 Jul '03

Forwarded from bugmail.. see below forward for my question ------------------------- > http://bugs.winehq.com/show_bug.cgi?id=1592 > > ------- Additional Comments From zombi(a)mailbox.hu 2003-14-07 12:19 ------- > With the patch, TA crashed at a different location (somewhere in TA own > code), > after I looking through the available config options, I realized, that my > kernel > use alsa, and in wine config, i used wineoss.drv instead of winealsa.drv, > after > i changed that, and some minor flags, finally i can play TA in linux :-) > Thx for > the help ... :) Shouldnt we have an error essage saying that the user's wine is configured to use wineoss.drv but linux is configured to use winealsa.drv? It would be similar to the error about not being able to find the floppy that people always seem to have in their config even tho they dont have it in their fstab.. ===== -- Dustin Navea Minor Contributor, winehq.com Buzilla Janitor, bugs.winehq.com Network Admin, irc.blynk.net (down) __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

2 1

Re: French keyboard layout without Euro
by Marcelo Duarte 15 Jul '03

15 Jul '03

Em Seg 14 Jul 2003 07:24, Dmitry Timoshkov escreveu: > "Sylvain Petreolle" <spetreolle(a)yahoo.fr> wrote: > > Please find it attached. > > Thanks for the log. It took awhile to figure out what happens. > > Changelog: > Huw D M Davies <hdavies(a)codeweavers.com> > Make the return buffer larger. (For example EuroSign in uft8 is 3+1 > bytes long). > > [Fixes entering of the Euro on uft8 locales]. Hi all, I have had some problems with my keyboard, that I discovered recently, reading the recent discussions. 1) My keyboard is ABNT-2 and in keyboard.c has 2 layouts and I believe that my keyboard is ABNT-2 with ALTGR but Wine detect it as the first layout (running wine --debugmsg +keyboard) 2) All ALTGR keys give me the result except the EuroSign (see the result of wine --debugmsg +key+keyboard): err:keyboard:X11DRV_ToUnicode Please report: no char for keysym 0000 (No Name) : err:keyboard:X11DRV_ToUnicode (virtKey=0,scanCode=138,keycode=8,state=10) err:keyboard:X11DRV_ToUnicode Please report: no char for keysym 20AC (EuroSign) : err:keyboard:X11DRV_ToUnicode (virtKey=45,scanCode=12,keycode=1A,state=2010) 2) If I press the key Delete from the non-numeric keypad and the numlock was on, the comma appears. If I am correct with my observation, wine is mapping like numeric keypad delete key was pressed, but it is pressed from nom-numeric keypad (I believe that other people have the same problem, but in other keyboard layouts is mapped to "point"). Thanks in advance. -- Marcelo Duarte

2 1

Re: Web: Fix the WWN intros
by Tom 15 Jul '03

15 Jul '03

Francois Gouget wrote: >A big but trivial patch. > >Changelog: > > * Pretty much every WWN > > s/It's main goal/Its main goal/ > Also fix the capitalization of 'Windows' in the intro. > > > > >------------------------------------------------------------------------ > >Index: wwn/wn19990620_1.xml >=================================================================== >RCS file: /home/wine/lostwages/wwn/wn19990620_1.xml,v >retrieving revision 1.1.1.1 >diff -u -r1.1.1.1 wn19990620_1.xml >--- wwn/wn19990620_1.xml 2 Dec 2002 17:08:23 -0000 1.1.1.1 >+++ wwn/wn19990620_1.xml 15 Jul 2003 06:36:35 -0000 >@@ -10,8 +10,8 @@ > > <intro> > >-<p />This is the first release of Wine's kernel cousin publication. It's main >-goal is to distribute widely what's going on around Wine (the Un*x windows >+<p />This is the first release of Wine's kernel cousin publication. Its main >+goal is to distribute widely what's going on around Wine (the Un*x Windows > emulator). > > In the FAQ we have this : http://www.winehq.com/?page=faq#Is_Wine_an_emulator (A) Fortunately, no. Wine provides low-level binary compatibility, but currently only for OSes running on Intel-compatible chips. So why do we still say (the Un*x Windows emulator). ? If it's *not* a emulator ? P.S I have another patch for link fixes ( in works ) last count down to 50 from 163 ...... should be close to zero when i send the patch :)) Tom

1 0

still many warnings from Mesa
by Gerald Pfeifer 15 Jul '03

15 Jul '03

As far as I can see, patches from Raphaël resolved many related warnings I used to see (Thanks!), but using XFree86 4.3 and Mesa 3.4.2 I still get the following. Could someone please have a look at addressing these? directx.c:779: warning: implicit declaration of function `glXGetProcAddressARB' wgl.c:325: warning: implicit declaration of function `glXGetProcAddressARB' wgl.c:325: warning: comparison between pointer and integer wgl.c:334: warning: assignment makes pointer from integer without a cast opengl_norm.c:26: warning: implicit declaration of function `glActiveTextureARB' opengl_norm.c:208: warning: implicit declaration of function `glClientActiveTextureARB' opengl_norm.c:2150: warning: implicit declaration of function `glMultiTexCoord1dARB' opengl_norm.c:2160: warning: implicit declaration of function `glMultiTexCoord1dvARB' opengl_norm.c:2170: warning: implicit declaration of function `glMultiTexCoord1fARB' opengl_norm.c:2180: warning: implicit declaration of function `glMultiTexCoord1fvARB' opengl_norm.c:2190: warning: implicit declaration of function `glMultiTexCoord1iARB' opengl_norm.c:2200: warning: implicit declaration of function `glMultiTexCoord1ivARB' opengl_norm.c:2210: warning: implicit declaration of function `glMultiTexCoord1sARB' opengl_norm.c:2220: warning: implicit declaration of function `glMultiTexCoord1svARB' opengl_norm.c:2230: warning: implicit declaration of function `glMultiTexCoord2dARB' opengl_norm.c:2240: warning: implicit declaration of function `glMultiTexCoord2dvARB' opengl_norm.c:2250: warning: implicit declaration of function `glMultiTexCoord2fARB' opengl_norm.c:2260: warning: implicit declaration of function `glMultiTexCoord2fvARB' opengl_norm.c:2270: warning: implicit declaration of function `glMultiTexCoord2iARB' opengl_norm.c:2280: warning: implicit declaration of function `glMultiTexCoord2ivARB' opengl_norm.c:2290: warning: implicit declaration of function `glMultiTexCoord2sARB' opengl_norm.c:2300: warning: implicit declaration of function `glMultiTexCoord2svARB' opengl_norm.c:2310: warning: implicit declaration of function `glMultiTexCoord3dARB' opengl_norm.c:2320: warning: implicit declaration of function `glMultiTexCoord3dvARB' opengl_norm.c:2330: warning: implicit declaration of function `glMultiTexCoord3fARB' opengl_norm.c:2340: warning: implicit declaration of function `glMultiTexCoord3fvARB' opengl_norm.c:2350: warning: implicit declaration of function `glMultiTexCoord3iARB' opengl_norm.c:2360: warning: implicit declaration of function `glMultiTexCoord3ivARB' opengl_norm.c:2370: warning: implicit declaration of function `glMultiTexCoord3sARB' opengl_norm.c:2380: warning: implicit declaration of function `glMultiTexCoord3svARB' opengl_norm.c:2390: warning: implicit declaration of function `glMultiTexCoord4dARB' opengl_norm.c:2400: warning: implicit declaration of function `glMultiTexCoord4dvARB' opengl_norm.c:2410: warning: implicit declaration of function `glMultiTexCoord4fARB' opengl_norm.c:2420: warning: implicit declaration of function `glMultiTexCoord4fvARB' opengl_norm.c:2430: warning: implicit declaration of function `glMultiTexCoord4iARB' opengl_norm.c:2440: warning: implicit declaration of function `glMultiTexCoord4ivARB' opengl_norm.c:2450: warning: implicit declaration of function `glMultiTexCoord4sARB' opengl_norm.c:2460: warning: implicit declaration of function `glMultiTexCoord4svARB' Thanks, Gerald

4 15

Combo & Listboxes Locale Handling
by Michael Jackson 14 Jul '03

14 Jul '03

Hi guys, What work needs to be done to get locale handling for combo and listboxes working properly? Im looking for tips / pointers / reference to another part of wine where it is implemented / refernce to msdn to help me implement this. Thanks Mike Jackson

2 2

RE: Question about WINE and adding the "low-level" CD access APIs...
by Robert Shearman 14 Jul '03

14 Jul '03

> Date: Mon, 14 Jul 2003 20:24:31 +0800 > From: Jonathan Wilson <jonwil(a)tpgi.com.au> > To: wine-devel(a)winehq.com > Subject: Question about WINE and adding the "low-level" CD access APIs... > > Many copy protections use special tricks on the CDs (I dont know the > details). Presumably these protections use some kind of > lower-level API to > access the data on the CD directly (instead of going through the file I/O > calls). Currently TransGaming does something specific for each > kind of copy > protection to make it work. Would it be possible to implement > these APIs in > WINE and have them redirect to whatever low level APIs are provided by > linux/x/whatever? That way (assuming the implementation was > complete), any > copy protection would work (i.e. when the protection says "give > me this bit > of data from the CD in this form", WINE hooks that, gets the > relavent data > and returns it to the application. I believe this can be done in ASPI, and has been already implemented. At least this is how SafeDisc v1 worked. > Same could be said for > protections that > use the "boot blocks" to store licence data (such as CDilla Licence > Manager), for those you could hook the "read from boot block" and > "write to > boot block" calls and store the data somewhere (preferably not the real > boot block :) You would probably need to run Wine as root to do this (as you would need to run the game as Administrator in WinNT), but the API's should be there. > If someone can tell me what the low-level access that these > protections use > is actually called (i.e. what search term to use in MSDN to look for > documentation etc) as well as info on whatever the relavent linux > low-level > access stuff would be, I can look at drawing up some kind of "here is how > this could be done" document. Again, I guess most protection methods (that would work on NT) would probably use ASPI. > Similar low-level hooks could be used to allow things like AudioCatalyst > (program that converts audio-cd tracks to MP3 files) and anything > else that > does lower level access to CDs/DVDs than the high-level file I/O APIs and > etc. (the day its possible to run Nero Burning Rom in WINE with > no problems > will be a great day indeed for the project :) Well in that case, the great day was a while ago as I have already burnt a CD in Nero (with version=Win2k). I'm not sure about AudioCatalyst but I see no reason why our current ASPI implementation shouldn't work. > If this isnt fesable for copy protection and so on, please explain why (I > know nothing about copy protection or how to program the CD-ROM in win32) > Basicly, I dont understand why there is a need for "protection-specific" > code in WineX when you could emulate whatever the protection uses and > appear just like real windows to the game... > Laurent Pinchart did a lot of work on this, but unfortunately a lot of it wasn't accepted into the Wine tree. Though his patch is available at http://www.winehq.com/hypermail/wine-patches/2002/04/0194.html. It may require some major work to get it working now, as I believe some of the hooks he used (in relation to NT kernel shared memory) have been removed now. Note that I'm unsure the un-hackish parts weren't accepted, although a good guess would be DMCA. Rob

1 0

Re: Mac OS X Support : Winebuild Assembler syntax
by Pierre d'Herbemont 14 Jul '03

14 Jul '03

ioops, this one was old, and buggy, sorry I didn't notice. You might prefer this one ;) Alexandre, I think I did find how to manage with the ".skip" instruction on darwin with mach-o, I use the .fill instrcution. I assumed that the ".skip n" instruction allocate n bytes. Thanks, Pierre On lundi, juil 7, 2003, at 14:02 Europe/Paris, Pierre d'Herbemont wrote: > Hi! > > This patch fix (again) the ppc syntax for Mac OS X's ld. I took care > of Alexandre suggestion. > > Hope it will be ok ;) > > Pierre > > ModifiedFiles: > tools/winebuild/import.c > tools/winebuild/spec32.c > tools/winebuild/build.h > > ChangeLog: > - Add support for Mac OS X's ppc assembler syntax. >

1 1