[Release] LuaNinja - Run protected Lua code

[Cypher]

I don't think I made myself clear. Runtime injection works, I am referring to either using a batch file (Loader_IA32.exe --launch="C:\WoW\WoW.exe" --module="LuaNinja.dll" --export="Initialize") or even your own GUI loader and its 'Launch' radio option.

Edit: The WOW process just hangs when I do either of the methods above.

What error do you get when trying to use the launch method?

[armen]

Problem Event Name: AppHangB1
Application Name: Wow.exe
Application Version: 3.3.0.10958
Application Timestamp: 4b157b80
Hang Signature: 9bc1
Hang Type: 16897
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Hang Signature 1: 9bc13c8411136884be1e7113e005485f
Additional Hang Signature 2: 2ce0
Additional Hang Signature 3: 2ce0791acc37132c285ffe6f7f64a73f
Additional Hang Signature 4: 9bc1
Additional Hang Signature 5: 9bc13c8411136884be1e7113e005485f
Additional Hang Signature 6: 2ce0
Additional Hang Signature 7: 2ce0791acc37132c285ffe6f7f64a73f

[CrazyCactuaR]

Using the setting's you have on the front page wow.exe will open but the program stay's as a white screen and requires task manager to close. That's using the launch process and IA32.

Choosing AMD64 will produce the following error;

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.21006.1 (B2Rel.021006-0100)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.21006/mscorlib.dll
----------------------------------------
LoaderGui
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///E:/World%20of%20Warcraft/LoaderGui.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.21006.1 built by: B2Rel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.21006.1 built by: B2Rel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.21006.1 built by: B2Rel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.21006.1 built by: B2Rel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Logging into the game manually, selecting the char and then using the Process on your launcher applies its self fine and lua code's work great.

On a side note, is it possible you could have it auto save the Module detail's on your Loader? Save's having to select the dll and type Initialize every time

Hope the report helps.

[pkaa4eva_jr]

Everytime i run this the injection seems to work but when i log onto wow it gives me an error message and it doesn't allow me to log into wow and then wow just closes.

[armen]

Cypher, on an unrelated topic, do you know of a way to switch which framework is being used for specific apps?

One of the apps I have been using lately (coded for 3.5) is no longer working post 4 install.

[armen]

Never mind, I realized I could just create an app.config with the supportedRuntime version in the same directory.

Edit: Hrm, still no lovin'. Cypher, was there a particular reason you had to use .Net 4 beta for this release? It seems no matter what I try, CLR 4 rewrites over existing versions and thus won't allow apps that rely on the current CLR to work (even if I explicitly call out the 'older' Runtime in the app.config).

[tombg]

ok so the new version is tested and it works. 1st i run wow, log and chose char. then i run loader, choose process and path to dll, write Initialize and press inject. its ok, but do we really need to manually enter path, write Initialize and choose process? any chance to have it automated? .bat scripts were much better, just 1 click and i was rdy to go.

[pubicbear]

Fantastic Release!

[Prodian0013]

ok so the new version is tested and it works. 1st i run wow, log and chose char. then i run loader, choose process and path to dll, write Initialize and press inject. its ok, but do we really need to manually enter path, write Initialize and choose process? any chance to have it automated? .bat scripts were much better, just 1 click and i was rdy to go.

Put this in a bat script

Loader_IA32.exe --launch="C:\Program Files\World Of Warcraft\Wow.exe" --module="LuaNinja.dll" --export="Initialize"

It will launch wow and run the injection all at once.

[armen]

Put this in a bat script

Loader_IA32.exe --launch="C:\Program Files\World Of Warcraft\Wow.exe" --module="LuaNinja.dll" --export="Initialize"

It will launch wow and run the injection all at once.

It certainly doesn't work for me (see my previous posts). I am on Win7 x64.

[Sikas]

Prolly have to change the directory in that code to where your WoW is dude. That's for XP. Vista or Win 7 is prolly different.

[armen]

Prolly have to change the directory in that code to where your WoW is dude. That's for XP. Vista or Win 7 is prolly different.

Sikas, was that a reply to me? I certainly know where my WoW instance is deployed to

[Prodian0013]

Prolly have to change the directory in that code to where your WoW is dude. That's for XP. Vista or Win 7 is prolly different.

Im running Windows 7, it works fine. Directory path is the same for me.

[masteramoebe]

thank you cypher ! awesome !!!

[Sikas]

Well, it doesn't launch WoW for it as it usually does.. but it works jus fine. Launch WoW manually, hit the batch script.. good to go.