Re: XEmbed Systray Support
Robert Shearman wrote: Hi, This patch allows new non-KDE systems to display notification area icons for Win32 apps in the window manager's system tray, instead of in a 16x16 top-level window. Changelog: Support XEmbed protocol for system tray windows. Sorry, I forgot to credit Mike Hearn in the changelog. It should be as follows: Robert Shearman [EMAIL PROTECTED] Mike Hearn [EMAIL PROTECTED] Support XEmbed protocol for system tray windows. Thanks, Rob
HKCU\Software created as volatile?
I've met this kind of errors so many times with fresh installs that I finally took a look at what was going on; err:winecfg:set_config_key Unable to set configuration key Audio in section Drivers, res=1021 This error occurs because HKCU\Software is created with REG_OPTION_VOLATILE, thus making it impossible to create non-volatile keys under HKCU\Software. This breaks about every app that's trying to create keys under Software - like winecfg. This is because SystemParametersInfoW in dlls/user/sysparams.c creates the HKCU\Software\Wine\Temporary System Parameters key with REG_OPTION_VOLATILE - and if you do not have HKCU\Software\Wine already available, they are crated as volatile also. ( see get_volatile_regkey() ) You can test this simply by (if you have a fresh install, you can go directly to 4.); 1. Opening regedit 2. Delete HKCU\Software (or HKCU\Software\Wine only) 3. Close regedit 4. Open regedit 5. Try to create a new key under HKCU\Software (or HKCU\Software\Wine, if you removed only that) 6. You'll get error message Subkey must be volatile Any comments? ( This could be fixed in sysparams.c - already got a patch ready for it, but probably it's better to ensure in wineserver that the Software\Wine exists or something, so that this bug does not pop up again later? )
documentation out of date.
I am trying to update from 20050524 to wine-20050830. The newer version tells me to use winecfg not the old config file , so I thought I should read up on it. bash-3.00#man winecfg No manual entry for winecfg So I tried man wine but no mention of winecfg , it still refers to the config file. It also lists a reference in the last line to a man entry for wineserver. So I decided to get upto date on wineserver... bash-3.00#man wineserver No manual entry for wineserver Wine is a very complex program, it would be helpful if the man entries were self-consistent and updated with the release they install with, especially when important changes like the introduction of wineconfig are concerned. So where do I look for info on winecfg? In short, does .wine/config still get read or is it dead? Also winecfg About tells me version is wine CVS , wine command tells me 20050830. I am trying to maintain an app in the appDB but this is difficult without consistent doc. TIA for any input.
Re: [Now ns7] Dragon ns8 problem
On Mon, 12 Sep 2005 13:14:44 +0200, Jean Magnan de Bornier [EMAIL PROTECTED] wrote: OK, I added rpcrt4.dll in c/windows/system, and now dns starts all right, although slowly and with strange messages, and WORKS! Hmm, I found it is very slow to open on more recent wine versions : ie after 20050524 but was getting crashes as soon as I tried to open dragonpad. This is regression, it used to work. Could you post which (all) dlls you have had to run native to get this working? Did you have to install IE6 first or not. (I cheated but it worked) I have not figured out I could save the output that is written on the dragon editor; if I try to save in a file dns crashes, if I try to save to clipboard (C-c) and then open it in e.g. emacs, I have nothing. Any ideas? Thanks, To copy text dictated into DragonPad I simply highlight it with the mouse. Standard X behaviour will copy this to the clipboard without any other clicking or hotkeys. Then I paste where I want it . Again, the std 3rd mouse button click will paste most places in X , but in Opera email I find I have to use Cntl-V to paste since the mouse-3-click seems to paste another buffer. I love this - highlight to copy; one click to paste - in X , it is so much more efficient than all the context menu stuff in Win. I seem to recall the Edit menu in dragonpad worked as expected as well. Cant advice on emacs behaviour. HTH
found it! the dce porting header file
http://examples.oreilly.de/english_examples/dce/dce_nt/dceport.h.aug95 o joy o joy. also, i found _this_!!! http://sourceware.org/pthreads-win32/ which is an implementation of pthreads on win32. _also_ i found - was reminded - by judicious searching on google, that of course entegrity.com have PC-DCE which is of course a _commercial_ product that has done exactly the work required: making dce (1.1? 1.2.2?) compile on Win32. including exceptions, dealing with mapping the names, blah blahhh. now. anyone got any brainy ideas on how to reverse dceport.h - in particular the thingy. wotsit. TRY/FINALLY/CATCH stuff? what i'm going to try to do is take a shot at simply compiling dcethreads - on win32. if that _works_ (the tests pass) it'll be great - it will prove two things: 1) that pthreads-win32 works 2) that the dce exception handling will fly, on win32, and _that_ means pretty much zero (urk! let's hope!) work. for now. my main goal: GetItWorking(tm). i couldn't care less about binary compatibility for now: i want services - i want srvsvcd, i want winregd, i want lsarpcd, i want samrd - all compiled, all working, using TCP/IP. i can then work on rewriting freedce's ntlmsspauth.so to be a DLL (starting off as my favourite - a stub with username and password of test). i can then work on writing an ncalrpc plugin transport (which is very straightforward: a matter of filling in about 25 functions in a vector table). and also on a ncacn_np plugin transport. working means that other people will then be able to focus on issues like binary compatibility. guys (wine team) i have to say this. you were utterly insane to not use freedce as your starting point - and i am still bewildered by you not even looking at its source code (which is topologically identical in almost all areas, to what you've created) or the opengroup's documentation. i say that with the greatest of respect for what you've achieved without freedce. l. -- -- a href=http://lkcl.net;http://lkcl.net/a --
Re: found it! the dce porting header file
Luke Kenneth Casson Leighton wrote: guys (wine team) i have to say this. you were utterly insane to not use freedce as your starting point I heard some ros guys want to implement smb from scratch without even looking at samba, it must be some mental disease that all people reimplementing windows get ;-) Ivan.
comctl32.dll: Running siap and modules under wine, first steps
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, /\/\ /\ `/
comctl32.dll: Running siap and modules under wine, first steps
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, /\/\ /\ `/ -- Saludos, /\/\ /\ `/
Re: comctl32.dll: Running siap and modules under wine, first steps
Maximiliano Curia wrote: ... 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? Start the program with WINEDEBUG=+treeview wine program.exe treeview.log and send the treeview log to the list (compressed if it is over 50kB). Is there some documentation of how to implement a certain Windows widget in wine? Not really. My guess is that either some message is failing because it is hitting some border case. Is anybody working in this dll, or has worked on this widget? I have worked on the control, but I don't really have time to look at the specific problem, other than giving a 5 minute look over any log files you send. -- Rob Shearman
Re: HKCU\Software created as volatile?
Kimmo Myllyvirta [EMAIL PROTECTED] wrote: I've met this kind of errors so many times with fresh installs that I finally took a look at what was going on; err:winecfg:set_config_key Unable to set configuration key Audio in section Drivers, res=1021 This error occurs because HKCU\Software is created with REG_OPTION_VOLATILE, thus making it impossible to create non-volatile keys under HKCU\Software. This breaks about every app that's trying to create keys under Software - like winecfg. This is because SystemParametersInfoW in dlls/user/sysparams.c creates the HKCU\Software\Wine\Temporary System Parameters key with REG_OPTION_VOLATILE - and if you do not have HKCU\Software\Wine already available, they are crated as volatile also. Please send a patch which fixes SystemParametersInfoW to wine-patches. -- Dmitry.
