[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

2666.0. "Install errors on windows HW v4.0.1 how to get around known problems." by CSC32::B_LEWIS () Wed Aug 23 1995 11:41

I see there is a known bug on hubwatch 4.0.1 during the install the customer
is asked about modifying his config.sys
                             autoexec.bat 
                             win.ini

After answering the question with no or bypass or any other option available
we get the following error message window.

    Fatal error
    Fatal error at script line 1947
    to many added lines.

I see in the readme.txt in the hubwatch help it talks about the how shall we
handle window and so on having a problem but it doesn't say how to get sround
this problem and we have tried as mich as we can to get around the error message
and still the install fails with the same message.


Brad Lewis US/CSC

T.R	Title	User	Personal Name	Date	Lines
2666.1	Is the customer using HP OpenView???	NETCAD::WAGNERCOFFIL		`Mon Aug 28 1995 14:48`	24
	>> Fatal error >> Fatal error at script line 1947 >> to many added lines. This is occurring in the HP OpenView setup portion of the script installer (HUBW40.INF on diskette 1). The installation program Instalit has some bugs. In version 5.0 of HUBwatch for Windows, we will be using another installation package and there should not be any Fatal run-time script errors. If the customer does not use HP OpenView then comment this section out in the HUBW40.INF file. If the customer uses HP OpenView, you may have to perform the installation edits manually. You can comment out this section to install HUBwatch successfully, then uncomment the section and select Set up for HP OpenView from the HUBwatch for Windows installation main menu. If this fails, you will have to setup the HP OpenView integration edits manually. By looking at this HP OpenView section in HUBW40.INF, it should be fairly clear what the installation does automatically for you. Barb
2666.2	need more info asap	CSC32::D_PERRIN		`Wed Nov 15 1995 18:07`	8
	Well, I'm glad that this looks 'fairly clear' to somebody ;-) but it's not to me. I've got a customer installing 4.1.1 running into this problem. I've looked at the procedure in the .inf file, but without HP openview to test with, I do not trust that I'll give him the right commands. Can somebody put in here the gist of what manual editing needs to be done? Thanks
2666.3	Instalit bugs fixed - where?	CSC32::B_HAAS		`Tue Feb 04 1997 10:50`	11
	Reply .1 states: ... In version 5.0 of HUBwatch for Windows, we will be using another installation package and there should not be any Fatal run-time script errors. Since there is no V5.0 of HUBwatch, is this problem fixed in clearVISN? Thanks, Barbara
2666.4	A rose by any other name...	SLINK::HOOD	Your bad news bear	`Tue Feb 04 1997 12:07`	3
	> Since there is no V5.0 of HUBwatch, is this problem fixed in clearVISN? What was called HUBwatch is now called clearVISN MultiChassis Manager.