[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1895.0. "error at 1233 on IBM MicroChannel (MC) PC" by HACMAN::HACK (Don Hack, NIS) Mon Jan 16 1995 18:42

    I am having problem with HUBwatch v3.1 for Windows on an IBM PC with
    MicroChannel.
    
    The client selected HUBwatch and Network installation.
    During the installation, a window pops up with a messages like,
    NONFATAL ERROR AT SCRIPT LINE 1233.
    source file not found
    
    We get two (2) of these windows.
    
    I *think* PROTOCOL.INI does not exist.  When we try and start the PC,
    As PROTMAN gets loaded, there is a complaint about PROTOCOL.INI.  If I
    make up a very minimal file with just the name of the driver in it
    (IBMNEII$), the loading of Protman complains about bad parameters.
    
    Questions ...
    1) Is there a better explanation of this non-fatal error at line 1233?
    
    2) Any known problems running HUBwatch from micro-channel PC with our
       TCP/IP stack?
    
    Thanks for any help and/or pointers.
    
    -Don
T.RTitleUserPersonal
Name		DateLines
1895.1more informationHACMAN::HACKDon Hack, NISTue Jan 17 1995 14:388
    follow-up to .0
    
    Customer called and left me voicemail with the following information.
    They got Protman to load, then when loading the Microchannel
    driver, IBMNEII.DOS, STRTNDIS.BAT they got the following error ...
    
    INVALID DEVICE REQUEST READING DEVICE IBMENII$
1895.2Enter more info; ?NDIS driver?NETCAD::WAGNERCOFFILFri Jan 20 1995 16:1020
	Sounds like the same old, same old PROTOCOL.INI is not matching
	the settings required for the IBMENII$ driver. 

	If you could post the required drivers settings for the 
	Microchannel driver and then the PROTOCOL.INI. 
	You may want to check out the READ_ME.TXT, it has some 
 	troubleshooting tips for the "Other Type of Network Card" option.

	When you install with the HUBwatch network(which currently is
	PATHWORKS TCP/IP V5.1), you MUST supply a network driver and
	and PROTOCOL.INI location. As the READ_ME.TXT indicates for
	"Other drivers" not specified in the installation, YOU have to
	manually merge the HUBwatch included PROTOCOL.TMP with the 
	incomplete vendor supplied PROTOCOL.INI.
	It seems like you got to that point.

	There may be some specifics about using this driver. Is it a NDIS
	driver?

Barb