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

https://oldwiki.cpcwiki.eu/api.php?action=feedcontributions&feedformat=atom&user=DavidL CPCWiki - THE Amstrad CPC encyclopedia! - User contributions [en] 2026-08-29T04:50:32Z User contributions MediaWiki 1.25.1 https://oldwiki.cpcwiki.eu/index.php?title=FAQ_-_Frequently_Asked_Questions&diff=102593 FAQ - Frequently Asked Questions 2018-12-30T14:26:16Z

<p>DavidL: /* Amstrad CPC */</p> <hr /> <div>== About ==<br /> <br /> comp.sys.amstrad.8bit Frequently Asked Questions v1.32 (10/16/2005)<br /> The FAQ exists in english, french, german, spanish and dutch. The spanish and german translations arent up to date. They are archived on :<br /> * http://www.genesis8bit.com<br /> * english text only :<br /> ** http://www.faqs.org/faqs/amstrad8bit-faq<br /> ** ftp://rtfm.mit.edu/pub/usenet/comp.sys.amstrad.8bit<br /> <br /> The french translation was done by Pierre Guerrier and then by Pierre Thevenet. Thanks to them.<br /> This FAQ is posted each month on the 4th to comp.sys.amstrad.8bit, comp.answers and news.answers<br /> <br /> * Lines preceded by '+' have been added since the last FAQ<br /> * Lines preceded by '*' have been modified since the last FAQ<br /> * Lines preceded by '-' will be removed in the next FAQ<br /> <br /> This FAQ is written by :<br /> * Emmanuel Roussin, sections A, D, E<br /> * Mark Ray, h089 mth.uea.ac.uk, section B (Notepad)<br /> * Frank van Empel, http://www.fvempel.nl/, section C (PCW)<br /> <br /> All mailto links have been removed, all emails addresses were translated like this : a@b.com is now a b.com<br /> <br /> If you have any ideas for the FAQ, send an email to the correct person. About parts written by E.R., as english isn't my mother tongue, this FAQ has certainly typing mistakes, grammar errors, etc... I welcome the corrections.<br /> <br /> This FAQ is freeware, you can use it freely for your personal use, but we retain the copyright. For commercial use, you must ask our permission before.<br /> <br /> Parts of this FAQ are taken from the documentation of CPCEMU, some are from the main faq keeper (E.R.) and Mark Ray (Notepad part), other parts are taken from articles of the newsgroup.<br /> <br /> ---------------------------<br /> <br /> Introduction<br /> <br /> The vote for the creation of this newsgroup passed on 28th July 1994 with 148:36, it was effectively created on 4th august 1994. It was the idea of Marco Vieth and David Long. This unmoderated newsgroup comp.sys.amstrad.8bit is open to discussions about the Z80 Amstrad computers : CPC (464, 664, 6128, 464+, 6128+), GX4000, PCW (8256, 8512, 9256, 9512, 9512+, 10, 16), NC100/150/200 and PDA600.<br /> <br /> Appropriate topics include, but are not limited to :<br /> <br /> * CPC, GX4000, PCW, NC, PDA hardware and software,<br /> * emulators,<br /> * specific Amstrad CP/M files, overlays...<br /> * ads for selling/buying the relative hardware and software.<br /> etc...<br /> <br /> The only topic that is excluded : discussion of Amstrad PC-compatible (1512, 1640, 2x86, 3x86 and others Amstrad compatible I don't know) because these computers are really compatible, so comp.sys.ibm.pc.* newsgroups must be used, especially comp.sys.ibm.pc.classic<br /> <br /> For questions about these PC see http://web.ukonline.co.uk/cliff.lawson and http://www.seasip.info/AmstradXT<br /> <br /> For easier reading and filtering, please use the following tags at the start of your subject line :<br /> <br /> * announce posts : [announce]<br /> * unrelated topic : [i]<br /> * for buying items : [want to buy]<br /> * for selling items : [want so sell]<br /> * for post in another language : [french], [german], etc..., but put a short summary in english to not ignore people who dont understand your language, also you will get much more help if more people can read your post.<br /> <br /> <br /> == Alan Michael Sugar TRADing ==<br /> <br /> Alan Michael Sugar created his company, and called it using his name : Alan Michael Sugar TRADing, that's Amstrad. More on Amstrad company later.<br /> <br /> == Amstrad CPC ==<br /> <br /> === Amstrad CPC(+), KC compact and GX 4000 presentation 06/30/2003 ===<br /> <br /> They use the Zilog Z80A processor which speed is 4.00MHz. From SOFT968 "The system centres round the Z80A with a 4.00MHz clock". Later it states that "Accesses to memory are synchronised with the video logic, constrained to occur on microsecond boundaries. This has the effect of stretching each Z80 machine cycle to be a multiple of 4 time states (clock cycles) In practice,this alters the instruction timing so that the effective clock rate is approximately 3.3MHz"<br /> <br /> Amstrad made the following CPC systems :<br /> <br /> * CPC 464 (Arnold 1),<br /> * CPC 664 (Arnold 2),<br /> * CPC 6128 (Arnold 3), there was also a CPC6128 cost down (Arnold 4 which was identical in operation to the original 6128 but had a new PCB and ASIC that reduced the board size and chip count to a mere fraction of the original size. If you open up a 6128 and the board fills the entire space you've got one of the originals. If you open one up and the board only occupies about 1/4 to 1/3 of the available space with a LOT of surrounding fresh air then you've got an Arnold 4.<br /> * CPC 464+ (Arnold 5),<br /> * CPC 6128+ (Arnold 6),<br /> * GX 4000, the Amstrad 8 bit console.<br /> <br /> The CPC+ and GX 4000 have enhanced graphics and sound (DMA), colour palette of 4096, hardware sprites, hardware scrolling, and used 128 Ko to 512 Ko carts.<br /> <br /> Amstrad used CRTC (Cathodic Ray Tube Controller) from different manufacturers, which worked the same in the main, but do have many different characteristics. This is the reason why a demo designed for CRTC type 1, may not display correctly (or even at all), on a CRTC type 0 :<br /> <br /> * CRTC 0 : chipset HD6845S, HD6845SP, UM6845<br /> * CRTC 1 : chipset UM6845R,<br /> * CRTC 2 : chipset MC6845, MC6845S, MC6845P<br /> * CRTC 3 : CPC+ ASIC AMS40489<br /> * CRTC 4 : CPC+ pre-ASIC AMS40226<br /> <br /> The KC compact (KC mean KleinComputer = little computer) is a clone of the Amstrad CPC. It was made by VEB Mikroelectronik in East Germany (the old DDR) in 1989. It was made the year before the Berlin wall came down, and ceased production soon after. The KC compact is 95% compatible to the CPC. The functions of the Gate-Array are simulated by TTL-Logic and a Zilog Z8536 CIO. The ROMs are a patched English CPC6128 Operating system ROM (includes setup code for the Z8536) and a unpatched Locomotive BASIC v1.1 rom.<br /> <br /> The only incompatibility lies with the interrupt generation mechanism. Any program that relies on exact interrupt generation behaviour may fail to work.<br /> <br /> In some respects, the KC compact is actually more powerful than the CPC, because the interrupt frequency can be programmed, in theory the resolution could be reprogrammed, and the colour palette changed (replacing the colour rom). More details are available at http://andercheran.aiind.upv.es/~amstrad<br /> <br /> If you can read french and want to learn more about Amstrad CPC history, you should order the excellent book "Ces ordinateurs sont dangereux" by François Quentin (fquentin club-internet.fr) for 25 Euros (postage included, send an international postal order by going to your post office) to :<br /> <br /> François Quentin<br /> 9 Nonneville<br /> 28140 Loigny la Bataille<br /> FRANCE<br /> <br /> == Emulators and utilities ==<br /> <br /> === Emulators ===<br /> <br /> There is a commercial spectrum emulator for the CPC, reviewed in Amstrad Action.<br /> <br /> The best emulator for DOS is Caprice32. For win9x, the emulators are quite good : Arnold, Winape32 and MTMW. All win9x emulators emulates CPC+, NO$CPC is the only DOS emulator which emulates CPC+. On Amiga, Emu-CPC should be the best emulator.<br /> <br /> ==== A1.1.1) CPCEMU (PC) 06/25/98 ====<br /> <br /> CPCEMU by Marco Vieth, last version is 1.5b1, get ftp://ftp.lip6.fr/pub/amstrad/emulator/cpcemu15.zip<br /> <br /> <br /> A1.1.2) Caprice32 (PC) and CPE (for PC and Amiga) and 04/28/2003<br /> <br /> CPE, first written by Bernd Schmidt and then by Ulrich Doewich<br /> (report bugs, suggestions to caprice32 cybercube.com) since v5.1<br /> <br /> Get ftp://ftp.lip6.fr/pub/amstrad/emulator/cpe52.zip, or if you have a<br /> 386, get ftp://ftp.lip6.fr/pub/amstrad/emulator/cpe51.zip<br /> For sources : ftp://ftp.lip6.fr/pub/amstrad/emulator/cpesrc52.zip<br /> <br /> CPE is now replaced by Caprice32, a 32bit emulator for dos (v1.11 or<br /> 2b2) or win9x, get it at :<br /> http://www.caprice32.cybercube.com<br /> <br /> Amiga CPE (68000, 1 Mo), last version is February 95, get<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/acpe_new.lzh<br /> <br /> <br /> A1.1.3) A-CPC (PC) (06/01/97)<br /> <br /> The Amstrad CPC emulator (v0.55beta) by Herman Dullink on PC, get<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/cpc055.zip<br /> <br /> Current beta version is v0.56<br /> <br /> <br /> A1.1.4) PC-CPC (PC) 11/07/2004<br /> <br /> A PC version of AMI-CPC by Ludovic Deplanque (see A1.1.7), go<br /> http://www.chez.com/deplanque/<br /> <br /> <br /> A1.1.5) NO$CPC (PC) 02/04/2001<br /> <br /> A german emulator by Martin Korth, go to http://www.work.de/nocash<br /> <br /> <br /> A1.1.6) Richard Wilson's emulators 12/23/99<br /> <br /> Richard Wilson (author of ParaDOS) wrote no less than 3 emulators, get<br /> them at http://winape.emuunlim.com :<br /> <br /> - RWCPC for msdos : ftp://ftp.lip6.fr/pub/amstrad/emulator/rwcpc.zip<br /> - CPC emulator for windows 3.1, with debugger and assembler :<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/cpcwin10.zip<br /> - WinApe 32, the CPC(+) emulator for win9x, comes with a built-in<br /> compatible Maxam assembler<br /> <br /> <br /> A1.1.7) AMI-CPC (Amiga) 07/11/2004<br /> <br /> A french CPC emulator for Amiga, by Ludovic Deplanque, sources included.<br /> http://www.chez.com/deplanque<br /> <br /> <br /> <br /> A1.1.8) A-CPC (Amiga)<br /> <br /> A CPC emulator for Amiga by Kevin Thacker. Get<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/acpcde20.lha<br /> It's an evaluation version of the real shareware. Don't forget the web<br /> page of Kevin (see A2.2).<br /> <br /> <br /> A1.1.9) Emu-CPC (Amiga) 04/15/99<br /> <br /> Another french CPC emulator on AMIGA by Stephane Tavenard, get EmuCPC<br /> v0.7 at ftp://ftp.lip6.fr/pub/amstrad/emulator/emucpc07.lzx<br /> <br /> <br /> A1.1.10) !CPC (Acorn) 07/18/99<br /> <br /> !CPC is a CPC emulator for Acorn RISC OS machines (Archimedes/RISC PC)<br /> by Mark RISON. Get ftp://ftp.lip6.fr/pub/amstrad/emulator/cpc0728.zip<br /> <br /> Get the sources on Lip6 : ftp://ftp.lip6.fr/pub/amstrad/emulator/cpcs0728.zip<br /> <br /> <br /> A1.1.11) !CPCemu (Acorn)<br /> <br /> This emulator for Acorn RISC OS machines is written by Andreas<br /> Stroiczek, aka Face Hugger. Get v1.10 at<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/cpcem110.zip<br /> or on ftp://ftp.uni-kl.de/pub/acorn/long/emulator<br /> ftp://ftp.uni-stuttgart.de/pub/systems/acorn/riscos/emulator<br /> <br /> <br /> A1.1.12) CPC++ (Unix and MAC) 03/02/2002<br /> <br /> <br /> This emulator for SunOS, Linux and MAC is written by Brice Rive.<br /> Go at http://bricerive.free.fr/cpc<br /> <br /> <br /> <br /> A1.1.13) SIMCPC (PC)<br /> <br /> Presumably the first CPC emulator written, for PC XT/AT by GHE,<br /> Aachen. It is only black and white, with additional ROMs.<br /> Get ftp://ftp.lip6.fr/pub/amstrad/emulator/simcpc.zip<br /> <br /> <br /> A1.1.14) Multi-Machine, or MTM (win9x) 01/11/2000<br /> <br /> Get MTM v1.30b by Paul Hodgson at ftp://ftp.lip6.fr/pub/amstrad/emulator/mtmw130b.zip<br /> <br /> MTM is a win9x multi-machine emulator. It emulates Amstrad CPC(+),<br /> Sinclair ZX80/81 and Spectrum, Jupiter Ace and Elan Enterprise.<br /> It can read .WAV or .CDT (digitalized Amstrad tapes).<br /> <br /> <br /> <br /> A1.1.15) Arnold (win9x, MACos, Unix/Linux), Arnold Jr (Java) 11/08/2004<br /> <br /> A CPC(+) emulator by Kevin Thacker for win9x, get binaries and<br /> sources at http://arnold.emuunlim.com<br /> <br /> Get the MACos conversion by Richard Bannister at http://www.bannister.org/software/emu.htm<br /> <br /> Andreas Micklei is working on the Linux version, get patches at<br /> http://arnold.berlios.de/<br /> <br /> Arnold Junior is a different emulator, the emulation is very simple.<br /> It uses the z80 emulation from Jasper (Spectrum emulator at <br /> http://www.spectrum.lovely.net<br /> The source to Arnold Jnr is available from<br /> http://www.arnoldemu.freeserve.co.uk<br /> <br /> <br /> A1.1.16) Zsim (PC) 05/06/2003<br /> <br /> Zsim v2.42 by Jurgen G. Weber, it simulates a CP/M Z80 machine. It<br /> DOES NOT simulate CP/M. It includes a PD CP/M compatible operating<br /> system and a program to format CP/M disks, so you can run CP/M<br /> programs. It can read DATA and SYSTEM disks directly.<br /> http://www.jwi.de/zsim<br /> <br /> <br /> A1.1.17) Yage (PC) 07/15/99<br /> <br /> Yage v0.91 by Antoine Pitrou, a CPC emulator which handles demos like<br /> 'The demo' and 'divine megademo'. Get<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/yage091.zip<br /> <br /> <br /> A1.1.18) CPCE (msdos/win9x) 05/06/2003<br /> <br /> A spanish Amstrad CPC emulator for msdos/win9x by CNGSOFT, go<br /> http://cpce.emuunlim.com<br /> <br /> <br /> A1.1.19) CPC-emulator (Linux/Unix) 02/05/2001<br /> <br /> CPC-emulator for Linux/Unix with X11 version 023 by Ulrich Cordes,<br /> features .DSK (with large formats : 720 Ko), sound, debugger.<br /> go http://www.amstrad-cpc.de<br /> <br /> <br /> A1.1.20) M.E.S.S. (PC, MAC, Amiga) 10/23/2001<br /> <br /> Multi-Emulator Super System (Amstrad CPC, PCW, and NC) is available<br /> on : http://www.mess.org<br /> <br /> For using PcW16 emulation, get ftp://ftp.lip6.fr/pub/amstrad/misc/pcwos.zip<br /> <br /> <br /> A1.1.21) Arnimedes (PC) 05/06/2003<br /> <br /> Arnimedes for msdos and win9x, by Oliver Lenz, get it at http://www.arnimedes.de<br /> <br /> <br /> A1.1.22) XCPC (Unix/X11R6) 10/24/2001<br /> <br /> An Amstrad CPC emulator by Olivier Poncet for unix and X11R6 at :<br /> http://xcpc.emuunlim.com<br /> <br /> <br /> A1.1.23 CoPaCabana (win9x) 05/06/2003<br /> <br /> A french windows Amstrad CPC emulator at :<br /> http://copacabana.emuunlim.com<br /> <br /> <br /> <br /> <br /> A1.2) Utilities<br /> <br /> A1.2.1) SNA2GIF (PC)<br /> <br /> SNA2GIF v1.1 by Marco Vieth is included in CPCEMU, it extracts<br /> screens from snapshots to GIF format.<br /> <br /> <br /> A1.2.2) SNAP GRAB (PC)<br /> <br /> SNAP GRAB v1.1 is a freeware by Georg Schwarz to extract screens from<br /> snapshots to Multiface II format, which can be seen on real CPC even<br /> with a multiface. If you want to see the picture on your PC, you will<br /> need CPC2x (see A1.2.3), get SNAPGR11.ZIP.<br /> <br /> <br /> <br /> A1.2.3) CPC2x (was CPC to TIFF) (PC)<br /> <br /> CPC2x v2.0 by Michael Stroucken converts Amstrad CPC screens to the<br /> graphic TIF and GIF format. Get CPC2X.ZIP with sources and<br /> binaries for MSDOS and CP/M.<br /> <br /> <br /> A1.2.4) CPC file system (PC) 06/08/2004<br /> <br /> CPCfs v0.85.3 by Derik van Zutphen, it transfers CPC files between .DSK<br /> files and DOS files, in the two ways. There is a useful batch mode.<br /> http://www.426.ch/cpcfs/<br /> <br /> Better get CPCXFS, the updated version by Kevin Thacker which<br /> supports now extended .DSK, bugs removed, other updates, at :<br /> http://andercheran.aiind.upv.es/~amstrad<br /> <br /> <br /> <br /> A1.2.5) Multiface II to Snapshot (PC)<br /> <br /> M2TOSNA v1.1 by James McKay converts CPC Multiface II files to 64<br /> Ko and 128 Ko snapshots files. Look for M2TOSNA1.ZIP.<br /> <br /> <br /> A1.2.6) CPDread and CPDwrite (PC) 06/03/99<br /> <br /> Copy Protected Disk reader v3.24 by Ulrich Doewich, for transferring<br /> CPC disks into the common DSK file format of CPC emulators. It uses<br /> the extended DSK format which manages copy protected disks better.<br /> Get CPDR324.ZIP<br /> <br /> CPDwrite v1.03, for writing back .DSK to a disk, even with protected<br /> games, get CPDW103.ZIP<br /> <br /> <br /> A1.2.7) MACTerm (MAC)<br /> <br /> Transfer files between CPC and MAC with a parallel cable, get CPCTERM.ZIP<br /> <br /> <br /> A1.2.8) 22disk (PC) 08/06/2000<br /> <br /> 22disk is a shareware utility by Sydex (http://www.sydex.com) which<br /> can read/write/format CP/M disks on PC. It can read CPC disks formats<br /> with a file called CPMDISKS.DEF which comes with CPCEMU, or EURO.DEF<br /> (ftp://ftp.lip6.fr/pub/amstrad/emu-uti/eurodef.zip) or my<br /> own file (ftp://ftp.lip6.fr/pub/amstrad/emu-uti/gen8-def.zip).<br /> You shouldn't use it under OS/2 or win95, unless you have the last<br /> version (ftp://ftp.lip6.fr/pub/amstrad/emu-uti/22dsk144.zip).<br /> <br /> Sydex has removed 22disk since 2000 from public distribution, but is<br /> still for sale on their web site.<br /> <br /> <br /> <br /> A1.2.9) DIC (PC) 06/14/97<br /> <br /> Disc Image Copier by Tim Rieman, transfer DATA and SYSTEM disc from<br /> CPC to PC with a parallel cable, get :<br /> ftp://ftp.lip6.fr/pub/amstrad/emu-uti/dic130.zip<br /> <br /> For conversion from PC to CPC, see A1.2.11<br /> <br /> <br /> A1.2.10) AIFF decoder (Unix, PC, Amiga) 02/28/2000<br /> <br /> AIFF decoder by Pierre Guerrier, a tool for retrieving data from<br /> sampled Amstrad CPC tapes, C sources included. Get programs from :<br /> <br /> - MSDOS port v1.2 by Ulrich Doewich :<br /> ftp://ftp.lip6.fr/pub/amstrad/emu-uti/pcdcdr12.zip<br /> - Amiga port by Kevin Thacker :<br /> ftp://ftp.lip6.fr/pub/amstrad/emu-uti/amiaiff.lzh<br /> <br /> A1.2.11) PC2CPC (PC)<br /> <br /> PC2CPC v2.0 by James Churchill converts CPC emulator EDSK images to 3"<br /> disks via the CPCEMU parallel link, look for<br /> ftp://ftp.lip6.fr/pub/amstrad/emu-uti/pc2cpc.zip<br /> <br /> For conversion from CPC 3" disk to PC .DSK see A1.2.9<br /> <br /> <br /> A1.2.12) DSK-CPC (CPC) 09/01/99<br /> <br /> DSK-CPC by Divine Coding reads a .DSK or .EDSK image from a 3.5" <br /> 720Kb DOS disc in drive B and writes the image to a CPC disc, thus<br /> recreating the original software disc. It can can cope with copy-<br /> protected software. Get it at : <br /> ftp://ftp.lip6.fr/pub/amstrad/disk/DSK-CPC.ZIP<br /> <br /> <br /> A1.2.13) CPCKEY (PC) 06/08/2001<br /> <br /> CpcKey v0.3 for msdos use the CPCEMU parallel link for :<br /> <br /> - command/replace CPC keyboard with the PC keyboard,<br /> - send files between CPC and PC<br /> - modify the CPC memory, poke during games<br /> - automatic procedures, etc...<br /> - compatible Intel HEX format<br /> <br /> <br /> A1.2.14) SEND2 (CPC) 06/15/97<br /> <br /> SEND2 v1.2 by J.GUEZENNEC (jguezenn icor.fr) is a complete parallel<br /> transfer package which is an amelioration of CPCPARA.BAS :<br /> <br /> - 3" disk transfer (DATA, SYSTEM, IBM),<br /> - ROM transfers,<br /> - tape transfers.<br /> <br /> <br /> A1.2.15) TransCPC<br /> <br /> CPC transfile project, a project aimed at simulating a small file<br /> system on the Amstrad CPC with the files being stored on a PC hard<br /> disk. The project is complete, there is no plan to improve it. Get<br /> ftp://ftp.lip6.fr/pub/amstrad/emulator/transcpc.zip<br /> The CPC asm code needs Devpac or similar to be compiled, and any PC<br /> assembler for the PC asm code.<br /> <br /> <br /> A1.2.16) ReadScr (PC)<br /> <br /> A PC utility for ms-dos by Ark for viewing Amstrad CPC screens, with<br /> palettes or not, get ftp://ftp.lip6.fr/pub/amstrad/graphic/readscr.zip<br /> <br /> <br /> A1.2.17 CPC2TAPE (PC) 08/16/99<br /> <br /> A dos utility (comes with C sources) to transfer Amstrad files from<br /> a PC to the CPC directly via the sound card, or to tapes, get<br /> ftp://ftp.lip6.fr/pub/amstrad/emu-uti/cpc2tape.zip<br /> <br /> <br /> A1.2.18) SLIP/IP stack 04/24/99<br /> <br /> A SLIP/IP stack developped by Mark Rison for Amstrad<br /> CPC6128s with Amstrad serial interfaces. Using this, you can<br /> establish a SLIP connection from your Amstrad and then ping it. To<br /> * find out more, go to http://www.nenie.org/cpcip/<br /> <br /> It's probably easiest if you connect your CPC to a Linux box,<br /> using a null modem, and the instructions assume this, but there's<br /> no reason in principle why you couldn't connect via a modem.<br /> <br /> <br /> <br /> A2) Sources of emulators, ROMs and programs<br /> <br /> ROMs are now included with CPCEMU and CPE, with the permission of<br /> Amstrad and Locomotive Software.<br /> <br /> If you have ROMs on a romboard, you can get them for use with an<br /> emulator, get CPCEMU, it comes with a basic program to transfer a ROM<br /> to a file.<br /> <br /> <br /> A2.0) IRC 07/24/2004<br /> <br /> You can exchange files with Internet Relay Chat, but its primary goal<br /> is to chat with other internet users.<br /> <br /> - #CPC, every days on IRCNet<br /> - #CPC, on irc.emm.fr<br /> - #CPC on irc.neoxys.org port 6667<br /> <br /> <br /> <br /> A2.1) FTP sites 07/31/2004<br /> <br /> If you have problems accessing FTP sites, use the following method :<br /> <br /> ftp://anonymous@ftp.lip6.fr/pub/amstrad/emulator/cpcemu15.zip<br /> <br /> - ftp://ftp.lip6.fr/pub/amstrad, thanks to Remy Card,<br /> http://genesis8.free.fr/files.php (HTML front-end with<br /> the list of all files, size and description included).<br /> <br /> all questions about this site should be directed to roussin noos.fr<br /> <br /> - ftp://andercheran.aiind.upv.es/pub/cpc/ADATE, thanks to Sergio Bayarri<br /> or creating the site, and to Kevin Thacker for maintaining it. Send<br /> what you have in /pub/cpc/ADATE/incoming. This site contains tape<br /> images (.cdt) and disk images (.dsk). The aim of this site is to<br /> preserve games, so only original games are allowed. No hacked or<br /> modified games will be allowed. Please see the documentation at this<br /> site about creating tape-images using existing tools. (voc2tzx)<br /> <br /> - ftp://ftp.nvg.ntnu.no/pub/cpc, thanks to Arnt Gulbrandsen for<br /> creating the site, and to Nicholas Campbell for maintaining it.<br /> Send what you have in /pub/cpc/incoming or email to nich otto.org,<br /> look for the HTML front-end : http://tacgr.emuunlim.com<br /> <br /> - ftp://ftp.math.uni-hamburg.de/pub/misc/cpc_emu<br /> mirror of ftp.nvg.ntnu.no<br /> <br /> - ftp://ftp.demon.co.uk/pub/cpm, thanks to Paul Martin, specific<br /> Amstrad CP/M related files.<br /> <br /> - http://www.cantrell.org.uk/mirrors, mirror of lip6 and nvg<br /> <br /> - Two Mag FTP site<br /> <br /> <br /> A2.2) WWW 07/24/2004<br /> <br /> You will find them at :<br /> <br /> - http://genesis8.free.fr<br /> the FAQ maintainer homepage with Amstrad news and more !<br /> <br /> Three other important web sites :<br /> <br /> - http://www.amstrad.com<br /> the official Amstrad web site<br /> <br /> - http://andercheran.aiind.upv.es/~amstrad<br /> the biggest Amstrad web page by Kevin Thacker<br /> <br /> - http://web.ukonline.co.uk/cliff.lawson/<br /> Cliff Lawson's site about all Amstrad computers range, even the PC ones <br /> <br /> <br /> A2.3) BBS 07/31/2004<br /> <br /> Informations removed indefinitely.<br /> <br /> <br /> A2.4) Using programs with emulators or real CPC<br /> <br /> A2.4.1) DSK files<br /> <br /> These files are images of a disk, you "insert" a disk with F3 in<br /> CPCEMU, and F6 with CPE, then you can type CAT to see the files,<br /> RUN"file_name" to run a program (.BAS or .BIN).<br /> <br /> <br /> A2.4.2) CPC files 11/07/2004<br /> <br /> Three solutions to use plain CPC files :<br /> <br /> a) put them in the TAPE directory, type |TAPE then the usual RUN"<br /> <br /> b) WinAPE comes with a ROM image called CPCDOS. Simply select the ROM<br /> (probably best below AMSDOS in ROM 6), then you can use |DOS,<br /> |DOS.IN, |DOS.OUT, |CD<br /> <br /> c) inject them in a .DSK file with CPCFS (see A1.2.4) :<br /> <br /> - create an empty .DSK : CPCFS -nd empty.dsk (you can omit the .dsk)<br /> - inject files : CPCFS empty -mp *.* (the files must be in the<br /> current directory, the DSK can be somewhere else)<br /> <br /> To extract files from a .DSK : CPCFS image.dsk -mg *.*<br /> <br /> XTI by Pierre Guerrier can also put amsdos files into a DSK.<br /> Note that there are MAC and Amiga ports of XTI.<br /> <br /> <br /> <br /> A2.4.3) How to run programs with a CPC or emulator ?<br /> <br /> Type CAT to get the directory of the disk, mostly programs are run<br /> with a BASIC loader, so looks for *.BAS, then type RUN"name.BAS" (.BAS<br /> can be omitted). If there isn't a basic loader, run the .BINary<br /> program directly : type RUN"name.BIN" (.BIN can be omitted).<br /> <br /> Some disks doesn't have a real directory, and must be launched with<br /> the CP/M command : |CPM.<br /> <br /> For running tapes on a real CPC, type RUN", the CPC will launch the<br /> first program on the tape.<br /> <br /> <br /> A2.4.4) How to format a disk 01/03/2003<br /> <br /> On a CPC, use the formatting utility on your CP/M disk (diskit) or<br /> the following basic program :<br /> <br /> 5 ' QuickFormat by Adrian Forbes<br /> 10 MODE 1:PRINT"Please Wait..."<br /> 20 GOSUB 150<br /> 30 MODE 1<br /> 40 INPUT "(D)ata or (V)endor";f$<br /> 50 PRINT "Sure (Y/N)"<br /> 60 a$=INKEY$:IF a$="" THEN 60<br /> 70 IF LOWER$(a$)<>"y" THEN GOTO 60<br /> 80 MODE 1<br /> 90 PRINT"Insert disc to format in drive A":PRINT"Then press a key..."<br /> 100 CALL &BB18<br /> 110 MODE 1<br /> 120 PRINT"Formatting..."<br /> 130 |QF,f$<br /> 140 GOTO 30<br /> 150 ch=0<br /> 160 add=&4000<br /> 170 ln=310<br /> 180 FOR x=1 TO 8<br /> 190 READ a$:a=VAL("&"+a$)<br /> 200 POKE add,a<br /> 210 add=add+1<br /> 220 ch=ch+a<br /> 230 NEXT<br /> 240 READ ch$<br /> 250 IF ch 'put 'not equal to' here, cant do it in HTML' VAL("&"+ch$) THEN PRINT"Error in line";ln:END<br /> 260 ln=ln+10<br /> 270 ch=0<br /> 280 IF ln 'put "not equal to' here, cant do it in HTML' 510 THEN GOTO 180<br /> 290 CALL &4000<br /> 300 RETURN<br /> 310 DATA 21,8D,40,01,91,40,C3,D1,354<br /> 320 DATA BC,FE,01,C0,21,9A,40,06,37C<br /> 330 DATA 09,36,00,23,36,00,23,36,F1<br /> 340 DATA 00,23,36,02,23,10,F2,21,1A1<br /> 350 DATA 88,40,CD,D4,BC,22,89,40,410<br /> 360 DATA DD,6E,00,DD,66,01,23,5E,310<br /> 370 DATA 23,56,1A,FE,44,CA,80,40,35F<br /> 380 DATA FE,64,CA,80,40,3E,41,32,39D<br /> 390 DATA 8C,40,11,00,00,06,28,C5,1D0<br /> 400 DATA 21,9A,40,7A,06,09,77,23,21E<br /> 410 DATA 23,23,23,10,F9,3A,8C,40,278<br /> 420 DATA 06,05,21,9C,40,CD,73,40,288<br /> 430 DATA 06,04,21,A0,40,CD,73,40,28B<br /> 440 DATA 21,9A,40,DF,89,40,14,C1,378<br /> 450 DATA 10,D5,C9,77,23,23,23,23,2B1<br /> 460 DATA 23,23,23,23,3C,10,F4,C9,295<br /> 470 DATA 3E,C1,32,8C,40,C3,3F,40,33F<br /> 480 DATA 86,00,00,07,00,00,00,00,8D<br /> 490 DATA 00,97,40,C3,09,40,C9,51,2FD<br /> 500 DATA C6,00,20,00,00,00,00,00,E6<br /> 510 DATA end<br /> <br /> On a PC, use 22disk, look for A128<br /> <br /> <br /> A2.5) Buying hardware/software<br /> <br /> A2.5.1) Auctions sites<br /> <br /> Auctions sites like http://www.ebay.com are good places to find<br /> hardware and software<br /> <br /> <br /> A2.5.2) Emmaüs (only in France)<br /> <br /> It's possible to find interesting things in Emmaüs shops, like at<br /> Trappes http://www.emmaus-trappes.com/informatique <br /> <br /> <br /> A2.5.3) Tradinpost<br /> <br /> - You can buy a selection of games cartridges for the CPC+ and the<br /> GX4000, cartridges are unboxed and without instructions. Price £7.99<br /> each including postage and packing in United Kingdom, also programs<br /> for CPC/PCW, go at http://www.tradeinpost.com<br /> <br /> John Thackeray (email : Tradingpost btinternet.com)<br /> Trade in Post<br /> Victoria Road<br /> Shifnal<br /> Shropshire TF11 8AF<br /> Tel/Fax : 00 44 (0)1952 462135<br /> <br /> <br /> A3) Transfer between CPC and PC<br /> <br /> Later mentions of DDI-1 can also be replaced by FD-1 (which comes<br /> without the interface for the 464)<br /> <br /> A3.1.1) 3" drive on PC (part one) 10/22/2002<br /> <br /> * A working solution on http://www.fvempel.nl/3pc.html<br /> <br /> <br /> <br /> A3.1.2) 3" drive on PC (part two) 01/11/2000<br /> <br /> Porting files across from CPC to PC is easy, at least, if you have<br /> a DDI-1 disk drive ! You need to follow exactly these instructions.<br /> As is usual with things like this, you do everything entirely at your<br /> own risk. I have done this on my own PC without damaging it, but<br /> cannot guarantee that it will work with yours. If you do damage your<br /> computer, it is YOUR FAULT.<br /> <br /> Note of the FAQ keeper, I have a report of someone trying out the<br /> following instructions, who had his controller burnt, and another<br /> whose 3" drive died, so beware.<br /> <br /> These instructions only apply to the DDI-1 package. They MAY work with<br /> the FD1 3" second drive, and will definitely NOT work with the<br /> internal drives on 6128s, 664s, and 6128+s.<br /> <br /> Install 22DISK! You will need to tell it you have no A: drive, and<br /> that B: is a 360K drive, physical unit 0, on the Primary adapter, with<br /> step-rate of 12 milli-seconds. You will also need the CPMDISKS.DEF<br /> file from CPCEMU.<br /> <br /> 0 Install 22DISK with CPMDISKS.DEF coming with CPCEMU or the one from<br /> EURODEF.ZIP<br /> <br /> 1 open your PC, following all usual precautions such as turning off<br /> the power and discharging any static electricity on your body!<br /> <br /> 2 Unplug any floppy drives. This step is important. (See note 1)<br /> <br /> 3 Find the connector that is meant for the B: drive. (It is probably<br /> on the same cable as the connector for the A: drive. The A: connector<br /> has a twist in it. The B: connector is the other one!)<br /> <br /> 4 Plug it into your DDI-1 drive unit. You may have to file the keyway<br /> on the connector off. (Different PCs have different keyways on their<br /> connectors, so you may not have to attack it with a file. So much for<br /> standardisation!)<br /> <br /> 5 Turn the DDI-1 drive on first, then the PC. When it does the<br /> Power-on test, press DEL to enter the setup menu (you have got an AMI<br /> BIOS haven't you?). Tell it you have no A: drive and a 360K 5.25" B:<br /> drive. (See note 2)<br /> <br /> 6 Use 22DISK to read (not under OS/2 or windows 95), write and format<br /> your 3" disks to your heart's content ! You could also use ANADISK I<br /> suppose.<br /> <br /> 7 When you've finished, restore the machine its original state. As<br /> well as using CPC disks, you'll probably be able to use Spectrum 3<br /> disks if you have an appropriate CPMDISKS.DEF. If of course you want<br /> to use Speccy disks...<br /> <br /> Note 1 : Amstrad's disk drive is reasonably standard, but not quite!<br /> When you install it, it claims to be both your physical drive 0 and<br /> physical drive 1. As such, if you expect it to be just drive 1 (B:),<br /> and leave unit 0 (A:) still plugged in, it will promptly ram the heads<br /> of unit 0 hard against the end stop, promptly trashing your unit 0. I<br /> found this the hard way, and had to buy a new 3.5" floppy drive.<br /> <br /> Note 2 : If you don't have an AMI BIOS, then this will be different.<br /> You may have to run a program from a system disk which came with your<br /> computer.<br /> <br /> The pin-outs of the 3" drive are _identical_ to the ones of a 5.25"<br /> drive - it will just plug in. It's a long time since I was inside my<br /> Einstein, but I'm pretty sure that drive is a 40track SS unit - what a<br /> PC would call a 180K drive. Things like the Disk Change line may be<br /> different, but if you set up your PC to ignore that (and possibly tell<br /> it it's a 360K drive), you should be OK.<br /> <br /> I've used a 3" drive (actually a Double-sided model) with an original<br /> IBM XT in this way.<br /> <br /> A reply to the last two paragraphs :<br /> <br /> It actually depends on the type of 3" drive. Some of them had a 34 way<br /> connector like the IBM PC 5.25 " drive (i.e. PCB gold plated edge<br /> connector) and are compatible. Genuine Amstrad drives on the other hand<br /> have a 26-way PCB header which contains all the useful signals, although<br /> some have been removed.<br /> <br /> I remember, that the 34 way connectors are only nearly compatible. In<br /> those days around 1985, I connected a CPC 464 External drive to<br /> another CPM computer with standard 5.25" drives like the PC-drives.<br /> It was necessary to swap the lines since the pin numbering was mirrored<br /> compared to the standard.<br /> <br /> I also think that the exact layout depends on the version of the<br /> computer (CPC 464/664/6128). So be careful and do not ruin your<br /> hardware by building sh circuits! (It shouldn't be very difficult to<br /> verify which are the GND-lines )<br /> <br /> A complement to this reply<br /> <br /> The Amstrad and PC disk connections are as follows:<br /> <br /> 26 pin Amstrad disk drive:<br /> <br /> Index 2 * * 1 GND<br /> DS0 4 * * 3 GND<br /> DS1 6 * * 5 GND<br /> Motor 8 * * 7 GND<br /> Dirn 10 * * 9 GND<br /> Step 12 * * 11 GND<br /> Wdata 14 * * 13 GND<br /> Wenable 16 * * 15 GND<br /> Track0 18 * * 16 GND<br /> WProt 20 * * 19 GND<br /> Rdata 22 * * 21 GND<br /> Side 24 * * 23 GND<br /> N.C ? 26 * * 25 GND<br /> <br /> 34 pin Standard disk drive:<br /> <br /> Head Load 2 * * 1 GND<br /> In Use ? 4 * * 3 GND<br /> DS3 6 * * 5 GND<br /> Index 8 * * 7 GND<br /> DS0 10 * * 9 GND<br /> DS1 12 * * 11 GND<br /> DS2 14 * * 13 GND<br /> Motor 16 * * 15 GND<br /> Dirn 18 * * 17 GND<br /> Step 20 * * 19 GND<br /> Wdata 22 * * 21 GND<br /> Wenable 24 * * 23 GND<br /> Track0 26 * * 25 GND<br /> WProt 28 * * 27 GND<br /> Rdata 30 * * 29 GND<br /> Side 32 * * 31 GND<br /> N.C. ? 34 * * 33 GND<br /> <br /> Note that on the Amstrad drive, DS3 and DS2 are missing.<br /> <br /> The pins marked with a ? may have been redefined on some<br /> drives (e.g. on high density PC drives, one of them is used<br /> to change the drive current - I can't remember which now),<br /> also on very old single sided drives, the Side signal used to<br /> be used to reset the drive. If you are using a 34 way<br /> connector drive in an Amstrad, you may want to hard wire<br /> Head Load to be permanently enabled (if it is used - not<br /> all drives do).<br /> <br /> <br /> <br /> A3.1.3) 3" drive on PC (part three) 02/17/98<br /> <br /> Here is other information by Juan Perez Delgado, as I know nothing<br /> of hardware, be cautious. This doesn't apply for Schneider drives.<br /> <br /> 1. Read all first<br /> <br /> 2. Then you open your PC, and unplug and take off the cable that goes<br /> from the FD controller to the FD drives. The cable looks something<br /> like this: (including the twist between the B: and A: connectors)<br /> (ctlr = Floppy Disc Controller)<br /> <br /> to FD ctler to B: drive to A: drive<br /> /-\ /-\ /-\<br /> 2 -|---------|-|---------|-|2<br /> 4 -|---------|-|---------|-|4<br /> 6 -|---------|-|---------|-|6<br /> 8 -|---------|-|---------|-|8<br /> 10-|---------|-|-\ /----|-|10 ) 16 of ctler, A: thinks it is 10<br /> 12-|---------|-|- \/ ----|-|12 ) 14 of ctler, A: thinks it is 12<br /> 14-|---------|-|- /\ ----|-|14 ) 12 of ctler, A: thinks it is 14<br /> 16-|---------|-|-/ \----|-|16 ) 10 of ctler, A: thinks it is 16<br /> 18-|---------|-|---------|-|18<br /> 20-|---------|-|---------|-|20<br /> 22-|---------|-|---------|-|22<br /> 24-|---------|-|---------|-|24<br /> 26-|---------|-|---------|-|26<br /> 28-|---------|-|---------|-|28<br /> 30-|---------|-|---------|-|30<br /> 32-|---------|-|---------|-|32<br /> 34-|---------|-|---------|-|34<br /> \-/ \-/ \-/<br /> <br /> 3. Using a screwdriver and a cutter I reordered the wires that go to<br /> the A: drive (I left some of them not connected):<br /> <br /> to FD ctler. to B: drive to A: drive<br /> /-\ /-\<br /> 2 -|---------|-|------- You can see that signals<br /> 4 -|---------|-|------- 2,4,6,10(16 from the ctler)<br /> 6 -|---------|-|------- are not used.<br /> 8 -|---------|-|---------\<br /> 10-|---------|-|-\ /-nc \-|-| 2 (connected to ctler pin 8)<br /> 12-|---------|-|- \/ -------|-| 4<br /> 14-|---------|-|- /\ -------|-| 6<br /> 16-|---------|-|-/ \-------|-| 8<br /> 18-|---------|-|------------|-| 10<br /> 20-|---------|-|------------|-| 12<br /> 22-|---------|-|------------|-| 14<br /> 24-|---------|-|------------|-| 16<br /> 26-|---------|-|------------|-| 18<br /> 28-|---------|-|------------|-| 20<br /> 30-|---------|-|------------|-| 22<br /> 32-|---------|-|------------|-| 24<br /> 34-|---------|-|------------|-| 26<br /> \-/ \-/ |-| 28<br /> |-| 30<br /> |-| 32<br /> |-| 34<br /> \-/<br /> <br /> Of course, odd pins must be connected to wires of ground (odd<br /> pins in the drive with odd pins in the ctler, doesn't matter the<br /> number).<br /> <br /> 4. Next, you open the CPC6128, and get the 3"FD, unplug only the cable<br /> that comes from the controller (the one in the 26-pin connector).<br /> <br /> 5. Plug-in the cable you have 'build' in step 3 to the FD cntler (as it<br /> was before you disconnected it), and connect the CPC 3"FD to the<br /> connector whose wires you have reordered. As the connector is 34 pin<br /> wide, and the drive is 26-pin, there will be a side not connected<br /> (corresponding to pins 28 to 34).<br /> <br /> Now you have the controller cable from the PC controller connected to<br /> the 3" drive. I think you can still connect another driver to the<br /> other free connector, but I didn't try it because I read some people<br /> have burned its controller doing similar things. You leave the power<br /> cable of the 3" drive connected to the CPC, as it was before.<br /> <br /> 6. Now, you switch on your CPC (monitor, then keyboard). The FD will<br /> start running continuously.<br /> <br /> 7. Now, you switch on your PC. If all is Ok, nothing should burn :), and<br /> the 3" FD will stop running. Then in the bios setup you tell you have<br /> a 360Kb 5.25" drive A. You boot the PC again if needed.<br /> <br /> 8. In order to use with CPDRead, you must set your drive<br /> (cpdread.cfg) as a 360Ko drive with 360Ko disks, and you must set<br /> #STEP to 2)<br /> <br /> #STEP set to 1 worked for somebody else.<br /> <br /> <br /> <br /> A3.2.1) 3,5" or 5,25" drive on CPC 06/29/98<br /> <br /> See A5.2 after installing your new drive.<br /> <br /> You can use a 3.5" or 5.25" drive on a CPC. You have to take care<br /> about the cabling, as some 6128s use a 36 pin port and the drive only<br /> has 34. A normal PC floppy cable (5 connector) can be used to connect<br /> drives, although some connectors may need changing. The six problems<br /> which can arrive are:<br /> <br /> - The drive has no ready signal. That is true for some older PC<br /> drives. In this case, forget it, if you are not able to solder some<br /> IC's to simulate the signal.<br /> <br /> - You can only use one side of the disk (180k). If you want to use<br /> both sides, you have to solder in a switch, or get another DOS<br /> (Vortex XDOS or Dobbertin X-DDOS), the best DOS is ParaDOS.<br /> <br /> - High-density drives have a hi/lo signal not present on CPCs which<br /> may cause problems, it is probably best to use older 720k drives.<br /> <br /> - Some 5.25" drives, namely 720k QD drives, may cause problems,<br /> however these are not very common and so shouldn't be a cause for<br /> concern.<br /> <br /> - Drives may not work properly on the CPC by giving read errors and<br /> seek errors, etc. The first thing to do in this event is to clean<br /> the edge connector on the CPC with some IPA (head cleaner fluid),<br /> and then clean the drive heads in the same way if necessary.<br /> <br /> - The jumper setting on the drive is wrong. On older 5.25" drives<br /> you may find that they have been set to Drive 0 (DS0), in which case<br /> you need to set the drive to drive 1 (DS1) or use a PC drive cable<br /> which has a twist in it.<br /> <br /> To copy disks from 3" in drive A to 3.5"/5.25" in drive B <br /> the best method is to use Disckit2/3 that comes with CP/M, depending on<br /> which version you have. If Disckit3 doesn't work, Procopy can tackle<br /> most disks, and runs from drive B so you can copy it across to your CPC<br /> fairly easily. You can read the CPC disks on the PC with 22DISK from<br /> Sydex, or Ulrich Doewich's CPDRead, see A1.2.6 and A1.2.8.<br /> <br /> The following diagram is a pin table comparing a modern 1.44Mb 3.5"<br /> drive to the drive B connector on a CPC, which you may find useful.<br /> Note that although the CPC connector is numbered backward, it is still<br /> directly compatible.<br /> <br /> 1.44Mb 3.5" drive: CPC drive B connector<br /> <br /> All odd pins: Ground -------------> All even pins: Ground<br /> 2: Hi/lo density -----------------> 33: N/C<br /> 4: N/C ---------------------------> 31: N/C<br /> 6: N/C ---------------------------> 29: N/C<br /> 8: Index -------------------------> 27: Index<br /> 10: Motor enable A ---------------> 25: N/C<br /> 12: Drive select B ---------------> 23: Drive select 1 (B)<br /> 14: Drive select A ---------------> 21: N/C<br /> 16: Motor Enable B ---------------> 19: Motor On<br /> 18: Direction select -------------> 17: Direction Select<br /> 20: Head Step --------------------> 15: Step<br /> 22: Write data -------------------> 13: Write data<br /> 24: Write gate -------------------> 11: Write gate<br /> 26: Track 00 ---------------------> 9: Track 0<br /> 28: Write protect ----------------> 7: Write protect<br /> 30: Read data --------------------> 5: Read data<br /> 32: Head select ------------------> 3: Side 1 select<br /> 34: Disk change ------------------> 1: Ready<br /> <br /> A detailed guide more specific to 5.25" drives can be found at the All<br /> Things CPC website, and there is also information at the other CPC<br /> sites, see A2.2.<br /> <br /> <br /> A3.2.2) 3,5" or 5,25" drive on CPC+ (by Simon Matthews)<br /> <br /> See A5.2 after installing your new drive.<br /> <br /> Adding a 3.5" drive to the CPC 6128 was a doddle - 34 way card edge<br /> connector on one end, 34 way IDC on the other end and you were away.<br /> <br /> The numbering on the pins was pretty easy, too. Looking at the<br /> connector from the BACK of the machine, Pins 1 to 33 (odd) ran from<br /> left to right along the bottom, pins 2 to 34 (even) ran from left to<br /> right along the top. All of the top pins were grounded, and pin 1<br /> (bottom left) was the READY line, which by convention would be denoted<br /> by the "stripe" of the ribbon cable. At the other end, a simple IDC<br /> plug connected to the external drive, usually with the "stripe"<br /> nearest to the power connector.<br /> <br /> The problem with the CPC+ is that the connector on the back of the<br /> computer is 36-way, not 34 and is numbered back to front as well. So,<br /> looking at the connector from the BACK of the machine again, pins 1 to<br /> 35 (odd) ran from RIGHT TO LEFT on the top of the connector, and pins<br /> 2 to 36 (even) ran from RIGHT TO LEFT on the bottom of the connector.<br /> Again, all of the even pins were grounded. Here's where it gets<br /> tricky...<br /> <br /> This time, pin 33 is READY, pin 31 is SIDE 1 SELECT all the way to pin<br /> 7 which is INDEX. In other words, the lines are in the same order,<br /> but different pin numbers. It all sounds quite hectic, but it's easy<br /> to sort out in practice.<br /> <br /> Firstly, take a length of 34-way ribbon cable and crimp the 34-way<br /> IDC connector on as usual. At the other end, peel away the cable on<br /> the other side of the "stripe" for a few centimetres. Now<br /> place this cable in the 36way Amphenol connector so that the stripe<br /> corresponds to pin 33; in other words, make sure the LEFTMOST 3<br /> blades are left empty. The other edge of the cable should be lying on<br /> the RIGHTMOST blade, with the wire you peeled away not connected to<br /> anything.<br /> <br /> ||||||||||||||||||||||||||||||||||<br /> "stripe" --->|||||||34 WAY RIBBON CABLE||||||||<br /> ||||||||||||||||||||||||||||||||||<br /> ||||||||||||||||||||||||||||||||| \<br /> ||||||||||||||||||||||||||||||||| \ <--- Peel away<br /> |||||||||||||||||||||||||||||||||<br /> Goes to pin 33->||||||||||||||||||||||||||||||||| <--- Goes to pin 1<br /> |||||||||||||||||||||||||||||||||<br /> pin 35 --------------------------------------- pin 1<br /> \ /<br /> \ 36 WAY AMPHENOL CONNECTOR /<br /> pin 36 ------------------------------------- pin 2<br /> <br /> * LEFTMOST 3 pins (36,35,34) NOT CONNECTED *<br /> <br /> Double check all is Ok, then crimp together. Now you can test the<br /> cable on your external drive. If the drive is unresponsive, or just<br /> spins constantly, try plugging the IDC cable in the other way around;<br /> most drives want the "stripe" nearest to the power connector, but a<br /> few want it the other way around.<br /> <br /> I know it sounds complex, but have a look at the pin-out diagrams and<br /> it's not too bad.<br /> <br /> <br /> A3.3) parallel cable 06/08/2001<br /> <br /> The CPCEMU emulator has documentation on how to make such<br /> a cable yourself and includes utilities for both the PC and CPC that<br /> allow two-way communication and file transfer. However CPCPARA.BAS<br /> supplied in this package can extract files from CPC disk drives, not<br /> those saved on cassette tape. For files on tape, see A1.2.14.<br /> <br /> following line to be removed on next FAQ<br /> See A8.1.1.1 for getting this cable in France.<br /> <br /> If you have a problem with PCPARA.BAS, coming with CPCEMU, load the<br /> program into the emulator (put it in the TAPE directory) and save it<br /> as an ascii file with this command : SAVE"PCPARA.BAS",A<br /> or use SEND2<br /> <br /> <br /> A3.4) RS 232 & RS 422<br /> <br /> Neither the CPC nor the PCW have a RS 232. You can buy it, you then<br /> just need a communication program on PC and CPC/PCW and a null modem<br /> cable to exchange files between the computers.<br /> <br /> Get ftp://ftp.lip6.fr/pub/amstrad/misc/rs232cpc.lzh for a circuit plan for<br /> a RS 232 interface, by Tim Riemann.<br /> <br /> <br /> A3.5) Companies<br /> <br /> Commercial companies can transfer your files<br /> <br /> A3.5.1) Locoscript Software (was Locomotive Software) 05/08/2000<br /> <br /> The Locomotive name and products has been sold to SD Micros (SD<br /> Microsystems Ltd). For sales write to sales locomotive.com,<br /> for support write to support locomotive.com<br /> <br /> See C3.1<br /> <br /> <br /> A3.5.2) Rowansoft<br /> <br /> Contact Tony Gill at tgill alystra.win-uk.net for rates.<br /> <br /> ROWANSOFT, ROWANCRAIG, ARDFERN,<br /> BY LOCHGILPHEAD, ARGYLL, PA31 8QN<br /> Tel. 01852 500 257<br /> <br /> <br /> A3.5.3) Holland Numerics Ltd 09/07/97<br /> <br /> Converts PCW data to PC format. A price list can be obtained by email<br /> from phil.holland bcs.org.uk on the web page :<br /> http://www.hollandnumerics.demon.co.uk/PCWPRICE.HTM<br /> or by post from:<br /> <br /> Philip R Holland<br /> Holland Numerics Ltd<br /> 94 Green Drift<br /> Royston<br /> Herts SG8 5BT<br /> United Kingdom<br /> <br /> <br /> A3.5.4) David Simpson<br /> <br /> David Simpson (email : DAS picknowl.com.au)<br /> PO Box 187<br /> Mitcham Shopping Centre<br /> South Australia 5062<br /> Ph +61-8-83731693<br /> <br /> Contact me for rates.<br /> <br /> I also supply belts and/or do the replacement for 3" drives<br /> <br /> I am the contact for Amstrad Computer Club Incorporated in South<br /> Australia.<br /> <br /> The club meets weekly on Tuesday evenings between 6:30 and 9:00pm at<br /> Torrensville Primary School, Hayward Avenue, Torrensville, SA. While<br /> the club is primarily a no-brand PC compatibles club, I and several<br /> other members are familiar with CPC and PCW machines and are only too<br /> happy to help.<br /> <br /> <br /> A3.6) Tapes 03/28/2002<br /> <br /> A3.6.1) Using AIFF decoder 03/28/2002<br /> <br /> - digitalize the tape as AIFF or WAV files, using Cool Edit for example,<br /> - use AIFFdecoder (A1.2.10) for transforming an AIFF file to<br /> plain Amstrad files to put in the TAPE directory of an emulator,<br /> or use CPCFS (A1.2.4) to put the files into a .DSK,<br /> - run the Multi-Machine emulator which can directly read .WAV files.<br /> <br /> You can use CPC2TAPE (A1.2.17) to transfer a tape directly from PC to CPC.<br /> <br /> A3.6.2) Using vox2tzx and playtzx 03/28/2002<br /> <br /> Voc2tzx is an utility to transfer cassette programs into CDT tape<br /> images for use with emulators. There are instructions at the ADATE<br /> archive which describe how to identify and convert various loading<br /> systems.<br /> <br /> Playtzx is an utility to convert CDT tape images to a real cassette<br /> for use on a real CPC. You can play the CDT through the sound card of<br /> your PC.<br /> <br /> Get voc2tzx and playtzx at Word of Spectrum<br /> <br /> <br /> <br /> <br /> <br /> A4) Maps, solutions, pokes, basic loaders ?<br /> <br /> A4.1) Maps & Solutions 02/14/2000<br /> <br /> Post solutions in the newsgroup, I will store them on lip6.<br /> <br /> - http://hjem.get2net.dk/gunn<br /> A lot of adventure games solutions<br /> <br /> - WOS games maps<br /> a lot of games maps<br /> <br /> <br /> A4.2) Pokes 03/05/99<br /> <br /> Starting with CPCEMU 1.3 you can easily poke games with an external<br /> database file. If you have new pokes, send them to<br /> tous club-internet.fr which maintains a database for CPCEMU. The last<br /> database is 1.641 pokes for 576 games, get<br /> ftp://ftp.lip6.fr/pub/amstrad/emu-uti/mix09.zip<br /> <br /> Amstrad CPC poke database (for CPCEMU), you can submit your pokes to<br /> be added in the database : http://andercheran.aiind.upv.es/~sergio/cpc<br /> <br /> <br /> <br /> A5) Hardware problems<br /> <br /> A5.1) Internal drive 07/22/2000<br /> <br /> If you have the error : 'disk missing', the drive belt should be the<br /> problem. The best solution is to come with your old belt in an<br /> electronics shop and see the available belts. You should look for<br /> one with the dimensions 72mm x 3 mm x 0.5 mm (although I believe it is<br /> OK to use belts in the length range of 69-72 mm long and either 3 or<br /> 4mm wide).<br /> <br /> You can find belts at Paris (75011), reference Koenig 7093.00 at<br /> Espace Composants Electronique, 66 rue de Montreuil, métro Nation,<br /> phone 01 43 72 30 64, fax 01 43 72 30 67 (http://www.ibcfrance.fr)<br /> <br /> Cibotronic at Paris (France) used to sell them, but they<br /> don't have them anymore. The reference was MASTER type CR 4092,<br /> dimensions 71.0 x 0.6 x 2.8 mm.<br /> <br /> An U.K. address : Andre Howard at 65 Altyre Way, Beckenham, Kent BR3<br /> 3ED. Price is #2.25 (UK pounds) including P&P.<br /> <br /> Still in U.K., CPC components sells them as reference AVBELT3 for 18<br /> pences. Phone (01772) 654455.<br /> <br /> Pinboard Computers can supply belts, email to Pinboardcomputers btinternet.com<br /> <br /> A working reference in U.K. : maplins reference RK99.<br /> <br /> For Germany, see A8.1.4.4 and A8.1.4.5<br /> <br /> Now it is time to change the belt of an Amstrad CPC 6128/6128+ :<br /> - open the CPC by unscrewing the screws at the back of the CPC,<br /> without disconnecting anything. For a CPC+ there are screws and 3<br /> clips,<br /> - unscrew the drive from the CPC,<br /> - disconnect the 2 cables (data and electricity),<br /> - if you have a CPC+, get out the drive from its metallic place, there<br /> are 4 screws and you have to push the drive,<br /> - put the drive to let you see the green electronic card,<br /> - unscrew the card from the drive,<br /> - disconnect the items which goes from the card to the drive to let<br /> you lift enough the card and see the belt (you wont be able to detach<br /> completely the card from the drive),<br /> - remove the belt with your fingers or a screwdriver. In all cases,<br /> keep always the drive with the head down, or a nail will fall.<br /> It is used for the detection of write protection.<br /> - buy a new belt (see above),<br /> - put the new belt, reconnect all items, screw again the green<br /> electronic card, reconnect the drive to the CPC, close the CPC.<br /> <br /> The other possibility is a fault with the index hole detection. As<br /> well as the large shutter on a 3" disc, there is also a smaller one<br /> through which the disc drive can watch for the index hole to go past.<br /> There is a LED and an associated detector that watch for this, and if<br /> either has gone wrong or got covered in dust you may get disc missing<br /> messages.<br /> <br /> <br /> A5.2) External drive 05/15/99<br /> <br /> See A3.2.1 and A3.2.2 for adding a 5,25" or 3,5" drive to your CPC.<br /> Then, when the drive is installed, you can't format your disk to the<br /> full 720 Ko unless you have a ROM box and another operating system<br /> such as RoDOS, ROMDOS (not CPC+ compatible) or ParaDOS (the best one).<br /> Parados recognise all ROMDOS formats and can replace ROM slot 7<br /> (Amsdos).<br /> <br /> <br /> A5.3) Components<br /> <br /> The place to go for CPC spares is (coincidentally) a company called<br /> CPC Spares in United Kingdom, at +44 1772 654477.<br /> <br /> There are 3 Gate Array, two types being used on 464 (a very old cpc uses<br /> 400007, the newer ones have 400010).<br /> <br /> The AM40007 is the type used in most CPC464's and they should be<br /> available from CPC Ltd. +44 1772 654455. They're gonna be expensive<br /> though, probably about 25-35 pounds.<br /> <br /> <br /> <br /> <br /> A6) How can I help the Amstrad world ?<br /> <br /> A6.1) Updating the FAQ<br /> <br /> By sending corrections, modifications, new informations for this FAQ<br /> to roussin noos.fr<br /> <br /> <br /> A6.2) Commercial games becoming freeware 07/31/2004<br /> <br /> If you know addresses of authors who wrote programs on CPC/PCW, send<br /> me their address, I will write them to ask the persmission for letting<br /> their games to become freeware or shareware (they still will retain<br /> the copyright, even after all these years).<br /> <br /> See http://genesis8.free.fr/gamecal.php<br /> for the games that already became freeware, or almost freeware<br /> (authors stating that they don't care for the distribution of their games).<br /> <br /> <br /> A6.3) Adding files to ftp.lip6.fr 04/15/2001<br /> <br /> You can send me your latest production. As there is no upload<br /> directory on lip6, you will need to email your programs to<br /> roussin noos.fr, or send them to ftp.nvg.ntnu.no/pub/cpc/incoming,<br /> I will then put it on ftp://ftp.lip6.fr/pub/amstrad<br /> <br /> <br /> A6.4) Updating ALL_CPC, ALL_HW, ALL_ROM, ALL_UTIL 04/14/2002<br /> <br /> Frederic Herlem (frederic.herlem planetis.com) is writing the complete<br /> inventory of the CPC programs, get v08 and help him to update it :<br /> ftp://ftp.lip6.fr/pub/amstrad/misc/all_cpc.zip<br /> <br /> Kevin Thacker (amstrad aiind.upv.es) wrote :<br /> <br /> - inventory of all hardware produced for the CPC (v1.0 is 02/04/97)<br /> ftp://ftp.lip6.fr/pub/amstrad/misc/all_hw.zip<br /> - inventory of all CPC ROM software, (v1.0 is 02/04/97)<br /> ftp://ftp.lip6.fr/pub/amstrad/misc/all_rom.zip<br /> - inventory of all CPC utilities, commercial or not, (v1.0 is 02/04/97)<br /> ftp://ftp.lip6.fr/pub/amstrad/misc/all_util.zip<br /> <br /> <br /> <br /> A7) Commercial programs which are now PD, freeware or shareware 07/31/2004<br /> <br /> See http://genesis8.free.fr/gamecal.php<br /> <br /> <br /> <br /> A8) Useful addresses and information<br /> <br /> A8.1) Addresses<br /> <br /> See A3.4 for a PCW address.<br /> <br /> A8.1.1) FRANCE<br /> <br /> A8.1.1.1) removed 05/18/2001<br /> <br /> <br /> A8.1.1.2) Futur's 10/31/99<br /> <br /> Futur's is a french group, they do many things. They bring you the<br /> Soundplayer (a better Digiblaster). It connects on the printer port.<br /> The Soundplayer is used by Protracker and Digitracker. You can do it<br /> yourself for about 5 euros of electronic components. The electronic<br /> plan is in the paper zine Quasar issue 9, see A9.1.3. With this little<br /> marvellous thing, you can have 8bit samples, instead of 4bit samples.<br /> The SoundPlayer+ is a better SoundPlayer, which can include Virtual<br /> Net 96 (see A10.5) for a bit more more, or which can use a CPC+ port instead<br /> of the normal CPC printer port.<br /> <br /> The SoundPlayer II now exists. It connects on the expansion port and<br /> permits to make mono 8 bits/22KHz digitalized sound. It offers one<br /> more port to connect a second Soundplayer (for stereo) or to free the<br /> printer port.<br /> <br /> For ordering a SoundPlayer+ or 2, see A9.1.3<br /> <br /> see http://www.chez.com/futurs or http://www.ifrance.com/futurs<br /> <br /> <br /> old A8.1.1.3 removed, A8.1.1.4 become A8.1.1.3<br /> <br /> <br /> A8.1.1.3) Association des Fans de CPC (AFC) 07/31/2004<br /> <br /> AFC is a french association whose aim is to be a link between the various<br /> CPC users. For more information, write to<br /> <br /> Emmanuel Roussin<br /> 10 rue du Capitaine Menard<br /> 75015 PARIS<br /> FRANCE<br /> <br /> or see http://genesis8.free.fr/<br /> <br /> <br /> A8.1.2) U.S.A<br /> <br /> A8.1.2.1) Sinotech Ltd.<br /> <br /> A source for Amstrad PCW, PC 1286/2286, PC1386/2386, PC 1512/6400, and<br /> PC 1640 disks, ribbons, memory and drive upgrades, etc. in the USA is:<br /> <br /> Sinotech Ltd.<br /> 218 Terrace Drive<br /> Mundelein, Illinois<br /> USA 60060<br /> <br /> phone: (708) 566-0504<br /> <br /> <br /> A8.1.3) United Kingdom<br /> <br /> A8.1.3.1) Comsoft (was Campursoft) 07/24/2004<br /> <br /> Comsoft doesnt exist anymore. This company was held by Peter Campbell.<br /> Comsoft was selling ParaDOS, DES, and other products. One of these<br /> products was the Basic Idea, a tutorial of 42 pages and disc of <br /> examples for the basic programmer, now available at :<br /> <br /> http://www.sean.co.uk/books/amstrad/index.shtm<br /> <br /> <br /> A8.1.3.2) United Amstrad User Group 06/01/98<br /> <br /> Martyn Sherwood<br /> Sherwood<br /> 13 Rodney Close<br /> Bilon<br /> Rugby<br /> Warwickshire<br /> CV22 7HJ<br /> United Kingdom<br /> <br /> The group has been going for 10 years now. We publish a magazine<br /> called "CPC User" every couple of months, and have other services<br /> for members (disk and tape library, book library, and help-lines).<br /> The magazine carries occasional articles on using CPCs in conjunction<br /> with PCs (how to set up emulators, share files, and so on), and other<br /> articles range from those aimed at beginners to experienced users,<br /> with competitions, type-ins, tutorials, and fiction.<br /> <br /> See A2.2 for web address and A9.1.2 for fanzine.<br /> <br /> <br /> A8.1.3.3) Brian Watson<br /> <br /> Brian Watson<br /> 39 High Street<br /> Sutton-in-the-Isle<br /> ELY<br /> Cambs<br /> CB6 2RA<br /> England<br /> <br /> Tel (and FAX by arrangement, phone first): +44 (0)1353 777006<br /> E-mail : brian spheroid.demon.co.uk<br /> <br /> Supplier or distributor of a number of products and services<br /> for users of CPCs, CPC Pluses, PCW/PcWs and some other<br /> computers. Fuller details with prices on application<br /> <br /> - The Protext family, including Proprint, Protext Office,<br /> Maxam, Utopia etc for the CPC and PCW (also the PC and<br /> Atari versions and the Prodata PC database). Free user<br /> support at normal phone rates is included with all items<br /> <br /> - Montrac: a new monitor/tracing program to work with Maxam<br /> <br /> - PcW16 operating system upgrades. Free for a DS/HD disc and<br /> return postage with your address in a padded bag<br /> <br /> - Pipeline Tutorials for the CPC: a printed tutorial course in<br /> parts (and firmware guides) with free example files on disc<br /> <br /> - Second-hand Software: an extensive range for the CPC, all<br /> originals with documentation. From 50 pence UK.<br /> <br /> Also editor of 8BIT magazine, and is the Publicity Officer of<br /> WACCI CPC club and IEBA (Independent Eight Bit Association)<br /> <br /> Send large Self Adressed Envelop (SAE) or two International Reply<br /> Coupons (IRC) for Brian Watson Software catalogue.<br /> <br /> <br /> <br /> A8.1.4) Germany<br /> <br /> A8.1.4.1) Karl-Heinz Weeske<br /> <br /> Karl-Heinz Weeske<br /> Potsdamer Ring 10<br /> D-71522 Backnang<br /> Tel +49 7191 60078<br /> Fax +49 7191 60079<br /> <br /> supply of:<br /> <br /> CPC hardware and software, printer ribbons (NQL401 & DMP), circuit<br /> diagrams, manuals, etc..., demand an offer list !<br /> <br /> <br /> A8.1.4.2) Walter Kuhn<br /> <br /> Walter Kuhn<br /> EDV-Zubehr<br /> Hessenstrasse 7 (Frohnhausen)<br /> D-35684 Dillenburg<br /> Tel./Fax +49 2771 32688<br /> <br /> supply printer ribbons Schneider/Amstrad, DMP 2000...3160, NLQ<br /> 401, Joyce, LQ 3500, PCW 8256/8512, PCW 9512,<br /> Multistrikeband, Maxell 3"-Disks 10 pack,<br /> <br /> <br /> <br /> A8.1.4.4) Beratung Mewes 06/09/2004<br /> <br /> EDV-Beratung Mewes<br /> Gartenstr. 2<br /> 53902 Bad Muenstereifel<br /> Tel. +49 2253 932388<br /> Fax +49 2253 932387<br /> Email : s.mewes usa.net<br /> <br /> drive belts (CPC, PCW), 3" drives (PCW), RAM-Extensions, repair<br /> service for disc-drives (3")<br /> <br /> <br /> A8.1.4.5) Andreas Micklei 06/19/2004<br /> <br /> Andreas will send out replacement belts for 3 inch drives to anyone in<br /> germany. The price is 1,5 euro per belt plus 0,55 euro for postage.<br /> Payment is accepted in cash, stamps, bank transfer or CPC hardware.<br /> <br /> To avoid long delays and assure that enough belts are in stock,<br /> contact him at nurgle gmx.de<br /> <br /> Andreas Micklei<br /> Lefevrestr. 15<br /> 12161 Berlin<br /> GERMANY<br /> <br /> <br /> A8.2) information<br /> <br /> A8.2.1) the firmware guide<br /> <br /> The unofficial (not the proper SOFT 968 guide) Amstrad CPC Firmware<br /> guide is available now! Thanks to Bob Taylor and Thomas Defoe for<br /> allowing the distribution.<br /> <br /> David Cantrell has scanned and reformatted the electronical version!<br /> <br /> Get ftp://ftp.lip6.fr/pub/amstrad/misc/firmware.zip<br /> <br /> <br /> A8.2.2) Pin-out for colour monitor<br /> <br /> u<br /> 5 1<br /> 6<br /> 4 2 (viewed from rear)<br /> 3<br /> <br /> 1 = Red 4 = Sync<br /> 2 = Green 5 = Gnd<br /> 3 = Blue 6 = Lum<br /> <br /> <br /> A8.2.3) Programs on ROMs (01/10/99)<br /> <br /> With RamRomBox by Inicron or RAMCARD by RAM7 (see A10.3.2) come the<br /> utility Softbrenner which can easily save any program on ROM (or<br /> fake, SRAM-simulated ROM in case of a RamRomBox), even ones longer<br /> than 16 kb.<br /> <br /> <br /> A8.2.4) "The Anatomy for the CPC's" 03/21/2005<br /> <br /> The Anatomy for the CPC is a hardback book, with a pink cover, and<br /> contains details of the CPC hardware and software. It describes the<br /> different Gate Array versions (including the one with the heat sink),<br /> the CRTC, FDC and more, their signals (and what those do), and how<br /> these relate to the CPC. It also contains:<br /> <br /> - a listing of the CPC firmware calls, plus the undocumented maths<br /> calls.<br /> - a commented "disassembly" of the CPC Basic and OS Rom (this comes<br /> in the form of an address and a comment. Although not a actual fully<br /> commented disassembly, it is still very useful).<br /> <br /> <br /> A8.2.5) using a CPC joystick on PC 09/18/99<br /> <br /> To use a CPC joystick on PC, get ftp://ftp.lip6.fr/pub/amstrad/misc/DPADPR50.ZIP<br /> <br /> <br /> A8.2.6) loading protected BASIC programs 02/20/2000<br /> <br /> 'Read Amstrad CPC protected BASIC files<br /> '<br /> ' Adapted from Clefs Pour Amstrad, 2. Systeme disque<br /> ' by Daniel MARTIN and Philippe JADOUL<br /> ' (c) Editions du PSI, 1986 ' ISBN 2-86595-256-8 '<br /> ' Run, type in filename (can be empty for tape) and<br /> ' then type 'CALL &A400'<br /> '<br /> ' This program will fail for very large BASIC files<br /> '<br /> ' A line needs to be changed for CPC464s '<br /> MEMORY &9FFF<br /> INPUT "Filename "; n$<br /> n = LEN (n$)<br /> FOR i = 1 TO n<br /> POKE &A430 + i, ASC (MID$ (n$, i, 1))<br /> NEXT i<br /> FOR i = &A400 TO &A428<br /> READ a$<br /> POKE i, VAL ("&" + a$)<br /> NEXT i<br /> POKE &a401, n<br /> DATA 06, 00, 21, 31, A4, 11, 00, A0, CD, 77, BC, 30, 18<br /> DATA C5, 21, 70, 01, CD, 83, BC, C1<br /> DATA 21, 70, 01, 09, EB, 21<br /> DATA 66 : ' Change this to 83 for CPC464s<br /> DATA AE, 06, 04<br /> DATA 73, 23, 72, 23, 10, FA, CD, 7A, BC, C9<br /> PRINT "Type 'CALL &A400'"<br /> NEW<br /> <br /> <br /> <br /> A9) Fanzines<br /> <br /> If french people are interested, don't forget to send stamps to get<br /> back your disk or paper fanzine. For foreign people, International<br /> Reply Coupons are available from post offices in all EU countries,<br /> US, Canada, and most others. A single International Reply Coupon<br /> (IRC) can be exchanged by the recipient for enough postage stamps<br /> to cover airmail for a letter weighing up to 10 grams. For heavier<br /> letters, such as those containing disks or zines, send more IRCs!<br /> <br /> <br /> A9.1) on paper<br /> <br /> A9.1.1) WACCI 07/24/2004<br /> <br /> For more informations see http://www.wacci.org.uk/<br /> <br /> They have a Book Library, Tape library, "Homegrown" Disk Library and<br /> PD Disk Library, 3" Disks supplied at 1 pound 50p each, alternative<br /> Firmware Guide and Disk, 6 pounds.<br /> <br /> For a free sample copy of the clubs magazine either Email at<br /> brian spheroid.demon.co.uk with your name and address.<br /> <br /> <br /> A9.1.2) CPC User<br /> <br /> A magazine published every couple of months by the United Amstrad<br /> User Group (UAUG), see A2.2 and A8.1.3.3<br /> <br /> <br /> A9.1.3) Quasar 05/02/2003<br /> <br /> A french zine, especially about programming on CPC(+). Last issue is<br /> no 20 (July 2002), for prices and availibility see their bilingual<br /> site at :<br /> <br /> http://www.chez.com/futurs/<br /> <br /> Philippe Rimauro (Futur's/Quasar)<br /> 8 chemin des Maillos<br /> 09200 SAINT-GIRONS<br /> FRANCE<br /> <br /> <br /> A9.1.4) Eurostrad 10/31/99<br /> <br /> A french paper zine, most of the articles are translated in english.<br /> Last issue is no 12 (summer 1999).<br /> <br /> Thomas FOURNERIE<br /> Le Reverdy<br /> 50530 SARTILLY<br /> FRANCE<br /> <br /> <br /> A9.1.5) Amstrad Action 07/24/2004<br /> <br /> Not a fanzine, but a commercial U.K. newspaper which stopped with<br /> issue 117 in June 1995. It was sold with cover tapes containing<br /> commercial games. Issue 117 came with North & South.<br /> <br /> Issues of Amstrad Action are now available online with the permission <br /> of its editor Future Publishing <br /> http://www.futurenet.co.uk/<br /> at the following address :<br /> http://cpcoxygen.digi-alt.net/<br /> <br /> <br /> A9.2) on disk<br /> <br /> A9.2.1) Boxon 07/28/97<br /> <br /> Nicolas Ader (Nicky one)<br /> Place du Donjon<br /> 32320 BASSOUES<br /> FRANCE<br /> <br /> Boxon issue 3 is out (07-96 to 02/97).<br /> <br /> <br /> A9.2.2) Demoniak 11/03/98<br /> <br /> Anthony Nevo (orphee)<br /> Le Louya<br /> 35290 GAEL<br /> FRANCE<br /> <br /> Get issues 3 to 6 on ftp://ftp.lip6.fr/pub/amstrad/zines (dmk*.zip)<br /> <br /> <br /> A9.2.3) Dracula Fanz 08/01/98<br /> <br /> Miguel Fremeaux (Dracula)<br /> 238 rue du cardinal Allen<br /> 59553 CUINCY<br /> FRANCE<br /> <br /> Last issue is 5 (December 1995) with articles in english, get the<br /> issues at ftp://ftp.lip6.fr/pub/amstrad/zines<br /> <br /> <br /> A9.2.4) Phaser<br /> <br /> Sebastien Broudin (Seb)<br /> 1 rue Emile Combes<br /> 60600 FITZ-JAMES<br /> FRANCE<br /> <br /> <br /> A9.2.5) Better Than Life<br /> <br /> An English disc fanzine, with around 40 articles (all in English)<br /> covering a huge range of subjects. Issues 1 to 4 are out, look at<br /> ftp://ftp.lip6.fr/pub/amstrad/zines, you can e-mail the editor<br /> Richard Fairhurst (CRTC/Systeme D) : richard systemed.u-net.com<br /> <br /> <br /> A9.2.6) Tribal Mag 05/23/99<br /> <br /> A good german zine, with some english articles, issue 8 is the last<br /> one. Tribal Mag has now merged with CPC-Telegramm. Web site is :<br /> http://tribal-mag.home.pages.de<br /> <br /> All issues are on ftp://ftp.lip6.fr/pub/amstrad/zines<br /> <br /> Jan Deppisch (email : Deppisch Internet-Service.nu)<br /> Lechstr. 10a<br /> 76437 Rastatt<br /> GERMANY<br /> <br /> <br /> A9.2.7) Art of Fantasy<br /> <br /> A TGS/Creators production. It's a discmag that is mainly about<br /> non-computer stuff, but instead about stuff like role-playing games,<br /> fantasy books, science fiction, stories, etc. Collapse, the editor,<br /> gets nearly no contribution, so it would be good to point his mag out<br /> a bit... The first issue (the only one out up to now) was German only,<br /> but if he gets English stuff, this mag could become international<br /> soon! The address:<br /> <br /> Collapse of TGS/Creators<br /> Tobias Zimmermann<br /> Augsburger Weg 3<br /> 59439 Holzwickede<br /> GERMANY<br /> <br /> <br /> A9.2.8) Guten TAG<br /> <br /> A new disc german-only mag by the group "TAG". I don't know much to<br /> write about it now... ask the editor! His address:<br /> <br /> Gremlin of TAG<br /> Thomas Schilling<br /> Rebenweg 28<br /> 79793 Wutschingen-Horheim<br /> GERMANY<br /> <br /> <br /> A9.2.9) Coders Paradise<br /> <br /> A disc mag for all the programmers out there. All Routines the editor<br /> (Steve of Wizcat) gets are published with many explanations<br /> (normally). Steve has many problems getting enough stuff for each<br /> issue, so pointing him out would be good again... The address:<br /> <br /> Steve of Wizcat<br /> Christian Stengel<br /> Ihnbergstrasse 9/1<br /> 73479 Ellwangen<br /> Germany<br /> <br /> <br /> A9.2.10) CPC-Telegramm 08/04/98<br /> <br /> German Diskzine by<br /> <br /> Andreas Koenig<br /> Hutstr. 7<br /> D-91056 Erlangen<br /> <br /> <br /> A9.2.11) Digital Press 07/11/2004<br /> <br /> At first a german zine with english articles, now a french-german<br /> production. Get the issues at ftp://ftp.lip6.fr/pub/amstrad/zines<br /> For information email oliver.floquet manchoo.com :<br /> <br /> Olivier FLOQUET<br /> 84 rue de Montbray<br /> 50200 COUTANCE<br /> FRANCE<br /> <br /> <br /> A10) Additional hardware<br /> <br /> For using older additional hardware on a CPC+, you will need an<br /> adaptor called a widget, as connections are not the same. They use<br /> the same connectors as german CPC (Schneider). All hardware should<br /> work with this adaptor, except the standard multiface, see A10.2<br /> (06/09/97)<br /> <br /> Look A6.4) for a list of hardware made on CPC.<br /> <br /> A10.1) Hard disks (no more produced)<br /> <br /> A10.1.1) MFM hard drive<br /> <br /> - a Dobbertin MFM interface with 20 MB HD,<br /> - in the very early years a Vortex Filecard with 20 MB MFM HD.<br /> <br /> <br /> A10.1.2) AT IDE hard drive<br /> <br /> A10.1.2.1) GIDE 11/08/2004<br /> <br /> The GIDE is a generic Z80 device that allows easy connection of any<br /> AT (16 bit) IDE hard drive to a Z80 computer. If your Z80 is<br /> socketed, you simply unplug it, plug the GIDE into the Z80 socket, and<br /> plug the Z80 into the GIDE. You need to write your own driver<br /> software, however.<br /> <br /> Gide doesnt exist for Amstrad CPC, but you will find informations<br /> about the GIDE for PCW on : <br /> - All about the GIDE interface<br /> - KC-Club.GIDE-Interface.<br /> <br /> <br /> <br /> <br /> A10.1.2.2) IDE Drives (by RAM7)<br /> <br /> It uses an ISA IDE controler and an adaptator card wich plugs in the<br /> expansion connector. It will be able to use IDE hard drives, CDROM<br /> (certainly) and disk drives (1.44 Mo). Not available for the moment.<br /> <br /> <br /> A10.2) Multiface II<br /> <br /> A useful add-on, connected to the expansion port, its primary use is<br /> to make snapshots, exactly like the emulators. See A1.2.7, an utility<br /> to transform multiface snapshot to emulators snapshot.<br /> <br /> There is a special multiface for the CPC+, standard multiface doesn't<br /> work on a plus, even with a widget. (06/09/97)<br /> <br /> <br /> <br /> A10.3) ROMBOX<br /> <br /> A10.3.1) ROMCARD and RAMCARD 10/31/99<br /> <br /> Francisco DOS SANTOS<br /> 123 boulevard Strasbourg<br /> 94130 NOGENT SUR MARNE<br /> FRANCE<br /> email : ram7 mail.dotcom.fr (no reply or very slow, best way is<br /> to use snail mail)<br /> <br /> The ROMCARD is a ROM box with 4 available slots which accepts 16 Ko<br /> (27128) or 32 Ko (27256 or 27C256) EPROM for a maximum of 128 Ko<br /> (so better use 32 Ko as there are only 4 slots). Other ROMCARDs<br /> can be put in parallel, to add another 128 Ko of ROMs each time.<br /> <br /> The RAMCARD is a ROMCARD that uses 128 Ko of RAM instead of ROM.<br /> <br /> the ramcard, a rombox using RAM<br /> <br /> <br /> A10.3.2) Inicron ROM-RAM-BOX 04/15/2001<br /> <br /> The RRB is a ROM box that doesn't need EPROMs. Up to 32 EPROMs can be<br /> simulated in the 512Kb big RAM (if build the enhanced RRB). Additional<br /> to this you can use a normal EPROM from 8-64Kb in a normal EPROM<br /> socket. Go at http://www.inicron.de or get<br /> ftp://ftp.lip6.fr/pub/amstrad/roms/rrb.zip<br /> <br /> <br /> <br /> A10.4) SoundPlayer 1 and 2<br /> <br /> See A8.1.1.2) and A9.1.3)<br /> <br /> <br /> <br /> A10.5) Network 10/31/99<br /> <br /> A10.5.1) Virtual Net 96 (VN96)<br /> <br /> Virtual net 96, a network for Amstrad CPC, made by germans, look at<br /> (english and german page) :<br /> <br /> http://www.geocities.com/SiliconValley/Park/6129/start.htm<br /> <br /> Get ftp://ftp.lip6.fr/pub/amstrad/misc/vn96eng.lzh (or ger instead of eng)<br /> for information about VN96.<br /> <br /> <br /> A10.5.2) Multi-IO card 05/30/2003<br /> <br /> VN96 doesn't work on a CPC+, but Futur's (see A8.1.1.2) has a plan for a<br /> VN96 card for CPC+, which will work of course on plain CPC. But the<br /> multi-IO card is more than a VN96 card, it has a standard parallel port<br /> where you will be able to connect all parallel devices such as a printer or<br /> a ZIP drive when a driver will be ready. The price will be about 15 euros.<br /> <br /> <br /> A10.6) Future OS 05/31/2003<br /> <br /> Future OS is a new operating system for Amstrad CPC that needs<br /> a rombox or a rambox, Future OS is more powerful than amsdos, but<br /> amsdos and CP/M programs must be adapted before using them under<br /> Future OS (they can even work faster). Type |OS or |FDESK to launch<br /> Future OS. For more information, go http://www.FutureOS.de<br /> You can use it on emulators like Caprice (install ROMs A B C D<br /> in slots 10 to 13) or WinAPE 2.0a4 (doesnt work with WinAPE 2.0a5).<br /> <br /> <br /> A10.7) Memory extension<br /> <br /> A10.7.1) 256 Kb to 2 Mb MemCard (by RAM7) 05/30/2003<br /> <br /> For 6128 and 6128+, it's compatible with Dk'tronics memory extensions,<br /> it plugs on the expansion connector. It uses the same memory managing<br /> of the 6128 second 64 Ko bank. It comes with 4 slots of static RAM (128 Kb<br /> or 512 Kb). For more information, see A10.3<br /> <br /> Beware the 256 Kb and 512 Kb models use 128 Kb RAM, the 1 and 2 Mo use<br /> 512 Kb RAM. An extra cable is also needed.<br /> <br /> the memcard, a memory extension compatible with Dktronics<br /> <br /> <br /> A10.7.2) Inicron RAM-BOX 04/24/2000<br /> <br /> A 512 Ko RAM extension for Amstrad CPC by Inicron, get<br /> ftp://ftp.lip6.fr/pub/amstrad/misc/rambox.zip<br /> or go at http://www.inicron.de<br /> <br /> <br /> A10.8) Card Tridge (by RAM7) 10/31/99<br /> <br /> The Card Tridge can read, copy and store Amstrad CPC+ cartridges with<br /> its 512 Ko of RAM). For more information see A10.3<br /> <br /> <br /> A10.9) CPC ISA 03/26/2005<br /> <br /> Connect ISA cards on your CPC by Siou (siou free.fr) :<br /> http://siou.free.fr<br /> <br /> As 26th March 2005, playing adlib music (.SA2 files) works with a Sound Blaster, and<br /> low level working of hard disks too, file system must still be done.<br /> <br /> the CPC ISA card<br /> <br /> <br /> A10.10) Amstrad MP1 and MP2 10/27/2000<br /> <br /> Amstrad MP1 and MP2 replace the CPC monitor alimentation and permits to<br /> use the television (SCART connector) for the video output (MP1 for 464,<br /> MP2 for 664/6128). You can also send the video signal on a PC which has<br /> a tuner card.<br /> <br /> The MP1 does not provide the 12V connector the 664/6128 needs to power<br /> the floppy disk drive. So you can use a 664/6128 with a MP1 but you<br /> cant use the floppy, or you need an external power supply.<br /> <br /> <br /> <br /> A10.11) CD-ROM 05/12/2003<br /> <br /> For several years people thought that the CPC version of the<br /> Codemasters CD-ROM (using a domestic CD player and a special<br /> interface to convert the audio signal into something suitable for<br /> Arnold) didnt exist. In fact, the developper (The Oliver Twins) of<br /> product acknowledged that it did exist, for more informations :<br /> http://andercheran.aiind.upv.es/~amstrad/docs/audiocd2.html<br /> <br /> <br /> A10.12) Mouse 08/06/2000<br /> <br /> You cant use a PC mouse (serial or PS/2). There are Amstrad CPC<br /> mouses, but few programs uses them (Advanced OCP art studio) :<br /> <br /> - AMX mouse (the most common),<br /> - GENIUS mouse,<br /> - DATEL mouse.<br /> <br /> <br /> <br /> A11) Upcoming Meetings<br /> <br /> <br /> <br /> <br /> <br /> <br /> B - Amstrad Notepad (NC100/150/200)<br /> <br /> B0) NC 100/150/200 presentation 08/06/2000<br /> <br /> The Notepad is Amstrad's idea of a simple word processor. It is NOT<br /> a PC-compatible and is NOT the PenPad PDA.<br /> <br /> The NC100, launched in september 1992, is about A4 size with a LCD<br /> screen (80 car. x 8 lines), nearly full size keyboard, a PCMCIA memory<br /> card slot on the left side, four coloured keys, 64 Kb of RAM. It<br /> features a word processor, word spell checker, address book,<br /> calculator, diary, clock, alarms and BBC basic. There are a serial<br /> and parallel ports.<br /> <br /> The NC200, launched in october 1993, has a fold-down LCD screen<br /> (80 car. x 16 lines), a 3.5" disk drive, 128 Kb of RAM, new software<br /> (spreadsheet and graphics, games).<br /> <br /> The NC150, launched in april 1993, has the look of the NC100 but<br /> the NC200 software, 128 Kb of RAM too, and the possibility to connect<br /> a 3,5 drive. It exists only in french and italian versions.<br /> <br /> <br /> B1) Emulators<br /> <br /> B1.1) M.E.S.S. 06/09/2004<br /> <br /> See A1.1.20.<br /> <br /> <br /> B1.2) NC100EM 03/17/2001<br /> <br /> NC100EM by Russell Marks for Linux (svgalib, X, tty) and MSDOS. It<br /> supports both the ROM software and ZCN, a free CP/M 2.2 clone. Get<br /> it at http://rus.members.beeb.net<br /> <br /> <br /> B2) How can I buy one ? 10/27/2000<br /> <br /> Unfortunately, Tandy finally stopped selling them in November 1996.<br /> The best way to buy one now is probably second-hand ads in national<br /> computer magazines, "for sale" newsgroups or auctions sites like<br /> http://www.ebay.com<br /> <br /> <br /> B3) What peripherals can I use ?<br /> <br /> The Notepads have standard Centronics parallel ports and RS232 9-pin<br /> serial ports. The system has drivers for 9 and 24-pin dot matrix,<br /> Canon inkjet and Laserjet printers. The serial port claims 9600 bps,<br /> but I can only make my NC100 work reliably at the full speed using<br /> Xmodem and the AC adapter. This seems to be a common problem probably<br /> because the AC adapter supplies 10 volts and the batteries only 6.<br /> <br /> <br /> B3.1) Printing 07/14/99<br /> <br /> The NC can use dot matrix, inkjet and laser printers with its built-in<br /> drivers (for emulating Epson, IBM, Canon, LaserJet). The LaserJet printer<br /> driver doesn't seem to be fully implemented. It doesn't support changing<br /> font sizes (at least in the german version of the NC100). If anyone fancies<br /> writing the necessary software, we'd love to hear about it...<br /> <br /> <br /> * B3.2) Extra Memory 09/09/2009<br /> <br /> A battery-backed PCMCIA memory card (SRAM) will keep data even if<br /> your Notepad crashes and increases the available memory. It also<br /> allows you to create a file with BASIC bigger than 2048 bytes. This is<br /> because BASIC allocates all available memory on start-up except 2048<br /> bytes. The memory card (maximum of 1 Mo) can be bought from :<br /> <br /> - Primary Simulation Inc., 2963 Mozart Drive, Silver Spring,<br /> MD 20904, USA. http://www.psism.com/sramsp.htm<br /> <br /> - - Talisman Electronics, P.O. Box 26 Pangbourne, Reading, RG8 8TL.<br /> - Telephone 01491 671914. http://www.talisman-uk.com<br /> <br /> - Vikant Corp., 512 Kb or 1Mb cards (http://www.vikant.com or<br /> https://secure.webcom.com/vikant/onlineorder.htm<br /> <br /> <br /> B3.3) Disks 08/15/99<br /> <br /> Cliff Lawson (NC Project Manager): if you have an NC200 you already<br /> have a disk and built in Ranger disk routines. If you have an NC150<br /> then the only bit of Ranger code is the terminal but it contains a hidden<br /> "hook" which allows the Ranger external disk to be connected to the<br /> machine and if you have an NC100 there is no Ranger code in it at all.<br /> <br /> <br /> B4) How do I connect it to a PC ?<br /> <br /> B4.1) What's the cable ?<br /> <br /> Brief instructions are given in the manual. You can either use the LapCat<br /> parallel port system or use a standard "null modem cable", available<br /> from most computer parts shops. If you really want to make your own, the<br /> NC serial port is a 9-pin RS232, and the PC cables are:<br /> <br /> 25 pins at PC 9 pins at PC<br /> <br /> NC PC NC PC<br /> 2 ----------- 2 2 ----------- 3<br /> 3 ----------- 3 3 ----------- 2<br /> 4 ----------- 6 4 ----------- 6<br /> 5 ----------- 7 5 ----------- 5<br /> 7 ----------- 5 7 ----------- 8<br /> 8 ----------- 4 8 ----------- 7<br /> <br /> <br /> B4.2) Settings<br /> <br /> Use a terminal program on the PC (Telix supports XModem file transfers<br /> as well, but standard windows terminal/hyperterminal works ok for text).<br /> Set both ends to the same speed (9600 is fine), 8 data bits, no parity,<br /> 1 stop bit, RTS/CTS handshaking on and experiments until it works...<br /> <br /> <br /> B4.3) Converting Word Processor Files 04/29/2000<br /> <br /> Converter programs are available for both PC and NC to convert from<br /> the NC's protext to RTF on the PC :<br /> <br /> - for msdos : ftp://ftp.lip6.fr/pub/amstrad/nc100/nc2rtf.zip<br /> - for NC : ftp://ftp.lip6.fr/pub/amstrad/nc100/nc2rtfb.zip<br /> <br /> <br /> <br /> B4.4) How do I connect it to a BBC micro 08/15/99<br /> <br /> You will need a 5 pin C-type DIN plug, a 9 pin serial plug, some<br /> cable, and the instructions from http://www.gre.ac.uk/~st702/qanda.htm#q11<br /> <br /> <br /> B5) BASIC<br /> <br /> Oddly enough, the Notepad includes a copy of BBC BASIC. This allows<br /> you to create your own programs and download other peoples. However,<br /> some people have found that using the WP to look at a BASIC file can<br /> crash the machine, so backup your important files first.<br /> <br /> <br /> B5.1) Where can I find programs for it ?<br /> <br /> - ftp.maekong.york.ac.uk/pub/BBC<br /> - http://www.ncus.org.uk<br /> Tim's Amstrad NC Users Site, go to links<br /> <br /> <br /> B5.2) Can I use the Word Processor to enter listings ?<br /> <br /> Certainly, to go from WP to BASIC type "*EXEC filename" into BASIC<br /> (don't forget line numbers). To go from BASIC to WP, load the program<br /> and then type:<br /> <br /> *SPOOL document<br /> LIST<br /> *SPOOL<br /> <br /> Don't put formatting (bold, etc...) in the program.<br /> <br /> B5.3) Can I make a program auto-run ?<br /> <br /> Of course, just save it with the name AUTO and whenever you start<br /> BASIC, it'll run.<br /> <br /> <br /> B6) Other Programs 07/11/99<br /> <br /> ZCN is a free operating system for the NC100. It's largely compatible<br /> with CP/M 2.2. It runs most CP/M 2.2 programs, including ZDE, QTERM,<br /> Mallard Basic, and Hitech C. It can also run the NC100's ROM BBC Basic<br /> as if it were a native ZCN program. You need an NC100 and at least one<br /> PCMCIA memory card to use it, a separate computer (perhaps a PC)<br /> and a serial lead to get the system code to it for the first time.<br /> It's available from ftp://ftp.lip6.fr/pub/amstrad/nc100 or<br /> http://www.ncus.org.uk<br /> <br /> <br /> B7) I've just crashed it...<br /> <br /> If you're lucky, switching it to standby and back will get you out. If<br /> you've got context saving on then it definitely won't. Try these:<br /> switching on while holding Function; switching on while holding<br /> Function, Stop, Del and the right-hand Shift; removing all the<br /> batteries (including the lithium cell) and the power adapter and<br /> trying to switch on. The last two definitely blank the memory. The<br /> first two don't always, but they don't always fix it.<br /> <br /> <br /> B8) I've just broken it...<br /> <br /> Try CPC supplies on +44 1772 654455 (Main switchboard) or Email their<br /> fax machine at remote-printer.Sales 6.6.4.4.5.6.2.7.7.1.4.4.tpc.int<br /> and ask them to 'phone you! Failing that, call Amstrad (see A2.2<br /> <br /> <br /> B9) Help! Where to ask 08/15/99<br /> <br /> Since the demise of Amstrad and Tandy stopping to sell the Notepad,<br /> the best place to ask for help is the newsgroup comp.sys.amstrad.8bit<br /> Free user support on Protext, the NC series word processor,<br /> from Brian Watson (protext spheroid.demon.co.uk).<br /> <br /> <br /> B10) Internet resources 12/17/2000<br /> <br /> - http://www.amstrad.com and http://web.ukonline.co.uk/cliff.lawson<br /> official and unofficial Amstrad page<br /> <br /> - ftp://ftp.nvg.ntnu.no/pub/cpc/nc100<br /> NVG FTP site<br /> <br /> - http://www.miracles.win-uk.net/NC100<br /> New address of Mark Ray NC page<br /> <br /> - http://www.ncus.org.uk<br /> Tim's Amstrad NC Users Site<br /> <br /> <br /> B11) Credits 08/15/99<br /> <br /> Although I appear to maintain this section, it wouldn't be in its<br /> current fine state without the many people who have asked questions<br /> and provided answers over the year. Especially Tim Surtell and<br /> Russell Marks, who have provided substantial amounts of information.<br /> <br /> <br /> <br /> C - Amstrad PCW<br /> <br /> C0) PCW presentation 08/04/2001<br /> <br /> Amstrad made the following PCW systems :<br /> <br /> 1) PCW8256<br /> 2) PCW8512<br /> 3) PCW9512<br /> 4) PcW9512+<br /> 5) PcW9256<br /> * 6) PcW10, see http://www.fvempel.nl/pcw10.html<br /> 7) PcW16<br /> <br /> 1) had 180K drives, 2) had a 180 kb A drive and a 720 kb B drive,<br /> 3) had only 720 kb drives. All subsequent models had 3.5" disks<br /> using CP/M format at 720 Kb until 7) when it switched to 1.44 mb in<br /> MS-DOS format. The PcW's (no capital 'c') all used EMT rather than<br /> EMS early morning start files with 3.5" drives. The PcW 9512+ was a<br /> look-alike from the older 9512, including the daisy-wheel printer.<br /> The 9256 (256 kb memory) was a redesign of the 8000 series, with<br /> thesame dot matrix printer and keyboard, but in a more modern<br /> lookingdesign. The PcW 10 resembled the 9256 but had 512 Ko.<br /> <br /> The PcW16 is a radical digression who's sole "raison d'être" was to<br /> make a true WYSIWYG product but this meant a change in the screen<br /> and processor (to 16MHz) which meant that it could not be kept<br /> compatible with the previous models (though documents ARE compatible).<br /> <br /> <br /> C1) Emulators and utilities<br /> <br /> C1.1) Emulators<br /> <br /> C1.1.1) Joyce 06/09/2004<br /> <br /> A superior PCW emulator with loads of features. Currently at version 2.02<br /> (stable) or 2.1.5 (unstable). The 2.1.1 emulates the PcW 16 as well, version<br /> 2.02 all the other PCW and PcW models.<br /> <br /> JOYCE 2.x is an integrated program: most utilities for e.g. converting disks to <br /> images (including MicroDesign disks) or vice versa, can be accessed through the<br /> menus. Features include, but are not limited to:<br /> <br /> - emulation of all PCW's (as from 2.1.1) with additional memory and hardware.<br /> - emulation of additional hardware includes amongst others: mouse, serial/<br /> parallel port and 2mb of memory;<br /> - support of actual disc drives;<br /> - virtual hard disc drives (8 mb each);<br /> - DOS directories for reading or writing, export and import tools;<br /> - one disc image included, with loads of CP/M tools, for use with JOYCE;<br /> - a variety of settings, including the original color settings of the PCW <br /> screens;<br /> - printer support. Either through LPT ports or rerouted to file (e.g. superb <br /> matrix printer emulation in Adobe PDF files);<br /> - the Windows version allows for easy creation of print screens (very useful<br /> for an editor);<br /> <br /> Check the documentation for obtaining or creating the boot disks.<br /> <br /> Available on http://www.seasip.demon.co.uk/Unix/Joyce/<br /> <br /> The (older) version for DOS v 1.36 is also still available.<br /> <br /> <br /> C1.1.2) Joyce MAC 11/08/2004<br /> <br /> MACOs port of Joyce by Richard Bannister at<br /> http://www.bannister.org/software/emu.htm<br /> <br /> <br /> C1.1.3) M.E.S.S. 06/09/2004<br /> <br /> See A1.1.20<br /> <br /> You need the boot images. M.E.S.S. should not emulate other hardware<br /> than the standard (i.e. no Centronics parallel port on a PcW 9256).<br /> <br /> <br /> C1.2) Utilities 08/04/2001<br /> <br /> See C2.2) for some PD stuff. A listing of the better commercial utilities<br /> as well as PD will follow shortly.<br /> <br /> <br /> C2) Where can I find emulators, ROMs and programs ? 08/08/2000<br /> <br /> C2.1) FTP sites 07/24/2004<br /> <br /> - ftp://ftp.demon.co.uk/pub/cpm/<br /> Demon UK, Amstrad directory, containing lots of programs for the PCW.<br /> <br /> - ftp://ftp.nvg.ntnu.no/pub/cpc/pcw/<br /> NVG, a few PCW programs.<br /> <br /> <br /> C2.2) WWW 10/03/2004<br /> <br /> - http://www.locomotive.com<br /> Locomotive Software, co-author of the Amstrad CPC and PCW ROMs<br /> bought in 2000 by SD Micros, see below<br /> <br /> - http://members.aol.com/sdmicro<br /> new owner of Locomotive name and products<br /> <br /> - http://web.ukonline.co.uk/cliff.lawson<br /> a site by an Amstrad member staff with information, files for all<br /> the Amstrad computers. The official Amstrad site :<br /> http://www.amstrad.com<br /> <br /> - http://ai.ansible.co.uk/<br /> Ansible information, makers of AnsibleIndex for LocoScript,<br /> AnsibleIndex Pro and AILINK (to convert LocoScript data to e.g. Word).<br /> Free downloadable CPM.EXE (freebies) to copy files from CF2DD to DOS.<br /> <br /> * - http://www.fvempel.nl<br /> PCW Joyce Computer Club : PCW serial communication with a PC,<br /> mounting a 3.5" drive on a PCW, a 3" on a PC, repairing a 3" drive,<br /> upgrading memory to 512 Ko, club news, PCW ads. Downloadable Public<br /> Domain.<br /> <br /> - http://www.seasip.demon.co.uk<br /> John Elliott's CP/M page, he is the man behind some of the finest PCW<br /> freeware around and provides links to many generic CP/M resources.<br /> He's also put up exhaustive information on the PCW's XBIOS.<br /> Lots of downloadable conversion tools, also for graphics.<br /> <br /> - http://www.systemed.net/pcw/<br /> Richard Fairhurst page about PCW hardware reference<br /> <br /> - http://www.xs4all.nl/~ianmacd/PCW.html<br /> Ian Macdonald, about PCW<br /> <br /> - Protext related issues: Brian Watson (protext spheroid.demon.co.uk).<br /> http://www.cix.co.uk/~mtilley/protext<br /> <br /> - Walnut Creek CD-ROM has a PCW section, no longer sold, but get it at<br /> ftp://ftp.barnyard.co.uk/cpm/walnut-creek-CDROM/ <br /> <br /> <br /> <br /> C2.3) Various sources 08/08/2000<br /> <br /> A PCW CD-ROM by P.D. Blake with over 4,500 files of PCW software,<br /> including all of his commercial titles and around two hundred PD and<br /> Freeware titles. There is also a large amount of Microdesign material<br /> and just about every programming language and utility available for<br /> the PCW. The CD costs £25 + £2.50 P&P. You can order it by<br /> sending a cheque for £27.50, made payable to Mr P.D.Blake to:<br /> P.D.Blake, 32 Sample avenue, Beverley, E.Yorks, HU17 9DW, England.<br /> E-mail address : pdblake yahoo.co.uk<br /> <br /> <br /> <br /> C3) Transferring between PCW and PC 08/08/2004<br /> <br /> Transferring data from floppy discs is easy if you have a 3.5" drive:<br /> all PcW's have one. A PCW (the 8256, 8512 and 9512) can be provided<br /> with such a drive. The free software CPM.EXE from Ansible Index at<br /> http://ai.ansible.co.uk/ can read CF2DD (double sided<br /> discs for drive B). If you have a 3.5" disc, reading it in a PC will be<br /> easy. If you only have a 3" drive you could opt for mounting the B<br /> drive in your PC (see C3.4). If you have other logical disc formats on<br /> 3.5", Sydex 22DISK will give you the best results.<br /> <br /> Summarising the hardware conversion alternatives:<br /> <br /> - 3.5" drive on PCW (DIY possible),<br /> - LocoLink between PCW and PC,<br /> - RS 232 serial null-modem between PCW and PC (DIY possible),<br /> - 3" drive on PC (DIY possible),<br /> - acoustic communication (DIY possible).<br /> <br /> The 22DISK, MS Odball, PCWTrans and CPM.EXE software is freely<br /> available: 22DISK still is shareware formally and should be purchased<br /> (USD 25, an unsupported license) with Sydex. Of these programs 22DISK<br /> is the only one that can handle all disc formats for the PCW : some<br /> formats require additional definitions, some common ones listed in<br /> * http://www.fvempel.nl/euro1.zip.<br /> If you have discs that have been formatted by DISCTOOL (the<br /> one from Matthijs Vermeulen, not the Moonstone program with the same<br /> name) which offered variable combinations of directory- and data-<br /> * allocation, see the site http://www.fvempel.nl/.<br /> <br /> There are quite a lot of commercial alternatives around: among others<br /> Moonstone 2-in-1 and DDriverPCW (a DOS driver that allows disks to be<br /> read and written on a PC). These two can still be obtained from<br /> LocoScript Software.<br /> <br /> Besides the hardware process you will need to pay some attention to<br /> the file format as well: at least where LocoScript is concerned.<br /> <br /> The simple and cheap option is to export the documents on the PCW to<br /> ASCII (American Standard Code for Information Interchange - the<br /> "language" that works with most computers, except for Windows which<br /> uses a slightly different dialect called ANSI). By exporting to ASCII<br /> your files will be restricted to the default 256 characters available<br /> with ASCII (quite a downgrade from the 600 as offered by LocoScript)<br /> and you will lose formatting, headers, footers, page numbers and<br /> accents. When you opt for the PAGE IMAGE attribute, present on all<br /> versions of LocoScript, you will at least retain some details like tab<br /> stops (replaced by spaces) and margins, but you definitely will have to<br /> check the end-result on the PC. When combined with mounting a 3" drive<br /> on a PC or (more expensive) a 3.5" drive on a PCW it is a cheap DIY<br /> solution, useful and reliable for confidential data or data that you do<br /> not want to risk losing in the mail.<br /> <br /> If you want to retain the document settings, layout, accents and the<br /> like you will have to convert the document(s), using the available<br /> commercial programs:<br /> <br /> - Ansible AILINK<br /> - LocoScript Professional or LocoScript Easy with or without LocoLink<br /> (for Windows)<br /> <br /> Which one suits you best depends on your budget and purpose. The<br /> AILINK http://ai.ansible.co.uk/ can read CF2DD format disks and convert<br /> all LocoScript formats (from 1 to 4) into a.o. Richmond Text Format,<br /> a format commonly used in word processors. At GBP 19.50 it may sound<br /> expensive and I have not used all of it's features but it seems like a<br /> good alternative to reformatting documents or buying a DOS word<br /> processor for conversion only. AILINK is a true Windows program<br /> (allowed for the occasional DOS box) and offers amongst others RTF,<br /> RTF for Word, WordPerfect 4.2, ASCII, ANSI, HTML and some other<br /> formats.It allows for mass copying and converting and seems to produce<br /> a 1:1 copy including formatting and accents. Do note that AILINK can<br /> read from CF2DD only (no CF2 or other formats) and does not solve the<br /> 3" problem, unless you mount a 3" drive in your PC.<br /> <br /> The LocoScript alternatives are more expensive but they also provide<br /> the hardware solution (LocoLink, part of LocoScript, does). Data<br /> conversion retaining layout and accents is also seamless but there is<br /> no mass-tagging option and the PCW LocoScript source file has to be<br /> translated to PC LocoScript source file before it can be exported to<br /> other formats. But then again, the LocoScript PC word processing<br /> software is not bad either. LocoFile datafiles need to be "squashed"<br /> by LocoScript Professional or PC Easy before they can be used.<br /> Conversion requirements do not apply for LocoLink for Windows, only<br /> the earlier version requires it.<br /> <br /> To use the data from a LocoFile datafile with other PC software you<br /> will need to use LocoScript Professional or LocoScript PC Easy<br /> Mailmerge commands to output the data to a LocoScript document. You<br /> should then export the document as above. Or LocoLink for Windows can<br /> be used to convert datafiles to DBase or FoxPro formats.<br /> <br /> I have heard from other projects on the subject, but have not seen<br /> products so far.<br /> <br /> Using Mallard BASIC programs on the PC is possible, though the<br /> following aspects should be considered. First of all, Mallard BASIC has<br /> a special file format that (I think) can be read by the PC version of<br /> Mallard BASIC only (an expensive and therefore rare item: I do believe<br /> it is still for sale, though). Saving it into ASCII format is easy<br /> though: just add the attribute A when you (re-)save a program, e.g.<br /> SAVE "PROG.BAS",A will save the file in ASCII format. This format can<br /> be read by 99% of the other Basic dialects. Also, unprotect your<br /> file program, if it has been protected, before exporting it.<br /> <br /> Although Mallard BASIC is pretty much standard in command convention,<br /> there are a couple of exceptions.<br /> 1) JetSam keyed-index databases cannot be used by other Basic dialects:<br /> redesign of the program to a sequential or random access database<br /> structure will be required.<br /> 2) GSX, the Graphics System eXtension, does not have an MS Dos<br /> equivalent. In fact it is not part of BASIC but if your application<br /> uses this add-on on the PCW, it can obstruct the proper working on<br /> another Basic language. It will have to be replaced by graphics<br /> functionality offered by the other Basic.<br /> 3) Machine code and peeks & pokes will not work at all. If the<br /> program contains too much of these: forget it...<br /> 4) The different hardware can be a bit of a problem when the program<br /> uses the PCW hardware to it's maximum. The big screen and the<br /> Epson FX-80 emulation on the printer may force you to re-write<br /> the program.<br /> <br /> I found that good old GWBasic, supplied in numerous quantities with MS<br /> Dos, works best when porting PCW Basic source to other computers. Check<br /> a program up-front for the mentioned issues and decide whether it is<br /> worth your while to adopt it on a PC, to redesign it on a PC or to use<br /> a PCW emulator on the PC. Do be careful when modifying a PCW Mallard<br /> BASIC program on the PC, though!<br /> <br /> Using PC data on a PCW is also possible: ASCII would be the normal<br /> standard here but several Dos and Windows programs offer export<br /> formats for older software (e.g. dBaseII, SuperCalc II) too. LocoScript<br /> Professional or LocoScript Easy documents can be read by LocoScript<br /> 2.50 or later on the PCW if they have been saved in the LocoScript 2/3<br /> format, a feature offered by LocoScript Professional 2 or LocoScript<br /> PC Easy (version 1.01 or later).<br /> <br /> LocoFile databases from a PC need to be extracted to a LocoScript<br /> document and can be converted to the PCW. On the PCW the LocoFile<br /> database needs to be rebuild.<br /> <br /> Software Versions and Requirements (Howard Fisher)<br /> <br /> To use LocoLink, LocoScript Professional or LocoScript PC Easy is<br /> required. The above information applies to versions since 1 st January<br /> 94 - LocoLink for LocoScript Professional, Version 1.08 or later of<br /> LocoScript Professional and Version 1.01 or later of LocoScript PC<br /> Easy. To export from LocoScript on the PC to the PCW you need v2.50<br /> or later of LocoScript on the PCW. LocoLink for Windows can<br /> convert documents and datafiles produced with any version of<br /> LocoScript.<br /> <br /> Alternatively, you can use a disc transfer service both to copy the<br /> discs and if necessary convert the files to other PC word processor<br /> formats.<br /> <br /> Here are those which can transfer and/or convert files :<br /> <br /> - http://www.locomotive.com,<br /> - http://members.aol.com/sdmicro,<br /> <br /> <br /> C3.1) 3.5" drive to a PCW 06/09/2004<br /> (this section by Axel_Berger Su2.Maus.De)<br /> <br /> Amstrad uses a 26-pin floppy bus, which is exactly similar to the 34<br /> pin Shugart bus but with 4 signals, that are never used anyway, left<br /> out. In both cases all odd numbered lines are grounded and all signals<br /> are active low. The unused lines of the Shugart are: (usage of some of<br /> them varies, I have tried to state the most common one)<br /> <br /> 2: Density<br /> 4: Head Load<br /> 6: Drive Select 3, Ready<br /> 14: Drive Select 2<br /> <br /> <br /> So you have to splice the cable and fit it to a 34-pin connector as:<br /> <br /> Amstrad Shugart Use<br /> 2 8 Index<br /> 4 10 Drive Select 0<br /> 6 12 Drive Select 1<br /> 8 16 Motor On<br /> 10 18 Step Direction<br /> 12 20 Step<br /> 14 22 Write Data<br /> 16 24 Write Gate<br /> 18 26 Track 00<br /> 20 28 Write Protect<br /> 22 30 Read Data<br /> 24 32 Side Select<br /> 26 34 Ready<br /> <br /> There is one problem with the choice of drive: The PCW expects to get<br /> a "Ready" on pin 26 and IBM compatible 3.5" HD don't deliver it.<br /> Drives used to have jumpers but with the Gates monopoly they don't<br /> have them anymore, so you might have to improvise something. A direct<br /> connection from Drive Select to Ready by Diode will deliver the signal<br /> too soon, reading will work, as the computer gives it a second try but<br /> writing will be dangerous. I haven't needed to try that, I have got<br /> enough old 720 k drives that can be jumpered or otherwise adapted<br /> to fit.<br /> <br /> Some people have experimented successfully with a diode protected push<br /> <br /> switch with a signal from motor on. See http://www.king27.freeserve.co.uk/<br /> <br /> *BEWARE OF A SERIOUS PITFALL*<br /> Amstrad has the *power connecter wired the other way round* and on top<br /> of that uses yellow for 5 V and red for 12 V!!!!<br /> <br /> Note from FvE: this remark is not valid for the PCW 9512!<br /> <br /> Details and a photo-session on the subject can be viewed on :<br /> * http://www.fvempel.nl/3pc.html<br /> <br /> I have added a changeover switch that allows me to make the 3.5"<br /> either drive A or drive B and the original 3" one the other. Of course<br /> my 3.5" disks have to be formatted differently for either use and the<br /> 3" accessed as drive B will not work, but allows me to boot from 3.5"<br /> and then switch over to use the full 720 k capacity.<br /> <br /> <br /> <br /> C3.2) LocoLink (for Windows) 06/09/2004<br /> <br /> LocoLink is a cable that can connect a PCW to a PC with a parallel<br /> cable (connects to the expansion port of the PCW). The software is a<br /> part of LocoScript Professional or LocoScript PC Easy and converts the<br /> complicated format of the PCW LocoScript file seamless.<br /> <br /> At present there are two versions around, the old LocoLink and LocoLink<br /> for Windows. The latter one provides mouse support and a wider range of<br /> direct conversions to PC format WPs.<br /> <br /> A Laplink serial cable can also be used.<br /> <br /> <br /> C3.3) RS 232 08/04/2001<br /> <br /> RS232 can serve for a null-modem cable to connect to a PC. In order to<br /> create such a cable (when you buy one in a store, do check for the<br /> prescribed connections!) connect the pins as stated below.<br /> <br /> PCW PC<br /> 2 3<br /> 3 2<br /> 5 20<br /> 7 7<br /> 20 5<br /> <br /> Pins 4, 6 and 8 must be connected to each other on the same side! It<br /> may look like a classic 'short circuit', but it has to be done !<br /> So : 4, 6 and 8 connected to each other on the PCW side and 4, 6 and<br /> 8 connected on the PC side connected to each other.<br /> <br /> A Laplink serial cable can also be used.<br /> <br /> For software I would recommend Kermit. An old (v 3.0, 1990) but<br /> functional DOS version can be downloaded : <br /> * http://www.fvempel.nl/mskermit.zip. <br /> * The PCW version is http://www.fvempel.nl/kermpcw.zip.<br /> If you cannot convert it to a 3" contact me. A safe speed is<br /> 9600 bps if you have a standard interface. Other transfer<br /> products like CSTAM and Pipeline will do too. If you have a high<br /> speed model you may try a higher baud rate.<br /> <br /> <br /> C3.4) 3" Drive on PC 08/04/2001<br /> <br /> Operating a 3" 720Kb drive on a PC is very well possible: the cable<br /> required is already presented under A3.1 (the CPC resembles the PCW in<br /> this respect). However, in view of my experiences with it I would<br /> recommend it only to experienced Do-It-Yourselfers. I would not take<br /> the risk and go through the trouble for just 10 3" disks. Besides the<br /> hardware troubles you probably still face the problem of how to convert<br /> LocoScript to a format common on PC's. If you absolutely want to do it,<br /> * consult http://www.fvempel.nl/3pc.html (specific details<br /> for the PCW and a photo session).<br /> <br /> Getting the data on a PC is a problem only with a 3" drive as mounted<br /> in an 8256, 8512 or 9512. When you have a 3.5" fitted there are plenty<br /> of utilities around to read from CF2DD format (Ansible's free<br /> downloadable CPM.EXE, the shareware program 22DISK from Sydex or the<br /> PCWTrans/MS Odball programs by John Elliott). The next problem is<br /> getting the data into a format that can be used on a PC: most programs<br /> (dBase, SuperCalc, Masterfile, TasWord, WordStar, MicroDesign) have a<br /> version commonly available for MS Dos and the CP/M file can therefore<br /> be imported in the PC counterpart easily and without loss of details.<br /> <br /> <br /> C3.5) Acoustic communication 08/08/2000<br /> <br /> At present experiments with acoustic communications are being<br /> conducted (in Spain). This would allow for cheap one-way communication<br /> (only the PCW to PC) that requires a PCW 8000 model, a PC with a sound<br /> card and a microphone. A short BASIC listing (that, will be made<br /> available after release of the programs) can be typed in on the PCW<br /> and will allow files to be converted into beeps (call it morse) that<br /> can be received by the microphone and converted back into files again<br /> on the PC.<br /> <br /> The software works already: the speed (at present 25 bps) is not very<br /> fast but it is a very promising project that finally could provide 3"<br /> PCW'ers with a cheap and easy way to exchange small data files. The<br /> object is to produce a program protocol that can reliably send and<br /> receive up to 400bps with the additional + feature to record it on<br /> tape, thus allowing for playback. Subject to be continued.<br /> <br /> <br /> <br /> C4) Shops supporting PCW 06/09/2004<br /> <br /> Mike Mackenzie (AVCOM Services)<br /> Brisbane, AUSTRALIA<br /> Phone/Fax: 07 32775701 (in Australia)<br /> International callers use "61 7" instead of "07"<br /> Email : avcom gil.com.au<br /> <br /> Elliam Associates still supports the Amstrad 8256, 8512 and 9512 in<br /> the US with software, hardware, supplies and repairs. Their address is<br /> <br /> P.O box 2664, Atascadero, CA 93423, USA<br /> Phone (805) 466-8440<br /> Fax (805) 461-1666<br /> <br /> Pinboard, repairs, parts and disc drives. UK.<br /> Pinboardcomputers btinternet.com<br /> http://www.btinternet.com/~pinboardcomputers<br /> <br /> Merline Serve, hardware and systems, books, consumables, repairs,<br /> parts, games, conversion. See their large, downloadable, catalogue.<br /> http://www.midnight.uk.com/merline<br /> <br /> Cambrian Computers, 50-52 Paget Street, Grangetown Cardiff<br /> 44 2920 384646 still undertakes repairs<br /> <br /> SD Microsystems Ltd, who took over LocoScript Software in 1999, are<br /> dedicated to the profesional support of the Amstrad PCW in general<br /> and all LocoScript products in particular. We offer probably the most<br /> comprehensive range of software and supplies for this market and can<br /> be contacted by phone on 08700 736427, by mail at PO Box 99 Thetford<br /> UK IP24 1NA, by email at sales locoscript.com or via our web site:<br /> http://www.locoscript.com<br /> <br /> <br /> To add a 3" drive to your PC you will need a 3" Disk Kit which<br /> includes both the drive and software to copy files from a 3" disc to<br /> a DOS disc. This is available from Eureka on 01329 239953.<br /> <br /> <br /> There are also some enthusiasts who continue to support the<br /> machines, including limited spares and repairs :<br /> <br /> - Geoffrey Hayes on +44 1606 - 784697<br /> - John King at http://www.pcwking.freeserve.co.uk for technical information,<br /> spares and some second user software.<br /> - Ron King at http://www.king27.freeserve.co.uk for technical information<br /> and repairs.<br /> - Anthony Hill at +44 2920 618012 or 07778 044696, email : anthony.rhill tiscali.co.uk<br /> <br /> HCC Amstrad Gebruikers Groep (Dutch only):<br /> http://www.hccnet.nl/hccworld/groeperingen/groepering.cfm?groep=AMS<br /> or directly at http://www.amstradcg.nl/<br /> <br /> Some clubs continue to exist in supporting the PCW, though many<br /> have expanded to include PC's:<br /> - British Amstrad PCW club<br /> - Crawley PCW club<br /> - North Wales Computer club contact http://www.nwcc.org.uk<br /> <br /> <br /> <br /> HCC Amstrad Gebruikers Groep (Dutch), web site will open in October 2001:<br /> <br /> http://www.hccnet.nl/hccworld/groeperingen/groepering.cfm?groep=AMS<br /> <br /> <br /> Look also for A8.1.4.4<br /> <br /> <br /> C5) Hardware<br /> <br /> C5.1) Printer 08/04/2001<br /> <br /> The original PCW printers can't be used on another computer, being<br /> controlled by the PCW itself.<br /> <br /> The 9 pin matrix printers, as supplied with the PCW 8256, PCW 8512,<br /> PcW 9256 and PcW 10 are basically the same. They are not fully<br /> compatible, though. Printers for the:<br /> <br /> 8256 can be used with the 8512 too. Separate data (flat)<br /> cable and power cord;<br /> 8512 can be used with the 8256 too. Separate data (flat)<br /> cable and power cord;<br /> 9256 only for the 9256. Integrated data and power cable,<br /> IBM/Centronics connector which is NOT Centronics<br /> compatible!!!<br /> 10 only for the 10. Connector type of the 8256/8512 but<br /> integrated data and power supply.<br /> <br /> All of these printers are basically identical, support 7 bit Epson<br /> FX-80 and use Seikosha SP 800/SP 1000 ribbons (available in both nylon<br /> and carbon).<br /> <br /> The matrix printer is one of the first parts that will wear and<br /> eventually break down (after 10 or more years). Spares cannot be<br /> obtained and repair is often an expensive and insufficient option. I<br /> can supply used print heads (at postal expenses) but no guarantee<br /> towards quality or life span. In view of the price of a new computer<br /> plus printer, expanding a PCW with a Centronics printer interface might<br /> be a realistic alternative.<br /> <br /> You would need to pay attention to the availability of printer drivers<br /> for LocoScript and CP/M and/or the emulation modes offered by the new<br /> printer. The original PCW printer is Epson FX compatible: partly<br /> (7 bits only). Other common emulations used on PCW's are HP Laserjet<br /> III, Diablo 630 and Canon BJ.<br /> <br /> The daisy wheel printer as supplied with the PCW 9512 and PcW 9512+<br /> are compatible with each other only. The part that can break down first<br /> in this printer is the hammer, which is subject to violet action.<br /> Spares can be obtained and replacing it is easy. The standard ribbon<br /> type is Olympia Carrera II.<br /> <br /> Some of the 9000 models were supplied with standard non-Amstrad<br /> printers as well, a common model was a Canon but Epsons were supplied<br /> too. Being standard models of printers, they are beyond the scope<br /> of this document.<br /> <br /> The PCW 9512, PcW 9512+, PcW 10 and PcW 16 have a standard parallel<br /> Centronics printer interface, the other types can be equipped with<br /> such a port through the expansion port (by means of an add-on<br /> <br /> interface). Several models were made some of them featuring<br /> additional options like a serial RS 232 port, a real-time clock,<br /> or additional memory (up to 2mb). There is a lot of software for the<br /> PCW's that can make use of external printer: LocoScript (using<br /> softfonts - downloaded from the RAM disc) and MicroDesign (up to 400<br /> dpi graphics) are the top in this respect. But utilities like<br /> landscape printing and screen dumping in text or graphics mode for<br /> CP/M are around too. Again, before considering attaching an external<br /> printer to the PCW, attention should be paid to the best combination(s)<br /> available!<br /> <br /> <br /> C5.2) Keyboard 08/08/2000<br /> <br /> Three different keyboard layouts were produced for most PCW's: the<br /> QWERTY lay-out used for the majority, the QWERTZ for Germans<br /> (Schneider's) and AZERTY for French machines.<br /> <br /> Usually reliable sources have told me that the entire series of PCW<br /> keyboards (8256, 8512, 9512, 9256, 9512+ and 10, that is) can be<br /> exchanged. I have not tested them all but found that the Teqniche (an<br /> XT keyboard meant for the 8000 series) does indeed work with a 9000<br /> model, so the statement should be true. In how far all keys will<br /> respond depends on the software version used but I see not much reason<br /> to exchange keyboards, unless you want to use the 9512/9512+/Teqniche<br /> keyboards on the other machines. PCW keyboard do not work on other<br /> computers (or the other way around).<br /> <br /> Interesting detail is that the PCW keyboards (already customised to<br /> work as a dedicated word processor) can be altered entirely to match<br /> the user preferences. Besides the standard CP/M SETKEYS.COM there is a<br /> more user friendly SMARTKEYS (a Resident System Extension, RSX) and<br /> LocoScript has the LocoKey program available to do the job.<br /> <br /> A negative side effect of the customised keyboard is the confusion<br /> when confronted with standard key-notation of PC (or CPC's for that<br /> matter). Here are some useful keys to remember in CP/M:<br /> <br /> PCW: Other computers:<br /> EXIT ESC<br /> ALT CTRL<br /> SHIFT+EXTRA+EXIT CTRL+ALT+DEL<br /> You will find the three keystrokes above useful when reading computer<br /> books or magazines: they confirm to the standards in the computer<br /> industry. ALT+P will for instance function as a toggle to turn print<br /> output (next to screen output) on or off. EXIT will work for certain<br /> strokes: it is the ESCape character that allows control over the<br /> hardware. This is usually from software to e.g. set the printer<br /> to italic. You can input some of these ESCape codes through the<br /> keyboard:<br /> EXIT+E+EXIT+H+ENTER will clear the screen. CP/M 3.0 converts all input<br /> to capital letters unfortunately so all small letter ESC's will not<br /> work: consult a good book on the subject. Some special key stokes on<br /> the PCW:<br /> PTR Printer control status<br /> EXTRA+PTR graphics screen dump of the screen on<br /> the printer<br /> ALT+ENTER CAPS lock (like SHIFT lock, except for<br /> the numeric keys)<br /> ALT+RELAY NUM lock (enables the 'numeric path',<br /> the section were the cursor keys are<br /> located to produce numbers.<br /> <br /> Using the standard Amstrad SETKEYS (or the enhanced SMARTKEYS) will<br /> allow you to redefine practically all keys on the board as long as you<br /> know it's number and the number of the character or ESC sequence you<br /> want to produce. Certain keys can take more than one character: the<br /> so-called expansion keys. There is a shorter way to modify the<br /> keyboard: the language. Take a look at the manual for the different<br /> accents that will produce.<br /> <br /> The PcW 16 Anne (section D) has a PS/2 compatible keyboard and will<br /> NOT work on a Joyce!<br /> <br /> <br /> C5.3) Disc drive 08/08/2000<br /> <br /> The 3" disc drives of the 8256, 8512 and 9512 can suffer from the some<br /> problems as the Amstrad CPC can. Refer to section A5.1) for tips on<br /> how to solve these. The usual problem with a PCW 3" drive is a worn or<br /> broken drive belt. The typical symptoms are: unable to boot, LED<br /> burning constantly, slipping motor noise and a variety of disc and/or<br /> data errors. When you have only one boot disk but do have more 3" data<br /> disks, try to boot from a data disk. If the PCW does not respond with<br /> three beeps (no system disk in the drive) chances are that the belt is<br /> defective.<br /> <br /> <br /> <br /> C6) Additional hardware 08/08/2000<br /> <br /> C6.1) Memory up to 512 kb 06/09/2004<br /> <br /> All PCW (except the 16) can take a maximum of 512kb on the main board<br /> and all of them do have this amount of RAM, except for the PCW 8256<br /> and PcW 9256, which came with a standard of 256kb. These machines can<br /> easily be upgraded to 512kb using 8 x IC 41256 in the range of 100-150<br /> nanoseconds. This is a standard chip, old fashioned nowadays and<br /> should cost a maximum of 10 euros.<br /> <br /> All extra memory goes into the RAM disc M and will not attribute to<br /> the computers internal memory capacity of 64kb. CP/M and LocoScript<br /> use a so-called bank switching system that allows the use of more than<br /> 64kb: the remainder of memory will go into drive M. A PCW with 256kb<br /> has 110kb drive M, a 512kb model has 368kb drive M. Increasing M can<br /> be very useful, as e.g. disc copying is done through the RAM disc. A<br /> 368 RAM disc will allow you to copy a 720kb disc is 2 passes (4 disc<br /> swaps). Moreover: several programs can work with virtual memory (see<br /> below) and starting (and running data-intensive) programs from disc M<br /> is a lot faster than from floppy disc.<br /> <br /> <br /> C6.2) Memory beyond 512kb 08/08/2000<br /> <br /> Besides the maximum of 512kb on board PCW's can use memory above that:<br /> <br /> the same applies as with normal RAM memory above the bank switching<br /> system. It will be assigned to the RAM disc M. Again, this is very<br /> useful: besides DiscKit, programs like LocoScript 3/4 (softfonts),<br /> MicroDesign (high resolution up to 400dpi), The Rocket, Scratchpad<br /> Plus (the latter two spreadsheets), Flipper (multitasking), The<br /> Network (networking) and several others can use disc M as virtual<br /> memory, thus allowing for more features or capacity.<br /> <br /> Several interfaces (see C6.3) were put on the market, while Cirtech<br /> also produced an on-board version called the Sprinter. That card<br /> replaced the Z80 processor by a faster processor on 8mHz and expanded<br /> memory up to a maximum of (I believe) 2 megabytes. Besides the<br /> processor you had to remove a memory chip as well in order to plug the<br /> Sprinter card onto the main board of the PCW. It fitted for the 8000<br /> models only, as the sizes of the main boards do vary.<br /> <br /> <br /> C6.3) Interfaces (various purposes) 08/04/2001<br /> <br /> An interface is an add-on that fits on the expansion port on the back<br /> of the PCW and provides additional communication ports or memory (at<br /> least that is how I define it). An interface is therefore always an<br /> add-on, but not the other way around. A break-through connector is a<br /> feature that allows a second add-on to be connected on the break-<br /> through connector (basically a second expansion port). This<br /> 'back-packing' of add-ons is commonly known as the Christmas Tree and<br /> can lead to potential dangerous situations regarding the power supply<br /> of the PCW or the risk of losing an add-on. The later is fatal to the<br /> life of any PCW when connected: never (dis-)connect devices while the<br /> PCW is switched ON!!! Many of the add-ons are no longer for sale.<br /> <br /> - Amstrad/Schneider (the German model known as CPS - Centronics<br /> Parallel Schnitstelle). Offered a Centronics parallel and RS 232C<br /> serial port but does not feature a through connector and has a<br /> female Centronics connector: with the normal type of printer that<br /> requires a cable with Centronics male/Centronics male connectors,<br /> rather than the stand Centronics male/IBM.<br /> - SCA Professional & Professional Plus. A look-alike from the original<br /> CPS, but the Professional Plus has a battery-backed up clock plus<br /> software.<br /> - Cirtech parallel interface. Low-budget printer interface with only a<br /> Centronics port. The right, market-standard, connector though!<br /> - Cirtech SpeedPrint. Print spooler that frees the PCW of print jobs.<br /> - Cirtech FlashDrive: non volatile RAM disc memory (data remains after<br /> switching off the PCW) in two different sizes of 1 Mb and 2Mb, with<br /> and without through connector<br /> <br /> - The SCA Rampack is an add-on of additional RAM memory of (I believe)<br /> up to a maximum of 2mb. Break through connector for a second add-on.<br /> - LocoMotive RAMpack, additional memory. Marketed when LocoScript started<br /> featuring downloadle soft fonts (with version 3).<br /> <br /> - Phono Set (Vortex) offered an RS232 port and an acoustic modem. Sure<br /> wish a had such a beast, considering the Spanish project for acoustic<br /> comm's.<br /> <br /> <br /> C6.4) ProScan 08/04/2001<br /> <br /> A hand-held scanner, 400dpi, by Creative Technology for use principally<br /> with MicroDesign and some other graphics packages. Uses an add-on box<br /> for the expansion port (through connector available).<br /> "Best in the West".<br /> <br /> <br /> C6.5) MasterScan 08/08/2000<br /> <br /> A scanner that is fitted on the print head of the 9-pin dot matrix and<br /> connects to the expansion port (break through available). Sheets that<br /> are fed through the printer can be scanned and digitised.<br /> <br /> Although the format supported was screen size only, the supplied<br /> MasterPaint (a Mac look-alike) is a piece of art in itself.<br /> <br /> <br /> C6.6) Electric Studio Light Pen 08/08/2000<br /> <br /> Light Pen from Electric Studio (PCW variant of the CPC device) for use<br /> with, among others, Fleet Street Editor. Break-through available.<br /> <br /> <br /> C6.7) Electric Studio Digitiser 08/08/2000<br /> <br /> Video digitiser, also from Electric Studio. European PAL system, works<br /> neat, although the monochrome effects of saved snapshots sometimes<br /> need editing. Break-through connector is available.<br /> <br /> <br /> C6.8) Robotics Hegatron Grafpad II 08/08/2000<br /> <br /> Graphics drawing pallet with a substitute keyboard (using the pen).<br /> This package was often used for (electrical) technical drawing.<br /> <br /> <br /> C6.9) Intergem interface 08/08/2000<br /> <br /> A lame duck: an interface that allows you to connect an 80 track disc<br /> drive from a BBC computer to the PCW. Not very useful, considering<br /> the number of BBC owners that would want to offer their drive(s) for<br /> this purpose.<br /> <br /> <br /> C6.10) Disc drives 08/04/2001<br /> <br /> Several manufacturers made (Pace) and still make (Pinboard) disc<br /> drives packages that allow 5.25" or 3.5" disc-drives to be connected<br /> to a PCW. In view of the relatively minor adjustments that are<br /> required for a do-it-yourself operation not very useful, unless you<br /> consider an external power supply (power supply is the PCW's weak<br /> spot). And with the exception of the Pinboard drives that are supplied<br /> in a variety of models. Besides switchable types that allow a 3" 720kb<br /> to be operated next to a 3.5" 720kb (both as drive B) there are also<br /> "double deckers" and versions that allow an 8000 model to boot from<br /> 3.5" 720kb discs.<br /> <br /> Pinboard is still in business : Pinboardcomputers btinternet.com<br /> http://www.btinternet.com/~pinboardcomputers/<br /> <br /> LocoScript software supplies a 3.5" that fits into the bay of a 3"<br /> drive, email sales locomotive.com<br /> <br /> ACW Soft (Germany) offered a kit to connect a 3" to the PC, Eureka<br /> 01329 239953 (UK) still does.<br /> <br /> <br /> C6.11) Hard disks 08/08/2000<br /> <br /> Several hard discs were made too for the PCW series.<br /> - The ACC Computer Services came as a 10mb hard disc, with Tasword<br /> (LocoScript was not supported).<br /> - Vortex (Germany) offered the WD2000 of 20mb.<br /> - WEB made a 20mb hard disc.<br /> - ASD supplied one in 10/20/40mb capacity with some utilities.<br /> - Cirtech offers a variety of hard discs with patched versions of<br /> LocoScript 2.<br /> Others were made for networking purposes and are very rare, considering<br /> the expensive software (back then) which came with these.<br /> <br /> <br /> C6.12) Margin Maker 08/08/2000<br /> <br /> A small, inexpensive add-on for the 9-pins matrix printer that allows<br /> for a shortcoming in the PCW's printer. The PCW printer does have a<br /> ruler but lacks a device that will align paper to the chosen left of<br /> right margins.<br /> <br /> <br /> C6.13) Mice & other input devices 08/04/2001<br /> <br /> Lots were made for the PCW series: the Kempston 2-button and the AMX<br /> 3-button mice are the most familiar but Star, Electric Studio and<br /> Gerdes also marketed these. Most DTP packages support these. The AMX<br /> features a through connector.<br /> <br /> Cirtech produced the keymouse, which unlike the others worked through<br /> the keyboard socket.<br /> <br /> d'k Tronics produced a joystick for the PCW and several adapters<br /> appeared from various producers. Some were supported by PCW software,<br /> others were not. A simple diy scheme was around that allowed a<br /> joystick to be connected to the cursor keys of the keyboard. Also see<br /> the sections on the light pen C6.6) and the graphics tablet C6.8).<br /> <br /> The PcW 16 (see section D) has a PS/2 mouse.<br /> <br /> <br /> C6.14) Teqniche keyboard 08/08/2000<br /> <br /> A standard 102 keyboard (IBM AT type) was made for the Amstrad PCW<br /> series. It fits on all PCW's except the PcW 16 (which uses a PS/2<br /> type). A real heavy keyboard featuring separate [F.] function keys,<br /> cursor and numeric keys, adopted for the Amstrad word processing<br /> layout.<br /> <br /> <br /> C6.15) LocoLink & LocoLink for Windows 08/08/2000<br /> <br /> See C3.2) <br /> <br /> <br /> C6.16) d'k Tronics sound synthesiser. 08/08/2000<br /> <br /> A sound synthesiser was produced by d'k Tronics but I do not know of<br /> any details. Some DIY layouts were published in magazines to produce<br /> sound add-ons for PCW's.<br /> <br /> <br /> C6.17) ISA card. 08/04/2001<br /> <br /> The layout to make an Industry Standard Adapter for the PCW is<br /> available on http://user.tninet.se/~psr810p/<br /> <br /> <br /> C6.18) Various DIY layouts. 08/04/2001<br /> <br /> A number of layouts for diy expansions to the PCW can be found on:<br /> * http://www.fvempel.nl/diy.html<br /> Amongst others they contain serial and parallel interfaces plus<br /> some applications for these and small modifications to the system.<br /> <br /> <br /> <br /> C7) Fanzines 06/09/2004<br /> <br /> No magazines are now produced, the last two PCWPlus and Amstrad PCW<br /> User ceased production in 1998 though the information they contained<br /> is still valid. Two Fanzines exist The Disc Dive produced by The<br /> British Amstrad Group, see above for details of membership or receive<br /> copies. The other is PCWtoday, though issue has become intermittent of<br /> late. Their web site http://www.pcwtoday.co.uk<br /> gives details and subscription rates.<br /> <br /> Joyce Bulletin, in Dutch, is the quarterly magazine of the Joyce<br /> Computer Club Amsterdam. It often includes 3" Disks.<br /> It is now available as on-line (Dutch only) Adobe PDF file on:<br /> http://http://www.amstradcg.nl/.<br /> It deviates slightly from the paper version, due to mismatches<br /> between the page layout in PDF and printer settings.<br /> <br /> <br /> <br /> D) PcW 16<br /> <br /> D0) PcW 16 presentation<br /> <br /> This presentation comes from a csa8 article by Cliff Lawson.<br /> <br /> Unlike all previous 4MHz Amstrad Z80 machines this has a 16MHz Z80<br /> core (hence the 16 in PcW16). I know a lot of people "hate" us for not<br /> making it binary compatible with the previous PCWs but the fact is<br /> that we couldn't do it and design the architecture optimised for<br /> graphic word processing software (which means that it is optimised for<br /> BitBlt type graphics). The screen is actually kind of VGA compatible<br /> in that it is 640x480x2 with a straight raster mapping rather than the<br /> character scan raster map and roller RAM of previous PCW (in fact a<br /> lot like the 640x200 mode on the CPC I suppose).<br /> <br /> The main thing that makes this machine such a dream to develop for is<br /> the graphic OS (windows, icons, mice are all in there in the core OS).<br /> The OS was developed in the main by Simon Hargreaves of Creative who<br /> is renowned for MicroDesign on the previous PCWs.<br /> <br /> The Rosanne operating system that he has put together is just so<br /> advanced compared to the other Z80 operating systems that we have been<br /> responsible for in the past that it just seems a shame that any Z80<br /> development talent out there isn't considering writing stuff for the<br /> system - you'd enjoy it, believe me.<br /> <br /> Apart from the graphic stuff, message based event system (a la<br /> Windows) you've got window, menu, dialog, scroll bar, radio button,<br /> checkbox, etc. etc. all immediately available in the OS.<br /> <br /> The OS also has a rich set of disk/flash disk filing stuff. The system<br /> read/writes MS-DOS format files/disks and can also read (not write)<br /> CP/M format files/disks.<br /> <br /> It has fairly advanced memory alloc/dealloc routines and OS support<br /> for 24 bit banked addressing.<br /> <br /> There's an RTC in there so functions exist for that.<br /> <br /> Even the spell checker in the WP is exposed as an OS callable<br /> function.<br /> <br /> Perhaps best of all is the huge support for variable typefaces for<br /> output to both the screen and printer using Swiss and Times in 6, 8,<br /> 10, 11, 12, 14, 18, 24, 36, 72 point.<br /> <br /> The machine has an unused RS232 on the back so there's a possibility<br /> for developing email/news software - perhaps even a web browser!<br /> <br /> There's a help engine in the OS so adding Help support to your apps is<br /> also very easy.<br /> <br /> For doing maths there's a 5 byte floating point system in the OS so<br /> sin/cos/tan/log/exp are all provided.<br /> <br /> If you want to read more about this operating system then get:<br /> ftp://ftp.lip6.fr/pub/amstrad/misc/ROSANDOC.ZIP<br /> or email me direct and chat about it.<br /> <br /> <br /> D1) Emulators 08/08/2000<br /> <br /> D1.1) CP/M v2.2 and 3.1 for the PCW16 08/04/2001<br /> <br /> Get this CP/M emulator for PcW16 by John Elliott at<br /> http://www.seasip.demon.co.uk/Cpm/pcw16.html<br /> or get directly ftp://ftp.lip6.fr/pub/amstrad/cpm/cpm_101.zip<br /> <br /> <br /> D1.2) M.E.S.S. 08/04/2001<br /> <br /> See above<br /> <br /> <br /> <br /> D2) Support 08/04/2001<br /> <br /> <br /> The PcW16 is still supported by Comsoft, Creative technology and<br /> Locomotive.<br /> <br /> <br /> <br /> <br /> If you know a PcW16 owner who can't download the operating system<br /> upgrades from Cliff Lawson's Web site, Brian Watson will supply a free<br /> upgrade for a DS/HD disk, return postage, and an address label. Send<br /> disk in a reusable padded bag to the address at A8.1.3.3). Or download<br /> the boot disc of a PcW 16 (rescue disk) at :<br /> <br /> <br /> <br /> http://web.ukonline.co.uk/cliff.lawson/files/pcwos.zip<br /> <br /> <br /> <br /> <br /> For more frequently asked questions and other support information, go to<br /> http://www.pcw16ers.fsnet.co.uk<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> E - PDA600 10/10/2000<br /> <br /> <br /> <br /> <br /> E0) PDA600 presentation 10/10/2000<br /> <br /> <br /> <br /> <br /> the PDA600<br /> <br /> <br /> <br /> <br /> The Amstrad PDA-600 Pen Pad created in 1993 has a weight of 400<br /> grams (14 ounces, 0.87 pound), size is 115mm x 160mm x 27mm<br /> (6.3" x 4.3" x 1.0"). The CPU is a Zilog Z8S180 at 14.3 Mhz. There<br /> is a reflective LCD screen by Kyorcera is 240 x 320 pixels, 70mm<br /> x 93mm (3.5" x 2.75"). The screen is pressure sensitive for Letter<br /> based printed handwriting recognition. It uses 3 batteries and a<br /> lithium pile. It has 128 Ko memory, 32 Ko for display, 32 Ko for<br /> recogniser software. It can also use PCMCIA type 1 SRAM cards upto<br /> 2 Mo. It features address list, telephone list, diary, time manager,<br /> todo list, note-taker, world time, multiple alarms, calculator,<br /> calendar, OS by the Eden Group, Mini serial RS232, Speaker, RTC.<br /> Optional Extras : PC-Organiser for Windows, Forms Software, memory.<br /> Probably the first PDA on the market.<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> F - CP/M 04/21/2002<br /> <br /> <br /> <br /> <br /> CP/M is an operating system widely used with computers before ms-dos<br /> existed. It is available on Amstrad CPC, PCW and the NC with ZCN. For<br /> more information, read the newsgroup comp.os.cpm and its FAQ at<br /> ftp://rtfm.mit.edu/pub/usenet/comp.os.cpm<br /> The Unofficial CP/M Web site : http://www.cpm.z80.de<br /> <br /> <br /> I823L814L180LD3.66KLRD3.66KRank13.3MAge2001|03|30l0+1n/awhoissourceRank27.2MTraffic0Video Adv0More dataSummary reportDiagnosisDensity98190n/a</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=User:DavidL&diff=102592 User:DavidL 2018-12-30T13:43:23Z

