On Thu, 8 Jan 2004, Eric Becker wrote: > Now I'm a bit confused as to what needs to be setup by my DOS network > client. Originally, I assumed that dosemu would be similar to vmware, > in that I would need to load a dos network driver. But, as you stated, > I won't need to load a network driver.
Essentially a packet driver is built in: int 0x60. The DOS applications must then be configured individually to know what IP they have and if applicable the gateway and name server. Where to do that depends on the app. E.g. for applications that use WATTCP it's wattcp.cfg VMWARE would actually emulate an ethernet device, but DOSEMU emulates something that is higher level, the packet driver. In real mode DOS I would load a packet driver that talks to my ether net card and use that (using int60) in DOS apps likewise. > However, the first set of > instructions for TUN/TAP support instruct the user to "Configure the DOS > network clients to have another IP address within the same domain". I'm > a bit confused as to what will need to be loaded on the dos client in > order for it to network. Nothing loaded, just a config setting. Try NCSA telnet or SSHDOS (sshdos.sf.net) to get the idea. > > Bridging comes in handy if you're talking to the > > outside world > > http://edeca.net/articles/bridging/ > > says how this works in user mode linux (UML). DOSEMU > works likewise. > > So then with the above setup I will only be able to communicate with the > machine I'm running dosemu on? But in order to communicate with the > rest of th 192.168.1.x subnet I will have to bridge tap0 with another > ethernet device (i.e. eth0)? And then the dosghsrv can recieve requests > from the ghost clients to broadcast the ghost images via multicast? AFAIK yes, yes, I don't know. Probably, but I never tried that myself. Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
