<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> When I built the science and simulation collections for distribution with PLaneT, I included pdfs of the reference manuals – for example, the science-ref.pdf file size is 677KB.  I built and tested it on my development machines (both Windows and Linux), which have at least 1GB each, and they work great.<o:p></o:p> <o:p> </o:p> As a test, try ‘(require (planet “science.ss” (“williams” “science.plt” 2 0)))’ or ‘planet –i williams science.plt 2 0’ from the command line.  On a 1GB machine. a minute or so later you have the science collection installed and compiled on your machine.<o:p></o:p> <o:p> </o:p> I went to demonstrate it on another machine, which had only 512MB, and five minutes later we had a very non-responsive machine and Drscheme eventually died – with a corrupt installation of the collection.  I tried it on various machines with the same result – any machine with 1GB or greater it works and anything 512MB or less it fails.  I tried various combinations of virtual memory settings and had the same result.<o:p></o:p> <o:p> </o:p> Watching the memory usage on task manager – yes, a very scientific way to do it J – shows that the process grows slowly until it fills memory; then it shrinks back to a couple tens of megs before finally dying several minutes later.  No errors are reported in the PLaneT install-log.  The science-ref.pdf file is corrupt (I assume truncated, but I didn’t check) and nothing after it is installed.<o:p></o:p> <o:p> </o:p> I will rebuild the .plts without the pdfs and that should fix the problem.  But, in looking over the unpack module in setup, it seems to go out of its way to avoid having the entire file in memory during the deflating process.  So I’m curious as to what is going on.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> <o:p> </o:p> M. Douglas Williams, Ph.D.<o:p></o:p> Sr. Scientist<o:p></o:p> Science Applications International Corporation<o:p></o:p> 4B <st1:Street w:st="on"><st1:address w:st="on">Inverness Drive East</st1:address></st1:Street>, <st1:address w:st="on"><st1:Street w:st="on">Suite</st1:Street> 210</st1:address><o:p></o:p> <st1:place w:st="on"><st1:City w:st="on">Englewood</st1:City>, <st1:State w:st="on">CO</st1:State>  <st1:PostalCode w:st="on">80112</st1:PostalCode></st1:place><o:p></o:p> office: (303) 217-4421<o:p></o:p> cell: (303) 229-0315<o:p></o:p> <a href="mailto:m.douglas.williams@saic.com">m.douglas.williams@saic.com</a><o:p></o:p> <o:p> </o:p> </div> </body> </html>