| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 734.1 | | MSE1::PCOTE | The plethora dilemma | Tue Jan 14 1997 11:01 | 12 |
| 734.2 | FX!32 - I hope we don't rely on it for SWCC client | CIVPR1::SIMMONS | Mike Simmons (301) 918-5597 | Thu Jan 30 1997 06:59 | 21 |
| FX!32 woes:
In my humble opinion, FX!32 is just too unstable/unpredictable for use on
a Cluster server. (Correct me if I'm wrong, but aren't most of the HSZ40/HSZ50
units used with Windows NT also a part of Digital Clusters for windows NT?) I
just re-installed Windows NT 4.0 after having FX!32 "hang" everytime during
startup. According the the FX32 notes conference, I can attribute this to
having the Network Monitor Agent installed.... Who woulda thunk it? Anyway,
with a fresh install of NT 4.0 SP2 and Clusters v1.1 FT (I know it's beta, but
works fine...), I installed FX!32 (I tried both v1.0 and v1.1 EFT) and then
SWCC client (& agent on the same machine). However, the subsystem view would
not show up! The way I finally got it to work was to deinstall and re-install
FX!32. (Go figure.) Now, I can only run SWCC in direct mode because now I
cannot connect to the agent. (I could before de-installing and re-installing
FX!32.) The saga continues...
It's gotta get better this!
I'm lucky that I'm doing this in the lab instead of at a customer site!
Is there a problem compiling Visual Basic code to run on Alpha?
|
| 734.3 | | MSE1::PCOTE | Rebuilt NT: 163, Rebuilt VMS:1 | Thu Jan 30 1997 13:45 | 19 |
|
Because of the problems you've noted, I still use Raid Manager on
Alpha and with NT4.0 SP2 on Intel.
NT4.0 SP2 breaks the SWCC client using the serial connection.
You'll notice a runtime error if you try the SCSI or Serial
connection.
There's simply too many issues with SWCC (V1.x) which makes it
unuseable. FX!32 V1.1 (which seems pretty slick) is NOT
supported on NT 3.51. FX!32 V1.0 has some interesting quirks
as you've noted. NT 4.0 SP2 breaks SWCC direct. And the list
goes on.
Use Raid Manager if you can. btw, Raid Manager seems to work
Ok with the HSZ50 although the documentation does state this
is not supported.
|
| 734.4 | Raid Manager is also buggy | AEOENG::16.40.240.154::annecy::lehy | | Fri Jan 31 1997 02:15 | 13 |
| > Use Raid Manager if you can. btw, Raid Manager seems to work
> Ok with the HSZ50 although the documentation does state this
> is not supported.
Raid Manager if you can ? Can we still sell Raid Manager for NT, and which
controllers/NT versions does it support. The behaviour of Raid Manager is
also not very satisfying on Alpha. I reported a pb in this notesfile which
is not yet solved. (the image just does not load because of an error in
CSTEXT.VBX). We tried with many different network copies of the kit, and
with regular (ordered) diskette kits.
Chris
|
| 734.5 | Microsoft acknowledges problem with SP2 | SSDEVO::MCSHANE | | Fri Jan 31 1997 17:06 | 8 |
| Microsoft has admitted to a bug with service pack 2 that breaks SWCC
V1.1 serial connect mode. The problem is with the OLEPRO32.DLL file. If
you load the old version, your problem will be resolved. We're working
with Microsoft on a fixing this. There should be a field blitz forth
coming.
SWCC 1.1b Client is not supported under Alpha WNT V4.0....yeah, I know
it works....We just never qual'ed it.
|
| 734.6 | Does it use FX!32? A pointer? | CIVPR1::SIMMONS | Mike Simmons (301) 918-5597 | Wed Feb 05 1997 13:36 | 4 |
| > SWCC 1.1b Client is not supported under Alpha WNT V4.0....yeah, I know
> it works....We just never qual'ed it.
Does SWCC v1.1b Client require FX!32? Is there a pointer to it?
|
| 734.7 | FX!32 needed for Alpha WNT V4.0 | SSDEVO::MCSHANE | | Wed Feb 05 1997 15:37 | 2 |
| If it was supported, yes...you need FX!32 on the Alpha WNT V4.0 system
to run SWCC V1.1b.
|