CompuServe Thread

#File Deleting Problem

4 messages in this thread
#68045From: KeyframeNov 24, 1993 4:59 AM
HELP ME !!! I am losing a lot of valuable data from within 3d Studio, it seems that whenever I view an images from within 3ds that is on a network drive, it erases it. Why Why Why… It used to do the same thing from within 3ds r2 but I foolishly thought that r3 had solved this problem as it does not happen all the time, the network is Novell Lite, I can use un-delete utilities to retreive the file but this is not really a good soloution as you can imagine. I am not using any memory managers, the network works fine in all other pieces of software that view images. What else can I say, I have 32 megs of RAM plenty of disk space tried dos5 dos6 dos6.2 drdos6. Novell say they know of no conflict and I am sure that other uses don't have this problem. Can anybody save my life. ps. I am taking a short holiday tommorow (25 November) but will be back on tuesday – wednesday next week, I hope by then I will have one or two suggestions to try. Thanks. Phil.
#68087From: Brian Rudolph [Adesk]Nov 24, 1993 10:48 AM
This is not a problem I have ever heard of before. It Sure sounds weird. What other TSR's or devices are you loading? Things like virus protection, disk compression, etc… Do you have both read and write capabilities on the driver you are reading from? -Brian
#68094From: Yost GroupNov 24, 1993 10:53 AM
I'm surprised you've held onto this problem since R2. I've never heard of it (including in R2), and don't really have a suggestion for you. Since you're not the only one taking off for Thanksgiving, this might not be the best time to leave this message. If you don't get any responses, I'd recommend you send it again when you get back. And, since you've waited this long, you might send it again in the first week of December after Gary gets back.
#68105From: ALAN IGLESIASNov 24, 1993 11:42 AM
Hmmmm…I've never heard of anything like this before, but the facts that (1)It only happens on network drives, and (2)It happened with r2 as well as r3 really makes it look like a network problem, perhaps a conflict with Pharlap and the Net bios. You could try moving/excluding the addresses around with QEMM and see if that makes a difference. Good luck, -Alan Iglesias