[Freedos-user] Connecting FreeDOS to a SMB share

[Santiago Almenara]

Hi!

I have set up my FreeDOS PC and everthing is working just fine except for
the audio (ok I pray to God someday there will be a way to play DOS games
with sound under plain DOS)

Now I want to connect this PC to a Windows/SMB share to speed the file
transfer. Right now, I have to burn a CDRW in one machine and use it in the
FreeDOS PC.

What I think I need in my DOS PC:
1. A network card (duh!)
2. A driver for the card
3. A packet driver for the card
4. mTCP (for DHCP)
5. some software to connect the DOS to SMB.

1. My laptop has 2 network interfaces:
- Broadcom BCM401 10/100
- Intel Wireless 3945 a/b/g

For now, I will discard the wireless option, I'll stick to the wired option.

2. In the Broadcom site, there are 3 DOS drivers for the Broadcom BCM401
10/100: NDIS2, 16 ODI, 32 ODI.
Reading in the web, ODI is for Netware and Apple. NDIS2 is for Microsoft
networks. What do I need? Or I need a fourth option specific for FreeDOS?

3. I think a packet driver is the same than the network driver, please help
here.

4. mTCP seems to be easy to configure.

5. Finally what package do I need to connect the FreeDOS to a SMB share
(assuming all previos steps are working fine). I can read the docs, but I
have to know what package to look and investigate.

Thanks for your help.

Santiago

[m***@brutman.com]

I appreciate the interest in mTCP, but there is a limitation you need
to be aware of.

The mTCP DHCP client is designed for the mTCP applications. You can
use it and adapt it to do other things, but you will have to write
some scripts or code to take the output from the DHCP client (a text
file) and make it usable for whatever app you had in mind.

For example, if you liked my DHCP client and wanted to use it with
WATTCP applications, you would have to run my DHCP client, extract the
IP addresses that you need from the MTCPCFG file, and then put them in
the WATTCP config file.

I don't know what it takes to make it usable for something like the MS
SMB client - it can probably be done/adapted, but it's not something I
thought about and I don't expect it to work 'out of the box'. It only
works out of the box with the other mTCP applications.


Mike

[Eric Auer]

Hi!

Post by Santiago Almenara
1. A network card (duh!)
2. A driver for the card
3. A packet driver for the card
4. mTCP (for DHCP)
5. some software to connect the DOS to SMB.
- Broadcom BCM401 10/100
- Intel Wireless 3945 a/b/g
For now, I will discard the wireless option, I'll stick to the wired option.

Exactly.

Post by Santiago Almenara
2. In the Broadcom site, there are 3 DOS drivers for the Broadcom BCM401

You can also try http://www.crynwr.com/drivers/00index.html
but I do not really see Broadcom there...

Post by Santiago Almenara
10/100: NDIS2, 16 ODI, 32 ODI.

NDIS and ODI are more high level. Depending on your app, you
simply need a low level packet driver. However, there are
also wrappers to turn one into the other as far as I remember.

Post by Santiago Almenara
Reading in the web, ODI is for Netware and Apple. NDIS2 is for Microsoft
networks. What do I need? Or I need a fourth option specific for FreeDOS?

See above, but better, see:

http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS
(formerly known as lazybrowndog.net/freedos/ :-))

Post by Santiago Almenara
3. I think a packet driver is the same than the network driver,
please help here.

See the page above :-)

Post by Santiago Almenara
4. mTCP seems to be easy to configure.

Maybe, but in DOS, networking is not a global operating system
thing. Instead, it is something done by one or more libraries
used by your network related software. For example your Arachne
web browser might use WATTCP, while your FTP client might use
MTCP instead. Both have separate configuration mechanisms. Of
course both can still access the same packet driver though :-)

Post by Santiago Almenara
5. Finally what package do I need to connect the FreeDOS to a SMB share
(assuming all previos steps are working fine). I can read the docs, but I
have to know what package to look and investigate.

There are basically two options: MSCLIENT, free by MS but very
old and using a lot of RAM. On the other hand, sources like the
FreeDOS Wiki / Lazybrowndog / FreeDOS FAQ etc etc have lots of
information on how to get MSCLIENT to work. The other option is
the DOS version of the Linux SAMBA smbclient. This works like a
command line FTP client / shell, so you type commands to go to
the files that you want and to upload and download them, all IN
the smbclient shell. Your SMB share does not get any DOS drive
letter that way and you cannot use it from, say, EDIT that way.

