Re: MI MapInfo 4.5/5.0 Hardware Specs (Universal Translator Problems)

[Warren Vick, Europa Technologies Ltd.]

Hello Frank,

> I was wondering if anyone could give me some help in 
> determining the best hardware options for MapInfo. I am currently using MapInfo 4.5 
> in Windows 95 with a P133Mhz, 32 MB RAM. I will be upgrading to MapInfo 5.0 
> as soon as I purchase a new system. The problem is in deciding on the best 
> hardware configuration for MapInfo 5.0
> 
> I am a geologist and have been using the Universal Translator 

The UT can be memory hungry. I've monitored memory usage on a system during some large 
translations and it can go through the roof.

> Unfortunately if  I try speed up the process by using the Table>Import option in the 
>"DXF 
> Import Information" window there is only 1 dxf layer listed, and the create 
> separate tables option is not available. Therefore by using the Table>Import 
>although 
> it is quicker the end product is one table with all of my data. This is of 
> very little value to me.

This could be automated to save on the manual interaction. Its probably a relatively 
small 
development job.

> I have also been using Vertical Mapper V.2 to contour 
> elevations, soil data etc. Once again some of these files are very large (i.e. 
> 35,000 plus elevation points) and the system I am currently using will stall in the 
> process of making contours at about 75%.

VM2 is pretty hungry on memory too. I hit over 500MB of committed memory recently 
during a 
complex operation. Ask Northwood if there is a limit on memory/disk consumption during 
contouring operations. 
 
> What I would like to know will MapInfo run better on Windows 
> 95/98 or Windows NT? Will MapInfo recognize a dual processor if it is run on 
> Windows NT? 

A negligible speed difference between each OS. If there are NT drivers available for 
everything you 
want to attach to the new system, I would go for NT4W.

> In the procedures described above am I better off to invest more of 
> my resources on RAM (how much is optimal)/ CPU speed or hard drive subsystem 
> (EIDE, SCSI). What about video display?  Any other spec that 
> should be considered??

I swear by SCSI disk systems - go for the highest spec you can, I use Ultra-Wide. VM2 
is doing a 
lot of maths and run-time will be highly dependant on the processor speed. Memory 
seems to be 
enjoying a cheap spell again so it shouldn't put too much of a dent in you budget. I'd 
start from 
128Mb for an NT based system. Make sure you don't fill all the memory banks 
immediately so that 
you have room for expansion. 

As I mentioned in another post, I believe the graphics card is less important. If it's 
a modern card it 
will be fine for MI/VM2 use. You could get one which has plenty of memory in order to 
support 24bit 
colour in hi-res, but this doesn't come without it's problems. e.g. raster style and 
transparency 
problems in MI.

In conclusion, optimise disk, memory & processor and make sure graphics card, monitor 
size, 
etc. is more than adequate. The most important things to think about are items that 
are either 
costly or not easy to upgrade.

Regards,
Warren Vick
Europa Technologies Ltd, U.K.
www.europa-tech.com
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]