| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3714.1 | Problems here also. | SLOSS1::BREINHOLT_RO | Reb Breinholt | Wed Jul 17 1996 04:12 | 7 |
| I have also had this problem using the CD we received at our SE
training as well as the CD than came thru the regular SDC channels. I
have tried loading on Windows-95 and NT. I have not been able to find
a workaround.
Reb
|
| 3714.2 | use the 32 bit kit not 16bit | WRAFLC::WOODALL | MACRO is the best. | Wed Jul 17 1996 11:49 | 6 |
| I had the same problem. On close examination of the CD I was using, I
noticed that it was for Windows 3.x and NOT WIN-95 OR NT!!! Once I
got the 32 bit WIN-95/NT kit the installation went ok.
FRANK
|
| 3714.3 | Ah, that's the rub... | PTOJJD::DANZAK | | Wed Jul 17 1996 12:34 | 9 |
| @$)*&@#)*!&@*)!@)!#*!()#*()!#*!()~!
We all have Windows/95 on our laptops and we get a Windows/V3.1
distribution.
It's always the little things with these computers, infernal machines.
(grumble)
j
|
| 3714.4 | Are RMON Manager problems and ODBC failure related? | LEMAN::JRS | John SHADE - 'Attila the Nun' | Thu Jul 18 1996 15:23 | 31 |
| I'm running ClearVISN on NT Alpha with the FX!32 translator and it seems to
work fine - almost.
I also had the ODBC load failure at the 95% point - and I used the 32-bit kit,
not the 16-bit kit for Windows 3.x. I chose the "ignore" option, but I'm now
wondering whether the fact that I can't get the clearVISN RMON manager to run
properly is related.
Despite having a valid Packet Probe agent (Test works), clicking on any of the
icons (Upper: Protocol Manager/Traffic Monitor/Ring Monitor/Remote Login/Data
Capture/Domain Manager/Resource Manager; Lower: Alert Monitor/Protocol
Decode/Filter Editor/Domain Editor/clearVISN Shell) results in a launching
error (File not found).
There are no useful console messages. When I choose Traffic Monitor, the
following console message appears systematically prior to the launching error:
Installing configuration "dvinst.cfg" for agent "PacketProbe"...
Host Segment Short Long Packet
Domain Mode Stats History History Host Conversation Capture
----------------- ------ ------- ------- ------- ---- ---------------------
ALL MAC y y y y n n
IP NET y y y y n n
NOVELL NET y y y y n n
DECNET NET y y y y n n
The NSHOME environment variable is correctly defined as D:\clearVISN\PROBEW
Any ideas?
-John
|
| 3714.5 | The number you have reached is out of service | BSS::RIGGEN | | Fri Jul 19 1996 21:04 | 8 |
| Before leaving LKG I checked my CD and found that I was handed a
Windows 3.1 I quickly replaced it with a Win95 CD from the same box.
BTW what can we do about "good" customers on the Dist service that we
all told that CLEARVISN will be a WIN95 or WNT and we delivered a win
3.1 CD ?
Jeff
|
| 3714.6 | needs WIN95/NT cd | CSC64::CESARONE | Maria Bingham CSC Network Support DTN:592-4743 | Mon Jul 29 1996 22:47 | 37 |
| RE: .5
The CSC has been getting calls from Windows NT maintenance customers
who report the same problems as in .0 with installation. The CD
clearly has Windows 3.x on it. We were notified that the customer
needs to order another CD ROM for Win95/NT at an additional cost.
Although I could not explain to the customer (who is on maintenance
for Hubwatch on NT) why he would receive Clearvisn for Windows 3.x.
Perhaps product management could enlighten me.
-Maria
USCSC Network Support Team
**************
From: CSC32::D_PERRIN "Start every day with a smile and get it
over with."
To: @HUBS
CC:
Subj: hubwatch maintenance customers receiving win 3.x cdrom
From: NAC::FORREST 25-JUL-1996 15:28:41.75
To: CSC32::D_PERRIN
CC: DELNI::MCMILLIN,NM%CHEFS::HARDYG,MTS$::"sno::john koole"
Subj: RE: hubwatch maintenance customers
Dan, I'm happy to hear that so many customers have already gone to
Win95, although I didn't expect the number to be so high. I thought
they would put clearVISN on the same machine.
If they want Win 95 or NT on Intel, all they have to do is order
QA-5FVAB-H8, which is the CDROM. This number won't be active until
Aug 5th, however. It will cost $49, which I think is a bargain. The
license numbers they have will work with the new CDROM.
**************
|
| 3714.7 | Sounds like a mistake in packing the order | NAC::FORREST | | Wed Jul 31 1996 15:00 | 5 |
| We ordered all Win 95/NT CDROMs for the SE's. We didn't check what we
got from Manufacturing before handing them out. I'm checking into
the problem.
jack
|
| 3714.8 | all the CD's were W95/NT | NAC::FORREST | | Fri Aug 02 1996 17:47 | 12 |
| Upon further investigation, we believe that all of the CD's we gave out
at the SE and Sales forums were Win95/NT. Those who had the HUBwatch
subscription service did get the Win 3.1 CDROMs - that was intentional.
It was our belief that those customers were running HUBwatch on a V3.x
system, and we should not surprise them by forcing them to upgrade the
OS before they could upgrade the application. A letter was included
with the Win 3.x kits informing the user that this would be the last on
V3.x, so they now have several months to prepare for the OS change.
|