CompuServe Messages

Gary, I figured that BROWSE was taking advantage of easy calls to internal 3D Studio code. The results are very good (image quality in the postage stamp), but decimation probably wouldn't have been too bad either. Or possibly utilizing a quick & dirty routine for images over a certain size. The use of Photo CD, digital cameras and scanned images makes the indexing time a little frightening though. Part of my problem was indexing some print files with only 16MB RAM. Quite a number of page faults from indexing. Yes, I could NOT cancel indexing on a CD-ROM (I was trying to index the WCT from 3DS R3). It continued to index file after file after file despite key presses and mouse clicks. This only seems to occur when the index is non-resident (index the CD, store the index in \3DS3 on the internal hard disk). Cancelling worked fine when just indexing directories on the hard disk. Regarding re-indexing – perhaps in the future at least a date/time check on the image file & ability to copy sections of the previous index? I killed one indexing due to time constraints, which blew away the previous index. What, no .BAK file? Please remember that any criticisms I may make are in the interest of everyone having access to better products, and all of us being more successful. Kevin Krell – Computer Support Associates