| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1702.1 | Probewatch 3.1 kit location | SNOC02::BOYLEBRENDAN | Brendan Boyle | Thu Nov 17 1994 18:47 | 8 |
| G'day Alphonse!!
The kit is in NAC::NIPG:[manage.rmon.windows], however, as far as I can
tell, there is no v3.1 user manual yet.
Later,
Brendan.
|
| 1702.2 | Licence for PROBEwatch V3.1?? | TRUCKS::EVANS_MA | It's all out there somewhere! | Fri Dec 02 1994 06:23 | 4 |
| Anybody like to comment whether this version needs a licence, given the
last kit licence exploded on 30-Nov??
Regards, Martin
|
| 1702.3 | Latest kit should not require a license | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Dec 02 1994 08:42 | 4 |
| According to Jack Forrest (PROBEwatch product manager) the kit on NAC does not require
a license.
...Roger...
|
| 1702.4 | More Info | CONSLT::BUZZELL | | Fri Dec 02 1994 16:51 | 8 |
|
Just to clarify this a bit. The PROBEwatch kit that is now
in NAC::NIPG:[manage.rmon.windows] installs automatically with
a non-expiring license. You should not be using or demoing the
NETscout version that was there initially.
|
| 1702.5 | online help update coming | NAC::FORREST | | Fri Dec 02 1994 20:18 | 1 |
| We will be updating online help only, not the manual.
|
| 1702.6 | no data in disk dirs?? | NEWOA::HARRISON | To be or not to be eligible? | Thu Dec 15 1994 06:44 | 23 |
| Correct me if I'm wrong but there is literally no data in the disk
directories for Probewatch for Windows???
yesAl$dir/siz NAC::NIPG:[manage.rmon.windows]
Directory NAC::NIPG:[MANAGE.RMON.WINDOWS]
DISK1.DIR;1 1
DISK2.DIR;1 1
DISK3.DIR;1 1
MANUAL.PTR;1 1
NOTICE.KIT;3 1
PROBE.PS;1 7853
QUIKSTRT.BAK;4 11
README.TXT;2 5
WIN10SPD.PS;1 97
Total of 9 files, 7971 blocks.
Can someone update me with another location for the 3.1 kit or upload
the disks again.
Thanks Al
|
| 1702.7 | I don't think the files left and came back... | NAC::FORREST | | Thu Dec 15 1994 10:35 | 6 |
| I just looked, and the files are still there. What you see by doing
the directory at the upper level is the file size of the directory
file, not the contents of the directory. If you
$ dir/siz NAC::NIPG:[manage.rmon.windows.disk1], you should see the
files in the disk1 subdirectory.
|
| 1702.8 | Problems Copying | ANGLIN::CLAYTON | Merlin Clayton DTN 445-7217 | Mon Jan 30 1995 17:16 | 15 |
| I'm having trouble preserving the respective disk IDs when I copy over the
network using a VMS
EXCHANGE/NETWORK/TRANSFER_MODE=BLOCK filename filename
command.
Disk 1 of the set loads ok, but when I get to disk 2, the install program
does not recognize the "disk2" diskid. Does anyone have any insight on this
glitch?
Thanks.
Merlin
|
| 1702.9 | Edit the file | NYOSS1::PLUNKETT | | Tue Jan 31 1995 10:55 | 8 |
| The disk.id file is a text file whose format should be readily
apparent. If you go into it with a text editor, and change the
number that the disk says it is to the number that it's supposed to
be, you can then continue with the install.
That's what worked for me.
-Craig
|
| 1702.10 | Disk label | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Feb 01 1995 20:26 | 9 |
| Or it might be that the disk label is incorrect. There's a way to
disable label checking from within the installation procedure, but it
may not have been put into the PROBEwatch installation script. I've
been bitten by that one before. Just use the File Manager's Disk ->
Label function to set the correct label on the diskette. The correct
label should be in the DISK.ID file. I don't know what it is for
PROBEwatch off the top of my head.
...Roger...
|
| 1702.11 | | CGOOA::PITULEY | Ain't technology wonderful? | Fri Mar 03 1995 11:11 | 10 |
| Has PROBEwatch 3.1 for Windows been officially released? The reason I ask
is that I ordered PROBEwatch for Windows for a customer and I got v1.0.
This seems quite ridiculous considering 3.1 has been on the net since
November 1994.
Brian Pituley
NPC, Calgary
|
| 1702.12 | it is ridiculous... | NAC::FORREST | | Mon Mar 13 1995 19:06 | 8 |
| No V3.1 never got released; by the time we finished Online help (which
Frontier didn't have), Frontier was almost ready to release V3.2. They
did not want to go back and change the V3.1 code to run Help, so we
had to wait for V3.2. We now have V3.2 and Help, and we are waiting for
Engineering cycles from the HUBwatch team to build the kit with the
network stack.
|