January 2005 - Wine-devel - list.winehq.org

[WINETEST] How is a visible desktop detected
by Paul Vriens 28 Jan '05

28 Jan '05

Hi, I was just wondering. I have a Win98/WNT/W2K (on VMWare) and a XP Home system. All are running the winrash service. All were started when I was logged in but only the W98 and WNT were considered running on a visible desktop. What's the criteria for 'running on a visible desktop'? Cheer,s Paul.

2 2

Re: X11DRV: Fix to incorrect detection and other bugs of keyboard driver in XKB presence
by Alexandre Julliard 28 Jan '05

28 Jan '05

"Oleh R. Nykyforchyn" <nick(a)pu.if.ua> writes: > Add alternative (alpha) code to keyboard driver in x11drv that can handle > correct detection and switching of keyboard layout both with and without > XKB extension. Add temporary --enable-xkb feature to configure script > to enable compilation with new code instead of existing one. You really need to get rid of these #ifdefs. If the patch is not working well enough to be enabled by default it won't go in at all. Most likely you need to split it in smaller parts that can be tested and applied separately. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: msvcrt: translate name to locate program
by Alexandre Julliard 28 Jan '05

28 Jan '05

Michael Wu <flamingice(a)sourmilk.net> writes: > if (args) > { > - ret = msvcrt_spawn(flags, fullname, args, envs); > + if (SearchPathA(NULL, name, exeA, MAX_PATH, fullname, NULL)) > + ret = msvcrt_spawn(flags, fullname, args, envs); That doesn't look right, spawnve is not supposed to search the path. -- Alexandre Julliard julliard(a)winehq.org

3 2

Re: Re: [winecfg] Show detected audio systems, and offer selection
by Paul van Schayck 28 Jan '05

28 Jan '05

So in the end we will just keep it all the same for now? Or did I lost you all. Or do we want to follow Chris suggestion by offering a frontend to the driver load order list? Thanks, Paul

1 0

Re: [x11/keyboard] numpad 5 key
by Dmitry Timoshkov 27 Jan '05

27 Jan '05

"Oliver Stieber" <oliver_stieber(a)yahoo.co.uk> wrote: > This little patch sends a scancode through for the 5 > key when numlock isn't on. > > This is needed to fire cannons in pirates. > > I hope this is ok, a quick test showed that the > keydown was already sending a scancode, but it may be > wrong, this just fixes keyup and should be correct. > - VK_END, 0, VK_INSERT, VK_DELETE, > + VK_END, 0x0c, VK_INSERT, VK_DELETE, Running spy++ under Windows confirms that your patch is correct, you just need to use symbolic name VK_CLEAR instead of 0x0c. -- Dmitry.

1 0

RE: [d3d9] VertexDeclaration support
by Ann and Jason Edmeades 27 Jan '05

27 Jan '05

Hi Raphael, Get/SetRenderTarget in d3d9 cant be right - if has to go through wined3d, as it's the only person who knows the front/back buffer etc. You don't want This->renderTarget at all at the d3d9 level The same issue later, + if (NULL == pDeviceImpl->backBuffer) { + pDeviceImpl->backBuffer = d3dSurface; + pDeviceImpl->renderTarget = d3dSurface; Note in the call to IWineD3DDevice_CreateVertexDeclaration you passed through 9, I assume for the dx level, but we store that in the device or directx impl already (cant remember which). In the wined3d version: Also, in the wined3d version please, please try to avoid using tabs, and use spaces instead - the rest of the file does (unless I missed some as I transferred them). Tabs are a real pain to work with if you ask me Jason

2 1

Re: [ddraw] more video memory
by Oliver Stieber 27 Jan '05

27 Jan '05

--- Raphael <fenix(a)club-internet.fr> wrote: There's a couple of other places that report the amount of video memory, GetAvaialbleVideoMemory in d3d, and static DDHALINFO hal_info in X11ddraw.c Is there somewhere where we can centralise the possibly tracking of video memory and read the initial setting from either a configuration file or the video cards i2c or registers if available instead of hard coding in three+ different places? I've got some agpgart code for detecting AGP memory usage and the DRI guys will probably have code for getting the 'real' video memory figures for some cards. > Hi, > > Changelog: > - set default video memory to 64Mb (was 16Mb) as > many d3d9 demos use d3d7 > code to get available video memory size (ex > ConfigSystem.exe on d3d9 sdk) > > Todo: > - autodetect this value (better than hardcoded) and > share it using wined3d > > Regards, > Raphael > > Index: main.c > =================================================================== > RCS file: /home/wine/wine/dlls/ddraw/ddraw/main.c,v > retrieving revision 1.58 > diff -u -r1.58 main.c > --- main.c 9 Jan 2005 17:35:44 -0000 1.58 > +++ main.c 27 Jan 2005 00:22:42 -0000 > @@ -118,7 +118,7 @@ > /* This is for the moment here... */ > This->free_memory = free_memory; > This->allocate_memory = allocate_memory; > - This->total_vidmem = 16 * 1024 * 1024; > + This->total_vidmem = 64 * 1024 * 1024; > This->available_vidmem = This->total_vidmem; > > return DD_OK; > > ATTACHMENT part 2 application/pgp-signature ___________________________________________________________ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com

2 5

Re: video4linux - wine
by Rick Romero 27 Jan '05

27 Jan '05

Looks like Webcamnow.com has a simple Win32 app now. They're setup quite simply - They merely grab a pic, and ftp it to their servers. After install, I assume I'm getting the same errors you were, as it enumerates the webcam devices: fixme:avicap:capGetDriverDescriptionA (0, 0x411f1050, 255, 0x411f2ef0, 255) stub! fixme:avicap:capGetDriverDescriptionA (1, 0x411f1050, 255, 0x411f2ef0, 255) stub! You can get the webcamnow Win32 app by going to their site with Firefox or Mozilla, and clicking "Broadcast", then you'll download the win32 app. Rick Jasper van Veghel wrote: > I've recently been looking into VFW with Wine, and though I certainly am no > expert at the Windows API concerning this (first time I really looked into DX), > nor Wine for that matter, I was able to get a bit further from where I started, > so allow me to share my experiences with you. > As an application to test this stuff with I went for MSN 6.2, though certainly > not the best application for this, it seemed neat to finally have Webcam support > on MSN - I eventually got some of it working with a load of native DLLs, some > hacking on the SSL stuff (I ended up simply setting useSSL = false, the applica- > tion was sending plain-text over an SSL socket, which wasn't working; this fixed > things, or at least for this application ;-)) and adding some undocumented flag > to InternetSetOption (optionId = 87) - anyway, it seems that MSN is using some- > thing along the lines of the following webcam class I found using Google - > indeed, using a DirectShow filter: > http://www.jolash.com/projects/other_projects/webcam/WebCam.h > For things to start working under Wine I used the following native DLLs, which > I also registered with regsvr32 (for CLSIDs etc.) > COMCTL32.DLL > urlmon.dll > CRYPT32.DLL MSOSS.DLL > oleaut32.dll ole32.dll rpcrt4.dll > MSVCRT.DLL > shlwapi.dll shdocvw.dll > MLANG.DLL > qcap.dll amstream.dll > Though I'm not sure if amstream is needed. Don't know what qcap does as I only > managed to get to a point where something in qcap was called which was then > being forwarded to Quartz (IAMStreamConfig, for which I added a bunch of stubs > and semi-stubs (filled in some bogus information for VIDEO_STREAM_CONFIG_CAPS, > VIDEOINFOHEADER and AM_MEDIA_TYPE) > It turned out that, at least MSN, and this webcam class too, uses devenum to > find the video input devices (CLSID_VideoInputDeviceCategory), for which I've > added the proper code to CreateSpecialCategories and hence CreateClassEnumerator > (it also seems that the windows DLL of devenum always recreates the dynamic > registery entries whereas Wine only seems to add them once and then never again, > that is, once they're in the registry they stay there (hence if a new audio card > gets added to the system ..)) The Windows DLL seemed to be using avicap32 to > collect information on the available video input devices, so I've simply had > capGetDriverDescription return some string with a fictional video driver (this > also makes it possible to use a native devenum.dll) Next up is Quartz, which > seemed to want IAMStreamConfig (collecting information on the video stream (res, > depth, sps, ..) for starters, but I never got around to implementing enough of > that for the program to accept it and move on, so that's where I got stuck. It > may also have had something to do with MSN wanting an IKsPin which isn't imple- > mented (which is why native quartz may have failed, when trying to approach the > kernel in some way) Here's a small scenario of what I observed working with both > native and hacked up DLLs ;-) > DEVENUM - Read all VideoInputDeviceRenderer's (from CLSID) > DEVENUM - BindToObject() --> VfwCapture > QCAP - BindToClass --> Quartz(VideoRenderer) > QUARTZ - VideoRenderer_create > QUARTZ - [FAIL] InputPin_QueryInterface (IKsPin) > QUARTS - VideoRenderer_QueryInterface (IAMStreamConfig) > Anyway, the 'patches' I wrote are probably not worth much as the whole under- > taking was more of a little endeavor trying to see how far I go (MSN actually > managed to sign in, by the way, but kept crashing a few seconds after that (the > webcam stuff can be accessed without signing in though, there's a preview option > in one of the menus), but perhaps this brief explanation of my steps will prove > useful for someone wanting to implement this aspect of VFW :-) Perhaps someone > could build a control from the class I mentioned earlier which can then be used > for testing (through the webpage that refers to it says it's missing some code; > but at least it's a starting point) > Jasper

1 0

Re: NtQuerySystemInformation: cpu information
by Oliver Stieber 27 Jan '05

27 Jan '05

I'll see if darwinia runs ok now, it fails witht a cannot detect CPU error. http://www.darwinia.co.uk/downloads/ --- Rein Klazes <wijn(a)wanadoo.nl> wrote: > Hi, > > Changelog: > dlls/ntdll : nt.c > include : winternl.h > > In NtQuerySystemInformation, handle request for > information > class 1, now named SystemCpuInformation. Return > some dummy > data for now. > > Rein. > > --- wine/dlls/ntdll/nt.c 2005-01-27 > 08:32:17.000000000 +0100 > +++ mywine/dlls/ntdll/nt.c 2005-01-27 > 13:52:32.000000000 +0100 > @@ -546,6 +546,22 @@ NTSTATUS WINAPI > NtQuerySystemInformation > else ret = STATUS_INFO_LENGTH_MISMATCH; > } > break; > + case SystemCpuInformation: > + { > + SYSTEM_CPU_INFORMATION* sci; > + sci = (SYSTEM_CPU_INFORMATION *) > SystemInformation; > + if (Length >= sizeof(*sci)) > + { > + /* FIXME: move some code from > kernel/cpu.c to process this */ > + sci->Architecture = > PROCESSOR_ARCHITECTURE_INTEL; > + sci->Level = 6; /* 686, aka Pentium > II+ */ > + sci->Revision = 0; > + sci->Reserved = 0; > + sci->FeatureSet = 0x1fff; > + } > + else ret = STATUS_INFO_LENGTH_MISMATCH; > + } > + break; > case SystemPerformanceInformation: > { > SYSTEM_PERFORMANCE_INFORMATION* spi = > (SYSTEM_PERFORMANCE_INFORMATION*)SystemInformation; > --- wine/include/winternl.h 2005-01-27 > 08:32:53.000000000 +0100 > +++ mywine/include/winternl.h 2005-01-27 > 13:54:11.000000000 +0100 > @@ -521,7 +521,7 @@ typedef enum _SECTION_INHERIT { > > typedef enum _SYSTEM_INFORMATION_CLASS { > SystemBasicInformation = 0, > - Unknown1, > + SystemCpuInformation = 1, > SystemPerformanceInformation = 2, > SystemTimeOfDayInformation = 3, /* was > SystemTimeInformation */ > Unknown4, > @@ -908,6 +908,35 @@ typedef struct > _SYSTEM_BASIC_INFORMATION > #endif > } SYSTEM_BASIC_INFORMATION, > *PSYSTEM_BASIC_INFORMATION; > > +/* CPU Information Class 0x01 */ > +typedef struct { > + WORD Architecture; > + WORD Level; > + WORD Revision; /* combination of CPU > model and stepping */ > + WORD Reserved; /* always zero */ > + DWORD FeatureSet; /* see bit flags below */ > +} SYSTEM_CPU_INFORMATION; > + > +/* definitions of bits in the Feature set for the > x86 processors */ > +#define CPU_FEATURE_VME 0x00000005 /* Virtual > 86 Mode Extensions */ > +#define CPU_FEATURE_TSC 0x00000002 /* Time > Stamp Counter available */ > +#define CPU_FEATURE_CMOV 0x00000008 /* > Conditional Move instruction*/ > +#define CPU_FEATURE_PGE 0x00000014 /* Page > table Entry Global bit */ > +#define CPU_FEATURE_PSE 0x00000024 /* Page > Size Extension */ > +#define CPU_FEATURE_MTRR 0x00000040 /* Memory > Type Range Registers */ > +#define CPU_FEATURE_CX8 0x00000080 /* Compare > and eXchange 8 byte instr. */ > +#define CPU_FEATURE_MMX 0x00000100 /* Multi > Media eXtensions */ > +#define CPU_FEATURE_X86 0x00000200 /* seems to > be alway ON, on the '86 */ > +#define CPU_FEATURE_PAT 0x00000400 /* Page > Attribute Table */ > +#define CPU_FEATURE_FXSR 0x00000800 /* FXSAVE > and FXSTORE instructions */ > +#define CPU_FEATURE_SEP 0x00001000 /* SYSENTER > and SYSEXIT instructions */ > +#define CPU_FEATURE_SSE 0x00002000 /* SSE > extenstions (ext. MMX) */ > +#define CPU_FEATURE_3DNOW 0x00008000 /* 3DNOW > instructions available > + (FIXME: > needs to be confirmed) */ > +#define CPU_FEATURE_SSE2 0x00010000 /* SSE2 > extensions (XMMI64) */ > +#define CPU_FEATURE_DS 0x00020000 /* Debug > Store */ > +#define CPU_FEATURE_HTT 0x00040000 /* Hyper > Threading Technology */ > + > /* System Information Class 0x15 */ > typedef struct { > ULONG CurrentSize; > ___________________________________________________________ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com

1 0

Re: Re: [winecfg] Show detected audio systems, and offer selection
by Chris Morgan 27 Jan '05

27 Jan '05

> So just keep the Audio tab and remove the autodetect button. Or keep > it all the same. But that would bring us back to the original > question. How should we handle multiple detected audio systems? > I think removing the auto detect would the best solution. If we store a list of drivers to autodetect in the registry we can search this list on wine startup for the first working one. Maybe winecfg can provide an interface to this list? Its probably not very likely that users will run multiple high level audio systems at the same time but this should let those users work around wine detecting and using the wrong one. Although as long as we can output sound through a given interface it isn't really the wrong interface... Chris

2 1