Date   : Sun, 06 Nov 2005 01:52:48 +0000
From   : "Ian Wolstenholme" <BBCMailingList@...>
Subject: Re: Copying from DFS to ADFS

I think you will have to create the target directory manually.  I suspect
you may also have to specify the files to transfer in the XFER command
(using wildcards) rather than just listing the filing systems, ie:

*XFER DISC.* ADFS.*

*FADFS puts you into ADFS without mounting the disc, so you change to
drive 1 with the *DIR command without ADFS first trying to mount the 
DFS disc in drive 0.

Best wishes,


Ian

----- Original Message -----
From: Richard Hobbis
To:  bbc <bbc-micro@...>
Sent: Sun, 06 Nov 2005 09:12:28 +1300
Subject: Re: [BBC-Micro] Copying from DFS to ADFS

Hi All

Thanks for the replies. The ADT command XFER looks very promising 
(thanks Raf) because it does multiple files at a time with simple 
commands. I found the MOVE command only seemed to accept one file at a 
time whereas ADT does entire directories at a time.

A question about the documentation for ADT - the document I downloaded 
has the following example:

    Insert the DFS disc into drive 0 and the ADFS disc into drive 1
    *DISC
    *DIR:0.$
    *FADFS
    *DIR :1.$. GAMES
    *XFER DISC ADFS

    This example would transfer all files in directory $ in DFS on drive 
0 to directory $.GAMES in ADFS on drive 1.

Two things to ask ...

1. does the target directory get created automatically or do I have to 
do it manually?
2. what's the *FADFS command?

I'm unable to use HDFS unfortunately because I currently have no way of 
transferring software from PC to Beeb - this is now my next priority!

Thanks again everyone - your help is invaluable
Cheers
Richard (NZ)


Raf wrote:

> For copying whole discs, quickly, between DFS and ADFS,
> or vice versa, I find the XFER command of the ADT ROM
> very useful.
>
> Best wishes, Raf
>
> ----- Original Message ----- From: "David Hunt" <dm.hunt@...>
> To: <bbc-micro@...>
> Sent: Tuesday, October 25, 2005 10:48 PM
> Subject: RE: [BBC-Micro] Copying from DFS to ADFS
>
>
>>> > The process is slow and shadow RAM is used as temporary memory, so 
>>> you
>>> need
>>> > to make sure it is switched off, e.g.
>>> >
>>> > *SHADOW 0
>>> > MODE 7
>>>
>>> I used *MOVE quite a bit when I was a regular Master user, and I don't
>>> ever recall having to turn off shadow memory. MODE 135 (shadowed 7) 
>>> was my
>>> usual mode of choice.
>>>
>>> I can imagine it might use the shadow memory if it was free, to 
>>> reduce the
>>> number of read-write cycles, but are you sure you were forced to use 
>>> main
>>> memory?
>>
>>
>> I'd suspect that it would use the remaining shadow RAM for the buffer 
>> during
>> the swap, the 1K used in MODE 135 won't make much odds, however, the 20k
>> used by MODE 128 would be significant.
>>
>> Dave ;)
>>
>>
>>
>
>
>
>
>
>