Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Trouble Installing Ethernet Driver in MS-DOS 6.22  (Read 20595 times)

0 Members and 1 Guest are viewing this topic.

jaydub

    Topic Starter


    Greenhorn
    • Yes
  • Experience: Experienced
  • OS: Windows XP
Trouble Installing Ethernet Driver in MS-DOS 6.22
« on: July 30, 2011, 04:59:53 PM »
I'm having difficulty installing an ethernet driver for my NIC under MS-DOS 6.22.  My goal is to get a broadband cable connection and install Arachne web browser.  Network hardware is as follows:
- Marvell Yukon 88E8001 Gigabit Ethernet Controller is built into ASUS motherboard and uses PCI-E bus.  Connected to router.
- Marvell Yukon 88E8056 Gigabit Ethernet Controller is built into ASUS motherboard and uses PCI bus.  Currently not connected to router.
- DLink 655 Wireless Router (using ethernet cable, not wireless)
The Yukon driver is NDIS2 Marvell DOS driver v8.21.1.1 from ASUS which includes the files yuknd.dos, protocol.ini and oemsetup.inf. 

To install the driver, I'm using instructions found at http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS_-_NDIS_driver_installation, which is based on DIS_PKT9.DOS.   So, I've assembled a floppy with the following files:
- protman.dos (extracted from MS Client 3.0)
- protman.exe (extracted from MS Client 3.0)
- netbind.com (extracted from MS Client 3.0)
- DIS_PKT9.dos (downloaded from link at the SourceForge page cited above)
- yuknd.dos (ethernet driver from ASUS)
- protocol.ini (new file created by me with MS-DOS EDIT command and saved with .ini extension)

It should be noted I did not include on the floppy two of the driver files from ASUS:
- oemsetup.inf (packet driver converter instructions did not say to use other files when assembling the floppy)
- the original protocol.ini (per packet driver converter instructions, I created and used a new protocol.ini file)
 
All files on floppy were copied to a new C:\NET directory and no other files exist in that directory.

Here is protocol.ini file I created:
Code: [Select]

--- PROTOCOL.INI ---

[protman]
DriverName=PROTMAN$

[YUKND]
DriverName=YUKND$

[PKTDRV]
drivername=PKTDRV$
bindings=YUKND
intvec=0x60
chainvec=0x68

Here is autoexec.bat file, as modified per instructions:
Code: [Select]
LH /L:0 C:\DOS\SMARTDRV.EXE /X
@ECHO OFF
PROMPT $p$g
PATH C:\DOS
PATH C:\NET;C:\NC;%PATH%
SET TEMP=C:\DOS
LH /L:1,32304 C:\DOS\MSCDEX /D:mscd
C:\DOS\MOUSE.COM
C:\NET\NETBIND.COM

Here is the config.sys file, as modified per instructions:
Code: [Select]
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS
BUFFERS=15,0
FILES=30
DOS=UMB
LASTDRIVE=E
FCBS=4,0
DOS=HIGH

DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\DOS\GCDROM.SYS /D:MSCD /C2
DEVICEHIGH=C:\NET\PROTMAN.DOS /I:C:\NET
DEVICEHIGH=C:\NET\YUKND.DOS
DEVICEHIGH=C:\NET\DIS_PKT9.DOS

So, when I boot up, I get the following screen that says Protocol Manager has not been loaded and system is unable to open PROTMAN$:
 
Code: [Select]
PRO0004E: A parameter does not belong to any logical module
Marvell(R) Yukon(R) Ethernet Controller NDIS 2.0.1 MAC Module  v8.21 (20060428)
(C)Copyright 2003-2006 Marvell(R).  All rights reserved..
   LTE0002E: Protocol Manager has not been loaded
MAC/DIS to Packet Driver converter loaded. Version 1.09
Copyright 1991 FTP Software, Inc.  All rights reserved.
Protocol Manager not present
 
C:\>
MS-DOS LAN Manager V2.1 Netbind
Error: 7906 Unable to open PROTMAN$.
C:\>

It should be noted that I later add oemsetup.inf to the \NET directory, but it didn't change the outcome.
 
Any suggestions would be really appreciated.  I'm attaching the following screen shots for reference:
- boot up screen showing the error
- list of files in the \NET directory

