Hi Guys,
I just found ROMAN v2 on cpc-power
http://cpc-power.com/index.php?page=detail&num=10969 (http://cpc-power.com/index.php?page=detail&num=10969)
I have tested it on the Symbiface and *REALLY* like it :) however it seems to not like my SST chipped x-mem. I managed to flash itself, and will backup as many roms as I want. but it does not seem to want to flash anything else.
Is this meant to work, and if not, is there anyway it can be patched to work on an X-Mem with an SST chip?
Craig
Quote from: CraigsBar on 23:29, 20 September 14
...snip... however it seems to not like my SST chipped x-mem. I managed to flash itself, and will backup as many roms as I want. but it does not seem to want to flash anything else.
It only flashes itself to the X-MEM? Sounds like a virus. :laugh:
Quote from: CraigsBar on 23:29, 20 September 14Is this meant to work, and if not, is there anyway it can be patched to work on an X-Mem with an SST chip?
You can use the new ROManager for Flashing the X-MEM with SST chip. Download here:
http://futureos.cpc-live.com/files/ROManager_1.8.zip (http://futureos.cpc-live.com/files/ROManager_1.8.zip)
2.0 is not newer that 1.8 ?
Quote from: radu14m on 06:22, 21 September 14
2.0 is not newer that 1.8 ?
No it's not, because we talk about romam 2.0 and ROManager 1.8. Just compare them and you well see. 8)
I am using Roman 2.0 with X-Mem and it works fine. Just set switch No#2 to Boot Mode = CPC and it should work. It is not working if you set the switch to XMem Boot. I don't know why, you should ask Nilquader for that, cause he did 2.0
If you need to flash into XMem Mode, i would try TFM Software, it should work fine.
Regards
Tom
Ahh, I did not try without fw 3.15. Will test that tonight.
Quote from: Pentagon on 07:53, 23 September 14I don't know why, you should ask Nilquader for that, cause he did 2.0
Probably because the firmware interruptions are not disabled.
So, the CPC can't access it while the board is programmed. The result is a crash with the BOOT mode.
Quote from: TotO on 09:33, 23 September 14
Probably because the firmware interruptions are not disabled.
So, the CPC can't access it while the board is programmed. The result is a crash with the BOOT mode.
it did flash itself correctly under fw 3.15 so it must be possible to fix. Under amsdos it is the best Rom based flashtool I've found. I do like your "flasher" too, but being disc based means I am forever looking for the floppy lol. Any chance of a Rom version of it?
Quote from: CraigsBar on 10:11, 23 September 14I do like your "flasher" too, but being disc based means I am forever looking for the floppy lol. Any chance of a Rom version of it?
A X-MEM tool in ROM version will be available soon. ;)
This i like the sound of. :-)
Great news TotO !!!
Quote from: CraigsBar on 10:11, 23 September 14I do like your "flasher" too, but being disc based means I am forever looking for the floppy lol. Any chance of a Rom version of it?
And if you use FW315.ROM and FW315EXP.ROM, you can use the FLASH rsx:
|FLASH,&address,rom_number
|FLASH,"filename",rom_number
Sure, the FLASH RSX is the best way for flashing the X-MEM you FW3.15 users. :)
I hope that many peoples use them.
Quote from: TotO on 18:35, 23 September 14
Sure, the FLASH RSX is the best way for flashing the X-MEM you FW3.15 users. :)
I hope that many peoples use them.
Yes I can, and Yes I do.... BUT.... even for flashing 1 rom that means I have to |help first to establsh which slots are free, If I want to then blank some slots so that all roms for a multi rom game or whatever are together then I need flasher to erase the slots. and then probably |help again to flash what I want, where I want.
On a single Drive system that is a pain.. lots of swapping discs between my X-Mem disc and the Rom Collection disks etc....
It would be much quicker to |flasher / |roman / |whatever do all the housekeeping tasks then reboot.
Flasher is great (But not currently on ROM) but I really like the interface for ROMAN 2 and that is on rom, it just does not play nice with FW 3.15
I guess these teething probelms will all be resolved in the fullness of time, but it's only gonna happen if people using it report them ;)
Craig
Quote from: Pentagon on 07:53, 23 September 14
I am using Roman 2.0 with X-Mem and it works fine. Just set switch No#2 to Boot Mode = CPC and it should work. It is not working if you set the switch to XMem Boot. I don't know why, you should ask Nilquader for that, cause he did 2.0
If you need to flash into XMem Mode, i would try TFM Software, it should work fine.
Regards
Tom
You probably got one from the first X-MEM batch, they have the Winbond Flash. Later versions use the SST Flash, since it's getting harder and harder to get the Winbond Flash.
BTW: ROManager 1.87 released:
http://futureos.cpc-live.com/files/ROManager_1.87.zip (http://futureos.cpc-live.com/files/ROManager_1.87.zip)
CraigsBar, the INFO and FLASH RSXs are in ROM. Why using floppy is a pain? :-\
Turning ON your CPC.
|INFO, give you informations about the installed and free ROMs. (and the RSX commands for each ROM)
|FLASH, program the wished ROM with the file or the memory area. No reboot is needed.
Last but not least, they can be used on your BASIC program for doing custom batch install... What else? :D
Quote from: TotO on 10:40, 24 September 14
CraigsBar, the INFO and FLASH RSXs are in ROM. Why using floppy is a pain? :-\
Turning ON your CPC.
|INFO, give you informations about the installed and free ROMs. (and the RSX commands for each ROM)
|FLASH, program the wished ROM with the file or the memory area. No reboot is needed.
Last but not least, they can be used on your BASIC program for doing custom batch install... What else? :D
all those actions provided in a nice gui. Akin to your flasher app, or roman2 or rommanager1.8.
Once Rom manager for amsdos is xmem friendly (it wasn't last time I checked) or roman2 works with fw 3.15 or a Rom version of flasher is available I won't need the disc anymore.
You will always need a disc - just to provide the ROM image you would like to burn.
Quote from: TFM on 15:56, 24 September 14
You will always need a disc - just to provide the ROM image you would like to burn.
Yes, one. romdos formatted with lots of Rom images on it. Or none.... Minibooster transfer the file from my Mac to the silicon disc and flash from there. However, is a working flashing/erasing general Rom image housekeeping app with a gui too much to ask for? Several exist.... But of those, the one that comes on Rom image itself does not play nice with fw 3.15. Just saying. Think I should forget I mentioned it.
Quote from: CraigsBar on 16:13, 24 September 14
Yes, one. romdos formatted with lots of Rom images on it.
Yes, right. That's the way I do it too. Have ROManager on one disc (0.7 MB Vortex format) and on disc there are my about fourty favorite ROMs. All I need it one disc, and I don't waste a ROM slot for the ROM management software (ok, waste it s bad word since there is really space enough).
Quote from: CraigsBar on 16:13, 24 September 14
Or none.... Minibooster transfer the file from my Mac to the silicon disc and flash from there.
:o OMH! That would be way to complicated to me. And I don't want to need to fire up the PC just to be able to burn a ROM on CPC. If you need your PC, then get the Flash to your PC Flasher and you can have all the comfort you want.
Quote from: CraigsBar on 16:13, 24 September 14
However, is a working flashing/erasing general Rom image housekeeping app with a gui too much to ask for? Several exist.... But of those, the one that comes on Rom image itself does not play nice with fw 3.15. Just saying. Think I should forget I mentioned it.
Well, I can only tell you what I think. If I don't like the situation then I change it by myself. That was the reason I made FutureOS.
We all have a different taste, maybe you should make your own ROM flasher?
ROMAN 2 works on the SST-based ROM boxes (Megaflash NG, FlashGordon and the X-MEM) but it is not compatible with the modified firmware inside the lower rom of the X-MEM. So if you want to use ROMAN 2 on the X-MEM, switch back to the original firmware first.
Quote from: Nilquader on 17:07, 24 September 14
ROMAN 2 works on the SST-based ROM boxes (Megaflash NG, FlashGordon and the X-MEM) but it is not compatible with the modified firmware inside the lower rom of the X-MEM. So if you want to use ROMAN 2 on the X-MEM, switch back to the original firmware first.
which was my original question... Can this be "fixed"?
Quote from: Nilquader on 17:07, 24 September 14
ROMAN 2 works on the SST-based ROM boxes (Megaflash NG, FlashGordon and the X-MEM) but it is not compatible with the modified firmware inside the lower rom of the X-MEM. So if you want to use ROMAN 2 on the X-MEM, switch back to the original firmware first.
Do you know what exactly is the problem with FW3.15?
Quote from: TFM on 18:42, 24 September 14
Do you know what exactly is the problem with FW3.15?
I've never analyzed this. I'm not really interested in debugging non-standard firmware configurations. ROMAN 2 is meant to be used on the CPC 464 or 6128 with the default firmware. Maybe you want to try the Megaflash NG RSX software at http://forum.spielquader.de/filebase/index.php/Entry/9-MegaFlash-NG-RSX/
No thanks. I already got something that works like a charm. But thanks for the information. :)
I think that is not related to a custom FW. (but, I should be wrong)
Trying to put a standard FW on the X-MEM for booting with should cause the same problem. (i.e. a 464 with FW3.0 on the X-MEM)
If yes, that means the interrupts are not disabled while writing... Else, help... SyX !!!!!!!! :-\
Quote from: TotO on 20:47, 24 September 14
I think that is not related to a custom FW. (but, I should be wrong)
Trying to put a standard FW on the X-MEM for booting with should cause the same problem. (i.e. a 464 with FW3.0 on the X-MEM)
If yes, that means the interrupts are not disabled while writing... Else, help... SyX !!!!!!!! :-\
Confirmed... using a standarg Basic 1.0 or 1.1 installed on the xmem I get the same issue when booting from the external firmware. so I guess the issue is simply that roman does not play nice with external firmwares. and that would seem to fit TotO's diagnosis.
Quote from: TFM on 16:30, 24 September 14
:o OMH! That would be way to complicated to me. And I don't want to need to fire up the PC just to be able to burn a ROM on CPC. If you need your PC, then get the Flash to your PC Flasher and you can have all the comfort you want.
Well that is not strictly easier, pulling flash chips and popping them into an external programmer sounds like a royal PITA to me, but I guess that is not the point you are making... But whilst we are at it I hardly need to turn the Mac on, it is all but never turned off, and if for some reason I have the Mac Pro off then my Macbook Pro boots in under 8 seconds. hardly a long wait.
Quote from: TFM on 16:30, 24 September 14
Well, I can only tell you what I think. If I don't like the situation then I change it by myself. That was the reason I made FutureOS.
We all have a different taste, maybe you should make your own ROM flasher?
Believe it or not we are not all coders, some of us are "simple users" we help out where we can with bug reports and feature requests. But when it comes down to it we have no skills when it comes to making code changes etc.
Building a cartridge or a case mod I can do, I am even looking forward to making the new Plus carts for Fluff Anniversary release. I know exactly what cases I am going to build. but these things I can do.
craig
Oh well, we all got our strength and abilities. But not everybody in the same field. :) Feedback and feature requests are very welcome.
For example since ROManager 1.4x up to 1.8x I basically added feature requests, like hotkeys for standard functions or pressing a single key to see all ROMs. That's all included now. So thanks to every body who gives critics and feedback. It's appreciated. On the other hand some people (German scene especially) are only good in bitching at others productions, and that's a let down. Here in the Wiki the situation is rather positive and I think also very productive.
But I'm getting off topic...
Quote from: TFM on 00:16, 24 September 14
You probably got one from the first X-MEM batch, they have the Winbond Flash. Later versions use the SST Flash, since it's getting harder and harder to get the Winbond Flash.
Thank you for the hint. I have looked at my X-Mem now and it is a "SST 39F040" Chip in the socket. It is really working fine with Roman 2.0
Regards
Tom
Quote from: TFM on 00:41, 25 September 14For example since ROManager 1.4x up to 1.8x I basically added feature requests, like hotkeys for standard functions or pressing a single key to see all ROMs. That's all included now.
I think that you have mainly improved the way to detect, lock/unlock and program the flash chips.
About the "TotOs X-MEM" text, you should remove my name or replace it by ACME. ;)
Quote from: Pentagon on 08:36, 25 September 14
Thank you for the hint. I have looked at my X-Mem now and it is a "SST 39F040" Chip in the socket. It is really working fine with Roman 2.0
Regards
Tom
using external firmware, or switched to the internal one?
Quote from: CraigsBar on 09:06, 25 September 14
using external firmware, or switched to the internal one?
Hi, i am just using the original internal CPC Firmware and not a customized external. It is working at CPC464 and CPC6128.
Regards
Tom
Quote from: TotO on 20:47, 24 September 14
I think that is not related to a custom FW. (but, I should be wrong)
Trying to put a standard FW on the X-MEM for booting with should cause the same problem. (i.e. a 464 with FW3.0 on the X-MEM)
If yes, that means the interrupts are not disabled while writing... Else, help... SyX !!!!!!!! :-\
Well, as i told in the P&P thread, if somebody asks politely instead of saying is a shit and doesn't work, i could try to discover why fail... but if nobody asks, i can not do anything.
I have taken a fast look (5 minutes) and the bug in ROMAN is because uses the zone in $BE00, exactly the same place used by the FW3.15 for storing the pointers to the 32 roms (one of the few changes to the rom the firmware makes :laugh: :laugh: :laugh: ).
Remember the thread of patching the firmware to use more than 16 roms, because booster was an awful hack, and we decided to put a table for 32 roms in other place and i chosen this place, because is free and before the Amsdos variables in $BE40.
I'm not going to be able to look deeper in a while, because i'm starting my university tests and few work presentations. But at least, there is more problems, it's only to change those address to a free zone and the program should work in FW3.15, if somebody wants a fast patched version, they can go ahead and change all the references to $BExx (xx < $40). And publish a diff or remember to ask permission for releasing this pacthed version.
@SyX I don't think I ever said Shit it does not work, and if this thread caused offence I appologise. Although I don't really see how the 32 rom mods to FW 3.15 can cause this. As detailed in my tests last night, when the external FW on the X-Mem has an un modified 464 or 6128 image the result is the same. ROMAN crashes and fails to program the xmem correctly. Also when I use my old FW 3.14 cartridge in my 6128 plus it works fine, but again not once the xmem is toggled to use the external FW.
It seems that the issue is simply that roman is not happy with an external FW but perfectly fine with an internal one, be that FW original or modified.
Again I appolgise fo any offence I certainly did not mean this to anyone
Craig
@CraigsBar: Don't feel bad, you don't need to apologise, because i was talking about a thread in P&P.
As you have discovered, this change for supporting 32 roms (more exactly for not having memory corruption when more than 16 roms that reserve RAM, as Protext, are used) happened between 3.14 and 3.15. And it's only bad luck that FW and ROMAN chosen to use the same ram zone.
Why did i change the zone? because in the original zone there is only a hole enough for 16 roms (32 bytes) and we need exactly the double, there is not a lot of places with 64 bytes between the ram firmware variables.
Maybe i should think for the FW 3.16, to add a configuration (similar to the RAM disk size) where you can choose between use 16 (in the old zone) or 32 roms.
The other thing is that you can have two different flash chips in a X-Mem, even we could have a third one in a future release (i'm not joking :P). Then the flashing software, as TFM's ROManager makes, check before of flashing for the chip in the board.
Quote from: TotO on 08:51, 25 September 14
I think that you have mainly improved the way to detect, lock/unlock and program the flash chips.
About the "TotOs X-MEM" text, you should remove my name or replace it by ACME. ;)
OK! Will be done for 1.89 ;-)
Quote from: SyX on 17:48, 25 September 14
I have taken a fast look (5 minutes) and the bug in ROMAN is because uses the zone in $BE00, exactly the same place used by the FW3.15 for storing the pointers to the 32 roms (one of the few changes to the rom the firmware makes :laugh: :laugh: :laugh: ).
OMG! Why in the world must a simple tool use that area? There is enough RAM left below &AXXX. Please all coders leave the Firmware area to the firmware!!! >:(
Quote from: SyX on 17:48, 25 September 14
I have taken a fast look (5 minutes) and the bug in ROMAN is because uses the zone in $BE00, exactly the same place used by the FW3.15 for storing the pointers to the 32 roms (one of the few changes to the rom the firmware makes :laugh: :laugh: :laugh: ).
So does ParaDOS for large Drive A format block allocation table since ROMDOS, Ultraform and ParaDOS41 formats require up to 50 bytes. I'm not sure there was anywhere else it could go.
Gentlemen you gotta talk to each other and find the right bytes to make it all running together. ;) :)
Maybe steal a bit of the stack?
Quote from: Executioner on 02:57, 26 September 14
So does ParaDOS for large Drive A format block allocation table since ROMDOS, Ultraform and ParaDOS41 formats require up to 50 bytes. I'm not sure there was anywhere else it could go.
Sure, for rom code, we haven't a lot of places to put data, jajaja.
I'll take another look for places to hide the extra 16 rom pointers for the next version of my firmware hack ;)
Quote from: SyX on 20:50, 26 September 14
Sure, for rom code, we haven't a lot of places to put data, jajaja.
I'll take another look for places to hide the extra 16 rom pointers for the next version of my firmware hack ;)
Would it also be possible to implement the "fix" suggested by @Executioner (http://www.cpcwiki.eu/forum/index.php?action=profile;u=17) and pass a |drive with no parameters on to Parados (or AmsDos) instead of returning an error?
Thanks
Craig.
any ideea why do i get this garbage on the screen ?
(http://i62.tinypic.com/ngawq1.jpg)
Probably the program is going to explode... Check the nice "dynamite" color cursor on the bottom-right of the screen. :o
It look to be ROMAN code that fill the ROM list. Nice "buffer overflow". :-\
The nice "dynamite" color cursor on the bottom-right of the screen is the reflection from the HXC light :)
No explosion :)
anyway, even if roman 2 fail to write the ROM"s, with the HELP RSX command i see that something was written.
what"s this ? ( 0.00 FOREGROUND )
(http://i61.tinypic.com/5nrgg7.jpg)
should i use another ROM utilities ?
Tried also with the FLASH command, same situation. A written ROM file appears in the same way :0.00 FOREGROUND
I suggest you to remove the BOOSTER ROM to see what happening...
You can test with the FLASHER program from the X-MEM floppy to see the ROM list too.
(best, using the EDITOR program to see the ROM content)
it did not help.
i try both method !
Quote from: radu14m on 13:50, 27 September 14
it did not help.
i try both method !
re-run init from the xmem disc to completely wipe it and reinstall perhaps?
yes, i did that.
rescue
init
install.
several times.
Quote from: radu14m on 14:20, 27 September 14
yes, i did that.
rescue
init
install.
several times.
damn. TotO? Corrupted (or pooched) flash chip perhaps. Mine does that exact same thing when I try to flash with Roman from fw3.15 but after a reboot all is happy again.
it"s wierd.
Every ROM file that i try give me that corrupted screen.
There is one exception: only ROMAN.ROM file i'am able to write in all ROM locations :)
(http://i57.tinypic.com/11qjsk9.jpg)
I try a lot of ROM images, no luck.
I test each board before shipping them. All with FW3.1x-EN.
The |HELP command display ROM0=BASIC, ROM1=FWEXP, ROM7=CPM. The others slots are empty.
radu14m, as you can see you are able to program all the slots (I see the extra CPM at ROM8/9 too), so the flash chip should not be defective.
If you got random garbages and strange program behavior, please, clean you expansion connector with 70° alcohol + cotton stabs on both sides, then plug and unplug 3/4 times the edge connector.
After that, run INIT then INSTALL to process again to the X-MEM default configuration.
Start the FLASHER program from the X-MEM floppy and post a screenshot on the X-MEM topic (http://www.cpcwiki.eu/forum/news-events/x-mem-a-new-memory-expansion-for-all-cpc/) to continue the discussion at the good place.
Thank you. :)
Obviously ROMAM is a virus which spreads over all empty ROM slots. :P
Shall I write some anti virus software for the CPC? :laugh:
Quote from: radu14m on 08:11, 27 September 14should i use another ROM utilities ?
Of course, take that here:
http://futureos.cpc-live.com/files/ROManager_1.87.zip (http://futureos.cpc-live.com/files/ROManager_1.87.zip)