CPCWiki - THE Amstrad CPC encyclopedia! - User contributions [en]

Roland javascript emulator

2013-01-13T09:33:33Z

Antoniovillena:

Information extracted from emulator homepage: [http://roland.retrolandia.net/ http://roland.retrolandia.net/]

<br> Roland is an Amstrad CPC emulator written in javascript. It can be slow in your machine, so I recommend you to use with Chrome 10+ for best performance results.

By now, only CPC 464 model is emulated. Sound & disk doesn't work, and many games will crash or doesn't work properly, because this is a beta release (the first beta one). Green links (on left frame) are .TAP files, and the blue ones are .CDT. Please be patient by loading .CDT files, they are very slow and there isn't any notification until loading is done.

Roland has a GPL license, the source code is here. It shares the same Z80 engine as jbacteria and jtandy, but the rest is developed from scratch. There is another CPC emulator, at a very advanced state (disk emulation), so I encourage you to try it.

Instructions:

*Only CPC 464 model supported.
*Keyboard is as in your PC, so the mapping PCKEY -> cpckey is: INS -> copy, ENTER -> return, PC NUMPAD KEYS -> cpc function keys, NUMPAD+ -> enter, DEL -> clr, BACKSPACE -> del.
*F1 for pause emulation, and show the keymap help.
*Supported .CDT and .TAP files from server (.CDTs in blue, .TAPs in green).
*Supported SNA files: load by dragging a local file to emulator window, save with F10.
*Supported memory snapshots: save with F3 and load with F4.
*F5 for reset (normal browser refresh) and F11 for full screen

Format:TAP tape image file format

2011-05-01T05:29:53Z

Antoniovillena: /* Tape-Image (.TAP) file format */

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF
^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..
^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Name of the file, padded with nulls
16 1 Block number The first block is 1, numbers are consecutive
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

List of file formats

2011-04-29T10:31:45Z

Antoniovillena:

== CPC file extensions ==

This list is a collection of file-extensions used on the Amstrad/Schneider CPC and CPC Plus computer range. It's not a collection of file-extensions used by PC systems for CPC related stuff.

{| class="FCK__ShowTableBorders"
|-
| ''Extension''
| ''Explanations''
| ''Programs that use this extenstion''
|-
| $$$
| Temporary Amsdos file
| [[Amsdos|amsdos]]
|-
| 128
| Soundtrakker 128KB music file
| [[Soundtrakker|Soundtrakker]]
|-
| 64K
| FutureOS Main-memory program
| [[FutureOS|FutureOS]]
|-
| ACE
| Packed Windows archive
| [[ACE|ACE]]
|-
| ARC
| CP/M, Xexor ARC File format
| [[CP/M]], [[Format:Xexor ARC file format|Xexor ARC Format]]
|-
| ASC
| ASCII text
|
|-
| ASM
| Assembler source code
| ASM.COM
|-
| AYC
| Derivate or converted YM music file
|
|-
| BAK
| Backup file
|
|-
| BAS
| Basic program
| [[AMSDOS|AMSDOS]]
|-
| BAT
| Batch-File
|
|-
| BIN
| binary file
| [[AMSDOS|AMSDOS]]
|-
| CCP
| Key definition for CP/M Plus
| [[CP/M 3.0|CP/M 3.0]]
|-
| COM
| Executable CP/M or [[SymbOS|SymbOS]]-SymShell program
| [[CP/M|CP/M]], [[SymShell|SymShell]]
|-
| CUT
| AMX Pagemaker Clipart
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| DD
| Device driver for GSX (CP/M Plus)
| [[CP/M 3.0|CP/M 3.0]]
|-
| DEU
| DEU German text
|
|-
| ENG
| English text
|
|-
| EXE
| EXE Executable file, SymbOS
| [[SymbOS|SymbOS]]
|-
| Fld
| Map file of a game
| [[GSED]]
|-
| FNT
| Font of AMX Pagemaker
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| FRA
| French text
|
|-
| GEs
| Set of Graphic-elements
| [[GSED]]
|-
| H
| C variable definitions
| Small C i.e.
|-
| HED
| Header/Icon definition for FutureOS
| [[FutureOS|FutureOS]]
|-
| HGB
| FutureOS Background Picture
| [[FutureOS|FutureOS]]
|-
| HLP
| Help file
| CP/M and others
|-
| INF
| AMX Pagemaker site
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| INS
| Soundtrakker Instrument file
| [[Soundtrakker|Soundtrakker]]
|-
| MAC
| Makroassembler source code
| MAC.COM
|-
| MAX
| Maxam Source Code
| [[Maxam|Maxam]]
|-
| MDL
| Digitracker Module
| [[Digitracker|Digitracker]]
|-
| MOD
| Crown Protracker Module or Amiga MO$D File
|
|-
| MP3
| MP3 Sound file
| [[FuturePlayer|FuturePlayer]]
|-
| OBJ
| Object Code
|
|-
| OVL
| Overlay parts of WordStar o.e.
|
|-
| PA1
| AMX Pagemaker site (part 1)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| PA2
| AMX Pagemaker site (part 2)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| PA3
| AMX Pagemaker site (part 3)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| PA4
| AMX Pagemaker site (part 4)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| [[Format:Advanced OCP Art Studio File Formats|PAL]]
| OCP Art Studio Palette
| [[The OCP Art Studio|The OCP Art Studio]]
|-
| PAS
| (Turbo-)Pascal source code
| Turbo Pascal
|-
| PRV
| AMX Pagemaker site (Preview)
| AMX Pagemaker
|-
| PRL
| page relocatable file
|
|-
| RAR
| Packed Windows Archive
|
|-
| ROM
| Rom-File (16K)
| diff. (Pseudo-)/(EP)ROM Manager
|-
| PT3
| Spectrum Protracker 3 Music
| [[SymAmp|SymAmp]]
|-
| SAV
| SymbOS screen saver
| [[SymbOS|SymbOS]]
|-
| [[Format:Advanced OCP Art Studio File Formats|SCR]]
| OCP Art Studio Screen
| [[The OCP Art Studio|The OCP Art Studio]]
|-
| [[Format:SGX (SymbOS graphic files)|SGX]]
| SymbOS graphic
| [[SymbOS|SymbOS]]
|-
| SKM
| compilated [[STarKos]] Module
| [[SymAmp|SymAmp]]
|-
| SKR
| Set of Scripts
|
|-
| SKS
| STarKos Module
| [[STarKos|STarKos]]
|-
| SMC
| Executable C Program for FutureOS
| [[FutureOS|FutureOS]]
|-
| SND
| Soundtrakker 64KB Music
| [[Soundtrakker|Soundtrakker]]
|-
| SPR
| Set of Sprites
|
|-
| ST2
| Compilated [[Soundtrakker|Soundtrakker]] 128 Module
| [[SymAmp|SymAmp]]
|-
| SUB
| Submit/Batch file (CP/M)
| [[CP/M|CP/M]]
|-
| TXT
| ASCII text
|
|-
| [[Format:VID (SymbOS video files)|VID]]
| [[SymbOS|SymbOS]] video
| [[SymPlay|SymPlay]]
|-
| [[Format:Advanced OCP Art Studio File Formats|WIN]]
| OCP Art Studio Clip
| [[The OCP Art Studio|The OCP Art Studio]]
|-
| WP
| Key definition for WordStar
| [[WordStar|WordStar]]
|-
| X16
| FutureOS Expansion RAM program
| [[FutureOS|FutureOS]]
|-
| YM
| YM Music file
| YM-Player and others
|}

== PC / Emulator related file formats ==

{| class="FCK__ShowTableBorders"
|-
| ''Extension''
| ''Explanations''
| ''Programs that use this extenstion''
|-
| [[Format:CDT tape image file format|CDT]]
| Tape image file format
| [[Arnold]],[[CaPriCe]], [[JavaCPC]], [[WinCPC]], [[WinApe]]
|-
| [[Format:CPR CPC Plus cartridge file format|CPR]]
| CPC Plus cartridge file format
| [[Arnold]],[[WinApe]]
|-
| [[Format:DSC disk image file format|DSC]]
| Disc image
| DSK-CPC
|-
| [[Format:DSK disk image file format|DSK]]
| Disc image
| [[Arnold]],[[CaPriCe]], [[JavaCPC]], [[SymSnap]], [[WinCPC]], [[WinApe]],DSK-CPC
|-
| [[Format:SNA snapshot file format|SNA]]
| Machine snapshot image file format
| [[Arnold]],[[CaPriCe]], [[JavaCPC]], [[SymSnap]], [[WinCPC]], [[WinApe]]
|-
| [[Format:TAP tape image file format|TAP]]
| Emulator tape image
| [[Roland javascript emulator|Roland]]
|}

[[Category:Definitions]]

List of file formats

2011-04-29T10:30:35Z

Antoniovillena:

List of file formats

2011-04-29T10:27:31Z

Antoniovillena:

== CPC file extensions ==

This list is a collection of file-extensions used on the Amstrad/Schneider CPC and CPC Plus computer range. It's not a collection of file-extensions used by PC systems for CPC related stuff.

{| class="FCK__ShowTableBorders"
|-
| ''Extension''
| ''Explanations''
| ''Programs that use this extenstion''
|-
| $$$
| Temporary Amsdos file
| [[Amsdos|amsdos]]
|-
| 128
| Soundtrakker 128KB music file
| [[Soundtrakker|Soundtrakker]]
|-
| 64K
| FutureOS Main-memory program
| [[FutureOS|FutureOS]]
|-
| ACE
| Packed Windows archive
| [[ACE|ACE]]
|-
| ARC
| CP/M, Xexor ARC File format
| [[CP/M]], [[Format:Xexor ARC file format|Xexor ARC Format]]
|-
| ASC
| ASCII text
|
|-
| ASM
| Assembler source code
| ASM.COM
|-
| AYC
| Derivate or converted YM music file
|
|-
| BAK
| Backup file
|
|-
| BAS
| Basic program
| [[AMSDOS|AMSDOS]]
|-
| BAT
| Batch-File
|
|-
| BIN
| binary file
| [[AMSDOS|AMSDOS]]
|-
| CCP
| Key definition for CP/M Plus
| [[CP/M 3.0|CP/M 3.0]]
|-
| COM
| Executable CP/M or [[SymbOS|SymbOS]]-SymShell program
| [[CP/M|CP/M]], [[SymShell|SymShell]]
|-
| CUT
| AMX Pagemaker Clipart
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| DD
| Device driver for GSX (CP/M Plus)
| [[CP/M 3.0|CP/M 3.0]]
|-
| DEU
| DEU German text
|
|-
| ENG
| English text
|
|-
| EXE
| EXE Executable file, SymbOS
| [[SymbOS|SymbOS]]
|-
| Fld
| Map file of a game
| [[GSED]]
|-
| FNT
| Font of AMX Pagemaker
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| FRA
| French text
|
|-
| GEs
| Set of Graphic-elements
| [[GSED]]
|-
| H
| C variable definitions
| Small C i.e.
|-
| HED
| Header/Icon definition for FutureOS
| [[FutureOS|FutureOS]]
|-
| HGB
| FutureOS Background Picture
| [[FutureOS|FutureOS]]
|-
| HLP
| Help file
| CP/M and others
|-
| INF
| AMX Pagemaker site
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| INS
| Soundtrakker Instrument file
| [[Soundtrakker|Soundtrakker]]
|-
| MAC
| Makroassembler source code
| MAC.COM
|-
| MAX
| Maxam Source Code
| [[Maxam|Maxam]]
|-
| MDL
| Digitracker Module
| [[Digitracker|Digitracker]]
|-
| MOD
| Crown Protracker Module or Amiga MO$D File
|
|-
| MP3
| MP3 Sound file
| [[FuturePlayer|FuturePlayer]]
|-
| OBJ
| Object Code
|
|-
| OVL
| Overlay parts of WordStar o.e.
|
|-
| PA1
| AMX Pagemaker site (part 1)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| PA2
| AMX Pagemaker site (part 2)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| PA3
| AMX Pagemaker site (part 3)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| PA4
| AMX Pagemaker site (part 4)
| [[AMX Pagemaker|AMX Pagemaker]]
|-
| [[Format:Advanced OCP Art Studio File Formats|PAL]]
| OCP Art Studio Palette
| [[The OCP Art Studio|The OCP Art Studio]]
|-
| PAS
| (Turbo-)Pascal source code
| Turbo Pascal
|-
| PRV
| AMX Pagemaker site (Preview)
| AMX Pagemaker
|-
| PRL
| page relocatable file
|
|-
| RAR
| Packed Windows Archive
|
|-
| ROM
| Rom-File (16K)
| diff. (Pseudo-)/(EP)ROM Manager
|-
| PT3
| Spectrum Protracker 3 Music
| [[SymAmp|SymAmp]]
|-
| SAV
| SymbOS screen saver
| [[SymbOS|SymbOS]]
|-
| [[Format:Advanced OCP Art Studio File Formats|SCR]]
| OCP Art Studio Screen
| [[The OCP Art Studio|The OCP Art Studio]]
|-
| [[Format:SGX (SymbOS graphic files)|SGX]]
| SymbOS graphic
| [[SymbOS|SymbOS]]
|-
| SKM
| compilated [[STarKos]] Module
| [[SymAmp|SymAmp]]
|-
| SKR
| Set of Scripts
|
|-
| SKS
| STarKos Module
| [[STarKos|STarKos]]
|-
| SMC
| Executable C Program for FutureOS
| [[FutureOS|FutureOS]]
|-
| SND
| Soundtrakker 64KB Music
| [[Soundtrakker|Soundtrakker]]
|-
| SPR
| Set of Sprites
|
|-
| ST2
| Compilated [[Soundtrakker|Soundtrakker]] 128 Module
| [[SymAmp|SymAmp]]
|-
| SUB
| Submit/Batch file (CP/M)
| [[CP/M|CP/M]]
|-
| [[Format:TAP tape image file format|TAP]]
| Emulator tape image
| [[Roland javascript emulator|Roland]]
|-
| TXT
| ASCII text
|
|-
| [[Format:VID (SymbOS video files)|VID]]
| [[SymbOS|SymbOS]] video
| [[SymPlay|SymPlay]]
|-
| [[Format:Advanced OCP Art Studio File Formats|WIN]]
| OCP Art Studio Clip
| [[The OCP Art Studio|The OCP Art Studio]]
|-
| WP
| Key definition for WordStar
| [[WordStar|WordStar]]
|-
| X16
| FutureOS Expansion RAM program
| [[FutureOS|FutureOS]]
|-
| YM
| YM Music file
| YM-Player and others
|}

== PC / Emulator related file formats ==

{| class="FCK__ShowTableBorders"
|-
| ''Extension''
| ''Explanations''
| ''Programs that use this extenstion''
|-
| [[Format:CDT tape image file format|CDT]]
| Tape image file format
| [[Arnold]],[[CaPriCe]], [[JavaCPC]], [[WinCPC]], [[WinApe]]
|-
| [[Format:CPR CPC Plus cartridge file format|CPR]]
| CPC Plus cartridge file format
| [[Arnold]],[[WinApe]]
|-
| [[Format:DSC disk image file format|DSC]]
| Disc image
| DSK-CPC
|-
| [[Format:DSK disk image file format|DSK]]
| Disc image
| [[Arnold]],[[CaPriCe]], [[JavaCPC]], [[SymSnap]], [[WinCPC]], [[WinApe]],DSK-CPC
|-
| [[Format:SNA snapshot file format|SNA]]
| Machine snapshot image file format
| [[Arnold]],[[CaPriCe]], [[JavaCPC]], [[SymSnap]], [[WinCPC]], [[WinApe]]
|}

[[Category:Definitions]]

Emulators

2011-04-29T10:24:15Z

Antoniovillena:

= Operating Systems =

== Acorn RISC OS ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[!CPC|!CPC]]
|
| Jul 28, 1996
| [[CPC old generation|CPC range]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/CPC0728.ZIP]
|-
| [[!CPCemu|!CPCemu]]
| 1.10
| Jun 4, 1997
| [[CPC old generation|CPC range]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/CPCEM110.ZIP]
|}

