|
Stephen,
You could do what the rest of us have done, create a FAT partition,
boot DOS and install Windows on this partition and then load the
HUBwatch s/w from inside the Windows program and then boot NT and all
will work.........or do as Tom says and chill til the V5 kit comes out.
Tis a tad strange though when you consider the "strategic" alliance we
have with MS and the number of OTHER platforms we can run HUBWATCH
under (like HPOV,etc)
Cheers
John
|
| Steve,
You know what they say about the word "assumed".
As experience increases, assumptions decrease.
I installed it, quite by chance, on Windows/NT/AXP and it worked fine.
The Software Product Description is a legal and binding document. Read
it, understand it. It is a contractual commitment which is for the
benefit of both Digital and the customer. It prevents us getting our
anatomy sued off for non-performance when very large users are
disappointed with features that they "assume" a product has.
Other notes in the file indicate that while it is NOT officially
supported under Windows/NT, it can work quite well. But if any serious
show-stopper issues show up - we can not remedy them unless they are on
a supported platform.
When you try to support software on a variety of platforms which are as
'standard' as the PC, the SPD becomes even MORE important!
Me, hell...I typically caution customers that "our direction is NT,
however we can run industrial-strength on Windows 3.11 today but you
can likely get it to work reasonably well under Windows/NT or 95. That
proviso usually satisfies the customers and they go happily along.
(Unless of course they want UNIX....which is another industry standard
story.)
So many standards, so little time...
ttfn,
j
^--who thought that Steve gave up unqualified superlatives for Lent..
|