Started by AMSDOS, 13:50, 01 August 14
0 Members and 1 Guest are viewing this topic.
Quote from: Bryce on 14:31, 01 August 14The device just has RAM ICs and some logic to map the RAM and buffer the bank selection. Adding RAM doesn't occupy ROM space normally. Here's a picture of what's inside 64K Version: http://www.cpcwiki.eu/index.php/File:DK64_Before.jpg and the 256K version: http://www.cpcwiki.eu/index.php/File:DK64_After.jpgBryce.
Quote from: arnoldemu on 20:13, 04 August 14- Bryce is correct that connecting a 64kb ram to a 6128 is pointless.
Readyout &7f00,&c0 ' page-out all extra RAM, just to be surepoke &4000,51 ' write a marker tag in the base 64K RAMout &7f00,&CC ' page-in page 1/bank 0poke &4000,42 ' write a marker tag in page 1/bank 0out &7f00,&c0 ' page-out all extra RAM? peek(&4000)51 ' base RAM was not modifiedout &7f00,&c4 ' page-in page 0/bank 0? peek(&4000)42 ' Uh! Oh!
Quote from: arnoldemu on 20:13, 04 August 14- few emulators seem to allow you to choose a basic 464 configuration without ram.
Quote from: Bryce on 23:40, 04 August 14I was referring to DK expansions, which were all made to start at bank 0. Obviously if you made your own 64K expansion for a 6128 you'd make it bank 1 (unless you are mad of course). Bryce.
Quote from: AMSDOS on 10:35, 06 August 14Can I use a Silicon Disk as an ordinary Memory Expansion unit or are they configured differently?
Quote from: arnoldemu on 10:49, 06 August 14If you have a 464 and connect a silicon disk, I expect most software will not find it.It can be used as ram, but it's not in the same ram "slots" the software is looking for.
Quote from: CraigsBar on 10:52, 06 August 14Amstrad Action rana hardware mod that added a switch to either a memory expansion or silicon disk so the result would function as either.Craig
Quote from: AMSDOS on 11:24, 06 August 14Yes I noticed that in AA46, but I'm assuming it's not possible to patch the ROM file to behave in that manner though an emulator.
Quote from: arnoldemu on 10:49, 06 August 14If you have a 464 and connect a silicon disk, I expect most software will not find it.It can be used as ram, but it's not in the same ram "slots" the software is looking for.The normal extra 64k of ram is access through ram configurations c4,c5,c6,c7.This is the normal 64k ram and the extra 64k in the 6128.But the silicon disk sits at something like cc,cd,ce,cf. If the software uses c4,c5,c6,c7 it will probably not detect it and use it.
Quote from: Bryce on 13:53, 08 August 14Yes, but on a 464 you would then have the base 64K, plus 256K (64K per bank) in banks 4 to 7. On a 6128 you would have the base 64K, 64K in bank 0 (the additional internal RAM) and 256K (64K per bank) in banks 4 to 7.Confusing, but it would work. Software that checks all banks for RAM should find it unless they are programmed to stop looking as soon as they find a non-populated bank.Bryce.
Page created in 0.202 seconds with 48 queries.