== Amiga ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[A-CPC|A-CPC]]
| 2.0
| Apr 10, 1996
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Shareware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/ACPCDE20.LHA]
|-
| [[Ami-CPC|Ami-CPC]]
| 0.46
| Jan 21, 1998
| [[CPC old generation|CPC range]]
| Open source
| [http://deplanque.chez.com/]
|-
| [[CPE|CPE]]
|
| Feb 24, 1995
| [[CPC old generation|CPC range]]
| Open source
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/ACPE_NEW.LHA]
|-
| [[Emu-CPC|Emu-CPC]]
| 0.7
| Sep 15, 1996
| [[CPC old generation|CPC range]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/EMUCPC07.LZX]
|}

== Amsdos ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[ZXM|ZXM]]
|
|
| [[ZX Spectrum|ZX Spectrum]]
|
| [http://www.systemed.net/cpc/zxm.zip]
|}

== DOS ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Arnimedes|Arnimedes]]
| 0.8a
| Apr 15, 2000
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.arnimedes.de/]
|-
| [[CPCE|CPCE]]
| 1.94
| Mar 7, 2011
| [[CPC old generation|CPC range]]
| Freeware
| [http://cngsoft.no-ip.org/cpce/]
|-
| [[CPCemu|CPCemu]]
| 1.5
| Jul 7, 1998
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.cpc-emu.org/]
|-
| [[NO$CPC|NO$CPC]]
| 1.8
| Nov 2, 2000
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Freeware
| [http://nocash.emubase.de/cpc.htm]
|-
| [[CPCEMU (RWCPC)|RWCPC]]
|
| Mar 23, 1995
| [[CPC old generation|CPC range]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/RWCPC.ZIP]
|}

