| 1 |
<HTML> |
| 2 |
<HEAD> |
| 3 |
<TITLE>File access</TITLE> |
| 4 |
</HEAD> |
| 5 |
<BODY> |
| 6 |
|
| 7 |
<H1>File access</H1> |
| 8 |
|
| 9 |
<HR> |
| 10 |
|
| 11 |
Frodo offers four possibilities for the 1541 emulation: |
| 12 |
|
| 13 |
<H3>1. Host system directory (Directory Mode)</H3> |
| 14 |
|
| 15 |
In this mode, the C64 programs and files are stored in a directory on your |
| 16 |
hard disk and can be <KBD>LOAD</KBD>ed and <KBD>SAVE</KBD>d as usual from |
| 17 |
the emulator. The paths to the directories of the simulated drives are |
| 18 |
given in the settings window in the path entry fields of the "Drives" |
| 19 |
box.<P> |
| 20 |
|
| 21 |
You can also load the directory with <KBD>LOAD"$",8</KBD>. All files are |
| 22 |
displayed as "PRG", all subdirectories as "DIR". To get into a |
| 23 |
subdirectory, you have to open the settings window and change the path for |
| 24 |
the drive, as the operating system of the C64 doesn't know about |
| 25 |
subdirectories. However, it is possible to use a "/" in the C64 file name |
| 26 |
to access these subdirectories (e.g. <KBD>LOAD"GAMES/ELITE",8</KBD>), |
| 27 |
unless the '/' translation setting is turned on.<P> |
| 28 |
|
| 29 |
For the opening of files, the file types "P" and "S" and the access modes |
| 30 |
"R", "W" and "A" are supported. Wildcards (*,?) can be used, but you have |
| 31 |
to remember that files in BeOS/Unix/AmigaOS directories have no determined |
| 32 |
order and the result of <KBD>LOAD"*",8</KBD> is rather random. Files are |
| 33 |
always overwritten even if they are not opened with "@:". Floppy commands |
| 34 |
other than "I" and "UJ", relative files and direct block access are not |
| 35 |
implemented. You can however read the error channel.<P> |
| 36 |
|
| 37 |
|
| 38 |
<H3>2. .d64/x64 disk image file (Disk Image Mode)</H3> |
| 39 |
|
| 40 |
Most C64 programs available on the Internet and on CD-ROMs, expecially demos |
| 41 |
and games, are stored in files with the ending ".d64". Such a file holds all |
| 42 |
683 blocks of a complete side of a 1541 disk, so that direct block accesses |
| 43 |
are possible from within the emulation. The path name of the disk image file |
| 44 |
must be given in the settings window in the path entry fields of the |
| 45 |
"Drives" box.<P> |
| 46 |
|
| 47 |
Apart from .d64 files, Frodo can also use image files of the "x64" emulator, |
| 48 |
automatically detecting the file type.<P> |
| 49 |
|
| 50 |
|
| 51 |
<H3>3. .t64/LYNX archive file (Tape/Archive Mode)</H3> |
| 52 |
|
| 53 |
.t64 and LYNX (.lnx) files are archive files like "tar". .t64 files are |
| 54 |
also often found on the Internet and on CD-ROMs; LYNX is a native C64 |
| 55 |
archiver. Frodo's .t64 support is a bit special in that it doesn't treat |
| 56 |
the .t64 file like a tape image (that's what the .t64 format was designed |
| 57 |
for), but rather like a disk image file. .t64's are not accessed with |
| 58 |
device number 1 (Frodo doesn't have any tape emulation), but with numbers |
| 59 |
8..11 like a disk drive.<P> |
| 60 |
|
| 61 |
When loading the directory with <KBD>LOAD"$",8</KBD>, Frodo creates a |
| 62 |
listing of all files within the archive. You cannot write to .t64 or LYNX |
| 63 |
files, they are read-only under Frodo.<P> |
| 64 |
|
| 65 |
|
| 66 |
<H3>4. Processor-level 1541 emulation</H3> |
| 67 |
|
| 68 |
The 1541 is an "intelligent" disk drive bearing its own CPU and memory that |
| 69 |
can even be programmed and execute code concurrently to the C64. Frodo is |
| 70 |
able to emulate a 1541 on this level, but as this slows down the whole |
| 71 |
emulation notably, the 1541 processor emulation can be turned on and off |
| 72 |
from the settings.<P> |
| 73 |
|
| 74 |
If the 1541 processor emulation is turned on, only drive number 8 in Disk |
| 75 |
Image Mode is available. The path name of the .d64/x64 file to be used must |
| 76 |
be given in the path entry field of drive 8.<P> |
| 77 |
|
| 78 |
</BODY> |
| 79 |
</HTML> |
