Virusbarrier X6 scan says DP7.21 files are corrupted

[mess]

Wait, so none of these files are actually causing any issues?

There once was a time in OS 9 where DW and other similar utilities would BASH the resource forks of DP files, actually causing them to be unusable. I would just go in and exempt the DP file type from the scan, this will prevent anything from happening to the files and alleviate your fears.

[1nput0utput]

Wait, so none of these files are actually causing any issues?

After reading this thread and the other one about this topic, that's my understanding. I have many DP project files that have been saved by various versions of the program, and I haven't noticed any problems opening or saving them with DP 7.2.1. I don't doubt that something in the resource fork is getting smashed, and that is probably a bug that MOTU can fix. I simply don't care unless it has real consequences.

[mess]

Based on the info here, the only thing getting bashed is the file version number. All data is still intact.

A missing file version is not going to cause the OS to go down, force the computers processors into a heated tailspin and then set fire to all my comic books that are in my basement fortress, err, I mean, studio, will it?

</serious business>

[sinkd]

Wait, so none of these files are actually causing any issues?

I am having this same issue (tracked with Disk Warrior) and I believe that it is causing me to be unable to save mid project on some files that were created with older templates. I have to keep saving with a new name.

[mess]

Well, that sounds like a template issue. How old are your templates? It's well known 'round these parts that old templates sometimes clog up the gears and cause some maddening behavior.

[sinkd]

Very well could be a template problem, but one of the files is an original, (re-built in DP 7.2)

[monkey man]

Based on the info here, the only thing getting bashed is the file version number.

No, it's the only symptom that's shown up so far with real-world use that we're aware of. A symptom a problem doesn't equal.

All data is still intact.

How do we know this? All we know is that one tiny set of data is missing or incorrectly published (explaining its being omitted from Get Info). To assume everything else is just dandy only because that which we know to be "missing" is benign, is illogical IMHO.

A missing file version is not going to cause the OS to go down, force the computers processors into a heated tailspin and then set fire to all my comic books that are in my basement fortress, err, I mean, studio, will it?

No, but other data that's possibly missing may indeed have as-yet unforseen consequences, mess.

I think I was the first to stumble across this issue, mess, and I'll be more than happy to embrace a sense of relief should MOTU declare the "problem" solved or provide a comprehensive explanation for us. For now, I know some of us may appear to be worry pots (or is that potty worriers?), but I'd rather be a worry pot with a problem than a careless 'Cornie with a problem I'm not aware of, if that makes sense.

[James Steele]

Okay... good news everyone. I *did* manage to send an email to a MOTU contact and let them know about this thread. It's not a dangerous issue as others have pointed out and projects playback normally, but it does need to be fixed and they say they've figured out what was causing it and it should be fixed in the next update. WHEN that is, I have no idea and they never tell, but they know about it and it's going to be fixed.

[Phil O]

Thank you, James. That is good news indeed!

[1nput0utput]

No, it's the only symptom that's shown up so far with real-world use that we're aware of. A symptom a problem doesn't equal.

The absence of other observable symptoms does not guarantee hidden symptoms, which is what you seem to be implying. There are much better software problems than this to twist your panties with.

[James Steele]

Well, the problem is with the project file itself. Whenever the next update comes out, this will be fixed and apparently all that will have to be done is simply re-saving the project file. Audio files aren't affected, so no need to duplicate audio.

[bayswater]

better software problems than this to twist your panties with.

Maybe for the next avatar, MM? (I think he means knickers)

[monkey man]

Great suggestion, Baysey. Maybe Paris'll lend me a pair...

No, it's the only symptom that's shown up so far with real-world use that we're aware of. A symptom a problem doesn't equal.

The absence of other observable symptoms does not guarantee hidden symptoms, which is what you seem to be implying.

No, all I said was that we're only aware of that one symptom thus far. The obvious implication was that there may have been others, or indeed an underlying issue with the app, and that we'd be foolish to assume the absence thereof.

There are much better software problems than this to twist your panties with.

Agreed, but then again, not knowing the full extent of the problem by definition precludes its being compared with real knicker twisters, IMHO.

[James Steele]

Bump!! This problem is now fixed with DP 7.22!! I opened some projects that had this problem and simply toggled a button on the Control Panel (to "dirty" the file) and then "Saved." File is fine now. Just open and save all the project files that had this error in DP 7.22 and you're good to go!

[monkey man]

You bloody ripper! Thank you, James.

... and thank you MOTU! I hope the files I trickled to tech support helped in some small way.