2510 2.F8 Quikee Modded Firmwares

OK1 I see paint!

---

Last edited by EARLTHEPEARL; 23-11-2004 at 01:38.

Quikee2:
Really like to see the speed up for Ricohjpnr01 to 8X as in HV2B5:
52 49 43 4f 48 4a 50 4e 52 30 31 02 01 -> [RICOHJPNR01 ] 2.4 4.0 6.0 8.0

I still have tons and it is the main dish for my 2500A when it is hungry Mine works great @ 8x.

Thanks again for all your great work

nobody knows ?

Maybe a issue with external enclosure... maybe it's just my firmware.. has enybody used beta 2 yet? =)

my friend wasn't online yet.

still trying to phone him at least...

@Quikee2
I'm using your beta2 and my Nec is working fine!
Post some scan's tomorrow.

I noticed today that my 3500 and 2510 will not read a music cd in nero but will in Sonic record.

Probably it's a problem with external enclosure. Connect him (nec ocdirectly on the ide channel. Should work.

Can you support and Mame dvd-r which have this id MAM8XG01 because it shows that can write with 8x speed ,but it starts with 4x it continues with 6x ant then go down to 4x and it doesnt write with 8x.Please help me because i have MAME 200 dvd-r.

Panos26: That's becouse the disc can't handle the speed =) I could try another writestrat however...

Qukee2.Thank you in advance

I had to use the last spindle of my Princo (Datawrite red) and I use to have reasonable results with my 2500@2510. But not with my last spindle, first I thought that it was the new 2f8 firmware but it is defitnitely a bad spindle.

First scan is princo at 4x with firmware 2f8 and the second is a princo at 8x with modified firmware 2f8 beta 2 by Quikee.
Not good either but better than the original firmware.

Yeah it's really hard to judge a firmware when testing with princo :P i had the same problem a while back....( i dont buy princo any more )

I do not buy them anymore too

Hi guys,

I'm a newbie here, and about to try the new Quikee2 firmware in my 2500@2510A. I used to have Herrie's 2k5107v2b5dl. It wasgreat 'cause it allowed me to buy crappy Princo's and record at 6X (no good at 8X).
A few days ago I bough a box of Platinum (Ricioh) + @ 8x, but although it claimed to be at 8X it would take 10 min. to record. So I came crawling back here looking for some news.
Apparently, I may be having some other issue, cause I notice sometimes the buffer missing and implicating buffer underrun action, and therefore more time...
Still, I wanted to thank Quikee2 for his efforts and will try to help (as user, of course...)
One more thing... I have more then 100 Princo's to record (promotion on a store...hehehe). PLEASE bring my speed again!!!
P.S.- sorry for the long post. :-)

Burning at 8x takes about 9:30 min.

/kick:
Any news on new modified firmwares?
I flashed the beta2 firmware, works good so far. Haven't burned to much trough.
Keep up the good work

Hello,
Thank you for continuing to work on the 2510. I have some Ridata brand +R's that are RICOHJPNR01. Currently they burn to 6x, but I would like to know if you can modify the write strategy to burn to 8x? Here's the media code:

08 02 00 00 01 0F 02 00 00 03 00 00 00 20 0E 7F ............. ..
00 00 00 00 00 00 01 52 49 43 4F 48 4A 50 4E 52 .......RICOHJPNR
30 31 02 38 23 54 37 09 00 3C 67 00 AC 62 16 18 01.8#T7..
0B 0B 0A 0B 01 19 1B 0B 0B 0E 0F 01 00 00 00 00 ................

Thanks in advance,
TedS

i sucessfully flash my 2500 to this firmware ok are you goin to add anymore write strats to overspeed more discs as i know you are working more on the 3500 firmware currently which is fantastic quikee2 keep up the good work!

it's hard when you (I) have a laptop

welcome to Discovery Channel: with beta2 as always the flash runs flawless..but when I put in a written cd/ dvd it reads it, a blank cd/dvd causes a looping endless spinning..and the disc is unrecognizable...

astonishing..

edit: also with tdb 2.17 and all the ones I flash with binflash..the only good one is herrie's 2.16

Uuupss... sorry. I didn't know. Maybe use someones pc

I also expreience this, written cd's appear as empty, but burning works ok. Herries 107v5b2 works fine. Is this an issue with BinFlash or the firmware?