VOGONS

Loading DIS_PKT9.DOS, but not from CONFIG.SYS

Topic actions

First post, by Grzyb

Posted on 
User metadata
Rank l33t
Rank
l33t

I'm experimenting with DIS_PKT9.DOS, an NDIS to Packet Driver converter.

The procedure described on this page - https://web.archive.org/web/20170816111631/ht … er_installation - works fine, tested it with mTCP's DHCP.EXE and FTP.EXE.

But there's this inconvenience: can't load it whenever I need it - it's loaded from CONFIG.SYS.

I believe there's no need to use CONFIG.SYS for NDIS stuff - in Microsoft Network Client it's all loaded later, via "net initialize".

But I don't know how to make "net initialize" to load the stuff I need - it seems to ignore PROTOCOL.INI, and uses SYSTEM.INI instead?

Any ideas?
Ideally, I'm looking for the minimum set of files to use as a replacement for Packet Driver...

Kiełbasa smakuje najlepiej, gdy przysmażysz ją laserem!

Reply 1 of 4, by dgorski

Posted on 
User metadata
Rank Newbie
Rank
Newbie

DEVLOAD allows you to load drivers from DOS that normally need to be loaded in CONFIG.SYS.

You can create a NET.BAT file and load your drivers only when you want them. Something like:

DEVLOAD C:\NET\PROTMAN.DOS /I:C:\NET
DEVLOAD C:\NET\EL3C574.DOS
DEVLOAD C:\NET\DIS_PKT.DOS

(just replace DEVICE= with DEVLOAD)

https://home.mnet-online.de/willybilly/fdhelp … til/devload.htm
https://www.ibiblio.org/pub/micro/pc-stuff/fr … es/dos/devload/

- Darrin

Reply 2 of 4, by maxtherabbit

Posted on 
User metadata
Rank l33t
Rank
l33t

In general I avoid the use of "net initialize" as we discussed previously here Re: Windows for Workgroups TCP/IP Disk

But that said I think it does use PROTOCOL.INI to know which drivers to load, it would almost have to. It should use the PROTOCOL.INI that's in your WINDOWS directory though, not the one from the MS NET client.

Reply 3 of 4, by Grzyb

Posted on 
User metadata
Rank l33t
Rank
l33t

OK, tried that DEVLOAD thing - works fine!

I still believe that there's no need for third-party utilities to load NDIS drivers - but I've found a reason not to care:

NET.EXE is 450 KB
DEVLOAD.COM is 3 KB

Size does matter - I'm likely to run that stuff off a floppy...

Kiełbasa smakuje najlepiej, gdy przysmażysz ją laserem!

Reply 4 of 4, by Grzyb

Posted on 
User metadata
Rank l33t
Rank
l33t

There's some incompatibility between mTCP NetDrive and ODI+ODIPKT.

But it works fine with NDIS+DIS_PKT9.
So, in case of lack (or poor quality) of native PD, this may be the preferred choice.

Anyway, I'm attaching both drop-in replacements for PD - just add the driver for your hardware, and edit CFG/INI and BAT.

Kiełbasa smakuje najlepiej, gdy przysmażysz ją laserem!

Go to top of page Go to top of page
Back to Software
Close window
Close window