<p>DavidL: </p> <hr /> <div>----<br /> Hi.<br /> <br /> I'm a French software development engineer with several years experience.<br /> <br /> I'm currently developing a generic machine emulator, which currently successfully runs a complete Amstrad PC1512. I didn't find any software that could not run on the emulated machine unless it would not run on the original machine.<br /> I started creating components to emulate the CPC464. This site is a good source for documentation.<br /> <br /> [[User:DavidL|DavidL]] ([[User talk:DavidL|talk]])<br /> <br /> ----<br /> +-------+<br /> | |<br /> +---------------------------------------------------------------------------------------------------------------------------+ | ▲ |<br /> | _ | | | <br /> | (_) | +-------+-------+-------+<br /> | A M S T R A D C P C 4 6 4 | | | | |<br /> | ORDINATEUR PERSONNEL COULEUR 64K COULEUR | | ◄ | COPY | ► |<br /> +---------------------------------------------------------------------------------------------------------------------------+ | | | |<br /> +-------+-------+-------+<br /> +-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-----------+ | |<br /> | | | | | | | | | | | | | | | | | ▼ |<br /> | ESC | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | [ | _ | CLR | DEL | | |<br /> | | & | é | " | ' | ( | ] | è | ! | ç | à | ) | - | | | +-------+<br /> +-------+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-----------+ +-------+-------+-------+<br /> | | | | | | | | | | | | | | | | | | |<br /> | TAB | Q | W | E | R | T | Y | U | I | O | P | | | < | | | 7 | 8 | 9 |<br /> | | | | | | | | | | | | ^ | * | | | | | |<br /> +-----------+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+-----+-+ ENTER | +-------+-------+-------+<br /> | | | | | | | | | | | | | | | | | | |<br /> | CAPS | A | S | D | F | G | H | J | K | L | / | + | > | | | 4 | 5 | 6 |<br /> | LOCK | | | | | | | | | | : | = | # | | | | | |<br /> +-------------+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-------------+ +-------+-------+-------+<br /> | | | | | | | | | | | | | | | | | |<br /> | SHIFT | Z | X | C | V | B | N | M | . | % | ? | @ \ | SHIFT | | 1 | 2 | 3 |<br /> | | | | | | | | | ; | ù | , | $ | | | | | |<br /> +-----------------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-----------------+ +-------+-------+-------+<br /> | | | | | | |<br /> | | CTRL | | 0 | . | ENTER |<br /> | | | | | | |<br /> +-----------------------------------------------------------------------+-------+ +-------+-------+-------+<br /> <br /> <br /> ----</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template_talk:CpcPower&diff=102591 Template talk:CpcPower 2018-12-30T11:11:37Z

