According to our MIS department here. I found out why the Custom Symbol Library does not work under Windows NT NTFS file system. Seems as though MI has develop the program to run under the DOS fat 16 system instead of developing the program for both file systems. The DOS FAT16 is used for troubleshooting tools within NT, and really should not be used for this purpose. If anyone has any information our solutions for me to relay to our MIS Dept, or a workaround on this please let me know. Tech Support has suggested that I save all the custom symbol files as 24 bit instead of 256 bit (Does not work). Some of us users need to make Custom Symbols for other uses, within a Network environment. The way Microsoft is developing the next versions of Windows & NT MI better follow suit also. If this is true who do we gripe to, MI has record of the problem under known problems. Richard Takacs Project Manager Hyperion Communications [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]
