A Land Far Away

Trying to open the Oct 10th Silverymoon module, I get 175 of these errors popping up. My worry is that they reflect corrupt resources, and the appearance of these errors is an indication that the toolset has become less corruption-tolerant- which is a good thing in the long run, but may be disheartening in the near-term.

I exported some of the areas from the Oct10 silvy module into a clean directory, though many of the areas wouldn't export (same sort of unexpected end of stream error). The Silverymoon exterior itself /did/ export without error, though it seems to trigger one error when opening up the new module. (better than 175 errors!)

I've uploaded the module directory to the DMFTP as AcadiusSilverymoon.7z in case anyone wants to compare- I only exported areas from the oct10 mod, not convos, NPCs, items, etc.

I tried to open an older Silvy module I have on my system, the one Indio sends to his builders with the Silvy exterior and some sample interiors. First I got an end of stream error and then it just kept loading and loading. After two minutes of loading I shut it down. Here's the error:

<a href="http://imageshack.us"><img src="http://img153.imageshack.us/img153/2504 ... roryo3.jpg" border="0" alt="Image Hosted by ImageShack.us"></a><br>

And yet, I trashed that old copy of Indio's Silverymoon and unRARed a new copy of it. This clean copy gave me the end of stream error and then opened up fine. All the prefab areas and the main Silvy exterior seem fine in it, too. Perhaps I'd made changes in the first copy I tried to open or perhaps my system just hung. In either case, I seem to be replicating your experience with the Silvy module, AL, for what it's worth.

I didn't touch any of the pre-fab areas, just the main Silverymoon exterior mod. If that works, great. That one would be the priority.

I'll check my current version, I get MOTB today or tomorrow. I now have a High Palace interior started and 18 forest exteriors that all use regular toolset stuff and should give no errors.

The fastest way to solve this is to export everything from the module in palette categories, make a new module directory, then reimport the lot.

After I'd done that, the error disappeared and the mod's behaved just as it used to.

Thanks, I'll do that and do a reinstall when I get MOTB.