Page 1 of 1

WOD client exec error

PostPosted: Tue May 11, 2004 1:09 am
by Chelsea Duklain
Ok, we have a problem. We reformated both computers and got DSL instead of cable. We've downloaded all necessary files and everytime we try to get onto WOD we get this error message:

WODCLIENT caused an invalid page fault in
module WODCLIENT.EXE at 017f:0043809c.
Registers:
EAX=00000000 CS=017f EIP=0043809c EFLGS=00010246
EBX=00000000 SS=0187 ESP=00f5f524 EBP=ffffffff
ECX=00000000 DS=0187 ESI=01ee7199 FS=18e7
EDX=00000000 ES=0187 EDI=00000000 GS=0000
Bytes at CS:EIP:
8a 01 84 c0 74 14 3c 2c 74 10 88 84 14 94 01 00
Stack dump:
420f3dee 420f4630 3dee3dee 3dee3dee 00003dee 86b42056 00000fdc 29570ec2 22fc86b4 0009044f 20560000 0000895e 00000000 46044200 3dee000b 4604420f

It's a foreign language to me. Anyone know what the problem is? Thanks in advance!

PostPosted: Tue May 11, 2004 1:10 am
by simon
Have you fully patched everything?

PostPosted: Tue May 11, 2004 1:14 am
by Chelsea Duklain
According to my husband, we fully patched everything. He said to mention that we're using LBR and yes, we installed the 2D version.

PostPosted: Tue May 11, 2004 1:23 am
by simon
Windows isn't perfect, what version are you using?

PostPosted: Tue May 11, 2004 1:25 am
by Bayn
I assume you did the following:

1) installed LBR
2) patched it
3) downloaded latest WoD files from WoD site
4) unzipped WoD files into your UO directory
5) downloaded config file from WoD site and put that in your UO directory.

What operating system on the computers?

Did you do a Windows update on them after installation?

Do you have the latest directx drivers?

What client are you using? 2.x or a newer one? The 2.x comes standard in the usual WoD file download.

I can't analyze dump files either so I'm just tossing out questions. :)

PostPosted: Tue May 11, 2004 1:27 am
by Dell-Leafsong
I think that's the error I got once when I reinstalled and failed to get the WODLI.CFG file from the website. It could be almost anything else though.

PostPosted: Tue May 11, 2004 2:22 am
by Chelsea Duklain
Thanks tons everyone for even looking at this and offering suggestions. The error seemed to be a stupid mistake that we overlooked. We're back! Thanks again for your support. Yet another reason why I love this shard.