- Wine-Devel - list.winehq.org

Re: Added path settings to winecfg
by Marcelo Duarte Aug. 16, 2004

Aug. 16, 2004

Hi, I think that you do not need to modify the .rc files from languages other than En.rc and your native language. If you do not translate, it will more easy to us to known that it is wrong and needs to be translated. This is my position in relation to Pt.rc. Thank you. Jacek Caban wrote: > Changelog: > Added path settings to winecfg. > >

2 1

Re: update the faq take 2 : faq-2.diff
by Andreas Mohr Aug. 16, 2004

Aug. 16, 2004

Hi, On Sun, Aug 15, 2004 at 06:23:05AM -0400, Tom wrote: > > Hello, > > change dll's back to dlls > > Tom > > Changelog: > remove rewind section due to lack of updates Hmm... Rewind is an important part for companies who choose to not publish all of their source under the (L)GPL (but hopefully do publish smaller utilities not essential to their core business :-). As such it might be useful to keep the reference. (to such companies at least ;-) Are there any "GPL-unencumbered" (ugh, gotta hate that word ;) alternatives? I don't know of any, so... Greetings, Andreas Mohr (who certainly would not be too unaffected by the non-availability of a rewind tree ;-)

2 1

WWN 235
by Tom Aug. 16, 2004

Aug. 16, 2004

Sorry my bad :) as it is now correct Tom

1 0

WWN 235 went from bad to worse!
by Tom Aug. 16, 2004

Aug. 16, 2004

