| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1309.1 | Officially, unsupported. | SLINK::HOOD | I'd rather be at the Kennebec | Mon Aug 15 1994 15:49 | 6 |
| Whatever the answer...
Please remember that HUBwatch does not support NT at this time. There's no one
in the HUBwatch group running NT. And NT support is not scheduled at this time.
Tom Hood
|
| 1309.2 | yes, but I volunteer | CHELSY::WOODALL | MACRO is the best. | Mon Aug 15 1994 23:35 | 9 |
| yes, I know that. This is a internal system which happens to be
running NT. Since everything else up to this point runs fine under NT,
I was hopeful that HUBwatch and PROBEwatch would also.
I think they would actually run ok if I could get by the install
problem.
Do ya'll want an NT tester volunteer?
|
| 1309.3 | Perhaps we'll get an NT system soon? | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Aug 16 1994 10:42 | 12 |
| This is not an official HUBwatch answer (since I'm not a member of the HUBwatch
team), but I suspect if you would like to volunteer to test HUBwatch on NT that
would be great. The problem is that if you are encountering an error in the
installation procedure it may be difficult for HUBwatch engineering to fix it at
this time. A third-party tool is used to create the installation procedure. As
far as I know, the particular version of this tool that we currently use is
specifically for Windows. It does not claim to support NT (although there may
be a version that does). Since we have no systems running NT, there is no way
for us to figure out what's wrong with the installation procedure so we can
provide you with a fix.
...Roger...
|
| 1309.4 | yes, I'll still test | CHELSY::WOODALL | MACRO is the best. | Tue Aug 16 1994 16:57 | 11 |
| Roger,
As I said in my last reply, I do have an NT system and would be
happy to test the software for ya'll. I have 7 dechub900s here at this
site to "play" with.
I also understand that support would be strictly on an as possbile
basis. I can live with that. I just can't stand to go back to DOS
after using NT.
Frank
|
| 1309.5 | We don't have the NT Installation Builder | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Aug 16 1994 18:07 | 15 |
| I understand what you're saying, Frank, and it is appreciated. The problem is
that the HUBwatch development team does not have an NT system on which to
develop the installation procedure so that you can install and run HUBwatch. In
fact, the team does not even have the version of the installation build utility
that runs under NT. Since the existing HUBwatch kit was built for the Windows
environment, and since it appears (based on your test) that it will not install
on NT, there's not much more that we can tell you at this time except that the
installation was never tested on NT and it is not surprising that it doesn't
work. The problem is likely in the installation procedure itself (some sort of
Windows O/S call to determine free space that works under Windows and chokes
under NT). But there's no way for us to know exactly how to fix it since we
don't have the NT version of the tool. So basically we can't even give you a
suggestion on what to try next.
...Roger...
|
| 1309.6 | Try this | BUDDIE::KORNS | | Thu Aug 18 1994 00:23 | 8 |
| If you have a Windows client machine which can file share to the
Windows NT system (using say LAN Manager or PATHWORKS), you could
install HUBwatch on that machine and then drag the HUBwatch directories
up to the Windows NT machine and give it a go. That would at least
get you the kit unpacked and installed. You might have to configure
some things by hand, but it's worth a try.
Dave
|
| 1309.7 | I'll try it. | CHELSY::WOODALL | MACRO is the best. | Thu Aug 18 1994 10:24 | 3 |
| GREAT IDEA! I'll give it a try.
Frank
|