Of course SAMBA also can help you to mount drives in Linux, but
because this works completely different in DOS, it would be hard
to port, compared to porting smbclient which just needs basic C
library services and a networking library and packet drivers :-)

Eric

[Mike Eriksen]

Post by Santiago Almenara
Hi!
I have set up my FreeDOS PC and everthing is working just fine except for
the audio (ok I pray to God someday there will be a way to play DOS games
with sound under plain DOS)
Now I want to connect this PC to a Windows/SMB share to speed the file
transfer. Right now, I have to burn a CDRW in one machine and use it in the
FreeDOS PC.
1. A network card (duh!)
2. A driver for the card
3. A packet driver for the card
4. mTCP (for DHCP)
5. some software to connect the DOS to SMB.

IMHO, not quite so. 2 and 3 is one point, If you can't get a packet
driver for your NIC, you are forced to fight with NIDIS 2. Have fun...
Ad 5) Well, depends... Windows for Workgroups ( and the DOS add-on
"DOS for Workgroups") originally worked through the NETBEUI protocol,
not TCP.

[Santiago Almenara]

Post by Mike Eriksen

Post by Santiago Almenara
Hi!
I have set up my FreeDOS PC and everthing is working just fine except for
the audio (ok I pray to God someday there will be a way to play DOS games
with sound under plain DOS)
Now I want to connect this PC to a Windows/SMB share to speed the file
transfer. Right now, I have to burn a CDRW in one machine and use it in

the

Post by Santiago Almenara
FreeDOS PC.
1. A network card (duh!)
2. A driver for the card
3. A packet driver for the card
4. mTCP (for DHCP)
5. some software to connect the DOS to SMB.

IMHO, not quite so. 2 and 3 is one point, If you can't get a packet
driver for your NIC, you are forced to fight with NIDIS 2. Have fun...
Ad 5) Well, depends... Windows for Workgroups ( and the DOS add-on
"DOS for Workgroups") originally worked through the NETBEUI protocol,

[Eric Auer]

Hi Santiago,

Update: I installed easily the NDIS2 drivers for my card, then the packet
driver wrapper. mTCP is working perfectly.
Right now, I am trying TCP's MS CLIENT 3.0 to connect to the SMB share
through TCP/IP.

Nice! Maybe you could email a summary of how you did it?
I mean what you installed and which config files you had
to edit in which way to make MTCP work via NDIS etc :-)

The SMB share is actually a Dlink NAS, I can use NFS too, but I have to
install some modules before. I'll try a little more for SMB and then try
NFS.

Interesting. I assume you can also access the NAS via FTP or even HTTP?
Samba sounds okay for me, but of course the choice between MSCLIENT and
the ported Linux Samba command line tool smbclient is not that big :-)

Eric

[m***@brutman.com]

Post by Eric Auer
Hi Santiago,

Update: I installed easily the NDIS2 drivers for my card, then the packet
driver wrapper. mTCP is working perfectly.
Right now, I am trying TCP's MS CLIENT 3.0 to connect to the SMB share
through TCP/IP.

Nice! Maybe you could email a summary of how you did it?
I mean what you installed and which config files you had
to edit in which way to make MTCP work via NDIS etc :-)

I second that motion - I've never used NDIS and a "shim" before and
I'd like to see how that is done.

Post by Eric Auer

The SMB share is actually a Dlink NAS, I can use NFS too, but I have to
install some modules before. I'll try a little more for SMB and then try
NFS.

Interesting. I assume you can also access the NAS via FTP or even HTTP?
Samba sounds okay for me, but of course the choice between MSCLIENT and
the ported Linux Samba command line tool smbclient is not that big :-)
Eric

If most NAS boxes do HTTP, is this the reason/motivation I need to get
wget done?


Mike

[c***@aol.com]

With all the discussion on mTCP it seems this package is getting a lot of attention.

Is there any update as to when we might be able to get source or even just a binary library?










-----Original Message-----
From: mbbrutman <***@brutman.com>
To: freedos-user <freedos-***@lists.sourceforge.net>
Sent: Mon, Jan 17, 2011 2:31 pm
Subject: Re: [Freedos-user] Connecting FreeDOS to a SMB share

Post by Eric Auer
Hi Santiago,

Update: I installed easily the NDIS2 drivers for my card, then the packet
driver wrapper. mTCP is working perfectly.
Right now, I am trying TCP's MS CLIENT 3.0 to connect to the SMB share
through TCP/IP.

