ken@CIT-HAMLET.ARPA (09/07/85)
I installed V4.2 a few days ago, and have the following experiences
to relate. This installation was on a 11/750 in a VAXcluster.
o I was unable to build the V4.2 Standalone backup kit on TU58s. It
got a device full error writing the second system volume. I fixed
this by editing STABACKIT.COM to leave off the line printer driver.
Gets some funny error when it boots, but boots quicker!
o I asked it to boot via the TU58, and the first reboot failed.
(Machine Check exception before even loading DEFBOO.CMD). I am
not the only one with this problem, but we both continued by
throwing away the TU58 and typing B/F0000000.
o (From someone else at CIT). His TU80 tape drive did not show up
after the first reboot. Something weird since STARTUP_P1 is "MIN"
perhaps? He solved the problem by doing a conversational boot and
AUTOCONFIGure ALLing.
o I noticed some weird NET jobs with control characters and garbage
in their names, but havn't been able to pinpoint more on this. If
anyone else sees this, please let me know.
-Ken Adelman
Caltech