<p>DavidL: Created page with "== Duplicate template == This is a duplicate template of :Template:CPCPower. I think these two pages need fusionning (preserving history), but I do not have administratio..."</p> <hr /> <div>== Duplicate template ==<br /> This is a duplicate template of [[:Template:CPCPower]].<br /> <br /> I think these two pages need fusionning (preserving history), but I do not have administration rights to do it.<br /> <br /> --[[User:DavidL|DavidL]] ([[User talk:DavidL|talk]]) 06:11, 30 December 2018 (EST)</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102590 Template:BrokenLink 2018-12-30T11:06:45Z

<p>DavidL: + Category:External link templates</p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''|text=''text''}}<br /> <br /> Mandatory parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> Optional parameter is:<br /> ;''text'':Text for the link. By default, same as URL.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33|<br /> text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> |}<br /> <br /> [[Category:External link templates]]<br /> </noinclude><includeonly>[{{{1}}} {{{text|{{{1}}}}}}] <small> ([https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}])</small></includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:CpcPower&diff=102589 Template:CpcPower 2018-12-30T11:04:45Z

<p>DavidL: </p> <hr /> <div>[http://www.cpc-power.com/index.php?page=detail&num={{{1}}} CPC-Power.com: {{{2}}}]<br /> <noinclude><br /> This template needs two parameters:<br /> * File-ID of the game at CPC-Power.com (have a look at the URL)<br /> * Link text<br /> == Example ==<br /> You can use it with:<br /> <nowiki>{{CpcPower|1234|Link text}}</nowiki><br /> </noinclude></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Z80_-_undocumented_opcodes&diff=102588 Z80 - undocumented opcodes 2018-12-30T11:01:54Z

<p>DavidL: /* Web links */</p> <hr /> <div>The [[Z80|Z80]] CPU contains several undocumented opcodes, which can be quite helpful sometimes. The most useful undocumented opcodes are probably these ones, which split up the 16bit index registers IX and IY in 8bit registers called IXL,IXH,IYL and IYH. <br /> <br /> Please note, that many Z80 successors like the Z180 are NOT able to execute some of the following opcodes properly. <br /> <br /> This is just an overview. Parts of this article have been copied from the [http://www.myquest.nl/z80undocumented/ "The Undocumented Z80 Documented"] originally by Sean Young and currently maintained by Jan Wilmans, which is one of the most comprehensive descriptions around. <br /> <br /> == CB prefix ==<br /> <br /> Of the 247 opcodes that use the prefix &CB, the block &CB &30 to &CB &37 is undocumented officially. These commands shift the operand register left and set its lowest bit to 1.<br /> <br /> This is in contrast to SRL (Shift Right Logical), which shifts right and clears the highest bit. Some believe these opcodes were supposed to be Shift Left Logical but that the setting of the lowest bit represents a bug in the Z80, claiming this is why the opcodes are undocumented. Others call the opcodes SLIA, for Shift Left Inverted Arithmetic.<br /> <br /> Regardless of the story behind this operation, its effective result is ''register'' = (''register'' * 2) + 1, something that does have its uses and has been employed in various programming contexts for that reason.<br /> <br /> <pre>CB30 SLL B<br /> CB31 SLL C<br /> CB32 SLL D<br /> CB33 SLL E<br /> CB34 SLL H<br /> CB35 SLL L<br /> CB36 SLL (HL)<br /> CB37 SLL A<br /> </pre><br /> <br /> == DD and FD prefixes ==<br /> <br /> The &DD or &FD prefixes are documented as causing operations using the 16-bit register HL to instead work with either of the 16-bit indexing registers IX or IY; if the operations access a memory location (''i.e.'' normally LD A,(HL), ''etc.''), the opcodes must additionally include an extra byte that specifies a signed displacement (-128 to +127) from IX/IY.<br /> <br /> However, Zilog have not documented the fact that these prefixes also affect opcodes that usually refer to the 8-bit components of HL, ''i.e.'' H and L. Thus, one gains access to the additional registers IXH, IXL, IYH, and IYL, for almost all commands that normally use H or L. It is even possible to do things like LD IXH,IXL (although you cannot combine IX and IY in the same instruction, for obvious reasons). These registers can be useful in routines that must process and/or store a lot of numbers. Thankfully, they are not as slow as their 16-bit counterparts: whereas access to (IX+d) is usually slower by 3 NOPs than the equivalent operation upon (HL), using the 8-bit components is (like PUSH IX, ''etc.'') only 1 NOP slower, and this is only due to the need to parse the prefixing byte.<br /> <br /> <pre>DB #DD:LD H,A -&gt; LD IXH,A<br /> DB #FD:LD B,L -&gt; LD B,IYL<br /> </pre> <br /> Note: These registers are called LX, LY, HX, and HY by [[WinAPE]]'s debugger, although its assembler uses the names given above.<br /> <br /> == ED prefix ==<br /> <br /> There are a number of undocumented EDxx instructions, of which most are duplicates of documented instructions. Any instruction not listed has no effect (same behaviour as 2 NOP instructions). <br /> <br /> The complete list except for the block instructions: <br /> <pre>ED40 IN B,(C) ED60 IN H,(C)<br /> ED41 OUT (C),B ED61 OUT (C),H<br /> ED42 SBC HL,BC ED62 SBC HL,HL<br /> ED43 LD (nn),BC ED63 LD (nn),HL<br /> ED44 NEG ED64 NEG *<br /> ED45 RETN ED65 RETN *<br /> ED46 IM 0 ED66 IM 0 *<br /> ED47 LD I,A ED67 RRD<br /> ED48 IN C,(C) ED68 IN L,(C)<br /> ED49 OUT (C),C ED69 OUT (C),L<br /> ED4A ADC HL,BC ED6A ADC HL,HL<br /> ED4B LD BC,(nn) ED6B LD HL,(nn)<br /> ED4C NEG * ED6C NEG *<br /> ED4D RETI ED6D RETN *<br /> ED4E IM 0 * ED6E IM 0 *<br /> ED4F LD R,A ED6F RLD<br /> ED50 IN D,(C) ED70 IN (C) / IN F,(C) *<br /> ED51 OUT (C),D ED71 OUT (C),0 *<br /> ED52 SBC HL,DE ED72 SBC HL,SP<br /> ED53 LD (nn),DE ED73 LD (nn),SP<br /> ED54 NEG * ED74 NEG *<br /> ED55 RETN * ED75 RETN *<br /> ED56 IM 1 ED76 IM 1 *<br /> ED57 LD A,I ED77 NOP *<br /> ED58 IN E,(C) ED78 IN A,(C)<br /> ED59 OUT (C),E ED79 OUT (C),A<br /> ED5A ADC HL,DE ED7A ADC HL,SP<br /> ED5B LD DE,(nn) ED7B LD SP,(nn)<br /> ED5C NEG * ED7C NEG *<br /> ED5D RETN * ED7D RETN *<br /> ED5E IM 2 ED7E IM 2 *<br /> ED5F LD A,R ED7F NOP *<br /> * = undocumented opcodes<br /> </pre> <br /> == DDCB prefix ==<br /> <br /> The undocumented DDCB instructions store the result (if any) of the operation in one of the seven all-purpose registers, which one depends on the lower 3 bits of the last byte of the opcode (not operand, so not the offset). <br /> <pre>000 B<br /> 001 C<br /> 010 D<br /> 011 E<br /> 100 H<br /> 101 L<br /> 110 (none: documented opcode)<br /> 111 A<br /> </pre> <br /> The documented DDCB0106 is RLC (IX+01h). So, clear the lower three bits (DDCB0100) and something is done to register B. The result of the RLC (which is stored in (IX+01h)) is now also stored in register B. Effectively, it does the following: <br /> <pre>LD B,(IX+01h)<br /> RLC B<br /> LD (IX+01h),B<br /> </pre> <br /> So you get double value for money. The result is stored in B and (IX+01h). The most common notation is: RLC (IX+01h),B <br /> <br /> I’ve once seen this notation: <br /> <pre>RLC (IX+01h)<br /> LD B,(IX+01h)<br /> </pre> <br /> That’s not correct: B contains the rotated value, even if (IX+01h) points to ROM. The DDCB SET and RES instructions do the same thing as the shift/rotate instructions: <br /> <pre>DDCB10C0 SET 0,(IX+10h),B<br /> DDCB10C1 SET 0,(IX+10h),C<br /> DDCB10C2 SET 0,(IX+10h),D<br /> DDCB10C3 SET 0,(IX+10h),E<br /> DDCB10C4 SET 0,(IX+10h),H<br /> DDCB10C5 SET 0,(IX+10h),L<br /> DDCB10C6 SET 0,(IX+10h) - documented instruction<br /> DDCB10C7 SET 0,(IX+10h),A<br /> </pre> <br /> So for example with the last instruction, the value of (IX+10h) with bit 0 set is also stored in register A. <br /> <br /> The DDCB BIT instructions do not store any value; they merely test a bit. That’s why the undocumented DDCB BIT instructions are no different from the official ones: <br /> <pre>DDCB d 78 BIT 7,(IX+d)<br /> DDCB d 79 BIT 7,(IX+d)<br /> DDCB d 7A BIT 7,(IX+d)<br /> DDCB d 7B BIT 7,(IX+d)<br /> DDCB d 7C BIT 7,(IX+d)<br /> DDCB d 7D BIT 7,(IX+d)<br /> DDCB d 7E BIT 7,(IX+d) - documented instruction<br /> DDCB d 7F BIT 7,(IX+d)<br /> </pre> <br /> == FDCB prefix ==<br /> <br /> Same as for the DDCB prefix, though IY is used instead of IX. <br /> <br /> == Web links ==<br /> <br /> * [http://www.myquest.nl/z80undocumented/z80-documented-v0.91.pdf "The Undocumented Z80 Documented" by Sean Young Version 0.91, 18th September, 2005] at [http://www.myquest.nl/z80undocumented/ Jan Wilmans' Website] <br /> * {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> <br /> <br /> [[Category:Programming]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102587 Template:BrokenLink 2018-12-30T11:00:28Z

<p>DavidL: </p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''|text=''text''}}<br /> <br /> Mandatory parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> Optional parameter is:<br /> ;''text'':Text for the link. By default, same as URL.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33|<br /> text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> |}<br /> <br /> </noinclude><includeonly>[{{{1}}} {{{text|{{{1}}}}}}] <small> ([https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}])</small></includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Z80_-_undocumented_opcodes&diff=102586 Z80 - undocumented opcodes 2018-12-30T10:59:59Z

