Recent posts

#21

Technical support - Hardware related / Re: cable DDI-1 for CPC 6128

Last post by Bryce - Yesterday at 18:29

https://www.cpcwiki.eu/index.php/File:Floppy_Cable.png

Bryce.

#22

Technical support - Hardware related / cable DDI-1 for CPC 6128

Last post by willow3411 - Yesterday at 18:02

Hello everyone,
So here I am going to try to be clear in my explanations.
I have a Schneider DDI-1 (external reader) with its Amsdos interface for my CPC 464. Everything works perfectly.
I would like to make a cable that directly connects my DDI-1 to my CPC 6128 (EDGE port).
Just by replacing the AMSDOS interface.
of course I would like to keep my internal 3" drive in A and the external one in B
I have the 34p cable, the 34p female connector and the EDGE connector.
The problem is that I don't know the exact pinout. I read a little bit of everything.
If anyone has a diagram that would be great.
Thanks for reading me.
Willow3411

#23

Amstrad CPC hardware / Re: Zilog Z84C0020PEG in my CP...

Last post by Prodatron - Yesterday at 16:23

OUT (C),0 is used in all optimized AY routines, so yes, that makes sense with the corrupted sound.

#24

Programming / Re: bits 5 and 3 of F register...

Last post by roudoudou - Yesterday at 15:14

iterating or not with LDI or LDIR, you keep S, Z and C
then you set P when BC will be zeroed
about the non documented behaviour, it's something like this

(((databusValue+A) & 2)<<4) | ((databusValue+A) & FLAG_3_BIT);

#25

Amstrad CPC hardware / Re: Zilog Z84C0020PEG in my CP...

Last post by roudoudou - Yesterday at 14:55

most of problems are due to (i guess) OUT (C),0 undocumented opcode which was fixed (or reassigned) in later versions

#26

Amstrad CPC hardware / Re: Zilog Z84C0020PEG in my CP...

Last post by Prodatron - Yesterday at 13:04

Thanks for reporting!
Very interesting, I would like to hear about more testings.
I wonder if the issues with BG-stuff are undocumented instructions or timing.
(btw I really like your Basic hacks!)

#27

Programming / Re: bits 5 and 3 of F register...

Last post by Fran123 - Yesterday at 12:57

Is there any reason why you should know about these undocumented bits in the F-register beside to develop a 100% correct Z80 emulator?
I never understood why this was necessary to know. Does it have any advantages for making code better/faster/shorter? Does anyone have an example for this? Or is this just for fun (which includes detecting, if a Z80 emu is cool or not).

I trying to emulate the z80, I'm not planning to make another RVM either

#28

Programming / Re: triple buffering

Last post by ervin - Yesterday at 10:44

Sounds like a good scheme.
Thanks!

#29

A

General Discussion - Introductions / Re: Interview with Dave Rogers

Last post by Anthony Flack - Yesterday at 10:13

While most people remember his music, for me it will always be The Scout Steps Out and especially Radzone. I love that game. 

#30

A

Programming / Re: triple buffering

Last post by Anthony Flack - Yesterday at 09:58

If you want to do something along these lines, the memory arrangement I used:

Main code goes in bank 0.

Front/back buffers are in bank 2 and 3 at &8000 and &c000.

Clean buffer, compiled sprites, and any other code all swap in to bank 1 at &4000, so that you can copy from any of these banks into either screen buffer.