wine-devel August 2004

wine-devel@winehq.org

122 participants
273 discussions

Re: ADVAPI32: implement SetThreadToken using NtSetInformationThread
by Dmitry Timoshkov 13 Aug '04

13 Aug '04

"Mike McCormack" <mike(a)codeweavers.com> wrote: > @@ -545,6 +545,12 @@ > case ThreadBasePriority: > case ThreadAffinityMask: > case ThreadImpersonationToken: > + { > + const HANDLE *phToken = data; > + if (length != sizeof(HANDLE)) return STATUS_INVALID_PARAMETER; > + FIXME("Set ThreadImpersonationToken handle to %p\n", *phToken ); > + return STATUS_SUCCESS; > + } Probably ThreadImpersonationToken handling should be isolated from other thread class identifiers otherwise FIXME will be printed for all them as well. -- Dmitry.

1 0

Missing Registry Value "VersionNumber"
by "Adrian Willenbücher" 13 Aug '04

13 Aug '04

I tried to install MS Visual Studio 6, but the install program exited after two seconds without error message. When I read the debug logs, I found out that the installer needs the following value: HKLM\Software\Microsoft\Windows\CurrentVersion\VersionNumber I had a look at my original Windows (98 SE) system.dat and there the value was set to "4.10.2222". I added the value with regedit in wine and the program was satisfied :-) Does someone know more about this value and its necessity? Should it be added to wine's standard set of registry keys and values? Here are some sites about these version numbers: 1) http://garrett.vdsworld.com/winver.htm 2) http://www.admins-tipps.net/software/microsoft/microsoft_windows_versionen.… 3) Googles translation of 2): http://translate.google.com/translate?hl=en&sl=de&u=http://www.admins-tipps… My wine is set to win98 and it doesn't use an original Windows installation. -- NEU: WLAN-Router f�r 0,- EUR* - auch f�r DSL-Wechsler! GMX DSL = superg�nstig & kabellos http://www.gmx.net/de/go/dsl

1 0

Win API Stats
by Tom 12 Aug '04

12 Aug '04

Hello, The Win API Stats page is broken in a bad way! See: http://www.winehq.org/site/winapi_stats I think we should just go with http://fgouget.free.fr/wine/winapi_stats-en.shtml and link to it. and kindly ask Francois to update it from time to time. And it has always been far better than the page on winehq... just my $.02 Tom

5 4

Re: ATL: DllRegsterServer
by Mike McCormack 12 Aug '04

12 Aug '04

Steven Edwards wrote: > Note: While this does allow my test app to install and run I dont think > this is correct because I dont have the ATL CLSID. > > Changelog: > Implement DllRegsterServer and DllUnregsterServer Windows 2000 has: ["CLSID\\{44EC053A-400F-11D0-9DCD-00A0C90391D3}"] @="Registrar Class" ["CLSID\\{44EC053A-400F-11D0-9DCD-00A0C90391D3}"\\InprocServer32] @="c:\winnt\system32\atl.dll" "ThreadingModel"="Both" Mike

1 0

Re: dsound mixer speedup
by Joerg Mayer 12 Aug '04

12 Aug '04

On Thu, Aug 12, 2004 at 12:24:20AM -0400, Robert Reif wrote: > Speed up mixing and unmixing by moving sample size and buffer > wrap tests to outside the loop. The code is not as compact or > pretty > but it should be faster. Just out of curiosity: *IS* it really faster? Maybe gcc already did the optimization? Ciao Joerg -- Joerg Mayer <jmayer(a)loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.

2 1

Future of .wine/config
by "Adrian Willenbücher" 12 Aug '04

12 Aug '04

Hello! I read on another thread that the config file is going to disappear in future wine versions. While I think that the dosdevices-principle is a good idea (it's very intuitive), there are several disadvantages in moving the content of the config file to the registry: 1. Even if the registry keys and values of wine's configuration should be well documented, it's easier to set some values using a text editor than to use regedit and look for the keys. 2. Although it might be convenient to access both, wine's and the Windows programs' data, using the same functions, this should not be done as there should be a clear distinction between wine and the programs it runs. 3. If a program misbehaves and messes up your registry and/or if you decide to start again with a clean installation, you just delete some registry files and directories and have a new system (I think of the case you don't work in a native Windows installation) without to setup wine's configuration again. 4. To put wine's configuration into the registry is a step towards a "Wine-is-Windows", i.e. not just providing Windows' functionality but also behaving like Windows (and this should be avoided under all circumstances ;-) ). Wine is "just" an emulator for Windows, it is not supposed to be a new "Open Source Windows". The Windows' handling of configuration data (every application puts its data into the same two files: the registry) is inferior compared to the Unix' one's (every application has its own configuration file/directory in a common place). This makes it difficult e.g. to manually deinstall a program/software package. Well, my opinion. What do you think about it? -- NEU: WLAN-Router f�r 0,- EUR* - auch f�r DSL-Wechsler! GMX DSL = superg�nstig & kabellos http://www.gmx.net/de/go/dsl

2 3

Re: config converting problem
by Mike Hearn 12 Aug '04

12 Aug '04