<p>DavidL: /* Web links */</p> <hr /> <div>The [[Z80|Z80]] CPU contains several undocumented opcodes, which can be quite helpful sometimes. The most useful undocumented opcodes are probably these ones, which split up the 16bit index registers IX and IY in 8bit registers called IXL,IXH,IYL and IYH. <br /> <br /> Please note, that many Z80 successors like the Z180 are NOT able to execute some of the following opcodes properly. <br /> <br /> This is just an overview. Parts of this article have been copied from the [http://www.myquest.nl/z80undocumented/ "The Undocumented Z80 Documented"] originally by Sean Young and currently maintained by Jan Wilmans, which is one of the most comprehensive descriptions around. <br /> <br /> == CB prefix ==<br /> <br /> Of the 247 opcodes that use the prefix &CB, the block &CB &30 to &CB &37 is undocumented officially. These commands shift the operand register left and set its lowest bit to 1.<br /> <br /> This is in contrast to SRL (Shift Right Logical), which shifts right and clears the highest bit. Some believe these opcodes were supposed to be Shift Left Logical but that the setting of the lowest bit represents a bug in the Z80, claiming this is why the opcodes are undocumented. Others call the opcodes SLIA, for Shift Left Inverted Arithmetic.<br /> <br /> Regardless of the story behind this operation, its effective result is ''register'' = (''register'' * 2) + 1, something that does have its uses and has been employed in various programming contexts for that reason.<br /> <br /> <pre>CB30 SLL B<br /> CB31 SLL C<br /> CB32 SLL D<br /> CB33 SLL E<br /> CB34 SLL H<br /> CB35 SLL L<br /> CB36 SLL (HL)<br /> CB37 SLL A<br /> </pre><br /> <br /> == DD and FD prefixes ==<br /> <br /> The &DD or &FD prefixes are documented as causing operations using the 16-bit register HL to instead work with either of the 16-bit indexing registers IX or IY; if the operations access a memory location (''i.e.'' normally LD A,(HL), ''etc.''), the opcodes must additionally include an extra byte that specifies a signed displacement (-128 to +127) from IX/IY.<br /> <br /> However, Zilog have not documented the fact that these prefixes also affect opcodes that usually refer to the 8-bit components of HL, ''i.e.'' H and L. Thus, one gains access to the additional registers IXH, IXL, IYH, and IYL, for almost all commands that normally use H or L. It is even possible to do things like LD IXH,IXL (although you cannot combine IX and IY in the same instruction, for obvious reasons). These registers can be useful in routines that must process and/or store a lot of numbers. Thankfully, they are not as slow as their 16-bit counterparts: whereas access to (IX+d) is usually slower by 3 NOPs than the equivalent operation upon (HL), using the 8-bit components is (like PUSH IX, ''etc.'') only 1 NOP slower, and this is only due to the need to parse the prefixing byte.<br /> <br /> <pre>DB #DD:LD H,A -&gt; LD IXH,A<br /> DB #FD:LD B,L -&gt; LD B,IYL<br /> </pre> <br /> Note: These registers are called LX, LY, HX, and HY by [[WinAPE]]'s debugger, although its assembler uses the names given above.<br /> <br /> == ED prefix ==<br /> <br /> There are a number of undocumented EDxx instructions, of which most are duplicates of documented instructions. Any instruction not listed has no effect (same behaviour as 2 NOP instructions). <br /> <br /> The complete list except for the block instructions: <br /> <pre>ED40 IN B,(C) ED60 IN H,(C)<br /> ED41 OUT (C),B ED61 OUT (C),H<br /> ED42 SBC HL,BC ED62 SBC HL,HL<br /> ED43 LD (nn),BC ED63 LD (nn),HL<br /> ED44 NEG ED64 NEG *<br /> ED45 RETN ED65 RETN *<br /> ED46 IM 0 ED66 IM 0 *<br /> ED47 LD I,A ED67 RRD<br /> ED48 IN C,(C) ED68 IN L,(C)<br /> ED49 OUT (C),C ED69 OUT (C),L<br /> ED4A ADC HL,BC ED6A ADC HL,HL<br /> ED4B LD BC,(nn) ED6B LD HL,(nn)<br /> ED4C NEG * ED6C NEG *<br /> ED4D RETI ED6D RETN *<br /> ED4E IM 0 * ED6E IM 0 *<br /> ED4F LD R,A ED6F RLD<br /> ED50 IN D,(C) ED70 IN (C) / IN F,(C) *<br /> ED51 OUT (C),D ED71 OUT (C),0 *<br /> ED52 SBC HL,DE ED72 SBC HL,SP<br /> ED53 LD (nn),DE ED73 LD (nn),SP<br /> ED54 NEG * ED74 NEG *<br /> ED55 RETN * ED75 RETN *<br /> ED56 IM 1 ED76 IM 1 *<br /> ED57 LD A,I ED77 NOP *<br /> ED58 IN E,(C) ED78 IN A,(C)<br /> ED59 OUT (C),E ED79 OUT (C),A<br /> ED5A ADC HL,DE ED7A ADC HL,SP<br /> ED5B LD DE,(nn) ED7B LD SP,(nn)<br /> ED5C NEG * ED7C NEG *<br /> ED5D RETN * ED7D RETN *<br /> ED5E IM 2 ED7E IM 2 *<br /> ED5F LD A,R ED7F NOP *<br /> * = undocumented opcodes<br /> </pre> <br /> == DDCB prefix ==<br /> <br /> The undocumented DDCB instructions store the result (if any) of the operation in one of the seven all-purpose registers, which one depends on the lower 3 bits of the last byte of the opcode (not operand, so not the offset). <br /> <pre>000 B<br /> 001 C<br /> 010 D<br /> 011 E<br /> 100 H<br /> 101 L<br /> 110 (none: documented opcode)<br /> 111 A<br /> </pre> <br /> The documented DDCB0106 is RLC (IX+01h). So, clear the lower three bits (DDCB0100) and something is done to register B. The result of the RLC (which is stored in (IX+01h)) is now also stored in register B. Effectively, it does the following: <br /> <pre>LD B,(IX+01h)<br /> RLC B<br /> LD (IX+01h),B<br /> </pre> <br /> So you get double value for money. The result is stored in B and (IX+01h). The most common notation is: RLC (IX+01h),B <br /> <br /> I’ve once seen this notation: <br /> <pre>RLC (IX+01h)<br /> LD B,(IX+01h)<br /> </pre> <br /> That’s not correct: B contains the rotated value, even if (IX+01h) points to ROM. The DDCB SET and RES instructions do the same thing as the shift/rotate instructions: <br /> <pre>DDCB10C0 SET 0,(IX+10h),B<br /> DDCB10C1 SET 0,(IX+10h),C<br /> DDCB10C2 SET 0,(IX+10h),D<br /> DDCB10C3 SET 0,(IX+10h),E<br /> DDCB10C4 SET 0,(IX+10h),H<br /> DDCB10C5 SET 0,(IX+10h),L<br /> DDCB10C6 SET 0,(IX+10h) - documented instruction<br /> DDCB10C7 SET 0,(IX+10h),A<br /> </pre> <br /> So for example with the last instruction, the value of (IX+10h) with bit 0 set is also stored in register A. <br /> <br /> The DDCB BIT instructions do not store any value; they merely test a bit. That’s why the undocumented DDCB BIT instructions are no different from the official ones: <br /> <pre>DDCB d 78 BIT 7,(IX+d)<br /> DDCB d 79 BIT 7,(IX+d)<br /> DDCB d 7A BIT 7,(IX+d)<br /> DDCB d 7B BIT 7,(IX+d)<br /> DDCB d 7C BIT 7,(IX+d)<br /> DDCB d 7D BIT 7,(IX+d)<br /> DDCB d 7E BIT 7,(IX+d) - documented instruction<br /> DDCB d 7F BIT 7,(IX+d)<br /> </pre> <br /> == FDCB prefix ==<br /> <br /> Same as for the DDCB prefix, though IY is used instead of IX. <br /> <br /> == Web links ==<br /> <br /> *[http://www.myquest.nl/z80undocumented/z80-documented-v0.91.pdf "The Undocumented Z80 Documented" by Sean Young Version 0.91, 18th September, 2005] at [http://www.myquest.nl/z80undocumented/ Jan Wilmans' Website] <br /> *{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> <br /> <br /> [[Category:Programming]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102585 Template:BrokenLink 2018-12-30T10:59:25Z

<p>DavidL: /* Example */</p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''|text=''text''}}<br /> <br /> Mandatory parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> Optional parameter is:<br /> ;''text'':Text for the link. By default, same as URL.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33|<br /> text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> |}<br /> <br /> </noinclude><includeonly><br /> [{{{1}}} {{{text|{{{1}}}}}}] <small> ([https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}])</small><br /> </includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102584 Template:BrokenLink 2018-12-30T10:58:08Z

