Re: Limit on number of pages plucked? (Error code=514)

2003-10-03 Thread Steven Spadt
Thanks, yes this could be the problem. Let me re-run and check the log as you suggest... Steve Chris Hawks [EMAIL PROTECTED] 09/29/03 11:40AM ---Reply to mail from Alexander R. Pruss about Limit on number of pages plucked? (Error code=514) It should handle 65000 pages or so, or at least

Re: Limit on number of pages plucked? (Error code=514)

2003-10-03 Thread Steven Spadt
The cutoff (after which the links, in the viewer generate the Error code=514 error) is at record 16326. I know I'm not qualified to assess the meaning of that but, just in case it helps, since 16k = 16x1024 = 163840 and I count 25 or so 30k+ pages, if there actually are more like 48 or so, and

Re: Limit on number of pages plucked? (Error code=514)

2003-10-03 Thread David A. Desrosiers
Is there any other piece of data we could provide, other than shipping you an archive of all the pages we're trying to pluck (which would be difficult but not impossible, logistically)? Can you just scramble the content in a non-reversible way, and ship those pages instead? I

Re: Limit on number of pages plucked? (Error code=514)

2003-10-03 Thread David A. Desrosiers
I know I'm not qualified to assess the meaning of that but, just in case it helps, since 16k = 16x1024 = 163840 and I count 25 or so 30k+ pages, if there actually are more like 48 or so, and we add that to our 16326 number from below, we come out awfully close to 16k, a limit which would

Re: Limit on number of pages plucked? (Error code=514)

2003-10-03 Thread Michael Nordstrom
On Tue, Sep 30, 2003, Steven Spadt wrote: The cutoff (after which the links, in the viewer generate the Error code=514 error) is at record 16326. I wrote a program that generated 16330 html files that each linked to the next file (except the first file that also included a link to 16325 (to

Re: Limit on number of pages plucked? (Error code=514)

2003-10-03 Thread Michael Nordstrom
On Fri, Oct 03, 2003, Michael Nordstrom wrote: I will run it in the debugger now and see if I can pinpoint the problem... I've found the problem (and it was actually related to the use of Int16 in the SearchDocument function:) We get an overflow in the code that is used to optimize the search