Nice! Maybe you could email a summary of how you did it?
I mean what you installed and which config files you had
to edit in which way to make MTCP work via NDIS etc :-)

I second that motion - I've never used NDIS and a "shim" before and

I'd like to see how that is done.

Post by Eric Auer

The SMB share is actually a Dlink NAS, I can use NFS too, but I have to
install some modules before. I'll try a little more for SMB and then try
NFS.

Interesting. I assume you can also access the NAS via FTP or even HTTP?
Samba sounds okay for me, but of course the choice between MSCLIENT and
the ported Linux Samba command line tool smbclient is not that big :-)
Eric

If most NAS boxes do HTTP, is this the reason/motivation I need to get

wget done?





Mike





------------------------------------------------------------------------------

Protect Your Site and Customers from Malware Attacks

Learn about various malware tactics and how to avoid them. Understand

malware threats, the impact they can have on your business, and how you

can protect your company and customers by using code signing.

http://p.sf.net/sfu/oracle-sfdevnl

_______________________________________________

Freedos-user mailing list

Freedos-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/freedos-user

[m***@brutman.com]

Post by c***@aol.com
With all the discussion on mTCP it seems this package is getting a lot of attention.
Is there any update as to when we might be able to get source or
even just a binary library?

Short story - working on it.

Longer story .. it's all my original code and I have copyright to it.
However, the large corporation that pays me insists on approving any
open source contributions. (Which is reasonable.) So you can imagine
the look on people's faces when I said "I want to start a new open
source project, for DOS." I seriously don't think they know what to
do. :-)

A binary library is possible and I originally started down that path,
but it makes more sense to just have people include the original
source code and directly compile and link in everything they need.
Otherwise they wind up dealing with whatever compromises were compiled
into the library.

It is all evolving as I learn ..


Mike

[Mike Eriksen]

[CUT]

Post by m***@brutman.com
If most NAS boxes do HTTP, is this the reason/motivation I need to get
wget done?

+1!

Mike

[Santiago Almenara]

Post by Santiago Almenara

Post by Eric Auer
Hi Santiago,

Update: I installed easily the NDIS2 drivers for my card, then the

packet

Post by Eric Auer

driver wrapper. mTCP is working perfectly.
Right now, I am trying TCP's MS CLIENT 3.0 to connect to the SMB share
through TCP/IP.

Nice! Maybe you could email a summary of how you did it?
I mean what you installed and which config files you had
to edit in which way to make MTCP work via NDIS etc :-)

I second that motion - I've never used NDIS and a "shim" before and
I'd like to see how that is done.

I am sorry I can answer just now. The shim was so easy to configure, I
followed the howto in the sourceforge FreeDOS networking page.

(FD)CONFIG.SYS:
DEVICEHIGH=C:\NET\PROTMAN.DOS /I:C:\NET
DEVICEHIGH=C:\NET\B44.DOS
DEVICEHIGH=C:\NET\DIS_PKT.DOS
;devicehigh=C:\NET\ifshlp.sys

B44.DOS is the NDIS2 driver for my ethernet card, PROTMAN.DOS is part of the
MS-DOS Addon for workgroup and DIS_PKT.DOS comes with FreeDOS. I comment the
ifshlp.sys because I am not completely sure what it is for. I think it is
something for DOS networking, not sure, though.

AUTOEXEC.BAT:
C:\NET\netbind.com
C:\MTCP\DHCP.EXE

PROTOCOL.INI:
[protman]
DriverName=PROTMAN$

[B44]
DriverName = B44$

[PKTDRV]
drivername=PKTDRV$
binding=B44
intvec=0x60
chainvec=0x68

It just works, so easy!


Santiago

[c***@aol.com]

The discussion about TUNZ got me thinking about the ARC file format.

There are several of the old shareware utilities out on the internet - ARCE, ARC-E, PKXARC ..
but are there any available which are GPL or close to GPL? (For DOS, of course!)

Poking around I noticed that Vernon Buerg passed away a year or so ago.

It seems like a lot of shareware will wind up dying with their authors due to licensing issues.

I wonder if shareware authors or their heirs are willing to open up their software licensing after death

Dave

[Rugxulo]

[dos386]

COOL :-)

Nevertheless, I'll stay with just ZIP and 7-ZIP (both possibly
containing a TAR).
I don't need 1'000'000'000'000 archive formats.

[Rugxulo]

