Hi all,
Xavier asks about network configuration with MS Client on
http://lazybrowndog.net/freedos
As it is a public question, I would like to forward this here. Perhaps
some of you have additional ideas or corrections? Thanks! :-)
---
8.01.2008 - 10:17:39
Hi Ulrich, Thanks for this nice and big doc. Until now I have been
using MS-DOS network client built from NT4 nressources. As I manage
almost 200 computers with different netcards I must use a 2-steps
procedure : disk1 = start MS-DOS (+ several utilities like ramdisk and
freedos-fdisk) and after disk2=start network client dedicated to the
lancard (so I had to build several different disk2, one for each
lancard-type, it was a very heavy procedure, generating several .ini
files that are almost un-understandable). In your doc you put
lancard-driver in the (fd)config.sys, that means while starting dos.
Do you have any idea about loading those drivers later like in my
procedure ? also my target is to create a full freedos procedure.
thanks in advance, [EMAIL PROTECTED]
---
Hi Xavier,
I first would like to mention: I am not a DOS network guru,
especially not with MS Client. I am just a technical writer /
journalist trying to be as accurate as I can. So here are just a few
thoughts:
1. Maybe you want to take a look at a solution Volker Rüddigkeit
describes at:
http://medien.bildung.hessen.de/support/techhilf/msclient
It is in german language - try with bablefish. He seems to do the same
task with one disk. He has different disks for different network cards
for download.
2. If you start MS Client the way described in the documentation
(Protman and driver in (fd)config.sys) you have to determine the
network driver at boot. I think in your situation it would be better
to only load the Installable File System Helper driver IFSHLP.SYS in
(fd)config.sys.
The network card is then only determined in PROTOCOL.INI (Line
DriverName in the section of the netcard) and in SYSTEM.INI. These
files are read when the binding / net.exe is started.
The binding of driver and protocol (by starting NETBIND.COM or
NET.EXE) is done in a batchfile. Normally this is AUTOEXEC.BAT but it
also can be some other *.BAT.
So just an idea:
Maybe you take a look at a free tool called INIFILE.COM which allows
you to manipulate ini files from a batch file. It can be downloaded here:
http://home.mnet-online.de/horst.muc/wbat32.htm#inifile
This means you can paste the appropriate driver into the correct place
in SYSTEM.INI and PROTOCOL.INI before you bind it. For example:
INIFILE.COM C:\NET\PROTOCOL.INI [NETCARD] DriverName=EL3C574$
INIFILE.COM C:\NET\SYSTEM.INI [network drivers] netcard=EL3C574.DOS
C:\NET\NET START
The advantage of doing this in a batchfile would be to be able to use
IF conditions, to present choices etc. If it would be possible to
detect a netcard by some procedure you even might be able to load the
correct driver automatically.
3. Ask the people who are doing bootdisks, for instance at:
http://www.nu2.nu/bootdisk/network/
http://drivesnapshot.de/en/index.htm
http://www.netbootdisk.com/
Good luck!
Ulrich Hansen
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
