PRS+: Enhanced firmware for Sony Reader, Folders, Games & more

[JSWolf]

Originally Posted by kartu

JSWolf
Were you able to connect to it not long before installing PRS+?
The easiest way to disable PRS+ is renaming /database/system/PRSPlus/PRSPlus.js file to anything else. (then connect to PC - disconnect, or reboot)

I think somebody else has already reported that problem, but then found out it wasn't related to PRS+

I've managed to sort the problem.

What I did was try to install PRS+ and it didn't work because there was not enough memory left internally. So I then copied the contents of the 505 to the HD. Then I had to get the 505 into flash mode and I then formatted the internal memory. After that I installed PRS+ and the 505 was unable to connect to Reader Library. I moved the contents of the 505 (with PRS+) to the HD. Wiping internal memory and then copying part of the original contents worked so Reader Library could see the 505. Then I used reader library to wipe all collections and content. Moved the PRS+ system directory and put the contents back and it works.

Now I do have one thing I'd like to have back from the original unmodified firmware. I'd like ot have the page numbers so they can go 62-63 of 436 instead of 62 of 436 followed by 62 of 436.

[kartu]

You can get the feature you want via:
Settings -> PRS+ Settings -> Page Index

[JSWolf]

Originally Posted by kartu

You can get the feature you want via:
Settings -> PRS+ Settings -> Page Index

Which index style do I want? I do have the clock on and set to 12 hour mode.

All I see is 8 of 36 and then the next page is still 8 of 36 instead of 8-9 of 36.

[kartu]

Hm, maybe your PageIndex.js file is corrupt? ^^ Try to overwrite it with the one from the installation zip. Actually running checkdisk on internal memory would also be a good idea.

[JSWolf]

I can turn the index off and switch it to another style. Just cannot get it to display with the dual page numbers. The PageIndex.js file did come right from the installation zip. And I did run checkdisk on my 505 in case that was part of my earlier problem.

I've attached my PageIndex.js so you can have a look at it.

[kartu]

The file is fine. Unless you've combined other hacks with PRS+, we have to investigate what's wrong. Create user.config file in /database/system/prsplus/ folder with the following content

var config = Utils.config;
config.defaultLogLevel = "trace";
config.logFile = "/Data/PRSPlus.log";

It should create PRSPlus log in the root of internal memory. Check it's content. (when we resolve this issue, don't forget to delete the user.config file)

[JSWolf]

I've no other hacks. In fact, I did do a firmware install back to square one because of the glitch.

One thing I suggest is telling people how much internal memory they'll need free to flash the image.

How much reading or what else should I do before looking at the log?

[JSWolf]

One quick note, the 8-9 of 36 was lost using Igorsk's flasher the first time. So could it be a bug in Igorsk's flasher?

[kartu]

How much reading or what else should I do before looking at the log?

2 pages is enough.

One quick note, the 8-9 of 36 was lost using Igorsk's flasher the first time. So could it be a bug in Igorsk's flasher?

It could be pretty much anything, but Igorsk's flasher normally reports "not enough memory" errors. And I don't get why would one need internal memory (accessible to user) to flash ^^. The "not enough memory" could happen if yuo are adding files to the image (using button 5 etc) which you shouldn't do if you install PRS+.

[dieterpops]

I also do not have the page 3-4 capability anymore. My reader only has about 20 files installed. Everything else works flawlessly.

[JSWolf]

Here's the log file...

2010-1-14 16:12:16.410 I autorun PRSPlus initialization took 0.59 seconds

That is all that is there.

[kartu]

JSWolf
Ok, so no errors are reported, just delete the user.config.

dieterpops, JSWolf
I'll re-check the code, but as a workaround try simply deleting PageIndex.js.

[JSWolf]

Originally Posted by kartu

JSWolf
Ok, so no errors are reported, just delete the user.config.

dieterpops, JSWolf
I'll re-check the code, but as a workaround try simply deleting PageIndex.js.

I renamed PageIndex.js to PageIndex.js.bak and now I see 79-80 of 436. zSo that would leave me to believe that it is something with PageIndex.js when reading ePub.

[kartu]

JSWolf
You are right, it doesn't work with (some?) epubs, at least in combination with pepak's epub style hack.

[JSWolf]

Originally Posted by kartu

JSWolf
You are right, it doesn't work with (some?) epubs, at least in combination with pepak's epub style hack.

Think you may be able to fix it? if not, it's no biggie for me.