Interact Problems

[lanman92]

Ahh, gotta love .NET ease I knew there was a reason I chose C# to be my first language to use...

[luciferc]

Did you get it to work i suspose? If so post code if you feel so inclined to share with the others :P.

Well off to sleep for now.

[lanman92]

Yeah, I'll give you the code tomorrow if I get it working. I have to go back to sleep soon, school starts back up =/

EDIT: F**k school... I have no idea why this code is not working. I have the import correct, but it keeps saying invalid arguments.

CONTEXT ctx = new CONTEXT();
ctx.ContextFlags = (uint)CONTEXT_FLAGS.CONTEXT_ALL;
Memory.GetThreadContext(hThread, ref ctx);

[lanman92]

I think x64 is giving me more grief. I'm sick of this already. I don't know how to operate on x64... **** you toshiba. Erm, Microsoft. /sigh, time to start DLing a x86 vista disk...

[Cypher]

I said it once and I'll say it again.

YOU'RE DOING IT WRONG!

I PERSONALLY (ie the ****ing computer I play WoW on and run hacks on) use Windows Server 2008 Enterprise x64. Stop blaming the architecture for your fail code imo.

EDIT: **** you Microsoft? Right.. its their fault they made an x64 OS and you're having trouble using it because you suck? >_>

What is it with stupid people and Microsoft bashing. Get a valid point or keep your mouth shut.

[Xarg0]

I said it once and I'll say it again.

YOU'RE DOING IT WRONG!

I PERSONALLY (ie the ****ing computer I play WoW on and run hacks on) use Windows Server 2008 Enterprise x64. Stop blaming the architecture for your fail code imo.

EDIT: **** you Microsoft? Right.. its their fault they made an x64 OS and you're having trouble using it because you suck? >_>

What is it with stupid people and Microsoft bashing. Get a valid point or keep your mouth shut.

Actually Microsoft did a great job on x64 *thinking back to the first x86_64 Linux kernel*, Linux had x86_64 support before Windows but the kernel was pretty unstable and nearly unusable while Microsoft had a rather good working x86_64 kernel at the first release (yet it required some patching but that's a normal thing), but still Microsoft was pretty late compared to other operating systems.

I personally like that Microsoft is finally starting to bring x86_64 into the normal desktop world, as it forces driver developers to create x64 drivers because a lot of companies then decides to also create linux x64 drivers or we just wrap the Windows driver to Linux (ndiswrapper does this for wlan drivers).


64bit is the future, maybe there'll be a 64bit version of WoW with the next addon

[Cypher]

Actually Microsoft did a great job on x64 *thinking back to the first x86_64 Linux kernel*, Linux had x86_64 support before Windows but the kernel was pretty unstable and nearly unusable while Microsoft had a rather good working x86_64 kernel at the first release (yet it required some patching but that's a normal thing), but still Microsoft was pretty late compared to other operating systems.

I personally like that Microsoft is finally starting to bring x86_64 into the normal desktop world, as it forces driver developers to create x64 drivers because a lot of companies then decides to also create linux x64 drivers or we just wrap the Windows driver to Linux (ndiswrapper does this for wlan drivers).


64bit is the future, maybe there'll be a 64bit version of WoW with the next addon

A native x64 WoW build would be kinda pointless but okay.

That aside, I know Microsoft did a great job on x64, I'm a big fan of Server 2008, dunno where you got the idea I didn't think they did a great job. (Or did you not mean that by quoting me?)

P.S. There were x64 XP builds. And I'll take stability and features over bleeding edge LOLWEWEREFIRST any day, kthx.

[Xarg0]

A native x64 WoW build would be kinda pointless but okay.

That aside, I know Microsoft did a great job on x64, I'm a big fan of Server 2008, dunno where you got the idea I didn't think they did a great job. (Or did you not mean that by quoting me?)

P.S. There were x64 XP builds. And I'll take stability and features over bleeding edge LOLWEWEREFIRST any day, kthx.

Well, I didn't claim that there wasn't a 64bit version of XP :-)
anyway you can't say windows is better than Linux or contrary, the better choice always depends on the problem and the personal experience with either systems.

And if you don't need any support Linux is way cheaper than Windows :-)
also I like OpenSource so Linux is my first choice OS, in near future my favorite maybe a GNU Hurd based OS.

[lanman92]

Okay, I'll show you the code that isn't working. It's the EXACT same code that Shynd, and PInvoke.net have posted in their libraries. I can't get GetThreadContext() to work. It keeps saying I have an invalid parameter. It compiles in Shynd's library, but I don't know if it actually works. The pinvoke.net example compiles as well, but it doesn't run correctly. Mine doesn't even compile.

CONTEXT ctx = newCONTEXT();
ctx.ContextFlags = (uint)CONTEXT_FLAGS.CONTEXT_ALL;
Memory.GetThreadContext(hThread, ref ctx);

[Cypher]

Well, I didn't claim that there wasn't a 64bit version of XP :-)
anyway you can't say windows is better than Linux or contrary, the better choice always depends on the problem and the personal experience with either systems.

And if you don't need any support Linux is way cheaper than Windows :-)
also I like OpenSource so Linux is my first choice OS, in near future my favorite maybe a GNU Hurd based OS.

Still trying to work out why you quoted me the first time. >_>