[WoW] [5.4.0 17359] Release x86 Info Dump Thread

[jh16]

I know this is a longshot but has anyone found the location of the subroutine that determines whether or not to continue running the 32-bit or to switch to the 64-bit client depending on what your system type is?

I was thinking about all of the people that are having to rename the 64-bit client just so they can use the 32-bit client. Maybe there is a way to force it to run the 32-bit version?

My current knowledge is limited to only finding the locations to allow custom patches to be applied. If I only knew what to search for. =\

Thanks for any help.

(meanwhile I'll continue trying myself...)

[andy2002ua]

There is launcher option to force start x32 client, but seems not working.

[jh16]

There is launcher option to force start x32 client, but seems not working.

The reason it isn't working is there is something in the code of of the 32-bit client that checks the Operating System type and if it reads it is a 64-bit OS then it runs the 64-bit client. Really stupid of Blizztards programmers to do this to us. They pulled this stunt on us on the PTR and it worked its way into the Live client. =\

I was thinking maybe to trick the 32-bit client into thinking the OS is a 32-bit system. That is if it is possible.

[_Mike]

The reason it isn't working is there is something in the code of of the 32-bit client that checks the Operating System type and if it reads it is a 64-bit OS then it runs the 64-bit client. Really stupid of Blizztards programmers to do this to us. They pulled this stunt on us on the PTR and it worked its way into the Live client. =\

I was thinking maybe to trick the 32-bit client into thinking the OS is a 32-bit system. That is if it is possible.

-noautolaunch64bit
Or patch byte 10AC9C (file offset) / 10B89C (memory offset) from 09 to 00, or patch GetNativeSystemInfo to return PROCESSOR_ARCHITECTURE_INTEL as cpu arch.

[Jadd]

The reason it isn't working is there is something in the code of of the 32-bit client that checks the Operating System type and if it reads it is a 64-bit OS then it runs the 64-bit client. Really stupid of Blizztards programmers to do this to us. They pulled this stunt on us on the PTR and it worked its way into the Live client. =\

I was thinking maybe to trick the 32-bit client into thinking the OS is a 32-bit system. That is if it is possible.

Just start the launcher/client with compatibility mode?

[doityourself]

just rename the wow-64.exe to idk wow-bla.exe and you can run the wow.exe

[jh16]

-noautolaunch64bit
Or patch byte 10AC9C (file offset) / 10B89C (memory offset) from 09 to 00, or patch GetNativeSystemInfo to return PROCESSOR_ARCHITECTURE_INTEL as cpu arch.

Really good info, I tinkered around and I found the "-noautolaunch64bit" thing on my own but didn't think of looking at the GetNativeSystemInfo part (didn't even know it existed until you told me). I had several attempts which ended with either a failure or WoW instantly crashed.

By knowing there was GetNativeSystemInfo I was able to successfully edit the 32-bit client to not run the 64-bit client by editing the following location through a hex editor:

at offset 0000 DE75 replace E8 0C CE 0F 00 with
90 90 90 90 90

Thanks a bunch _Mike! Now I can put this info in with my post for those that want to run the 32-bit client for custom patches.

+rep when I'm off cd!

[-Ryuk-]

You can also just delete the wow-64.exe

[andy2002ua]

Who can share the method of determining D3Device offsets for DirectX9 (while in process) ? Trying to use CreateDevice(...) in injected DllEntryPoint by Apoc ([C#][Patch Independant] Getting the IDirect3DDevice9 Pointer), but unsuccessfully. Always got D3DERR_INVALIDCALL error. (When compiled in separate program, d3d device created successfully).

[imzz]

The "World__Intersect" offset is “005E054C” do?
Why the old code does not work, the parameter change?

' push GUID_h
' push GUID_l
' call Base + Interact
' add esp,8

[andy2002ua]

The "World__Intersect" offset is “005E054C” do?
Why the old code does not work, the parameter change?

' push GUID_h
' push GUID_l
' call Base + Interact
' add esp,8

Don't mix up Interact and Intersect, it's absolutely different functions.
int __cdecl CGGameUI::Interact(__int64 guid) at address 'wow.exe' + 0x8BA907 (not checked, just diff result)

[imzz]

Don't mix up Interact and Intersect, it's absolutely different functions.
int __cdecl CGGameUI::Interact(__int64 guid) at address 'wow.exe' + 0x8BA907 (not checked, just diff result)

Thank you！！

[rainren00]

Public Enum Groupoffset
Partyptr1 = &HDAA1AC
Partyptr2 = &HA0
Raidptr = &HDAA1B0
MemberGuid = &H10
End Enum

[evil2]

There is launcher option to force start x32 client, but seems not working.

btw you only need these 4 files in your main directory to run wow (multiboxer will know)

DivxDecoder.dll
Scan.dll
Wow.exe
WoW.mfil

[szKaXo]

CTM_Base = 0x00CF99D0,
CTM_Push = 0x1C,
CTM_X = 0x8C,
CTM_Y = CTM_X + 0x4,
CTM_Z = CTM_Y + 0x4,
CTM_GUID = 0x20,
CTM_Distance = 0xC,