== Java ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Arnold Jnr|Arnold Jnr]]
|
| Aug 27, 2001
| [[CPC old generation|CPC range]]
| Open source
| [http://www.arnoldemu.freeserve.co.uk/]
|-
| [[CPCInAJar|CPCInAJar]]
|
| Mar 16, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://sourceforge.net/projects/cpcinajar/]
|-
| [[JEMU|JEMU]]
|
| Feb 19, 2007
| [[CPC old generation|CPC range]], [[BBC Micro]], [[VZ-300]], [[ZX Spectrum]], [[ZX80]], [[ZX81]]
| Open source
| [http://jemu.winape.net/]
|-
| [[JavaCPC|JavaCPC]]
| 6.7
| Nov 1, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://cpc-live.com/]
|-
| [[WebCPC|WebCPC]]
|
|
| [[CPC old generation|CPC range]]
| Open source
| [http://sourceforge.net/projects/webcpc/]
|}

== Javascript ==

{| class="wikitable sortable" style="width:100%"
|-
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[CPCBox|CPCBox]]
| beta
| Apr 3, 2011
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.cpcbox.com/]
|-
| [[Roland javascript emulator|Roland]]
|
| Apr 20, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://roland.antoniovillena.es/]
|}

== MacOS ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Arnold_(Emulator)|Arnold]]
| 1.7.8
|
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Open source
| [http://www.bannister.org/software/arnold.htm]
|-
| [[CPCplusplus|CPC++]]
| 2.0.0
| Jan 14, 2003
| [[CPC old generation|CPC range]]
| Shareware
| [http://bricerive.free.fr/cpc/cpcpp.html]
|-
| [[MacMESS|MacMESS]]
| 0.132
| Jul 19, 2009
| [[CPC old generation|CPC range]], [[Plus|Plus range]] & lots of other computer systems
| Open source
| [http://www.macmess.org/]
|-
| [[MacCPC|MacCPC]]
| 0.9.2
| Jan 22, 2010
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.wincpc.ch/index.php?topic=projects-maccpc]
|}

== SunOS / Solaris ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[CPCplusplus|CPC++]]
| 1.5.0
|
| [[CPC old generation|CPC range]]
| Shareware
| [http://bricerive.free.fr/cpc/cpcpp.html]
|}

