Hi Felix,

I use fixed IPs so I am not common with the problem you describe. I 
just activated my routers DHCP server and set the appropriate line in 
WATTCP.CFG to

"my_IP = dhcp"

instead of giving it a fixed IP.

If I now start Arachne, the DHCP server assigns an IP to the FreeDOS 
machine and I can browse the web without problem. Other programms 
(like ping in the wattcp collection) seem to require a fixed IP (at 
least it didn't work for me at the moment).

Can't say anything about the installer.

Please keep in mind, that networking is not already built-in in 
FreeDOS (as it is in GNU/Linux) but is provided by other software: 
network drivers, TCP/IP stacks and applications (or applications with 
a built-in stack as the Wattcp programs or Arachne).

Look at http://www.lazybrowndog.net/freedos for more general info 
about (Free)DOS networking. (If anyone is interested, we could 
transfer this site including the pictures into a wiki)

Uli


Felix Miata schrieb:
> This was my 2nd installation ever, but my first in a system with a NIC, and
> the boot messages are perplexing. According to my router, FreeDOS never got a
> DHCP IP assignment from the router. I see among the boot messages on the 
> screen:
> 
> ...
> Multicast setup workaround used for both 10 Mbits and 100 Mbits
> This board supports 100 Mbits
> PHY device 1 - National DP83840 100BASE-TX, C step
> ...
> Negotiated speed 100Mbs (100Base-TX) full duplex
> PHY device 2 - No PHY device installed
> Using twisted pair cable
> ...
> Packet driver software interrupt is 0x60 (96)
> Interrupt number 0xB (11)
> I/O port 0x6800 (26624)
> My Ethernet address is xx:xx:xx:xx:xx:xx
> ...
> 
> When I boot the same system from a Knoppix CD, I get:
> 
> #lspci | grep thern
> 00:0b.0 Ethernet controller: Intel Corp 82557/8/9 [Ethernet Pro 100] (rev 01)
> #ifconfig eth1
> eth1: error fetching interface information: Device not found
> #ifconfig eth0
> eth0  Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
>       inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0
>       ...
> 
> Is there some way to translate the FreeDOS boot messages into the networking
> language Linux uses, and figure out if the FreeDOS installer misconfigured,
> or otherwise why it doesn't seem to acquire an IP address via DHCP? Would it
> be easier to set up FreeDOS to use a fixed IP than to figure it out?
> 
> The non-organization of the FAQ on sourceforge is a real pain on which I've
> yet to find anything directly on point. Googling pages on freedos.org did
> little more than provide a poorly organized mess of links, no onsite page
> that seems to cover networking.
> 
> TIA


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to