Mail Archives: djgpp-workers/2001/02/01/14:44:19
Hello.
Tim Van Holder wrote:
>
> Richard Dawe wrote:
> Can't we use a dynamically loaded custom version of wsock2.vxd (i.e.
> patch a copy of wsock2.vxd, distribute it with libsocket (under a
> different name) and have libsocket dynamically load that vxd (the way it
> does for coda.vxd))? There may be some legal issues, but IIRC patching
> software for purposes of interoperability is protected by fair use, so
> as long as the origin of the patched wsock2.vxd is clearly stated, there
> shouldn't be a problem. Of course, IANAL.
I did consider this. However, I don't think it will work, because both
versions would have the same virtual device driver ID. Background: You can
load VxDs by ID (the old way) or by name (the new way). To get a VxD ID,
you send a mail to Microsoft. Now, one could probably patch the VxD ID
too, but I'm not sure what kind of justification you have to give to
Microsoft. Somehow I don't think they/their lawyers would be very willing
to give out a VxD for this purpose.
> > Tim, you may want to try Watt-32 instead.
[snip]
> No point - CVS currently doesn't work in a SFN environment. I intend to
> fix that someday - but that probably requires extensive work, and I just
> don't have the time (I consider working on autoconf/automake more
> important than adding SFN support to cvs).
What about users who use LFN TSRs? Surely CVS would work OK in those
cases. I've not tried loading an LFN TSR at the same time as a packet
driver, though.
> Indeed it would. <song>Someday, my SFN-enabled CVS(*) will come.</song>
>
> (*) OK, this doesn't rhyme with 'prince'(**). It's not even similar.
> So sue me.
<JOKE>Heh, don't give up your day job to become a
singer/songwriter.</JOKE>
> (**) Those that don't get the reference: never mind. 'tis not important.
A tune by Miles Davis?
Bye, Rich =]
--
Richard Dawe <richdawe AT bigfoot DOT com> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
- Raw text -