| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1909.1 | confirm if FDDI NIC is supported | ZPOVC::SINSPS | | Fri Jan 20 1995 06:17 | 6 |
| Hi,
Do we need to escalate this officially to get response ?
Our customer is breathing down our neck to get this fixed !
- LEH
|
| 1909.2 | Take advantage of the CSC support structure | NETCAD::BATTERSBY | | Fri Jan 20 1995 09:12 | 5 |
| If they are breathing that hard, (and perhaps aren't using
Listerine) :-), I'd escalate it. That way you will have the
full support of the resources and information of the CSC folks.
Bob
|
| 1909.3 | We're working on it | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jan 20 1995 09:23 | 14 |
| RE: .1
My God, it's only been one day since you're original posting! The notesfile
file is *NOT* the place to make time-critical requests. We (engineering) try to
get in here to reply to requests as often as possible. If you're not satisfied
with the response time in here, contact the product manager.
As for your problem with the DEFEA, I have asked the question of the appropriate
people. The response so far is that he seems to recall someone having a problem
but does not remember the exact situation or solution. Possibly something to do
with a parameter in PROTOCOL.INI. As soon as more detail is avaiable, a
response will be posted.
...Roger...
|
| 1909.4 | my appology for mistaken on date | ZPOVC::SINSPS | | Mon Jan 23 1995 01:07 | 15 |
| re .3
>My God, it's only been one day since you're original posting!
My appology. In my haste, I've mistaken the date of posting with
another one in September last year.
>Possibly something to do with a parameter in PROTOCOL.INI.
Appreciate your assistance. Perhaps you could post copy of a working
PROTOCOL.INI here ?
Thanks,
- LEH
|
| 1909.5 | One from a working system | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Jan 23 1995 13:28 | 31 |
| I have attached a copy of the PROTOCOL.INI file from a PC in our system test
area that has a DEFEA installed (and yes, HUBwatch runs fine). In addition,
here is the list of the relevant files and their dates.
>>> FILES <<<
protman.dos 13366 4/25/94 3:07:26pm
defea.dos 34443 9/23/93 9:32:08am
dllndis.exe 14627 7/28/94 3:35:04pm
netbind.com 8513 2/25/94 4:55:36pm
schk.exe 6782 6/28/94 9:43:42am
tcpip.exe 55467 7/27/94 4:50:42pm
tn.exe 52225 7/6/94 12:39:18pm
bapi.exe 28565 7/6/94 12:39:32pm
>>> PROTOCOL.INI <<<
[protocol manager]
DRIVERNAME = PROTMAN$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 14
SM_BUFFERS = 6
OUTSTANDING = 32
BINDINGS = DEFEA
DECPARM = C:\HUBWATCH\
;; NI_IRQ = 5
[DEFEA]
DRIVERNAME =DEFEA$
|
| 1909.6 | still same message | ZPOVC::SINSPS | | Tue Jan 24 1995 20:23 | 12 |
| re .5
Thanks for your fast response.
The customer have checked and verified their files to be similar as
yours. He had also tried with similar settings in PROTOCOL.INI but the
error message is still "NO RESPONSE FROM THE AGENT".
Any other ideas ? BTW, he is using DEC3002 FDDI card. Would that make
any difference ?
- LEH
|
| 1909.7 | System parameters, maybe? | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Jan 25 1995 07:20 | 7 |
| The only other thing I can think of is to check that the parameters in your
CONFIG.SYS and AUTOEXEC.BAT files are set to the minimum values specified in the
HUBwatch READ_ME.TXT file, specifically BUFFERS and FILES. For V3.1 there do no
appear to be any specific hints regarding the DEFEA but some of the minimum
parameter values for other cards may apply.
...Roger...
|
| 1909.8 | problem solved ! | ZPOVC::SINSPS | | Wed Jan 25 1995 21:47 | 11 |
| re .7
Hi Roger,
Although I've not spoke to the customer personally today but received
feedback from him that the problem has been solved !
Thank you very much for your effort and help. I supposed we've gain
another satisfised customer.
- LEH
|
| 1909.9 | Do tell ... | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Jan 26 1995 09:40 | 6 |
| That's great. Please tell us what the solution was for the benefit of those who
may encounter similar problems in the future. We're trying to accumulate and
write up such things in the "Hints on installing..." section of the READ_ME.TXT
file.
...Roger...
|
| 1909.10 | Certainly, once the answer is found | ZPOVC::SINSPS | | Thu Jan 26 1995 21:30 | 6 |
| re .9
I would once I'm able to talk to the customer personally. Since the
problem was solved, he may have went on vacation for couple of weeks.
- LEH
|
| 1909.11 | Good move | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jan 27 1995 08:45 | 5 |
| >> problem was solved, he may have went on vacation for couple of weeks.
That would have been my first reaction, too! :-)
...Roger...
|
| 1909.12 | re-run SETUP script solved ! | ZPOVC::SINSPS | | Thu Feb 09 1995 01:58 | 16 |
| re .11
Hi Roger,
I managed to speak to the customer today.
He mentioned that all he did was to run the SETUP script to let it
configure the PROTOCOL.INI file automatically.
Surprisingly, he claimed that it didn't worked when he tried to modify
the file manually as in my .6 reply. Does that sound possible ?
Otherwise, could there be other files that are taken care and modified
by the SETUP script ?
- LEH
|
| 1909.13 | Editiing PROTOCOL.INI is a black art | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Feb 09 1995 09:51 | 8 |
| Yeah, it's possible. The network config files are *VERY* picky about syntax.
One misplaced character and things just don't work. And, as your customer found
out, the error messages that appear when attempting to run a network application
are all but useless for helping to determine what is wrong/misconfigured.
I'm glad everything is working again.
...Roger...
|