HP3000-L Archives

March 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Glenn A. Mitchell" <[log in to unmask]>
Reply To:
Glenn A. Mitchell
Date:
Sat, 24 Mar 2001 08:17:59 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
I too ran into this problem late last week with a couple of patches.  I
second the suggestion to include the build parameters in the example in the
installation guide.  I so rarely use those that I stumbled around a bit
before getting things to work.

--
Glenn A. Mitchell  Mailto:[log in to unmask]
3GM Associates, Inc   Brainbench MVP for COBOL II
Portland, ME  04102    www.brainbench.com
207-772-9370

"Danny A. van Delft" <[log in to unmask]> wrote in message
news:3abb1c45.5652102@news.bart.nl...
> Hi all,
>
> a tip when downloading MPE patches from HPITRC by using the FTP client
> from the HP3K. When downloading patch MPELX36C (for MPE6.0) I had an
> unpleasant surprise after about an hour  (using a 64K dialup line):
> The patch size exceeded the filesize limit imposed by the default FTP
> settings in BLDPARMS.ARPA.SYS and the transfer was aborted. Not nice.
> Perhaps a caveat to include in the "MPE/ix patch installation guide"
> to supply the get command with sufficient build parameters, like "get
> MPELX36C ./MPELX36C;rec=-1,,b,ascii;disc=1000000000".
>
> regards
> Danny A. van Delft   [log in to unmask]

ATOM RSS1 RSS2