Author Topic: Module Corruption  (Read 648 times)

Legacy_Rosinbag

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
Module Corruption
« on: September 16, 2014, 04:35:21 am »


               

So I have Neverwinter Nights Diamond Edition and I love that you can make modules but whenever I try and make one it gets corrupted. Sometimes it will get corrupted soon after I create it and other times I will be able to waste a ton of time and effort before it gets corrupted. All that it says is:


"Could not open module


Reason: Invalid Header.


It is possible that this is not a module file or that the file is corrupted."


 


I would like to make a module so if you guys have a solution to this problem that would be greatly appreciated.


 


Thanks.



               
               

               
            

Legacy_BelowTheBelt

  • Hero Member
  • *****
  • Posts: 699
  • Karma: +0/-0
Module Corruption
« Reply #1 on: September 16, 2014, 11:53:44 pm »


               

Is this a new install of NWN?  Did you get it from GoG.com?


 


Have you run the 1.69 critical rebuild patch



               
               

               
            

Legacy_Tarot Redhand

  • Hero Member
  • *****
  • Posts: 4165
  • Karma: +0/-0
Module Corruption
« Reply #2 on: September 19, 2014, 06:01:03 pm »


               

This used to be a problem in the old days. If the solution that BelowTheBelt has suggested doesn't work for you there are a couple of other things to try. The first is to save often. The reason for this is not just the obvious one. If you look in your modules file once you have saved a couple of times, as well as your module file (ends in .mod) you should also find a backup mod (ends in BackupMod). This backup is a copy of the module previous to the last saved one and may well not be corrupted. By deleting the faulty mod and then changing the extension of your backup (from BackupMod to mod) you may well be able to retrieve some of your work.


 


Also if the 1.69 critical rebuild patch does not work to fix this problem, it is just possible that you may have a problem with your hd so run windows disk checking utility.


 


TR