[Freedos-devel] Wget + Ndis ?

Discussion:

Sébastien FAVIER

2014-11-26 10:08:35 UTC

Hello!

Thank you for your reply, i know how i doing for use packet driver with NDIS2 ! :-)
(MSClient3.0)
but, when i install DIS_PKT.DOS (With DEVLOAD) i have this
"Interrupt vector for Packet Driver not specified in PROTOCOL.INI"

then that this file is in the same directory and i have specified this!

This is Protocol.ini :
==============================================
[network.setup]
version=0x3110
netcard=nic,1,NIC,1
transport=tcpip,TCPIP
lana0=NIC,1,tcpip

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP

[NIC]
DriverName=ATL1E$
; This file gets inserted in to the driver's protocol.ini file.
; You can set hardcode lines for setting duplex/speed here.

[tcpip]
NBSessions=3
DEFAULTGATEWAY0 = 192 168 1 10
SUBNETMASK0 = 255 255 255 0
IPADDRESS0 = 192 168 1 11
DisableDHCP = 1
DriverName=TCPIP$
BINDINGS=NIC
LANABASE=0
TCPSEGMENTSIZE=1450
TCPWINDOWSIZE=4350
WINS_SERVER0 = 192 168 1 10

[PKTDRV]
DriverName=PKTDRV$
Bindings=NIC
intvec=0x60
chainvec=0x66
==============================================

Can help me ?

Best regards
FAVIER Sébastien

Ulrich Hansen

2014-11-26 14:16:16 UTC

Permalink

Bonjour Sébastien,

I am looking into it. I got a test system up and running with a DOS driver (not packet driver) on FreeDOS in VirtualBox. Unfortunately I couldn't reproduce the too easy setup I described years ago on the wiki site. :-(

At the moment I seem to be unable to get emm386 / jemmex to provide umbs that do not crash MS protman.

I try to find time again this evening.

Sorry for the inconvenience.

Ulrich

Post by SÃ©bastien FAVIER
Hello!
Thank you for your reply, i know how i doing for use packet driver with NDIS2 ! :-)
(MSClient3.0)
but, when i install DIS_PKT.DOS (With DEVLOAD) i have this
"Interrupt vector for Packet Driver not specified in PROTOCOL.INI"
then that this file is in the same directory and i have specified this!
==============================================
[network.setup]
version=0x3110
netcard=nic,1,NIC,1
transport=tcpip,TCPIP
lana0=NIC,1,tcpip
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP
[NIC]
DriverName=ATL1E$
; This file gets inserted in to the driver's protocol.ini file.
; You can set hardcode lines for setting duplex/speed here.
[tcpip]
NBSessions=3
DEFAULTGATEWAY0 = 192 168 1 10
SUBNETMASK0 = 255 255 255 0
IPADDRESS0 = 192 168 1 11
DisableDHCP = 1
DriverName=TCPIP$
BINDINGS=NIC
LANABASE=0
TCPSEGMENTSIZE=1450
TCPWINDOWSIZE=4350
WINS_SERVER0 = 192 168 1 10
[PKTDRV]
DriverName=PKTDRV$
Bindings=NIC
intvec=0x60
chainvec=0x66
==============================================
Can help me ?
Best regards
FAVIER Sébastien
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk_______________________________________________
Freedos-devel mailing list
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Ulrich

2014-11-26 23:53:42 UTC

Permalink

Bonsoir Sébastien,

I could verify for me, that I still know how to use a NDIS driver as packet driver. :) I confess though, I was unable to do it with DEVLOAD.

It was kind of a relief that it works still exactly the way I documented it in the wiki. Earlier today I read too fast and missed some important parts of it, so I was pretty désolé in my previous mail. Seems my wiki article is way too long even for me :-) and obviously too long ago.

I use only very few elements of MS CLIENT to make your NDIS driver work as packet driver. If you want to use all of MS CLIENT, you will need additional programs loaded at boot, like IFSHLP.SYS in FDCONFIG.SYS. You also will need a SYSTEM.INI.

But before you go there, I would really like you to follow these steps once and create a VERY simple install. Just to see if and how it works:

For the PROTOCOL.INI the following lines alone do the job:

[protman]
DriverName=PROTMAN$

