Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1119
  • Last Modified:

(Norton/Novell)32 bit packet driver

Hey.

Background :
Novell Netware 5.00 (SP1A) running Norton Ghost Multicast server (nwghsrv.nlm)

The problem is when i try to connect a client machine to the Multicast session running on the Netware server.

I've made a startup disk containing the .lan driver for the NIC.

***************************************************
The .bat file which starts it all looks like this :
***************************************************
SET NWLANGUAGE=ENGLISH
NIOS.EXE
LOAD NBIC32.NLM
LOAD LSLC32.NLM
LOAD CMSM.NLM
LOAD ETHERTSM.NLM
LOAD 3C5X9.LAN PORT=300 INT=5 LIST=ISA FRAME=ETHERNET_II MSB
LOAD TCPIP.NLM
LOAD TRANNTA.NLM
LOAD SRVLOC.NLM
LOAD CLIENT32.NLM
**********************************
The NET.CFG in use is like this :
**********************************
NetWare DOS Requester
      FILE CACHE LEVEL = 0
      FIRST NETWORK DRIVE = F
      NETWARE PROTOCOL = NDS BIND
        PREFERRED SERVER = 10.1.10.20
      NAME CONTEXT = "O=DISTRIBUTE"

Protocol TCPIP
      PATH TCP_CFG A:\CLIENT32
        BIND 3C5X9 1 ETHERNET_II NIC_1
      IF_CONFIGURATION DHCP LAN_NET
***************************************
Ok, so far so good, everything works.
I can log on to the Netware server (name = GHOST) with a user i have made (SKGHOST).
In SKGHOST's login script i wrote some
mappings + the command line :
#GHOST -clone,src=@MCtest,dst=1:1
-(this is the ghost startup command to join the multicast session "test" on the Netware Server)

Ok, when i log in and the login script executes this line it comes up with the following error :

ABORT: 20070, No Packet Driver Found - Multicasting not available

Help ? :)

Regards,
Loke

ps. Yes i am aware i can set it up using a DOS or Windows server as well, but i want it working on Novell.
0
Loke
Asked:
Loke
1 Solution
 
SysExpertCommented:
You need a apcket driver for your client NIC.
It should be on the NIC install floppy or available from the manufacturer.
See the pktdvr dir, normally on diskette 2.
There should also be instructions on how to use it.
If you have any more problems, let me know !!

--------------------------
                      3Com (R) Corporation
                     EtherDisk (R) Diskette for
                   The EtherLink 10 ISA NIC Family
                      Clarkson Packet Driver

The EtherLink 10 ISA family of NICs are all software configured.
When the packet driver is loaded the only required command line
parameter is the software interrupt value `PKT_INT_NUM.'  This
software interrupt is used for communication between the driver and
the protocol and should not be confused with the NIC's hardware
interrupt.  As of version 1.09 of the Packet Driver Specification
valid software interrupt values are in the range 0x60 to 0x80.

The packet driver for the EtherLink 10 ISA is a DOS mode driver that
does not support plug and play.  Plug and play must be disabled on the
EtherLink 10 ISA, and this can be done by running PNPDSABL.BAT from
the second diskette of the 6.1 driver set.

The packet driver for the EtherLink 10 ISA does not support auto-media
sensing.  The driver will default to the media programmed on the NIC.
The default is "Twisted Pair" when the adapter is shipped.  The NIC can
be forced to the appropriate media by running the configuration utility,
3C5X9CFG.EXE, from the second diskette.  Refer to the manual for
instructions on configuring the 3C509B NIC.

The SLOT and IOBASE parameters are to be used only when there is
more than one EtherLink 10 ISA board in the machine.  This parameter
indicates to the packet driver which NIC to use.  For NICs in ISA mode,
use the IOBASE parameter.  On Microchannel NICs, EISA NICs, or ISA NICs
in EISA mode, use the SLOT parameter.  You cannot use both IOBASE and
SLOT on the same command line.

EXAMPLE:  You have two EtherLink 10 ISA NICs in your machine.
One is installed at I/O Base 300 hex and the other at 320 hex.  To
use the card located at 300 hex and load it at software interrupt
60 hex for use in a Windows environment, use the command line:

        3C5X9PD -w 0x60 IOBASE=0x300

For a complete usage summary, enter 3C5X9PD at the DOS command prompt.


           (%VER PACKET.TXT - Packet Driver v6.1b)
0
 
LokeAuthor Commented:
Thanks, it worked.
The reason i posted this question was because i was loading 32-bit .lan drivers for the 3c509 nic.
And i thought i had to be using a packetdriver which ended in .lan (not .com which i thought was 16-bit).

Anyways, i contacted Russel Nelson at Crynwr Software and asked him if packet-drivers would work on both 32-bit and 16-bit (.lan and .dos .com), reply was that he didnt know, so i guess this is a matter of test and see basis.

Thanks again.

Regards,
Loke
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now