[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
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 |
Hi,
I have one customer who is running hub watch 4.1.1 on Hp 486/@66 pc with 8 mb.
We are having DECSWITCH 900FE,DECrepeater90ts & DECrepeaters90t-16 (7nos).
DECrepeater90ts & DECreapters90 t-16 are configured in DECstack 90.We are
facing a peculiar problem when we try to connect DECstack 90 through hub
watch.When DECstack 90 is having one agent 90ts and 5 DECrepeater 90T-16
it takes 1 minute to display the pictorial view of stack on pc.When all
7 90T-16 along with agent 90TS are connected it takes 23 minutes to give
pictorial view on pc.Any suggestion to reduce this time lag are welcomed.
Pc is having following config.sys and autoexec.bat config files,
config.sys file
DEVICE=C:\DOS\HIMEM.SYS /testmem:off
DEVICE=C:\DOS\EMM386.EXE RAM
BUFFERS=15,0
FILES=8
DOS=UMB
LASTDRIVE=Z
FCBS=4,0
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
DOS=HIGH
STACKS=9,256
DEVICEHIGH /L:1,4560 =C:\WINDOWS\IFSHLP.SYS
rem COUNTRY=001,437,C:\DOS\COUNTRY.SYS
rem DEVICE=C:\DOS\DISPLAY.SYS CON=(EGA,,1)
rem DEVICE=C:\DOS\ansi.sys
autoexec.bat file
rem set HUBWATCH_HUBLOADER=C:\HUBLOAD
rem set HUBWATCH_LIBRARY=C:\HUBWATCH\USERDATA
C:\WINDOWS\net start
set pctcp=c:\pctcp\pctcp.ini
c:\pctcp\vxdinit.exe
set WSAVERS=1.1
@ECHO OFF
cls
LH /L:0;2,45456 /S C:\DOS\SMARTDRV /X 1024 2048
PROMPT $p$g
PATH C:\WINDOWS;C:\DOS;C:\MOUSE
set path=c:\pctcp;%path%
SET LMOUSE=C:\MOUSE
rem C:\MOUSE\MOUSE.EXE
SET TEMP=C:\TEMP
rem MODE CON CODEPAGE PREPARE=((437) C:\DOS\EGA.CPI)
rem MODE CON CODEPAGE SELECT=437
rem KEYB US,,C:\DOS\KEYBOARD.SYS
rem ***cd \windows
rem ***win
rem ***CALL C:\NET\bin\lanwp.bat
win
T.R | Title | User | Personal Name | Date | Lines |
---|
3107.1 | Two possible explanations | STEVEV::VINGERHOET | | Tue Jan 02 1996 10:42 | 6 |
| HUBwatch requires more memory for hubs/stack with large number of ports.
16 Meg is a more reasonable requirement.
You might also want to read the READ_ME.TXT file that ships with HUBwatch.
It mentions the fact that your FILES and BUFFERS parameters are probably way
too low.
|