In regards to transferring monster files, and the error message Reflection
gave about extents - the problem is at the HP end and PCLINK2.

When my version 5.21 came out who would have thought that we'd be
transferring files of 400MB to 2 GB from a PC to an HP3000?...

Someone suggested switching it to binary - and that seemed to work although
in tests the file at the HP end had a byte or 2 (or 3 or indeterminate
number)
wrong - LIST (telesup) showed that to be the case - If I had spent some time
I could have resolved it simply by uploading via binary mode.

My work around was to simply split the file in 2 at the PC end and take 14
hours each to upload (yes, we are behind the times - I use a simple  19.2 
serial
line)

I went to the Reflection site as someone suggested and they understandably
want a subscription to download the latest PCLINK2 -

My little business such as it is may not be around in a couple of years
(certainly not the fault of the HP3000) so for now modifying my C++ pgm on
the PC to split the file in 2 will suffice.

Many thinks to all who took the time to respond to my query!

Bill

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *