My new ISP (TelkomNet) was advertised as an instant ISP. This also means
that all you have to do is just dial-in, and your computer will be auto-configured.
They *do* have BOOTP server, but it's not configured properly. When I asked
about this to the local customer support, they told me that the auto-config
worked just fine for everyone else -- I'm the first who complaining. Indeed,
Win95 winsock was auto-configured properly!
Turns out that they use DHCP to transmit the netinfo! Gee, so that's why Or
asked about DOS DHCP to this list some time ago! <G>. Finally I'm emailed
their cs centre, and been told that they will fix their BOOTP setup -- problem
solved.
I'm just wondering, while my ISP was generous enough to provide a properly
configured BOOTP server, what about another ISPs? DHCP is a newer
protocol, so it's quite logical that sooner or later it will become the ultimate
choice; while BOOTP either not supported or not properly configured. So, why
not adapting our DOS internet apps to accept DHCP?
Most likely the modification will be somewhere around the existing BOOTP
code (see RFC 951 for BOOTP spec). For those who interested, detailed
specs about DHCP could be found in RFC 1533, 1534, 1541, and 1542.
--Eko
-= We are Microsoft. Resistance is futile. You will be assimilated. =-
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
