|
Martin:
Welcome to a very irritating and persisting problem
with MI. I am glad to hear you have this problems as well "down under" so as to
eliminate seasonal and rotational causes.
I posted a similar message on 6/23 and got quite a
few responses (By-the-way, thanks to
all who responded). Some with advice, some with "learn to live with it". I had edge matched 24, USGS DRGs 7.5 minute "topos" together to cover our county with about 52,000 parcels "over the top". At 1 :24,000 (now in theory only as it turns out) I had planned to run two landscape 36 x 108 inch panels. It will not even create the print files. It will print the first 48 inches or so either on paper or to a file and that is it all. This in postscript 3 on a HP 2500 CP with Max RAM. In HPGL/RTL I am running 1 in 10 chance to successfully print in portrait a 36 X 72 inch map (still working on the same above map but now with three vertical panels). I have to limit copies to 1. I have to increase the Page File to about 1.5 - 2.0 GB. I have to reboot (NT 4.0 + all serv. packs) and go straight to the workspace. I can not run anything else, no CD's, no internet, and nobody can access my machine for data, including data management for daily backup or it will be sudden death for the print. In MI under print options under "advanced" under "process options" activate "in computer". The hard drive space in your printer will max out in no time otherwise. I also reboot the printer. It is now 5 PM I touch off this unstable mix and go home. Sometimes I have a map in the morning other times like this morning it printed all but one inch and I get to try it all over again at 5 PM. It is not the file size. I can print in postscript 36 square miles of ortho imagery with a one foot pixel. The print file will be something like 1020 MB. But try not to exceed the magic 48 to 60 inch (this also still variable) paper size limit. When attempting foolish things in MI like printing to 108 inch wide maps I notice in "Task Manger" (I am running Micron Powerdigm Dual 300 MHz, 256 RAM) a level of activity normally not seen in MI. Both processors will max out and the Page File Mem Usage will be huge. When attempting the same foolery in postscript it appears not to be the size of the Memory Page File that potentially kills everything but just available hard drive space allocated to your TEMP file. My ultimate quest is to print a 24 GB (probably resampled down to 2.4 GB by increasing pixel size to 3 feet) countywide 40 X 24 mile ortho image for the entrance hall wall of the county courthouse, since an image such as this one, 6 x 9 feet, will do more for my future budgets than a dozen refereed articles in obscure journals. It appears that I might have to print this in TNTmips where I do not have these problems or heaven forbid in the new ArcInfo 8. Lets hope it does not have to come to this. Jeroen Wagendorp, Ph.D., AICP Director, Allegan County GIS p.s.. if you sensed a level of frustration you're absolutely correct. ----- Original Message ----- From: Martin Higham <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, July 02, 2000 10:15 PM Subject: MI - Long plots to HP1055 > Hi, > > A client has a problem plotting 1500mm (=59") long PostScript plots on an > HP1055. The correct length of paper is produced but the printed output > stops at 1170mm (=46"). > > The plots are OK using HPGL/RTL on the HP1055 and are also OK using > PostScript on an HP755. The HP1055 also produces long PostScript plots from > software other than MapInfo. > > Any ideas ? > > > Best Regards, > > Martin Higham > Manager - GIS Services > > Encom Technology > PO Box 727 ph 61 3 9428 4088 > Richmond fx 61 3 9428 0470 > Vic 3121 mob 61 3 624 117 > Australia www.encom.com.au > > ---------------------------------------------------------------------- > To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put > "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] > |
