Anyone know of a way to find out where the flaw is in this software. After a short while it complains with error message of "Not enough storage is available to process this command", yet I have 40GB of 160GB HD FREE, and my available Ram is hovering at 500MB of 1GB, running Windows XP Home SP3 on Dual Core Atom CPU on my netbook.
I have tried to contact the programmer to ask about what could cause this, given he was the one who put the error message in his program, but its been about a month of repeated e-mails out to him and no response, and the website is dated 2007 so he might not be managing it anymore.
Only way to reset this error is to reboot windows. If you exit the program and then restart the program it complains immediately with the same error. ( So I am thinking its a Cache Issue - overflow maybe, in how it uses IE's engine to navigate to web pages and then save them as images for archiving web pages just as they can be viewed but flattened in an image with no further functionality.)
Perfect for archiving sites with text that you want to look back at such as articles etc, but can be used for just about any purpose to snapshot webpages for reference as jpgs or bmps.
http://www.priyatna.org/webthumbnailer.phpIs there a way to see if a buffer is full in cache? Such as a buffer that IE would be using, where I am expecting to find the issue? Is there a way to reset all Cache without having to reboot the computer to reset a buffer that may have overflowed?
For now its set it and when it crashes, look at the data captured and remove from the list that of which processed correctly, save the list as text file, reboot windows, copy/paste the list of URLs and then run it again until it crashes and then repeat. Eventually i will have everything I want to capture.
*Also to note it doesnt always crash after say 20 pages captured. It seems random in how much is captured before it bales out with that error, and only reset is system reset to get it to run further. If it crashed always after so many pages etc then that would be a nice indicator of where to look for the flaw in which maybe I can band-aid this issue by another program that would clear the buffer etc after so many minutes etc. Although it can be hairy with resetting a buffer that is in current use by the app and maybe this is not repairable... Its too bad his Delphi source is not available to look at the source and pick away at it for potential or known flaws in the code.