T.R | Title | User | Personal Name | Date | Lines |
---|
595.1 | Not firmware image | MSBCS::KALKUNTE | Ram Kalkunte BXB1-1/D3 | Thu Jun 04 1992 11:31 | 4 |
| Why have you booted minimum ? I don't have a problem using NDU when
booted normally. I don't think it is a problem with the firmware image.
Contact Maureen PROXY::JEAN for help. I don't know if she reads this
notesfile.
|
595.2 | just guessing | COMICS::REYNOLDSJ | Mad Dogs and Englishmen | Thu Jun 04 1992 13:51 | 8 |
| I was working with Kevin on this problem. We tried the load under a
normal boot and got the failure, so then tried a minimum boot to simplify
the problem.
I have got this to work before on a 6000 (after getting the same error
due to the UPDATE switch not being set!) but can't see what the problem
could be here.
John Reynolds.
|
595.3 | need some info | PROXY::JEAN | MAUREEN JEAN | Thu Jun 11 1992 12:23 | 11 |
|
Can you let me know what version of VMS and what version of the fxdriver you
have? I don't believe that your .sys file is bad but if you want to verify it,
send mail to me and I will give you a pointer to DEMFA013.sys.
Just FYI, you also want to use the /reset qualifier on your command line.
If you don't, the update will not take affect until the adapter is re- inited.
Maureen
|
595.4 | Still a problem. | PTOECA::MCELWEE | Opponent of Oppression | Thu Oct 15 1992 12:21 | 16 |
| I recently encountered the DEVICE REQUEST ERROR when updating a
DEMFA. The update completed when the DEMFA was initialized upon system
reboot, as a subsequent $DOWNLOAD SHOW DEVICE FXA0 reported the new
version.
Environment: VAX 6530, VMS 5.5-1, FXDRIVER X-16 (link date
12-Oct-91), DEMFA014 update, NDU012 kit.
BTW, there were problems with the KITINSTAL procedures for DEMFA014
plus a bogus filename in the DEMFA014 save set. The high version limit
for VMS was 5.3; this prevented it from installing on 5.5-1. Also, the
NDU012 kit has an incorrect directory and filespec for the executble
in the .CLU file. This causes the DCL command verb DOWNLOAD to fail.
Both of these kits were obtained from the CSC. They have been notified.
Phil
|
595.5 | | CSC32::B_GOODWIN | Time is an illusion... | Thu Oct 15 1992 16:02 | 9 |
| Phil,
I tried to update the DEMFA014 kit that we have so it would not fail with the
VMS version, I'm still having problems with the kit, it now fails the IVP. I'm
changing the kit to a CSCPAT format so we won't run in to the problem again. Also,
I don't know what NDU kit was given to you (SSB or net), but V2.0 is now released
on the Sept CD rom.
Brad
|
595.6 | Good to hear something's happening. | PTOECA::MCELWEE | Opponent of Oppression | Mon Oct 19 1992 23:33 | 14 |
| Brad,
I had the 1.2 NDU kit. I dunno exactly where it came from.
Is the DEMFA014 kit failing IVP because of the incorrectly named
file in the save set or something else? I got it to work by renaming
the {..RELEASE_NOTES} file and rebuilding the kit...
BTW, the NDU license issue is being discussed in RBMS_LANBRIDGE100
Note 590.
Phil
|
595.7 | | CSC32::B_GOODWIN | Time is an illusion... | Tue Oct 20 1992 09:43 | 8 |
| > Is the DEMFA014 kit failing IVP because of the incorrectly named
> file in the save set or something else? I got it to work by renaming
> the {..RELEASE_NOTES} file and rebuilding the kit...
I ran into that problem, but fixed it and was getting another error, don't
remember it of the top, it wasn't worth my time to figure it out. I gave it to
the CSCPAT people and will let them make a new kit.
|