megalomaniac wrote:99$ is right for the barebones pcb with no chip and no ports
but if you pay to have those installed as they would already be installed on a 64drive, then the everdrive comes out to about 150$
how many everdrive64 firmware releases and pcb versions have been created compared to 64drive?
which one offered almost 99% support from initial release vs multiple months/years of updates just to get it where it is now?
Not anyone needs a usb port , it's only for dev reasons. And you can just add it later with a usb port and a MAX chip that you get from eBay easily.
It is irrelevant how many updates it took the ED64 to be what it is, the man is talking about getting one NOW , not 2 years ago.
Not to mention that AFAIR
when the ED64v1 was released the only other available cart was the neoflash one, the 64drive was in design/beta/closed stage or something. And the v2 ED64 added nothing to compatibility , it only added way faster rom loading.
You can use the CIC/shell from a 1$ game, if you can't do it yourself then like with all things in life you gotta pay
So if you get the ED64 with case/cic it costs you a total of 134$ with worldwide shipping. Add the USB port for dev reasons and you are at 149$.
The 64drive costs 205$ for US people or 213$ for the rest of the world.
The price is nowhere near unless a ~60$ difference means nothing to a person.
Don't get me wrong, I have nothing against the 64drive , it's great and awesome but still remains expensive compared to the ED64 while offering the same thing to the end user. (if you know something different please correct me)
And I don't go for the cheapest cart either, I bought a Mega-Everdrive and a SD2SNES but these two were clearly a superior design, something that can't be said to justify the +60$ the 64drive demands.
it is not recommended to use a 7105 CIC, supposedly it breaks compatibility with other games... it's been some time now but these games play just fine on the ED64 , you don't need any patched versions anymore. Krikzz released an update to the OS that takes care of them, basically "cracking" them on the fly when they get copied on SDRAM as far as I understood