| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3700.1 | Some questions | NETCAD::FORINO | | Tue Jul 16 1996 11:32 | 17 |
| Two things:
1. Did you reboot your system after the clearVISN installation?
What platform are you running on - 95 or NT?
2. If you did reboot and are still having problems your
message indicates that the path to top level directory
that you installed clearVISN into is missing.
If on NT, look at your paths setting in the
Main => Control Panel => System
If on 95 ,look in the autoexec.bat file in the
top level directory of your boot drive.
John
|
| 3700.2 | Possible causes | STEVEV::VINGERHOET | | Tue Jul 16 1996 14:13 | 12 |
| Larry,
Before installing the official kit, I would manually delete any field
test kit you previously installed. This involves deleting the entire
'clearvis' directory and selecting the clearVISN program group and
deleting it.
If you have done this, could you please tell me if you experienced any
warnings or errors during the installation, such as DLLs not copying
correctly?
Steve
|
| 3700.3 | | IROCZ::MORRISON | Bob M. LKG1-3/A11 226-7570 | Tue Jul 16 1996 16:12 | 10 |
| I tried installing MCM BL X1.1.5 (from a ZIP file I copied over the network)
on a Win 95 PC that didn't have an earlier version of Hubwatch or MCM in place.
After several false starts, I got to the "real" installation, during which I
got a series of errors such as "Not enough disk space for system registry
file C:\Win95\system.dat." I had earlier selected drive D to install it on
because I don't have huge amounts of space on drive C. The process hung when
the "modifying files" process was 97% complete, and I had to reboot to get
un-hung.
I am posting this to show that .0 is not the only person having problems
installing these field test kits.
|
| 3700.4 | update to problem | TROOA::LWEBSTER | NIS, London, Canada | Mon Jul 29 1996 15:43 | 44 |
| Sorry for the delay...on vacation.
note .3 ... this was not FT software. CD distribution. Same as
customers would get.
HInoteCS475 was rebooted several times.
FT versions was deinstalled before install 3rd time.
Have found that HWCTL, HWMIFC and HWUTIL .dll files must be in the
\clrvisn\hubwatch directory to be found. Once I copied them
to this directory, Chasis manager works.
MDI.EXE never gets installed. I checked the Quarterdeck Cleansweep
installation monitor that I use, and that file was never added.
Ehandler, plus srmdb, lock, setupsup .dll files, have to
be installed in the \clrvisn\routerdb directory for the DeviceDB
to work correctly. These files, like the HW files mentioned above
were installed into the \clearvision directory.
Normally, I would say that this is a "dos path" problem, but the
path does not get modified by the installation procedure. My sets
seem OK (current "set" command displayed)
TMP=C:\WINDOWS\TEMP
winbootdir=C:\WINDOWS
COMSPEC=C:\COMMAND.COM
PROMPT=$p$g
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOS;C:\MOUSE
LMOUSE=C:\MOUSE
TEMP=C:\TEMP
AUTOBAHN=h:\clrvisn
WSAVERS=1.1
HUBWATCH_LOAD=h:\clrvisn\FIRMWARE
HUBWATCH_HUBLOADER=h:\clrvisn\HUBLOOAD
HUBWATCH_LIBRARY=h:\clrvisn\HUBWATCH\USERDATA
NSHOME=h:\clrvisn\PROBEW
HUBWATCH_SYSTEM=h:\clrvisn\HUBWATCH
NETRIDER_LIBRARY=h:\clrvisn\NETRIDER
windir=C:\WINDOWS
If you want to see the Cleansweep log, let me know.
-Larry
|
| 3700.5 | Win95 OS | TROOA::LWEBSTER | NIS, London, Canada | Mon Jul 29 1996 15:46 | 3 |
| Forgot to mention, this was installed on a Windows95.
-Larry
|
| 3700.6 | Win 3.1 vs. Win95/NT | TROOA::LWEBSTER | NIS, London, Canada | Mon Jul 29 1996 16:05 | 8 |
| Just read notes 3714 and 3716. Did see that there is a version
specific to Win95/NT.
But the installation manual, that comes with the WIN 3.1 CD, states
how to install on a Win95 OS. I would guess that this 16 bit app was
tested to install and operate correctly on the 32 bit OS.
-Larry
|