== Unix / Linux ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Arnold_(Emulator)|Arnold]]
|
| Mar 17, 2009
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Open source
| [http://arnold.berlios.de/]
|-
| [[CaPriCe|CaPriCe]]
| 4.2.0
| May 14, 2005
| [[CPC old generation|CPC range]]
| Open source
| [http://sourceforge.net/projects/caprice32/]
|-
| [[Caprice Reloaded]]
| r449
| Jan 30, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://code.google.com/p/cpcsdk/]
|-
| [[CPCplusplus|CPC++]]
| 1.5.0
|
| [[CPC old generation|CPC range]]
| Shareware
| [http://bricerive.free.fr/cpc/cpcpp.html]
|-
| [[cpc4x|cpc4x]]
| 0.26
| Dec 11, 2004
| [[CPC old generation|CPC range]]
| Open source
| [http://www.ulrich-cordes.de/cpc/english/cpcemu.htm]
|-
| [[CPCemu|CPCemu]]
| 1.7
| Dec 6, 2009
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.cpc-emu.org/]
|-
| [[DSP|DSP]]
| 0.11b1 WIP
| Feb 18, 2011
| [[CPC old generation|CPC range]], [[ZX Spectrum]], [[Nintendo NES]], [[ColecoVision]], [[Arcade]]
| Open source
| [http://code.google.com/p/dsp-emulator/]
|-
| [[ep128emu|ep128emu]]
| 2.0.9.1
| Jan 3, 2011
| [[CPC old generation|CPC range]], [[ZX Spectrum]], [[Enterprise]]
| Open source
| [http://sourceforge.net/projects/ep128emu/]
|-
| [[MESS|MESS]]
| 0.141
| Jan 9, 2011
| [[CPC old generation|CPC range]], [[Plus|Plus range]] & lots of other computer systems
| Open source
| [http://www.mess.org/]
|-
| [[Roland Emulator|Roland]]
| 0.5b2
| Jan 5, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://www.rolandemu.de/home.en.html]
|-
| [[XCPC|Xcpc]]
|
| Jan 22, 2007
| [[CPC old generation|CPC range]]
| Open source
| [http://xcpc.sourceforge.net/]
|}

== Windows ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Arnimedes|Arnimedes]]
| 1.01
| Sep 17, 2006
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.arnimedes.de/]
|-
| [[Arnold_(Emulator)|Arnold]]
|
| Jan 11, 2004
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Open source
| [http://arnold.emuunlim.com/]
|-
| [[CaPriCe|CaPriCe]]
| 4.2.0
| May 14, 2005
| [[CPC old generation|CPC range]]
| Open source
| [http://sourceforge.net/projects/caprice32/]
|-
| [[Caprice Reloaded]]
| r449
| Jan 30, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://code.google.com/p/cpcsdk/]
|-
| [[CoPaCabana|CoPaCabana]]
| 0.74
| Apr 12, 2006
| [[CPC old generation|CPC range]]
| Freeware
| [http://copacabana.emuunlim.com/]
|-
| [[CPC-em|CPC-em]]
| 0.4
| Jul 7, 2004
| [[CPC old generation|CPC range]]
| Open source
| [http://cpc-em.emuunlim.com/]
|-
| [[CPC3D/CPC32]]
| 0.3
| Feb 8, 2003
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.angelfire.com/retro2/cpc3d/]
|-
| [[CpcAlive|CpcAlive]]
| 1.09h
| Dec 12, 2010
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.cpcalive.com/cpcalive_en.html]
|-
| [[CPCE|CPCE]]
| 1.94
| Mar 7, 2011
| [[CPC old generation|CPC range]]
| Freeware
| [http://cngsoft.no-ip.org/cpce/]
|-
| [[CPCemu|CPCemu]]
| 1.7
| Dec 6, 2009
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.cpc-emu.org/]
|-
| [[CPE|CPE]]
| 5.2
| Apr 21, 1997
| [[CPC old generation|CPC range]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/CPE52.ZIP]
|-
| [[DSP|DSP]]
| 0.11b1
| Mar 10, 2011
| [[CPC old generation|CPC range]], [[ZX Spectrum]], [[Nintendo NES]], [[ColecoVision]], [[Arcade]]
| Open source
| [http://code.google.com/p/dsp-emulator/]
|-
| [[ep128emu|ep128emu]]
| 2.0.9.1
| Jan 3, 2011
| [[CPC old generation|CPC range]], [[ZX Spectrum]], [[Enterprise]]
| Open source
| [http://sourceforge.net/projects/ep128emu/]
|-
| [[MESS|MESS]]
| 0.141
| Jan 9, 2011
| [[CPC old generation|CPC range]], [[Plus|Plus range]] & lots of other computer systems
| Open source
| [http://www.mess.org/]
|-
| [[MTMW|MTMW]]
| 1.30B
| Jan 11, 2000
| [[CPC old generation|CPC range]], [[Plus|Plus range]], [[ZX Spectrum]], [[ZX80]], [[ZX81]], [[Jupiter ACE]], [[Enterprise]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/MTMW130B.ZIP]
|-
| [[NO$CPC|NO$CPC]]
| 1.8
| Nov 2, 2000
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Freeware
| [http://nocash.emubase.de/cpc.htm]
|-
| [[PC-CPC|PC-CPC]]
| 0.1as
| Dec 30, 2010
| [[CPC old generation|CPC range]]
| Freeware
| [http://demoniak-contrib.forumactif.com/f3-programmes-pc-pour-cpc]
|-
| [[Roland Emulator|Roland]]
| 0.5b2
| Jan 5, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://www.rolandemu.de/home.en.html]
|-
| [[VirtualCPC|Virtual CPC]]
| 1.06
| Aug 8, 2007
| [[CPC old generation|CPC range]]
| Freeware
| [http://antaresweb.dyndns.org/cpc/]
|-
| [[WinApe|WinApe]]
| 2.0a17
| Sep 9, 2008
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
| Freeware
| [http://www.winape.net/]
|-
| [[WinCPC|WinCPC]]
| 0.9.25
| Jan 6, 2007
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.wincpc.ch/index.php?topic=projects-wincpc]
|-
| [[Yage|Yage]]
| 0.91
| Oct 24, 1998
| [[CPC old generation|CPC range]]
| Freeware
| [ftp://ftp.lip6.fr/pub/amstrad/emulator/YAGE091.ZIP]
|}

= Home Consoles =

== Microsoft XBOX ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Arnold|ArnoldX]]
| v5
| Apr 20, 2010
| [[CPC old generation|CPC range]], [[Plus|Plus range]]
|
| [http://forums.xbox-scene.com/index.php?showtopic=711667]
|}

== Nintendo Wii ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Wiituka|Wiituka]]
| 0.98.8
| May 15, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://wiituka.dantoine.org/]
|}

== Sega Dreamcast ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[CPCast|CPCast]]
|
| May 6, 2006
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.dcemu.co.uk/vbulletin/showthread.php?t=24100]
|-
| [[DreamCPC|DreamCPC]]
| Alpha 3
| Oct 16, 2005
| [[CPC old generation|CPC range]]
| Freeware
| [http://dreamcast.dcemu.co.uk/dreamcpc.php]
|}

= Handheld Consoles =

== Dingoo A320 ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Pituka|Pituka (Dingux)]]
| 0.8pre
| Aug 19, 2010
| [[CPC old generation|CPC range]]
| Open source
| [http://david.dantoine.org/proyecto/4/]
|-
| [[Caprice|Dingux-CAP32]]
| 1.1.2
| Oct 17, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://zx81.zx81.free.fr/serendipity/index.php?/categories/105-Amstrad/]
|}

== Gamepark GP32 / GP2X / Wiz / Caanoo / Pandora ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Pituka|Pituka (GP32)]]
| 1d
| May 15, 2010
| [[CPC old generation|CPC range]]
| Open source
| [http://david.dantoine.org/proyecto/4/]
|-
| [[Caprice|CapriceGP2x]]
| 0.5
| Feb 22, 2006
| [[CPC old generation|CPC range]]
| Open source
| [http://wiki.gp2x.org/wiki/CapriceGP2x]
|-
| [[Caprice|GP2X-CAP32]]
| 1.5.1
| Aug 29, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://zx81.zx81.free.fr/serendipity/index.php?/categories/42-Amstrad/]
|-
| [[Caprice|Wiz-CAP32]]
| 1.1.0
| Aug 29, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://zx81.zx81.free.fr/serendipity/index.php?/categories/89-Amstrad/]
|-
| [[Caprice|Caanoo-CAP32]]
| 1.1.2
| Mar 21, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://zx81.zx81.free.fr/serendipity/index.php?/categories/165-Amstrad/]
|-
| [[Caprice|Pandora-CAP32]]
| 1.1.0
| Jun 27, 2010
| [[CPC old generation|CPC range]]
| Open source
| [http://zx81.zx81.free.fr/serendipity/index.php?/categories/131-Amstrad/]
|}

== Nintendo DS ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[AmeDS|AmeDS]]
| 4.0
| Apr 25, 2010
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.portabledev.com/pages/ds/jeuxdev.-perso/ameds.php]
|-
| [[CrocoDS|CrocoDS]]
| 2.0
| Nov 9, 2007
| [[CPC old generation|CPC range]]
| Freeware
| [http://deadketchup.kyuran.be/tag/cpc/]
|}

