wine-devel

wine-devel@winehq.org

9 participants
84458 discussions

printing with wine
by Ricahrd Canada 07 Aug '01

07 Aug '01

Does anybody have complete instructions on how to set up a printer to use in wine? I have tried all of the suggestions with add entries to the wine.conf file, using the internal driver, etc. I cannot seem to get wine to see any printers. I use lprng through a print server, so I do not have any local printers attached. Can anyone help?? Richard

1 0

printing in wine
by richard.canada＠mrlinternational.com 07 Aug '01

07 Aug '01

1 0

AbiWord 0.9 problems even with latest Wine from CVS
by Dan Kegel 07 Aug '01

07 Aug '01

The AbiWord win32 0.9 problems I described recently on wine-users with Codeweavers Preview 4 also happen with the latest Wine built from CVS this afternoon. These problems don't happen when run on Windows, nor when running the native Linux version; they therefore appear to be Wine bugs. Details at http://www.kegel.com/wine/abiword0.9/readme.html I stand ready and willing to apply and test patches, but might not have time to write any fixes myself. Thanks, Dan -- "I have seen the future, and it licks itself clean." -- Bucky Katt

2 4

Re: named critical sections
by Andreas Mohr 07 Aug '01

07 Aug '01

On Tue, Aug 07, 2001 at 04:15:41PM +0200, Andreas Mohr wrote: > Hi all, > > this patch implements *names* for the most important critical sections. > > I simply grew tired of constantly having to look up the crst addresses > in winedbg whenever there was some crst timeout. > Yeah, I know, that patch is slightly weird/dirty, but it's useful. Yup, this patch is weird: > + TRACE("#1\n"); > + TRACE("#2: %p\n", obj); Alexandre, please apply it without this crap ;-) (hmm, I really thought I had properly checked it) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/

1 0

Re: CoGetClassObject
by r.maurizzi＠gvs.it 07 Aug '01

07 Aug '01

[Notes 5.0.8] > The only error message the installer came up with was a dialog saying > "AddFolderIcon" failed. The same here. > I had also understood that there was now a facility to add programs that > would have installed themselves into the Windows startup menu into the KDE > menu structure. I am running KDE 2.2 from CVS if it matters. But nothing > appeared. Had I understood wrong, or do I need to try to do some > debugging? Maybe not for all the InstallShield versions: it worked for me for the game "I-War" (quite old... DirectX 5 I think), with KDE 2.1 Or it could be that the installer crash doesn't help in getting the icon loaded... :-) I didn't had time to look into this feature. Ciao, Roberto.

3 2

CoGetClassObject
by Daniel Walker 07 Aug '01

07 Aug '01

I was thinking of ways to get the CLSCTX_LOCAL_SERVER option working in wine. The only program that uses it , that I know of, is installshield v6 .. I pretty sure some other people are working on this, but I don't know that status. (Anyone care to update me?) There is another problem. It's with the TypeLib information in the IKernel.exe that comes with InstallShield v6. The TypeLib information is encoded somehow, any ideas? I was able to get around that problem because installshield also looks for type information in "ikernel.tlb" . So I was able to create a .tlb that worked. I also used the reaktivate typelib patch so the typelib info gets put into the registry. So the way I understand it is that when CoGetClassObject is called Wine is suppose to , in this case, execute IKernel.exe . Then IKernel.exe will CoRegisterClassObject on all needed objects .. One problem is that the registered class object list isn't shared between the two processes, so we would need to move that list into the wine server (Right?) .. Then we would also need to send an instance of the class object to the Wine server (Yeah??) .. Following that road seems to lead to some messy address translations for DLL's and whatever else.. Since we have complete control over how IKernel.exe is run, how would we get the two processes to share memory? Maybe have IKernel.exe execute in a thread? IKernel.exe doesn't do anything but register it's class objects .. Would it be possible to treat IKernel.exe as a DLL then run CoRegisterClassObject for it? Daniel Walker

8 13

Re: CoGetClassObject
by David.Goodenough＠dga.co.uk 07 Aug '01

07 Aug '01

