Drivers for Addtron AE-200LC.

[Chuck(G)]

Most likely. When I do an install from a manufacturer's floppy image, I make sure that the disks I use are perfect. Errors on floppies have an ugly way of "creeping"...

 

[DOS lives on!!]

Well, I finally did it!

I found another download where all the files were in one folder. No extraction needed, which is probably why the installation errored out. I attached the hard drive from the System 310 as a slave to the "hope this works" computer. The MS Lan Manager installation program didn't let me install it directly to the slave hard drive, probably because Windows 98s DOS mode didn't load the proper driver to recognize it. So it installed to the main hard drive, then I copied the MSLANMAN folder to the slave hard drive.

I put the slave hard drive back into the Dell System 310. I ran the Lan Manager program and let it modify the AUTOEXEC.BAT to load it on startup. A restart, and everything loads perfectly! I can now see a DOS machine on my network from XP! YEEEEHHOOOOOO!

 

[DOS lives on!!]

Well, I kind of saw it on my network. The initial settings had it on the network, but me being myself, I fiddled around with the settings and lost it on the network. Poking around in there has also brought up a few more questions.

I have NETBEUI, TCP/IP, and Microsoft DLC installed. Do they share the same settings, as the configuration screens for each are the same. There are spaces to enter in settings for the IP address and Subnet Mask. Even though I have "Automatic configuration of DHCP" enabled, do I still have to manually enter in the settings?

One last thing, there is a configuration for "Connectivity". When I attempt to access the configuration page, the "Connectivity" disk is needed. What is the function of "Connectivity"?

 

[DOS lives on!!]

Also, is there a place to specify a workgroup? I only see a place for a domain.

 

[Chuck(G)]

I'll go through the setup routine again on one of my own machines. It's been too long since I set up MSLANMAN, so I could use a refresher.

 

[DOS lives on!!]

I also learned that MS Network Client can do workgroups, but I'm wanting to use MSLANMAN for all the hard work I put into it.

 

[Chuck(G)]

I went through and did setup again, using a Artisoft AE-2/T card set to 8-bit mode.

I think "workgroup" is a matter of terminology. When you're installing, SETUP asks you for the domain somewhere along the line. That's your workgroup.

At least that's what works for me.

I have two questions, though. I can't get DHCP to work talking to my Linux box DNS server. Any ideas? It's perfectly happy using a static IP, and I may leave it that way.

The other deals with a WINS server. LANMAN seems to appreciate one. Any way to get it to use a DNS server instead?

 

[DOS lives on!!]

Thanks for that Chuck!

Did you set the "Automatic configuration of DHCP," or did it only work with the static IP address?

I'll work with it more later today.

 

[Chuck(G)]

I could never get DHCP to work with it and had to use a static IP address. The funny thing is that it's still querying the DHCP service even when PROTOCOL.INI has a line in it that says DISABLEDHCP=1--but the static IP is eventually honored.

I'm going to try MS Network Client with the WG addon next to see if things are any better.

Apparently, if you do have a WINS server, you can add dnr to TCPIP services so that you can perform TCPIP operations (e.g. ping, telnet) to other machines by name. Apparently, the service is in LANMAN, it's just never configured.

One of the guides to configuring MS DOS networking has the right idea. Start off with a bottle of aspirin and a few bottles of your favorite alcoholic drink...

