Conference netcad::hub_mgnt

1334.0. "3C509 made me dizzy !" by ZPOVC::DAIV02::DANIEL_H (Digital Astra Nusantara) Mon Aug 22 1994 23:05

    Hi all,
    
    I got trouble with 3C509 card (UETP transceiver). My customer used
    Hubwatch for Windows V2.0 to manage DECHub ONE.
    The problem is, when strtndis.bat run schk then come up error :
    
    SCH0011 : No NDIS Interrupt Activity. Maybe NI_IRQ set wrong or cable
              not attached or hardware/DLL broken.
    
    Situation that made me very confused is, sometimes it work but some-
    times it won't. It is very intermittenly. In Protocol.ini I put this :
    
    [protocol manager]
    DRIVERNAME  = PROTMAN$
 
[DATALINK]
    DRIVERNAME  = DLL$MAC
    LG_BUFFERS  = 14
    SM_BUFFERS  = 6
    OUTSTANDING = 32
    BINDINGS    = elnk3.dos
    DECPARM     = C:\HUBWATCH\
 
[ethernet 16] 
    DRIVERNAME = elnk3$
    DriverName = elnk3$


In Strtndis.bat file :

@echo off
C:
cd \HUBWATCH

if %path% == "" goto no_path
	path >c:\HUBWATCH\oldpath.bat
	goto path_done
:no_path
	echo set path=>c:\HUBWATCH\oldpath.bat
:path_done
	set OLDPCSA=%PCSA%
	set PCSA=C:\HUBWATCH
	SET PATH=%PCSA%;%PATH%
save
ld c:\hubwatch\protman.dos /i:C:\HUBWATCH

REM Choose the proper NDIS driver for your network card.
REM Refer to your NDIS driver documentation for details.
REM Uncomment only one of the following, or add a line to
REM ld the driver for your network card

REM Choose the next line for the etherwork III network card
REM ld ewrk3.dos

REM Choose the next line for the etherwork (depca) network card
REM ld depca.dos

ld elnk3.dos


dllndis
netbind
schk
tcpip
    
    I already tried to change with another card but still same. I
    tried to change the IRQ (def is 10) but still failed. Tried to
    reinstall the Hubwatch, no effect. My God, what's wrong ?
    
    I do appreciate any reply. Thank's a lot in advanced.
    
    
    Rgds,
    
    Dnl

    

    I had a similar problem and found that using a switch when starting the
    Scheduler solved the problem. I think it was a /n but I wouldn't swear
    to it.
    
    Dennis Faust
    

In your PROTOCOL.INI file you might try the following:

* Replace the line "[ethernet 16]" with "[elnk3.dos]"
 
* I'm not sure why there are two occurrences of the DRIVERNAME directive under
  your [ethernet 16] label although it shouldn't hurt anything.

* Add the following line under the [DATALINK] section:

  NI_IRQ = 10

...Roger...