HP3000-L Archives

November 2002, Week 3

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:
POSIX 'tobyte' limitation
From:
Eben Yong <[log in to unmask]>
Reply To:
Eben Yong <[log in to unmask]>
Date:
Fri, 15 Nov 2002 16:29:05 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (1 lines) 
An interesting thing occurred to us this month, wherein we were trying to convert a very large MPE file:

 

record count: 102370

record length: 25158

bytes:  2575424460, or approx. 2.5 GB

 

to a bytestream file.  Unbeknownst to us, the tobyte program has a 2 GB limit--or so it seems.  Using the POSIX command 'tobyte <source> <dest>' where <source> was the original file, the <dest> file was always produced with a bytecount of 2147483647 (which is one byte less than 2 GB).  Moreover, it did not produce a warning or an error, so we didn't initially realize the tobyte-ed file was incomplete.  Anyone know why this is the case and if there's a workaround (other than splitting up the original file and converting the split files separately)?

ôèþ:"Ÿù^jø¶–+-ûj·!ýªÜ†+ÞÀ/Ü…©à‡ùb³ìzÛbžÿ0¿z×ÿúey«þø¬‹á¶Û?ÿúڽ꿺×ÿyÛ¿j·!Š÷¬þwÓMÿ£ømš¿

ATOM RSS1 RSS2