[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
2856.0. "Hubloader doesn't work after I installed the latest Hubwatch kit on my PC" by GIDDAY::STANISLAUS () Thu Oct 12 1995 21:53
Hubloader used to work fine on my PC with Hubwatch version 4.0.1 kit.
After installing the latest Hubwatch v 4.1 which has Hubloader v1.1.0, hubloader
doesn't work anymore. When you do a load, you don't see the transfer count go up
on the Netrider Loader window although the TFTP server says running. I tried
load the MAM module and I tried loading a PEswitch same problem.
On the Hubloader window it says READING FILE INTO LANDING PAD
as though everything is working fine. But because the transfer count is not
going up on the TFTP server window and because the module is at the same
revsion as before, I can tell that the load did not work.
Alphonse
T.R | Title | User | Personal Name | Date | Lines |
---|
2856.1 | | STRWRS::KOCH_P | It never hurts to ask... | Fri Oct 13 1995 00:03 | 3 |
|
Well, did you make sure that no IP addresses changed? Is the correct IP
address for your station in TFTP field of HUBloader?
|
2856.2 | Yes IP address was the problem | GIDDAY::STANISLAUS | | Wed Oct 18 1995 03:50 | 10 |
|
The same time I installed the latest DCF my PC IP address was changed
from 16.153.32.102 to 16.153.32.201.
The info under device data for TFTP server was wrong was .201 instead
of .102.
Thanks
Alphonse
|