July 2002 - Wine-Devel - list.winehq.org

Re: DTR / DTS vs RTS/CTS vs Wine

by Mike McCormack

Hi Miguel, You are correct; the Linux kernel does not support DTR/DSR flow control. If a windows program requests DTR/DSR flow control in wine, we just write a FIXME to stderr and ignore the setting. Your idea to build a cable that wires the printer's DTR/DSR to the computer's RTS/CTS may work, but you may also need some small hacks in wine to select RTS/CTS flow control when the program asks for DTR/DSR flow control. That won't garantuee that your program works, but it will at least be a little better... I guess the other option is to implement DTR/DSR flow control in the Linux kernel... but that may not be easy :) Mike List vmn wrote: > Hi, > > I am testing a serial printer driver that uses DTR/DTS hardware flow > control on wine. > While testing the driver running winedbg everything worked, not so when > I ran the program directly from wine. > I sent this problem to the printer manufacturer and they put a data > scope on the serial line. > It seems that the DTR/DTS signal was not being caught by the computer > and therefore the computer was sending info > over the serial port when the printer was not ready. > I read on the net that the linux kernel does not implement DTR/DTS > but only RTS/CTS hardware flow control. > > I also read that it is usual for cables to be built that connect the > RTS/CTS pins to the DTR/DTS pins therefore tricking the computer and > printer [the computer understands RTS/CTS and the printer DTR/DTS ] and > getting good results. > > The output of --debugmsg +comm after SetCommState was called was ~IXONN > ~IXOFF. > Can anybody indicate that If I build the correct cable and ask for > RTS/CTS with SetCommState , that the serial io will work? > Any limitation of wine with RTS/CTS? > > Is it correct that windows does not do ANY hardware flow control? > If so, how can this app work under windows since it only uses standard > SetCommState, ReadFile, WriteFile calls... > > Thanks, > Miguel Feitosa > >

July 24, 2002

Re: Re : Coded breakpoints

by P. Christeas

> Never mind, if WAS a stupid question :-) > For who needs it too, just add > > __asm__("int $0x03\n\t") ; > > at the required point, maybe inside an huge if(....) > > Regards > > Max Just one objection: it is bad programming style to use assembly inside C. There are so many C functions and macro definitions, that wrap almost any processor instruction (I recently came accross the 3Dnow fn's). They are much better, because they will refuse to compile if sth goes wrong. Say: #define DBG_BREAK { MY_WARN("I'm brreaking here..."); \ __asm__("int $0x03\n\t"); } end later use: DBG_BREAK whenever you want. In addition you 'll be able to #define DBG_BREAK { /* these brackets won't break conditionals */ } to disable the breakpoint feature..

July 24, 2002

DTR / DTS vs RTS/CTS vs Wine

by List vmn

Hi, I am testing a serial printer driver that uses DTR/DTS hardware flow control on wine. While testing the driver running winedbg everything worked, not so when I ran the program directly from wine. I sent this problem to the printer manufacturer and they put a data scope on the serial line. It seems that the DTR/DTS signal was not being caught by the computer and therefore the computer was sending info over the serial port when the printer was not ready. I read on the net that the linux kernel does not implement DTR/DTS but only RTS/CTS hardware flow control. I also read that it is usual for cables to be built that connect the RTS/CTS pins to the DTR/DTS pins therefore tricking the computer and printer [the computer understands RTS/CTS and the printer DTR/DTS ] and getting good results. The output of --debugmsg +comm after SetCommState was called was ~IXONN ~IXOFF. Can anybody indicate that If I build the correct cable and ask for RTS/CTS with SetCommState , that the serial io will work? Any limitation of wine with RTS/CTS? Is it correct that windows does not do ANY hardware flow control? If so, how can this app work under windows since it only uses standard SetCommState, ReadFile, WriteFile calls... Thanks, Miguel Feitosa

July 24, 2002

Calling a winelib program (wcmd) from inside wine with arguments

by Uwe Bonnes

Hallo, how do I call a winelib programm with arguments from inside wine. I tried several appoaches in a first hack for Batch file support in wine, but I didn't succeed. It seemed that either the winelib programm insisted on the "--" divider or it tried to interpret it. Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

July 24, 2002

Re: Dinput - Keyb Bug

by Kristoffer Ericson

Greetings, I've been working with this problem for about 2 weeks now (play alot of tribes) and it's finally working with keyboard. I tried dinput about a week ago but couldn't make it work but as you said i should have used directx5 or 6 instead. Keyboard works fine but i still have other issues, to make the game fully functional. Dsound komplains somewhat and the sound sounds pitched (plays to fast, thus giving the smurf syndrom), i tried to use -dll dsound.dll but it says that it can't find the file. I know i've done right so i checked around on irc.openprojects.net and they said that not all -dll's can be used natively, is this right? Also i fail to get opengl to work, i simply can't select it in game. Any ideas? I've compiled with --enable-opengl and i've run a testprogram using opengl which works fine. Tribes running in fullscreen mode it feels slow and strange, but running it in window mode makes it feel fast and stable. Why? i tried to use native ddraw.dll but then the game won't even start, there's just a black screen. Thank you for all your support, considering i've been running around looking at homepages and chatting on irc when you all solved my problem within 1 day, THANKS(!). Other than that Tribes works fine. >From: Steven Edwards <steven_ed4153(a)yahoo.com> >To: Kristoffer Ericson <kristoffer_e1(a)hotmail.com>, wine-devel(a)winehq.com >Subject: Re: Dinput - Keyb Bug >Date: Tue, 23 Jul 2002 15:11:53 -0700 (PDT) > >You need to use the windows dinput.dll as ours is (still) not up to spec. I >used to play this game >all the time under linux till tribes2. I dont know if this will work with >the directx 8.1 but if >you can find a dinput.dll from dx5 or 6 it should work. > >I will add this information to the wine application database if its not >already there and if >someone working on directx can figure out what is going on that would rock >long term. > >Thanks >Steven > > >--- Kristoffer Ericson <kristoffer_e1(a)hotmail.com> wrote: > > I'm trying to get StarSiege Tribes (1) to work, and from what i gather >is it > > suffering from a quite common wine-gaming-problem (both wine & winex). > > > > The game starts smoothly enough but keyboard is dead. When i press any >key > > it will instantly drop out and quit. No error message or breaks. > > Considering the keyboard makes you move it basicly leaves you jumping up >and > > down shooting at everything that comes..=) Other than the keyboard error > > tribes runs fine. > > > > I daily run updates from winex & wine but been working at this problem >for > > about 2 weeks. > > > > I've read all the info i could find on the subject and from what i can > > gather is that tribes used to work on older wine. So can anyone give me >some > > futher info about where i could find older wine-archives or if the >dinput (i > > guess the problem is due to dinput) problem is about to be solvedŽ, >tweaks, > > patches, ideas.. > > > > With respect Ken > > > > > > > > _________________________________________________________________ > > Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > > > > >__________________________________________________ >Do You Yahoo!? >Yahoo! Health - Feel better, live better >http://health.yahoo.com _________________________________________________________________ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com

July 24, 2002

Re: cleanup patch

by Andreas Mohr

On Wed, Jul 24, 2002 at 12:03:17PM -0700, Alexandre Julliard wrote: > Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> writes: > > > - dlls/kernel/format_msg.c: use debugstr_a > > lpSource is not necessarily a string. Hmm, ok. > > > - include/wingdi.h: add offsets to LOGFONTA struct > > That would probably be more useful with correct offsets <g> Arghouch ! ;-) OK, I guess that morally forces me to resubmit it ASAP ;) -- Microsoft Licensing 6.0: "Pay us now in advance, so that we can own you later."