Hi,

Post by dos386
COOL :-)
Nevertheless, I'll stay with just ZIP and 7-ZIP (both possibly
containing a TAR).
I don't need 1'000'000'000'000 archive formats.

Nobody needs more than a few, but there are still a ton of old .ARC
files out there. And since you brought it up again, I re-searched (and
found) the unpacker I was thinking about.

I actually emailed the author a handful of years ago (on my other
account), and he'd pretty much forgotten about it (no surprise, it's
been 20+ years). And I never properly learned Forth, so I have no idea
which dialect would be most compatible with this, and I never tried
too hard to build it (source only). IIRC, he did say he probably used
LMI, but that's an old commercial one. And it's in "block file" format
(16x64). :-))

First get an .ARC unpacker (w/ TP src):

http://www.vectorbd.com/bfd/pascal/dearc40.lzh

Then get this converter:

ftp://ftp.taygeta.com/pub/forth/Archive/ibm/blktofth.arc

BTW, you can get an .ARC (and others) lister tool here (w/ .ASM src):

http://sta.c64.org/arclds.zip

Listing archive: blktofth.arc

Original Packed Ratio Date Time Attr Name
--------- --------- ---- -------- -------- ----- ------------------------------
12324 12025 97% 04-15-86 11:11:12 BLKTOFTH.COM
2362 1105 46% 03-11-86 10:43:34 BLKTOFTH.PAS
--------- --------- ---- -------- -------- ----- ------------------------------
14686 13130 89% 04-15-86 11:11:12 2 files

You can use "BLKTOFTH" to convert to normal text format.

ftp://ftp.taygeta.com/pub/forth/Archive/ibm/rdarc.arc

Listing archive: rdarc.arc

Original Packed Ratio Date Time Attr Name
--------- --------- ---- -------- -------- ----- ------------------------------
45056 5829 12% 09-09-88 19:11:06 READARC.SCR
--------- --------- ---- -------- -------- ----- ------------------------------
45056 5829 12% 09-09-88 19:11:06 1 file

URUNARC 03:08 09/09/88, Written by Kevin L. Pauba

Don't be fooled by the "READARC" name, it can allegedly unpack
(unstore, unsquash, uncrunch). And clearly .ARC packs Forth block
files extremely well.

Post by dos386
The other was written in ancient (LMI?) Forth (on Taygeta FTP archive
somewhere), so I never tested it. (They had a lot of old .ARC files,
not many others still do.)

[unknown]

Hi,

Post by c***@aol.com
The discussion about TUNZ got me thinking about the ARC file format.
There are several of the old shareware utilities out on the internet - ARCE,
ARC-E, PKXARC ..
but are there any available which are GPL or close to GPL? (For DOS, of
course!)

The unpacker I used (occasionally) in recent times was DEARC, mostly
3.1 (w/ TP src) though someone unofficially might have updated it for
TP4 (DEARC40).

http://www.vectorbd.com/bfd/pascal/dearc40.lzh

The other was written in ancient (LMI?) Forth (on Taygeta FTP archive
somewhere), so I never tested it. (They had a lot of old .ARC files,
not many others still do.) Okay, well, here's a different one (oddly),
but interesting at least:

ftp://ftp.taygeta.com/pub/forth/Archive/talk/unarc_2.txt
ftp://ftp.taygeta.com/pub/forth/Archive/talk/unarc2.scr

A quick search also reveals:

http://en.wikipedia.org/wiki/ARC_(file_format)

ftp://ftp.ibiblio.org/pub/Linux/utils/compress/nomarch-1.4.tar.gz
http://sourceforge.net/projects/arc/

Can't find Thom's statement, but I'm pretty sure he said "personal"
use of ARC (without registering) was okay. But take that with a grain
of salt.

ftp://ftp.sac.sk/pub/sac/pack/arc602.exe

Post by c***@aol.com
Poking around I noticed that Vernon Buerg passed away a year or so ago.

His ARCE seemed to (mostly) work, and it was very very small too.

ftp://ftp.sac.sk/pub/sac/pack/arce41a.zip

Post by c***@aol.com
It seems like a lot of shareware will wind up dying with their authors due
to licensing issues.

(I think?) U.S. Copyright is 70 years after author's death. :-/

Post by c***@aol.com
I wonder if shareware authors or their heirs are willing to open up their
software licensing after death

Probably not. Clearly copyright law is in need of reform for software,
but nobody's bothered to do it.