By now I am really frustrated, desperate and tired. I would like to connect a PC that's running under MS-DOS 6.22 to my
home network consisting of a few win98 and XP pcs using a Netgear614v2 Router with DLS. My main aim is to be able to transfer Files from the DOS Pc to the others.

I have a Realtek 8029 card installed and connected with a CAT cable to the Router. After installing MS-Dos Network Client 3.0 when I boot the PC the following happens:

c:\Net\net initialize
..... starts fine, no error message but a few copyright notices
C:\net\netbind.com
.... starts fine
C:\net\umb.com
.... starts fine
C:\net\tcptsr.exe
Initializing TCP/IP via DHCP ....
.... and that's where the system hangs up and that's it.

The next commands on the list would be tinyrfc, nmtsr, emsbfd and
net, but of course I never get there.

I have tried with and without DHCP support in the router, and with or without a dedicated IP address. I have changed the protocol.ini
various times, I have tried a different card (Realtek8139). The result remains the same. From a different PC I can take a look at the
router and I observe that, a new PC is connecting and that it gets an IP address properly assigned. But still, the DOS PC freezes there and that's it. I removed Network Client and installed MS Lanman and the result is basically the same.

Any ideas?

Btw I saw some references to something called Waterloo TCP but was not sure if that would solve my problems and could not find a good description for downloading and setting it up anyway.

Thank you in advance for your kind attention.

Is umb.com an UMB provider?

Are you using himem?

EMM?

What params are allowed in TCPTSR?

What does it do with the cable unplugged?

If at first you don't succeed, you're about average.

M2

You need M$ NetworkClient 3 both Server and Client and only TCP/IP protocol, plus an NDIS driver for the Realtek NIC,this is available in the full download driver oem package from:

http://www.realtek.com.tw

http://www.windowsnetworking.com/j_helmig/dosclnt3.htm
http://www.windowsnetworking.com/j_helmig/doscltcp.htm
http://www.windowsnetworking.com/j_helmig/dosservr.htm

http://www.spartacom.com/products/lantastic.htm

http://83.67.55.228/index.htm

Hi,

To me the right thing isn't to suggest wasting the
PC's precious resources for MS NetWork Client v3.0
or MS LanMan (v7?)! My favourite DOS applications
are those made for Erik Engelke's Waterloo TCP/IP.

