Hi
It's great that Dr Thomas Blinn was able to help someone with 40F patch kit 5 (earlier post) but is it only me that wonders why Compaq continue to allow us to download the patch kits when they could easy fix these problems and reissue them.
I pointed out to Compaq within 3 days of the release of patch kit 5 that the -procees option nolonger worked with dupatch and the reply was that I should wait until patch kit 6. Unfortunately, we could not wait and and workaround was supplied.
With patch kit 4 it was the fdi.mod issue that mean that ES40's would hang once the patch kit was applied.
I understand that all patch kits are a best efforts approach and they are not infallible but how much effort would it take to include revision info in the patch kit and make a new revision available as required. It must be better than having every Compaq customer learn by trial and effort, the pitfalls that other customers experienced months earlier and reported back to Compaq.
Some of have mission critical systems and we need to do everything in our power to keep all downtime (planned or unplanned) to a minimum.
Regards - Mike
-----Original Message-----
From: Darryl Cook [mailto:dlc_at_cs.appstate.edu]
Sent: Thursday, April 19, 2001 6:16 PM
To: tru-64
Subject: Summary: Patch Kit 5 problem with 4.0f
Thanks goes to Dr. Thomas Blinn who resolved the problem with patch kit 5 for
4.0f. Ill post the instructions below as well as some of his comments because the
problem doesnt pertain to all systems.
> > Dr. Blinn,
> >
> > First thanks tremendously for the response. Your help is greatly
> > appreciated. I did as you say and looked at both /usr/sys/BINARY/files
> > and at /usr/sys/conf/alpha/files. They both had a line for the ee entry
> > and both had a line for the MODULE entry. I removed the entries from the
> > /usr/sys/BINARY/files file. I ran doconfig -c system-name and
> > everything ran fine. I copied the new vmunix to / and rebooted. I dont see
> > any problems at this point.
> >
> > thanks for your help!
> > darryl
>
> You got it 100% correct. I wish I could tell you when the fixed patch
> kit will be available; but the work-around is EXACTLY what you did.
>
> Note this will only bite someone who has the NHD3 kit installed AND
> tries to add the patch kit.
>
> The use of the "files" files is messy, and it's easy to accidentally
> make something that won't work if you don't test it adequately. I've
> not double checked, but it's possible that unless you have the DE6xx
> type of Ethernet card (that uses the "ee" driver), this actually will
> NOT impact you. So that might be how it fell through the cracks, the
> testers might have NOT been running on a system with a DE6xx option.
>
> Tom
>
>
Received on Fri Apr 20 2001 - 06:37:38 NZST