* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
This is some information on the subject:
STARTNET.BAT
The installation program creates a file called STARTNET.BAT in the target
directory you specified.
The file contains the following lines, which load the core NetWare Client
software:
SET NWLANGUAGE=preferred_language
C:\NetWare_Client_directory\LSL.COM
C:\NetWare_Client_directory\LAN_driver.COM
C:\NetWare_Client_directory\IPXODI.COM
C:\NetWare_Client_directory\VLM.EXE
NET.CFG
The installation program reads the existing NET.CFG file or creates a new
one if one does not exist in order to set a configuration for the network
board installed in your client workstation. Your old NET.CFG file is saved
as NET.BNW.
The following is an example of a NET.CFG file for a Novell® NE2000TM
Ethernet board:
LINK DRIVER NE2000
PORT 300
INT 3
FRAME ETHERNET_802.2
NETWARE DOS REQUESTER
NETWARE PROTOCOL = NDS BIND
FIRST NETWORK DRIVE = F
Because the NetWare DOS RequesterTM software is a redirector on the back
end of DOS, it requires that the LASTDRIVE=Z parameter be added to the
CONFIG.SYS file. The first network drive is now set in the NET.CFG file.
CONFIG.SYS
In previous client versions, the software set the first network drive after
the DOS LASTDRIVE setting in the CONFIG.SYS file. The current software
requires that the LASTDRIVE setting be set to drive Z:.
files=60 ( I prefer files=100)
Add or modify the LASTDRIVE=Z line at the end of the CONFIG.SYS file.
NOTE: If you are modifying the CONFIG.SYS file after running the
installation program, your original CONFIG.SYS file is saved as CONFIG.BNW
in the same directory. This happens only if you allowed the installation
program to modify your DOS configuration files.
STARTNET.BAT
1.Create a STARTNET.BAT file in the NetWare Client directory or modify the
existing STARTNET.BAT file.
The default is C:\NWCLIENT.
2.Add the necessary line to load the STARTNET.BAT in your AUTOEXEC.BAT file
or load the STARTNET.BAT file manually each time you want to connect to the
network or a server.
3.(Conditional) If you are running MS Windows for Workgroups 3.11, you must
add a line for the ODIHLP.EXE file.
IMPORTANT: Ensure that the ODIHLP.EXE file is loaded in the STARTNET.BAT
file after loading the transport protocol (The default the IPXODI.COM file).
If you currently load the ODIHLP.EXE file in the AUTOEXEC.BAT file, move the
line to the STARTNET.BAT file.
The STARTNET.BAT file should appear as follows. If you are creating a new
STARTNET.BAT file, add the following lines in the given order:
set nwlanguage=preferred_language
c:\client directory\lsl.com
c:\client directory\odi_lan_driver
c:\client directory\ipxodi.com
c:\MS Windows directory\odihlp.exe
c:\client directory\vlm.exe
NOTE: Include the line for the MS Windows directory only if you are running
MS Windows for Workgroup.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming!
The worlds best convention on networking
Brainshare is coming!
March 18 - 23, 2001
http://www.novellbrainshare.com/
"Bantha" <baddmatt...@tecinfo.com.invalid> wrote in message
news:0d5781d8...@usw-ex0106-048.remarq.com...
Contains a complete IPX boot disk.
Just replace the drivers with your network cards drivers and update the
net.cfg and startnet.bat to reflect the new drivers.
--
Mike Maynard
http://www.ccnyi.com
I finally found out how to do IPX with the NLMs (not VLMs or NETX)
instead of TCP/IP. I wanted 32-bit functionality with IPX, not 16-bit.
Some places I read said that it couldn't be done due to disk space
restrictions on 1.44 MB disk. I did it with room to spare. My
AUTOEXEC.BAT is:
@ECHO OFF
PROMPT $P$G
SET NWLANGUAGE=ENGLISH
NIOS.EXE
LOAD NBIC32.NLM
LOAD LSLC32.NLM
LOAD CMSM.NLM
LOAD ETHERTSM.NLM
LOAD 3C90X FRAME=ETHERNET_II
LOAD TCPIP.NLM
LOAD TRANNTA.NLM
LOAD SRVLOC.NLM
LOAD IPX.NLM
LOAD SPX_SKTS.NLM
LOAD CLIENT32.NLM
F:
LOGIN
So if anyone is interested in using IPX with NLMs instead of VLMs, this
is the command. Just remember to use NLMPACKR on IPX.NLM and
SPX_SKTS.NLM instead of TCPIP.NLM that the instructions tell you to.
I was going in the direction of getting you able to login first and then
attack the NLM issues.
Glad to hear that you've resolved the problem AND that you gave us the
feedback. Thanks.
8- )
-Barry. [Novell Support Connection SysOp]
> STARTNET.BAT
>
> The file contains the following lines, which load the core NetWare Client
> software:
>
> SET NWLANGUAGE=preferred_language
> C:\NetWare_Client_directory\LSL.COM
> C:\NetWare_Client_directory\LAN_driver.COM
> C:\NetWare_Client_directory\IPXODI.COM
> C:\NetWare_Client_directory\VLM.EXE
I find LSL.COM in the Client for DOS/Win 2.71 distribution, but where can I find
IPXODI.COM and VLM.EXE?
Same question for ODIHLP.EXE
Look at Mike Maynards site:
http://www.ccnyi.com/bootdisk.zip
Contains a complete IPX boot disk.
Just replace the drivers with your network cards drivers and update the
net.cfg and startnet.bat to reflect the new drivers.
--
Felton Green (SysOp)
Novell Support Connection
Brainshare is coming
Brainshare is COMING!
18 - 23 March 2001
http://www.novellbrainshare.com
http://www.chasetown.staffs.sch.uk/technical/novell/clients/clients.html
Download VLM121_1.EXE through VLM121_6.EXE. These are self-extracting
archives. Extract them all to a common directory, such as C:\VLMINST,
then run INSTALL.EXE from there.
This will get you the LSL, IPXODI, VLM, and ODIHLP files you seek.