I have REALLY been enjoying using this program on my netbook and using it like an eReader. The only problem I have encountered so far is that when my little netbook stays idle for too long it goes to sleep. This little program seems to have some major troubles when waking up from sleep states. The entire page I was viewing when the sleep state started is completely unreadable. The entire page is glitched. This happens no matter the actual state of the program. Minimized, or full screen. Doesn't matter. It also seems to lock out the hotkeys (F11 for instance) for an extended period of time. The page only returns to normal after clicking on it to change it's state from library view to full screen. I'm sure this is an easy fix that would really improve my viewing experience and anyone else with a netbook and windows XP that does a lot of reading. Let me know if you have any more questions that might further the remedy of this bug.

Win XP 32bit
1.66 Mhz
2Gig Ram
Asus 1005HA
ComicRack 0.9.121

I can confirm this on my netbook (MSI Wind U100 - Atom 1.6 N270, integrated Intel 950 graphic card).

However my hotkeys aren't blocked (f11 works).

You can refresh the page (f5) each time to remove the glitch or disable hardware acceleration in preferences - that solves the problem completly.

I'll try both those things. Thanks for the tip, but bug nevertheless. I'm updating to .122 today, hope there's a fix in there!

This is a driver issue IMHO. None of my Tablet PCs has this issue.

But as stated, a refresh/resize should fix it.

Turned off hardware acceleration and that basically fixed everything. The pages were a little blurrier than with it on, and took a little longer to move from page to page. I recognized another problem though. Seems there's a little problem with the filters as well. I guess it's possible it's related. With the software filter turned on there's a small strip of blurry page at the bottom left corner. I've decided to just turn the filters off and keep the acceleration on. Keeps the pages moving smoothly, sharpens them up a little, and I use f5 whenever there's a problem. Works great, but it's still a workaround. Just letting you guys know it's easily replicable if you want any details.

I was actually having a filters problem like that on my new box myself. I figured it was just the machine though - the fact that turning off hardware acceleration fixed the problem indicates that cYo was 100% correct - this is an issue with the video driver (or else the card itself). The filters will be the same thing, more or less.