So you have a ebook device. When will you upgrade?

[NatCh]

Originally Posted by The GreatGonzo

When you can drop an e-reader like you can drop a book and nothing happens to it, that'll be a great day.

I agree completely. Of course, if being ruggedized were the main improvement, I'd probably still hold off on getting one until I dropped the one I have on something hard enough to bust it.

[yvanleterrible]

Maybe the promised flexible displays will be tougher and less expensive if broken.

[athlonkmf]

Originally Posted by kacir

I have paid quite a lot of money for Sony Reader quite recently and I also had to invest considerable effort to be able to get it here - in Central Europe.

I will replace it when it dies. Period.
It does everything I need it for.
If there was version without mp3 player that was $10 cheaper I would have purchased the one without the mp3 player.

That's why the first posts ask you what kind of features will MAKE you upgrade?

[athlonkmf]

Originally Posted by The GreatGonzo

No. 2 would be near-indestructibility. I really feel that e-ink devices, insofar as that is at all possible, need to be much sturdier for me to be completely comfortable with them. When you can drop an e-reader like you can drop a book and nothing happens to it, that'll be a great day.

If it's flexible and scroll-like and when you drop it, it roll up it's flexible display real fast. That'd make it much more sturdy. And maybe fill up the electronics space with non-conducting waterproof gel, so it even becomes machine washable

[Roy White]

Be able to read UNDERWATER! at 60 FSW at Tormento's reef at Cozumel!

[JSWolf]

One thing nobody mentioned that would be a big boon to any reader... More internal memory. Maybe 4gig would do. 2gig for the OS and programs and 2gig for data. That way all these upgrades and hacks and whatnot would have plenty of room. I can picture the day when someone will have to decide what programs to load (on the iLiad) and what not to cause it's not got enough ram.

[NatCh]

Originally Posted by Roy White

Be able to read UNDERWATER! at 60 FSW at Tormento's reef at Cozumel!

You're scuba diving off of Cozumel, and you can't find anything to hold your attention away from wanting to read? Perhaps you should de-fog your mask.

[astra]

Originally Posted by mogui

But I would feel guilty

This is the reason why I would not swap my reader with anything else. I think I am going to use it until it dies or at least 3 years old. Then I might consider a replacement which would include:

- next generation eInk screen with features such as:
Better refresh rate, less ghosting, maybe 8-10" instead of 6". I think that would be the only reason that would seduce me for a new reading device.

There are a few more features that I would like to have but they would not be crucial and could not persuade me to part with $350 or more.

[TadW]

Seeing the news that the first e-readers with Vizplex technology have already arrived, I think I am ready to upgrade soon.

Easy decision for me because my Reader has already found a new owner (=my wife).

[athlonkmf]

Originally Posted by JSWolf

One thing nobody mentioned that would be a big boon to any reader... More internal memory. Maybe 4gig would do. 2gig for the OS and programs and 2gig for data. That way all these upgrades and hacks and whatnot would have plenty of room. I can picture the day when someone will have to decide what programs to load (on the iLiad) and what not to cause it's not got enough ram.

I'm not sure about this. While internal memory can be useful for programs. I prefer using highcapacity memory cards, because 1) they're cheaper and 2) it's always faster to pump data in a m-card with a seperate (fast) cardreader than through a device.

[NatCh]

There are a couple of caveats there, athlonkmf. The first is that the memory cards will drain your battery faster, though you'll still get 2~3 weeks between charges, so you may not care about that.

The second is that using memory cards the way you describe means that the Reader has to do all the page parsing, rather than the PC (which is faster at it), and it will re-parse the entire card every time you insert it. That will have an effect on your battery life too, but mostly it's just slow to wait for.

For me, I've found that I prefer to just wait the time that it takes to xfr the files into internal memory. Since I'm rarely moving more than a few files at a time, I don't find the speed to be a burden, I don't have to worry about losing my bookmarks that way, and I get to use collections, which are a particular boon to me.

If you're happy with what you're doing, though, don't let me talk you out of it.

[athlonkmf]

Originally Posted by NatCh

There are a couple of caveats there, athlonkmf. The first is that the memory cards will drain your battery faster, though you'll still get 2~3 weeks between charges, so you may not care about that.

The second is that using memory cards the way you describe means that the Reader has to do all the page parsing, rather than the PC (which is faster at it), and it will re-parse the entire card every time you insert it. That will have an effect on your battery life too, but mostly it's just slow to wait for.

For me, I've found that I prefer to just wait the time that it takes to xfr the files into internal memory. Since I'm rarely moving more than a few files at a time, I don't find the speed to be a burden, I don't have to worry about losing my bookmarks that way, and I get to use collections, which are a particular boon to me.

If you're happy with what you're doing, though, don't let me talk you out of it.

Hmm.. the last time I've thrown in a couple of manga in the readers internal memory, the reader still needs to parse it when opening. But then again, these are generally small manga of around 100 pages and 10MB in size, compared to the 200MB 3000+ pages on my card, it's of course nothing.

So I'm wondering if the connect-software actually preparse stuff.

But then again, parsing and indexing only needs to be done once, so...

[NatCh]

That's odd. I've never had it parse something that I've loaded through ConnSoft, and it always parsed everything I loaded via the card -- something else must be going on there, athlonkmf, but I'm at a loss as to what.

[HarryT]

Originally Posted by NatCh

That's odd. I've never had it parse something that I've loaded through ConnSoft, and it always parsed everything I loaded via the card -- something else must be going on there, athlonkmf, but I'm at a loss as to what.

When you load an LRF through Connect, you never (in my experience) get any "parsing delays" on the Reader. When I used to use RTF on the Reader, though, there'd be a lengthy delay (several minutes for a large book) on first loading the book, and whenever a different font size was first selected.

[astra]

Originally Posted by HarryT

When you load an LRF through Connect, you never (in my experience) get any "parsing delays" on the Reader. When I used to use RTF on the Reader, though, there'd be a lengthy delay (several minutes for a large book) on first loading the book, and whenever a different font size was first selected.

Ditto.