Lavish Software

I have same problem "wow.exe has generated errors and will be closed ... "

Sometimes I go to blue screen with a 0x000001E error.

I use WinEQ2 to do that in EQ all the time, but can't get it to work in WoW. This is not perfect but it might be ok for what you need, you will not be banned for using it:

http://www.solidice.com/keyclone/

I just can't log into WoW reliably with WinEQ2, but I get into EQ all the time with it....

Well seems to be working now, Ill post again if tehre are problems.

Windows Version: Microsoft Windows 2000/Service Pack 4/
System Physical RAM: 3032/3582MB

Kinda cool, my motherboard has a 512m vista ready boost memory on it so I can see 3582 in my 32 bit operating system, with 512m video ram.

I run 4 EQ on this machine fine, and I can start multiple wow without wineq. With Wineq I cant start a 2nd wow (not enough video memory) even though the first is only on the log in screen: here is the sysinfo after trying to start the 2nd wow and clicking ok on the not enough memory error box: WinEQ...

One of the other computers shows the EXACT same error:

Sun Sep 02 04:24:31 2007]00323:fatal error in main thread Code = c0000005 ADDR=0x00672073


So there it is.


3rd computer shows same error but at different memormy location:

addr=0x00459320

but right after the UI reset again.

Here is the EQ sysinfo.txt for the above crash after it crashed. WinEQ 2 System Information System: ----------------------------------- Windows Version: Microsoft Windows 2000/Service Pack 4/ System Physical RAM: 2025/2559MB Page File: 4074/4497MB Virtual Memory: 939/2047MB (Extended: 0MB) CPU 1: AM...

This is the loading world crash that is common after the newest patch in eq: [Sun Sep 02 04:24:30 2007]00300:Initializing cameras. [Sun Sep 02 04:24:30 2007]00301:Initializing lights. [Sun Sep 02 04:24:30 2007]00302:Initializing visual effects. [Sun Sep 02 04:24:30 2007]00303:Initializing target ind...

Humm ok logging in 4 and 3 out of the 4 crashed at the same time. It happens on all computers, but randomly. It does not happen during zoning. Also if you have one character from an account logged in and switch to another character from that account it usually won't happen. So it something that gets...

Well got in with a single instance on each computer this morning (with wineq running) with no problems and got out without the old message.

here is from the main computer and I think this was an everquest 1 client crash, just one the one instance only: WinEQ 2 System Information System: ----------------------------------- Windows Version: Microsoft Windows 2000/Service Pack 4/ System Physical RAM: 2049/2559MB Page File: 6865/7292MB Virt...

Using win2K sp 4 and 3 gig ram on all computers 6600 video on 5 and 7800 one 1 and athon 64 single cores.

I also am getting this problem ever since the patch. Its kinda random but is on all six of my machines, and seems most promenint when I try and log on six characters at a time (I think if I were to do it one at a time there would be less problems as I don't crash much when just one character tryes t...

If wowglider wins then "passive macroquest" and afk botting will possibly not be bannable. Lax might have more then a passing interest in this case. WinEQ is obviously legal though.

The post is mostly to inform Lax of the case in the event he is unaware of it.

http://www.theimageplace.net/uploads/7b600767fb.pdf In early 2005, MDY developed a software program under the name WoWGlider. WoWGlider is a software program designed to interact with the World of Warcraft. WoWGlider assists a player with in-game tasks in World of Warcraft such as advancing levels o...