wine-devel September 2005

wine-devel@winehq.org

136 participants
273 discussions

winspool: ERROR_INVALID_NAME in GetDefaultPrinter() ?
by Detlef Riekenberg 09 Oct '13

09 Oct '13

Hi. >From which configuration does the "ERROR_INVALID_NAME" came from, when calling GetDefaultPrinter(NULL, &size) and no Printer is installed? This Test is Present in the current "dlls/winspool/tests/info.c". MSDN told us, that we receive an "ERROR_FILE_NOT_FOUND", if no Printer is installed: http://msdn.microsoft.com/library/en-us/gdi/prntspol_0hma.asp I get the "ERROR_FILE_NOT_FOUND" on win98se, winme, w2k and win2003 in this Situation. -- By By ... ... Detlef

3 3

The status of the wintab dll
by Robert North 24 Dec '07

24 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think after the 10 or more patches to the Wintab dll that I submitted last month, I should say something about it's status... And of course thank Alexandre for applying those patches. P.S. I won't be available from the 15th for about a week or so. So, if you have any questions, I'm afraid you might have to be patient. Hope this is of interest to someone -Rob. ******Applications: Current status*********** ***In Painter 5 *Cursor pressure works. (Therefore is usable by most) *Cursor orientation is a little odd: The orientation maths needs to be re-done. *No eraser. Haven't yet cracked what enables the eraser. *Doesn't work in desktop mode: Need to map to desktop coordinates. *Repeats windows bugs where cursor looses pressure/orientation info almost bug for bug (Is this a feature? ;-) *Cannot detect pressure/orientation int the "Brush Tracking" window: The tablet context is attached to the main window, so no events get to the popup, even if they overlap. This is not how windows wintab functions. ***In Photoshop 6. *Can only get tablet data in desktop mode: This is because the tablet context is attached to the desktop. Which generates/receives no wine events outside desktop mode. * Eraser and pen pressure working. *But* to get them working, you must have 3 XInput devices listed in your XF86Config file, They need to be the last entries in the "ServerLayout" section and the following order: eraser, tablet mouse. This is a far from ideal way of specifying the devices Wintab should use :-/ I'll document this if someone can point me to a good place to put the docs. *******To Do************* 1. Look at X11 errors. There appear to be some errors that deny some users the ability to access Wintab enabled apps. (I think I know how to fix this) 2. Improve orientation data. Orientation comes in as X-Y coords (Implicit Z), and has to leave as spherical coords. This calculation needs to be re-done. 3. When tablet context is on top, let it read XInput events from all the app's top-level windows. (This simulates the fact that the context is usually designed to cover the whole screen) 4. When tablet context is attached to desktop, read XInput events from all the app's top-level windows. 5. Tests ~ --My current philosophy on tests is... ~ Use Photoshop & Painter, any formal tests ~ can be written if anyone else gets involved in patching Wintab, to avoid regressions, and conflict. **********Long term to do (Anyone interested?):********* There's a lot of work that could be done here, but what gets done and who does it probably depends upon whether anyone finds an app that needs these features. I'd love to implement these, but realistically, I don't foresee doing this unless someone hires me to do so ;) 1. Improve configuration of wintab. Wintab could probably do with some information entered into the config file, to avoid the user having to hack their Xfree86cfg file. 2. Handle Z-Order of context properly. This entails *sharing Z-Order between apps. *Working out exactly what role windows have in determining tablet context z-orders. *Allow tablet contexts that don't cover the whole screen/tablet. *Handle inter-application clipping of tablet contexts *Allow all application's windows to receive tablet events when tablet context is on top 3. Implement non-system tablet contexts (Where system cursor not moved by pen or mouse) 4. Unicodify 5. Implement various wintab extensions. 6. Implement wintab manager functions. 7. Tests. *********Unknowns********* 1. How are wintab contexts are raised lowered? Contexts have their own z-order independent of windows, and their own viewport concept, based upon the tablet's coordinate system, not that of the OS. It appears that entering, or clicking on the window the tablet context is attached to will raise/lower the context. But I haven't done much testing on this. In particular, what happens if more than one app request their tablet context is attached to the desktop? 2. How Painter detects the eraser. Have 3 possibilities i. Windows can detect an eraser, and sends specific messages. (I'm sure I've seen this, but can't work out where!) ii. Only works if tablet and cursors are named correctly. (Probably linked to wacom tablets only). iii. I've missed something 3. Requirements of other applications -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCC8zI2vfwxdLxwWYRAsisAJ4q2gAYTgRc6f9wDI+Ruv943eDxOQCfcl3s /ZKMUGwQOuw/SIIbOkIUbd0= =R4M7 -----END PGP SIGNATURE-----

2 1

comctl32.dll: Running siap and modules under wine, first steps
by Maximiliano Curia 12 Jun '06

12 Jun '06

