[Bug 3002] problems writting to serial ports on 2005-05-24 release

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=3002





------- Additional Comments From dclark at akamail.com  2005-02-06 11:23 -------
The VXD problems with running under Win98 are common, and it is very unlikely
that anyone will attempt to fix this. My understanding is that a fix would
require someone to implement pedrv.vxd, which is unlikely to happen. When run
under WinNT variants, the program does not use the VXD (because the WinNT
variants do not allow it), so that particular problem goes away.

I assume you mean that the program works with:
cvs update -D "2005-01-14 CDT"
and is broken with
cvs update -D "2005-01-15 CDT"

If som then it means one of the CVS commits on the 14th broke the application.
Browsing through the commits on that day doesn't give an obvious candidate. I
don't know where the message "wine client error" comes from. So since you are
now an expert on CVS updates, how about narrowing it down to a particular patch?
I know it is tedious, but you are almost there ;)

The guide to CVS regression testing talks about how to do that, but in brief, go
to the page:
http://www.winehq.org/hypermail/wine-cvs/2005/01/index.html
Those are the CVS commits for January. Go down to the 14th and pick a patch
roughly in the middle. For example, it looks to my like the one with the time
stamp of "Fri Jan 14 2005 - 10:09:34 CST" is roughly in the middle. So I would
execute the command:
cvs update -D "2005-01-15 10:09:00CST"
Since the January patches use the "CST" timezone, be sure to use that when
running CVS or the results will be confusing. You can then shift the time back
and forth to find the exact patch that caused the problem. 



-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.