flat assembler
Message board for the users of flat assembler.
![]() Goto page 1, 2 Next |
Author |
|
comrade
You need to use a hex-editor.
|
|||
![]() |
|
kerr
comrade wrote: You need to use a hex-editor. yes. but i need modify it .
_________________ I hope we will be good friends. |
||||||||||
![]() |
|
kerr
Does this bug have no friends to know how to modify it?
|
|||
![]() |
|
Furs
Is this for the DVD drive, or the disc? I doubt anyone knows how to modify the firmware of a specific drive, that's proprietary most of the time.
![]() |
|||
![]() |
|
kerr
Furs wrote: Is this for the DVD drive, or the disc? I doubt anyone knows how to modify the firmware of a specific drive, that's proprietary most of the time. This is hitachi dvd drive firmware model number. It's more difficult than imagined. Do you know ? _________________ I hope we will be good friends. |
|||
![]() |
|
Furs
Nope, and I doubt anyone on this board knows, unless they deal with this stuff (at work or hobby).
|
|||
![]() |
|
kerr
Panasonic firmware is better modified , but Hitachi's firmware modification is not so easy.
|
|||
![]() |
|
kerr
How can i modify dvd firmware to enable it to boot properly?
|
|||||||||||
![]() |
|
MSrobots2
Firmware is usually written by the manufacturer of the device. And if they need to update it they have to send it out to existing customers.
But they have to make sure that the provided image not actually got corrupted on the way to their product. This is usually done by a checksum in the image. Not for copy protection, more as integrity check. Most often this is done with a simple xor over all bytes, patching the last byte so that the xor over all bytes ends up as zero. But this is just a example, not in any way the rule how it is done. So your attempt to just change one byte might just not boot because of a wrong checksum, somewhere. Mike |
|||
![]() |
|
kerr
MSrobots2 wrote: Firmware is usually written by the manufacturer of the device. And if they need to update it they have to send it out to existing customers. Yeah,this is usually done by a checksum,but i changed the number of 10 at address 0x703a to 0c , its model number changed has taken place, but i was prompted to get the command failed. please help me ,thanks. _________________ I hope we will be good friends. Last edited by kerr on 04 Jun 2018, 02:12; edited 1 time in total |
|||
![]() |
|
revolution
Have you tried contacting the manufacturer?
|
|||
![]() |
|
kerr
revolution wrote: Have you tried contacting the manufacturer? Oh No this is manufacturer give me . _________________ I hope we will be good friends. |
|||
![]() |
|
revolution
Did you tell them your problem? What did they suggest?
|
|||
![]() |
|
kerr
revolution wrote: Did you tell them your problem? What did they suggest? This is for me to modify the model number. I modify the GUEN1 to GUE2N But show the original. but i changed the number of 10 at address 0x703a to 0c show the GUE2N ,But this model number show the "boot" string . firmware is get cmd failed. _________________ I hope we will be good friends. |
|||
![]() |
|
kerr
Hi friends.
please help me,how to edit this firmware version? _________________ I hope we will be good friends. |
|||
![]() |
|
revolution
The "how" is easy, download a hex editor. The problem is determining which bytes to change and what to change them to.
What bytes did the manufacturer say should be changed? |
|||
![]() |
|
kerr
revolution wrote: The "how" is easy, download a hex editor. The problem is determining which bytes to change and what to change them to. Firmware model number change GUE1N into GUE2N . _________________ I hope we will be good friends. |
|||
![]() |
|
revolution
Why can't the manufacturer send you a new updated file?
|
|||
![]() |
|
kerr
revolution wrote: Why can't the manufacturer send you a new updated file? This is change drive ,So updated file is ineffective. _________________ I hope we will be good friends. |
|||
![]() |
|
Goto page 1, 2 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2019, Tomasz Grysztar.
Powered by rwasa.