CompuServe Messages

>> I had a similar problem using Personal Netware. The Map paths embedded in the project to be rendered pointed to drives that didn't exist in the context of the slave. When I removed these, it worked. << What a timely reply particularly re: >> pointed to drives that didn't exist <<!! Brian Rudolph's [Adesk] reply/advice about the locations of the different types of temp files/locations lead me write a short COM program earlier this week for determining if a drive is available. It returns an errorlevel code, which a batch file can then use to help select the appropriate *.SET file; ie., if the drive is available, use the SET file which uses that drive, if not then use an alternative SET file. I've started using it with a 3DS SET file to send related TEMP files to the removable drive when it is there, an more importantly, not sending TEMP files there when it is not there ;-). Whether the notion of sending the TEMP files to the removable drive _actually_ works is another matter… The program, ISDISK.COM, has only been tested on my machine. So far it has worked with a CDROM, SYSQUEST removable drive, and the floppy drives. It will only run in DOS due to its use of DOS interrupts, however running it from a DOS window in Windows works, too, of course. If anyone in these environs think they could use it, I will load it along with the C source code onto one of the ASOFT libraries for either free usage or an all-expenses-paid trip to somewhere sunny and warm 😉 Cheers, Chas -Charles Dixon