2009-10-11, 04:35 PM
yes youre right, its not vmware's fault at all, i guess the warning should be double instancing SOM.
The thing that was really odd about it was I know how it happened, and what I expected to fix it didnt work.
It would seem logical to me that if you have conflicting data in a specific section of a file, especially one that is segmented in such a way as SOM files are (x number of slots per record then it moves on to the next record) that you should be able to just move further down the list of the record and fix the problem. i.e. if event # 50 was corrupted somehow i would think the way the file works i should have been able to go to event 51, or 52 and be able to do what i wanted, however when doing so whacky stuff was happening...for instance when i tried to move to event 51, and say make an event that played a sound when you approached a circle, it would end up being an event that i would have to examine and it would show me garbled text. very weird.
oh well, just be careful guys.
The thing that was really odd about it was I know how it happened, and what I expected to fix it didnt work.
It would seem logical to me that if you have conflicting data in a specific section of a file, especially one that is segmented in such a way as SOM files are (x number of slots per record then it moves on to the next record) that you should be able to just move further down the list of the record and fix the problem. i.e. if event # 50 was corrupted somehow i would think the way the file works i should have been able to go to event 51, or 52 and be able to do what i wanted, however when doing so whacky stuff was happening...for instance when i tried to move to event 51, and say make an event that played a sound when you approached a circle, it would end up being an event that i would have to examine and it would show me garbled text. very weird.
oh well, just be careful guys.
- Todd DuFore (DMPDesign)
Site Founder
Site Founder