HP3000-L Archives

September 1995, Week 2

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:
Jim Wowchuk <[log in to unmask]>
Reply To:
Jim Wowchuk <[log in to unmask]>
Date:
Wed, 13 Sep 1995 10:32:53 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (61 lines)
At 05:54 PM 9/11/95 +1000, I wrote:
>Okay, so I transferred MOVER.bin down from JAZZ with Netscape to my PC.
>After that I uploaded with Reflection as a binary with a receiving file spec
>of "REC=128,1,F,BINARY;DISC=,1;CODE=NMPRG".
>
>Unfortunately it will not run:
>FAILED TO LOAD PROGRAM MOVER.MOVER.SYS.  (LDRERR 469)
>File is not a valid program file. (CIERR 630)
....
>So either my file transfer from JAZZ was bad, or the format is something
>other than a binary image - UHAUL?
 
Thanks to everyone for their suggestions and hints -- a solution has been
reached but the problem is not solved.
 
The clue was that the 3000 file, even when built as a byte stream, was
*larger* than the binary file on my PC.  So despite my misgivings about
Netscape, it appeared the problem lay in the file transfer from PC to HP3000.
 
For this file transfer I was using Reflection (4.10) on a Win95 network
transport with PCLINK2.PUB.SYS V2.69.  The file size on the PC is 137984
bytes, which should come out to 539 records.  For some reason unknown, a
binary file transfer with Reflection was producing a file with 1725 records.
Most peculiar. Transferred as a Byte Stream file, the file was only a little
larger...139709 bytes -- a mere extra 1725 bytes, but sufficient to cause
MPE to reject it as a program file.
 
Suspecting there could be a problem with Refletion, I looked for other means
of transfer.  While perhaps I could have enabled HP's FTP server on the
3000, I didn't know the means.  As I have Fransen/King's FTP server also
present and more experience with it, I decided on that.  Unfortunately, I
couldn't find a successful way to specify using WRQ's FTP Client the MPE
parameters (REC=128,,F,BINARY;CODE=NMPRG) in the transfer.  Without these I
got a variable binary files, which perhaps could have been copied locally to
fix, but this was not my idea of fun.
 
Finally I enabled WRQ's FTP Server on my PC, and using HP's FTP on the host
transferred the file using the clause (as recommended on jazz):
 
        GET MOVER.BIN MOVER;REC=128,,F,BINARY;CODE=NMPRG
 
/Sic hoc fit/  -- And in this manner the latter is done.
 
Program works. :)
 
So what is the problem???  It could be Reflection or its partner PCLINK2.
 
IT COULD EVEN BE WINDOWS 95.  %)  (since I'd never had this problem before)
 
But at least it works!
 
 
Cheers to all for their assistance.
----
Jim "seMPEr" Wowchuk           Internet:    [log in to unmask]
Vanguard Computer Services     Compu$erve:  100036,106
 _--_|\                        Post:        PO Box 18, North Ryde, NSW 2113
/      \                       Phone:       +61 (2) 888-9688
\.--.__/ <---Sydney NSW        Fax:         +61 (2) 888-3056
      v      Australia

ATOM RSS1 RSS2