CompuServe Thread

#POV Bug?

4 messages in this thread
#21298From: Jim Orleff RST/NATCAMay 3, 1993 11:08 PM
#POV Bug? — declared parent_msg_num=(none), resolved parent_id points to #(none)
Hi, I used a batch file with POV to generate graphics while I slept. When I awoke the hard drive I had been writing to was trashed big-time. I suspect it ran out of room, but the partition table, FAT, directories i.e. my whole world were gone. Thank God for back-ups. Anybody heard of this happening before? There are 2 Replies. Read action !
#21323From: Dan FarmerMay 4, 1993 9:03 AM
#21298-#POV Bug? — declared parent_msg_num=21298, resolved parent_id points to #21298
Jim, I've run out of harddrive a lot of times (doing animations from batchfiles. Never had anything like that happen. You using any sort of stacker-like compression or anything else unusual? There is 1 Reply. Read action !
#21348From: Jim Orleff RST/NATCAMay 4, 1993 3:37 PM
#21323-POV Bug? — declared parent_msg_num=21323, resolved parent_id points to #21323
type Hi Dan, Glad to hear it isn't common. I have stacker on drive C but drive D where the incident occurred is pure IDE uncompressed DOS 5.0 flatland. I am running a 486 33 and have never had anything like this happen before. I don't even know that POV caused it but it and the batch file were all that was running when I went to bed. Could be something related to the drive itself I suppose. Anyway thanks for the reply, I'll keep checking. Read action !
#21473From: Eric BarishMay 5, 1993 10:12 PM
#21298-POV Bug? — declared parent_msg_num=21298, resolved parent_id points to #21298
I've also run out of space on my hard drive this way, but I've never had any real problems. I occationally get bad files, but I think it's strictly the swap file and TGA files (it happens generally when I RESET out of POV). They always clean up fine with Norton. There was a problem I had twice, but I don't know if POV was involved. One sector (same one twice) of my root directory got trashed, and I had to go into Norton and do some repairs by hand, but no data was lost. According to your description, it sounds like *something* in the DOS enviroment was at fault. Even an out of control program isn't supposed to get easy access to those areas. $0.02 signed, Not-A-DOS-Expert <G> Read action !