i have one flashchip left
im going to try and solder that on top of the original flashchip and put a switch on it so i can switch between Nextor and "normal"
The Sunrise IDE driver (which works on the CF interface) works as it is now, all the modifications from the previous version have been made in the Nextor code itself.
Anyway that driver still can't detect media changes. Nextor can handle that, but with reduced performance (anyway this can be solved by locking drives).
So, can we consider stable the current version of Nextor for Sunrise ide chart?
We had recently an upgrade of its SW to allow full access to the CF chart, does it impact on Nextor ?
So, can we consider stable the current version of Nextor for Sunrise ide chart?
All I can say is that the Sunrise IDE driver currently available for Nextor is the one I am using in blueMSX for testing and it seems to work fine. For sure it has huge room for optimization, but yes, I would say that it is stable.
We had recently an upgrade of its SW to allow full access to the CF chart, does it impact on Nextor ?
No. The recent update is on the standard BIOS, which is based on MSX-DOS and has its own "old style" driver. The Sunrise IDE version of Nextor uses a "Nextor style" driver made from scratch and has nothing to do with the official BIOS.
Wow, amazing achievement!
Just a small question about Nextor/ dos2.5; did you also check the 2.4 versions for fixes and improvements?
Just a small question about Nextor/ dos2.5; did you also check the 2.4 versions for fixes and improvements?
What do you mean by "2.4 versions"? COMMAND.COM 2.4x?
Sorry for the confusion, I see you recommend command2.com v2.44 ( http://www.tni.nl/products/command2.html ) on your page ( http://www.konamiman.com/msx/msx-e.html )
:RNFF:
Well, there are news: a new Nextor release is in the oven..
Cool.. about the new features... what's new ?
Cool.. about the new features... what's new ?
Mainly bugfixing, but also a few new BASIC commands for drive(r) information gathering and a CALL USR command that does the same as DEF USR but allows you to control the contents of the Z80 registers.
Release in a couple of days, so stay tuned.
Maybe Nextor is incorrectly assuming that it is always running in a Turbo-R, and hence uses always the internal mapper. It is something that I must investigate.
I hope the mapper problem i have from the other forum post is solved
I hope the mapper problem i have from the other forum post is solved
In fact it was not... thanks for pointing that out, it has been an easy last minute fix. (Damn, I really need a bug tracking system...)