can't wait to get my hands on mine... the 1st may in "hand-clean" ?May be...
Can't wait to get mine :)May be, if someone start it... Because I'm not "wiki friendly".
Any chance for a Wiki article?
Does it helps for existing games? Like Black land or defender of the crown?It help for all games/programs that need more than 64K RAM on 464/664. (and ROM games released on 2013 contest)
Dilemma! Do I even bother with my MegaROM now? I guess I may as well still...
Tell me about it - I spent ages redesigning a new MegaFlash board I could produce and up pops this one with a ram expansion too! TotO's definitely got a great sense of timing :D
The main advantage is to allow to handle all the PAL modes (RMR) over the 512K of memory (C0-FF).
[...]
The X-MEM push all CPC to the same level of compatibility.
Ram disc support in SymbOS: Ok, makes sense, if you only have floppy discs available (which is not the case for most MSX configs and my CPC config).Should be nice. :)
I will think about a possibility to add this...
Btw, I wonder if mode #C1, #C2 and #C3 work on the 464 as well?? I thought especially #C3 would be impossible on the 464 (and 664)?I'm using 64K CPC for testings and that work fine. The DK'Tronics RAM expansions does it using transistors in 80's.
Should be nice. :)Still wonder, why you would need a ram disc, as you can load all applications at the same time and don't need to quit them again ;D
I'm using 64K CPC for testings and that work fine. The DK'Tronics RAM expansions does it using transistors in 80's.Did you try SymbOS with your expansion on a 464? It doesn't use #c3, only #c1,#c2 and #c4-#c7. But I was sure, that it doesn't work on a 464... :o
Only one problem caused by the GA :
6128 &4000 access with active ROM in C3 mode = RAM in &C000
464/664 &4000 access with active ROM in C3 mode = ROM in &4000
But, if your are not in this configuration all work fine.
No problem with CP/M without patch, Pacman or Phortem double buffering.
The memory should be used as a RAM Drive C and can be shared with CP/M. (here boot from FW3.13 and CP/M ROM)
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
Did you try SymbOS with your expansion on a 464? It doesn't use #c3, only #c1,#c2 and #c4-#c7. But I was sure, that it doesn't work on a 464... :oYes c3 does work on 464 but to be 100% you need to have upper rom disabled if you want to read/write &4000-&7fff.
Still wonder, why you would need a ram disc, as you can load all applications at the same time and don't need to quit them again.To unpack from ROM the system files and set C: as default drive on 464 w/o floppy?
Did you try SymbOS with your expansion on a 464?Haha. ;D
It doesn't use #c3, only #c1,#c2 and #c4-#c7. But I was sure, that it doesn't work on a 464... :o
Is there a ROM image of FW3.13 around somewhere?Please, wait the X-MEM release. Need more work actually. :)
Please, wait the X-MEM release. Need more work actually. :)
The RAD (RAm Disc) start from an extra ROM actually, because not sure to fit inside.
TFM will said: "so FutureOS pointer will not work" ... And it's true. (tested yesterday)
Hey Stefan! Time to make it a great command line OS only!!! ;D
btw.: Command line is exactly what I never wanted (take CP/M+ ;) ).
Isn't that what QCMD does?
With its great performances and hardware support, a command line version of FutureOS will be the best alternative of CP/M and *NIX for the CPC.For command line we already have SymbOS, it's performance is great and like I remember it's kind of command line it great. Others do know much more about it than me.
Its GUI should be a layer over it to not force peoples to use a mouse than nobody own.
The command line system should be based on BSD.
With the X-MEM, it may be more interesting as more peoples will be able to use it.
Thank's to TotO we know pretty precisely how the X-MEM works. Now let me ask a question: Which kind of software is Syx working on? Or is it secret?SyX do a great work on the FW3.x !
How to switch on and off a ROM for write access?Not needed, it's automatic. The switch is only used to force hard protection against paranoia. ;D
Not needed, it's automatic. The switch is only used to force hard protection against paranoia. ;D
Dilemma! Do I even bother with my MegaROM now? I guess I may as well still...
Yes. I got that. So how does that automatic work? Which Flash do you use? The same as in the FlashGordon, so you have to unprotect the Flash for every write cycle? But this is not in agreement with the 256 bytes page written by SyX program.
The ROM logic is handled by the CPLD as the same way as the "CTC-AY" cartridges, not like the Megaflash or the FlashGordon.
The X-MEM use a Winbond W29C040 in DIP package. (not compatible with FlashGordon but MegaFlash)
Because I have tried W29C020 too, it's why the SyX programs support 128 and 256 bytes pages values.
So, peoples using a MegaFlash + Lower-ROM stay compatible.
Does futur game will use x-Mem?any 464 or (rarer) 664 user may be interested just for the extra RAM so they get the 128k productions.
So I was wondering as I have a 464 + DDI is there someway I can still use both this and the DDI? or do I have to wait for Bryce to develop a DDI-2 which has a passthrough so that other devices can be attatched after the DDI?The cable for the X-MEM could have an extra connector added like the serial interface (http://www.cpcwiki.eu/index.php/File:Amstrad_RS232C_Top_FR.jpg (http://www.cpcwiki.eu/index.php/File:Amstrad_RS232C_Top_FR.jpg)), you could plug your DDI-1 in there. Though finding a reversiboard (as maplin used to call them) may be difficult.
So I was wondering as I have a 464 + DDI is there someway I can still use both this and the DDI? or do I have to wait for Bryce to develop a DDI-2 which has a passthrough so that other devices can be attatched after the DDI?You can also try this:
Has anyone ever had a batch of reversiboards made up recently?
It can be inserted in an IDC connector added on a 50-way ribbon cable, to reproduce the edge connector on the cpc. With just straight through tracks, the signals end up on the wrong side.
Well, I can only strongly suggest to move to 50 pin Centronics connectors like German CPCs had, and later on the 6128 Plus too.not everyone would be willing to modify a collector machine...
However, it would be better to include the OS on the FDC PCB so that it doesn't depend on other expansions to work.Well, a 464 would need both Extra RAM and FDC/Disk to be suitable to my taste...
not everyone would be willing to modify a collector machine...Not the machine. :) But anything "after" it :) .
A little update... ;D
X-MEM preorders (updated) - Cent Pour Cent (http://www.centpourcent.net/4/post/2014/05/x-mem-preorders.html)
On the firsts... Your board is ready. :p
How cool is that! :) Does it have my name on it?I can try to engrave it, but that should cut some tracks... :laugh:
I can try to engrave it, but that should cut some tracks... :laugh:
and fight against Tipiaks:D
Btw, because someone asked me my opinion on the Gigabyte I mentioned above: no, I didn't buy one; it was just the most expensive model I found within ten seconds of looking online :D
Damn, now I want that!
(wtf?? A decimal off??)
@Bryce (http://www.cpcwiki.eu/forum/index.php?action=profile;u=225), Is that the average retail price for that board or is it the inflated ebay price.
"C'est un chip développé par notre ami ToTo"i corrected, sorry^^ thank you Gryzor
BUT IT'S NOT A CHIP!!! It's got tracks and all!
can I call you 0+0 ? ;D
Thank you for the news! :)
Sorry, but my nick-name is TotO and not ToTo.
And about the "homebrew" news, it's not iXian but iXien. (from the "iXian factory")
Abtin a répondu sur Boostez votre Amstrad CPC grâce au X-MEM. [...] Merci.
I'm curious about the 512KB ROM limit that has been chosen for the X-MEM.
As you know, the Amstrad CPC can handle 4MB ROM, and the Amstrad Plus can handle 2MB ROM.
So, is it because it would have been much more costly to use 2MB (or 4MB) ROM expansion for the X-MEM?
Or is it because "512KB ROM should be enough for anyone" ©Bill Gates? :)
Than mean, around 70 CPC will run in the next months with 512K ROM and 512K RAM!!!That's great indeed! :)
It's amazing, because that means a new users base should run tools and games using this extra power is definitively viable.
30 years after the CPC was born, we should considerate to be enough to start a new life. :)
In Brazil, arrived=lost in timeYes, the package remains in Curitiba, the brazillian equivalent to the Bermude Triangle for postal service :'(
I'm curious about the 512KB ROM limit that has been chosen for the X-MEM.
As you know, the Amstrad CPC can handle 4MB ROM, and the Amstrad Plus can handle 2MB ROM.
What would be the use case of 2MB of ROM ?At least there is someone (Yarek) that felt this was important enough to actually make real hardware to use all the 4MB ROM address space:
I don't quite understand the use of ROM here. Does this mean we can upload our own ROMS (for example PARADOS) from the CPC?
I have a standard 464 with Piotr's DDI-1 clone on order. I'm thinking the DDI-1, X4 and X-Mem would be an ideal combination; assuming I can solve the lack of passthrough on both the X4 and DDI-1.
TFM? Is that you? Damn, the forum database must be broken.
But, on the other hand, the standard RAM mechanism tailored by Amstrad gives space for only 512KB(+64KB)!
So what TFM preach is to use non standard RAM extensions that goes beyond that limitation.
And that's bad I think, because RAM devices that goes beyond 512KB are frankly alien to the Amstrad CPC/Plus DNA.
So really, the point I'm making here is far different than the usual TFM rant ;)
CraigsBar: I figured Parados was an additional ROM; I didn't realise it was a replacement ROM for AMSDOS. If you do have a spare, that would be very kind of you.
new memory expansion for ALL CPCSince some people have ordered this for a Plus, do I correctly understand X-MEM works on both the CPC6128 and the CPC6128plus?
[...]
The main advantage is to allow to customize the boot by replacing the Lower/Upper ROM 0 for a full softwares compatibility.
Exemple:
- 464 with switch to BASIC 1.1 and FW3.0
- 6128 with switch to BASIC 1.0 and FW 1.0
- 6128 with switch to BASIC 1.1 and FW3.x
The RAM part is compatible with Amstrad / DK'Tronics / Dobbertin expansions.
The main advantage is to allow to handle all the PAL modes (RMR) over the 512K of memory (C0-FF).
The memory should be used as a RAM Drive C and can be shared with CP/M. (here boot from FW3.13 and CP/M ROM)
[...]
The X-MEM push all CPC to the same level of compatibility.
I recall from MegaFlash Progress (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/megaflash-progress/msg26658/#msg26658) that ROMDIS 7 wasn't considered possible on (at least some of) the "classic" CPCs (any replacement DOS without hardware mod had to use a lower and potentially incompatible ROM number),No, it's not possible to replace ROM 7 without a hardware mod, because those CPCs not disable this rom when the ROMDIS pin is enabled, it's an Amstrad bug.
I recall from MegaFlash Progress (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/megaflash-progress/msg26658/#msg26658) that ROMDIS 7 wasn't considered possible on (at least some of) the "classic" CPCs (any replacement DOS without hardware mod had to use a lower and potentially incompatible ROM number),So unlike we assumed in the thread linked above, this hardware bug persists on the Plus?
but feasible on the Plus (with the replacement such as ParaDOS still appearing at number 7 when in X-MEM?).No, it's not possible to replace ROM 7 without a hardware mod, because those CPCs not disable this rom when the ROMDIS pin is enabled, it's an Amstrad bug.
But having Parados in ROM 6 (and i have used that config since the first day of my Megaflash) is not incompatible per se (even uses the same work ram than amsdos), it's more a problem of faulty software that only reinitialize the ROM 7, the same case of software that only works from drive ASure, Vortex and Dobbertin also used the "lower ROM number" workaround at least as an option, but not much software will get fixed after 30 years (though arguably most of us know CPC MC down to opcode level and your program will come to help :) ).
The ROM7 have to be provided by the floppy drive expansion to be compatible with all CPC and programs.
The ROM7 is not intended to be disabled, because it handle hardware than should make for CPC no more working properly.
Than mean:
- A CPC w/o floppy drive don't have to provide a ROM7.
- The DDI-1 external expansion provide the ROM7 and the floppy controller.
- The CPC 6128 and 6128 PLUS internal expansion provide the ROM7 and the floppy controller.
- An external ROM Board shouldn't provide the ROM7, because it not provide a floppy controller.
Parados (or any other DOS) should be used instead of AMSDOS (physically replacing it) or after the AMSDOS initialization.
If programs are not properly written and don't allow to work under ROM 7, don't use them. (they probably done more bad things)
Parados is not an exception. It's a ROM like others and only its priority allow it to replace previous code into the memory.
If you put it at ROM 7, yes it fully replace AMSDOS. (like other DOS)
If you put it at ROM 6,5,4,3,2,1, it will override the ROM 7. (like other DOS)
They are not DOS, but DOS patchs. (or upgrade if you prefer)
It's better because, as AMSTRAD done, the ROM7 was not intended to be replaced.
As no CPC allow to replace the ROM7 without hacking... no.
The fact that it work fine is an other thing. (thank to the authors for it)
I am not sure on this point either.The plus is the only one that allow disabling ROM7 externally. While on 464 the AMSDOS ROM is on socket and can be easily replaced by PARADOS one, on 664 and 6128 you need to unsolder the internal ROM for doing so. That's not an easy task !
My symbiface replace slot 7 without and hardware mod on the plus. I cannot remember if it does the same on the Cpc tho.
Sent from my HTC One_M8 using TapatalkCan't you disable this ;) [nb]unless tapatalk is giving 1€ to cpcwiki for each sponsored post :laugh: [/nb]
While on 464 the AMSDOS ROM is on socket and can be easily replaced by PARADOS oneOn DDI-1 I suppose? Or magic 464? :D
Sure, putting Parados at ROM 7 work as it's a full DOS.The ROM 7 replacement being the most inconvenient on the Plus (as cartridge clones incl. ACID (http://www.cpcwiki.eu/index.php/Modern_Cartridges) are not commonly available), it should be tested whether PARADOS (or a Vortex variation) can actually be installed on X-MEM slot 7 and toggled on the fly to switch between AMSDOS and its replacement(s) between resets.
Probably, the PLUS not avoid to replace it like the 6128/DDI-1 does.
To be CPC friendly, the best is to not done thinks that not work on all of them.Au contraire, as a replacement ROM 7 can be piggy-backed on the original one (unsoldering just one Enable pin thereof) on the classic CPCs (where the lack of ROMDIS ought to be considered nothing but a routing flaw) but not on the Plus.
Personally, I don't use Parados because it's useless today. (but everybody is free to do what they wants...)"Useless" unless you need its (or any other DOS's) utilities and/or have a pile of aging disks of various sizes that need to be salvaged to image files before they demagnetize entirely.
As no CPC allow to replace the ROM7 without hacking... no.
The fact that it work fine is an other thing. (thank to the authors for it)
Au contraire, as a replacement ROM 7 can be piggy-backed on the original one (unsoldering just one Enable pin thereof)That is hack.
That is hack.Of course, but as I suggested in X-MEM, a new memory expansion for all CPC. (http://www.cpcwiki.eu/forum/news-events/x-mem-a-new-memory-expansion-for-all-cpc/msg81556/#msg81556) (see also with respect to the MotherX4 Board) ...
There is enough space free on the ROM boards to put it under ROM 7 if needed.... there just isn't that space inside a Plus cartridge.
Is it not ROM7 that can be used externally on some 6128s and not others? IIRC I have at least one 6128 where it _does_ workProbably one of the later "cost-down" versions that pre-empted some of the Plus circuitry?
Of course, but as I suggested [...] there just isn't that space inside a Plus cartridge.I don't plane to allow features on some CPC that not work on others. The goal is to reassemble the community, not to share it.
Hence the Plus is where an override for ROM 7 would be particularly useful, if you find it does work after all.
purpose) when AMSDOS got bolted on in the usual hurry (http://www.theregister.co.uk/2014/02/12/archaeologic_amstrad_cpc_464/), then fixed in later revisions.This suprised me:
I don't plane to allow features on some CPC that not work on others. The goal is to reassemble the community, not to share it.I for one ain't ringing no division bell either: ;)
Probably one of the later "cost-down" versions that pre-empted some of the Plus circuitry?No, no, no :D : Look at Arnold4 - CPCWiki (http://www.cpcwiki.eu/index.php/Arnold4)
That would support my point that the trace for ROMDIS 7 was probably forgotten (rather than omitted on purpose) when AMSDOS got bolted on in the usual hurry (http://www.theregister.co.uk/2014/02/12/archaeologic_amstrad_cpc_464/), then fixed in later revisions.On 664/6128 amstrad only merged the DDI1 schematics to the main board. And I think it was left like this because Amstrad did not plan to have that specific rom disabled by external extension (and would have cost few gates ....)
On DDI-1 I suppose? Or magic 464? :D:P
In this case, you have to know that is not always socketed and some are soldered too. (need to find the pictures)The DDI1 I've seen all had a socket, but they range from 85 to late 87. Want pictures !
No, no, no :D : Look at Arnold4 - CPCWiki (http://www.cpcwiki.eu/index.php/Arnold4)
As for these CPC that works with external ROM 7, this is not an expected behaviour but rather a 'lucky' one.
There is a dedicated thread (Disabling ROM 7 (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/disabling-rom-7/msg69899/#msg69899)) where we can discuss that endlessly :laugh:Great, you found it :D
So unlike we assumed in the thread linked above, this hardware bug persists on the Plus?When i wrote about "those faulty CPCs", i was talking about the ones where ROM 7 can not be disabled. This theme has been discussed to death, my CRTC 4 can not disable it and my multicrtc neither (i think originally was a CRTC 0), but in my CPC+ can.
I thought ROMDIS had been fixed for the CPC6128plus, hasn't it?Sure, Vortex and Dobbertin also used the "lower ROM number" workaround at least as an option, but not much software will get fixed after 30 years (though arguably most of us know CPC MC down to opcode level and your program will come to help :) ).I don't understand that obssesion for putting Parados in slot 7, when in slot 6 works perfectly fine too and not take any extra byte.
; Save number of disk drive used to load the program
LD HL,(AMSDOS_RESERVED_AREA)
LD A,(HL)
LD (.sm_floppy_drive + 1),A
LD C,$FF ; Disable roms
LD HL,.real_start ; Real program start address
CALL MC_START_PROGRAM ; Run program
.real_start
CALL TXT_VDU_DISABLE ; Hide initialize roms messages
CALL KL_ROM_WALK ; Initialize all the roms (not everybody has Parados in 7)
CALL TXT_VDU_ENABLE ; Unhide firmware messages
; When Amsdos is initialized, the default disk drive is 0. Because that
; we need to restore the number of the drive used to load the program.
.sm_floppy_drive
LD A,0
LD HL,(AMSDOS_RESERVED_AREA)
LD (HL),A
OK, this will be my last post on the matter of Disabling the internal Amsdos with an external Slot 7 parados.Thanks for the confirmation. :) At a minimum, there should be one more post from you (no matter the first sentence ;) ) when you've actually received the X-MEM as I'll probably have to hold my order until we know this works in spite of TotO's (somewhat surprising) opposition to the idea (of using what is clearly a feature of some CPCs at least).
Of my machines....
both 6128 pluses are fine with external slot 7 parados and work (as we know they do)
interestingly my UK cpc 6128 works as detailled . External slot 7 has no effect, Amsdos is initialised (as expected) however my Schneider CPC 6128 works in the same way as the plus. in that an external slot 7 disables amsdos and uses parados instead.
I now cannot wait to get my hands on the X-Mem I have ordered to see if that exhibits the same functionality as the Symbiface.
I hope it does :)
Thanks for the confirmation. :) At a minimum, there should be one more post from you (no matter the first sentence ;) )Ok one more when I get the X-mem then. No worries. Or is that 2 more, does this one count
@OCT (http://www.cpcwiki.eu/forum/index.php?action=profile;u=245) : You can forget. The ROM7 have to be provided by the floppy controller. That all. Is difficult to understand?Not sure what got you on the wrong foot here - except that I hadn't been around for a while and hence would not know of an earlier debate in a different thread.
X-MEM allows a highest level of compatibility than all existing boards, because it respect the AMSTRAD CPC hardware design.
If you want to use Parados, like SyX said, you should put it at ROM 6.
The FDC functionality is just 16K preferably in ROM slot 7We may of course agree to disagree without any need for decapitations, :o the year not being around 1790.
SyX do a great work on the FW3.x !
Now, it's possible to use a simple CALL from the BASIC to program any ROM and we no more need to turn the hard switch ON/OFF on each programming. (it's use is more like a floppy disc now)
10 MEMORY &3FFF:LOAD"MYROM.ROM"
20 CALL &B8DD,&4000,1,256 (,256 is optional)
Now, MYROM is written at ROM 1 using a 256bytes page.
10 MEMORY &3FFF:LOAD"BLANK.ROM"
20 FOR i = 1 TO 31
30 CALL &B8DD,&4000,i
40 NEXT i
The ROM Board is now cleaned.
By the way, how does one (safely) replace a ROM 0 through X-MEM for that matter (e.g. to temporarily turn a 6128 into a 464, or vice versa) ?The save way to write ROMs on the X-MEM is to set the bit5 to 1.
I suppose the method might be different from the one outlined below:
For those of us who not installed ROMs can you provide some guidanceThe X-MEM board is provided with a notice and a floppy disc including tools and examples.
SIDE A:
- README .TXT : This file.
- GETSTART.TXT : Text version of the CPC X-MEM Get Started! notice.
- INIT . : Erase all the X-MEM ROMs. Should keep the systems ROMs if needed.
- INSTALL . : Install the system ROMs (FW3.14, FW3.14 EXP, BASIC 1.1) and optionally CP/M.
- EDITOR . : X-MEM editing tool v1.0. Allow to explore the ROM content and update them.
- FLASHER . : X-MEM flashing tool v1.6. Allow to copy ROMs from floppy or RAM drive, to ROMs.
- MONITOR . : X-MEM monitoring tool v1.4. Allow to visually check the ROMs integrity.
- RESCUE . : Disable all the X-MEM ROMs. needed is a bad ROM/flashing avoid to boot the CPC.
- EXRAM1 .BAS : RAM example. Display the Video Gate Array (64K) and the CPU (512K) memory.
- EXROM1 .BAS : ROM example. Use the FW3.14 |FLASH RSX for writing the wished ROM.
- EXROM2 .BAS : ROM example. Use the OvL! BURNX.ROM |BURN RSX for writing the wished ROM.
SIDE B:
- README .TXT : This file.
- GETSTART.TXT : Text version of the CPC X-MEM Get Started! notice.
- INSTALL . : Install the originals CPC system ROMs. (FW1.0, BASIC1.0 or FW3.0, BASIC1.1)Question, If I make a "cart" game (compatible with cpc) and write it to the x-mem, writing the new "lower" rom and some expansion roms, is it still possible to rescue it with "rescue"?The RESCUE program don't unset LOWER and ROM0, as they should be needed to boot from the X-MEM. (assuming they are well written)
Will cartridge roms work with this without the presence of an ACID chip?No. Acid (or emulating PLD) is part of the plus design. It does not work without.
Will cartridge roms work with this without the presence of an ACID chip?My plan wasn't really to create a cart this way, at least not a plus cart. But a form of cart game for cpc would be possible.
Can the X-Mem improve performance as I note some slow downs in Dizzy and games like Ikari Warriors when a grenade blows up a bunker
@TFM (http://www.cpcwiki.eu/forum/index.php?action=profile;u=179): Please feel free to prove it by modifying dizzy or ikari warriors to make them faster.
Yes it can. But you have to write games for it. It will not work with old games which don't use the new features.
I don't think he means it will be faster as in the game runs faster, but it can be used to make the whole game experience smoother, by removing mid-game data loading or removing the need to compress data in RAM. The data will still need to be loaded at the start, but it should improve the overall feel by not having to wait between level. I'd like to see this done on something like Gauntlet, where the re-loading used to really annoy me.He means that, but he really does mean the game can also run faster if modified to take advantage of the extra ram. Faster=more fps.
Bryce.
Maybe, but I don't see how really. If at all possible I doubt the difference would be enough to be obvious to the player.Some things can be stored uncompressed, compiled sprites can be used for faster drawing potentially. But compiled sprites and clipping is not easy and a lot of games like ikari warriors have sprites that clip.
Bryce.
The 5th X-MEM batch will be dispatched tomorrow !!! ;Dooohh I hope I'm in the 5th batch.
The 6th batch will be dispatched start of July.
The 7th batch will be dispatched half of July.
I also discovered a small guest inside my CPC :)
[ You are not allowed to view attachments ]
Did you notice the CPC running any slower? :)Nice!
Regarding adding expansions externally. Any expansion that doesn't offer similar functions will work fine, but other ROM or RAM expansions could cause an issue.
Which RS232 expansion do you have?
take care that the files doesn't have the AMSDOS header... they have to be pure bin files.
I will write the image to a floppy tonight and test the ROMs. I'm quite sure it will work.
I used SymCommander to copy the files from an MS-DOS formatted 720kb floppy to an AMSDOS floppy. I don't know if SymCommander altered the files in any way.SymCommander doesn't alter anything when copying files. The only thing which may be altered is the size of a file, as in AMSDOS you always have to round the size up to 128byte aligned values.
cleaning it successfully was a pain. Ended up scratching at the pads with a screwdriver to get them to shine up (my fibreglass cleaning pen's gone missing again.)Using 70° alcohol on cotton swab is enough to clean properly a 30 years old connector. Then, plug/unplug some times the edge connector.
Any way to get the mode-2 boot screen using a different colour scheme though? Not being gold on blue just looks *wrong*.The FW 3.1 boot on MODE 2 using readable CP/M styled bright Platinum on blue (yes...white)
A bigger issue is my Mini-booster stops being visible if the X-MEM is also plugged in - inp(&ff00) gives 170 if the minibooster is alone, and 255 if the X-MEM is presentIt look to be not enough power for the two boards...
It look to be not enough power for the two boards...
Do you use a 3"1/2 drive connected to the CPC +5V ;D (if yes, it's bad as you have to use 12V to 5V regulator instead :p)
A way to fix that is to plug an external 5V PSU to the MotherX4 for powering the external expansions.
Fine, I'll figure out the palette change myself, it won't be hard to find.The palette is in the same place than the 6128 rom (offset $1052) ;)
No external drive, but I am using a separate 12v/5v psu (my CTM640 is in storage) which might not be sourcing enough current. Easily enough fixed.
More likely to be that my edge connector is still heavily oxidised and needs much more rigorous cleaning - I used a good 5v supply to no benefit.I had yesterday the same problem and it was that, i used a cotton wet with the clean electronics and circuits spray and everything return to working perfectly :)
Is there an unused Pin (and a few free cells) on the X-MEM CPLD left? If yes, and if TotO wants to help, it would be easy to upgrade the X-MEM to 64 ROM slots by soldering a second flash chip piggybacked on top of the other and connect the !CE-Pin to the free CPLD pin. Need s some CPLD reprogramming, though. Would be great for the game ROM collectors...
Indeed that would be fantastic...You can Imagine that I have needed to remove extra settings features because no pin left and not the invert. :)
Is there an unused Pin (and a few free cells) on the X-MEM CPLD left? If yes, and if TotO wants to help, it would be easy to upgrade the X-MEM to 64 ROM slots by soldering a second flash chip piggybacked on top of the other and connect the !CE-Pin to the free CPLD pin. Need s some CPLD reprogramming, though. Would be great for the game ROM collectors...
There's already been problems reported when all 32 ROMs have been populated, so I doubt 64 ROMs would ever be usable without doing lots of parking/unparking of ROMs.I've not yet had any problems with all 32 slots populated on my symbifaces. Games, serious stuff and cp/m or a mix of all 3. What issues have been seen?
Bryce.
But the best solution for game roms, it's making a rom launcher and mark the games roms as not need to be initialized by the firmware.
Not every ROM must be an Expansion ROM!!! When using extension ROM no RAM will be wasted. For example you need only one ROM initialized for FutureOS, the other three ROM can or can not be initialized. I guess it's similar with symbos. And for games, if a game uses 2 or 3 ROMs, then just initialize the first one, a smart launcher system will find the other parts too. Just my 7 Pfennige.
For information, some peoples answer when I ask for package information but don't when I ask to pay the shipping fees. :-X
You'll always get those when you sell retro hardware. I found it to be about 10%. You learn to recognize and compensate for it though./me hopes he never falls into that 10%.
For information, some peoples answer when I ask for package information but don't when I ask to pay the shipping fees. :-X
You have to know that I give your boards each time to next peoples on the list...
You'll always get those when you sell retro hardware. I found it to be about 10%. You learn to recognize and compensate for it though.It was around 10% before I ask, then 5% left.
I wholeheartedly thank That 10%.Sure, because 3 of them was before you. ;D
I've also had several people who paid and never sent their address and don't react to request e-mails although I know they are still active ?? Can't explain that one at all. :D
Bryce.
Gesendet von meinem Motorola DynaTEC 8000X mit Tapatalk 2.
Got mine today, works nicely indeed ;D
Although I did have to flip my cable around as we have different opinions as to where pin 1 is :P
1 week in not enough here... And after reading on Internet, it's said that the Sun don't send the good UV to achieve that.if you post it to me I'll erase it in my 5 minute eraser
But OK, I'm going to let it for August 1st to August 15th and see. :D
Are you in North France? :DOr just buy a new, blank chip.
You can buy an EPROM eraser for the cost of the postage to Ireland and back.
Bryce.
You can buy an EPROM eraser for the cost of the postage to Ireland and back.For the same delay, I will retry the free Sun power first. ;D
I have to replace the flash IC from Winbond to SST after the need to return 20 "defectives" chips...
As, I was not able to wait 1 month for the exchange.
That means, the FW3.15 and the provided tools support both chips, as well as Megaflash and FlashGordon boards.
Does this mean that some X-MEM have a Winbond and some have a SST Flash?Yes, and the next release could have even a different flash chip, for the user is not important the technical details while the flash program works perfectly :)
It's not possible to switch off ROM 7 to get a pure CPC464 without Amsdos, cause the internal CPC6128 Amsdos ROM7 is always be initialized?
Or does anybody know a special hint to switch off internal and external #07?
I believe utopia and/or protext do the same.
Sure. Install f.e. X-DDOS at position 6. Then enter "!ROMON" without parameters, the result is a CPC with only BASIC (ROM 0) initialized, but not ROM 7 (or any other ROM).
I believe utopia and/or protext do the same.
package arrived but there was no documentation with my x-mem , mother x-something, booster and bluetooth :-( I don't even know how to plug it in :-) not a sheet of paper with someting on it :-(
package arrived but there was no documentation with my x-mem , mother x-something, booster and bluetooth :-( I don't even know how to plug it in :-) not a sheet of paper with someting on it :-(Hello,
For peoples that not give me the information, I have sent an email to know that. (download, or 3"1/2 + paper or 3" + paper)Oops I guess that was me then. Still the system works as I got the mail and requested accordingly.
I send the 3" package by default if peoples not answer to my email.
Can I ask a few questions as a currently non hardware owner, but somebody that would at some point like to make a very large game using a 512k Rom X-Mem boardthe xmem has a 2x25 pin connector, and as such use on any CPC needs an adaptor. Either edge or centronics connector to 2x25 way. As mine has not yet arrived I can not comment on if the 2x25 connectors as male or female.
Am I correct in thinking this fits directly like a game cartridge might on another system directly onto the 464/6128 connector (I assume the + would require an additional connector)... meaning we had a base cartridge that costs just 20 euros. Any hope of a case?
If after that somebody has a PlayCity card we could take advantage of it but that would need the Mother 4 also.
Cheers
If the CPC hardware is designed to take up to 256 external ROM ( theoretically ), then we can use 8 X-MEM boards ?
That would also bring us to 4mb of RAM, right ?
I would love to see such a "train" setup: two 4XMother and 8 X-MEM :)
Hi!
I would need help to test ROManager 1.8 (FutureOS) for X-MEM (SST chip), FlashGordon and MegaFlash.
Any volunteers?
At the moment only the FutureOS version is ready to go. As soon as I know that it works I will also update the version for Amsdos.
If you want to check with X-MEM (SST) please have a try... Start the "-R" file, Docs are in "-ROM.TXT"
Your help is appreciated :)
EDIT: Update added, there was the most important thing missing in non-German language interface. Sorry dear single downloader, please download again. :)
Hello CPC_Fan,
Originally, the fact is that I don't want to spend my time building cables with rare connectors for many peoples that will not deserve my projects... And going to miss connectors for peoples ordering for MotherX4. (that allow to plug 4 boards with only one cable)
Understand that is why I have made this choice. :)
Now... I'm going to see if I can do that for peoples ordering only 1 board. (next, MotherX4 will be provided w/o if needed)
I will let you know.
Thanks for the reply TotO and for clearing that up for me. I will hopefully be able to order a X-Mem and a MotherX4 soon.do it, you won't look back
Post a screenshot? :)
Is it possible, the Demo Batman Forever http://www.pouet.net/prod.php?which=56761 (http://www.pouet.net/prod.php?which=56761) doesnt work with the RAM-Expansion?Is your XMEM configured for the 464 (1st switch on the left) ?
I have testet the 1-Disk and 3-Disk Version.
The Loading Screen starts, but when i press any key, he Comes again.
With the dk'tronics 64K MEMORY works fine.
I use a CPC464.
A little advice for coders. Since the wonderful X-MEM is now a new standard (= almost every active CPC user (except the shameful Eliot) have it connected to his CPC), coders must be careful with their BANK selection. This advice is valid even if you don't need the X-MEM for the final version of your program, and just use it for development.
Until now, on a naked CPC, you can select a BANK with B=[#7F, #7E, #7D, #7C, #7B, #7A, #79, #78] if C=#80 (BIT 7 = 1).
But the X-MEM decode the BIT 0 of the MSB of the BUS adress, so we have now:
- #7F, #7D, #7A, #79 : select X-MEM RAM
- #7E, #7C, #7B, #78 : select CPC RAM
So be careful if, like me, you like to send data on the BUS with OUTI (LD BC,#8080 followed by 8 OUTI), your BANK selection must occur when BIT 0 of B register = 1. I just corrected this bug on my part for the 30 YMD: I selected a BANK with #78, and everything was crashing with an X-MEM connected. I replaced #78 by #79 and everything work fine.
Note that with this decoding technic, we still have access to the 64K extended memory of the CPC, so we have 512+128=640k (and not only 512+64=576k). Maybe this memory supplement will allow to Iron to make an acceptable demo one day, because he can obviously make only beginners demos with 128k (history testified).
yes, Switch is on 464.OK :) , I've done some test on my 464s, and BF would detect that the XMEM is not properly configured (ie says that it need 128k to run).
or it could have to do with the new 464 board. Without ZILOG Z80?Do you mean the pre-asic version of the 464. (Which indeed have a Z80, but no more CRTC CI ;D )
yes, Switch is on 464.Hello,
you could change the address on the X-MEM? or it could have to do with the new 464 board. Without ZILOG Z80?
could someone test this?
The Bootscreen from the FW3.15-EN says:
RAM:576K | CRTC4 | FW3.15-EN
Board Vers. see Attachment
OK. So, the pre-ASIC (CRTC4) is the problem. It prevents the X-MEM to force the 464 to work "like" a 6128.As far As I remember, the pre-asic is not the problem, but the Z80 itself. A Z80 swap could do the trick.
Strangely, that not occur with the PLUS ASIC... Gerald already told me about.
I can send you a dedicated version of the CPLD for trying to fix that.
As far As I remember, the pre-asic is not the problem, but the Z80 itself. A Z80 swap could do the trick.I remember I asked you to do this test. That worked on one of your 464... So, I have added a warning on the X-MEM page.
On my CPC, replacing the ST one by a Zilog or SGS solved the problem.
As far As I remember, the pre-asic is not the problem, but the Z80 itself. A Z80 swap could do the trick.@gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250): Why must it be Zilog or SGS Z80? Do these allow the signal to be manipulated by the X-mem so that the expansion works??
On my CPC, replacing the ST one by a Zilog or SGS solved the problem.
@DerSchatten (http://www.cpcwiki.eu/forum/index.php?action=profile;u=603), what is the Z80 model on your CPC ? Also, do you have an other one and try a swap ?
I remember I asked you to do this test. That worked on one of your 464... So, I have added a warning on the X-MEM page.I've got my notes ;D
I got some zilog Z80 in stock for peoples who have doubt with that.
But... I'm not sure that was on the pre-ASIC model. :D
@gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250): Why must it be Zilog or SGS Z80? Do these allow the signal to be manipulated by the X-mem so that the expansion works??The signals are A15 and MREQn from the Z80.
Which signal is it manipulating? I am sure it has been mentioned before.. but I just wondered why exactly.
I've got my notes ;DExactly, it was the conclusion and the better think to do. :D
That a shame that AMSTRAD fixed the RAMDIS behaviour (so we don't need the force mreqn), but did not fix the C3 mode when in 464 configuration (and we still have to force A15).
But there is a simple solution to this : configure the pre-asic in 6128 mode so the XMEM work like on a 6128.
This need two wire soldering :
- one grounding the pre-asic configuration pin (tricky, 0.5mm pich IC) to switch to 6128 mode
- one preventing the non existing amsdos rom to be mapped in place of the basic one
But there is a simple solution to this : configure the pre-asic in 6128 mode so the XMEM work like on a 6128.Updated Arnold4 page with the modification : Arnold4 - CPCWiki (http://www.cpcwiki.eu/index.php/Arnold4#Enabling_6128_mode_on_464)
This need two wire soldering :
- one grounding the pre-asic configuration pin (tricky, 0.5mm pich IC) to switch to 6128 mode
- one preventing the non existing amsdos rom to be mapped in place of the basic one
Are you sure that EXT pin must be forced to GND for making it working?
Isn't the DDI-1 task to do that?
I think that stops the CPC from crashing when no DDI-1 is connected.Yes !
I think yes, as CPC 464 V1 and V2 with Zilog CPU use this Z80400APS.
CPC 464 V3 and 6128 with Zilog CPU use the Z8040004PSC.
Hit me! But IMHO it would be great if expansions would just work with the CPC without the need of changing the CPU. :-XIMHO, it had been great if ST properly clone the Z80 CPU... ::)
Ok, I'm a hardware novice. :( What do they fight for? :-X
I noticed that Switchblade wouldn't work with the X-MEM plugged in and instead the tape would just stop without the intro showing up.
Is this true? That's one of the games I wanted extra memory for (to have the awesome music).I'll check this tonight on my 464plus and x-mem.
Is this true? That's one of the games I wanted extra memory for (to have the awesome music).You can ear this fabulous music in this demo (http://astimpact.weebly.com/uploads/6/7/7/3/6773862/no_inspiration_1992ast_system.zip)
Well, I may remember wrong. But it runs on my 6128 Plus from Disc at least.yeah, Same here. It seems to be that the plus machines have far less flexability on the quality of the audio signal from the tape. The same tapes work fine on my cpc 6128 but are far more temperamental on the plus machines (Either my 464+ or 6128+).
Well I had it set to 464 and to boot from CPC when I tried to load switchblade from tape on my 464. Might have another look when I get home.As FW 3.15 has no Tape support in order to load from tape you will NEED to boot from the CPC Firmware.
Please excuse my ignorance here, but I have a couple of newbie questions I hope this great community can help me with:The Bad Command is because there is a bug in the Expansion rom for the RamDisc. There is a fixed version which TotO provided to me in this thread somewhere. OR if you rerun the install turning off the RamDisc until this new EXT rom is included on the next disc image release then this also fixes it...
1. Can you let me know where I can get an X-MEM floppy disk image from? Mine was working OK but now has many read errors - it isn't my drive as this has recently been replaced with a new 3.5" one and other discs are working fine. I can't find one on the support page of the centpourcent website.
2. I have installed PARADOS.ROM in ROM position 6 and this seems to show up fine in MONITOR, plus typing |HELP,6 shows the RSX commands ok. However, how do I get ParaDos to actually run/work when I boot the machine? If I type |DRIVE I just get BAD COMMAND. In fact, how do you get any ROM (e.g a game) to run once it has been installed in a ROM slot?
Many thanks for your help!
The Bad Command is because there is a bug in the Expansion rom for the RamDisc. There is a fixed version which TotO provided to me in this thread somewhere. OR if you rerun the install turning off the RamDisc until this new EXT rom is included on the next disc image release then this also fixes it...
On Second thoughts I am sure the guys will not mind me uploading a DSK copy of my XMEM disc that has the fixed EXT rom included. You only need to replace side 1 but both sides are included purly for completeness.
Craig
Hi all,I cannot help but notice 2 missing 'essential' peripherals. You need to get a PlayCity and a minibooster too [emoji6].
Here I have some photos of the extension that I have for my Amstard CPC 464:
img1 (http://www.subirimagenes.com/fondosycapturas-img1-9188316.html)
img2 (http://www.subirimagenes.com/fondosycapturas-img2-9188317.html)
img3 (http://www.subirimagenes.com/fondosycapturas-img3-9188318.html)
Here detail of the cable I made, and the extension connector, the DDI-1 Clone is connected to pass through the MotherX4 Main Board
img4 (http://www.subirimagenes.com/fondosycapturas-img4-9188319.html)
img5 (http://www.subirimagenes.com/fondosycapturas-img5-9188320.html)
http://www.subirimagenes.com/fondosycapturas-img6-9188321.html (http://www.subirimagenes.com/fondosycapturas-img6-9188321.html)
It is a perfect combination for 464.
I cannot help but notice 2 missing 'essential' peripherals. You need to get a PlayCity and a minibooster too (https://s3.amazonaws.com/tapatalk-emoji/emoji6.png).
Otherwise a sweet collection of boards.
Replacing a clone CPU with an original Zilog not conflict with "how it was", has there was used too.
On 100 X-MEM sold, only 2 peoples got the problem. And it was fixed like that. :-*
Look to be put online by mistake... It was for a private test. :-\Hi,
(not a final version. Please, don't use it if you made the download)
Also I couldn't get into Parados using the |drive command when the X-Mem worked briefly the first time. The 6128 just came back saying "bad command"For the bad command, its because the provided lower/basic ROM does not pass |drive on to parados. If you search the thread you will find a fixed version attached here somewhere. If you cannot find it I'll dump it from my xmem tonight, but I a playing house removal guy today.
Any ideas of what the problem might be?
Ahh I see. Thanks Craig. I will have a look through the thread to see if I can find it.the flasher on the disc will let you do it.
Next stupid question: Can I erase just one ROM image at a time from the X-MEM, or do I have to eraser the whole lot in one go? What program do I use and how do I do it? Sorry for asking, but I can seem to find how to do it in either of the get started notices.
I did see the flasher tool on the disc Craig. However I am still not sure how I erase one/all of the ROM'S? What command do I use and what exactly do I type??
Yes, it should be the problem. The +5V line is not intended to be used with a floppy drive.
You may try to add a +5V PSU to the MotherX4 for testing. (or unplug the floppy drive power to see if the CPC boot again)
I have found the bug fix dump on this thread :)OK, so you run flasher, and it loads to a screen that lists all the room slots. To delete a specific slot (eg 10) simply type
I did see the flasher tool on the disc Craig. However I am still not sure how I erase one/all of the ROM'S? What command do I use and what exactly do I type??
Sorry for being so thick, but this is all new to me.
Thanks Craig. I thought that it would be something easy like that, but I wasn't sure.a combination of winape and cpcdiskxp.
Now all I need to do is to figure out how to get .ROM files/images onto a Amsdos formatted 3.5 inch floppy disc using windows.
Ah I see. I take it that it's fairly easy to make a dsk image in Winape? How do I do it? Sorry for all the questions Craig. It's just that I've not done this sort of thing before and I want to make sure that I get it right first time.
Yes it is a real floppy drive in the pc that I use for copying Amstrad stuff on to :D
Thanks for the run down Craig.Oh I have just remembered how you can get into Parados when you have the bugged xmem rom files....
You mean 6, not 9!? Do you?no no. I meant 7 not 9 ;-)
Eventually 6 turned out to be 9! Oh, if Jimmy would have known...
Jimi Hendrix Experience - If 6 Was 9 (http://www.youtube.com/watch?v=Ui4ckbUNe3k#)
Ok, so it seems X-Mem on it's own is the ultimate rom/ram CPC solution.It's the best you can buy now. But 4 MB of RAM would be better of course :laugh:
- The only viable option of changing ROM7 is physically replacing the chip, right?It depends on your PCB, my 6128 has no problem if an external card replaces ROM 7. But other PCB versions do.
It depends on your PCB, my 6128 has no problem if an external card replaces ROM 7. But other PCB versions do.I think we had this discussion many times and you should better stop saying that is PCB dependant.
I inspected my 6128's board and it looks most closely to MC20000C and MC20000B. My Z80 chip has 8622 written on it , and the Amstad 40010 chip has 28622. What are my options?The only proper option are :
The only proper option are :Thanks gerald for your insight. So if I'm after alternative slot 7 rom (i.e. Parados) , after unsoldering the original rom and soldering the rom socket to the physical rom slot 7 to alternate between vanilla Amsdom rom and Parados and other forthcoming awesome roms I would unscrew the amstrad case to open it and physically replace it? And that's the best possible solution?
- remove the AMSDOS ROM and use an external extension that can replace ROM7 (The XMEM cannot do that)
- put the AMSDOS ROM on socket and put a your select ROM7 in the socket (EPROM)
- do what every one does, put alternate ROM in slot below 7, as they are supposed to work ;)
- do what every one does, put alternate ROM in slot below 7, as they are supposed to work ;)Wait that made me think. So let's focus on Parados for now. Using X-mem if I put it in slot 6, will it override the IO disk handling of internal Amsdos rom on slot 7? So is there a point for replacing the rom 7 at all if I aim for external hardware like x-mem?
I think we had this discussion many times and you should better stop saying that is PCB dependant.Sorry @gerald, I am with @TFM on this. I have both an Amstrad CPC 6128, and a Schneider badged one. On both of these my symbiface perfectly well replaced the soldered internal amsdos and replaces it with parados in slot 7. I do believe that there are only 3 specific machines that this works on. And that @TFM has one, and I have the other 2 seems unlikely.
There is NO WAY to disable the internal AMSDOS ROM on ANY 6128 PCB, whatever the revision. Only the Plus range allow this.
The fact that yours is working is just a lucky conjunction. It may fail at any time by either damaging the internal or external ROM.
The only proper option are :
- remove the AMSDOS ROM and use an external extension that can replace ROM7 (The XMEM cannot do that)
- put the AMSDOS ROM on socket and put a your select ROM7 in the socket (EPROM)
- do what every one does, put alternate ROM in slot below 7, as they are supposed to work ;)
Wait that made me think. So let's focus on Parados for now. Using X-mem if I put it in slot 6, will it override the IO disk handling of internal Amsdos rom on slot 7? So is there a point for replacing the rom 7 at all if I aim for external hardware like x-mem?Yes there is... 2 reasons in fact....
Sorry @gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250), I am with @TFM (http://www.cpcwiki.eu/forum/index.php?action=profile;u=179) on this. I have both an Amstrad CPC 6128, and a Schneider badged one. On both of these my symbiface perfectly well replaced the soldered internal amsdos and replaces it with parados in slot 7. I do believe that there are only 3 specific machines that this works on. And that @TFM (http://www.cpcwiki.eu/forum/index.php?action=profile;u=179) has one, and I have the other 2 seems unlikely.You can be sorry :P
I'd luv to see a noob guide on this matter ;) Anyway X-Mem by design I presume does not allow to replace rom7 (because most Amstrad pre-Plus PCBs won't allow it). I might by lucky enough (or not) that my MC20000C/MC20000B would still allow it without any internal modifications , but which hardware is for the job of providing rom slot7? (apart from Symbiface which might be hard to get)Symbiface II ? :laugh:
Symbiface II ? :laugh:Are schematics available for it?
Are schematics available for it?Not that I know of. And the required code to run the ide, ps2 mouse, rtc etc is not available either.
Not that I know of. And the required code to run the ide, ps2 mouse, rtc etc is not available either.You mean not available in Basic right? SymbOS can handle those^ with the Symbiface2?
I think we had this discussion many times and you should better stop saying that is PCB dependant.
There is NO WAY to disable the internal AMSDOS ROM on ANY 6128 PCBe supposed to work ;)
Wait that made me think. So let's focus on Parados for now. Using X-mem if I put it in slot 6, will it override the IO disk handling of internal Amsdos rom on slot 7? So is there a point for replacing the rom 7 at all if I aim for external hardware like x-mem?
You can be sorry :P
If you're with TFM on this, can you list how to identify a CPC that will work without any doubt with an external ROM7, without first plugging the extension ?
Yes, we hat that discussion often enough. The SF2 and the RRB can replace the ROM 7, which works for me, Toklkin, Mr.Ams, BrainBlaster, Prodatron and a lot of others.
The SF2 and the RRB can replace the ROM 7, which works for me, Toklkin, Mr.Ams, BrainBlaster, Prodatron and a lot of others.That's not true. I never replaced my Rom7 with the SYMBiFACE II.
That's not true. I never replaced my Rom7 with the SYMBiFACE II.
I did some tests to find why many Amstrad Plus demos don't work correctly if my X-mem is connected, but i didn't really find any way to solve the problem.Does not work with the XMEM nor my own memory extension.
I did some tests to find why many Amstrad Plus demos don't work correctly if my X-mem is connected, but i didn't really find any way to solve the problem.Yep, Mine does the same thing. I also noticed that the rb / mf patched plus cart also does not work with the XMem connected but works fine with the Symbiface.
Someone to help me? Can anyone confirm me the same problem?
This test has been made with my last demo "revival'n impact cooperation" in the part 1. You could find the dsk here (http://astimpact.weebly.com/mes-deacutemos.html)
Does not work with the XMEM nor my own memory extension.Yes, i only use c0,c4,c5,c6 and c7 with port #7f...
Are you sure you only use C0-C7 memory banks (1st 64K block of extension RAM) and not others ? Without the XMEM you always reach the 1st 64k extension block, whatever you select.
Yes, i only use c0,c4,c5,c6 and c7 with port #7f...AnorldWIP show the same symptoms (even with only 128k), WinApe is OK with 512k.
Synergy Demo and xMas 2008 do the same thing...
Maybe yes... But what?I'll take a look and tell you later :)
Unfortunately this intro (http://www.cpc-power.com/index.php?page=detail&num=7411) by Roudoudou does the same thing...
Problem is only on amstrad plus, i think.
Edit:
Same problem with Mario+ and Shadow of the Beast+ who can only work without x-mem.... It's so strange!
No problems. Thanks.nothing obvious. both using asic pri.
nothing obvious. both using asic pri.I still have an unmodified 464plus. Will try this tonight.
both using expansion ram normally.
@Ast (http://www.cpcwiki.eu/forum/index.php?action=profile;u=573): Did you try x-mem and 464Plus?
I wonder if there is a conflict between ram on x-mem and internal 6128plus extra ram.
@gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250): I think it's a coincidence that demo doesn't work on arnold wip. It's using split screen and scroll quite heavily.
Yes, i only use c0,c4,c5,c6 and c7 with port #7f...@gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250): I enabled I/o breakpoints in arnold debugger, set it to "dk'tronics ram compatible write" and it will break on the i/o write to select the ram. Then look at the IOAddr and value in the details to see the port and data that the z80 saw if it's not obvious from the dissassembly. I could see it was only these writes.
Synergy Demo and xMas 2008 do the same thing...
@gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250): I enabled I/o breakpoints in arnold debugger, set it to "dk'tronics ram compatible write" and it will break on the i/o write to select the ram. Then look at the IOAddr and value in the details to see the port and data that the z80 saw if it's not obvious from the dissassembly. I could see it was only these writes.How do I set a I/O breakpoint :-[
nothing obvious. both using asic pri.Sorry, no 464 plus.
both using expansion ram normally.
@Ast (http://www.cpcwiki.eu/forum/index.php?action=profile;u=573): Did you try x-mem and 464Plus?
I wonder if there is a conflict between ram on x-mem and internal 6128plus extra ram.
@gerald (http://www.cpcwiki.eu/forum/index.php?action=profile;u=250): I think it's a coincidence that demo doesn't work on arnold wip. It's using split screen and scroll quite heavily.
I still have an unmodified 464plus. Will try this tonight.Please tell us if it's running or not when your tests were done.
How do I set a I/O breakpoint :-[Open the debugger window. In the bottom right is the stack and the breakpoint windows.
If it works on 464 with x-mem, then it's probably x-mem ram clashing with extra 64kb ram inside 6128 plus.So what others non amstrad plus proggy works correctly?
If it is still broken, then the only thing I can think of is that somehow the data bus is clashing so that the value written to the asic registers is a combination of the data in the x-mem ram and the value you write giving wrong results.
The last could be tested by keeping the ram active, writing various values into it, paging in the asic registers to setup a pri interrupt and see if it doesn't trigger correctly.
So what others non amstrad plus proggy works correctly?do cartridge games work with it?
I also answered in my edit :Pit seems like a clash between asic ram and the expansion ram.. :(
You can use the FutureOS System monitor (Plus version) to check if RAM or Memory-Mapped is banked it. RAM/ROM/MM can be selected individually. No need to invent the wheel again. :)My test will be different ;)
My test will be different ;)
good point.
Yes, but if it fails in that (check banking in system monitor), why do bother wasting time?
Open the debugger window. In the bottom right is the stack and the breakpoint windows.Fount it, thanks to your screenshot. The stack/breakpoint pannel had a zero vertical size !
(see attached picture)
Fount it, thanks to your screenshot. The stack/breakpoint pannel had a zero vertical size !Hmmm.. I will reset my settings and see if I can fix it. If not I will report the fault to wxwidgets.
I think problem must be between asic page connection and xmem mapping connection...At least it is not xmem only related, my own interface has the same problem.
@Ast (http://www.cpcwiki.eu/forum/index.php?action=profile;u=573): I agree please try the attached dsk and tell me what you see.I'm going to test it and came back to tell you the result.
if all is good there will be a stable pri interrupt.
no pri = ram probably takes priority.
stable pri = asic ram takes priority
unstable pri = data potentially mixing.
And the result is :ok. That is correct, so no problem with that test.
Stable PRI Black 2/3 and Cyan 1/3
It seems to be all right so what to do? :-\Small question, is your demo code reading from the ASIC ram while extension RAM is also selected ?
ld bc,#7fb8:out (c),c
ld hl,#6400 ; copy anciennes couleurs
ld de,oldcol ; dans oldco
ld bc,#20
ldir
;
ld hl,#6000 ; Raz position/zoom Sprite Hard
ld de,#6001
ld bc,#7c
ld (hl),l
ldir
;
call sproff ; on planque les sprites hard derriere
; le plastique du moniteur (x=-64)
hop ld hl,tbout2:call tbout
ld hl,color1
ld de,color1+1
ld bc,32
ld (hl),0:ldir
ld bc,#7fa0:out (c),c
call clearinit
fininit
;
ei
ld bc,#7fc7:out (c),c
call intro
Small question, is your demo code reading from the ASIC ram while extension RAM is also selected ?I see writes to the soft scroll and split screen.. and that the crtc is reading from &4000-&7fff.
What do you mean exactly?I am thinking of another thing to test.
expansion ram active, asic registers active, split screen at &4000. :DWell, the video access should not do any harm, the demo works well without the external expansion RAM.
I am thinking that the x-mem ram causes problems (or the asic has a bug) and the asic reads pixels from the extra ram and not the base 64kb of ram. So you get pixels in the wrong place? I think the photo of your monitor is showing repeated graphics for the logo?That's not possible at all. The ASIC would need to be able to drive the Z80 address/contril bus to do so.
I don't know if the extra ram is also active at this time.This is something you need to add to the debugger ;)
ld bc,#7fb8 : out (c),c
call rll ; Rvi Plus Emulation
ld bc,#7fa0 : out (c),c
;
ld bc,#7fC7 : out (c),c
...do what you want...
That's not possible at all. The ASIC would need to be able to drive the Z80 address/contril bus to do so.
At least it is not xmem only related, my own interface has the same problem.
@CraigsBar (http://www.cpcwiki.eu/forum/index.php?action=profile;u=482), can you test with your symbiface ?
The write goes to asic ram AND to expansion ram?Yes I guess. I will make some test to confirm.
Does the asic assert any signals to indicate it's a internal asic ram access?There is no signal like this. Remember that the extension port did not change with the plus.
Should ALL expansion rams will suffer from this problem?To not suffer from this problem, the extension need to decode the ASIC ram mapping register. And to to it properly, it also need to emulate the ASIC lock/unlock mechanism ...
Ast said that he used 7fc0 to restore base ram before he did asic writes?I've seen the problematic write with a logic analyser. I cannot say for sure the ASIC RAM was enabled but writes clearly targeted ASIC register (sprite position &6000 and further), and the ram extension did the write as well.
the test program should show the error gerald has discovered.Pen0 :
it enables extra ram.
it writes &aa to it
it then enables asic ram
it writes &55 to it
it then disables asic ram
it reads the value
if it's changed, then value has gone to asic and extra ram. pen 0 changes colour.
if pen 0 is black, no write through.
So I guess that all memory extension made suffer from this problem.Wow, that explains a lot! Thanks so much for this finding!
Pen0 :Great. One more test. 7fc0 is selected.
- black without external ram extension
- yellow with external ram extension
Problem confirmed !
Yes I guess. I will make some test to confirm.Perhaps it can be worked around?
There is no signal like this. Remember that the extension port did not change with the plus.I hoped an existing signal would indicate it somehow.
To not suffer from this problem, the extension need to decode the ASIC ram mapping register. And to to it properly, it also need to emulate the ASIC lock/unlock mechanism ...ouch!
So I guess that all memory extension made suffer from this problem.
So, lets look on the positive side:Read is not a problem. The ASIC is generating the RAMOEn signal that the extension should use, and Amstrad engineer did they work properly ! (I've already checked this)
1. we know about the problem now
2. we can detect it.
3. if we detect it, writes could be done to the unmapped area in asic ram, now we can keep asic ram open AND make writes to extra ram! BONUS! :D
EDIT: What happens to the a memory read? Is it visible in the unmapped area exactly, does it conflict with read/write registers like sprite data...?
Great. One more test. 7fc0 is selected.This obviously work ;)
If this shows black, which I hope it does, then to work around the issue, 7fc0 must be selected before asic registers are enabled.
Is this "bug" should allow to exchange the sprites content by swapping the external expansion banks? ;Dno ;D
@Ast (http://www.cpcwiki.eu/forum/index.php?action=profile;u=573): Please can you post a photo of Roudoudoduodu's asm demo running on your plus with x-mem?Sorry, i can't. I ´m on holidays during one week. You must wait for my return...
does the asic not assert ramdis when asic ram is active? some ram expansions use diodes, but could they use pullups to handle the two way signal?Ramdis has to be asserted by the extension to prevent access to internal ram.
So to eradicate this bug, you just had to Reset bank by putting #c0 to port #7f before to connect Asic i/o page, am i right ?Yes
Ramdis has to be asserted by the extension to prevent access to internal ram.yes.
The asic assert RAMOEn when reading RAM (be it internal base/extension or external)
yes.I don't think any ram expansion listen to ramdis since they have to assert it during an access.
ram expansion assert ramdis, but they also listen to ramdis and do not activate if they see it? in this way ram expansion can take priority.
the asic does asset ramdis to block all external and internal ram when asic ram is active?
Strange that problem not exist 6128plus with its 64K expansion. (and no user see it before)
When has occurred? using 128K or more?
If we can find a way to fix the problem I will send a new CPLD for plus users.
ld bc,&7fc0
out (c),c
ld bc,&7fb8
out (c),c
Well, in the Dobbertin as in the Inicron RAM expansions the Bank &C4-&C7 can be switched on / off. So either CPC or expansion RAM is used.It will be a problem for ALL ram expansions and ALL RAM configurations (c4-ff) (ok excluding c0 "mirrors").
So what actually is the problem? You bank in some exp. RAM like &CF and MM IO and then?
To summarize all that has been found by Ast and gerald:@Executioner (http://www.cpcwiki.eu/forum/index.php?action=profile;u=17) : Do you think to add this to your new Winape version ?
- This problem concerns all ram expansions when used on Plus
- This problem is not isolated to x-mem. All ram expansions will show this problem.
- The problem is seen when extra ram is paged into &4000-&7fff, asic registers are paged into &4000-&7fff and a write is done.
- The problem is not seen with the extra 64KB in the 6128Plus when used without ram expansions. The ASIC knows about it and controls it.
- The problem *is* seen if you connect a ram expansion to the 6128Plus. The expansion occupies c4-c7. The write will go to expansion the read will come from expansion.
- to avoid the problem (choose a ram configuration where expansion ram is not at &4000-&7fff. e.g.
ld bc,&7fc0
out (c),c
ld bc,&7fb8
out (c),c
@Executioner (http://www.cpcwiki.eu/forum/index.php?action=profile;u=17) : Do you think to add this to your new Winape version ?
That may be a bit hard to emulate. If I read correctly, depending on the expansion, the write can go to both the exapnsion memory and ASIC RAM, but what does the read get? Are both the ASIC and expansion driving the bus?A simple (half) way to emulate would be to have the write done on both ASIC ram and extension RAM. That is what happen on the real HW.
A simple (half) way to emulate would be to have the write done on both ASIC ram and extension RAM. That is what happen on the real HW.I have implemented it this way :)
A complete emulation is not really possible as both ASIC and extension RAM return a value, the Z80 only seeing the result of the bus conflict.Ok I thought the read would only come from asic registers. I can implement this.
You can either return garbage, ASIC, RAM or a mix of ASIC/RAM value. But ideally you could trigger some kind of emulator HW exception that will stop the emulator and enter the debugger like a breakpoint.
@Arnoldemu : Are you always working on Arnold ? Is window version ready ? Could you give us the link to download it, please ?Yes.
Ok I thought the read would only come from asic registers. I can implement this.I need to double check that on HW, looking at the bus with a scope.
Does not work with the XMEM nor my own memory extension.
Are you sure you only use C0-C7 memory banks (1st 64K block of extension RAM) and not others ? Without the XMEM you always reach the 1st 64k extension block, whatever you select.
At least it is not xmem only related, my own interface has the same problem.Which is your own memory extension/interface referred to?
@CraigsBar (http://www.cpcwiki.eu/forum/index.php?action=profile;u=482), can you test with your symbiface ?
Which is your own memory extension/interface referred to?Prototype visible here : CPC+ RAM extension ? (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/cpc-ram-extension/msg51592/#msg51592)
Prototype visible here : CPC+ RAM extension ? (http://www.cpcwiki.eu/forum/amstrad-cpc-hardware/cpc-ram-extension/msg51592/#msg51592)OIC, great to fill the void until SymbiFace3 Hardwareentwicklung | Dr. Zed's evil Lab (http://dr-zed.de/?cat=5) comes to life Really Soon Now, but not "commercialized" in light of TotO's X-MASS & X-MEM (BTW allowing 640kB on 6128s too?) ?
Final version had some instability on the compact flash side that need a redesign.
The RAM/ROM is fully functional.
OIC, great to fill the void until SymbiFace3 Hardwareentwicklung | Dr. Zed's evil Lab (http://dr-zed.de/?cat=5) comes to life Really Soon Now, but not "commercialized" in light of TotO's X-MASS & X-MEM (BTW allowing 640kB on 6128s too?) ?640k support on 6128 : Yes
Since mentioned in the testing, does any of these provide an equivalent of the Cherry-T/Khany RAM bank swapper (unless someone has figured out how to replicate that on a CPC6128plus) for the first memory bank, which so often allows to capture 64k code with its defences down? 8)Switching the 64k main banks requires modification to the motherboard.
an unpublished tip for pyradev users (http://www.cpcwiki.eu/forum/emulators/an-unpublished-tip-for-pyradev-users/msg7122/#msg7122)
an unpublished tip for pyradev users (http://www.cpcwiki.eu/forum/emulators/an-unpublished-tip-for-pyradev-users/msg7163/#msg7163)
File:Khany's BankSwapper.jpg - CPCWiki (http://www.cpcwiki.eu/index.php/File:Khany's_BankSwapper.jpg)
640k support on 6128 : YesTotO, same for yours?
Switching the 64k main banks requires modification to the motherboard.Anyone with more than one Plus, ;) how about trying this out?
Doing this on a Plus should be easy, the CAS signals are going through resistor from ASIC to RAM devices.
Over X-MASS I tested the Inicron 512 KB expansion, which is S-RAM buffered and allows to select between internal or external 2nd 64 KB (&C4-&CC). Works like a charm! I couldn't test with X-MEM though.Do you still have access to it?
The X-MEM allow to select the extra 64K (or 512K) at $7E00 to reach 640K or 1MB.Is this always active? Or is it selectable with a switch.
Do you still have access to it?
I have emulated the inicron ram in arnold wip and I want to check I emulated it correctly.
Yes but not 100% compatible.
It's nothing different, compatible to Dobbertin and dk'tronics. Only difference: A switch selects between internal or external 2nd 64 KB bank on a CPC6128 (or 6128 Plus in this case).
Yes but not 100% compatible.
on cpcwiki:
"Since the box is not 100% compatible to DK-tronics or Dobbertin-Expansions, it is not supported by Symbos or FutureOS."
Document attached.
I hope I emulated it correctly. I will send you a link that you can use to try it out :)
I should assemble them with my eyes closed. ;D
Don't, you'll burn your fingers :D
Bryce.
I'm new to the scene, but I'm interested in the X-MEM, should be a nice companion to the HxC that will arrive soon. I'm a bit confused at how to plug it to the Amstrad proper. You need the additional ribbon cable, right? And you only need one ribbon cable if you get the MotherX4 and more addons afterwards.The X-MEM use a 50 pins connector, to be used with an Edge or Centronic ribbon cable, depending of the CPC model or directly plugged on the MotherX4 slots. (in this case, the ribbon cable is used to connect it to the CPC instead)
I was playing with the new firmware in WinApe (Is there a thread for the new firmware? I couldn't find any) and I have to say it is brilliant. But there is one thing that I wish could be changed. Correcting the keyboard so that the | key prints | instead of ù on the screen is good. However, ù should have been kept its function as an alternate of |, if you get what I mean? Pressing | and ù correctly displays | and ù, and the commands |cpm and ùcpm should both work. Now, only |cpm works and I have to say 1) it messes with 30 years of ingrained keyboard use and 2) having a direct access to | without using SHIFT was freaking awesome.The 'ù' key is definitively a side effect of the french firmware. Both symbols can't definitively works together... I have always used SHIFT+'|' on the french keyboard for the RSX ; It is the right way. ;)
The 'ù' key is definitively a side effect of the french firmware. Both symbols can't definitively works together... I have always used SHIFT+'|' on the french keyboard for the RSX ; It is the right way. ;)
Accessing Level 2 characters are just slower and more difficult. It's why the various French characters were placed at direct access on the first row instead of the numbers, or why accentuated letters have their own key instead of using a dead key. Professional programmers tend to switch to more efficient layouts, with direct access to the characters most used in their favourite coding language in order not to use SHIFT or ALT.German QWERTZ is actually much less useful to programmers than many other layouts: Even with the latest PC keyboards' "many keys more", > needs Shift (unlike < on the same key: oh the joy of writing HTML/XML that way :'( ), and each of @ { [ ] } \ ~ | even "Alt Gr" (an extra Alt to the right of Space, the additional level of which often fails over terminal emulators).
I just feel it's sad to relegate |ù to a second level when we had it on direct access for so long, especially as it's a character used quite often in AMSDOS. At least " is still on direct access on AZERTY, unlike QWERTY users who have to use SHIFT every time they want to start a program, be it run"disc or |cpm.An AZERTY keyboard have far more 2nd level keys than a QWERTY keyboard... So the argument is not valid for the occasional RSX usage. ;D
Yay! My X-MEM arrived at the long last :)
Hmm, where to start, what roms to install, have lots of things to think about this evening, olé!
I've found one game which doesn't work when the RAM is expanded. More precisely, the DSK image I'm using has trouble when the 4M expansion is activated in WinAPE 2.0beta2. I don't know if it happens on real hardware with an authentic copy of the game.
The game is Eve of shadows, the text is completely garbled during gameplay.
Have you considered mounting an extra switch on your board to disable the RAM? I only see switches for ROMs in the documentation.
That's not needed. You compare apples and peas here. The X-MEM has 512 KB while the 4M has 4 MB. There is a difference! I'm 90% sure it will work with X-MEM. Reason: X-MEM uses port &7Fxx, but the 4 MB expansion uses ports between &7Fxx and &78xx. Also don't judge from an emulator to real hardware!!! :)
Oh of course, as long as I can't test on the real hardware I can't decently fill a bug report about it. I just thought about mentioning it here in case it was something known or common.
I got mixed in my bits and bytes then, I thought the 4M option in WinAPE was akin to the 512k of the X-MEM. Sorry about that! It didn't help that the 3.15 firmware shows a 576K RAM value when the 4M option is selected (hard limit?)
Hello,
I am new to the Amstrad so be nice ;) .
I have a 464, but so many demos are for 128K :( , and CPC6128's are very expensive.
Sorry if this is stupid, but could the excellent X-MEM be plugged into Zaxon's DDI3 USB Floppy Emulator to give us poor 464 owners a nice access to 128K programmes? Maybe a firmware tweek is required.
If this is a stupid idea, then are there any alternative suggestions?
Thanks.
DDI3 USB Floppy EmulatorDDI3 USB Floppy EmulatorDDI3 USB Floppy EmulatorZaxonZaxon216
DDI3 USB Floppy EmulatorDDI3 USB Floppy EmulatorDDI3 USB Floppy EmulatorZaxonZaxon216:-\
:-\
So I would end up with a rats nest of MotherX4, X-MEM and DDI3, making my 464 as deep as it is already wide :laugh:
I have loved to be able to make cases for my expansions, but it was not really easy to use the switches.
I received mine today, but I've been running into a bunch of problems using it with ROMs.I have tested your X-MEM and programmed ROM on it without any problem.
Could you take a Photo of the CPC and the cable and the mother 4 as you have it connected Please.There is no MX4, only the X-MEM board with the ribbon cable, chips facing up.
I have tested your X-MEM and programmed ROM on it without any problem.I just did. I forgot to do it at first and I hoped it was my problem, but
Please, try to clean your expansion connector with cotton-stab and alcohol. 8)
Every time I've had problems flashing a ROM file to my X-MEM it's because I forgot to add the AMSDOS header to it when transferring it from my PC.That did the trick. I redid my .dsk with headers on on winape, and it seems to be working now.
Every time I've had problems flashing a ROM file to my X-MEM it's because I forgot to add the AMSDOS header to it when transferring it from my PC.
ROMAN still randomly hangs, but I suppose it's because the software wasn't specifically designed for your board? Can anyone else confirm it doesn't work with them either? Shame, I quite appreciate its user interface (it just needs an editor and a tool to move ROMs now)
Then use ROManager 2.14 (for FutureOS, see my homepage). It work with and without headers. ;)Eh, I thought the default provided tool would have maximum compatibility. Maybe next update.
Also: Could it be the case that your PSU is (too) weak?I doubt it, it's a new PSU from retrocables.es. I got it with their Scart cable: it makes for quite a tangled mess but it has been working fine so far.
Eh, I thought the default provided tool would have maximum compatibility. Maybe next update.
I did consider using ROManager and played with it briefly in emulation, before settling for Roman. iirc some user interface design choices were not to my liking. Would you be interested in some opinions about it?
I doubt it, it's a new PSU from retrocables.es. I got it with their Scart cable: it makes for quite a tangled mess but it has been working fine so far.
316 = 3.16 version (X-MASS, no RAM Drive)
FR = AZERTY keyboard layout
32 = 32 ROM support
Ram drive would be important to transfert data from Disc to X-mass. I mean full copy Disc, of course...Use the RAM. :-\
Not actually, because they use the same system memory space. So it is a big work to rewrite all.[size=78%] [/size]
The X-MASS is as fast as the RAM for the drive usage, so it is actualy not justified to do it.
FW316 is a minor update. You can continue to use the FW315 with the RAM Drive for CP/M.That sure is well with subdirectories.[emoji6] To install the new firmware 3.16 on a real cpc, how can I do it?
But sure, it will be great to be able to use the X-MASS with folders too.
The ROM 7 is not altered by the X-MEM device. The Firmware is used instead.
You must set the bit6 to 1 for writing the Lower ROM (&47) and ROM 0 (&40).
|FLASH,"FW316ES32.ROM", 71 (for spanish keyboard)
|FLASH,"FW316EXP.ROM", 1 (update the exp rom)
But sure, I will see to update the install tool (it does the same with CALL instead of RSX)
C'est normal ce ",71" comme emplacement de la ROM ?
hello Toto, i want to buy a memory expansion for my cpc like xmem BUT i already have the m4 wifi board WITH EDGE connector!
is possible a converter edge to mother x4 board?
:picard2: :doh:
Hey!
May be your "464/6128" switch solder need to be redo? (forcing the 6128 as a 464 work but is not a solution)
Please, send me the both side pictures by mail, so I will be able to take a look. ;)
I'm pretty sure the solder was ok, but I've redone the switches just in case. Email sent.
I've checked my edge connector and it looked pretty bad, so I cleaned it with some alcohol and that seems to have improved the situation and can now boot with the switch on 6128. I'm still seeing a strange things accessing drive B when booted from the X-MEM. I'll play more and see if I can work out whats going on
Any chance that you have ParaDOS installed?
Bryce.
Yep, in Slot 6
As far as I know, drive B: acts differently when ParaDOS is enabled.
Bryce.
@opticpow (http://www.cpcwiki.eu/forum/index.php?action=profile;u=1075)
Parados Version 1.2 Modifications.
So that the Drive B defaults to 40 Track Single sided.
and then you can use Parados to make adjustments to the drive setup.
To make the “B” drive default to 40 Track Single sided.
Modify the byte at &3ffe from &03 to &00 (drive B).
and alter the Checksum Byte at &3fff from &E5 to &E2
Good luck Ray
@opticpow (http://www.cpcwiki.eu/forum/index.php?action=profile;u=1075)
Here is a copy of the Rom that i use, it will save you having to patch a rom.
I have renamed it to ParDV2m.rom to save confusion.
Good luck Ray
Try pressing esc while you boot the system for skip the ROMs initialization
http://www.centpourcent.net/uploads/2/2/9/8/22986686/getstart.txt (http://www.centpourcent.net/uploads/2/2/9/8/22986686/getstart.txt)
Enviado desde mi iPad utilizando Tapatalk
The Bad Command is because there is a bug in the Expansion rom for the RamDisc. There is a fixed version which TotO provided to me in this thread somewhere. OR if you rerun the install turning off the RamDisc until this new EXT rom is included on the next disc image release then this also fixes it...
On Second thoughts I am sure the guys will not mind me uploading a DSK copy of my XMEM disc that has the fixed EXT rom included. You only need to replace side 1 but both sides are included purly for completeness.
Craig
For information, the X-MEM 512K RAM IC should be replaced with the M48Z512 or M48T512 IC.Happy New Year .
?? Ram Drive ??The RAM Drive already exist (CP/M, FW3.15, some softwares). That allow to not lost its content when your turn off the CPC.
?? RTC ??
Will there be some software support ???
About the RTC, it is really easy as you just have to write or read 8bytes to do it into your own programs.Sounds interesting, I will have a look at the specs. So for accessing the RTC you just do
Sounds interesting, I will have a look at the specs. So for accessing the RTC you just doExactly.
OUT #7F00,#FF and read/write bytes #7ff8-#7fff ?
I have ordered one (M48Z512) For about $6.00 Australian to use as a test.Nice deal for the NVRAM version. (no RTC)
Looks like it could be the culprit. Removed ParaDOS and I can CAT drive B without screen issues.
Dam, using ParaDOS with my 3.5 drive was my main use case :picard:
Wayne
Just to understand correctly, what is rtc ? What CAN we do with it ?
Thanks for explanations.
[quote author=zhulien link=topic=9292.msg139197#msg139197 date=1483670096]
Perhaps you can try the super.rom and modified amsdos80.rom?
Hi Zhulien
do you have a link for the super.rom and modified amsdos80.rom?
Thanks Ray
So to eradicate this bug, you just had to Reset bank by putting #c0 to port #7f before to connect Asic i/o page, am i right ?
Asic Off
ld hl,#4000
ld bc,#7FC4
out (c),c
ld (hl),c
Asic On
ld (hl),l
Asic Off
ld a,(hl)
or a
jp z,ExpansionKOLate to the party: Does anyone know how to order an X-MEM board these days? The original link doesn't seem to work anymore (looks like a blank site).Hi llopis, see in
Yep, in Slot 6AMSDOS/PARADOS v1.2 is usually Slot 7?
AMSDOS/PARADOS v1.2 is usually Slot 7?Often.
A litle update for the X-MEM PCB:
- add HACK pins (boot rom switch) for deported usage
- add BRST pins (reset button) for deported usage
Will allow peoples to improve the internal CPC intergration or HACKIT feature.
Hi Ray!
The BRST pins (bus reset) are just the same as the MotherX4 reset signal took from the bus to deport it using a 2-wire cable with button.
The HACK pins (hackit) are just the same as the BOOT sliding switch (CPC/ROM) from the X-MEM to deport it using a 2-wire cable with switch.
Those allows peoples using the X-MEM as "Siren Hackit" or embedded into a CPC to have easy access to the features.
It is already possible on the previous versions by soldering wires from the PCB. (require to remove the sliding switch to operate)
Just a commodity for peoples asking me that for this usage.Thanks,TotO.