Why? Because of memory considerations, before all
other (it's limited)... Which? I'm thinking of a
combination, actually: RLFossil v1.23 + MS-Kermit
v3.16 Final. You set one to "Auto-Answer" (as for
a classic Hayes MoDem: AT S0=1). The client will
dial to the server just as if it were a DialUp BBS
or FreeNet: once connected to the terminal, users
type a Hayes-compatible command like this: "AT DT
192.168.7.3", etc. The remote PC auto-responds to
"CONNECT" with "ATA" which RLFossil emulates... I
am confident in the Kermit file transfer protocol,
it doesn't mean i don't have an other favorite and
hence i suggest you read "Long Filename Null modem
Transfers" of January 12, 2004 - Over 2 years old:

http://www.computing.net/dos/wwwboard/forum/14435.html

Salutations,

Michel Samson
a/s Bicéphale

http://www.windowsnetworking.com/j_helmig/dosclnt3.htm
and
http://www.windowsnetworking.com/j_helmig/doscltcp.htm

are two of the links / procedures I followed until I got stuck. Nulmodem-Cable is not really the alternative to the network via ethernet. If anyone could tell me how to use Waterloo/Wattcp for my purpose I would be happy.

I have no idea what umb.com is or does and yes, I will be using emm if possible or reasonable once the system works, but i dont think thats the point. When I do not connect the cable the result is the same.

I do know Lantastic because they had it in an office I worked many years ago and I very much like it, its a great programme, but a price of 120 US$ per user (which means I would have to pay a minimum of US$ 240,00) is more than I can and want to afford.

Hi,

Co> I would like to connect a PC... ...to my home
Co> network... ...transfer Files... ...If anyone
Co> could tell me how to use Waterloo/Wattcp...

Why not TelNet, instead of MicroSoft's proprietary
NetBEUI, TCP/IP, IPX/SPX, NDIS or NT4 SoftWare?...

Lets begin with the RealTek 8029 Packet-Driver for
Waterloo TCP/IP (DOS)... Apparently, it's a clone
of the venerable NE2000 in PCI version but i found
an archive which seems very promissing. Get this:

http://www.abn.ru/support/Realtek/oem8029.exe
RTL8029 Driver Disk v3.55 - Fall of 1998, 461 Kb;
LANTastic, Linux, MS-LANMan (DOS & OS/2), NT 3.51,
NetWare Client, NetWare Server, PCI Packet-Driver,
SCO, Windows 16/32 (WorkGroups v3.11, 95, 98, NT).

Open it with WinRAR and extract `PCIPkt.COM', it's
the file you need to get started! DOS ODI is also
an option when used with a "shim", that's what the
`PCIODI.*' files from the NWClient (DOS) directory
are for so, feel to extract these too if suitable.

Once you have the Packet-Driver loading correctly,
let me know if TelNet is an acceptable solution...

Salutations,

Michel Samson
a/s Bicéphale

... Although I believe thats just the drivers I have already installed I'll give it a try. The reason why I thought I had to use TCPIP is because I thought the router all PCs are connected to might require TCPIP. Am I wrong there?

Could I just as well use NetBEUI or IPX/SPX on my DOS PC to connect to the others? And I thought Telnet (as an example) was an application that would require TCP (or another protocol) to be running. Am I wrong again?

Hi,

Co> If anyone could tell me how to use Waterloo...

I'll assist with Waterloo TCP/IP alternatives, not
MicroSoft's proprietary NDIS (Windows) protocol or
any DOS applications created specifically for this
environment: my expertise doesn't include WatTCP-
friendly SoftWare with the look, feel and features
of a typical Windows File Browser which you'd load
under DOS instead of Windows! It's not clear what
suggestion suits you best but FTP comes to mind (i
know that Engelke's FTP v0.70 application displays
LFNs correctly and files DownLoad as "8.3" renamed
copies, provided there's no exception characters).

TelNet relies on no particular OS neither and this
is also very true of Kermit TelNet Clients/Servers
with the same-name file transfer protocol (there's
a version for every OS in existance, practically).

MS-Kermit (the DOS built) implies "8.3 File Names"
here again, though... Which now reminds me that i
never use LFNs under real DOS, only from a W32 DOS
Box!... Maybe you'd be better ask yourself if LFN
support matters, oh and... by the way... IPXCopy
v2.70 has nothing to do with "Null-MoDem" cabling!

A TelNet Client/Server like MS-Kermit has internal
interfacing available for a few DOS TCP/IP stacks,
including Class-1 WatTCP-compatible Packet-Drivers
and DOS ODI enrironments. RLFossil enables TelNet
using an emulated (BIOS Int-14/FOSSIL) serial-port
to allow LEGACY terminal emulators to connect with
a Packet-Driver, or DOS ODI via a suitable "shim".

The IPX tool isn't universal like TelNet but would
allow you to copy whole trees including your LFNs;
it may even work correctly in a VMWare WorkStation
DOS box but i didn't care to evaluate that, euh...

Now, how to make DOS support LFNs is another story
(or worst with MicroSoft TCP/IP and/or NetBEUI)!!!

Salutations,

Michel Samson
a/s Bicéphale

>I'll assist with Waterloo TCP/IP

Thank you for your kind offer of assistance: I do not care about the interface. I actually prefer command lines in DOS to graphical interfaces. I tried with the MS Network Client and failed, any method that would work is agreeable.

If I may repeat myself: I have a router and a few PCs connected to it. The router has assigned an address of the 192.168.0.xx type to each of the PCs. I would love to attach another PC of mine to my router which is running with MS-DOS as its OS.

Isn't it necessary to have the connection between the PC and the Router via TCP/IP working properly before I can begin to think about any file transfer protocols like Telnet or FTP or Net commands?

Hi,

Co> ...any method that would work is agreeable.

Here's how i suggest you set a WatTCP environment:

_______________________________________________________________[Go.BAT]_
@Echo Off
LH VMANSI.COM>Nul
:SetWatTCP
LH RTsPkt.COM 0x60
Echo.
If (%MyIP%)==() Set MyIP=192.168.7.5
If (%RemIP%)==() Set RemIP=192.168.7.1
If (%NetMask%)==() Set NetMask=255.255.255.0
If (%DNS1%)==() Set DNS1=64.235.193.5
If (%DNS2%)==() Set DNS2=69.28.239.8
If (%Domain%)==() Set Domain=electrobox.net
If (%PeerMRU%)==() Set PeerMRU=1496
If (%MSS%)==() Set MSS=1456
If (%WATTCP.CFG%)==() Set WatTCP.CFG=C:\EtherNet

Echo.
Echo Creating `%WatTCP.CFG%\WATTCP.CFG'...
Echo my_ip=%MYIP%>%WatTCP.CFG%\WATTCP.CFG
Echo gateway=%REMIP%>>%WatTCP.CFG%\WATTCP.CFG
Echo netmask=%NETMASK%>>%WatTCP.CFG%\WATTCP.CFG
Echo nameserver=%DNS1%>>%WatTCP.CFG%\WATTCP.CFG
If Not (%DNS2%)==() Echo nameserver=%DNS2%>>%WatTCP.CFG%\WATTCP.CFG
If Not (%DNS3%)==() Echo nameserver=%DNS3%>>%WatTCP.CFG%\WATTCP.CFG
Echo domainlist=%DOMAIN%>>%WatTCP.CFG%\WATTCP.CFG
Echo print="WatTCP configuration...">>%WatTCP.CFG%\WATTCP.CFG
Echo hostname="bbs">>%WatTCP.CFG%\WATTCP.CFG
Echo idname=p-200mmx>>%WatTCP.CFG%\WATTCP.CFG
Echo aamask=0000>>%WatTCP.CFG%\WATTCP.CFG
Echo cd_delay=72>>%WatTCP.CFG%\WATTCP.CFG
Echo nc_delay=18>>%WatTCP.CFG%\WATTCP.CFG
Echo term_type=vt100/115200>>%WatTCP.CFG%\WATTCP.CFG
Echo inport=0>>%WatTCP.CFG%\WATTCP.CFG
Echo outport=23>>%WatTCP.CFG%\WATTCP.CFG
Echo handshake=3>>%WatTCP.CFG%\WATTCP.CFG

This batch-file loads `VMANSI.COM v2.70' (from the
`VMix285.ZIP' archive), this is a lightweight ANSI
driver (less than 2 Kb) which loads/unloads as you
require. `RTsPkt.COM' is for the RealTek RTL-8139
based NIC i use over here and `PCIPkt.COM' is what
you must replace it with if you keep your RTL-8029
instead (note that syntax varies in some cases)...

A DOS environment variable named WatTCP.CFG points
at the C:\EtherNet directory in this example, have
this defined correctly in order to fit your setup!

Co> Isn't it necessary to have the connection
Co> between the PC and the Router via TCP/IP
Co> working properly before I can begin to think
Co> about any file transfer protocols...

You seem to refer to the ping test, i'd start with
loading a Packet-Driver 1st: does it load at all?

Once the Packet-Driver has been managed with, your
router is the next potential source of problem but
lets simply suppose it's ready for Engelke's Ping.

For an FTP test you'll need an FTP server to begin
with, `IPSwitch WS_FTP Server v5' is one of those.

Let me know if you want to try MS-Kermit, a proper
.INI setup file will ease its configuration simply
by reading DOS environment variables directly (you
would need a different .INI file plus a 2nd batch-
file if you prefer my RLFossil + MS-Kermit combo).

Other possibilities which you'll enable: Arachne,
Lynx, etc. The Waterloo TCP/IP environment should
be suitable for a number of applications but there
may be some more tweaks necessary, keep us posted!

Salutations,

Michel Samson
a/s Bicéphale

Report Offensive Follow Up For Removal

Just to let you know, this looks great. Thank you! I am working at it and I shall reply as soon as it either works out or if any difficulties should arise. I just have a difficult assignment which keeps me busy so it will take 2 or 3 more days until I get back to this issue.

Hi Coracle,

Co> Just to let you know...

My warm thanks to you as it's a real pleasure when
a correspondant will care enough to keep us posted
instead of vanishing in thin air! I must have got
irreversibly affected by my former BBSing hobby...

:-)

Co> ...this looks great.

"Great"? Nah... A full-fledged batch-file musn't
attempt to load your Packet-Driver if it's already
present, it should check that you IP isn't 0.0.0.0
(IPRead v0.15a helps with that) and unload it even
before pinging if it's necessary... But as it is,
the batch-file captured from above works fine with
Engelke's FTP v0.70 application after i applied it
(Cut & Paste) to my IBM ThinkPad 486-50 Mhz LapTop
in the next room, yesterday. Lynx is OKay too and
tools like DayTime, NTime, TCPInfo, etc. just work
as expected. I only had to load Enabler.EXE (some
PCMCIA Client Driver) and replace RTsPkt.COM using
PCM100_P.COM instead (which is a Packet-Driver for
my LinkSys PCM100 Fast EtherNet PCMCIA Adapter)...

B-)

