I can only agree with you on this topic. MapInfo and HP don't go together smoothly. Recently we purchased some HP 8100N network printers and what happened: If these printers were set as 'default' in Windows NT, MapInfo (all versions) chrashed on startup with a strange errormessage. MapInfo techsupport had no solution other than 'don't use this printer as default', hooray for good support. I then experimented with some older printer drivers and solved the problem using PCL5e drivers instead of PCL6. I had no problems with the HP8100N in ANY other program than MapInfo. Johann -----Original Message----- From: Robert Crossley [mailto:[EMAIL PROTECTED]] Sent: 12. august 1999 05:02 To: 'Talbot, Gary W' Cc: 'MapInfo List' Subject: RE: MI 5.5 Printing of Raster Have you noticed that most of the printing problems seem to involve HP printers? I haven't had a problem printing to a NovaJet. HP's make great hardware but I think that their printer drivers generally suck. By any chance did you change your printer drivers or NT version when you upgraded from version 4.5? Does the problem fix itself if you use version 4.5 or were the features that caus the problem in printing just not available back then? Robert. -----Original Message----- From: Talbot, Gary W [SMTP:[EMAIL PROTECTED]] Sent: Thursday, 12 August 1999 5:17 To: '[EMAIL PROTECTED]' Subject: MI 5.5 Printing of Raster Well MapInfo People, I have decided to go back to version 4.5 once again. 4.5 is the best version that MapInfo has come up with dealing with Printing and raster images. I love the additions to 5.5 but will have to do without because providing prints to my clients is much more important than 3d thematic. When version 5.0 came out we had problems with raster concerning the transparent, so we called to get a fix and no response and now 5.5 comes out and it fixes the transparent bug but now it creates such enormous plot file that nothing will cure it. It is really funny that AutoCad can print out these huge files and MapInfo can not. I remember when Halos were a RAM intense animal and now if you use transparent on raster USGS quads it is RAM intense. I really think this should tell MapInfo Techies to work on how MapInfo allocates it memory and give it moment of their time to cure this problem. Take a look at Version 4.5 and see how it handle it because it works fantastic. Why did you have to go and change things. "If it ain't broke, don't fix it". Thank You for this forum to allow me to vent my whining. From Gary W. Talbott email: [EMAIL PROTECTED] phone: 562-491-2817 ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
