Hi there,
New release of the ROManager for the new MegaFlash and the Symbiface in Version 1.34 beta (Disc version). Now everything should be fine.
Will include the ROM versions tomorrow if I find time......... getting tired... Good night!
Have a great CPCing Sunday ;)
Great News!!! :D I will test this week :D
Quote from: SyX on 14:46, 28 August 11
Great News!!! :D I will test this week :D
Thank's a lot! Guess we're entering the final phase ;-)
Ok, now you can get the ROManager for the MegaFlash in Ver 1.34 as ROM version. You still need two ROM places.
Please report any issues :o ;D 8) ;) ;) ;)
And now you can also download a ROManager ROM version for the SF2, here:
www.futureos.de (http://www.futureos.de) (download section)
Well, don't use park/unpark or adapt checksum. There is still a bug (a damn bug from outer space hard to kill). But with the help SyX and others we will get it right!
EDIT: First bug pictures...
The Bug from Outer Space (http://www.youtube.com/watch?v=ti26_5t459g#ws)
Holly frak! Like an ant/bee/grasshoper combo!!!! Ew...
That bug wouldn't fit in a MegaFlash, it must be some other bug :D
Bryce.
Quote from: Bryce on 08:32, 01 September 11
That bug wouldn't fit in a MegaFlash, it must be some other bug :D
Bryce.
That's right. SyX helped me finding it! Currently he is testing Ver. 1.35, which will be released as soon as prooven working reliable. The bug was rather looking like this:
.
Yup, that's a small and fast one. They're the most difficult ones to catch :D Any news on the ROM version making it down to being just one ROM?
Bryce.
The good news are Ver. 1.35 seems to work reliable now ;D
And SyX checked also the ROM version 1.35 with success :-)))
Yes, both versions work really great :D
I only need to test the FutureOS version of ROManager, but if somebody can confirm that it works perfectly, everybody will be very grateful to him ;)
Thanks TFM for your program, the perfect companion for the MegaFlash :D
It wouldn't be there without You!
Feature request! Please add a Reset command to the interface (hopefully with a hotkey); since, I guess, all of us want to use a ROM after installing it, the machine must initialize it, and merely dropping off ROMManager doesn't cut it :D
I added a reset button for the CPC, it's very useful, not only for the MegaFlash, it was very easy to add and it doesn't destroy the sexy look of the CPC :)
Quote from: Gryzor on 06:59, 23 September 11
Feature request! Please add a Reset command to the interface (hopefully with a hotkey); since, I guess, all of us want to use a ROM after installing it, the machine must initialize it, and merely dropping off ROMManager doesn't cut it :D
Hehe, actually I added that point yesterday to my "2DO" list :laugh: And it's a good request!
However, I'm a bit scared to really use a hotkey, because .... well, if you touch it by accident???
BTW: If you use Control-Shift-ESC, the CPC should make a reset. Can you confirm (I know you have to hit ESC two or three times... Well, I can only check on an emulator here).
Quote from: SyX on 08:41, 23 September 11
I added a reset button for the CPC, it's very useful, not only for the MegaFlash, it was very easy to add and it doesn't destroy the sexy look of the CPC :)
Hell yes!!! Games do definitely NEED one :-))) A reset button was the first thing I added to my Plus (internally), when I got it in 1992.
Please update the ROManager for FutureOS! That's very important!
Thanks to the endless testing efforts of SyX the (hopefully last) bug has been killed.
SyX, muchas gracias!!!
Bitteschön!!! :)
It has been a pleasure, you know that i have been very entertained with all the tests during these weeks ;)
Quote from: TFM/FS on 16:30, 23 September 11
BTW: If you use Control-Shift-ESC, the CPC should make a reset. Can you confirm (I know you have to hit ESC two or three times... Well, I can only check on an emulator here).
Actually, it just refreshes the screen...
And by 'hotkey' I meant a key combo, of course :)
Quote from: SyX on 18:56, 23 September 11
Bitteschön!!! :)
It has been a pleasure, you know that i have been very entertained with all the tests during these weeks ;)
Well, tests? Ah yes, some 900 or so :laugh:
Quote from: Gryzor on 19:48, 23 September 11
Actually, it just refreshes the screen...
And by 'hotkey' I meant a key combo, of course :)
Interresting, with an emulator you hold Control & Shift, then you hit ESC twice or three times, then you get your reset. I'll care about it in the next version!
I tried that, it either refreshes or does nothing as a matter of fact!
Quote from: Gryzor on 10:23, 24 September 11
I tried that, it either refreshes or does nothing as a matter of fact!
Oh, well, it works with emulators, and sadly I got no CPC here right now. But I will implement that feature :)
Now you can download the ROManager for the MegaFlash and the Symbiface as single 16 KB ROM. Goto the download section on:
http://www.FutureOS.de (http://www.futureos.de)
Have fun!
Why don't you try to merge all your versions of ROMManager into a single one?
If the way to manage it change (writing stuff)... just display a question to the user at startup, something like :
(M)egaFlash or (S)ymbiface ?
It wouldbe easier for you to manage... and easier for people to catch up new versions.
As far as I know, the MegaFlash version would work on the SymbiFace, just a few milliseconds slower, but the SymbiFace version wouldn't work on the MegaFlash (due to write-delays being required for Flash).
Bryce.
Quote from: norecess on 11:55, 27 September 11
Why don't you try to merge all your versions of ROMManager into a single one?
If the way to manage it change (writing stuff)... just display a question to the user at startup, something like :
(M)egaFlash or (S)ymbiface ?
It wouldbe easier for you to manage... and easier for people to catch up new versions.
That's right, it would be more easy for me. But not for the User. Why bother the user with an additional question? Ok, the software could sense which one is attached. But nobody is using both expansions at the same time. They are not compatible, because both provide ROMs. So one of them will deactivate the other or they collide and crash. I'm fine with two special versions, it's a bit more work but both versions will probably evolve in slightly different ways.
Actually I have six versions (MF, SF for FutureOS, CPC-OS Disc and CPC-OS ROM). It's a bit a work, but why not.
Also people either have the MF or the SF. So it's not a problem for them.
Quote from: Bryce on 12:04, 27 September 11
As far as I know, the MegaFlash version would work on the SymbiFace, just a few milliseconds slower, but the SymbiFace version wouldn't work on the MegaFlash (due to write-delays being required for Flash).
No, the SF2 gets its ROMs programmed at &4000. (The MF as you know at &C000).
However the ROManager for the MF shall be able to program the ROM-RAM-Box and the French RAMcard, but I can't try. Can somebody confirm?
6 versions !? wow..
Pressing M key at startup would not bother me, but this is me.
Ok, also the SF2 version is not ready for download. One ROM (16 KB), that contains the Inicron ROM Booster (ZAQ) and the ROManager. Thank's to all of you for help and support and interrest.
I hope that an friend from Spain who has the SF2 will like this version.
Links (for MegaFlash and SF2):
http://www.colorado-boys-muenchen.de/users/futureos/files/MF_ROManager.zip (http://www.colorado-boys-muenchen.de/users/futureos/files/MF_ROManager.zip)
http://www.colorado-boys-muenchen.de/users/futureos/files/SF_ROManager.zip (http://www.colorado-boys-muenchen.de/users/futureos/files/SF_ROManager.zip)
Good nite!
Next week I'll have some time to test both the MegaFlash and the SF2, but tomorrow starts GameFest and I'll be there with some more friends supporting the retro side of the event ;D
The rom version working fine here :) Only trouble in loading from Hard Drive with BonnyDOS partition (as before, same than disc version). Great job !!
Well, I'm using the standard DISC vectors, therefore most DOS are supposed to be compatible.
Is it possible to set up an CPC emulator with BonnyDOS? (WinApe?) Maybe that way I can check which parts of BD are incompatible. Or does BD require hardware to run? Any experiences?
Bdos is working fine here with RomManager and Harddisc. I dont have any issues. I just got an issue when i start the CPC with active BDOS ROM, but without active harddisc. Then i get an error and a crash with megaflash. The inicron box doesnt crash in that case and i got a message from BDOS "Harddisc not found", Megaflash just crash. Dunno what that issue is, but if you switch on the harddisc that issue is fixed immediatly.
Should work fine then.
Kindly regards
Tom / Pentagon
Interesting. I'll take a look at the hardware of both and see if I can see anything different that could cause that. But they are so similar in function and in how they are decoded, that I really can't think of what could cause that.
Did both devices have exactly the same selection of ROMs saved in the same positions?
Bryce.
Hello Bryce,
yes i did the roms at the same positions like i did in inicron box. So the config is the same. I can start the inicron box now with my cpc but without a plugged harddisc. The CPC give me a message that he didnt found a harddisc.
When i do the same with the megaflash i get a crash and no message from Bdos, my screen turn into another color border and some messy letters. Its still possible to type but sometimes not. So its crashed, when i delete the BDOS Rom then everything is fine again. Thanks a lot for the modding switch you gave me, without that switch i had to remove the poor little flashchip 2000 times. LOL ;-)
So i dont know, whats the problem in that case, but its interesting yes.
If i plug a harddisc to the CPC and then switch on CPC with megaflash, Bdos is starting up fine and everything is running fine and smooth like the inicron box did too. The inicron box can work and startup without running harddisc, Bdos is booting and recognize that its missing, with megaflash its not working without harddisc, just with plugged and ready to go harddisc.
Well i can live and deal with that, but its important to people who like to use Megaflash with BDOS.
There is another thing to explain. People with an Symbiface II, dont need to flash a megaflash with BDOS, cause the Symbiface II have its own ROM Box inside. So just people who are using the first version of CPC IDE or my fixed version of CPC Free IDE, need the megaflash with a flashed BDOS. The Symbiface I, CPC-IDE, CPC-Free IDE doesnt have a built in ROM Box. So im thinking that MiguelSky is using megaflash without SFII, but with an SFI / CPC-IDE, else it doesnt make any sense to flash BDOS inside the megaflash. Nobody would plug a SFII and a Megaflash together at the same port, cause the SFII has its own Rom Box inside.
Please excuse my poor english, i am very sorry.
Kindly Regards
Tom / Pentagon
To me this sounds like a power-surge problem.
BTW: Like I know from Dr. Zed a SF1 never existed. If it does though, then a picture would be interresting.
Quote from: Pentagon on 07:01, 30 September 11So im thinking that MiguelSky is using megaflash without SFII, but with an SFI / CPC-IDE, else it doesnt make any sense to flash BDOS inside the megaflash.
Hi, pentagon :)
No, I'm using a Symbiface2 and I use its own IDE. Well, I'll try to reproduce my matter: I choose Load 1 rom and sign C has the unit from where I want to load; it changes to the screen with the disc directory in the right and show the one in the path I had previously selected (ROM directory, in my drive). Well, the info is bad tabuled due the format of CAT command of BonnyDOS, you know, it shows the type of file, the permissions... but the name of files is yet legible. I introduce then the file name, 0C:MAXAM150.ROM, for example (this rom was copied from the RMA dsk and has a 17kb size, I assume is has his header) bad the red border is show, the beed is sound and the Bad command message is displayed. Sometimes, it hangs the CPC and don't let me continue without restarting the CPC. I though it could be due to the rom position of ROManager as I had it below the BDOS rom in my last message (the TFM message gave me the clue) but now I changed it above it and there is not difference.
Well, my guess is that Bonnydos has a problem either in changing the device or in loading a file. I have to try to simulate the problem. However, since I'm not the coder of it, it's questionable if I can help here.
Are games running with bonnydos?
Yes, a good bunch of them :) I make a dump of the entire NVG by extracting the files from nonprotected dsks to folders. The ones unprotected by XOR don't work anyone. You can see a list of some working games I tried here http://amstradcpc.mforos.com/attachments.php?accion=download&foroid=305097&fileid=1375572&rand=107226 (http://amstradcpc.mforos.com/attachments.php?accion=download&foroid=305097&fileid=1375572&rand=107226)
You asked above about use BDOS in an emu. I tried and it is not possible, none of the emus emulates the HDD in a manner that BDOS can handle it.
Quote from: MiguelSky on 08:29, 03 October 11
You asked above about use BDOS in an emu. I tried and it is not possible, none of the emus emulates the HDD in a manner that BDOS can handle it.
Yes, but does file load / save work from disc?
After thinking about this for a while (what's the difference between games and ROManager?), my guess is that BD can't work with filenames like "0A:filename.ext". In detail I guess it has a problem with the 0A part of it, which selects drive and user.
If this it true, I may could create a work-around.
I will ask in the C64 forum, where the BDOS programmer is usually to be found.... Question posted!
Quote from: TFM/FS on 20:23, 03 October 11
Yes, but does file load / save work from disc?
Do you mean in emu? There is no way in mount the HDD in emus.
QuoteAfter thinking about this for a while (what's the difference between games and ROManager?), my guess is that BD can't work with filenames like "0A:filename.ext". In detail I guess it has a problem with the 0A part of it, which selects drive and user.
If this it true, I may could create a work-around.
I will ask in the C64 forum, where the BDOS programmer is usually to be found.... Question posted!
Hey, from diskette it is working, if this is that you are asking. Respect the 0A: I tried to load without it too without results (I set the drive in the early screen).
Quote from: MiguelSky on 21:15, 03 October 11
Do you mean in emu? There is no way in mount the HDD in emus.
Hey, from diskette it is working, if this is that you are asking. Respect the 0A: I tried to load without it too without results (I set the drive in the early screen).
Sorry, with disc I did mean floppy disc. Just to check the filename functionality.
But the 0A seems not to be the problem, seems to be something hard-disc specific.
Two things:
- It seems I'm not able to solve the problem of bdos and ROManager incompatibility. You should contact the programmer of bdos himself for help. Maybe he can help you. I don't have the bdos, so I can't help.
- I do need somebody who has a MegaFash connected to a CPC 464 and also a CPC 664 for beta testing of the ROManager for 64 KB CPCs. SyX did help me already for long hours with the 128 KB version. Any kind of help in testing is appreciated. Email me to futuresoft at gmx dot de.
Well, you know that i only have a pair of 6128, but i don't mind to test the 464 and 664 version, if you promise don't page the ram, jejejeje.
Promised! ;)
Good news!
Here it is, the ROManager 64K for CPC 464 and 664. Download at www.futureos.de (http://www.futureos.de) (download section).
Good nite now :-) ZzzzzzzzzzzzzzzzzzzzZZZZZZ!
THX to SyX for testing :D D D
Je je je, always a pleasure my friend ;)
Now, I'm pretty much done with all the ROManager stuff. If ever there will be a new release, then it will be not before 1.44. However this can take a looong time. I intend to continue some of my bigger projects now.
It's an splendid work and you should be proud of it ;)
But now it's time to follow with your other projects, ¡¡¡Animo!!! :D
Can I just ask what changes were required to make it 464/664 compatible?
I think ROManager works pretty well as it is. I think it mostly needs some UI changes, like a reset option and dialog boxes where text doesn't flow outside the box... stuff like that :)
Quote from: redbox on 07:12, 09 October 11
Can I just ask what changes were required to make it 464/664 compatible?
Well, basically it was a conversion from an 128 KB version to an 64 KB version.
- The two ROMs are buffered in the first 64 KB now, not in E-RAM
- The multi-language-interface has been deleted
- Option, which just show informations have been deleted, just read the doc file now ,-)
- Using a bit more CPC-OS API functions than before (which doesn't make it more quick :-()
- However, it may be wise to use a command like !ROMON(,)7 before usage, in case HIMEM is smaller than &A400 roughly.
Quote from: Gryzor on 11:00, 09 October 11
I think ROManager works pretty well as it is. I think it mostly needs some UI changes, like a reset option and dialog boxes where text doesn't flow outside the box... stuff like that :)
I know what you mean, but you must know that ROManager for BASIC is basically an hybrid program between CBM (which was developped for FutureOS), some parts of FutureOS and some adaptions, that make in running under the native CPC-OS.
If I would have made a clean rewrite for the CPC-OS then this would take me month longer (because my spare time is very scarce) and the result would work way slower.
So the hybrid solution seems to be ok for me. Having said that the hybrid solution will not make the size of the program smaller.
Here a trick for entering file names: Just press Control+TAB first, then you switch to "overwrite" mode, and the text will not flow out of the box. In additon: You don't have to delete charactes that way.
(I can't activate the overwrite mode automaticly, because this is the BASIC string editor. I could use the one of FutureOS, but neither I have the intention to port half of my OS into a program, nor it would just cost a coupe of bytes. In contrast it's rather large).
Thanks TFM.
Was just wondering as I'm writing some ROM stuff and want to make it both 6128 and 464 compatible.
Quote from: redbox on 21:39, 09 October 11
Thanks TFM.
Was just wondering as I'm writing some ROM stuff and want to make it both 6128 and 464 compatible.
Well, if you look at the beginning of my ROManager source code then you see, there is just one CPC-OS call (the editor IIRC) that had to be adapted.
No need to mention that anybody can use my source as long as it is mentioned in the final program.
In case there are questions, just let me know.
Ctrl+TAB: nice trick. You should actually put this as a tip in the program interface!
Quote from: Gryzor on 07:28, 10 October 11
Ctrl+TAB: nice trick. You should actually put this as a tip in the program interface!
Ok, for the next version :-)
Any wishes for the next update left? Request here!
Keyboard shortcuts?
Like, L3W4 would load the fourth file and write it into the 4 slot... or something like that.
Wouldn't that be L4W4? :D
Bryce.
I will list all I can think of at the moment...(nice to have's)...
1)Grey out any options not available in BASIC version or a BASIC only version.
Under "File"
2)An option to Load a range of ROMs eg Load positions 20-23 for those apps the occupy
more than one position.
3)A "Reset CPC" option to initialise ROM/s.
Under "ROM management"
4)A SIMPLE "List ROMs" Option.
5)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).
Under "Process"
6)An option to "Turn Off" the Flash Write Protection in the event a new Flash chip is
inserted (May never be required, but who knows 10 years down the track).
Cheers,
Shane
Thanks' for all the input!!! Ok, the next release will take longer now ;-) I see what I can do :-)))
When you replace the Flash, it needs to be initialised, ie: The write protection needs to be turned off. It would be nice if the software could do this too. It's only a short (4 byte) sequence that needs to be sent to the Flash.
Bryce.
Quote from: Bryce on 13:29, 30 January 12
When you replace the Flash, it needs to be initialised, ie: The write protection needs to be turned off. It would be nice if the software could do this too. It's only a short (4 byte) sequence that needs to be sent to the Flash.
Bryce.
Great! I just wanted to ask you if the CPC is capable of doing it!
Please let me know how to do it (PM or here). As soon as I understand how to initialize the Flash I will add this function to the software like you requested.
Hi there,
In a German forum I did read that the ROManager 1.34 had problems to write ROMs to the SF2. Sorrowly I life in the USA and can not check that by myself here, since I have no CPC here - and no SF2.
Can somebody please tell me if ROManager 1.34 work with the SF2? If not, please describe the error. If the "Load ROM" function does not work, please send me a dump of the 'burned' ROM.
Any kind of help is strongly appreciated! Your help will help us to get better software :) :) :)
Download:
http://www.colorado-boys-muenchen.de/users/futureos/files/SF_ROManager.zip (http://www.colorado-boys-muenchen.de/users/futureos/files/SF_ROManager.zip)
Hi there,
Today I uploaded an small update of the ROManager for BASIC to the download section of FutureOS - The revolutionary UltraOS for the CPC6128 and CPCPlus (http://www.futureos.de)
Now also the BASIC version can read ROMs which are saved as 16 KB ASCII files.
Well, I could do only few testing, so please report problems here - or let me know if it works.
Thanks to SyX (like usually ;-)) for his help,
TFM
Oh, and I forgot to add the 464 version yesterday. Now added :-D
Update for the SF2 added. Happy ASCII ROM reading :)
Well maybe there will be a version for the new FlashGordon too...
Flash Gordon Originaltrailer - YouTube (http://www.youtube.com/watch?v=AMEc_MiLmgw)
After a week of testing I have to thank Toms and Bübchen for testing the FlashGordon version of the ROManager. And - unexpectedly - it seems to work from the beginning :laugh:
Now I only have the BASIC version for you, since I'm very busy in the lab. [nb]The new zombi cell line suxx greatly.[/nb]
Direct download here:
http://www.colorado-boys-muenchen.de/users/futureos/files/MF_ROManager.zip (http://www.colorado-boys-muenchen.de/users/futureos/files/MF_ROManager.zip)
Read the read-me to find out which DSK is the right one. Good luck with that :P
Are you sure they've tested it properly? The ROManager can write to it no problem, but the Flash chip has 64K pages, so for example, writing to ROM 3 would seem to work if the Flash is empty otherwise (the new ROM would be successfully written), but it would also delete ROMs 5, 6 and 7 if they had previously ROMs installed there. Or have they chosen a new Flash IC? Do you know which Flash was used for the tests?
Bryce.
The chip shown on the pictures on PushnPop show a 39SF040, which has 4K pages.
(I do have a beta version of my software for my flash rom board which supports 64K pages. Onviously you have to copy the other 3 16K images into ram and then re-write them if the slot you want to program is not blank. I've been using a 29F040 for testing. Only works on machines with extra ram).
Ah, ok, then it shouldn't be a problem. I thought they were using something else.
Bryce.
The FlashGordon and the Bübchen version of the MegaFlash are using the same Flash. Both decided independently for that, so there must be some reasons. Since that chip is available now it would be great not to start producing cards with different chips agian.
The Flash is the SST39SF040 from SST. Sure I know which chip that is else I couldn't make software for it.
In the case of the SST39SF040 you have to erase 4 KB sectors and write anything byte-wise.
SDP does NOT exist in the way like for the Winbond. Or let's put it this way, the SDP can NOT be switched off.
Look:
I am also using the SST39SF040 for my own RAM/Flash extension. Mainly for its availability and the CPC friendly 4K page :).
By the way, SST=Microchip.
So.... it should work with your card too!?!
Quote from: TFM/FS on 19:02, 04 March 13
So.... it should work with your card too!?!
Yes and no :D .
I am using a different IO port for allowing write to the flash.
I've modified the Amsdos v1.44 of your ROMmanager.
Let me know if you want the changes.
Well, a release is of interrest as soon as you decide to release your card itself.
You can transfer your changes to 1.45, since it supports also headerless ROMs now.
@all:
Ok, let me use this thread here to ask a question... Does anybody need to use a version smaller than 1.44 / 1.45 ??? If not, then I can delete the older stuff from the archive and make the download more slim and clear.
Ok, have problems to access my CMO hosted homepage, dunno why. So here the archive including ROMs of the ROManager for the FlashGordon device... Please let me know if it works or not (I can't test myself). Thanx, TFM
Ok, upload finally worked out (goto FutureOS - The revolutionary UltraOS for the CPC6128 and CPCPlus (http://www.futureos.de) download section). Now also the 64 KB Version is there for the FlashGordon device.
It there is no error, then this will be the last update for a long time (I hope).