This is not close to a MicroSoft-based LAN but the
FTP transfers are supported already and i couldn't
resist the urge to show what TelNet would be like:

==============================================================================
Addr. Low area High area Program or device driver
--
0272h 752 .. Device=DREMM386 Attr=C000h Name=EMMQXXX0
02A8h 256 .. COMMAND C:\ /E:3072 /P
02D7h 99,552 .. RLFOSSIL :\ETHERNET\KERMIT.EXE
1B27h 319,056 .. KERMIT -f ArcnRLFK.INI
6942h 3,744 .. COMMAND
6A17h 219,776 .. <largest free area>
C002h .. 224 DOSMAX
C012h .. 4,192 Device=ANSI Attr=C053h Name=CON
C119h .. 8,288 Device=DISPLAY Attr=C053h Name=CON
C320h .. 432 Device=TDSK Attr=0800h Drive D
C33Ch .. 432 Device=TDSK Attr=0800h Drive E
C358h .. 2,672 FILES
C400h .. 960 FCBS
C43Dh .. 18,624 BUFFERS
C8CAh .. 2,288 LASTDRIV
C95Ah .. 3,008 STACKS
CA17h .. 144 INSTALL
D202h 64 6,080 COMMAND 2 1 "Kermit.EXE -f ArcnRLFK.INI"
D2BFh .. 7,424 KEYB CF,863,C:\DOS\KeyBoard.SYS
D490h .. 3,872 DOSKEY /BufSize=256
D583h .. 672 ENABLER
D5AEh .. 9,280 PCM100_P

