• Please review our updated Terms and Rules here

Looking for a file for GEOS - EtherPKT.Geo

gepooljr

Experienced Member
Joined
Dec 8, 2012
Messages
161
Location
Las Vegas NV
I'm installing Breadbox 4.13 on my 486/133 and need EtherPKT.GEO to link to my DOS Packet Driver. I check other forums and couldn't find the file. Its listed a EtherPKT.zip. Does anyone have this to send to me?

Geoff
 
Hello again keenerb. Is there any specific entries in the geos.ini that need to be made? And does the *.geo file go into the system folder or another?

Thanks in advance.

Mark.
 
I've been successfully using ETHERPKT.GEO with a NewDeal Office 3.2a setup for the past day-or-so, per an adaptation of this configuration.

Here is a generalized procedure:

1. Place ETHERPKT.GEO in the \SYSTEM\SOCKET subdirectory of your NDO installation.​

2. Load the packet driver for your particular NIC.​

3. Configure and run "DHCP" from Mike Brutman's mTCP package, taking note of the returned IP information.​

4. Edit your GEOS.INI file to reflect the following for the [tcpip], [accpnt], and [accessPoint0001] sections. Populate the relevant IP fields with the information returned by the DHCP utility.​

Code:
[tcpip]
driver = TCP/IP Driver
driverType = 0
link = Packet Ethernet Driver
linkDomain = Packet Ethernet
port = 2

[accpnt]
prevID = 4
contents = {
00010001
}

[accessPoint0001]
name = LAN
netType = 1
default = 1
ipaddr = [i]x.x.x.x[/i]
ipgate = [i]x.x.x.x[/i]
ipmask = [i]x.x.x.x[/i]
dns1 = [i]x.x.x.x[/i]

5. Fire-up NDO, and go to town.​


There has been mention of the "ipaddr" field of the GEOS.INI file being dynamic if set to "0.0.0.0," but this failed to work for me. Also, it's worth noting that, in the absence of DHCP persistence in your environment, the expiration of an IP lease may require regular updating of the static IP address in that field.

The only anomalous behavior worth mentioning in all of this is that, with my particular system, some quirk of the ETHERPKT.GEO driver causes the keyboard to become unresponsive when exiting back to DOS from NDO. As a workaround, I'm just initiating "Exit > Reboot the Computer" instead.
 
Last edited:
Back
Top