Updates / new features:
- Bugs killed (guess I got em all, Thanks to SyX!!!)
- Edit ROM option (FutureOS only, using the machine monitors EDIT function)
- Protect Flash option (the opposite of Init. Flash). It renders the Flash unwriteable by ROManager
- Init Flash option (allows it initialize and deprotect a new 512 KB Flash chip)
- Reset CPC option (for a quick reset, to check in the new ROMs feel well)
- Small Spy-OS which needs an Ethernet card to work (perfectly to rip Cartridges)
Any further suggestions? Let me know! Else just be patient for a while :-)
Good stuff, mate. Thanks!
It probably does not need much else, but I previously posted some "nice to have's" (well for me anyway) .
A simple "List ROMs" Option.
An option to Load a range of ROMs eg Load positions 20-23 for those apps the occupy more than one position.
An option to clear a range of ROMs eg clear positions 20-23 for those apps the occupy more than one position.
This would also allow the user to clear all ROMs if required 0-31 (automatically excluding ROMs 0 & 7).
Cheers,
Shane
There will probably be further changes coming later. I also pointed out to TFM the fact that having the "Init Flash" feature on the FOS version is a chicken and egg problem: If you have FOS running, then your Flash IC has already been initialised, so Init Flash only make sense on the BASIC disk version. Both the ROM version and FOS version only run if you already have a working initialised Flash in the MegaFlash.
Bryce.
Quote from: Bryce on 14:31, 05 March 12
There will probably be further changes coming later. I also pointed out to TFM the fact that having the "Init Flash" feature on the FOS version is a chicken and egg problem: If you have FOS running, then your Flash IC has already been initialised, so Init Flash only make sense on the BASIC disk version. Both the ROM version and FOS version only run if you already have a working initialised Flash in the MegaFlash.
Bryce.
That's surely right. But as I explained before I added this function to the FutureOS version first, because I needs it to be tested first. Later on I can make it common (all versions). I mean you built the basement first, then the 1st level ;) Actually I asked you a very looooooooooooooooong time ago to do the test. And - sorry - until I get 'green light' from you I can't go any further. This must be done step by step, else we would end up with software that leaves the quality control to the user. And I don't like that. :) If the function works flawless in the FutureOS version, then I will integrate it in all the other versions (ok, maybe not the 464, depends on needed space). :) :) :)
@00WRex: These are good ideas, maybe not easy AND quick to implement. I'll think about it, but choosing a region is always more 'ask user for data' intense. I'll hopefully find a solution, if not now, then soon :) :) :)
Great week to all of you!!!
??? How can I test it? It's impossible to have FOS running AND have an un-initialised Flash connected at the same time. :o
Bryce.
Quote from: 00WReX on 14:21, 05 March 12An option to Load a range of ROMs eg Load positions 20-23 for those apps the occupy more than one position.
An option to clear a range of ROMs eg clear positions 20-23 for those apps the occupy more than one position.
This would also allow the user to clear all ROMs if required 0-31 (automatically excluding ROMs 0 & 7).
QuoteThese are good ideas, maybe not easy AND quick to implement. I'll think about it, but choosing a region is always more 'ask user for data' intense. I'll hopefully find a solution, if not now, then soon (http://www.cpcwiki.eu/forum/Smileys/SoLoSMiLeYS1/smiley.gif) (http://www.cpcwiki.eu/forum/Smileys/SoLoSMiLeYS1/smiley.gif) (http://www.cpcwiki.eu/forum/Smileys/SoLoSMiLeYS1/smiley.gif)
This remember me the REBOOT command from BonnyDOS: it lets you reboot the system only with the roms which number is indicated as a parameter; i.e: REBOOT,0,6,15 restarts the system with the ROMs 0, 6 and 15 (but without AMSDOS ROM 7). This is a useful way to temporally change the system configuration without parking/uninstalling ROMs :)
Quote from: Bryce on 16:36, 05 March 12
??? How can I test it? It's impossible to have FOS running AND have an un-initialised Flash connected at the same time. :o
Bryce.
As explained in my email :) :
- Install FutureOS to your MegaFlash and all other ROMs (so basicly what you have right now).
- Get the Flash chip out and put it into your Flash-burner connected to your PC
- Activate the Software-Data-Protection
- Move Flash back from Flash-burner at PC to the MegaFlash connected to the CPC
- Now start ROManager 1.44 (DSK you got from me) and use Init Flash option
- Now test if you can erase or copy a ROM (or whatever)
That should be doable :) :) :)
Eh ok, you do realise that that's a situation that can only exist on my MegaFlash, not on anyone elses? Which is why I questioned the fact that the Init is on the FOS version at all.
Bryce.
Quote from: MiguelSky on 17:00, 05 March 12
This remember me the REBOOT command from BonnyDOS: it lets you reboot the system only with the roms which number is indicated as a parameter; i.e: REBOOT,0,6,15 restarts the system with the ROMs 0, 6 and 15 (but without AMSDOS ROM 7). This is a useful way to temporally change the system configuration without parking/uninstalling ROMs :)
That sound like a clone of the !ROMON RSX command of of XDDOS. Also MAXAM of PROWORT, UTOPIA have RSX commands like ROMOFF or ROMON. Also HELP or HELP,romnumber is appreciated :-)))
Quote from: Bryce on 20:04, 05 March 12
Eh ok, you do realise that that's a situation that can only exist on my MegaFlash, not on anyone elses? Which is why I questioned the fact that the Init is on the FOS version at all.
Bryce.
Dear Bryce! I just please you to test if the routine works or not. I told/explained several times that I have intergrated it
for testing purposes in the FutureOS version of the ROManager 1.44. It does not matter if anyone, anyhow, or ever will use the FutureOS version to ever use the function. Just read what I wrote before (and before... ;-)))
However, the test has to be conducted in that concrete context. The reason for this it that in this environment there are no disturbing events (like in the AMSDOS context f.e.). I can't expain all my source here, but it's provided on disc and shall speakt for itself.
We're discussing this now since weeks, we can discuss it for months more. But as long as I don't know if the function per se works, I can't move on in development.
I will test it as you wish. It's just 10 times more work for me and at the moment, time isn't something I have a lot of. It means having to install FOS (not normally installed on my MegaFlash), then dismantle my MegaFlash to remove the Flash (it's in a case). Then setup my burner, set the bits in the flash and put everything back together. I'm sure you have your reasons for making an FOS version, it just seems like a very complicated way for me, especially when the feature isn't any use to anyone else in this version and I could test the BASIC version in just a few minutes. But whatever...
I will try to get the test done sometime late next week.
Bryce.
If you are building some more megaflash units, could you use one of those?
I could but I literally only build them as they are ordered. Even the one in the LowerROM photo is already on its way to the person who ordered it. So I only have my own one here at the moment and would need to order the parts for a new one, because no-one has ordered one.
Bryce.
Quote from: Bryce on 20:44, 05 March 12
I will test it as you wish. It's just 10 times more work for me and at the moment, time isn't something I have a lot of.
Sure, but for you it's one hour of work. For me it's a week to transfer all that stuff/text/code from the FutureOS verson into to the Amsdos version. The ROManager is encoded in Z80 source, not in BASIC. That makes it harder. Further I have to deal with several languages. That sums up to a shocking amount of time. One week is not too much for that.
And there is no need to bring all that stuff/functions/options into the AMSDOS version, if it doesn't work on the CPC at all. (We don't know if it works, we only assume it could work).
And if I would start up with the Amsdos version, and it will not work under Amsdos, then it would mean nothing, because there is much more interacting in this case. So more toubles... Therefore we need the first test under FutureOS (where I feel at home and know exactly what happens. So debugging is way more easy).
So thanks a lot for your help, really appreciate your help!!!
I spare you usually from testing whenever possible. But this time... ... ... you know ;-)
Quote from: Bryce on 20:44, 05 March 12
It means having to install FOS (not normally installed on my MegaFlash)...
That's done automaticly. The installer does it all. :-)))
But don't beg for understanding for not using FutureOS *hehehehe*
It does neiter interfere with other ROMs, nor does it steal RAM, so there is no reason to not have it in the MegaFlash.
If you like I can even make you a vesion, that sets ROM numbers, screen MODE and colors in a way you like (where are the smily symbols if I need them???) :-)))
I knew the "I don't usually have FOS installed" comment would get you annoyed :D I actually have the FOS installer on my HxC, but I have been testing so many ROMs that I removed it to test other things.
Bryce.
We need the 8 MB ROM-Box *hahahaha*. *Duck und weg*
For English speakers: "Duck und weg" means you catch a duck on the sidewalk, so you have always something to eat. ... maybe I'm wrong :-DDD
Ok, Protect Flash option added. So the Software Data Protection (SDP) can now be switched ON or OFF. More easy for Bryce and more fun in playing with the Flash chip.
Oh, btw. Did you guys know that all Flash Chips have a Manufacturer ID and a picture of the Manufacturers 21 years old daughter?
Cool! Is the new version in my Inbox?? :)
I was aware of the Manufacturers ID (there's a few other things such as part No. stored there too) but I didn't know that the daughter picture is there, I need to check those ICs again :D
Bryce.
Do I need a microscope?
No just type - Load "Manufactures Daughter.bin", &C000 and you can view it in Mode 2 :)
Bryce.
CRTC-specific?
No, but don't use LCD screens. Because it needs the hardware antializing feature of the original CPC monitor. Now.... only if Bryce is ok with the release of the GFX I can post that here. Else we have to wait until the manufacturer will create another daughter and grow her up - which can take some time ;-)
Hello dear users of the MegaFlash!
I would need your help, else I'm unable to finish Ver. 1.44. But you should have a Flash-Burner, just in case something goes wrong.
Your job would be to test the "Prot. Flash" option.
Please answer me here!!!
Your help will be greatly appreciated!!!
TFM
Sorry TFM, i haven't a flash burner for helping with these tests.
Quote from: SyX on 12:03, 06 April 12
Sorry TFM, i haven't a flash burner for helping with these tests.
No problem. It's about the "Init. Flash" and "Protect Flash" options. Bryce has good reasons to think that this functions can never ever be used with the CPC. However since I tried to implement them in Ver. 1.44 (only FutureOS up to now), I really would like somebody to test it. However, I will be able to do it by myself in my holiday in Germany (beginning at Mai 18th).
Not too many I would guess... :(
The ROManager archive has been updated: 1.44 is not final, but you may find some nice help texts now. Also debugging has been done. And you can select your language at startup (using "-RMA-LNG" as start file.
The ROManager 1.44 (FutureOS) (WIP)[nb]Now - since it is working - I can also make the corresponding verson for BASIC[/nb] can now activate and deactivate the Software-Data-Protection (SDP) of a Flash Chip.
This means: You can use any[nb]Any means still the same type of chip[/nb] new Flash Chip for the MegaFlash, because the SDP can be deactivated.
Quote from: TFM/FS on 16:48, 05 June 12
The ROManager 1.44 (FutureOS) (WIP)[nb]Now - since it is working - I can also make the corresponding verson for BASIC[/nb] can now activate and deactivate the Software-Data-Protection (SDP) of a Flash Chip.
This means: You can use any[nb]Any means still the same type of chip[/nb] new Flash Chip for the MegaFlash, because the SDP can be deactivated.
Can you explain this a bit more? I understand I can now change chips, but why couldn't I before?
Hi!
Well, if you get a MegaFlash (MF) from Bryce then you can use it in the way you know. Bryce did deactivate the so called SDP[nb]see before[/nb] of the Flash, and so the Flash can be written.
Now, if you get a new Flash chip from the factory then the SDP is active. This means that no data can be written to the Flash, it behaves like a ROM.
If you get a new Flash chip for your MF (for which reasons ever) or if you decide to built up a MF by yourself then you must deactivate the SDP, else you can't use the Flash chip to write on it.
To deactivate (or activate) the SDP you have to send a byte array (a code) to specified addressed of the Flash.
Hope it's a bit more clear now, don't hesistate to ask if not.
Quote from: Gryzor on 08:27, 07 June 12
Can you explain this a bit more? I understand I can now change chips, but why couldn't I before?
The flash chip as shipped from the manufacturer has the software protection enabled. I pressume any MegaFlash devices from Bryce have the software protection disabled. So with the older Flash software and a new flash chip, it wouldn't send the appropriate disable commands to the chip, and nothing could be written to the chip, unless you put the chip in an eprom programmer and disabled the software protection.
If the flash software now detects the software protection, and disables it before programming a rom, you could put a new flash chip in your megaflash.
I have a home built Flash based romcard which goes a bit further and identifies the the chip and picks the appropriate programming alogrythm. It currently suppports the W29c020 and 39sf020. It should be fairly easy to modify to support xxx040 chips, should just be different page sizes for programming or sector erase.
Does the MegaFlash software detect the end of write using toggle bit, data polling, or just a fixed timeout?
The Software doesn't detect whether the SDP is turned on or not, but the new software has a command to turn it off if needed (when you insert a new IC) otherwise it can only work with ICs where the protection is turned off.
Regarding the end of page delay, it just uses a fixed delay, because otherwise you'd need to read the IC, which would require switching the write switch. Pretty pointless when the delay is only 11ms anyway. So it waits the 11ms and then starts to write the next page of data.
Do you have a link to your device? What computer does it work on?
Bryce.
Quote from: Bryce on 22:32, 07 June 12
Do you have a link to your device? What computer does it work on?
It's for the CPC. There is a pic on the RCM forums, but you need to be a member to view it. (pic hopefully attached here)
It uses D6 to enable the write support, so roms 0-15 are read only, but the software (still needs some work) selects roms 64-79 to enable write support, with Software protection enabled, the chance of accidental overwrite are minimal.
Thanks for the replies, guys, I'm right on track in my "learn something new every day" target :)
IanS, thanks and welcome!!
"Nearly done" updates uploaded... (MF, SF2, both OS).
Hi TFM,
just wondering if it was possible to produce a ROM version of the latest ROManager (or is it now too big for one ROM ?).
I have had v1.35 on my Megaflash since day one and find it really handy in ROM form...v1.44 would also be nice as I understand you fixed / tidied up a few things.
Cheers,
Shane
Quote from: 00WReX on 08:35, 15 October 12
Hi TFM,
just wondering if it was possible to produce a ROM version of the latest ROManager (or is it now too big for one ROM ?).
I have had v1.35 on my Megaflash since day one and find it really handy in ROM form...v1.44 would also be nice as I understand you fixed / tidied up a few things.
Cheers,
Shane
Hi! Well, yes... I'm still not completely happy with the ease of usage, but you are right. I'll care about a ROM version ASAP. Means after work if it is not too late. Thanks for the hint, I already forgot about it.
For 2 hours I tried to press all in one ROM, it fits. But for some reason it makes problems. Maybe the compression or ????? I try to find the problem...
So sorry, no ROM version right now. But 1.35 should work though.
Some time more... and it works.....
Now there is the release of the ROManager 1.44 on Disc and ROM and with extra features under FutureOS.
Get it at: FutureOS - The revolutionary UltraOS for the CPC6128 and CPCPlus (http://www.futureos.de)
Constructive critics is always welcome :)
Thanks TFM, much appreciated.
Already got it on the MegaFlash and moved a few ROMs around...works like a charm :D
Cheers,
Shane
My pleasure, sir.
Glad it works now. Had to delete some REMarks in the loader to fit it all in one ROM. But CPCT can do wonders :)