Hi, I'm trying to use a program called "siap"[1] under wine. It's the required program to pay taxes that the Argentinian government uses. So, it's quite important for the free software community in Argentina to be able to use it in a free software environment. However, I haven't heard of any real success on it, so far. I've been trying to make it run using winetools[2], and differents versions of wine. The furthest I've gone, has been with version 20050310 and all the "plugins" that winetools provides, installed. Only then, could I install the application, run it, switch between the different modules (although it worked only sometimes), but I can't really use it. There are a couple of important widgets that seem to be incompatible with wine. But as I'm not an expert neither in Windows nor in wine, the one I could really track down is a TreeView widget (from comctl32.dll) (from the main window of the program), that is not fully implemented in wine, and by using a native comctl32.dll (I tried using the win98, winme, win2k libraries) the widget would work but some of the other stuff, like switching to one of the modules wouldn't. I made a screenshot to make this clearer, the wine version[3] and the w2k version[4]. So, what should I do next? Is there some documentation of how to implement a certain Windows widget in wine? Is anybody working in this dll, or has worked on this widget? I'd appreciate any comments. Thanks, [1] http://www.afip.gov.ar/programas/siap_main.asp (spanish only) [2] http://www.von-thadden.de/Joachim/WineTools/ [3] http://gnuservers.com.ar/~maxy/wine/siap-wine.png [4] http://gnuservers.com.ar/~maxy/wine/siap-w2k.png -- Saludos, /\/\ /\ >< `/

4 8

Window geometry problem
by Pavel Troller 28 Nov '05

28 Nov '05

Hi! I would like to report a long lasting problem with an application, which renders its main window incorrectly in wine. The app is "iRiver caption editor" and it can be freely downloaded at http://www.iriveramerica.com/download/ce.zip . Installation of the program is easy and proceeds and the program itself runs well, but its window looks like a total mess. For a snapshot, look at http://www.sinus.cz/~patrol/ircape.png . I think it's not necessary to write more, what's wrong, simply the widgets are misplaced, incorrectly sized, the window has scrollbars, which it IMHO shouldn't have etc. The window is not resizable. It's the only app known to me which exhibits such a behaviour. I don't have a possibility to test it on a real windoze system, I don't have it. I'm about to file a bug for it, but I'm asking first here to verify that it's not an easily resolvable problem with my setup etc., and also whether a similar (or the same) behaviour isn't already registered. With regards, Pavel Troller

3 2

Re: setupapi: implement SetupGetInfFileListW and SetupGetInfInformationW
by Robert Shearman 17 Nov '05

17 Nov '05

Steven Edwards wrote: >Documented here: > >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/s… >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/s… > >Changelog: >Hervé Poussineau (hpoussin(a)reactos.com) >Implement SetupGetInfFileListW and SetupGetInfInformationW >Inf file parser now accept UNICODE files with FF FE header > > >------------------------------------------------------------------------ > >Index: dlls/setupapi/parser.c >=================================================================== >RCS file: /home/wine/wine/dlls/setupapi/parser.c,v >retrieving revision 1.20 >diff -u -r1.20 parser.c >--- dlls/setupapi/parser.c 12 Sep 2005 22:07:53 -0000 1.20 >+++ dlls/setupapi/parser.c 24 Sep 2005 06:52:23 -0000 > > ... >@@ -951,12 +956,20 @@ > WCHAR *new_buff = HeapAlloc( GetProcessHeap(), 0, size * sizeof(WCHAR) ); > if (new_buff) > { >- DWORD len = MultiByteToWideChar( CP_ACP, 0, buffer, size, new_buff, size ); >+ DWORD len = MultiByteToWideChar( CP_ACP, 0, buffer, size, new_buff, >+ size * sizeof(WCHAR) ); > err = parse_buffer( file, new_buff, new_buff + len, error_line ); > HeapFree( GetProcessHeap(), 0, new_buff ); > } > } >- else err = parse_buffer( file, buffer, (WCHAR *)((char *)buffer + size), error_line ); >+ else >+ { >+ WCHAR *new_buff = (WCHAR *)buffer; >+ /* Some UNICODE files may start with the UNICODE marker */ >+ if (*new_buff == 0xfeff) >+ new_buff++; >+ err = parse_buffer( file, new_buff, (WCHAR *)((char *)new_buff + size), error_line ); >+ } > > Any time a Zero-Width Non-breaking Space is specifically skipped like this it is a bug. You should *never* have to do this if you use the right functions (isspaceW, etc). Is there some other bug lurking that made this change necessary? -- Rob Shearman

2 4

Half-Life 2 / Counter-Strike: Source under Wine
by James Liggett 31 Oct '05

31 Oct '05

Hi, Out of curiosity, has anyone successfully been able to play HL2 or CS:S under wine? Today I finally worked out the kinks getting the original HL to work, and I know some people have been playing around with this stuff. Currently, HL2 and CS:S freeze over on startup. Has anyone even gotten it to start or even play? James Liggett

9 24

Re: listview: infoPtr might be invalid after WM_NOTIFY
by Robert Shearman 18 Oct '05

18 Oct '05

