wine-devel October 2001

wine-devel@winehq.org

71 participants
173 discussions

Re: Make serial fd blocking mode depend on FILE_FLAG_OVERLAPPED
by Mike McCormack 08 Oct '01

08 Oct '01

Hi Eric, Probably a bit of overzealous use of occam's razor. It was being set to zero on the client side, and passed into the server. I wasn't quite sure what to do with it ... so i removed it. There's no harm in leaving it there i guess... Mike >hi Mike, > >I don't understand why you got read of the inherit flag in the protocol >definition for serial handles. Even, if security attribute isn't pass >around yet for file/comm port creation, it should be kept for comm port > >A+ >-- >--------------- >Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) >"The future will be better tomorrow", Vice President Dan Quayle ------------------------------------------ mailto:Mike_McCormack@start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

1 0

Re: Make serial fd blocking mode depend on FILE_FLAG_OVERLAPPED
by eric pouech 08 Oct '01

08 Oct '01

Mike McCormack wrote: > > This patch causes a serial port's fd to be put into blocking mode if > FILE_FLAG_OVERLAPPED is not specified and non-blocking mode if it is. > > ReadFile should block on serial ports for non-overlapped reads. The > next step is to refuse overlapped reads and writes if the file isn't > opened with FILE_FLAG_OVERLAPPED specified. hi Mike, I don't understand why you got read of the inherit flag in the protocol definition for serial handles. Even, if security attribute isn't pass around yet for file/comm port creation, it should be kept for comm port A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

1 0

Re: err:edit:EDIT_LockBuffer no buffer ... please report
by lawson_whitney＠juno.com 08 Oct '01

08 Oct '01

On Sun, 7 Oct 2001 whit(a)giftie.alien.org wrote: > Well, ... yes. The err: goes away. File and directory names still > disappear from the winhelp file dialog (?) as they did before, but > still, if you select the right empty space, the operation proceeds to a > satisfying crash. If I thought that little err: was all that was wrong > with winhelp, that was silly of me. I _think_ this is a good patch. > > Regards, > > Lawson > ---cut here--- So as not to damn you with faint praise, I think winhelp is more nearly usable with this patch than without. I can actually select and see a topic in terminal.hlp before winhelp crashes. Lawson ---slowly, but with considerable uncertainty--- ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/.

1 0

err:edit:EDIT_LockBuffer no buffer ... please report
by lawson_whitney＠juno.com 08 Oct '01

08 Oct '01

Good day! Okay, I reported it, attached is an unexpurgated --debugmsg +edit trace of me trying to open the lcc-win/lccpub/bin/wedit.hlp file from ftp://ftp.mathematik.tu-darmstadt.de/pub/linux/bonnes/lcc-bin-alpha.tar.gz with wine's builtin winhelp program. Current cvs, no windows, no fat nor nt filesystems. Kernel 2.4.10 with devfs and devfsd. [DllOverrides] "*" = "builtin, so, native" I would be happy to make other traces, but probably this is easy to duplicate. Just to add insult to injury, I will attach a backtrace of winhelp trying to work with terminal.hlp (from wfw 3.11, I think). In case anyone is really short on things to debug. Regards, Lawson

2 2

Re: SetSystemMetrics
by Alexandre Julliard 07 Oct '01

07 Oct '01

Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > Files sysmetrics.c, sysmetrics.h: > Implementation of SetSystemMetrics function which sets data accessed by > GetSystemMetrics. Applied, but I renamed it to SYSMETRICS_Set. Internal functions should not be named the same way as exported APIs, otherwise people reading the code will think this is a standard Windows function. -- Alexandre Julliard julliard(a)winehq.com

2 1

dosmem
by Nog 05 Oct '01

05 Oct '01

In my quest to get helppc running and working in wine, I noticed that it tries to access the text mode buffer directly (b000, I think). This memory doesn't seem to be emulated in dosmem.c and my exploration into how to implement it were in vein. Could anybody please help? Anyway on another note, to get the program to exectute this far I had to add a hack to vga.c. What the program was doing, was, it waited until the light pen trigger was set, when it read the light pen trigger set (bit 1) from the vga status register (3da) and then it would wait until it was unset again. I've attached a patch to solve this problem, but its definatly not the right way of doing it, anyway see what you think. Index: vga.c =================================================================== RCS file: /home/wine/wine/msdos/vga.c,v retrieving revision 1.7 diff -u -r1.7 vga.c --- vga.c 2001/06/19 18:14:08 1.7 +++ vga.c 2001/10/04 17:54:02 @@ -31,6 +31,8 @@ typedef HWND WINAPI (*CreateWindowExAProc)(DWORD,LPCSTR,LPCSTR,DWORD,INT,INT, INT,INT,HWND,HMENU,HINSTANCE,LPVOID); static CreateWindowExAProc pCreateWindowExA; +int pentrigger = 0; + static void VGA_DeinstallTimer(void) { if (poll_timer) { @@ -333,6 +335,15 @@ we need to fake the occurrence of the vertical refresh */ ret=vga_refresh?0x00:0x08; vga_refresh=0; + + /* The light pen trigger is a bit tricky, programs want it set first + and then they wait until its unset agian */ + if(pentrigger == 1) { + pentrigger = 0; + ret += 0x5; + } + else + pentrigger = 1; break; default: ret=0xff;

3 4

OLE File Format Documentation
by Charles Wyble 05 Oct '01

05 Oct '01

Hello Everyone. My name is Charles Wyble, and I am working on an open-source library for reading/writing ole files. I want to get all the documentation/source code I can. So far, I have gotten things from: 1)John E. Adams(provided an ole-dump utility) 2)Martin Schwartz's document 3)libole2 4)The Filters Project I was wondering if the wine developers, have any source documentation to share? Also which modules contain the ole source code in CVS? If you are interested in the items I have gathered, I can post them to the list or an FTP/WEB site. ===== Charles Wyble God Bless jackshck(a)yahoo.com __________________________________________________ Do You Yahoo!? NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1

2 1

CVS, diffs, and a newbie (me)
by Daniel Sabo 04 Oct '01

04 Oct '01

What is the proper way to submit a patch to wine? Do you need a special password to use cvs commit or can you only mail in diffs? How do you make a propper diff (yeah, I'm really new at this)? If someone could just add the needed 'fi' to the end of tools/winelauncher.in I'd be happy too :).

2 1

Re:CVS, diffs, and a newbie (me)
by Eric Pouech 04 Oct '01

04 Oct '01

well there should be some info on www.winehq.com (development or tools part). basically, patches are generated with cvs diff -u and sent to wine-patches(a)winehq.com the project leader takes care of putting them into cvs A+ > What is the proper way to submit a patch to wine? Do you need a > special password to use cvs commit or can you only mail in diffs? > How do you make a propper diff (yeah, I'm really new at this)? > > If someone could just add the needed 'fi' to the end of tools/winelauncher.in > I'd be happy too :). > > > > --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) The future will be better tomorrow, Vice President Dan Quayle __________________________________________________________ Faites un voeu et puis Voila ! www.voila.fr Pendant tout l'été, gagnez une Ford Ka sur Voila Gratter ! http://cybergrattage.voila.fr/voila

1 0

Re: typelib patch 2
by Marcus Meissner 04 Oct '01

04 Oct '01

On Wed, Oct 03, 2001 at 04:35:14PM +0200, Ove Kaaven wrote: > As far as I can tell, the DISPATCH_METHOD flag shouldn't be masked out > in here... (Marcus, was there a reason for this?) No, I was just confused by the bad enum and lack of documentation mostly ;) Ciao, Marcus

1 0

Jump to page:

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 October 2001