<p>DavidL: </p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''|text=''text''}}<br /> <br /> Mandatory parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> Optional parameter is:<br /> ;''text'':Text for the link. By default, same as URL.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33|<br /> text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> |}<br /> <br /> </noinclude><includeonly><br /> [{{{1}}} {{{text|{{{1}}}}}}] <small>([https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}])</small><br /> </includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102583 Template:BrokenLink 2018-12-30T10:57:46Z

<p>DavidL: </p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''|text=''text''}}<br /> <br /> Mandatory parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> Optional parameter is:<br /> ;''text'':Text for the link. By default, same as URL.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33|<br /> text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> |}<br /> <br /> </noinclude><includeonly><br /> [{{{1}}} {{{text|{{{1}}}}}}] ([https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}])<br /> </includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102582 Template:BrokenLink 2018-12-30T10:57:21Z

<p>DavidL: </p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''|text=''text''}}<br /> <br /> Mandatory parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> Optional parameter is:<br /> ;''text'':Text for the link. By default, same as URL.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33|<br /> text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33|text=Short information about the internal "MEMPTR" 16bit register of the Z80 and its influence on the F-Register}}<br /> |}<br /> <br /> </noinclude><includeonly><br /> [{{{1}}} {{{text|{{{1}}}}}}] / [https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}]<br /> </includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102581 Template:BrokenLink 2018-12-30T10:54:47Z

