search

ashene64 / open-sauce

Automatically exported from code.google.com/p/open-sauce
0 stars 0 forks source link

Invalid Header #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
So I'm hoping you guys can give me some positive answers here that could bring 
me some hope.

A couple weeks ago I made a big mistake.  I was working within my Ubuntu system 
using the "DD" command to write a Fedora ISO image to a USB drive.  Instead of 
the USB drive I accidentally overwrote my windows drive with all my halo tags.  
Okay not good but not the end of the world.  I was due for a fresh install of 
windows anyways.  So I used the "DD Recover" command to create a .img file of 
the hard drive I just overwrote.  Afterwards I reinstalled Windows, HaloCE, 
Opensauce etc.  I successfully recovered all my files from the Windows IMG and 
repopulated my tags directory.  Now, thinking everything is back to normal I 
try to load a scenerio file and I find that all my tags created within 
OpenSauce Guerilla prompts me this error  "tag.shader_model) had an invalid 
header couldn't open tag"

I'll attach one of the tags that you guys can investigate and maybe bring some 
light to what is causing this problem.  Thanks

Original issue reported on code.google.com by halo0sta...@gmail.com on 17 Nov 2012 at 6:09

Attachments:

GoogleCodeExporter commented 9 years ago 
I was also able to recover the tags using Hek+ from a previous .yelo map I 
have.  Unfortunately I still had no luck with the OS Tags.  I could open all 
the tags created in normal guerilla but the ones created in OS_Guerilla still 
would not open.  If you guys know any secrets to extracting these files from a 
.yelo map I would love to hear from you.

Original comment by halo0sta...@gmail.com on 18 Nov 2012 at 7:47

GoogleCodeExporter commented 9 years ago 
I've already responded to your thread on halomods.com. Just as I thought, the 
data in those files is not actual tag data. The file records may have been 
recovered, but something overwrote the data to which the file pointers for 
these tags were referencing. Or the file pointers were invalidated.

As I said in my reply, we have no plans on adding any extraction features for 
OS-specific/modified tag groups.

Original comment by kornma...@gmail.com on 19 Nov 2012 at 12:29