PS I've added wine-devel back as from the wording it sounded like it was meant to go there: wine-devel is one of these annoying old-skool lists which don't rewrite Reply-To, but that rant is something for another time :) Holly Bostick wrote: > Yeah, fine, "it sucks"-- and I admit that I myself never install to > "C:\Program Files", under Windows or Wine, but geez guys-- who do you > think your users are when you say things like this? > > They're *Windows users*. And that means they probably use the defaults, > and that means that their whole data tree is in ./wine. And if that data > tree meant so much to them that they installed Wine in the first place, > it's kinda cold to say "just blow it away". Well, I'd guess that most users run perhaps one or two apps in Wine at the most, unlike Windows users who run lots and lots of apps. So every so often reinstalling these programs is not such a big deal, unless you have things like the Office XP activation scheme which don't like that. > They're non-technical (a behaviour encouraged by being a Windows user). > So while I'm sure they're used to "blowing away" their Windows > installation regularly (due to the "non-technical" nature of things like > My Documents rather than putting your bloody docs on another partition > rather than C:\, for example), since half the reason to move to Linux is > to put an end to that necessity, it seems a bit odd to reinstate it here. Yeah, I agree that at minimum we should force My Documents elsewhere, and maybe have wineprefixcreate link H: to $HOME along with putting a label on that drive saying "Save Your Files Here" (or whatever). > Wouldn't it just make more sense to *separate the config files from the > (wine) system files*?? Why in the heck is fake_windows in the ./wine > directory anyway??? Good question. I suspect the answer is "because it's always been there" :) > 1) it's hidden, so if I'm inexperienced and non-technical, I don't even > know where my programs are; Yes this is a fairly common question. TransGaming put a ~/Transgaming_Drive symlink in the home dir. Proposal: patch wineprefixcreate to build "~/Virtual C Drive" as the users fake windows tree (notice the lack of ugly underscores)? Cons: - Some users may not like it (really there's not much useful stuff in there except the program EXEs) - Are there issues with spaces in the paths used for these drives? I don't think we want to have underscores here - Localization: do we really want to translate "Virtual C Drive" into a bazillion languages? If so is the support hassle of having everybodies C drive in a different place worth it? OTOH you can say "the C drive is always in ~/.wine/dosdevices/c:/*" and be done with it. > 2) there is no reason I should have to "blow away" my data just because > I have to blow away the config. Reinstalling a program over itself is > far far easier than reinstalling it from scratch, and that doesn't even > cover the pure data that might be in "C:\My Documents". Well by "config" we mean: * Drive mappings * Registry * Config file, or what's left of it :) In future the config file will disappear and you'll only have the registry. The problem is we don't have a good way to upgrade it. Currently once the users .wine is created their registry is "static" and even if we improve the default registry it'll never be recreated. Ditto for COM registrations, they are only done at wineprefixcreate time as well. This comes back to the discussions me, Dimi and Alexandre were having a while ago. So for now the easiest way to make sure you're up to date is just to reinstall stuff because if you delete the registry, you also lose app settings and quite a few programs don't like their registry trees disappearing. > And I don't see why we don't gently educate the users in the importance > of this issue (as a dedicated dialog would certainly do), but instead > just let them keep on doing things the same old crummy Windows way, as > if it was ever a good idea. Many users don't read info/error dialogs especially when technical, likewise Wine has to be auto-configuring. Not only is it required by most packaging technologies (they don't allow user interaction, often by design) but if we want Wine to ever stabilise and become a part of most distros base sets again it has to involve zero user interaction to setup.

3 3

Re: developers-hints.diff
by Ivan Leo Puoti 12 Aug '04

12 Aug '04

> I dont think so....... I know, sorry about that, but in the wine-patches archives there appears to be an extra space amstream/ - MultiMedia Streams + atl/ - Active Template Library avicap32/ - AVI capture window class but if I do the diffing on my pc I don't get this. But patching works with both your patch, that appears to have the extra space, but doesn't, and with my patch that doesn't appear to have an extra space. I have of what is going on. BTW the patch that I sent was edited manually, so had a missing space at every added line. Ivan.

3 2

Re: X11DRV: Fix signed/unsigned comparison warnings
by Rein Klazes 12 Aug '04

12 Aug '04

On Wed, 11 Aug 2004 23:10:29 +0200, you wrote: > static int LookupEntry(LFANDSIZE *plfsz) > { > - int i, prev_i = -1; > + unsigned int i; > + int prev_i = -1; > > for(i = mru; i >= 0; i = glyphsetCache[i].next) { ^^^^^^^ Hey, this comparison is now always true, does gcc does not warn about this? I am afraid that this exercition is in many cases changing perfectly valid C code, but with warning, to possibly buggy code without warnings. I do not like this idea at all. Rein. -- Rein Klazes rklazes(a)xs4all.nl

1 0

RESEND CryptEnumProviders a->w cleanup and tests
by James Hawkins 12 Aug '04

12 Aug '04

Hi, I'm not sure whether these two patches were misplaced or they were considered not good enough to be committed, but I've included the patches now. I spent a lot of time hunting down any bugs in my unicode version of CryptEnumProviders as well as writing tests of its functionality. All the tests succeed except for one (wrong error message being sent back from undersized buffer) but that bug is a part of the original CryptEnumProviders as well and as soon as this patch can be committed, I can submit a fix for that bug. If there turns out to be problems with the patch, or the style is not up to par with wine coding standards, please let me know, because I really want to get this committed. -- James Hawkins

1 0

← Newer
1
...
17
18
19
20
21
22
23
...
28
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel August 2004