<p>DavidL: </p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''}}<br /> <br /> Parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> </noinclude><includeonly><br /> [{{{1}}} {{{text|{{{1}}}}}}] / [https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}]<br /> </includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Template:BrokenLink&diff=102580 Template:BrokenLink 2018-12-30T10:53:46Z

<p>DavidL: New Template for alternative link to web.archive.org when a website is not available</p> <hr /> <div><noinclude><br /> == Description ==<br /> <br /> This template is used to present an alternative link to an archive on web.archive.org of a web site that became unavailable.<br /> <br /> == Syntax ==<br /> <br /> <nowiki>{{</nowiki>BrokenLink|''url''|''year''|''month''|''day''|''hour''|''minute''|''second''}}<br /> <br /> Parameters are the following:<br /> ;''url'': URL of the website<br /> ;''year'', ''month'', ''day'': Snapshot date from web.archive.org of the website. Each value must be padded with zeroes to have 4-digit year, and 2-digits month and day.<br /> ;''hour'', ''minute'', ''second'': Snapshot time from web.archive.org of the website. Each value must be padded with zeroes to have 2-digits hour, minute and second.<br /> <br /> == Example ==<br /> <br /> {|<br /> |<br /> <nowiki>{{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|<br /> 2017|01|22|21|32|33}}</nowiki><br /> |-<br /> |<br /> {{BrokenLink|http://www.grimware.org/lib/exe/fetch.php/documentations/devices/z80/z80.memptr.eng.txt|2017|01|22|21|32|33}}<br /> |}<br /> <br /> </noinclude><includeonly><br /> [{{{1}}} {{{text|{{{1}}}}}}]<br /> - Resource no more available, archived here: [https://web.archive.org/web/{{{2}}}{{{3}}}{{{4}}}{{{5}}}{{{6}}}{{{7}}}/{{{1}}} Web archive {{{2}}}-{{{3}}}-{{{4}}} {{{5}}}:{{{6}}}:{{{7}}}]<br /> </includeonly></div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Some_features_of_the_Z80&diff=102573 Some features of the Z80 2018-12-29T21:45:41Z

<p>DavidL: /* IFF0 and IFF1 */ --> IFF1 and IFF2 are official names found in all Zilog Z80 datasheets</p> <hr /> <div><div style="border: 1px solid rgb(228, 222, 222); margin: 0px 0px 5px; padding: 0.5em 1em; background-color: rgb(249, 249, 249);"><center>'''''This article originally came from Kevin Thackers' archive at [http://www.cpctech.org.uk http://www.cpctech.org.uk].'''''</center></div> <br /> <br /> ==Flags/Status Register (F and F')==<br /> <br /> This register contains the condition flags. When a command is executed the flags are used to show information about the result. (e.g. the flags may be used to check if the result was positive, negative or zero). <br /> <br /> The flags register has this form: <br /> <br /> <br /> {| border="1"<br /> | Bit 7<br /> | Sign flag<br /> <br /> |-<br /> | Bit 6<br /> | Zero flag<br /> <br /> |-<br /> | Bit 5<br /> | (note 1)<br /> <br /> |-<br /> | Bit 4<br /> | Half-carry flag<br /> <br /> |-<br /> | Bit 3<br /> | (note 1)<br /> <br /> |-<br /> | Bit 2<br /> | Parity/Overflow flag<br /> <br /> |-<br /> | Bit 1<br /> | Subtract flag<br /> <br /> |-<br /> | Bit 0<br /> | Carry flag<br /> <br /> |}<br /> Note: <br /> <br /> There are two bits in the flags register which are documented by Zilog as being unused. But in fact these bits do change: these bits are updated according to an undocumented register of the Z80 named either WZ or MEMPTR. This undocumented register is used to store temporary results such as 16-bits arithmetic results, and address (for example, loading I register and the vector byte for interruption mode 2 to compute the value to load in PC register).<br /> <br /> == Sign flag ==<br /> This flag indicates if the result is positive or negative. If a result is negative, this flag is set to 1, if the result is positive, this flag is set to 0. <br /> <br /> == Zero flag ==<br /> This flag indicates if the result is zero or non-zero. If the result was zero, this flag would be set to 1, if the result was non-zero (i.e. a number other than zero), this flag would be set to 0. <br /> <br /> == Parity/Overflow ==<br /> This bit has two functions. In some commands it is used to show parity and other commands it is used to show overflow. <br /> <br /> Parity: <br /> <br /> If a byte has an even number of 1 digits then it has "even parity", and if the byte has an odd number of 1 digits then it has "odd parity". <br /> <br /> The Parity Overflow is set to 1 when the byte has even parity, and set to 0 if the byte has odd parity. <br /> <br /> Overflow: <br /> <br /> This bit will hold the overflow after a arithmetic command. <br /> <br /> == Subtract ==<br /> This flag is set to 1 if the command used subtraction, it is set to 0 if the command used addition. This flag is used in the execution of the DAA instruction to calculate the correct BCD representation of the contents of A. <br /> <br /> == Half-Carry flag ==<br /> This flag holds the carry from bit 3 to bit 4. It is used by the DAA instruction to convert the contents of the A register to BCD form. <br /> <br /> == Carry flag ==<br /> This flag holds the carry. <br /> <br /> '''Refresh Register (R)'''<br /> <br /> This register is special and it cannot be used to store data. Some people consider it to be random, but it is not, and you can easily predict it's value. However, by the way it works, it could be used as a simple but crude random number generator. <br /> <br /> This register is used mainly in protections, because when an instruction is added or removed the value of R will be different to the intended value and the data will not be deprotected correctly. <br /> <br /> Bit 7 remains unchanged, and it's value is only defined when a LD R,A instruction is executed. The lower 7 bits hold a count which is incremented after each z80 instruction executed. <br /> <br /> Generally, all commands which have a &CB, &ED, &DD or &FD prefix, increment R by 2, and all other commands increment R by 1. The execeptions to this rule are commands which repeat. <br /> <br /> '''Interrupt Modes'''<br /> <br /> The interrupt mode can be defined using the "IM" instruction. There are 3 interrupt modes: mode 0, mode 1 and mode 2. <br /> <br /> The descriptions below assume: <br /> <br /> * Interrupt requests are accepted by Z80, <br /> * An interrupt request has been issued <br /> <br /> == Mode 0 ==<br /> In this mode, the interrupting device will generate an interrupt and put a single-byte instruction onto the CPU bus. The Z80 will execute this instruction, and then continue with program execution. Since we can only put a single byte onto the bus, the RST instructions provide an excellent way of handling different interrupts. <br /> <br /> On a standard CPC the byte on the cpu data bus is normally &FF (but this is not guaranteed). &FF corresponds to the "RST 38H" instruction, and therefore on the CPC interrupt mode 0 is the same as interrupt mode 1. <br /> <br /> On the Plus, the ASIC will generate a byte to put onto the processor data bus, see the documentation on the ASIC for a description of this byte. <br /> <br /> == Mode 1 ==<br /> In this mode the following will be done when a interrupt is "executed": <br /> <br /> * The current program counter (PC) is pushed onto the stack. (SP) <br /> * The program counter address is set to &0038. <br /> <br /> == Mode 2 ==<br /> In this mode the following will be done when a interrupt is "executed": <br /> <br /> * The current program counter (PC) is pushed onto the stack (SP), <br /> * A address is formed using the I register and the data on the bus. <br /> <br /> <br /> {| class="prettytable"<br /> | Bit 15..8<br /> | from I register<br /> <br /> |-<br /> | Bit 7..0<br /> | Byte put onto processor bus by interrupting device<br /> <br /> |}<br /> * The Z80 will read the interrupt handler address from the location pointed to by the interrupt handler pointer, and then jump to that address. interrupt handler pointer: <br /> <br /> On a standard CPC, the byte put onto the processor bus is always &FF. So, on a standard CPC the following will be done: <br /> <br /> * The current Program Counter is pushed onto the stack <br /> * The z80 fetches an address from &xxFF and jumps to that address. (where xx is the value from the I register) <br /> <br /> On a Plus, the ASIC can generate a different byte to put on the processor bus. So the lower 8 bits may be different. This is part of the extended interrupt handling features to cope with DMA Sound interrupts, scan line interrupts etc.. <br /> <br /> '''The Interrupt Vector Register (I)'''<br /> <br /> The I register is used in Z80 Interrupt Mode 2 to form When it is used in this way, it forms the upper 8-bits of an address which points to the interrupt handler. The lower 8-bits are put onto the CPU bus by an interrupting device. If you program uses Mode 0 or Mode 1 interrupts, then this register can be used to store data. <br /> <br /> '''DAA (Decimal Adjust accumulator)'''<br /> <br /> This Z80 command will convert the contents of the A register to BCD (Binary-Coded-Decimal) representation. (e.g. the BCD representation of 15 is &15). DAA uses the carry flag, subtract flag, half-carry flag and the A register to calculate a value to add to the A register to change it into a BCD number. I believe that the original value in the A register must be in BCD for this conversion to work. It is provided so that any non-BCD value can be added to a BCD value and then the result can be adjusted to BCD again. I tried to convert from a non-BCD number to BCD using DAA and it didnt work. In the following tables, x corresponds to the upper nibble of register A (before the command has executed), and y corresponds to the lower nibble. These tables show the value that is added to the A register to convert it to BCD representation depending on the flags. These values are the ones used by my emulator (A-CPC). I have found information about other tables, but these did not produce the correct values. <br /> <br /> <br /> Flags set Byte<br /> (0..9)(0..9)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &00<br /> Carry: + &60<br /> Subtract: + &00<br /> Subtract+Carry: + &A0<br /> Half-carry: + &06<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &FA<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> Flags set Byte<br /> (0..9)(A..F)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &06<br /> Carry: + &66<br /> Subtract: + &00<br /> Subtract+Carry: + &a0<br /> Half-carry: + &06<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> <br /> Flags set Byte<br /> (A..F)(0..9)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &60<br /> Carry: + &60<br /> Subtract: + &00<br /> Subtract+Carry: + &A0<br /> Half-carry: + &66<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> <br /> Flags set Byte<br /> (A..F)(A..F)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &66<br /> Carry: + &66<br /> Subtract: + &00<br /> Subtract+Carry: + &a0<br /> Half-carry: + &66<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> '''LDIR and LDDR'''<br /> <br /> This is a block copying function, it is used to transfer data from one part of memory to another fast. <br /> <br /> * HL must be pre-loaded with the start address <br /> * DE must be pre-loaded with the destination address <br /> * BC must be pre-loaded with the length of data <br /> <br /> == LDIR ==<br /> LDIR operation: <br /> <br /> * read byte from memory address pointed to by HL and write it to the memory address pointed to by DE <br /> * Increment HL by 1 <br /> * Increment DE by 1 <br /> * If BC=0 then increment PC by 2 (otherwise dont increment it) <br /> <br /> == LDDR ==<br /> LDDR operation: <br /> <br /> * read byte from memory address pointed to by HL and write it to the memory address pointed to by DE <br /> * Decrement HL by 1 <br /> * Decrement DE by 1 <br /> * Increment Program counter by 2 <br /> * If BC=0 then increment PC by 2 (otherwise dont increment it) <br /> <br /> == NOTES ==<br /> * an interrupt can occur while a LDIR/LDDR is being executed. <br /> <br /> * If the LDIR/LDDR opcode is overwritten by itself then command execution will stop. Effectively, the LDIR opcode is repeatidly fetched and decoded for each byte fetched from memory. <br /> <br /> == IFF1 and IFF2 ==<br /> IFF1 reflects the state of the maskable interrupt. The maskable interrupt can be enabled using the Z80 instruction "EI" and disabled using the Z80 instruction "DI". When IFF1 is "1" masked interrupts are enabled, when a interrupt request is received by the Z80 it will be acknowledged and the interrupt handler executed. When IFF1 is "0" masked interrupts are disabled, any interrupt requests are ignored. <br /> <br /> When a non-maskable interrupt (NMI) is executed by the Z80, IFF2 is set to the value of IFF1. Then IFF1 is set to "0" to disable maskable interrupts. The NMI handler will be executed. When a "RETN" instruction is executed by the Z80, IFF1 is set to the value in IFF2, therefore the maskable interrupt state is restored. The state of IFF1 can be set at any time using the "DI" and "EI" instructions.<br /> <br /> == IM 0, IM 1, IM 2 ==<br /> * The instructions "IM 0 ","IM 1" and "IM 2" set the Z80 interrupt mode which defines the actions taken to execute the maskable interrupt handler.<br /> <br /> [[Category:Programming]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Some_features_of_the_Z80&diff=102572 Some features of the Z80 2018-12-29T20:29:43Z

<p>DavidL: /* Flags/Status Register (F and F') */</p> <hr /> <div><div style="border: 1px solid rgb(228, 222, 222); margin: 0px 0px 5px; padding: 0.5em 1em; background-color: rgb(249, 249, 249);"><center>'''''This article originally came from Kevin Thackers' archive at [http://www.cpctech.org.uk http://www.cpctech.org.uk].'''''</center></div> <br /> <br /> ==Flags/Status Register (F and F')==<br /> <br /> This register contains the condition flags. When a command is executed the flags are used to show information about the result. (e.g. the flags may be used to check if the result was positive, negative or zero). <br /> <br /> The flags register has this form: <br /> <br /> <br /> {| border="1"<br /> | Bit 7<br /> | Sign flag<br /> <br /> |-<br /> | Bit 6<br /> | Zero flag<br /> <br /> |-<br /> | Bit 5<br /> | (note 1)<br /> <br /> |-<br /> | Bit 4<br /> | Half-carry flag<br /> <br /> |-<br /> | Bit 3<br /> | (note 1)<br /> <br /> |-<br /> | Bit 2<br /> | Parity/Overflow flag<br /> <br /> |-<br /> | Bit 1<br /> | Subtract flag<br /> <br /> |-<br /> | Bit 0<br /> | Carry flag<br /> <br /> |}<br /> Note: <br /> <br /> There are two bits in the flags register which are documented by Zilog as being unused. But in fact these bits do change: these bits are updated according to an undocumented register of the Z80 named either WZ or MEMPTR. This undocumented register is used to store temporary results such as 16-bits arithmetic results, and address (for example, loading I register and the vector byte for interruption mode 2 to compute the value to load in PC register).<br /> <br /> == Sign flag ==<br /> This flag indicates if the result is positive or negative. If a result is negative, this flag is set to 1, if the result is positive, this flag is set to 0. <br /> <br /> == Zero flag ==<br /> This flag indicates if the result is zero or non-zero. If the result was zero, this flag would be set to 1, if the result was non-zero (i.e. a number other than zero), this flag would be set to 0. <br /> <br /> == Parity/Overflow ==<br /> This bit has two functions. In some commands it is used to show parity and other commands it is used to show overflow. <br /> <br /> Parity: <br /> <br /> If a byte has an even number of 1 digits then it has "even parity", and if the byte has an odd number of 1 digits then it has "odd parity". <br /> <br /> The Parity Overflow is set to 1 when the byte has even parity, and set to 0 if the byte has odd parity. <br /> <br /> Overflow: <br /> <br /> This bit will hold the overflow after a arithmetic command. <br /> <br /> == Subtract ==<br /> This flag is set to 1 if the command used subtraction, it is set to 0 if the command used addition. This flag is used in the execution of the DAA instruction to calculate the correct BCD representation of the contents of A. <br /> <br /> == Half-Carry flag ==<br /> This flag holds the carry from bit 3 to bit 4. It is used by the DAA instruction to convert the contents of the A register to BCD form. <br /> <br /> == Carry flag ==<br /> This flag holds the carry. <br /> <br /> '''Refresh Register (R)'''<br /> <br /> This register is special and it cannot be used to store data. Some people consider it to be random, but it is not, and you can easily predict it's value. However, by the way it works, it could be used as a simple but crude random number generator. <br /> <br /> This register is used mainly in protections, because when an instruction is added or removed the value of R will be different to the intended value and the data will not be deprotected correctly. <br /> <br /> Bit 7 remains unchanged, and it's value is only defined when a LD R,A instruction is executed. The lower 7 bits hold a count which is incremented after each z80 instruction executed. <br /> <br /> Generally, all commands which have a &CB, &ED, &DD or &FD prefix, increment R by 2, and all other commands increment R by 1. The execeptions to this rule are commands which repeat. <br /> <br /> '''Interrupt Modes'''<br /> <br /> The interrupt mode can be defined using the "IM" instruction. There are 3 interrupt modes: mode 0, mode 1 and mode 2. <br /> <br /> The descriptions below assume: <br /> <br /> * Interrupt requests are accepted by Z80, <br /> * An interrupt request has been issued <br /> <br /> == Mode 0 ==<br /> In this mode, the interrupting device will generate an interrupt and put a single-byte instruction onto the CPU bus. The Z80 will execute this instruction, and then continue with program execution. Since we can only put a single byte onto the bus, the RST instructions provide an excellent way of handling different interrupts. <br /> <br /> On a standard CPC the byte on the cpu data bus is normally &FF (but this is not guaranteed). &FF corresponds to the "RST 38H" instruction, and therefore on the CPC interrupt mode 0 is the same as interrupt mode 1. <br /> <br /> On the Plus, the ASIC will generate a byte to put onto the processor data bus, see the documentation on the ASIC for a description of this byte. <br /> <br /> == Mode 1 ==<br /> In this mode the following will be done when a interrupt is "executed": <br /> <br /> * The current program counter (PC) is pushed onto the stack. (SP) <br /> * The program counter address is set to &0038. <br /> <br /> == Mode 2 ==<br /> In this mode the following will be done when a interrupt is "executed": <br /> <br /> * The current program counter (PC) is pushed onto the stack (SP), <br /> * A address is formed using the I register and the data on the bus. <br /> <br /> <br /> {| class="prettytable"<br /> | Bit 15..8<br /> | from I register<br /> <br /> |-<br /> | Bit 7..0<br /> | Byte put onto processor bus by interrupting device<br /> <br /> |}<br /> * The Z80 will read the interrupt handler address from the location pointed to by the interrupt handler pointer, and then jump to that address. interrupt handler pointer: <br /> <br /> On a standard CPC, the byte put onto the processor bus is always &FF. So, on a standard CPC the following will be done: <br /> <br /> * The current Program Counter is pushed onto the stack <br /> * The z80 fetches an address from &xxFF and jumps to that address. (where xx is the value from the I register) <br /> <br /> On a Plus, the ASIC can generate a different byte to put on the processor bus. So the lower 8 bits may be different. This is part of the extended interrupt handling features to cope with DMA Sound interrupts, scan line interrupts etc.. <br /> <br /> '''The Interrupt Vector Register (I)'''<br /> <br /> The I register is used in Z80 Interrupt Mode 2 to form When it is used in this way, it forms the upper 8-bits of an address which points to the interrupt handler. The lower 8-bits are put onto the CPU bus by an interrupting device. If you program uses Mode 0 or Mode 1 interrupts, then this register can be used to store data. <br /> <br /> '''DAA (Decimal Adjust accumulator)'''<br /> <br /> This Z80 command will convert the contents of the A register to BCD (Binary-Coded-Decimal) representation. (e.g. the BCD representation of 15 is &15). DAA uses the carry flag, subtract flag, half-carry flag and the A register to calculate a value to add to the A register to change it into a BCD number. I believe that the original value in the A register must be in BCD for this conversion to work. It is provided so that any non-BCD value can be added to a BCD value and then the result can be adjusted to BCD again. I tried to convert from a non-BCD number to BCD using DAA and it didnt work. In the following tables, x corresponds to the upper nibble of register A (before the command has executed), and y corresponds to the lower nibble. These tables show the value that is added to the A register to convert it to BCD representation depending on the flags. These values are the ones used by my emulator (A-CPC). I have found information about other tables, but these did not produce the correct values. <br /> <br /> <br /> Flags set Byte<br /> (0..9)(0..9)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &00<br /> Carry: + &60<br /> Subtract: + &00<br /> Subtract+Carry: + &A0<br /> Half-carry: + &06<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &FA<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> Flags set Byte<br /> (0..9)(A..F)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &06<br /> Carry: + &66<br /> Subtract: + &00<br /> Subtract+Carry: + &a0<br /> Half-carry: + &06<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> <br /> Flags set Byte<br /> (A..F)(0..9)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &60<br /> Carry: + &60<br /> Subtract: + &00<br /> Subtract+Carry: + &A0<br /> Half-carry: + &66<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> <br /> Flags set Byte<br /> (A..F)(A..F)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &66<br /> Carry: + &66<br /> Subtract: + &00<br /> Subtract+Carry: + &a0<br /> Half-carry: + &66<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> '''LDIR and LDDR'''<br /> <br /> This is a block copying function, it is used to transfer data from one part of memory to another fast. <br /> <br /> * HL must be pre-loaded with the start address <br /> * DE must be pre-loaded with the destination address <br /> * BC must be pre-loaded with the length of data <br /> <br /> == LDIR ==<br /> LDIR operation: <br /> <br /> * read byte from memory address pointed to by HL and write it to the memory address pointed to by DE <br /> * Increment HL by 1 <br /> * Increment DE by 1 <br /> * If BC=0 then increment PC by 2 (otherwise dont increment it) <br /> <br /> == LDDR ==<br /> LDDR operation: <br /> <br /> * read byte from memory address pointed to by HL and write it to the memory address pointed to by DE <br /> * Decrement HL by 1 <br /> * Decrement DE by 1 <br /> * Increment Program counter by 2 <br /> * If BC=0 then increment PC by 2 (otherwise dont increment it) <br /> <br /> == NOTES ==<br /> * an interrupt can occur while a LDIR/LDDR is being executed. <br /> <br /> * If the LDIR/LDDR opcode is overwritten by itself then command execution will stop. Effectively, the LDIR opcode is repeatidly fetched and decoded for each byte fetched from memory. <br /> <br /> == IFF0 and IFF1 ==<br /> IFF0 reflects the state of the maskable interrupt. The maskable interrupt can be enabled using the Z80 instruction "EI" and disabled using the Z80 instruction "DI". When IFF0 is "1" masked interrupts are enabled, when a interrupt request is received by the Z80 it will be acknowledged and the interrupt handler executed. When IFF0 is "0" masked interrupts are disabled, any interrupt requests are ignored. <br /> <br /> When a non-maskable interrupt (NMI) is executed by the Z80, IFF1 is set to the value of IFF0. Then IFF0 is set to "0" to disable maskable interrupts. The NMI handler will be executed.When a "RETN" instruction is executed by the Z80, IFF0 is set to the value in IFF1, therefore the maskable interrupt state is restored. The state of IFF0 can be set at any time using the "DI" and "EI" instructions. <br /> <br /> == IM 0, IM 1, IM 2 ==<br /> * The instructions "IM 0 ","IM 1" and "IM 2" set the Z80 interrupt mode which defines the actions taken to execute the maskable interrupt handler.<br /> <br /> [[Category:Programming]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=Some_features_of_the_Z80&diff=102571 Some features of the Z80 2018-12-29T20:28:48Z

<p>DavidL: /* Flags/Status Register (F and F') */ Completing information about undocumented flags bits 5 & 3</p> <hr /> <div><div style="border: 1px solid rgb(228, 222, 222); margin: 0px 0px 5px; padding: 0.5em 1em; background-color: rgb(249, 249, 249);"><center>'''''This article originally came from Kevin Thackers' archive at [http://www.cpctech.org.uk http://www.cpctech.org.uk].'''''</center></div> <br /> <br /> ==Flags/Status Register (F and F')==<br /> <br /> This register contains the condition flags. When a command is executed the flags are used to show information about the result. (e.g. the flags may be used to check if the result was positive, negative or zero). <br /> <br /> The flags register has this form: <br /> <br /> <br /> {| border="1"<br /> | Bit 7<br /> | Sign flag<br /> <br /> |-<br /> | Bit 6<br /> | Zero flag<br /> <br /> |-<br /> | Bit 5<br /> | (note 1)<br /> <br /> |-<br /> | Bit 4<br /> | Half-carry flag<br /> <br /> |-<br /> | Bit 3<br /> | (note 1)<br /> <br /> |-<br /> | Bit 2<br /> | Parity/Overflow flag<br /> <br /> |-<br /> | Bit 1<br /> | Subtract flag<br /> <br /> |-<br /> | Bit 0<br /> | Carry flag<br /> <br /> |}<br /> Note: <br /> <br /> There are two bits in the flags register which are documented by Zilog as being unused. But in fact these bits do change: these bits are updated according to an undocumented register of the Z80 named either WZ or MEMPTR. This undocumented register is used to store temporary results such as 16-bits arithmetic results, and address (for example, loading I and the vector byte for interruption mode 2 to compute the value to load in PC).<br /> <br /> == Sign flag ==<br /> This flag indicates if the result is positive or negative. If a result is negative, this flag is set to 1, if the result is positive, this flag is set to 0. <br /> <br /> == Zero flag ==<br /> This flag indicates if the result is zero or non-zero. If the result was zero, this flag would be set to 1, if the result was non-zero (i.e. a number other than zero), this flag would be set to 0. <br /> <br /> == Parity/Overflow ==<br /> This bit has two functions. In some commands it is used to show parity and other commands it is used to show overflow. <br /> <br /> Parity: <br /> <br /> If a byte has an even number of 1 digits then it has "even parity", and if the byte has an odd number of 1 digits then it has "odd parity". <br /> <br /> The Parity Overflow is set to 1 when the byte has even parity, and set to 0 if the byte has odd parity. <br /> <br /> Overflow: <br /> <br /> This bit will hold the overflow after a arithmetic command. <br /> <br /> == Subtract ==<br /> This flag is set to 1 if the command used subtraction, it is set to 0 if the command used addition. This flag is used in the execution of the DAA instruction to calculate the correct BCD representation of the contents of A. <br /> <br /> == Half-Carry flag ==<br /> This flag holds the carry from bit 3 to bit 4. It is used by the DAA instruction to convert the contents of the A register to BCD form. <br /> <br /> == Carry flag ==<br /> This flag holds the carry. <br /> <br /> '''Refresh Register (R)'''<br /> <br /> This register is special and it cannot be used to store data. Some people consider it to be random, but it is not, and you can easily predict it's value. However, by the way it works, it could be used as a simple but crude random number generator. <br /> <br /> This register is used mainly in protections, because when an instruction is added or removed the value of R will be different to the intended value and the data will not be deprotected correctly. <br /> <br /> Bit 7 remains unchanged, and it's value is only defined when a LD R,A instruction is executed. The lower 7 bits hold a count which is incremented after each z80 instruction executed. <br /> <br /> Generally, all commands which have a &CB, &ED, &DD or &FD prefix, increment R by 2, and all other commands increment R by 1. The execeptions to this rule are commands which repeat. <br /> <br /> '''Interrupt Modes'''<br /> <br /> The interrupt mode can be defined using the "IM" instruction. There are 3 interrupt modes: mode 0, mode 1 and mode 2. <br /> <br /> The descriptions below assume: <br /> <br /> * Interrupt requests are accepted by Z80, <br /> * An interrupt request has been issued <br /> <br /> == Mode 0 ==<br /> In this mode, the interrupting device will generate an interrupt and put a single-byte instruction onto the CPU bus. The Z80 will execute this instruction, and then continue with program execution. Since we can only put a single byte onto the bus, the RST instructions provide an excellent way of handling different interrupts. <br /> <br /> On a standard CPC the byte on the cpu data bus is normally &FF (but this is not guaranteed). &FF corresponds to the "RST 38H" instruction, and therefore on the CPC interrupt mode 0 is the same as interrupt mode 1. <br /> <br /> On the Plus, the ASIC will generate a byte to put onto the processor data bus, see the documentation on the ASIC for a description of this byte. <br /> <br /> == Mode 1 ==<br /> In this mode the following will be done when a interrupt is "executed": <br /> <br /> * The current program counter (PC) is pushed onto the stack. (SP) <br /> * The program counter address is set to &0038. <br /> <br /> == Mode 2 ==<br /> In this mode the following will be done when a interrupt is "executed": <br /> <br /> * The current program counter (PC) is pushed onto the stack (SP), <br /> * A address is formed using the I register and the data on the bus. <br /> <br /> <br /> {| class="prettytable"<br /> | Bit 15..8<br /> | from I register<br /> <br /> |-<br /> | Bit 7..0<br /> | Byte put onto processor bus by interrupting device<br /> <br /> |}<br /> * The Z80 will read the interrupt handler address from the location pointed to by the interrupt handler pointer, and then jump to that address. interrupt handler pointer: <br /> <br /> On a standard CPC, the byte put onto the processor bus is always &FF. So, on a standard CPC the following will be done: <br /> <br /> * The current Program Counter is pushed onto the stack <br /> * The z80 fetches an address from &xxFF and jumps to that address. (where xx is the value from the I register) <br /> <br /> On a Plus, the ASIC can generate a different byte to put on the processor bus. So the lower 8 bits may be different. This is part of the extended interrupt handling features to cope with DMA Sound interrupts, scan line interrupts etc.. <br /> <br /> '''The Interrupt Vector Register (I)'''<br /> <br /> The I register is used in Z80 Interrupt Mode 2 to form When it is used in this way, it forms the upper 8-bits of an address which points to the interrupt handler. The lower 8-bits are put onto the CPU bus by an interrupting device. If you program uses Mode 0 or Mode 1 interrupts, then this register can be used to store data. <br /> <br /> '''DAA (Decimal Adjust accumulator)'''<br /> <br /> This Z80 command will convert the contents of the A register to BCD (Binary-Coded-Decimal) representation. (e.g. the BCD representation of 15 is &15). DAA uses the carry flag, subtract flag, half-carry flag and the A register to calculate a value to add to the A register to change it into a BCD number. I believe that the original value in the A register must be in BCD for this conversion to work. It is provided so that any non-BCD value can be added to a BCD value and then the result can be adjusted to BCD again. I tried to convert from a non-BCD number to BCD using DAA and it didnt work. In the following tables, x corresponds to the upper nibble of register A (before the command has executed), and y corresponds to the lower nibble. These tables show the value that is added to the A register to convert it to BCD representation depending on the flags. These values are the ones used by my emulator (A-CPC). I have found information about other tables, but these did not produce the correct values. <br /> <br /> <br /> Flags set Byte<br /> (0..9)(0..9)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &00<br /> Carry: + &60<br /> Subtract: + &00<br /> Subtract+Carry: + &A0<br /> Half-carry: + &06<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &FA<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> Flags set Byte<br /> (0..9)(A..F)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &06<br /> Carry: + &66<br /> Subtract: + &00<br /> Subtract+Carry: + &a0<br /> Half-carry: + &06<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> <br /> Flags set Byte<br /> (A..F)(0..9)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &60<br /> Carry: + &60<br /> Subtract: + &00<br /> Subtract+Carry: + &A0<br /> Half-carry: + &66<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> <br /> Flags set Byte<br /> (A..F)(A..F)<br /> <nowiki>--------------------------------------------</nowiki><br /> <br /> (None) + &66<br /> Carry: + &66<br /> Subtract: + &00<br /> Subtract+Carry: + &a0<br /> Half-carry: + &66<br /> Half-carry+Carry: + &66<br /> Half-carry+Subtract: + &fa<br /> Half-carry+Subtract+Carry: + &9A<br /> <br /> '''LDIR and LDDR'''<br /> <br /> This is a block copying function, it is used to transfer data from one part of memory to another fast. <br /> <br /> * HL must be pre-loaded with the start address <br /> * DE must be pre-loaded with the destination address <br /> * BC must be pre-loaded with the length of data <br /> <br /> == LDIR ==<br /> LDIR operation: <br /> <br /> * read byte from memory address pointed to by HL and write it to the memory address pointed to by DE <br /> * Increment HL by 1 <br /> * Increment DE by 1 <br /> * If BC=0 then increment PC by 2 (otherwise dont increment it) <br /> <br /> == LDDR ==<br /> LDDR operation: <br /> <br /> * read byte from memory address pointed to by HL and write it to the memory address pointed to by DE <br /> * Decrement HL by 1 <br /> * Decrement DE by 1 <br /> * Increment Program counter by 2 <br /> * If BC=0 then increment PC by 2 (otherwise dont increment it) <br /> <br /> == NOTES ==<br /> * an interrupt can occur while a LDIR/LDDR is being executed. <br /> <br /> * If the LDIR/LDDR opcode is overwritten by itself then command execution will stop. Effectively, the LDIR opcode is repeatidly fetched and decoded for each byte fetched from memory. <br /> <br /> == IFF0 and IFF1 ==<br /> IFF0 reflects the state of the maskable interrupt. The maskable interrupt can be enabled using the Z80 instruction "EI" and disabled using the Z80 instruction "DI". When IFF0 is "1" masked interrupts are enabled, when a interrupt request is received by the Z80 it will be acknowledged and the interrupt handler executed. When IFF0 is "0" masked interrupts are disabled, any interrupt requests are ignored. <br /> <br /> When a non-maskable interrupt (NMI) is executed by the Z80, IFF1 is set to the value of IFF0. Then IFF0 is set to "0" to disable maskable interrupts. The NMI handler will be executed.When a "RETN" instruction is executed by the Z80, IFF0 is set to the value in IFF1, therefore the maskable interrupt state is restored. The state of IFF0 can be set at any time using the "DI" and "EI" instructions. <br /> <br /> == IM 0, IM 1, IM 2 ==<br /> * The instructions "IM 0 ","IM 1" and "IM 2" set the Z80 interrupt mode which defines the actions taken to execute the maskable interrupt handler.<br /> <br /> [[Category:Programming]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=CRTC&diff=102541 CRTC 2018-12-29T01:35:24Z

<p>DavidL: /* The 6845 Registers */ Add explanation</p> <hr /> <div>* ''This is an article about the "Cathode Ray Tube Controller" hardware unit of the Amstrad CPC. For the cpc scene member see [[ChaRleyTroniC]]''<br /> <br /> <br /> The '''CRTC''' (Cathode Ray Tube Controller) helps to generate the video signal of the Amstrad CPC.<br /> <br /> NOTE: This document describes the functionality in terms of the CPC with its separate CRTC and Gate-Array. The Plus has both integrated into the same IC, but could be considered to have two functional blocks, one for CRTC and one for Gate-Array. In this document the term 'Gate-Array' is used, but this also applies to the ASIC.<br /> <br /> == Overview ==<br /> <br /> The 6845 Cathode Ray Tube Controller (CRTC) is a programmable IC used to generate video displays. This IC is used in a variety of computers including the Amstrad CPC, Amstrad CPC+ and KC Compact. <br /> <br /> The CRTC was a common part available from many different manufacturers. During the life of the CPC, Amstrad sourced the CRTC from various manufacturers. <br /> <br /> All ICs used were based on the same design but have a different implementation. As a result they do not operate identically in all situations. This document highlights these differences. <br /> <br /> This table lists the known ICs used, with their part number, manufacturer and type number. <br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''Part number''||''Manufacturer''||''Type number (note 3)''<br /> |-<br /> |HD6845S||Hitachi||0<br /> |-<br /> |UM6845||UMC||0<br /> |-<br /> |UM6845R||UMC||1<br /> |-<br /> |MC6845||Motorola||2<br /> |-<br /> |AMS40489||Amstrad||3 (note 1)<br /> |-<br /> |40226||Amstrad||4 (note 2)<br /> |}<br /> <br /> '''NOTES''' <br /> <br /> 1. The CRTC functionality is integrated into the CPC+ ASIC. This type exists only in the CPC464+,CPC6128+ and GX4000. <br /> <br /> 2. This type exists in "cost-down" CPC464 and CPC6128 systems. In the "cost-down" the CRTC functionality is integrated into a single ASIC IC. This ASIC is often refered to as the "Pre-ASIC" because it preceeded the CPC+ ASIC. The CRTC functionality of the Pre-ASIC is almost identical to the CRTC within the ASIC.<br /> <br /> 3. In the Amstrad community each 6845 implementation has been assigned a type number. This type identifies a group of implementations which operate in exactly the same way. <br /> <br /> As far as I know, the type number system was originally used by demo programmers. <br /> <br /> It is possible to detect the 6845 present using software methods, and this is done to: <br /> <br /> * warn that the software was not designed for the detected 6845 and may function incorrectly, <br /> * to adapt the software so that it will run with the detected 6845 <br /> * In most cases, the type of the detected 6845 is reported. <br /> <br /> 4. As far as I know, the KC compact used HD6845R only.<br /> <br /> == Timings and relating with Z80 instructions count ==<br /> <br /> Some informations like : how many Z80 instructions can I fit within a scan line ? Within a screen ? Etc... See http://www.cpcwiki.eu/forum/programming/frame-flyback-and-interrupts/msg25106/#msg25106<br /> (To be extracted/edited to conform to wiki good practices).<br /> <br /> ==Programming==<br /> <br /> The 6845 is selected when bit 14 of the I/O port address is set to "0". Bit 9 and 8 of the I/O port address define the function to access. The remaining bits can be any value, but it is adviseable to set these to "1" to avoid conflict with other devices in the system.<br /> <br /> The recommended I/O port addresses are<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''I/O port address''||''Function''||''Read/Write''<br /> |-<br /> |&BCxx||Select 6845 register||Write only<br /> |-<br /> |&BDxx||Write 6845 register data||Write only<br /> |-<br /> |&BExx||(note 1)||Read only<br /> |-<br /> |&BFxx||(note 1)||Read only<br /> |-<br /> |}<br /> <br /> '''NOTE'''<br /> <br /> 1. The function of these I/O ports is dependant on the CRTC type<br /> <br /> 2. If you perform an IN instruction to the select or write functions it will write data to the CRTC from the current data on the bus.<br /> <br /> ==Addressing==<br /> <br /> The following table defines the generated memory address from the CRTC and Gate-Array signals. <br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''Memory Address Signal''||''Signal source''||''Signal name''<br /> |-<br /> |A15||6845||MA13 <br /> |-<br /> |A14||6845||MA12<br /> |-<br /> |A13||6845||RA2 <br /> |-<br /> |A12||6845||RA1 <br /> |-<br /> |A11||6845||RA0 <br /> |-<br /> |A10||6845||MA9 <br /> |-<br /> |A9||6845||MA8 <br /> |-<br /> |A8||6845||MA7 <br /> |-<br /> |A7||6845||MA6 <br /> |-<br /> |A6||6845||MA5 <br /> |-<br /> |A5||6845||MA4 <br /> |-<br /> |A4||6845||MA3 <br /> |-<br /> |A3||6845||MA2 <br /> |-<br /> |A2||6845||MA1 <br /> |-<br /> |A1||6845||MA0<br /> |-<br /> |A0||Gate-Array||CCLK<br /> |-<br /> |}<br /> <br /> CRTC generates the address, Gate-Array reads the data and converts it to pixels based on the current mode.<br /> <br /> == DISPTMG ==<br /> <br /> DISPTMG signal defines the border. When DISPTMG is "1" the border colour is output by the Gate-Array to the display. The DISPTMG can be forced using R8 (DISPTMG Skew) on type 0,3 and 4 or by setting R6=0 on type 1. It is not possible to force the DISPTMG on type 2 or 5.<br /> <br /> The border has higher priority than pixels but lower priority than the black colour output when HSYNC/VSYNC are active.<br /> <br /> == HSYNC and VSYNC ==<br /> <br /> On CPC, HSYNC and VSYNC from the CRTC are passed into the Gate-Array.<br /> <br /> When HSYNC is active Gate-Array outputs the palette colour black. If the HSYNC is set to 14 characters then black will be output for 14us.<br /> <br /> The HSYNC is modified before being sent to the monitor. It happens 2us after the HSYNC from the CRTC and lasts 4us when HSYNC length is greater or equal to 6. <br /> <br /> If R2=46, and HSYNC width is 14 then monitor hsync starts at 48 and lasts until 51.<br /> <br /> On a CPC monitor, the HSYNC is rendered in "absolute black". It is darker than the black output by the Gate-Array.<br /> <br /> The VSYNC is also modified before being sent to the monitor. It happens two lines* after the VSYNC from the CRTC and stay two lines (same cut rule if VSYNC is lower than 4). PAL (50Hz) does need two lines VSYNC_width, and 4us HSYNC_width.<br /> <br /> Using CRTC1, VSYNC width value 0 means a value of 16.<br /> <br /> == The 6845 Registers ==<br /> <br /> The Internal registers of the 6845 are:<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''Register Index''||''Register Name''||''Range''||''CPC Setting''||''Notes''<br /> |-<br /> |0||Horizontal Total||00000000||63||Width of the screen, in characters. Should always be 63 (64 characters). 1 character == 1μs.<br /> |-<br /> |1||Horizontal Displayed||00000000||40||Number of characters displayed. Once horizontal character count (HCC) matches this value, DISPTMG is set to 1.<br /> |-<br /> |2||Horizontal Sync Position||00000000||46||When to start the HSync signal.<br /> |-<br /> |3||Horizontal and Vertical Sync Widths||VVVVHHHH||128+14||HSync pulse width in characters (0 means 16 on some CRTC), should always be more than 8; VSync width in scan-lines. (0 means 16 on some CRTC. Not present on all CRTCs, fixed to 16 lines on these)<br /> |-<br /> |4||Vertical Total||x0000000||38||Height of the screen, in characters.<br /> |-<br /> |5||Vertical Total Adjust||xxx00000||0||Measured in scanlines, can be used for smooth vertical scrolling on CPC.<br /> |-<br /> |6||Vertical Displayed||x0000000||25||Height of displayed screen in characters. Once vertical character count (VCC) matches this value, DISPTMG is set to 1.<br /> |-<br /> |7||Vertical Sync position||x0000000||30||When to start the VSync signal, in characters.<br /> |-<br /> |8||Interlace and Skew||xxxxxx00||0||00: No interlace; 01: Interlace Sync Raster Scan Mode; 10: No Interlace; 11: Interlace Sync and Video Raster Scan Mode<br /> |-<br /> |9||Maximum Raster Address||xxx00000||7||Maximum scan line address on CPC can hold between 0 and 7, higher values' upper bits are ignored<br /> |-<br /> |10||Cursor Start Raster||xBP00000||0||Cursor not used on CPC. B = Blink On/Off; P = Blink Period Control (Slow/Fast). Sets first raster row of character that cursor is on to invert.<br /> |-<br /> |11||Cursor End Raster||xxx00000||0||Sets last raster row of character that cursor is on to invert<br /> |-<br /> |12||Display Start Address (High)||xx000000||48<br /> |-<br /> |13||Display Start Address (Low)||00000000||0||Allows you to offset the start of screen memory for hardware scrolling, and if using memory from address &0000 with the firmware.<br /> |-<br /> |14||Cursor Address (High)||xx000000||0<br /> |-<br /> |15||Cursor Address (Low)||00000000||0<br /> |-<br /> |16||Light Pen Address (High)||xx000000||||Read Only<br /> |-<br /> |17||Light Pen Address (Low)||00000000||||Read Only<br /> |-<br /> |}<br /> <br /> registers 18-31 read as 0, on type 0 and 2.<br /> registers 18-30 read as 0 on type1, register 31 reads as 0x0ff.<br /> <br /> Details about Reg. 12 and Reg. 13 specifically:<br /> <br /> .------- REG 12 --------. .------- REG 13 --------.<br /> | | | |<br /> 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00<br /> .--.--.--.--.--.--.--.--. .--.--.--.--.--.--.--.--.<br /> |X |X | | | | | | | | | | | | | | | |<br /> '--'--'--'--'--'--'--'--' '--'--'--'--'--'--'--'--'<br /> '--.--'--.--'---------------.-----------------'<br /> | | |<br /> | | '------> Offset for setting<br /> | | videoram <br /> | | (1024 positions)<br /> | | Bits 0..9<br /> | |<br /> | '-------------------------> Video Buffer : note (1)<br /> |<br /> '-------------------------------> Video Page : note (2)<br /> note (1) note (2)<br /> .--.--.--------------. .--.--.---------------.<br /> |11|10| Video Buffer | |13|12| Video Page |<br /> |--|--|--------------| |--|--|---------------|<br /> | 0| 0| 16Ko | | 0| 0| 0000 - 3FFF |<br /> |--|--|--------------| |--|--|---------------|<br /> | 0| 1| 16Ko | | 0| 1| 4000 - 7FFF |<br /> |--|--|--------------| |--|--|---------------|<br /> | 1| 0| 16Ko | | 1| 0| 8000 - BFFF |<br /> |--|--|--------------| |--|--|---------------|<br /> | 1| 1| 32Ko | | 1| 1| C000 - FFFF |<br /> '--'--'--------------' '--'--'---------------'<br /> <br /> So, it's possible to use 32KB screen size (used for [[Programming:Overscan|overscan]]) by setting bits 11 and 10 both to 1 (of Register 12). Bits MA11 and MA10 of the address generated by the CRTC are not written on the address bus to access video memory; settings both bits to 1 is the only way to cause a carry to bit MA12 when address pass over the end of current video page to change the memory address to the next video page.<br /> <br /> == CRTC Differences ==<br /> <br /> In this section I will attempt to identify all the differences between each CRTC. <br /> <br /> The following tables list the functions that can be accessed for each type: <br /> <br /> Type 0<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||-||- <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |-<br /> |}<br /> <br /> Type 1<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||Read Status Register||Read Only <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |}<br /> <br /> Type 2<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||-||- <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |-<br /> |}<br /> <br /> Type 3 and 4<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||Read from selected internal 6845 register||Read Only <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |-<br /> |}<br /> <br /> It is not possible to read from all the internal registers, this table shows the read/write status of each register for each type: <br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |rowspan=2|''Register Index''||rowspan=2|''Register Name''||colspan=4|''Type'' <br /> |-<br /> |0||1||2||3||4<br /> |-<br /> |0||Horizontal Total||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |1||Horizontal Displayed||Write Only||Write Only||Write Only||(note 2)||(note 3)<br /> |-<br /> |2||Horizontal Sync Position||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |3||Horizontal and Vertical Sync Widths||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |4||Vertical Total||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |5||Vertical Total Adjust||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |6||Vertical Displayed||Write Only||Write Only||Write Only||(note 2)||(note 3)<br /> |-<br /> |7||Vertical Sync position||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |8||Interlace and Skew||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |9||Maximum Raster Address||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |10||Cursor Start Raster||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |11||Cursor End Raster||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |12||Display Start Address (High)||Read/Write||Write Only||Write Only||Read/Write (note 2)||(note 3) <br /> |-<br /> |13||Display Start Address (Low)||Read/Write||Write Only||Write Only||Read/Write (note 2)||(note 3) <br /> |-<br /> |14||Cursor Address (High)||Read/Write||Read/Write||Read/Write||Read/Write (note 2)||(note 3)<br /> |-<br /> |15||Cursor Address (Low)||Read/Write||Read/Write||Read/Write||Read/Write (note 2)||(note 3)<br /> |-<br /> |16||Light Pen Address (High)||Read Only||Read Only||Read Only||Read Only (note 2)||(note 3)<br /> |-<br /> |17||Light Pen Address (Low)||Read Only||Read Only||Read Only||Read Only (note 2)||(note 3)<br /> |-<br /> |}<br /> <br /> '''Notes'''<br /> <br /> 1. On type 0 and 1, if a Write Only register is read from, "0" is returned. <br /> <br /> 2. See the document "Extra CPC Plus Hardware Information" for more details.<br /> <br /> 3. CRTC type 4 is the same as CRTC type 3. The registers also repeat as they do on the type 3.<br /> <br /> == Horizontal and Vertical Sync (R3) ==<br /> <br /> UM6845:<br /> <br /> Bits 7..4 define Vertical Sync Width. If 0 is programmed this gives 16 lines of VSYNC.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed no HSYNC is generated.<br /> <br /> UM6845R:<br /> <br /> Bits 7..4 are ignored. Vertical Sync is fixed at 16 lines.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed no HSYNC is generated.<br /> <br /> MC6845:<br /> <br /> Bits 7..4 are ignored. Vertical Sync is fixed at 16 lines.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed this gives a HSYNC width of 16.<br /> <br /> Pre-ASIC/ASIC:<br /> <br /> Bits 7..4 define Vertical Sync Width. If 0 is programmed this gives 16 lines of VSYNC.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed this gives a HSYNC width of 16.<br /> <br /> == UM6845R and R31 ==<br /> <br /> R31 is described in the UM6845R documentation as "Dummy Register".<br /> <br /> Its use is described in the documentation for the Rockwell R6545 in combination with R18, R19 and R8 and the Status Register.<br /> <br /> In the UM6845R it appears to have no effect. Reading and writing does nothing. Reading it returns 0x0ff.<br /> <br /> R31 doesn't exist on types 0,2,3.<br /> <br /> == UM6845R and R12/R13 ==<br /> <br /> The UM6845R differs to other CRTC in respect of R12/R13. <br /> <br /> When VCC=0, R12/R13 is re-read at the start of each line. R12/R13 can therefore be changed for each scanline when VCC=0. <br /> <br /> Just like other CRTCs when RC==(R9-1), the current MA is captured for the next char-line.<br /> <br /> In demos to make a display compatible with all CRTCs program R12/R13 when VCC!=0. This will then take effect at the next frame start.<br /> <br /> == UM6845R status register ==<br /> <br /> The UM6845R has a status register that can be read using port &BExx.<br /> <br /> Bit 6 is set to 1 if there is a strobe input to the /LPEN signal. It is cleared to 0 when either R17 or R16 (LPEN address) of the CRTC are read. It signals there is a valid LPEN input. On my CPC (arnoldemu) with UM6845R, it is triggered at power on, R17 and R16 have the values 0 when read.<br /> <br /> Bit 5 is set to 1 when CRTC is in "vertical blanking". Vertical blanking is when the vertical border is active. i.e. VCC>=R6. <br /> <br /> It is cleared when the frame is started (VCC=0). It is not directly related to the DISPTMG output (used by the CPC to display the border colour) because that output is a combination of horizontal and vertical blanking.<br /> This bit will be 0 when pixels are being displayed.<br /> <br /> All the other bits read as 0 and don't have any function.<br /> <br /> == Datasheets ==<br /> <br /> * [[Media:hd6845.hitachi.pdf|HD6845S (Hitachi) (aka type 0)]]<br /> * [[Media:Um6845.umc.pdf|UM6845 (UMC) (aka type 0)]]<br /> * [[Media:Um6845r.umc.pdf|UM6845R (UMC) (aka type 1)]]<br /> * [[Media:Mc6845.motorola.pdf|MC6845 (Motorola) (aka type 2)]]<br /> <br /> * [[VHDL implementation of the 6845]]<br /> <br /> == Clones ==<br /> * [CM607P a Bulgarian clone made in Pravetz factory]<br /> * [EF6845P by Thomson Semiconductors]<br /> <br /> <br /> == Tools about CRTC ==<br /> <br /> * [http://www.cpcwiki.eu/imgs/9/99/Elmar_Krieger-SPECIAL_EFFECTS.dsk some BASIC tools to detect CRTC types 0-1-2 and show some effects - by [[Elmar Krieger]] ] (DSK for Emulators)<br /> <br /> == Links ==<br /> <br /> * [http://en.wikipedia.org/wiki/6845 Wikipedia on the CRTC]<br /> * [http://www.grimware.org/doku.php/documentations/devices/crtc CRTCs on grimware]<br /> <br /> ==Related pages==<br /> <br /> *[[Gate Array]]<br /> <br /> *[[ASIC]]<br /> <br /> *[[Video modes]]<br /> <br /> *[[Synchronising with the CRTC and display]] : technic and details on the relationship between Gate Array and CRTC.<br /> <br /> [[Category:Hardware]] [[Category:CPC Internal Components]] [[Category:Programming]] [[Category:Datasheet]] [[Category:Graphic]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=CRTC&diff=102540 CRTC 2018-12-29T01:25:15Z

<p>DavidL: /* The 6845 Registers */ R12 is set to 0x30 (48) : MA13=1 MA12=1 => A15=1 A14=1 to start video at address 0xC000</p> <hr /> <div>* ''This is an article about the "Cathode Ray Tube Controller" hardware unit of the Amstrad CPC. For the cpc scene member see [[ChaRleyTroniC]]''<br /> <br /> <br /> The '''CRTC''' (Cathode Ray Tube Controller) helps to generate the video signal of the Amstrad CPC.<br /> <br /> NOTE: This document describes the functionality in terms of the CPC with its separate CRTC and Gate-Array. The Plus has both integrated into the same IC, but could be considered to have two functional blocks, one for CRTC and one for Gate-Array. In this document the term 'Gate-Array' is used, but this also applies to the ASIC.<br /> <br /> == Overview ==<br /> <br /> The 6845 Cathode Ray Tube Controller (CRTC) is a programmable IC used to generate video displays. This IC is used in a variety of computers including the Amstrad CPC, Amstrad CPC+ and KC Compact. <br /> <br /> The CRTC was a common part available from many different manufacturers. During the life of the CPC, Amstrad sourced the CRTC from various manufacturers. <br /> <br /> All ICs used were based on the same design but have a different implementation. As a result they do not operate identically in all situations. This document highlights these differences. <br /> <br /> This table lists the known ICs used, with their part number, manufacturer and type number. <br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''Part number''||''Manufacturer''||''Type number (note 3)''<br /> |-<br /> |HD6845S||Hitachi||0<br /> |-<br /> |UM6845||UMC||0<br /> |-<br /> |UM6845R||UMC||1<br /> |-<br /> |MC6845||Motorola||2<br /> |-<br /> |AMS40489||Amstrad||3 (note 1)<br /> |-<br /> |40226||Amstrad||4 (note 2)<br /> |}<br /> <br /> '''NOTES''' <br /> <br /> 1. The CRTC functionality is integrated into the CPC+ ASIC. This type exists only in the CPC464+,CPC6128+ and GX4000. <br /> <br /> 2. This type exists in "cost-down" CPC464 and CPC6128 systems. In the "cost-down" the CRTC functionality is integrated into a single ASIC IC. This ASIC is often refered to as the "Pre-ASIC" because it preceeded the CPC+ ASIC. The CRTC functionality of the Pre-ASIC is almost identical to the CRTC within the ASIC.<br /> <br /> 3. In the Amstrad community each 6845 implementation has been assigned a type number. This type identifies a group of implementations which operate in exactly the same way. <br /> <br /> As far as I know, the type number system was originally used by demo programmers. <br /> <br /> It is possible to detect the 6845 present using software methods, and this is done to: <br /> <br /> * warn that the software was not designed for the detected 6845 and may function incorrectly, <br /> * to adapt the software so that it will run with the detected 6845 <br /> * In most cases, the type of the detected 6845 is reported. <br /> <br /> 4. As far as I know, the KC compact used HD6845R only.<br /> <br /> == Timings and relating with Z80 instructions count ==<br /> <br /> Some informations like : how many Z80 instructions can I fit within a scan line ? Within a screen ? Etc... See http://www.cpcwiki.eu/forum/programming/frame-flyback-and-interrupts/msg25106/#msg25106<br /> (To be extracted/edited to conform to wiki good practices).<br /> <br /> ==Programming==<br /> <br /> The 6845 is selected when bit 14 of the I/O port address is set to "0". Bit 9 and 8 of the I/O port address define the function to access. The remaining bits can be any value, but it is adviseable to set these to "1" to avoid conflict with other devices in the system.<br /> <br /> The recommended I/O port addresses are<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''I/O port address''||''Function''||''Read/Write''<br /> |-<br /> |&BCxx||Select 6845 register||Write only<br /> |-<br /> |&BDxx||Write 6845 register data||Write only<br /> |-<br /> |&BExx||(note 1)||Read only<br /> |-<br /> |&BFxx||(note 1)||Read only<br /> |-<br /> |}<br /> <br /> '''NOTE'''<br /> <br /> 1. The function of these I/O ports is dependant on the CRTC type<br /> <br /> 2. If you perform an IN instruction to the select or write functions it will write data to the CRTC from the current data on the bus.<br /> <br /> ==Addressing==<br /> <br /> The following table defines the generated memory address from the CRTC and Gate-Array signals. <br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''Memory Address Signal''||''Signal source''||''Signal name''<br /> |-<br /> |A15||6845||MA13 <br /> |-<br /> |A14||6845||MA12<br /> |-<br /> |A13||6845||RA2 <br /> |-<br /> |A12||6845||RA1 <br /> |-<br /> |A11||6845||RA0 <br /> |-<br /> |A10||6845||MA9 <br /> |-<br /> |A9||6845||MA8 <br /> |-<br /> |A8||6845||MA7 <br /> |-<br /> |A7||6845||MA6 <br /> |-<br /> |A6||6845||MA5 <br /> |-<br /> |A5||6845||MA4 <br /> |-<br /> |A4||6845||MA3 <br /> |-<br /> |A3||6845||MA2 <br /> |-<br /> |A2||6845||MA1 <br /> |-<br /> |A1||6845||MA0<br /> |-<br /> |A0||Gate-Array||CCLK<br /> |-<br /> |}<br /> <br /> CRTC generates the address, Gate-Array reads the data and converts it to pixels based on the current mode.<br /> <br /> == DISPTMG ==<br /> <br /> DISPTMG signal defines the border. When DISPTMG is "1" the border colour is output by the Gate-Array to the display. The DISPTMG can be forced using R8 (DISPTMG Skew) on type 0,3 and 4 or by setting R6=0 on type 1. It is not possible to force the DISPTMG on type 2 or 5.<br /> <br /> The border has higher priority than pixels but lower priority than the black colour output when HSYNC/VSYNC are active.<br /> <br /> == HSYNC and VSYNC ==<br /> <br /> On CPC, HSYNC and VSYNC from the CRTC are passed into the Gate-Array.<br /> <br /> When HSYNC is active Gate-Array outputs the palette colour black. If the HSYNC is set to 14 characters then black will be output for 14us.<br /> <br /> The HSYNC is modified before being sent to the monitor. It happens 2us after the HSYNC from the CRTC and lasts 4us when HSYNC length is greater or equal to 6. <br /> <br /> If R2=46, and HSYNC width is 14 then monitor hsync starts at 48 and lasts until 51.<br /> <br /> On a CPC monitor, the HSYNC is rendered in "absolute black". It is darker than the black output by the Gate-Array.<br /> <br /> The VSYNC is also modified before being sent to the monitor. It happens two lines* after the VSYNC from the CRTC and stay two lines (same cut rule if VSYNC is lower than 4). PAL (50Hz) does need two lines VSYNC_width, and 4us HSYNC_width.<br /> <br /> Using CRTC1, VSYNC width value 0 means a value of 16.<br /> <br /> == The 6845 Registers ==<br /> <br /> The Internal registers of the 6845 are:<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''Register Index''||''Register Name''||''Range''||''CPC Setting''||''Notes''<br /> |-<br /> |0||Horizontal Total||00000000||63||Width of the screen, in characters. Should always be 63 (64 characters). 1 character == 1μs.<br /> |-<br /> |1||Horizontal Displayed||00000000||40||Number of characters displayed. Once horizontal character count (HCC) matches this value, DISPTMG is set to 1.<br /> |-<br /> |2||Horizontal Sync Position||00000000||46||When to start the HSync signal.<br /> |-<br /> |3||Horizontal and Vertical Sync Widths||VVVVHHHH||128+14||HSync pulse width in characters (0 means 16 on some CRTC), should always be more than 8; VSync width in scan-lines. (0 means 16 on some CRTC. Not present on all CRTCs, fixed to 16 lines on these)<br /> |-<br /> |4||Vertical Total||x0000000||38||Height of the screen, in characters.<br /> |-<br /> |5||Vertical Total Adjust||xxx00000||0||Measured in scanlines, can be used for smooth vertical scrolling on CPC.<br /> |-<br /> |6||Vertical Displayed||x0000000||25||Height of displayed screen in characters. Once vertical character count (VCC) matches this value, DISPTMG is set to 1.<br /> |-<br /> |7||Vertical Sync position||x0000000||30||When to start the VSync signal, in characters.<br /> |-<br /> |8||Interlace and Skew||xxxxxx00||0||00: No interlace; 01: Interlace Sync Raster Scan Mode; 10: No Interlace; 11: Interlace Sync and Video Raster Scan Mode<br /> |-<br /> |9||Maximum Raster Address||xxx00000||7||Maximum scan line address on CPC can hold between 0 and 7, higher values' upper bits are ignored<br /> |-<br /> |10||Cursor Start Raster||xBP00000||0||Cursor not used on CPC. B = Blink On/Off; P = Blink Period Control (Slow/Fast). Sets first raster row of character that cursor is on to invert.<br /> |-<br /> |11||Cursor End Raster||xxx00000||0||Sets last raster row of character that cursor is on to invert<br /> |-<br /> |12||Display Start Address (High)||xx000000||48<br /> |-<br /> |13||Display Start Address (Low)||00000000||0||Allows you to offset the start of screen memory for hardware scrolling, and if using memory from address &0000 with the firmware.<br /> |-<br /> |14||Cursor Address (High)||xx000000||0<br /> |-<br /> |15||Cursor Address (Low)||00000000||0<br /> |-<br /> |16||Light Pen Address (High)||xx000000||||Read Only<br /> |-<br /> |17||Light Pen Address (Low)||00000000||||Read Only<br /> |-<br /> |}<br /> <br /> registers 18-31 read as 0, on type 0 and 2.<br /> registers 18-30 read as 0 on type1, register 31 reads as 0x0ff.<br /> <br /> Details about Reg. 12 and Reg. 13 specifically:<br /> <br /> .------- REG 12 --------. .------- REG 13 --------.<br /> | | | |<br /> 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00<br /> .--.--.--.--.--.--.--.--. .--.--.--.--.--.--.--.--.<br /> |X |X | | | | | | | | | | | | | | | |<br /> '--'--'--'--'--'--'--'--' '--'--'--'--'--'--'--'--'<br /> '--.--'--.--'---------------.-----------------'<br /> | | |<br /> | | '------> Offset for setting<br /> | | videoram <br /> | | (1024 positions)<br /> | | Bits 0..9<br /> | |<br /> | '-------------------------> Video Buffer : note (1)<br /> |<br /> '-------------------------------> Video Page : note (2)<br /> note (1) note (2)<br /> .--.--.--------------. .--.--.---------------.<br /> |11|10| Video Buffer | |13|12| Video Page |<br /> |--|--|--------------| |--|--|---------------|<br /> | 0| 0| 16Ko | | 0| 0| 0000 - 3FFF |<br /> |--|--|--------------| |--|--|---------------|<br /> | 0| 1| 16Ko | | 0| 1| 4000 - 7FFF |<br /> |--|--|--------------| |--|--|---------------|<br /> | 1| 0| 16Ko | | 1| 0| 8000 - BFFF |<br /> |--|--|--------------| |--|--|---------------|<br /> | 1| 1| 32Ko | | 1| 1| C000 - FFFF |<br /> '--'--'--------------' '--'--'---------------'<br /> <br /> So, it's possible to use 32KB screen size (used for [[Programming:Overscan|overscan]]) by setting bits 11 and 10 both to 1 (of Register 12).<br /> <br /> == CRTC Differences ==<br /> <br /> In this section I will attempt to identify all the differences between each CRTC. <br /> <br /> The following tables list the functions that can be accessed for each type: <br /> <br /> Type 0<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||-||- <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |-<br /> |}<br /> <br /> Type 1<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||Read Status Register||Read Only <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |}<br /> <br /> Type 2<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||-||- <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |-<br /> |}<br /> <br /> Type 3 and 4<br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |''b1''||''b0''||''Function''||''Read/Write'' <br /> |-<br /> |0||0||Select internal 6845 register||Write Only <br /> |-<br /> |0||1||Write to selected internal 6845 register||Write Only <br /> |-<br /> |1||0||Read from selected internal 6845 register||Read Only <br /> |-<br /> |1||1||Read from selected internal 6845 register||Read only <br /> |-<br /> |}<br /> <br /> It is not possible to read from all the internal registers, this table shows the read/write status of each register for each type: <br /> <br /> {|{{Prettytable|width: 700px; font-size: 2em;}}<br /> |rowspan=2|''Register Index''||rowspan=2|''Register Name''||colspan=4|''Type'' <br /> |-<br /> |0||1||2||3||4<br /> |-<br /> |0||Horizontal Total||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |1||Horizontal Displayed||Write Only||Write Only||Write Only||(note 2)||(note 3)<br /> |-<br /> |2||Horizontal Sync Position||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |3||Horizontal and Vertical Sync Widths||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |4||Vertical Total||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |5||Vertical Total Adjust||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |6||Vertical Displayed||Write Only||Write Only||Write Only||(note 2)||(note 3)<br /> |-<br /> |7||Vertical Sync position||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |8||Interlace and Skew||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |9||Maximum Raster Address||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |10||Cursor Start Raster||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |11||Cursor End Raster||Write Only||Write Only||Write Only||(note 2)||(note 3) <br /> |-<br /> |12||Display Start Address (High)||Read/Write||Write Only||Write Only||Read/Write (note 2)||(note 3) <br /> |-<br /> |13||Display Start Address (Low)||Read/Write||Write Only||Write Only||Read/Write (note 2)||(note 3) <br /> |-<br /> |14||Cursor Address (High)||Read/Write||Read/Write||Read/Write||Read/Write (note 2)||(note 3)<br /> |-<br /> |15||Cursor Address (Low)||Read/Write||Read/Write||Read/Write||Read/Write (note 2)||(note 3)<br /> |-<br /> |16||Light Pen Address (High)||Read Only||Read Only||Read Only||Read Only (note 2)||(note 3)<br /> |-<br /> |17||Light Pen Address (Low)||Read Only||Read Only||Read Only||Read Only (note 2)||(note 3)<br /> |-<br /> |}<br /> <br /> '''Notes'''<br /> <br /> 1. On type 0 and 1, if a Write Only register is read from, "0" is returned. <br /> <br /> 2. See the document "Extra CPC Plus Hardware Information" for more details.<br /> <br /> 3. CRTC type 4 is the same as CRTC type 3. The registers also repeat as they do on the type 3.<br /> <br /> == Horizontal and Vertical Sync (R3) ==<br /> <br /> UM6845:<br /> <br /> Bits 7..4 define Vertical Sync Width. If 0 is programmed this gives 16 lines of VSYNC.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed no HSYNC is generated.<br /> <br /> UM6845R:<br /> <br /> Bits 7..4 are ignored. Vertical Sync is fixed at 16 lines.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed no HSYNC is generated.<br /> <br /> MC6845:<br /> <br /> Bits 7..4 are ignored. Vertical Sync is fixed at 16 lines.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed this gives a HSYNC width of 16.<br /> <br /> Pre-ASIC/ASIC:<br /> <br /> Bits 7..4 define Vertical Sync Width. If 0 is programmed this gives 16 lines of VSYNC.<br /> Bits 3..0 define Horizontal Sync Width. If 0 is programmed this gives a HSYNC width of 16.<br /> <br /> == UM6845R and R31 ==<br /> <br /> R31 is described in the UM6845R documentation as "Dummy Register".<br /> <br /> Its use is described in the documentation for the Rockwell R6545 in combination with R18, R19 and R8 and the Status Register.<br /> <br /> In the UM6845R it appears to have no effect. Reading and writing does nothing. Reading it returns 0x0ff.<br /> <br /> R31 doesn't exist on types 0,2,3.<br /> <br /> == UM6845R and R12/R13 ==<br /> <br /> The UM6845R differs to other CRTC in respect of R12/R13. <br /> <br /> When VCC=0, R12/R13 is re-read at the start of each line. R12/R13 can therefore be changed for each scanline when VCC=0. <br /> <br /> Just like other CRTCs when RC==(R9-1), the current MA is captured for the next char-line.<br /> <br /> In demos to make a display compatible with all CRTCs program R12/R13 when VCC!=0. This will then take effect at the next frame start.<br /> <br /> == UM6845R status register ==<br /> <br /> The UM6845R has a status register that can be read using port &BExx.<br /> <br /> Bit 6 is set to 1 if there is a strobe input to the /LPEN signal. It is cleared to 0 when either R17 or R16 (LPEN address) of the CRTC are read. It signals there is a valid LPEN input. On my CPC (arnoldemu) with UM6845R, it is triggered at power on, R17 and R16 have the values 0 when read.<br /> <br /> Bit 5 is set to 1 when CRTC is in "vertical blanking". Vertical blanking is when the vertical border is active. i.e. VCC>=R6. <br /> <br /> It is cleared when the frame is started (VCC=0). It is not directly related to the DISPTMG output (used by the CPC to display the border colour) because that output is a combination of horizontal and vertical blanking.<br /> This bit will be 0 when pixels are being displayed.<br /> <br /> All the other bits read as 0 and don't have any function.<br /> <br /> == Datasheets ==<br /> <br /> * [[Media:hd6845.hitachi.pdf|HD6845S (Hitachi) (aka type 0)]]<br /> * [[Media:Um6845.umc.pdf|UM6845 (UMC) (aka type 0)]]<br /> * [[Media:Um6845r.umc.pdf|UM6845R (UMC) (aka type 1)]]<br /> * [[Media:Mc6845.motorola.pdf|MC6845 (Motorola) (aka type 2)]]<br /> <br /> * [[VHDL implementation of the 6845]]<br /> <br /> == Clones ==<br /> * [CM607P a Bulgarian clone made in Pravetz factory]<br /> * [EF6845P by Thomson Semiconductors]<br /> <br /> <br /> == Tools about CRTC ==<br /> <br /> * [http://www.cpcwiki.eu/imgs/9/99/Elmar_Krieger-SPECIAL_EFFECTS.dsk some BASIC tools to detect CRTC types 0-1-2 and show some effects - by [[Elmar Krieger]] ] (DSK for Emulators)<br /> <br /> == Links ==<br /> <br /> * [http://en.wikipedia.org/wiki/6845 Wikipedia on the CRTC]<br /> * [http://www.grimware.org/doku.php/documentations/devices/crtc CRTCs on grimware]<br /> <br /> ==Related pages==<br /> <br /> *[[Gate Array]]<br /> <br /> *[[ASIC]]<br /> <br /> *[[Video modes]]<br /> <br /> *[[Synchronising with the CRTC and display]] : technic and details on the relationship between Gate Array and CRTC.<br /> <br /> [[Category:Hardware]] [[Category:CPC Internal Components]] [[Category:Programming]] [[Category:Datasheet]] [[Category:Graphic]]</div>

DavidL https://oldwiki.cpcwiki.eu/index.php?title=User:DavidL&diff=102425 User:DavidL 2018-12-09T18:13:08Z

<p>DavidL: Création</p> <hr /> <div>Hi.<br /> <br /> I'm a French software development engineer with several years experience.<br /> <br /> I'm currently developing a generic machine emulator, which currently successfully runs a complete Amstrad PC1512. I didn't find any software that could not run on the emulated machine unless it would not run on the original machine.<br /> I started creating components to emulate the CPC464. This site is a good source for documentation.<br /> <br /> [[User:DavidL|DavidL]] ([[User talk:DavidL|talk]])</div>

DavidL