From: "Stipe Tolj" <[EMAIL PROTECTED]>
Sent: Monday, February 04, 2002 8:24 AM


> Ben Hyde wrote:
> > 
> > Rodent of Unusual Size wrote:
> >  > There's a FAQ I'm getting more and more to which I don't
> >  > know the answer; to wit, does Apache 1.3.* run on Windows XP?
> >  > What *is* the answer?
> > 
> > "Not known not to work."
> 
> at least our Cygwin 1.3 based port of 1.3.x works on Windows XP. So this
> is something like a "yeno".

Stipe, how many boxes had you tested yet, before you make that assertion?

About one dozen XP users (+ those who haven't checked in with us through
either bugs or c.i.s.w.ms-windows) have a very serious sockets bug that
results in corrupted -script- output (e.g. SHTML, PGP, etc.)  Cygwin now
essentially shares sockets code, so I'd consider your statement suspect.

FirstBill and I have banged our heads together and come up with nothing
useful yet.  Nobody in Bill's or my own work groups can reproduced the bug.
It's probably with a specific transport provider, but which one nobody can
isolate yet.

So, does it work on Cygwin?  About as well as XP - in that there is a buggy
driver out there to bite 'em in the arse.  And no, turning of QoS or other
driver extensions does not clear the bug, and no, you won't see it on any
localhost loopback requests.

The mystery...

nobody [on the very same boxes] with Apache 2.0.28 can reproduce =-/

Bill

Reply via email to