spacer
Service and Support - Platinum Support
tab end platinum support tab divider gold support divider my symantec divider log out navbar end
navbar end home news and alert archives platinum security center platinum knowledge base navbar end
spacer
Platinum Knowledge Base
choose a product

spacer
spacer

Rate This Document
1x3 spacer
1x1 spacer

print this documentDocument ID:2000022511014025
Last Modified:03/25/2002

Error: "Interrupt vector for Packet Driver not specifed in PROTOCOL.INI:" in Ghost Multicast Assist or Ghost Boot Wizard

Situation:While creating a boot disk for the Xircom CardBus Ethernet 10/100 Adapter NDIS v2.58 (990607), you see the message "Interrupt vector for Packet Driver not specified in PROTOCOL.INI:"

Solution:This problem appears to be caused by the configuration of NIC drivers, specifically the Protocol.ini file.

Configuring your NIC drivers is an advanced subject. Your best source of information for proper driver configuration is the documentation included with your NIC or information available from the NIC manufacturer. NIC manufacturers often include a Readme.txt file with the NIC drivers that has configuration instructions or have additional information available on their Web site. Consult this documentation for specific instructions regarding your particular NIC.

More information
Symantec provides the following information as an aid to NIC configuration. This information is a suggestion only and is not intended to replace information from your NIC manufacturer or from Microsoft.
  • The problem is sometimes caused by not including the file Protocol.ini in the list of driver files from which Ghost creates the boot disk. Verify that the folder for this NIC, located under the \Ghost\Templates folder, includes Protocol.ini.
  • The problem is sometimes caused by using a Protocol.ini that is empty. That is, if you edited Protocol.ini and removed all entries from it, you may see this message. Replace the file with a copy that has the default entries. You can obtain a fresh copy by reinstalling Ghost, or by downloading the appropriate driver files from the NIC manufacturer.
  • For at least one customer, this problem was resolved by editing the file Protocol.ini. Using the following entries might resolve the problem in your situation.

    ; Protocol.ini generated by Ghost Multicast Assist Wizard

    [protman]
    drivername=PROTMAN$

    [pktdrv]
    drivername=PKTDRV$
    bindings=XIRCOMNET
    intvec=0x60
    chainvec=0x66
    ; The following section contains information specific to your network card
    [XIRCOMNET]
    DRIVERNAME = XIRCOM$
    MEM=0xD200
    NOCHECK


print this documentDocument ID:2000022511014025
Last Modified:03/25/2002


rate this document
Does this document answer your question?
Yes
No
Maybe, need to test
None of the above
Is this document well written and easy to use?
Submit specific suggestions to improve the quality of this document.


Product(s): Symantec Ghost 7.0, Symantec Ghost 7.5, Norton Ghost 2003
Operating Systems(s): DOS, Windows 95, Windows 98, Windows ME, Windows NT, Windows 2000, Windows XP, Linux, Novell NetWare
Date Created: 02/25/2000

  © 1995-2014 Symantec Corporation. All rights reserved. feedback | legal notices | privacy policy