Last Friday night, I installed (with Patch/IX) the TurboImage patches TIXHXX9A
and MPEHX97A that I had downloaded via the web after talking to HPRC about a
logging password problem we were having.

All of the patched NM programs failed with LDRERR 56 and all the CM programs
failed with LOAD ERR 53 whenever a regular user would try to :RUN them.  But
from MANAGER.SYS (with SM) the programs would load OK.  Weekend production
was waiting, and so I had to back out the patches.

A more leisurely investigation Monday morning revealed that all of the patched
programs had the following bogus ACD entries:

        $OWNER          :       R,W,RACD
        $OWNER          :       R,W,RACD
        $GROUP_MASK     :       R,W,RACD
        $GROUP          :       R,W,RACD
        @.@             :       RACD

With @.@ only having RACD, that would explain why normal users couldn't run
the programs.

The HPRC says the appearance of these bogus ACDs is a known issue pertaining
to web patches.  SO WHY DON'T YOU FIX IT, HP?  To me, bugs in the patch
process is a problem of high severity.  The HPRC suggested workaround until
this is fixed is to ALTSEC ;DELACD all patched files with bogus ACDs.

Since both patches have been superseded, HPRC is sending them to me on DDS
this time around.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave., Costa Mesa, CA, USA 92626-5429
Technical Support               +1 714 432-5865 x26010
"You can tune a file system, but you can't tune a fish." - tunefs(1M)