Date   : Mon, 04 Sep 2006 01:58:02 +0100
From   : jgh@... (Jonathan Graham Harston)
Subject: Re: Tube File Copying

>Message-ID: <6BF09AC717744330A5F84EF0A677931E.MAI@...>
 
"Ian Wolstenholme" <BBCMailingList@...> wrote:
> Can anybody point me to a file copying utility which works across
> filing systems which will:
> 
> a) work correctly across the Tube
> b) use all the available RAM in the Tube as a buffer.
 
Any copying program... After all, the whole point of the Tube is
that the APIs are the same. A program running on the other side of
the Tube that does OSCLI "LOAD "+f$+" "+STR$~mem% will just load
to mem%.
 
Try TreeCopy at http://mdfs.net/
 
> Unfortunately Logcopy doesn't like it, giving me a "NET filing system
> not present" error result from an OSARGS call and then giving me
> a Bad FS Map error when I have got round that.
 
That will be the ARMTube OS, not LogCopy. There are some calls
that are not correctly passed to the host. I found one or two
recently when testing, most crucially OS_Args 0,0, which should
return the current filing system number. Any cross filing system
copying utility is going to cruically depend on that working.
 
I've just tested TreeCopy with the ARMTube turned on, and it does
exactly the same, whereas is works perfectly on the 6502 and Z80
CoPros.
 
> So at the moment I am using trusty old *MOVE but it still seems to
> be doing it a few KB at a time whereas I'd hoped it might load in
 
*MOVE uses a 512-byte buffer in private workspace, unless a
non-shadow screen mode is selected, where it uses the 20K shadow
screen memory.
 
-- 
J.G.Harston - jgh@...                - mdfs.net/User/JGH
BBC BASIC for Windows and Internationalisation
  See http://mdfs.net/Software/BBCBasic/Windows/ProgTips