• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

R.I.P Optorite

K

KeyserSoze

Diamond Member
You were a good burner, and we had some good times. You will be missed.....

Ugh. Firmware flashing with a corrupt floppy disk....sons of b!tches.

BUT.....I do get to look forward to a dual layer now 😀

Damn, this sux.





KeyserSoze
 
Originally posted by: KeyserSoze
You were a good burner, and we had some good times. You will be missed.....

Ugh. Firmware flashing with a corrupt floppy disk....sons of b!tches.

BUT.....I do get to look forward to a dual layer now 😀

Damn, this sux.





KeyserSoze
Click to expand...

what about flashing it again?
 
Originally posted by: Evadman
Can the eprom be removed? if so, get another.
Click to expand...


I have no idea what you're talking about, so I'm going to hit Google and do a little research about this "eprom" you speak of.





KeyserSoze
 
It's very hard to completely fry the thing, unless you somehow overwrote the ENTIRE eprom.

Yeah, you could get a replace the eprom, though finding it might be a pain. On the other hand, Optorite drives aren't the best when it comes to compatibility. Sure, HD-Burn is cool, but I'd like to be able to buy cheap-ass generic DVD media and not have problems burning it.
 
Originally posted by: Yossarian
the eprom is the memory chip that gets flashed.
Click to expand...

Aight, thanx ladies...I'm gonna do a little research. But I actually wouldn't just mind getting a dual layer for $61 bux which is what Aphex found on Newegg.

Thanx again.




KeyserSoze
 
Okay, quick rundown of microprocessors:

The firmware you're flashing is a microprocessor. It has the RAM, where data is stored, and the EPROM, where the process instructions are stored. Both are memory storage areas. Whenever the drive loads it runs a very simplistic program from the EPROM. But since you flashed it incorrectly it's likely that the program in the EPROM is either nonexistant or gibberish. Now assuming the EPROM isn't physically damaged you could theoretically re-write the entire thing with an older/working firmware revision, but since your drive won't turn on that's out. If you can remove the EPROM you could theoretically interface it with some external microprocessor -- there are 4 major ones and one of those will likely work -- and flash the chip that way. But that's only fun if you're an EE major. 😛 Otherwise you can find a new EPROM elsewhere, online.

If the EPROM is physically damaged then replacing it with a new, blank chip would probably fix the problem.
 
Originally posted by: yukichigai
Okay, quick rundown of microprocessors:

The firmware you're flashing is a microprocessor. It has the RAM, where data is stored, and the EPROM, where the process instructions are stored. Both are memory storage areas. Whenever the drive loads it runs a very simplistic program from the EPROM. But since you flashed it incorrectly it's likely that the program in the EPROM is either nonexistant or gibberish. Now assuming the EPROM isn't physically damaged you could theoretically re-write the entire thing with an older/working firmware revision, but since your drive won't turn on that's out. If you can remove the EPROM you could theoretically interface it with some external microprocessor -- there are 4 major ones and one of those will likely work -- and flash the chip that way. But that's only fun if you're an EE major. 😛 Otherwise you can find a new EPROM elsewhere, online.

If the EPROM is physically damaged then replacing it with a new, blank chip would probably fix the problem.
Click to expand...

Thanx! So what I do is first look for the Eprom that was located in my drive (Version, etc.), and just find the replacement for it? Should be easy enough with Google.

But yeah, this reprogramming stuff isn't for me! Damn EE people 😛



KeyserSoze
 
First you have to figure out what chip(s) are the EPROM. They may be labelled, they may not. Chances are that you just need to find the right size (in terms of kb) chips and merely get the firmware onto them. I'm sure there are services out there that will do that, though they may not be cheap.

Or you could try to recruit some EE majors from the local college to do some extra-curricular hands-on stuff for their microprocessor class.
 
Originally posted by: yukichigai
First you have to figure out what chip(s) are the EPROM. They may be labelled, they may not. Chances are that you just need to find the right size (in terms of kb) chips and merely get the firmware onto them. I'm sure there are services out there that will do that, though they may not be cheap.

Or you could try to recruit some EE majors from the local college to do some extra-curricular hands-on stuff for their microprocessor class.
Click to expand...


Ugh, sounds like a lotta work. I dunno, my friend "NewEgg" might be able to help me out a lot more! 😀



KeyserSoze
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top