| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1612.1 | Windows NT: Not supported. | SLINK::HOOD | I'd rather be at the Penobscot | Tue Oct 25 1994 09:53 | 8 |
| HUBwatch has never been officially run on Windows NT, nor has it ever
been officially tested to run on Windows NT.
If there's a need for HUBwatch for Windows NT, contact the product
manager, Jack NAC::Forrest.
Tom Hood
HUBwatch
|
| 1612.2 | Does it work with standard TCP/IP stack? | OSL09::OLAV | Do it in parallel! | Tue Oct 25 1994 10:42 | 3 |
| Does it work under Windows for Workgroups with Microsoft TCP/IP-32?
Olav
|
| 1612.3 | Works GREAT under NT V3.1 | WRAFLC::WOODALL | MACRO is the best. | Tue Oct 25 1994 12:34 | 12 |
| I am successfully running HUBWATCH X3.1.3 on WINDOWS-NT V3.1. I had to
boot dos/windows v3.1 and install hubwatch from there. Something about
the hubwatch install procedure couldn't handle WINDOWS-NT.
Once HUBWATCH was installed, it was easy to shutdown, reboot under NT,
manually create an ICON group and create the hubwatch entry.
Everything works great!
Frank Woodall
|
| 1612.4 | INSTALLIT does not run under Windows-NT | NETCAD::WAGNERCOFFIL | | Mon Oct 31 1994 11:25 | 5 |
| The version of INSTALLIT(the installation program for HUBwatch for
Windows) does not support Windows-NT. That is why you had problems
with the HUBwatch installation under NT.
Barb
|
| 1612.5 | Windows NT 3.5 revisited... | BIGUN::chmeee::Mayne | My TARDIS isn't big enough | Fri Feb 03 1995 00:04 | 5 |
| So, has anybody tried the installation under Windows NT 3.5 (Intel)? If it
doesn't work, does anyone have a workaraound? (Booting to DOS isn't a
workaround: this must be done entirely from Windows NT.)
PJDM
|
| 1612.6 | Just boot Win 3.1 to install it, then pointer in Win-NT | ROMEOS::HARRIS_MA | Sales Executive II | Mon Feb 06 1995 15:59 | 11 |
| I've been told that if you have Win-NT *AND* Windows V3.1 running on
the same machine (using dual-boot option for instance) then you can
boot into Windows V3.1 like regular and install Hubwatch, THEN
re-boot the machine to Win-NT and add an icon for the HUBwatch
application (since it was already installed). You can then disable
dual-boot option and run the whole thing from Windows-NT and never see
DOS and/or Win 3.1 again...
So I've been told.
Mark
|
| 1612.7 | | BIGUN::chmeee::Mayne | My TARDIS isn't big enough | Tue Apr 04 1995 05:22 | 13 |
| So, we installed HW on a Windows machine and copied the files to Windows NT.
Ran fine. So we then ZIPped up the files and took them to the customer's Windows
NT machine. Not only doesn't it run, it crashes the Win16 subsystem when it
attempts to start.
Please don't remind me that Hubwatch isn't supported on Windows NT. I know that.
Please don't remind me to write to the PM. I've done that.
Has anybody got even the faintest idea as to why Hubwatch is doing something as
drastic as crashing the Win16 subsystem on one machine, using the same files
that were copied from a Windows NT machine where it works fine?
PJDM
|