654,336 bytes (639k) total DOS 6.20 conventional memory.
219,776 bytes (215k) largest executable program. 32,944 bytes if loaded high.

High memory is managed by DOS.

0 bytes Extended (AT/286/386) memory, reported by BIOS.
7,012k bytes XMS 3.0 (3.00) memory: 0 used + 7,012k free. DOS in HMA.
==============================================================================

The most noticeable difference is when you look at
how much memory remains available after RLFossil &
MS-Kermit (not even the light version of it!) have
been loaded. Sometimes, simpler does mean better.

Co> ...shall reply as soon as it either works out
Co> or if any difficulties should arise.

Good, i hope you'll enjoy it when you get there...

8-)

In the meantime, for a taste of what "Great" would
involve in my book, i'd suggest a search on Yahoo!

;-D

Salutations,

Michel Samson
a/s Bicéphale

Report Offensive Follow Up For Removal

Hello again, I am back:
Step 1:
The batch file runs fine without errors. The packet driver seems to install perfectly.
I copied and ran Ping.exe (from the Wattcp 32 package) to the router and to the other PC's IP addy's connected to the router and I get response. Name Resolution does not seem to work but that is of no concern to me right now. TCPINFO reports proper IP address of my DOS PC.

Possible Issue: running Ping from one of the other PCs and targetting the DOS PC's IP address gives me time-out, so it does not seem to work properly this way round. Also, the Router does not seem to recognize the existance of the DOS Pc.

Step 2:
Now that they seem to be connected somehow I would like to transfer files from the DOS PC to a Win98 PC both connected to the router. What are the next steps?

Hi,

Co> ...packet driver seems to install... ...ran
Co> Ping... ...I get response. TCPInfo reports
Co> proper IP... ...Issue... ...Ping from one
Co> of the other PCs... ...time-out... ...the
Co> Router does not seem to recognize...

I re-read the whole thread, LFNs and TelNet didn't
retain your interrest so i'll consider this leaves
FTP as an answer, especially if the PC is a 75 Mhz
P1 with 64 Mb RAM. Consequently, i don't see what
more to add since i've made my statements already!

About tools, be warned you better try TCPInfo from
2 different packs; as for appearing invisible, it
doesn't suprize me that the Packet-Driver fails to
operate like a File Server in a LAN environment...

My MoDem/Router can show stations running a LiveCD
but it doesn't display the name and MAC address of
a DOS WatTCP machine and yet i'm TelNetting on the
later - which is fine with me, but i can be wrong.

Co> ...I would like to transfer files from the DOS
Co> PC to a Win98 PC both connected to the router.

I wrote a pre-emptive reply to your attention. If
Erik Engelke's FTP v0.70 client works as expected,
you're able to access an FTP server which is ready
for the connection. Of course, non-DOS SoftWare &
Systems means Off-Topic here... Discussions about
server conflicts would be better handled elsewhere
too - not to mention configurating a MoDem/Router.

How pre-emptive? When you've read my story of the
cow i'll know that you've read far enough. Enjoy!

Co> What are the next steps?

Quite frankly, i gather that Linux might be a more
suitable forum but i doubt the users can help when
resources are so scarce... The LiveDefender CD is
still slow on a P1 with more than twice your speed
and four times the memory amount you have! Sorry.

Salutations,

Michel Samson
a/s Bicéphale