After spending some time tracking down an elusive bug in the Warhammer 40k files, we discovered an interesting ummmm feature.
Files in the data directory that are marked read-only are not replaced when a datafile is imported, nor are files deleted that aren't replaced by the update if they are marked RO.
While this is a usefull method of protecting user's augmentation files, is the non-replacement by design? abexport will copy the read only bit, and set the imported file as such. The importer should either set all the read-only bits to 0 or overwrite the replaced files, or at the least, warn the user that the file wasn't replaced. Leaving non-replaced files that are marke read-only alone is a benefit though, as it eliminates the need for people to back up all their augmentations before an import. Maybe mention should be made of this is the documentation.
Cheers,
--
Graham H. Tracey - aka ImhotepTheArchitect
I'd rather have a full bottle in front of me than a full frontal labotomy.
40k3 AB Group: groups.yahoo.com/group/ab-40k3
40k3 AB Files: groups.yahoo.com/group/ab-files/
---------------------------------
Do You Yahoo!?
HotJobs, a Yahoo! service - Search Thousands of New Jobs
[Non-text portions of this message have been removed]
------------------------ Yahoo! Groups Sponsor ---------------------~-->
4 DVDs Free +s&p Join Now
http://us.click.yahoo.com/pt6YBB/NXi....GAA/IMSolB/TM
---------------------------------------------------------------------~->