[regaining space - attachment deleted by admin]
« Last Edit: July 30, 2011, 06:00:40 PM by jaydub »

Computer_Commando



    Hacker
  • Thanked: 494
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #1 on: July 30, 2011, 05:48:21 PM »
I see only 1 thing.
never seen 2 DOS statements, it's always 1 line:
DOS=HIGH,UMB

http://www.computerhope.com/ac.htm

I tried to do what you are attempting on my old DOS 6.22 machine.  Never did get it to work.

I did a Novell network in DOS like a 100 years ago.  I don't remember it being this difficult.  I believe it was only peer-to-peer for a print server.  I do remember it was all 10-base-2 (coaxial cable not UTP).

jaydub

    Topic Starter


    Greenhorn
    • Yes
  • Experience: Experienced
  • OS: Windows XP
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #2 on: July 30, 2011, 06:14:35 PM »
Thanks for the tip on UMB,HIGH.  I changed that in cofig.sys.  Too bad it didn't change the outcome on my driver.

Do you know of any other way to install the driver without having the overhead of like MS Network Client 3.0?  Gobbles up too much memory to use Arachne.

Computer_Commando



    Hacker
  • Thanked: 494
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10

jaydub

    Topic Starter


    Greenhorn
    • Yes
  • Experience: Experienced
  • OS: Windows XP
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #4 on: July 30, 2011, 06:44:53 PM »
That file first shipped with Windows.  As it isn't a file native to 6.22, I don't see how it could solve the problem.

Computer_Commando



    Hacker
  • Thanked: 494
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #5 on: July 30, 2011, 06:51:21 PM »
I don't know.  Have my 6.22 machine next to me which also has Windows for Pen Computing.  Touch screen still works in Windows.  I'm out of ideas.

jaydub

    Topic Starter


    Greenhorn
    • Yes
  • Experience: Experienced
  • OS: Windows XP
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #6 on: July 30, 2011, 06:56:06 PM »
I do appreciate your time and effort. 

patio

  • Moderator


  • Genius
  • Maud' Dib
  • Thanked: 1769
    • Yes
  • Experience: Beginner
  • OS: Windows 7
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #7 on: July 30, 2011, 06:57:30 PM »
Quote
SET TEMP=C:\DOS

Why not C:\Temp...?
from the autoexec.

Quote
DEVICE=C:\DOS\GCDROM.SYS /D:MSCD /C2

GCDRom ? ?

Quote
yuknd.dos (ethernet driver from ASUS)

If this isn't a native DOS driver it'll refuse to load...have you tried a DOS driver from the manuf. site ? ?

Course i'm a bit rusty on these ...others here are way more accomplished.
" Anyone who goes to a psychiatrist should have his head examined. "

jaydub

    Topic Starter


    Greenhorn
    • Yes
  • Experience: Experienced
  • OS: Windows XP
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #8 on: July 30, 2011, 08:33:17 PM »
SET TEMP=C:\DOS was the default setting when I installed the O/S

GCDROM is CD ROM driver for Sata drives

yuknd.dos is definately a native DOS driver.  It was downloaded from the manufacturer's site (Marvell).


jaydub

    Topic Starter


    Greenhorn
    • Yes
  • Experience: Experienced
  • OS: Windows XP
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #10 on: July 31, 2011, 06:10:41 PM »
Finally got my driver installed.  Jeees.  The packet driver instructions seemed to imply that " ---PROTOCOL.INI--- " should be at the top of protocol.ini file.  Nope.  I guess I took instructions to literally.  I took that header out and the driver loaded fine.  So, anyway I'm now connected to the web under MS-DOS 6.22 and browsing in Arachne.  Thanks for everyone's help.

Computer_Commando



    Hacker
  • Thanked: 494
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Re: Trouble Installing Ethernet Driver in MS-DOS 6.22
« Reply #11 on: July 31, 2011, 06:18:20 PM »
Missing a semicolon (which comments the line, so is ignored) or delete the line as you did.  How did I miss that?  It seems so obvious, now.

;--- PROTOCOL.INI ---

[protman]
DriverName=PROTMAN$

[YUKND]
DriverName=YUKND$

[PKTDRV]
drivername=PKTDRV$
bindings=YUKND
intvec=0x60
chainvec=0x68