OK NOW!! Thought I had learned my lesson regarding saving often and not saving over old files (rather saving 'em new in incremental fashion), but have once again run into files that VUE tells me it is unable to read!! This whole folder (see attachment) is *unreadable*!! Did nothing other than save the latest file (5.vue), exit VUE for a bit, and upon returning to work on what happens to be the first working idea I've had in Lord-knows-how-long...NOTHING!!! Both my brain cells are fried, not to mention a bit unhappy at this turn of events...so ANY and ALL ideas would be greatly welcomed?!? TIA!! ==steve

Well, the plot thickens! In looking thru' other folders/files that I have saved away waiting to be finished......at least that was the plan anyways...sighhhhh...it appears that more than 75% of THESE files ARE unreadable!!! Looks like time?!? for a re-install maybe?!? ==steve

If you have the *.bak fles, just rename them to *.vu and try to open it:-) Guitta

Well, i feel with you. Ok, i had unreadable files from time to time, but 75%? Huuhh that is serious. Are you sure that your system is ok? Especially when it comes to saving bigt files to disk? My gut feeling says that this sounds more like an individual system problem than a Vue one. Otherwise we would have had a lot of discussions here already. Which we hadn't. Again, sorry to hear something like this. Walther

Well, I'm still tryin' to figure this one out... Gebe, what I've been led to believe is that since I don't save over files (rather saving 1.vue, 2.vue, 3.vue)there are no .bak files...AND for wabe I just (in Poser) saved a file with MilDragon, 2 V3'S, and a Mikey2 (almost 46Mb) with no problem, so it, to me?!?, doesn't seem to be a machine or system issue... ==steve

Few days ago I got some Great help from MityPete about O/S. While working with his advices, I came up with a saving issue. Well certainly it wasn't as terrible as yours. I think you should make a test/demo image in Vue and save it. And then add few more things to it and save it under the same name. And follow the steps one or two more time. (The idea is to see if your Vue can STILL create a bak file & can open 'one name' saved file). Reboot your system and then see if you can open this file. If you can, then you know what is the cause. If the problem presist same as the series saving my bet would be, Vue is having a run time error with the O/S or explorer. Do a quick scan for viruses or bugs. The reason for my assumption is since it's 75%, but not all, that means the error doesn't occur every time. So, something is sticking it's nose while you working in Vue. See what other programs run in the background, they might play some role too. ... Presuming you are in Windows system. Sorry to hear your situation.

Steve, have you checked the sizes of your Vue files? Mine are normally between 100, up to 600 MB. Only very small scenes with nearly no vegetation are smaller 50 MB. I remeber how surprised i was when i founf this out. So my disk is mostly filled with Vue scenes now. First step could be in your case to defrag the disk. I always had the intention that my file problems came when something happened on my system while i was saving. Sort of runtime problems. Means that another program is doing an input/output at the same time and confuesed Vue. As Nish said as well. So you see, i still think that it could have to do with something related to your system. Because my feeling is that in my case it has to do with mine. And again, if it would be a Vue in general problem a lot more people would have this problem - the discussion would be very loud!

This may sound totally off-the-wall, but give your files different names, not just numbers, and see if that makes a difference.

Thanks for the input all! WILL give these suggestions a go! For wabe...it's definitely not a defrag issue as I have my machine set-up to defrag every nite! Soon as I've had some dinner, I'll build a test/demo scene as Nish has suggested. AND Spit, I assume you're referring to actually saving the files with 'names' as opposed to 'numbers' rather than just renaming 'em, 'cuz renaming (which I've already tried) doesn't help?!? AGAIN, thanks all!! ==steve

Seems to me that you have one of those old crappy Operating Systems. Turn to Win2k or XP and format to NTFS and you'll never need to whine anymore. The choice is up to you ;-)

John12, seems that you have a bad day. I even have this problem on my Mac with OS 10.2.6 - nothing to do with old Windows versions at all. I am using Windows 2000 Pro as well and can say that i havd never so many problems like this one. A complete new sort of problems that is true, but far away from a stress free system. I still think that the problem has to do with something else happening in a background process on this system. Virus check for example or something like this.