== Sony PSP ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[Caprice32 PSP]]
| 4.2.0.2
| Nov 28, 2007
| [[CPC old generation|CPC range]]
| Open source
| [http://psp.akop.org/caprice32]
|-
| [[CPCPSP|CPCPSP]]
| 0.1
| Dec 24, 2005
| [[CPC old generation|CPC range]]
| Freeware
| [http://dl.qj.net/psp/emulators/cpcpsp-v01.html]
|-
| [[PSPCAP32|PSPCAP32]]
| 1.5.1
| Aug 21, 2009
| [[CPC old generation|CPC range]]
| Open source
| [http://zx81.zx81.free.fr/serendipity_fr/index.php?/categories/3-Amstrad/]
|}

= Smartphones / PDAs =

== Android ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[andcpc]]
| 1.5.1
| Apr 4, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://code.google.com/p/andcpc/]
|-
| [[CPCDroid]]
| 1.5.1
| Mar 2, 2011
| [[CPC old generation|CPC range]]
| Open source
| [http://fmsdevel.wisecoding.es/blog/cpcdroid---2011-03-02]
|}

== Maemo ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[CPCm]]
| 1.20-1
| Apr 27, 2010
| [[CPC old generation|CPC range]]
| Open source
| [http://maemo.org/downloads/product/Maemo5/cpcm/]
|}

