Hi all: My interest into Raster Engine Error 2 has reached a new twist. A quick background, for years I was able to print any size raster file to any size map. Then one day it would not anymore.
I have followed the "Raster Engine Error 2" issue over the years. It talked about backward compatibility issues with Windows 98, it talked about max. number of rows and columns in the raster print not to exceed so many cells, etc. It talked about work-arounds, screen captures and other tricks to coop. Then last month; An other county GIS MapInfo colleague called me with the same problem and explained that since he moved to a new hardware platform (the latest and greatest) he too was now having this problem. He is using XP; we use WIN2000, but used to use NT and 95 & 98 in the past. Thus, it used to work on any of those OS's. Hence, hardware platform became suspect. MapInfo versions also do not appear to make any difference (4.5, 5.0 5.5, 6.5, 7.0 all behave the same way). For kicks I fired a 30 GB ortho off to print from my oldest, almost museum piece PC; A 6 year old, AMD K6((tm)) 3D with only 256MB Ram. It huffed, it puffed, it spooled like crazy but in 35 minutes, it produced a 36 by 24 ortho. The Windows Task Manager showed the MEM Usage bouncing back and forth between 100 and 256 MB as it was spooling the image. But amazingly it produced about a 250MB printfile with the entire image on it. My current Dual 2.6, Xeon with 3GB of Ram will not do this. My old Pentiums 3, Dual 600 and 800 Mhz with 1 GB of Ram would not do it either. However, my old Micron Pentium 2, 300 would, so would my colleague's Pentium 4 Laptop using XP, but not his brand new raw horsepower workstation. When watching the MEM Usage in Windows Task Manager when it does not work, it climbs to about 1.1GB and then produces the Raster Engine Error 2. Somehow it will not use additonal available RAM, nor spool it to the harddrive. the 1.1GB seems to be the magic threshold beyond which it can go. The common denominator for failure appear to be the newer Intel processors perhaps with exception of perhaps a Celeron powered laptop used by my colleague up-north. Therefor, my latest work around for large print jobs is to save them in a workspace. Then go back to previous millenium AMD technology and let it rip. Obviously something else is going on here, but what is it? Anybody out there that has any ideas? Cheers, Jeroen Wagendorp, Ph.D., AICP Director, Allegan County Land Information Services 3255 122nd Ave, Suite 103 Allegan, MI 49010 Phone 269 673-0518 Fax 269 673-0361 [EMAIL PROTECTED] --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 12499
