This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: no valid address (Windows 95)
- To: cygwin-xfree at cygwin dot com
- Subject: Re: no valid address (Windows 95)
- From: "Tim Koenig" <grey_hat at lycos dot com>
- Date: Wed, 26 Sep 2001 23:03:06 +0100
- Cc: m dot plowman at hexapole dot com
- Organization: Lycos Mail (http://mail.lycos.com:80)
- Reply-To: grey_hat at lycos dot com
>I debugged the code and it seems that the interpretation of the registry keys
>is wrong.
It certainly is - that's what I've found out over the last two hours. ;-)
[patch snipped]
Thanks! Great work! But I've also been busy and figured out a work-around
(I wrote this earlier, so details are most certainly not correct):
------ snip ------
As it turns out, Cygwin is unable to get your local interface address under Windows 95, if the number of the interface in HKEY_LOCAL_MACHINE\\Enum\\Network\\MSTCP (which is, if there is only one, 0000) differs from the entry of the key "Driver", whose contents are
"NetTrans\000X". Here, X was 2, a possible cause might be past changes of the local IP-address).
After I changed the key's contents to "NetTrans\0000" (and the name of the key it references, which is now HKLM\\System\\Services\\Class\\NetTrans\\0000) it worked.
(Editing the registry by hand is a sure way to force a reinstallation of Windows! You have been warned!)
------ snip ------
Another thing to be noted is that the way to obtain the interface address
that's being used under Windows 98 (which I consider to be a much "cleaner" approach) should possible under Windows 95 with IE4+ (^= WinInet.DLL), too.
- Tim
Make a difference, help support the relief efforts in the U.S.
http://clubs.lycos.com/live/events/september11.asp