DVD in motion patch for NR261UM
I tried the procedure three times, no joy !
jsrd mentioned the file size for alldata.kwi = 4 KB and
loading.kwi = 24,464 KB, on the ISO I extracted have a different file size, alldata.kwi = 4 KB,loading.kwi = 24,828 KB, Did I downloaded the wrong rar ?? Can someone point me to the correct rar to download.
Any chance people have problem may have different firmware on their MMCS that caused this issue?
My version is NR-261UM 1.09
jsrd mentioned the file size for alldata.kwi = 4 KB and
loading.kwi = 24,464 KB, on the ISO I extracted have a different file size, alldata.kwi = 4 KB,loading.kwi = 24,828 KB, Did I downloaded the wrong rar ?? Can someone point me to the correct rar to download.
Any chance people have problem may have different firmware on their MMCS that caused this issue?
My version is NR-261UM 1.09
Hey I noticed that some people have posted a software version with the bootloader version the same (BLD-NR-261UM 1.09) as mine (which is what the UM patched KWI file is based on). I drive an 08 Lancer from March 07. The application version on mine is "00.20.68" where someone who drives an Evo X had app version "00.30.94" -- even different microcomputer versions. Maybe this is why the updates won't take on your units.
In that case, it sounds like someone with a "newer" version will have to pull their drive and patch their Loading.KWI file manually (or send it to us).
Here is a screenshot of my versions:

And a screenshot of someone driving an Evo X (which claims the update didn't work):

In that case, it sounds like someone with a "newer" version will have to pull their drive and patch their Loading.KWI file manually (or send it to us).
Here is a screenshot of my versions:

And a screenshot of someone driving an Evo X (which claims the update didn't work):

I think you're onto something..my bootloader version is (BLD-NR-261UM 1.09) I drive an 08 Outlander from Nov 07.My application versionis "00.30.94" Maybe this is why the updates won't take onmy unit.
Here isa screen shot:
[IMG]local://upfiles/16364/CFFAD644F63F442D8F0A260A9D3FC399.jpg[/IMG]
Here isa screen shot:
[IMG]local://upfiles/16364/CFFAD644F63F442D8F0A260A9D3FC399.jpg[/IMG]
Making tests with the MMCS and RES yesterday...
Otaku, rcostin, is not possible to see the image in the MMCS while I'm driving when RES is the source; is possible one patch to be able to "correct" this?
Otaku, rcostin, is not possible to see the image in the MMCS while I'm driving when RES is the source; is possible one patch to be able to "correct" this?
Outie08, I upload to rapiddhare iso file that I unloaded; tries to update your MMCS with this iso, perhaps it works this way. . . The link:
http://rapidshare.com/files/11887654...261UM.iso.html
http://rapidshare.com/files/11887654...261UM.iso.html
ORIGINAL: jsrd
Making tests with the MMCS and RES yesterday...
Otaku, rcostin, is not possible to see the image in the MMCS while I'm driving when RES is the source; is possible one patch to be able to "correct" this?
Making tests with the MMCS and RES yesterday...
Otaku, rcostin, is not possible to see the image in the MMCS while I'm driving when RES is the source; is possible one patch to be able to "correct" this?
What is "RES" ?
O.
I just drove around the block watching a dvd...cool....thanks agaiin to Otaku, rcostin and brian360 for all of your efforts! For the people having issues burning the .iso --maybe it is similar to the CDDB upgrade where certain burning apps didnt seem to work?..not finalizing the disk properly? If possible, try another app--i used dvd-decrypter..its free...



.
