-=> Quoting Ben Ritchey to All on 02-14-08  14:48 <=-

Hi, Ben.  Here's my Wizard...  

 BR> I am trying to replace my dial-up scripts/programs with ethernet
 BR> under native MS-DOS 6.22. I have a working packet driver (3c90xpd.Exe)
 BR> for my working nic (nic works great under Win98SE on same box) that
 BR> loads but it does not create the requisite IP-UP.BAT file for the apps
 BR> to use. The nic is connected to a router so the IP address may be fixed
 BR> (?). 

Routers put you on a private network and usually support the Dynamic
Host Configuration Protocol (DHCP) and expect you to use that. They also
support private IP addesses 192.168.0.0 through 192.168.255.255. The
simplest way is the way W9x does it - use DHCP. If you can't DHCP, then
just assign fixed addresses to your computers. Make sure the fixed
addresses are in your local network and unique, and not in the range of
addresses used by the router for DHCP (read the fine manual).

# WATTCP.CFG for Ethernet/Fixed IP - according to my router manual
MY_IP = 192.168.100.10    #an IP not used by the router
NETMASK = 255.255.255.0   #the mask my router expects
GATEWAY = 192.168.100.0   #the address of my router
NAMESERVER = 


For Wattcp make the above permanent .CFG, load the packet driver, and
skip the IP-UP.BAT stuff. Just run the utilities. You don't need to do
dialup or hangup anymore. You can even install the packet driver in
AUTOEXEC.BAT.

 BR> These are all Wattcp apps that I run and depend on the wattcp.cfg
 BR> file which is built dynamically from scripts during the packet driver
 BR> load process (hence the need for IP-UP.BAT). Where do I go from here?
 BR> I cannot see any option or locate a program that will create an
 BR> IP-UP.BAT file with the required variables. Help!

Sometimes fixed addresses are best and sometimes dynamic addresses are
better. In the private network provided by a router, do what works for
the application. Some DOS network stuff *must* have fixed addresses.

WATTCP supports BOOTP and DHCP. You just delete the WATTCP.CFG file and
it does it automatically. If you need some special parameters and can't
remove the file, then remove NETMASK, GATEWAY, and NAMESERVER entries -
DHCP will set these automatically (the router passes them along from
your ISP). So:

# WATTCP.CFG for Ethernet/DHCP
MY_IP = DHCP
HostName = MyPC


(16bit WATTCP has a really bogus hostname "012345678901..." for 50
characters) 

 BR> p.s. if IP addresses (local & remote) are fixed and I therefore need
 BR> a static IP-UP.BAT, where do I obtain the addresses from? The info
 BR> program for the nic gives all the hardware info including mac address,
 BR> but no IP! I can write a program or script to pull the addresses if I
 BR> could just discover them! 

P.S. Some routers don't play well with WATTCP 16bit when it comes to
DHCP (LinkSys for instance). WATTCP 32bit works ok. I modified the 16bit
library for my use (and fixed it) rebuilding PING, TCPINFO, FTP, TNPORT,
and POPSMT. We use a batch file that does Dialup or DSL depending on an
environment variable (our DSL provides both services).
...Ask and ye shall receive...

Me, again... hope this is helpful... :)

ttyl        neb

... When I contemplate the moon, my head aches [Galileo]

___ Blue Wave/QWK v2.20

--- ViaMAIL!/WC v1.60d