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

Re: DirectX API information - where?

by Vincent Béron

Roland a écrit : > > At 10:47 PM 4/3/02 +0200, Andreas Mohr wrote: > >search.microsoft.com. > > > >That's where I get quite some information from. > > > >Apart from that, mostly web searches and my pretty good collection of > >books (it's starting to extend to 1 meter of expert windows books now :-) > > Ok, let me ask this question: > > where do you get the information about the *nix API, the X-Windows API, > OpenGL etc? > > Roland *nix: man 3 should have a lot of info. X-Window (without the "s"): www.xfree86.org. If you want something more portable, try starting at www.x.org. OpenGL: www.opengl.org There are also a ton of books on each of those subjects, although picking the good ones is difficult. Vincent

April 3, 2002

Re: DirectX API information - where?

by Roland

At 10:47 PM 4/3/02 +0200, Andreas Mohr wrote: >search.microsoft.com. > >That's where I get quite some information from. > >Apart from that, mostly web searches and my pretty good collection of >books (it's starting to extend to 1 meter of expert windows books now :-) Ok, let me ask this question: where do you get the information about the *nix API, the X-Windows API, OpenGL etc? Roland

April 3, 2002

DeviceIoControl

by Laurent Pinchart

Hi everybody, I need to add support for a currently unsupported VxD, and I'm quite puzzled by the way that DeviceIoControl currently processes the device control requests. DeviceIoControl starts by checking the high word of dwIoControlCode, which is the device type. If the device type is 0, it gets a client ID by sending a get_file_info request to the server, and uses the client ID as the device type. It then looks in the VxD table for a handler for the device type, and calls it if it exists. No problem with that. If the high word of dwIoControlCode is not 0, it checks if the device is a CDROM (by calling GetDriveTypeA). If so, it calls CDROM_DeviceIoControl, and if not is just fails. I was wondering why the same VxD table as for (HIWORD(dwIoControlCode) == 0) wasn't used when the device type in dwIoControlCode is not 0. It seems to be a mistake to me. I was thinking about implementing the following algorithm: - check HIWORD(dwIoControlCode) - if 0, deviceType = GetCliendID( Device ) - if ! 0, deviceType = HIWORD(dwIoControlCode) - look for a VxD handler in the VxD table using the deviceType. - call the handler if it exists, fails otherwise This leaves out the special case for CDROM_DeviceIoControl. Could anyone explain to me why that special check is needed, if it is ? Thanks in advance. Laurent Pinchart

April 3, 2002

Re: Startup fix for scanbin 6.0

by Dimitrie O. Paun

On April 3, 2002 03:58 pm, Stefan Leichter wrote: > + if (!str) { > + ERR("called without text\n"); ^^^ This is not an ERR (which signals an internal Wine error), maybe a WARN, but I would suggest instead just: + if (!str) return 0; -- Dimi.

April 3, 2002

VirtualAlloc bug ?

by Laurent Pinchart

Hi, I tried to use VirtualAlloc with MEM_COMMIT to map a page at address 0x7ffe0000. The call to VirtualAlloc failed with ERROR_INVALID_ADDRESS. I then tried to reserve the pages first, using VirtualAlloc with MEM_RESERVE, and the call to VirtualAlloc/MEM_COMMIT worked fined after that. The MSDN state that "(MEM_COMMIT) If a memory page is not yet reserved, setting this value causes the function to both reserve and commit the memory page.". Is that a wine bug ? I can try to fix it, but I'm scared to break something in VirtualAlloc, as I'm new to wine internals. Laurent Pinchart

April 3, 2002

Re: Read of memory location 0x7ffe0000 in windows NT

by Laurent Pinchart

> > After some investigation, it seems that reading the memory location > > 0x7ffe0000 should return KeTickCount.LowPart to the user process. Has > > anyone ever heard about that ? I was wondering if it was a native windows > > NT behaviour, or if it was done by a special kernel-space exception > > handler installed by the program. > > It's a native NT thing; a page of memory at that address is shared > between user and kernel space. The definition in the w2k ddk. I downloaded the w2k ddk, and SharedUserData seems to be located at 0xffdf0000 (line 5099 of ntddk.h). Did Microsoft move the page around between NT4 and NT5, or is there something I don't understand ? Laurent Pinchart

April 3, 2002

Re: Removed sorting of registry key values

by Paul Millar

On Wed, 3 Apr 2002, Andriy Palamarchuk wrote: [snip - Eric's info on why the registry has to be sorted] > The tests show that values are exported in the same > order in which they are created. This means the values > are stored not in any particular order. That doesn't necessarily follow ... The export function(s) could map the sorted registry back into its original order. At the cost of sizeof( void *) bytes per registry entry (perhaps less, I haven't looked too closely at the registry code), you could have the registry keys sorted (for fast access) and export back into the original order in O(n) Is it worth the memory for that level of compatibility? ---- Paul Millar

April 3, 2002

Uninstaller issues on windows

by Steven Edwards

Hola Andi, I've built the uninstaller under mingw32 but have been having problems getting it to work. It will crash shortly after startup. Is it being developed on win32 or is it wine only? If you don't mind supporting it on windows I will send you a full bug report. Thanks Steven _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

April 3, 2002

Re: DirectX API information - where?

by Andreas Mohr

On Wed, Apr 03, 2002 at 07:09:52PM +0200, Tels wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Moin, > > I want to learn more about the directx and general windows APIs. Now > I looked at some books, but was very unsure as to buy what and where, if > ever. > > First, it seems that good books about these topics come from Microsoft > Press. Naturally I don't want to support them ;) > Second, it seems that you need for the examples and SDK Visual C++ - again > from MS. Eeek! > And of course, you have to run and use it under Windows *sigh* > I am also worried about the different EULAs, licence and all that other > stuff "tainting" me - even though I do believe that all of this stuff isn't > legal binding for me anyway. But you never know. > > So, my question: Where can I obtain *free* information about the API's, > their working etc. What do you use? Books you can advise? search.microsoft.com. That's where I get quite some information from. Apart from that, mostly web searches and my pretty good collection of books (it's starting to extend to 1 meter of expert windows books now :-) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 3, 2002

Re: dynamic .fon conversion

by Huw D M Davies

On Tue, Apr 02, 2002 at 11:38:53PM +0900, Dmitry Timoshkov wrote: > "Huw D M Davies" <h.davies1(a)physics.ox.ac.uk> wrote: > > > > Now, IIRC (Huw will correct me if I'm wrong), it was said that > > > FreeType also supports Postscript fonts and .fon fonts. So the way to go > > > would be to extend Wine's FreeType support to .fon fonts. > > > > Yes, that's the idea. At the moment we ignore any font that isn't > > sfnt format (that's anything that isn't TT or OpenType). The issues > > are that we need to implement something sensible for GetGlyphOutline > > and GetOutlineTextMetrics for bitmap or Type1 fonts. > > I would expect that for at least very first time that functions will > fail for bitmap fonts and return glyph data in GGO_BEZIER format for > Type1 fonts. Later we can add cubic <-> quadratic spline conversion > routines and some special handling for bitmap fonts. Most applications > don't use or provide advanced vector graphics at all. As a side effect > of adding support for bitmap fonts will be retired x11drv font support. > and a possibility for real WYSIWYG in printing. For bitmap fonts to be useful GetGlyphOutline will have to return the bitmaps for GGO_BITMAP (this probably isn't what Windows does, but I think we can live with the difference). Of course once we do it for .fon's then .pcf/.bdf come almost for free. Actually I expect the hard bit is getting the TEXTMETRICs right. Huw.

April 3, 2002