Michael Jung wrote: >Hello Alexandre, Dimi and Phil, > >This is a patch for the infoPtr problem in comctl32's listview.c. I guess it >matches your suggestion on IRC? I've only changed the minimum necessary to >get rid of the file dialog crash. If that's the correct approach in your >opinion, I will continue to work on this. I will be on vacation for three >weeks, though, starting from Friday. > >Dimi, if you think this is ugly, or if you are working on a better solution, >please do protest. > >Changelog: > infoPtr might be invalid after a WM_NOTIFY message was sent, since the >application might have destroyed the listview. Pass around hwnd instead and >call GetWindowLongPtr, if we have to access the listview instance data. >Spotted by Phil Krylov. > > Since this was a behaviour in our file open dialog, did we even verify that this was a listview bug or is it that destroying the listview in the middle of a notification is something that you shouldn't do? If the latter, then one could easily modify the file dialog to post a message to itself to destroy the listview after the listview has finished processing the message that caused the notification. -- Rob Shearman

4 3

Release plans
by Alexandre Julliard 11 Oct '05

11 Oct '05

Folks, I just released 20050930, this should be considered the pre-0.9 release, so please give it some good testing. In particular, please test the things that new users will encounter first, like the automatic .wine creation and winecfg. Even if you normally build from source, please for once try the binary package for your distro and check if you spot anything the packager is doing wrong. Bugzilla has had a good cleanup lately (thanks guys!) and most of the irrelevant bugs have been closed, so please have a look at the remaining ones to see if there's anything you know how to fix. We also still need many documentation updates, so please consider helping with that. If you have scripts that handle releases, now is the time to ensure they can cope with a version number not in the YYYYMMDD format... If all goes well, and if the documentation is updated by then, the real 0.9 should be released in a couple of weeks. In the meantime we should consider ourselves in a code freeze, so please don't submit new features or large changes, only small bug fixes will be allowed in. Thanks everybody for your help, it has been a long trip but we are getting there... -- Alexandre Julliard julliard(a)winehq.org

15 27

DosDefineDevice breaking mapping to unix folders
by Christian Costa 09 Oct '05

09 Oct '05

Hi, It seems there is something wrong with DosDefineDevice. If we consider a drive declared as F: -> /mnt/win_e Remapping the drive F: to G: with this function leads to F: -> G: with G: non defined. This makes, in my case, my app to break all my drives assignement. It's seems the code lacks a level of inderection as shown below: Logical drive -> Real drive -> unix dir Any idea? Bye, Christian

2 5

Office97 Install issue
by Steven Edwards 09 Oct '05

09 Oct '05

Hi, As some of you might know I really would like to see Office 97 be able to at least install and parts of it sort of work on Wine 1.0. One of the things I hope to contribute to the 1.0 effort is fixing this. I'm wondering if anyone could give me a pointer or two as to the problem. There are two issues with Winehq that prevent Office 97 from installing and I need help with issue #2 if anyone has ideas. 1. Wine needs to have the "PROCESSOR_ARCHITECTURE"="x86" string in the Key in HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Environment On CrossOver we are hard setting this (and we install in a Win98 bottle so it does not really matter) but for Winehq we need to properly detect and report the CPU due to Winehq default mode being Win2k. I'll try to make 30mins or so in the next couple of weeks to submit a patch that does this as I think I know where it needs to be implemented. 2. Wine is not properly handling some of the default values in key HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Environment If you notice from the diff CrossOver uses "%SystemRoot% where the default Wine system.reg had the values hard coded. My wifes Win2k box has these values set with "%SystemRoot% also. Is there a reason that Winehq is setup this way? Should they strings in the wine.inf just be changed for those values? With the default Winehq registry you get a message box error that says something along the lines of "This setup program is not supported under your version of Windows" -[System\\CurrentControlSet\\Control\\Session Manager\\Environment] 1126302066 -"ComSpec"="c:\\windows\\system32\\wcmd.exe" -"PATH"="c:\\windows\\system32;c:\\windows" -"ProgramFiles"="c:\\Program Files" -"SYSTEMROOT"="c:\\windows" -"TEMP"="c:\\windows\\temp" -"TMP"="c:\\windows\\temp" -"USERPROFILE"="c:\\windows\\profiles\\sedwards" -"windir"="c:\\windows" -"winsysdir"="c:\\windows\\system32" +[System\\CurrentControlSet\\Control\\Session Manager\\Environment] 1126301456 +"ComSpec"=str(2):"%SystemRoot%\\System\\wcmd.exe" +"PATH"=str(2):"%SystemRoot%;%SystemRoot%\\System" +"PROCESSOR_ARCHITECTURE"="x86" +"SystemDrive"="C:" +"SystemRoot"="C:\\Windows" +"TEMP"=str(2):"%SystemRoot%\\Temp" +"TMP"=str(2):"%SystemRoot%\\Temp" +"USERPROFILE"="C:\\windows\\profiles\\sedwards" +"windir"=str(2):"%SystemRoot%" +"winsysdir"=str(2):"%SystemRoot%\\System" So if anyone has any ideas I would appreciate feedback. Thanks Steven

2 4

Jump to page:

2025

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 September 2005