Re: A look at the C-One (Commodore One) reconfigurable computer

[MagerValp <MagerValp@cling.gu.se>]

>>>>> "P" == Prodatron / SymbiosiS <mika@falkag.com> writes:

P> Hm, I don't know. I just have some values like this: Data transfer
P> to/from the IDE-Interface: CPC: 162KB/s, C64: 60KB/s Floppy speed:
P> CPC: 20KB/s, I don't know the speed on C64, but I heard something
P> about 9KB/s, when you use tricks.

Yes, the C64's disk interface is crippled, due to management insisting
on backwards compatibility with the VIC-20 :/

P> CPC was also able to do HW scrolling, but not many games used it.

Well, it can move the base of the bitmap screen, which shifts the
screen by 2 pixels at a time (if you're using 160x200), but can it do
single pixel scrolling?

P> The video addressing was a little bit complicated, but you are
P> still able to do very fast screen output on CPC when you know how,
P> so that doesn't cost any performance at the end.

Sure, just like the C64 can overcome the bitmap addressing using
tables, but the complete lack of a character/tile based video modes is
a huge drawback for action games. The CPC has to set 16000 bytes to
redraw the whole screen, which is a lot more than the C64's 2000.

P> And as a spoiled Z80 programmer I am in a shock, when I see 6502
P> assembler ;-) It's a little bit different, if you have 3x8Bit
P> Registers at all (6502) to work with, or 18x8Bit Registers (Z80),
P> from which you can use 16 as 8x16Bit Registers. Ok, the Z80 doesn't
P> have a zeropage.

Yes, the zeropage makes all the difference. The 6502 is minimalistic,
but quite comfortable to work with once you get used to it.

-- 
    ___          .     .  .         .       . +  .         .      o   
  _|___|_   +   .  +     .     +         .  Per Olofsson, arkadspelare
    o-o    .      .     .   o         +          MagerValp@cling.gu.se
     -       +            +    .     http://www.cling.gu.se/~cl3polof/