Curiously (on the subject of InstallSheild) I have just successfully installed the latest (5.0.8) Lotus Notes client on a wine system (latest tarball) and the new Lotus installer is InstallSheild based. It ran perfectly EXCEPT that the program would not terminate. The Lotus installer takes over the whole screen, and that went away, but wine never returned to the command line. As far as I could see there were no messages about locks or anything. The only error message the installer came up with was a dialog saying "AddFolderIcon" failed. I had also understood that there was now a facility to add programs that would have installed themselves into the Windows startup menu into the KDE menu structure. I am running KDE 2.2 from CVS if it matters. But nothing appeared. Had I understood wrong, or do I need to try to do some debugging? Ove Kaaven <ovehk(a)ping.uio.no> on 08/07/2001 07:55:41 AM To: Rein Klazes <rklazes(a)xs4all.nl> cc: wine-devel(a)winehq.com (bcc: David Goodenough/DGA/GB) Subject: Re: CoGetClassObject On Tue, 7 Aug 2001, Rein Klazes wrote: > On Tue, 7 Aug 2001 01:12:34 +0200 (CEST), you wrote: > > > > > > > It couldn't get it from the ikernel.exe because I think > > > it's encoded somehow (unicode, MultiByte??). > > > > It doesn't look encoded, it's just different (it's most likely what is > > boasted as the "Typelib 2 Format"). Win2000's stdole32.tlb also uses this > > new format (it has a "SLTG" signature instead of the old "MSFT"). > > > SLTG is the old format, MSFT came later. Wine can (natively) only read > MSFT. Allright, but the most important question remains: who will volunteer to reverse engineer these SLTG typelibs and make Wine able to read them, so I can concentrate on the actual COM marshaling stuff (which is pretty hard enough as it is), so we can finally get those @#&% InstallShields up?

1 0

Re: ownerdrawn button fix
by Alexandre Julliard 06 Aug '01

06 Aug '01

Aric Stewart <aric(a)codeweavers.com> writes: > A full fix would be to make sure we never call the paint function > directly. However the only time this seems to actually cause a crash is > with owner drawn. This patch corrected the problem with owner drawn so > that we do not have to retest everything with buttons. This seems to defeat the purpose of having the ODA_* constants. Would it also fix your problem to only do the PAINT_BUTTON when the window is visible? -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: (no subject)
by Alexandre Julliard 05 Aug '01

05 Aug '01

Ladislav Sladecek <lsla(a)post.cz> writes: > If you run the binary in the Windows, you will see two properly sized > red rectangles on a white background. If you run the same binary in > Wine, you will see only one large red child but no white parent > background. If either the CS_PARENTDC or WS_CLIPSIBLINGS gets removed > from my example, both Windows and Wine give identical results. Yes, there were a number of problems with the flags handling in GetDCEx. I think the behavior with the current CVS should now be correct in all cases; please give it a try. -- Alexandre Julliard julliard(a)winehq.com

3 3

Just out of interest whats this?
by Robert Laverick 05 Aug '01

05 Aug '01

FIXME:pthread_rwlock_rdlock FIXME:pthread_rwlock_unlock what's this, what's causing it and what needs fixing (I'll give it a look if it's needed) or is it just an old error that dosn't really need fixing (I can run almost everything I want to and the all show this error) just intersted Rob

1 1

Window-position bug?
by davep 04 Aug '01

04 Aug '01

Here's one I haven't seen before. Build the 'winemine' application in the programs directory and start it running. Click on the smiley-face button (which redraws the window). Every time I press the button the entire window moves down the screen one pixel. Dave

1 0

Re: wine/dlls/oleaut32 typelib.c
by Dmitry Timoshkov 04 Aug '01

04 Aug '01

"Alexandre Julliard" <julliard(a)winehq.com> wrote: > Log message: > Malte Starostik <malte(a)kde.org> > Implemented RegisterTypeLib. > > Patch: http://cvs.winehq.com/patch.py?id=99686240431774649117142 + if (res == S_OK && RegCreateKeyExA(key, "FLAGS", 0, NULL, 0, + KEY_WRITE, NULL, &subKey, NULL) == ERROR_SUCCESS) + { + CHAR buf[20]; + /* FIXME: is %u correct? */ + snprintf(buf, strlen(buf), "%u", attr->wLibFlags); ^^^^^^^^^^^ + if (RegSetValueExA(subKey, NULL, 0, REG_SZ, + buf, lstrlenA(buf) + 1) != ERROR_SUCCESS) + res = E_FAIL; + } I'm sorry, it's late a bit. But anyway, instead of strlen() above should be sizeof(). -- Dmitry.

1 0

Re: PATCH: ITypeInfo::Invoke
by Dmitry Timoshkov 04 Aug '01

04 Aug '01

"Marcus Meissner" <marcus(a)jet.franken.de> wrote: > +static void dump_VarType(VARTYPE vt,char *szVarType) { > + /* FIXME : we could have better trace here, depending on the VARTYPE > + * of the variant > + */ > + switch(vt) { > + case VT_UI1: MESSAGE(szVarType, "VT_UI"); break; ^^^^^^^ > + case VT_I2: sprintf(szVarType, "VT_I2"); break; > + case VT_I4: sprintf(szVarType, "VT_I4"); break; Seems to be a typo. Shouldn't it be sprintf instead of MESSAGE? -- Dmitry.

1 0

RE: What is the @ in the function headers
by Patrik Stridvall 03 Aug '01

03 Aug '01

> Quick question. What is the @ in a function header supposed > to contain? > Presumably it is the ordinal in the Dll. Well, functions either has an ordinal or a @. If it has a @ it is means that it doesn't matter what the ordinal is, that winebuild can assign any ordinal it likes for the function. > But what if the > same function has > different ordinals in different copies of the Dll? You mean different versions? Anyway, Wine has no support for it, because none is really needed, because any application that tries to access functions by ordinal that doesn't have a fixed ordinal across DLL version is broken even on Windows.

1 0

What is the @ in the function headers
by Bill Medland 03 Aug '01

03 Aug '01

Quick question. What is the @ in a function header supposed to contain? Presumably it is the ordinal in the Dll. But what if the same function has different ordinals in different copies of the Dll? Bill

1 0

Re: Dont allow SetSelectorBase to change into an kernel region
by Alexandre Julliard 03 Aug '01

03 Aug '01

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > If I only allow to set the selector base when (selector base + selector > limit) is smaller than 0x8000000, the application goes on and lets me read > an eprom plugged into the Galep3 Programmer. Is the appended fix a right > acceptable? No, it's legal to have selectors covering the entire address space. I'm afraid there is no good solution to this kind of problem. What does the app do under NT or with -winver nt40? -- Alexandre Julliard julliard(a)winehq.com

2 1

Some questions about TB_REPLACEBITMAP
by Marco Bizzarri 03 Aug '01

03 Aug '01

Hi all. I'm trying to implement the TB_REPLACEBITMAP message in the comctrl32, and I would like to have some advice about the ImageList structure. The TB_REPLACEBITMAP provides (via the hInst, nID pair) the handle to the old bitmap and the handle to the new bitmap, as well as the number of button in the new bitmap. I think I could use the ImageList_Replace to actually replace the bitmaps. However, the ImageList_Replace function requires a number, which is the first bitmap to be replaced. How can I retrieve this information? For what I can see, once a bitmap has been added to the imagelist, no information about is is stored. I'm doing some tests, using a value (like 0) as the bitmap index, but this is of little help, of course. Any help will be appreciated. Bye Marco

1 0

Some questions about TB_REPLACEBITMAP
by Marco Bizzarri 03 Aug '01

03 Aug '01

1 0

Switching threads in winedbg
by Francois Gouget 03 Aug '01

03 Aug '01

Is it possible to switch threads in winedbg? I can use 'walk thread' to see a list of the threads of my application but I could not find how to get a backtrace of one of these other threads. It's not in the Wine Developper's Guide and I could not find it from the source. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ In a world without fences who needs Gates?

2 1

Dose wine people hate Solaris?
by EriK W 03 Aug '01

03 Aug '01

I have posted my question for compiling Wine in solaris x86 for 2 weeks, seems no anybody even has a bit interest. Do you guys hate solaris? :) I checked almost all the documents and faq, except it mentioned wine works with Solaris, there almost have no other info for it at all. Does anybody has even a suggestion for me? pls don't tell me nuke my solaris. :)

5 8

Re: Documenting functions
by Alexandre Julliard 02 Aug '01

02 Aug '01

"Bill Medland" <medbi01(a)accpac.com> writes: > Ay, there's the rub. It isn't our function. It';s Microsoft's function. > Now was it Holub or McConnell that complains about functions having weird > behaviour on certain inputs. IMO Microsoft functions need less documentation than internal ones, since there is MSDN and other countless books about Windows. You can assume that people reading your code already know what the various APIs are supposed to do. > The biggest problem, I believe, is the functions that take flags. Bear in > mind that a single DWORD argument used for flags is equivalent to up to 32 > boolean arguments. Documenting the relationship between those is a pain > but it needs to be done if we expect compatibility. This is clearly something that is best documented with code, not with text. You may need pages of text to describe the flags behavior in English, while with code it's usually only a few lines, plus a few comments here and there. This doesn't mean it wouldn't be a good thing to also have the full description in English; but in a separate document, not in the code. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Prevent excessive clipping in SysListView32
by Uwe Bonnes 02 Aug '01

02 Aug '01

>>>>> "Medland," == Medland, Bill <Bill.Medland(a)accpac.com> writes: Medland,> I am not very comfortable with this one but strange as it may Medland,> seem it solves the problem. I'd love to know why. Medland,> <<diff13.txt>> Bill Medland (medbi01(a)accpac.com) Prevents Medland,> excessive clipping in SysListView32. Medland,> Medland,>-static inline int perfect_graphics(void) Medland,>+static int perfect_graphics(void) Medland,> { Medland,> static int perfect = -1; Medland,> if (perfect == -1) Medland,> Some C-Expert is requested here, but I suspect that in the old function the variable "perfect" was created in every instantiation of the "perfect_graphics" inlined function. Could you perhaps try to declare the "perfect" outside the inlined function, like static int perfect = -1; static inline int perfect_graphics(void) Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

6 9

Re: Documenting functions
by Alexandre Julliard 02 Aug '01

02 Aug '01

Jeremy White <jwhite(a)codeweavers.com> writes: > I would say that I would rather have 100% of the effort a > particular developer *wants* to put in, rather than only > have his/her coding efforts. Absolutely; I'm not going to discourage anybody from writing doc if they feel like it. But I don't want anyone to feel somehow obliged to spend time on the doc if they'd rather be writing code, which I expect is the case with most developers... > However, I think that there should be a standard function > header, with a standard place to put notes and comments > in general about a function. I don't see a need to standardize anything. If you want to add a comment before a function just do it, there is no need for a standard format, plain text works just as well. > I have been trained, and I suspect that many of us have > been trained, to look at a function header for general > tips and tricks before diving into the code. I know > this is sacriledge to you, Alexandre, but there are some > of us who like to quickly look at a function, rather than > always reading the code to understand it completely. I think you misunderstand my position; I'm not opposed to having a comment at the start of the function explaining the general goal and the non-obvious things going on. But if you need more than a couple of paragraphs to do this, then either there are too many non-obvious things going on in your function, or you are wasting space explaining the obvious. I do strongly think that the goal should be to write code that doesn't require documentation in order to be understood. Of course adding a small amount of comments is a good idea; but when you start having more lines of documentation than lines of code, something is very wrong IMO. But this is mainly a matter of personal taste, and except in extreme cases I'm not going to reject code because it has too much (or not enough) documentation. It may happen that some of your beloved horizontal lines get lost during the cvs commit though ;-) -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Documenting functions
by Jeremy White 02 Aug '01

02 Aug '01

[Resend due to exim crash; thanks Ove] >> I'd much rather have developers spend their time writing code. Making >> them duplicate the whole MSDN documentation would be a huge waste of >> their time. Our resources are not infinite, and it's much more useful >> to have 100% API coverage with no docs at all than 50% coverage and >> tons of docs. I think this is a dangerous attitude to take. I think that you cannot (and should not) attempt to force volunteer developers to add documentation to code. However, there are some few of us, who don't feel that the job is satisfactorily done until the documentation reflects important things that we've learned. I would say that I would rather have 100% of the effort a particular developer *wants* to put in, rather than only have his/her coding efforts. If I, like Bill, spend 24 hours ripping my hair out to learn some oddball things, I want a place to put those things. I want someone else (or an older version of me) to have a chance to not have to learn those things the hard way. Please don't misunderstand me. I agree that we shouldn't try to replicate MSDN. I'm not even sure we should provide minimal documentation like parameter lists and return values. Further, I agree that where it makes sense, the best place for comments is inline with the relevant code. However, I think that there should be a standard function header, with a standard place to put notes and comments in general about a function. I have been trained, and I suspect that many of us have been trained, to look at a function header for general tips and tricks before diving into the code. I know this is sacriledge to you, Alexandre, but there are some of us who like to quickly look at a function, rather than always reading the code to understand it completely. <in joke> Finally, I think all the code would be dramatically improved, in fact, I bet we'd be at Wine 1.0 by now, if there were nice big horizontal separator lines everywhere. </in joke>

1 0

Re: Documenting functions
by Alexandre Julliard 02 Aug '01

02 Aug '01

Francois Gouget <fgouget(a)free.fr> writes: > So I think the functions implemented in Wine should be fully > documented. And the only place to do that is in the code source because > this is the only place where they have a remote chance of staying up to > date (and also where it's most practical to have it). I have to disagree here. Yes it would be nice to have a free Win API documentation, but it definitely doesn't belong inside the Wine source. First it would be a huge bloat in the source; and more importantly the Wine source doesn't define the Windows API, it is defined by Microsoft. > Of course developpers are very well-known for hating to document > stuff so it's going to be pretty hard to get proper documentation. But > we should encourage all Wine developpers to write good documentation for > the functions they implement/fix, not dissuade them to do so. I'd much rather have developers spend their time writing code. Making them duplicate the whole MSDN documentation would be a huge waste of their time. Our resources are not infinite, and it's much more useful to have 100% API coverage with no docs at all than 50% coverage and tons of docs. > Also I agree with you that the strict minimum is to at least document > all the undocumented/weird behaviors. Especially since without some sort > of documentation the next developper may be tempted to remove what looks > like unnecessarily convoluted/obviously wrong code. That should be done with comments inside the code itself. And in many cases it would actually be better to comment the places where the behavior is not right. What I mean is, instead of adding a comment on every line stating "yes this is what Windows does", I'd prefer adding a comment/FIXME to mark the lines that have been written without checking whether Windows really does it this way. -- Alexandre Julliard julliard(a)winehq.com

2 1

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