July 24, 2002

Re: wine/dlls/shell32 shellord.c shlexec.c

by Alexandre Julliard

Duane Clark <dclark(a)akamail.com> writes: > Ouch, that version had some serious bugs. It would be much better to > apply the version I posted to wine-devel, which I think works pretty > good. Oops sorry, that was the one I intended to apply, I didn't notice it was only sent to wine-devel. > I can supply a diff between this version and the fixed one, if > desired. Yes please. -- Alexandre Julliard julliard(a)winehq.com

July 24, 2002

Re: wine/dlls/shell32 shellord.c shlexec.c

by Duane Clark

Alexandre Julliard wrote: > ChangeSet ID: 1027537179446510804425092 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 02/07/24 13:59:39 > > Modified files: > dlls/shell32 : shellord.c shlexec.c > > Log message: > Duane Clark <dclark(a)akamail.com> > Combined implementations of ShellExecute/Ex. > > Patch: http://cvs.winehq.com/patch.py?id=1027537179446510804425092 > > Revision Changes Path > 1.100 +0 -186 wine/dlls/shell32/shellord.c > 1.4 +326 -111 wine/dlls/shell32/shlexec.c Ouch, that version had some serious bugs. It would be much better to apply the version I posted to wine-devel, which I think works pretty good. I can supply a diff between this version and the fixed one, if desired.

July 24, 2002

Re: cleanup patch

by Alexandre Julliard

Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> writes: > - dlls/kernel/format_msg.c: use debugstr_a lpSource is not necessarily a string. > - include/wingdi.h: add offsets to LOGFONTA struct That would probably be more useful with correct offsets <g> -- Alexandre Julliard julliard(a)winehq.com

July 24, 2002

Re: 10072002 version - printing bug

by Huw D M Davies

On Wed, Jul 24, 2002 at 05:33:54PM +0800, leanne wrote: > Dear all, > > I found the 10072002 version of WINE that the layout of printout got > problems. > some letters overlap. This is probably a bug in the Type 42 font download code. Could you try editting your ppd file (by default generic.ppd) and chaging the line *TTRasterizer: Type42 to *TTRasterizer: None this will get Wine to download the fonts as Type 1 outlines instead. Let me know if it makes a difference. Huw.

July 24, 2002