View Single Post
Old 05-21-2010, 12:09 PM   #19
tselling
Addict
tselling will become famous soon enoughtselling will become famous soon enoughtselling will become famous soon enoughtselling will become famous soon enoughtselling will become famous soon enoughtselling will become famous soon enough
 
Posts: 366
Karma: 510
Join Date: Apr 2008
Device: NookColor (MiRage/CM7.2 & Moon+ Reader Pro)
Quote:
Originally Posted by jackie_w View Post
Thank you for responding.

I have re-downloaded and tried a couple of my epubs with your fonts and CSS. That seemed to go OK. So I have now updated to my fonts and CSS. So far so good. I will see what happens tomorrow with more extended use. Now I'm really confused, but keeping my fingers crossed.

After the testing earlier today I had a further complication when my reader suddenly became unreadable by the PC and I had to reformat it all. I wondered whether the hacking had caused the problem. Now I'm wondering whether it was the other way round and the internal memory was already in trouble when I started to test your hack. Only time will tell.
I don't see how the hack could cause a problem with memory since all I did was change the bytes that pointed to the original css file to the one in user accessible memory. It is probably more likely that there was a problem with the particular memory locations that the files were copied to.

I used a hex editor to change only 23 bytes:
res:///adobe/pxf/userStyle.css
to
res:///mnt/ext1/userStyle1.css
tselling is offline   Reply With Quote