Hello, In reference to Winehq frontpage error..... Now it looks like : c:\\windows is not accessible Error (con't) Tom

1 0

Re: wine/dlls/commdlg fontdlg.c
by Vincent Béron Aug. 16, 2004

Aug. 16, 2004

Le ven 13/08/2004 à 20:42, Alexandre Julliard a écrit : > ChangeSet ID: 13294 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2004/08/13 19:42:35 > > Modified files: > dlls/commdlg : fontdlg.c > > Log message: > Jacek Caban <jack(a)itma.pwr.wroc.pl> > Fix a bug in passing parameters to CFn_WMInitDialog and CFn_WMCommand > in FormatCharDlgProcW. > > Patch: http://cvs.winehq.org/patch.py?id=13294 > > Old revision New revision Changes Path > 1.69 1.70 +2 -5 wine/dlls/commdlg/fontdlg.c At least the last part of this patch looks wrong. - return CFn_WMCommand(hDlg, wParam, lParam, lpcf32a); + return CFn_WMCommand(hDlg, wParam, lParam, (LPCHOOSEFONTW)lpcf32w); This cast is absolutely non-sense, as lpcf32w is already a LPCHOOSEFONTW. Aslo, CFn_WMCommand expects a LPCHOOSEFONTA as its fourth parameter, not a LPCHOOSEFONTW. Maybe just changing the cast to LPCHOOSEFONTA would work, but a quick glance in CFn_WMCommand told me it uses some A fields of that structure, so maybe it's not enough and we'll need to actually do a conversion (or transform CFn_WMCommand to expect a LPCHOOSEFONTW). Vincent

3 2

provider type of Microsoft Base Cryptographic Provider v1.0
by James Hawkins Aug. 15, 2004

Aug. 15, 2004

Hi, If you run regedit in wine and view the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider Types\Type 001 Type 001 does not have a "TypeName" value. Should Type 001 have a "TypeName" value? CryptEnumProviderTypes calls RegQueryValueEx on this value to see what the provider type is, but fails (but not in an obvious way). Should RegQueryValueEx return an error code describing that there is no such value? If so, what is the error code/name? -- James Hawkins

1 0

config converting problem
by Henning Gerhardt Aug. 15, 2004

Aug. 15, 2004

Hi all, a friend of me would update the wine package (20030813) from his SuSE 9.0 system to the latest availabe package for this system (20040716). After the update following error message appears on each start of wine: .... Warning: the specified Windows directory L"C:\\Windows" is not accessible. Warning: the specified System directory L"C:\\Windows\\System" is not accessible. He get me also an output of the first wine start: Created symlink /home/julian/.wine/dosdevices/c: -> ../${HOME}/.wine/fake_windows .... Created symlink /home/julian/.wine/dosdevices/y: -> ../${HOME} .... Warning: the specified Windows directory L"C:\\Windows" is not accessible. Warning: the specified System directory L"C:\\Windows\\System" is not accessible. After my advise to get me the content of his "~/.wine/dosdevices", he send me the following output: .... lrwxrwxrwx 1 julian users 28 10. Aug 18:50 c: -> ../%HOME%/.wine/fake_windows .... lrwxrwxrwx 1 julian users 9 10. Aug 18:50 y: -> ../%HOME% .... and he send me also his config file (snipped content): [Drive C] "Path" = "${HOME}/.wine/fake_windows" "Type" = "hd" "Label" = "fake_windows" "Filesystem" = "win95" ... [Drive Y] "Type" = "network" "Path" = "${HOME}" "Label" = "Home" "FS" = "win95" .... (I translated the german dialog with him to english) I think the problem is the ${HOME} variable which is not parsed / correct replaced during the convert process. Have anyone an idea to solve this problem ? Or is it only a problem of the SuSE distribution ? Regards, Henning

7 16

Windows Default Button Observations
by Zach Gorman Aug. 15, 2004

Aug. 15, 2004

While fixing some compatibility problems in Wine relating to my app, I had the opportunity to compare how Wine handles default buttons to how Windows handles them. [Definition: Default buttons have the BS_DEFPUSHBUTTON style, are drawn with an extra-thick border, and are the buttons chosen when the user types Enter.] I fixed a couple problems today, but there are more issues left: ------- (1) Windows: When a dialog is deactivated in Windows, all buttons are made non-default. When it is activated again, Windows remembers which button was last the default button and makes it default again. It does all this by means of BM_SETSTATE messages. Wine: Default buttons are unaffected by activation/de-activation of their parent dialogs. (2) Windows: When the user clicks and holds on a button, then moves the mouse off that button before releasing it, the button is made default and receives the focus. The existing default button is made non-default. Wine: The button receives the focus but is not made default. -------- My impression is that (1) could be handled by remembering the default button (which, as Krishna Murthy has shown, is not the same as the default button id) in the DIALOGINFO structure. Number (2), however, is more difficult. When a button receives the capture, it can send a BM_SETSTATE to itself easily enough to make itself a DEFPUSHBUTTON, but how does it determine which other buttons to query and make non-default as necessary? It could simply query all its sibling controls, but this wouldn't work if it was contained within a sub-window in the dialog box. How can it determine how far up the hierarchy it needs to go? Any comments would be welcomed. Thanks, Zach

3 4

Large memory reporting
by Ivan Leo Puoti Aug. 15, 2004

Aug. 15, 2004

> /* work around for broken photoshop 4 installer */ You may have to consider handling this like Microsoft does. If you read trough m$ blogs, you'll find that what microsoft usually does is have all sort of workarounds for broken apps, without them lots of stuff would not run on window xp. To work like windows, wine will have to do the same. For example, at some point m$ found that a game called "The sims" didn't work on recent versions of windows, because it freed some heap memory, and then immediately tried to access it. The M$ guys had to reverse engineering the game to find this out, and then introduced a hack that would make windows compensate for the apps bug. The game did work on previous versions of windows. M$ has it's code full of this stuff, they give priority to m$ apps, followed by stuff from big vendors like IBM, adobe, macomedia and so on. Wine will have to unfortunately do the same to achieve 100% compatibility for all the apps that work on windows only thanks to specific hacks. I'm not saying that it's a good solution in this case, but at some point this sort of stuff will have to be done. Ivan.

2 1

Large memory reporting
by Shachar Shemesh Aug. 15, 2004

Aug. 15, 2004

Hi list, I have a Windows program that tries to find out how much memory it has at its disposal using "GlobalMemoryStatus". The machine has 4GB of physical memory and about 100MB of swap. GlobalMemoryStatus returns 2GB of physical memory and 0 available swap. It seems the problem is at dlls/kernel/heap.c, around lines 1150. First we make sure we never report more than 2GB of total or available memory, and then we make sure that we never report more than 2GB combined available physical+swap memory (which effectively zeros the available swap if there is more than 2GB of available memory). The comment next to this is: /* work around for broken photoshop 4 installer */ While I understand the need for the workaround, this significantly reduces the usefulness of the whole function. My question: Can we make these two rounding conditional on the application not wishing to work with more than 2GB? I.e. - can we let applications that were linked with LARGEADDRESSAWARE see the true state of the machine? If so, is there a way for me, when at the heap.c code, to know whether that flag was set on loading the current process? Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

2 1