Dtivo 2.5.2 mwstate error & fix

[rc3105]

there's a method of prodding tivoapp aka myworld to dump it's current state to the file /tmp/mwstate which can be pretty handy

event send $TmkEvent::EVT_REMOTEEVENT [binary format II 32 0]

unfortunatly...

Originally posted by embeem
2.5.x had a bug where two programs would attempt to write to /tmp/mwstate simultaneously thus corrupting the file.

There's no easy fix, you can backup your tivo, hexedit /tvbin/tivoapp and change the second occurance of "mwstate" to "mstat1" so the two programs write to different files.

here's how I did it

copied tivoapp out to the pc via tivoftpd
edited it with hextreme
renamed it to tivoapp.new
transferred it back to the tivo
made it executable with chmod +x

WITH THE TIVO RUNNING...
renamed tivoapp to tivoapp.bak
renamed tivoapp.new to tivoapp
rebooted the tivo

all was well


--
Riley

[mrblack51]

is 2.5.5 and 2.5.2 the only versions with this issue, or are newer versions affected as well?

[John1980]

Note, the following patch will alter the second occurance of /tmp/mwstate to be /tmp/mwstat1... in fact this is the only difference between v2.5.5 and v2.5.5a of tivoapp. Assuming you have 'dd' available to you on the TiVo then the following can be applied directly (after you make the filesystem read-write and change to /tvbin).

WARNING: Do not do this unless your tivoapp is exactly 5646960 bytes in size (eg version 2.5.5).

cd /tvbin
mv tivoapp tivoapp-bak
cp tivoapp-bak tivoapp
echo -n '1' | dd conv=notrunc of=tivoapp bs=1 seek=5137975