× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That's an option.

I am looking into ways to speed up the processing too.  I
know there are things I can do to speed things up.  I have
it on my "list" to do for the next version release. 

Of course, as usual, all service pack fixes will also be
included in the next release.

Brad

On Fri, 15 Apr 2005 14:51:46 -0400
 MWalter@xxxxxxxxxxxxxxx wrote:
> User space?
> 
> Thanks,
> 
> Mark
> 
> Mark D. Walter
> Senior Programmer/Analyst
> CCX, Inc.
> mwalter@xxxxxxxxxx
> http://www.ccxinc.com
> 
> 
>
                                                          
>                 
>              "Brad Stone"
> 

                                                 
>              <brad@xxxxxxxxxxx
>                                             
>              m>
>
                                                        To
> 
>              Sent by:                  Midrange Systems
> Technical          
>              midrange-l-bounce         Discussion
>                          
>              s@xxxxxxxxxxxx
>            <midrange-l@xxxxxxxxxxxx>           
>
                                                          
>              cc 
>
                                                          
>                 
>              04/15/2005 02:29
>                                      Subject 
>              PM                        Re: PDF
> Limitations?                
>
                                                          
>                 
>
                                                          
>                 
>              Please respond to
>                                             
>              Midrange Systems
>                                              
>                  Technical
>                                                 
>                 Discussion
>                                                 
>              <midrange-l@midra
>                                             
>                  nge.com>
>                                                  
>
                                                          
>                 
>
                                                          
>                 
> 
> 
> 
> 
> Now that I look at it closer, I use an array to keep
> track
> of each page (object).  That is maxed at 32767 elements,
> and that is what was causing the problem.
> 
> When I looked at it previously the line I looked at I
> swore
> was the XREF portion, but it wasn't.  It was this array
> becoming too large.
> 
> Hmmm... now... to figure the best way to fix it since
> that
> array is maxxed...
> 
> Brad
> 
> On Fri, 15 Apr 2005 13:20:55 -0500
>  "Brad Stone" <brad@xxxxxxxxxxxx> wrote:
> > Hold the phone!  :)
> >
> > I found a small bug in SPLTOOL that was causing the
> 3000
> > page limitation!  It wasn't with the XREF at all, but
> > with
> > the pages listing portion of the spooled file.
> >
> > I will be issuing a service pack ASAP!
> >
> > Brad
> >
> > On Fri, 15 Apr 2005 12:53:48 -0500
> >  "Brad Stone" <brad@xxxxxxxxxxxx> wrote:
> > > My 10,000 page report just finished after about 5
> hours
> > > of
> > > running.  No problems.
> > >
> > > The report was basically the same line of text
> repeated
> > > over and over again.  The file is about 74meg.
> > >
> > > I know a lot of people are running older versions of
> my
> > > software still, so that may be part of it.
> > >
> > > If someone has the current version and wants to run
> > some
> > > tests, I'd love to see the job log and a dump if the
> > > program crashes, as well as the temp file that is
> > created
> > > (to see how many pages it got to.)
> > >
> > > Brad
> > >
> > > On Fri, 15 Apr 2005 11:13:19 -0600 (MDT)
> > >  James Rich <james@xxxxxxxxxxx> wrote:
> > > > On Fri, 15 Apr 2005, Mike Wills wrote:
> > > >
> > > > >The resulting file of a 3000 or so page PDF comes
> > out
> > > to
> > > > be about 5-10MB
> > > > >range I believe.
> > > >
> > > > In that case the should be no problem with the XREF
> > > > running out of space. The PDF Reference (version
> 1.5)
> > > > states that the format of the xref is as follows:
> > > >
> > > > nnnnnnnnnn ggggg n eol
> > > >
> > > > where nnnnnnnnnn is a 10-digit byte offset, ggggg
> is
> > a
> > > > 5-digit generation number, n is a literal keyword
> > > > identifying this as an in-use entry, and eol is a
> > > > 2-character end-of-line sequence.
> > > >
> > > > Therefore, if the PDF file is only 10MB large, the
> > byte
> > > > offset cannot possibly be larger than 10 digits.
>  So
> > > the
> > > > 3,000 page limit is not due to limitations of the
> PDF
> > > > xref.
> > > >
> > > > btw - the offset is the number of bytes from the
> > > > beginning of the file. The largest the offset could
> > > > possibly be is the size of the file.  That means a
> > PDF
> > > is
> > > > limited to 10GB in size (before the xref and
> without
> > > > doing any other tricks).
> > > >
> > > > James Rich
> > > >
> > > > It's not the software that's free; it's you.
> > > >              - billyskank on Groklaw
> > > > --
> > > > This is the Midrange Systems Technical Discussion
> > > > (MIDRANGE-L) mailing list
> > > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > > To subscribe, unsubscribe, or change list options,
> > > > visit:
> > > >
> http://lists.midrange.com/mailman/listinfo/midrange-l
> > > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > > Before posting, please take a moment to review the
> > > > archives
> > > > at http://archive.midrange.com/midrange-l.
> > > >
> > >
> > > Bradley V. Stone
> > > BVS.Tools
> > > www.bvstools.com
> > > --
> > > This is the Midrange Systems Technical Discussion
> > > (MIDRANGE-L) mailing list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit:
> > > http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the
> > > archives
> > > at http://archive.midrange.com/midrange-l.
> > >
> >
> > Bradley V. Stone
> > BVS.Tools
> > www.bvstools.com
> > --
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> > http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the
> > archives
> > at http://archive.midrange.com/midrange-l.
> >
> 
> Bradley V. Stone
> BVS.Tools
> www.bvstools.com
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.