== Palm OS ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[CaPriCe for Palm OS|CaPriCe for Palm OS]]
| 2.7
| Jul 5, 2010
| [[CPC old generation|CPC range]]
| Open source
| [http://frederic.coste.pagesperso-orange.fr/cpc/cpc_en.htm]
|-
| [[CoPaCabana|CoPaCabana]]
| 0.75
| Dec 4, 2007
| [[CPC old generation|CPC range]]
| Freeware
| [http://copacabana.emuunlim.com/]
|}

== Pocket PC ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[CaPriCe|PocketCaprice]]
| 0.9
| Aug 19, 2007
| [[CPC old generation|CPC range]]
| Freeware
| [http://www.clickgamer.com/moreinfo.htm?pid=4079&section=ppc]
|}

== Symbian ==

{| class="wikitable sortable" style="width:100%"
! Name
! Actual version
! Last release
! Emulated systems
! License
! Link
|-
| [[S60-CPC|S60-CPC]]
| 0.74
| Feb 21, 2006
| [[CPC old generation|CPC range]]
| Open source
| [http://kokak.free.fr/s60cpc.htm]
|}

= Hardware =

*[[CPC TREX|CPC TREX]] (TurboCPC core running on a terasIC T-Rex C1)
*[[C-ONE|C-ONE]] (TurboCPC core running on the C-One reconfigurable computer)

= Emulation Tools =

*[[ConvImgCPC|ConvImgCPC]]
*[[CPCDiskXP|CPCDiskXP]]
*[[CPCGamesCD-CPCLoader|CPCGamesCD-CPCLoader]]
*[[CPCTapeXP|CPCTapeXP]]
*[[CPRTools|CPRTools]]
*[[Dsktools|Dsktools]]
*[[ManageDSK|ManageDSK]]
*[[WriteDSK|WriteDSK]]

= Emulator Detection =

*[[Emulator_IDs|Emulator IDs]]

[[Category:Emulator| ]]

Roland javascript emulator

2011-04-29T10:21:17Z

Antoniovillena: Created page with "Information extracted from emulator homepage: [http://roland.antoniovillena.es/ http://roland.antoniovillena.es/] <br> Roland is an Amstrad CPC emulator written in javascript. ..."

Information extracted from emulator homepage: [http://roland.antoniovillena.es/ http://roland.antoniovillena.es/]

<br> Roland is an Amstrad CPC emulator written in javascript. It can be slow in your machine, so I recommend you to use with Chrome 10+ for best performance results.

By now, only CPC 464 model is emulated. Sound & disk doesn't work, and many games will crash or doesn't work properly, because this is a beta release (the first beta one). Green links (on left frame) are .TAP files, and the blue ones are .CDT. Please be patient by loading .CDT files, they are very slow and there isn't any notification until loading is done.

Roland has a GPL license, the source code is here. It shares the same Z80 engine as jbacteria and jtandy, but the rest is developed from scratch. There is another CPC emulator, at a very advanced state (disk emulation), so I encourage you to try it.

Instructions:

*Only CPC 464 model supported.
*Keyboard is as in your PC, so the mapping PCKEY -> cpckey is: INS -> copy, ENTER -> return, PC NUMPAD KEYS -> cpc function keys, NUMPAD+ -> enter, DEL -> clr, BACKSPACE -> del.
*F1 for pause emulation, and show the keymap help.
*Supported .CDT and .TAP files from server (.CDTs in blue, .TAPs in green).
*Supported SNA files: load by dragging a local file to emulator window, save with F10.
*Supported memory snapshots: save with F3 and load with F4.
*F5 for reset (normal browser refresh) and F11 for full screen

Format:TAP tape image file format

2011-04-28T14:46:15Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF
^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..
^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:43:03Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF
^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..
^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:39:38Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF

^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..

^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:36:53Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF

^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..

^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:35:27Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF

^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..

^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:34:07Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF

^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..

^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:33:08Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF

^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..

^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:31:19Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF

^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name .^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ..............................................^^
last block (a non-zero value means last block) ...............^^
file type (02 unprotected binary) ...............................^^
data length (88 bytes) .............................................^^^^^
data location (0xAD00) ...................................................^^^^^
first block (a non-zero value means first block) ...............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..

^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:24:49Z

Antoniovillena:

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF
^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name ..^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ............................................^^
last block (a non-zero value means last block) .............^^
file type (02 unprotected binary) .............................^^
data length (88 bytes) ...........................................^^^^^
data location (0xAD00) .................................................^^^^^
first block (a non-zero value means first block) .............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..
^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

Bit 0 Protection If this bit is set the file is protected in some way
Bits 1..3 File contents 0 = Internal BASIC
1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated
Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2

Format:TAP tape image file format

2011-04-28T14:19:44Z

Antoniovillena: Created page with "This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine. = Tape-Image (.TAP) file format = T..."

This document describes the TAP format for use in Amstrad CPC emulators, and a simple way to implement by trapping the ROM loader routine.

= Tape-Image (.TAP) file format =

The .TAP files contain blocks of tape-saved data. All blocks start with two bytes specifying how many bytes will follow (not counting the two length bytes). Then raw tape data follows, starting with the flag byte. Unlike speccy format, the checksum bytes are not included, so you don't need calculate the crc-ccitt every 256 bytes, or padding the last page with zeroes, or ending with four 0xff bytes trailer.

1D 00 2C 50 68 61 6E 74 6F 6D 61 73 32 20 20 20 20 20 20 01 FF 02 58 00 00 AD FF
^^^^^...... first block is 29 bytes (28 bytes+flag)
^^... flag byte (A reg, 2C for headers, 16 for data blocks)
file name ..^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
block number ............................................^^
last block (a non-zero value means last block) .............^^
file type (02 unprotected binary) .............................^^
data length (88 bytes) ...........................................^^^^^
data location (0xAD00) .................................................^^^^^
first block (a non-zero value means first block) .............................^^

58 00 10 AD 59 00 16 06 12 0A 00 2A 02 18 06 1E 07 30 0C 00 0D ..
^^^^^............... logical length, in consecutive blocks (88 bytes)
^^^^^......... execution address for machine code programs (0xAD10)
^^^^^... second block is 89 bytes (88 bytes+flag)
flag byte ........^^
second block data ...^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Note that it is possible to join .TAP files by simply stringing them together.

For example, in DOS / Windows:

COPY /B FILE1.TAP + FILE2.TAP ALL.TAP

or in Unix/Linux:

cp file1.tap all.tap && cat file2.tap >> all.tap

For completeness, I'll include the structure of a tape header. A header always consists of 28 bytes:

Byte Size Name Description

0 16 Filename Padded to 16 bytes with nulls
16 1 Block number Filename (padded with blanks)
17 1 Last block A non-zero value means that this is the last block of a file
18 1 File type A value recording the type of the file (see below)
19 2 Data length The number of data bytes in the data record
21 2 Data location Where the data was written from originally
23 1 First block A non-zero value means that this is the first block of a file
24 2 Logical length This is the total length of the file in bytes
26 2 Entry address The execution address for machine code programs

The file type (byte 18) is split into a number of fields:

----

Bit 0 Protection If this bit is set the file is protected in some way Bits 1..3 File contents 0 = Internal BASIC

1 = Binary
2 = Screen image
3 = ASCII
4..7 are unallocated

Bits 4..7 Version ASCII files should be version 1, all other files, version 0

= Trapping the ROM routine =

The recommendable entry point in the Amstrad CPC ROM is a routine named "CAS READ", that has the next parameters:

A = sync byte
HL = location of data
DE = length of data

So when you trap the routine, you must check that sync byte matches with A register and length of block-1 with DE register. Then copy from file to memory starting at HL address, and finally change the F register to 0x45 (no errors) and the PC with the exit point. Addresses are, in hexadecimal, in the next table:

464 ROM 664 ROM 6128 ROM
Entry Point 2836 29A6 29A6
Exit Point 2872 29E2 29E2