For those wondering why I'm not using other TCPIP drivers, it's because I want NetBEUI connectivity with my 98SE, XP and 2K boxes. I suspect that I could try installing the Novell NetBIOS drivers (they're available), but I'm not quite ready for another bottle of aspirin yet.

 

[Chuck(G)]

Well, I tried to get MSClient 3.0 installed on my XT, but no go. Even though I've got a V20 installed, I still get multiple messages about trying to run 80286 code on an 8088 or 80186. I'm guessing that that 286+ mode is firmly embedded in the TCPIP stack drivers.

 

[DOS lives on!!]

I got MS LAN Client installed. Now, with the AE-200LC drivers, there isn't a folder for the LAN Client, but there is one for LAN Manager. I did try to point the setup program to various locations in the driver disk, but it didn't find any of the files it wanted. Is there a specific driver for the LAN Client, or is the one for MSLANMAN supposed to work?

 

[Chuck(G)]

Give the one for MSLANMAN a try. I never could get MS LAN Client to work on an 8088 box, so I didn't take it any further.

 

[DOS lives on!!]

Ok, I finally got the drivers for the card to work, and selected the protocols to install, and now its asking me for an OEM driver disk. I tried the AE-200LC disk, but nothing is working. Do you know what it could be asking for?

EDIT: I just got it working! It installed the network card drivers and the protocols. Just have to work out a few errors, then maybe I can see it on my network.

 

[DOS lives on!!]

The results.

The results.

Got it installed, got the drivers and protocols on there, but the error messages still linger.

Here's what the startup process is with the protocols TCP/IP and NETBEUI installed,

NDIS 2.0 Network Driver, v 1.01
Copyright 1992, Addtron Tech. Co,. Ltd
*** AE-200 series card not present at IO addresses.
***Initialization failure
Error loaing device driver AE-200.DOS.

Error 7302: This device driver type is not supported by the device loader AE-200.DOS was not loaded.

C>C:\NET\nwlink
Microsoft (R) NWLINK Version 1.0
Copyright (C) Microsoft 19994. All rights reserved

C>C:\NET\netbind.com
MS-DOS LAN Manager v2.1 Netbind
Error: 33 Unable to bind.

C>C:\NET\umb.com

C>C:\NET\tcptsr.exe
NET0111: Error accessing NEMM.DOS. TCP 1.0 not loaded.

C>C:\NET\tinyrfc.exe
NET0111: Error accessing NEMM.DOS. Tiny RFC 1.0 not loaded.
Press any key to continue

C>C:\NET\nmtsr.exe
NET0111: Error accessing NEMM.DOS. NMTSR 1.0 not loaded.
Press any key to continue

C>C:\NET\emsbfr.exe

C>C:\NET\net start
Could not load the transport netbeui.
Error 3659: To load NETBEUI, the NDISHLP.sys driver must be listed in the [Network Drivers] section of the SYSTEM.INI file.

Error 7361: IPX or NetBIOS must be running in order to load the network services.

C>
C>

There is a protocol installed called NWLINK IPX Compible. How would I get NetBIOS running?

And heres the startup process when NETBEUI and MS TCP/IP aren't installed. Although there is one protocol that installs with the card and can't be removed (NWLINK IPX compatible protocol).

PRO0012E: Multiple protmanname in PROTOCOL.INI
NDIS 2.0 Network driver, v 1.01
Copyright 1992, ADDTRON Tech. Co,. Ltd
***AE-200 series card not present at IO address.
***Initialization failure
Error loading device driver AE-200.DOS.

Error 7302: This device driver type is not supported by the device loader. AE-200.DOS was not loaded.

Error 7321: Network-card drivers failed to load.

C>C:\NET\nwlink
Microsoft (R) NWLINK version 1.0
COPYRIGHT (C) Microsoft 1994. All rights reserved

C>C:\NET\net start

Error 5733: The protocol manager has reported an incomplete binding.

C>
C>

What is this utility trying to bind?

 

[DOS lives on!!]

I can easily edit the SYSTEM.INI file to add the NETBEUI service, but is there a place to get the NetBIOS protocol? How come the ADDTRON.DOS driver isn't being accepted by the program?

 

[Chuck(G)]

***AE-200 series card not present at IO address.

Is the I/O address correct in your PROTOCOL.INI file?

Isn't DOS network setup fun?

 

[DOS lives on!!]

Is the I/O address correct in your PROTOCOL.INI file?

Isn't DOS network setup fun?

As soon as I can get a text editor on there, I'l tell you. I only SYS C:'d the drive, not fully installing DOS. Wouldn't network file transferrs be easier.

Oh yes, I'm having fun at this. Once I blog this process, there's MUCH more I had to do behind the scenes.
But it doesn't top the fourteen hours in a row I spent finding and downloading seven gigabytes worth of DOS utilities at many different FTP sites.

 

[DOS lives on!!]

Plan 3, I'm going to use mTCP. The reason why the computer and MS Lan Client weren't detecting the card was because the card has two modes, which are set by jumpers. Mode 1 is for Compaq computers and C&T chipsets. Mode 0 is for all other computers. The card was set on Mode 0. But the computer had C&T chipsets in it. Then, I configured the right I/O address. Then ran the diagnostic program and it detected the card! Now, I'm in the process of setting up mTCP and I'll report back when I get further.

 

[Chuck(G)]

That's one of the reasons I like NE2000 (and clones) adapters for ISA. Almost everything understands them.

 

[DOS lives on!!]

Well before I found the support document here, I certainly couldn't get it to work. But after finding that the jumpers needed to be switched, everything is running smooth.