[NIC]
DriverName=ATL1E$

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

In your FDCONFIG.SYS please add the following lines

1?DEVICEHIGH=C:\NETWORK\MSCLIENT\PROTMAN.DOS /I:C:\NETWORK\MSCLIENT
1?DEVICEHIGH=C:\NETWORK\MSCLIENT\ATL1E.DOS
1?DEVICEHIGH=C:\NETWORK\MSCLIENT\DIS_PKT.DOS

(I assume you have all your files in C:\NETWORK\MSCLIENT. Please change that, if you have them in a different place.

In FDCONFIG.SYS there is also a line for the memory manager JEMMEX. Sigh. :-( Unfortunately it is not working well with the NDIS-driver or PROTMAN and crashes as soon I let it use UMBs. So I just comment it out for the moment by putting a ";" before it:

;1?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST NOVME NOINVLPG

I suggest to use HIMEMX instead, which is currently only activated by the second item in the bootmenu. So we add a "1" before it:

12?DEVICE=C:\FDOS\BIN\HIMEMX.EXE

I know loosing UMBs completely is unfortunate and you end up with only 550 kilobytes for programs. Maybe others here know how to help :-)

In your AUTOEXEC.BAT some additional lines need to be added:

Please add MSCLIENT directory to the PATH:
SET PATH=%dosdir%\BIN;C:\FDOS\BIN\CTMOUSE;C:\FDOS\MTCP;C:\NETWORK\MSCLIENT

I suggest to put C:\FDOS\BIN and C:\FDOS\MTCP before the MS CLIENT directory. Because MS CLIENT includes some commands with the same name like "ping".

In AUTOEXEC.BAT you find already a line like:

IF "%config%"=="2" LH SHARE

That means that FreeDOS 1.1 SHARE is loaded with the second item in the boot menu.
I suggest to load your network with the first menu item (as we already did in FDCONFIG.SYS), so you add these two lines:

IF "%config%"=="1" LH SHARE
IF "%config%"=="1" C:\NETWORK\MSCLIENT\NETBIND.COM

Now reboot.

:-)

Happy hacking with ftpsrv and wget. Bonne nuit!

Post by Ulrich Hansen
Bonjour Sébastien,
I am looking into it. I got a test system up and running with a DOS driver (not packet driver) on FreeDOS in VirtualBox. Unfortunately I couldn't reproduce the too easy setup I described years ago on the wiki site. :-(
At the moment I seem to be unable to get emm386 / jemmex to provide umbs that do not crash MS protman.
I try to find time again this evening.
Sorry for the inconvenience.
Ulrich

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk_______________________________________________
Freedos-devel mailing list
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Tom Ehlert

2014-11-27 12:11:13 UTC

Permalink

Post by Ulrich
I know loosing UMBs completely is unfortunate and you end up with
only 550 kilobytes for programs. Maybe others here know how to help :-)

use EMM386 or JEMMEX, but don't use

1?DEVICEHIGH=C:\NETWORK\MSCLIENT\ATL1E.DOS

use

1?DEVICE=C:\NETWORK\MSCLIENT\ATL1E.DOS

instead. this should take care of the problem.

Tom

Sébastien FAVIER

2014-11-27 12:41:24 UTC

Permalink

Hello
Thank you for your responses

the problem is in SYSTEM.INI

[network drivers]
netcard = ATL1E.DOS
transport = tcpdrv.dos,nemm.dos
devdir = C:\cpcdos\pilotes\reseau
LoadRMDrivers=yes

in 'transport' line, ',dis_pkt.dos' is missing
i added this, and my the problem was resolved :-)

Thank you all

Ulrich

2014-11-27 14:36:49 UTC

Permalink

Hi Tom,
hi Sébastien,

@Tom: Thanks for the help! At least in my installation of FreeDOS 1.1 in VirtualBox I had to load all three drivers into low memory.

1?DEVICE=C:\NETWORK\MSCLIENT\PROTMAN.DOS /I:C:\NETWORK\MSCLIENT
1?DEVICE=C:\NETWORK\MSCLIENT\ATL1E.DOS
1?DEVICE=C:\NETWORK\MSCLIENT\DIS_PKT.DOS

