HP3000-L Archives

June 1998, 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:
Chris Bartram <[log in to unmask]>
Reply To:
Date:
Wed, 10 Jun 1998 19:18:51 -0400
Content-Type:
Text/Plain
Parts/Attachments:
Text/Plain (35 lines)
 In <[log in to unmask]> [log in to unmask] writes:

> 1 - Upload a file from the PC using Reflection v5.10 into a POSIX
> directory

In the file-transfer setup screen, wrq/reflection tab, you can select the
attributes and advanced buttons to specifically send the file as a byte-
stream file. Not doing this causes the problem you encountered; I hit it
quite a bit myself. Easy solution after-the-fact is to just "cp" the file
in the shell to a new name and edit the copied file - it will be built
correctly.

> 2 - Edit the file using vi (adding something I forgot on the PC side, or
> someone else is adding to it)
> 3 - Save the file using the vi command :wq
> 4 - The following error message is returned:
>         "Write error (out of space)" File too large
> 5 - Issue the vi command :q!
> 6 - If I added 10 bytes somewhere in the file, 10 bytes have been
> removed from the end of the file.
>
> I'm wondering if anyone else has run into this problem and what
> workaround they have developed (if any).

I believe the problem stems from the fundamental problem in the posix
implementation where when posix apps read MPE files, they count on getting
actual "byte counts" of the contents of the file, where MPE with it's byte-
filled fixed records (padding - which don't count as file contents) throw
the byte counts off, causing the posix app to think there's more room in the
file than there really is.

Or I could be wrong. ;-)

       -Chris Bartram

ATOM RSS1 RSS2