UOX3.org

I've recently upgraded to the new release of UOX3 v0.99.1. I have gotten an intermittent ntdll.dll error on my Windows 7 Professional pc. It occured after an automatic world save and the following garbage collection. I use Razor to launch the client. I only logged in as my GM. I would ride my horse around going through the standard moongates and using the "go place" command while eyeballing the location.dfn.

***On a completely separate, but possibly related issue, now that I'm thinking about it, UOX3 seems to freeze when I go between the UO client window, Razor and some other windows program at about the time of a world save or garbage collection. However, if I don't flip between any other windows proggy while playing...no problems.


Here is ALL of the info that I could gleen from the error window:

Problem signature:
Problem Event Name: APPCRASH
Application Name: uox3.exe
Application Version: 0.0.0.0
Application Timestamp: 4f69572f
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec49b8f
Exception Code: c0000005
Exception Offset: 000332a0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789



I'm not sure if I performed the installation correctly because many moons have past since my kids and I have played. I have also been experiencing this ever growing urge to play ever since I started re-reading my collection of DragonLance novels over the last month or so. My installation went like this:
1. I archived my old version of UOX3 and UOML.

2. I unzipped uox3all-in-one_0_99_1.zip to my UOX3 folder.

3. I downloaded and installed UOClassicSetup_7_0_10_3.exe.

4. I deleted the new Accounts folder and replaced it with the Accounts folder from my previous UOX3 installation.

5. I deleted the new DFNData folder and replaced it with the DFNData folder from my previous UOX3 installation.

6. I moved the contents of my Shared folder from my previous UOX3 installation to the new installation. This included all of the MUL, WSC, resource[#].BINs, regions.bak and multi.idx.

7. I deleted all of the MUL files and multi.idx from the Shared folder and replaced them with the newer versions from the UOClassicSetup_7_0_10_3.exe installation.

8. I replaced my spawn.dfn with dragon slayer's Spawn V1.0.

8a.I know that he's planning on adding to it but I had go into comment out the following to prevent some errors: GazerLarva, SkeletalKnight, skeletonaxeman, Executioner and SkeletalMage.

8b.I was also getting an error on the fire elemental too but I can't remember or find which files I modified to fix it. Although I am sure that it was a naming convention discrepancy between "firele" and "fireele". I used the latter.

9. I commented out the default "_mg_" in the teleport.scp.

10.I added some of dragon slayer's other custom stuff including the farming/fishing quests, pink champaine, holiday tree deed, arcane circle, random brigands, elemental knights, floating npcs, frost elves, rat variety, xmas gifts, city snow globes and holiday bells;.

11.I am also getting an error with Razor which says "Razor was unable to locate and load a suitable UO cliloc file. Some text may not be displayed." I was thinking that it has to do with a client localization file of some sort.

12.Of course I changed the necessary settings in the uox.ini file as well.


I hope that this is enough info to find a solution. If not, lemme knows. I sure hope that the original problem doesn't turn out to be the infamous "ID-10-T" problem.

First time I'm hearing about this error (with ntdll.dll) in relation to UOX3. I'm using Windows 7 myself (64 bit), and have not experienced this myself. It's very hard to say what could be causing that error - it could be faulty memory-chips in your computer, it could be conflicts with other software running on your computer (antivirus/security-software, for instance), it could be some obscure bug or option in UOX3 that is hard to pinpoint. A quick google sees that specific error turn up in all kinds of programs, from Explorer.exe to games like Skyrim and Battlefield 3. :/

A couple of things you can do to try to pinpoint where the error lies, though:

1) Run a "clean" version of UOX3 0.99.1, with no custom scripts and without replacing any of the files or folders from earlier versions, and see if it's still happening.
2) Try this alternate UOX3 exe (based on CVS source), where I have switched around the compiling options a bit to see if there's anything in those options (which I changed specifically for the latest UOX3 release for some performance boosts) that could be causing this.
3) You can run a memory diagnostic tool to rule out faulty memory chips.
4) Try to disable anti-virus/security software and see if it still happens. If this makes you uncomfortable, unplug your computer from the Internet while having these softwares disabled.
5) Follow this Microsoft-guide to do a "clean boot" and minimize the amount of possible software/services-conflicts that could occur, then try to pinpoint which software/service is causing the conflict.

Btw, if your UO client-screen ever goes all "white" (as if frozen) when you switch away to other programs and then back, this is very likely a Razor-issue with Windows 7. You should be able to fix it by running Razor in Windows XP-compability mode (right-click on Razor.exe -> Properties -> Compability -> Run program in compability mode for: Windows XP (Service Pack 3).

Note about upgrading UOX3: If you overwrite the entire DFN-folder in a new UOX3 version with the same folder from an older UOX3 version, chances are you will lose out on whatever DFN-specific fixes/additions have been made for the new UOX3 version. A better method for upgrading is to only copy over files from the older folder that you know you have edited and still need, and only after having compared the two to see what the changes are. This can easily be done using a free program like WinMerge, which can compare files in two folders and give you list of files that are different between those folders, and will also highlight the changes in each files and allow you to copy/merge from one to the other.

One additional tip related to upgrading is to keep all your custom DFN-stuff in separate definition-files that you create yourself, which means they will never be overwritten or overwrite newer files when you upgrade to a newer UOX3 version. UOX3 will read all .DFN files that are present in any given folder, as long as the data they contain has the correct format and does not conflict with data in other .DFN files.