Loading PROTMAN.DOS high would just stop and freeze the machine. Loading the NDIS driver high (in VirtualBox this is of course PCNTND.DOS, not Sébastiens driver) leads to some colorful dancing pixels ;-). Loading DIS_PKT.DOS blocks the last line in FDCONFIG.SYS to be executed, which is:
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT

But loading all three drivers low solved the issue! :-) I was even able to load JEMMEX with the line:
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG

so it accepted B000-B7FF. I end up with 586,752 bytes free, which seems OK for everything. Of course for me this was just a test scenario. In VirtualBox everyone would just use the native packet driver PCNTPK.COM. But nice to see it works. Thanks a lot!!

@Sébastien: Great to hear you got it up and running! :-) I would be interested to see your AUTOEXEC.BAT, FDCONFIG.SYS and SYSTEM.INI if this is okay with you. There are not many people in the world, I guess, who are using FreeDOS with network shims, so it would be nice to see how others do it and to learn from it. If it's too sensitive info or you don't have the time, just ignore it. :-)

Have fun
Ulrich

Sébastien FAVIER

2014-12-02 14:13:44 UTC

Permalink

Hello! :-)

@Ulrich:

I use this for install automaticly networks drivers for DOS (Dr-dos,MS-DOS, FreeDos..)
http://www.netbootdisk.com/about.htm

I have extracted UHA files for get content and batch source files and modify this
If you use FreeDos, (i have encounter problems), so, i use comfree interpreter with :

COMFREE.COM /E:10240

My FDCONFIG.SYS content :

DEVICE=\cpcdos\pilotes\dos\himemx.exe
SHELLHIGH=\COMFREE.COM /E:10240 /P=C:\FDAUTO.BAT
LASTDRIVE=z
DEVICE=\CPCDOS\PILOTES\DOS\IFSHLP.SYS
FILES=128
DEVICE=\CPCDOS\PILOTES\DOS\XMSDSK.EXE

rem DEVICE=\Cpcdos\pilotes\DOS\SMARTDRV.EXE /DOUBLE_BUFFER (bugs with some pc)

If you have any question, i'm here :-)

Rugxulo

2014-12-03 04:44:10 UTC

Permalink

Hi,

On Tue, Dec 2, 2014 at 8:13 AM, Sébastien FAVIER

Post by SÃ©bastien FAVIER
I use this for install automaticly networks drivers for DOS (Dr-dos,MS-DOS, FreeDos..)
http://www.netbootdisk.com/about.htm

"
Computer Requirements

* 16MB RAM [...probably for UHarc...]
* A supported network card/chipset [...sounds difficult...]
* An existing bootable disk made from Windows XP or PC-DOS 7 [...never
heard of FreeDOS ??...]
"

"2014 Note: I first started creating the NetBootDisk back in 2001 - in
the height of re-imaging many machines from DOS/Windows 98 to Windows
XP. Today I use more modern tools via PXE Booting - not to mention the
machines don't even have floppies any more! :)"

"UPDATE 2014 - The content below was originally published back in the
early Windows XP days before Windows PE was around. Personally I
wouldn't even bother using NetBootDisk for reading NTFS now, but I'll
still include these instructions anyway since I've already documented
it..."

I did download his (circa 2010) NETBOOT65.ZIP , which is apparently
supposed to let you roll your own image (for obvious reasons). Most of
the stuff is in FILES.UHA (presumably all the actual network packet
drivers).

It's been years since I've tried UHarc. Back in the day, it was quite
nice (but a very slow memory hog). I'm not really much into trying
various obscure compressors anymore, though I'd still lean more
towards 7zdecode or maybe a paq8 variant or zpaq or whatnot. And
obviously I'd (mostly) ignore MS-DOS/PC-DOS entirely in lieu of free-r
tools (if possible), e.g. FreeDOS.

It's commendable that someone has done this, but it's not what I'd
call ideal. In other words, although tedious, it could use some
obvious improvements, but I fear that testing on actual hardware would
be more trouble than it's worth. And if you're just going to use an
emulator anyways, it's probably not worth much effort (but see my
recent MetaDOS .img).

N.B. "Modern" OSes don't really cater to "old" machines, so it's of
little use to recommend them (via liveUSB or liveCD) if the machine
won't actually run it. Maybe without X11, but that's another
complicated ball of wax.