Quote:
Originally Posted by FoxCharm
I think the reasoning for this is because the game was first made to run on 32bit, therefore the process was hidden to prevent things happening. Then came along 64 bit and 86bit.
But that's just me taking a wild guess, seems accurate to me though.
|
Thanks for answering! I wasn't really expecting someone this capable in English to respond :p.
Yes, I've gotten a similiar respond from a friend of mine, so I do believe your explanation has a high probability of being spot on.
Quote:
Originally Posted by PŠPplą’ər
How to inject ItemManager.dll on 32 bits OS's:
Open Faith Injector=>Settings=>Check Auto-Inject
Click Inject and it will say "Waiting for process"
Then start S4league and it will automaticly inject.
PS:If you don't use a bypass Xtrap gonna detect it.
|
I've tried this in the past and sadly the first problem I have is the same as plasma 4's and vichilangelo's; I get a blue screen. Actualy, that's not the only instance in which I've gotten a blue screen error either, which is somewhat concerning. The second problem is that some dll.'s (like Alice Item Manager for example) need to be injected at the login screen and not prior to that.
I have been thinking of using Process Explorer (PE) to suspend the S4 process, keeping it visible/not hidden thus enabling Faith (or any other) injector to detect S4 as a valid process. I have however, encountered a problem in attempting this alternative: PE is detected by HGWC (plus aegis and perhaps even X-Trap) and I get an error screen. To this I've downloaded a HWGC bypass only to later find out it is outdated and is useless. I will try to find a HWGC bypass that is more recent. Alternatively I will try to time the suspension of HWGC itself between it's completion (100%) and the initialising of S4. So far suspending the HWGC process prior to completion results in it freezing and not progressing to S4 start-up.
Really, other than doing it PE, "old school" style I have no other idea how to secure the visibility of the S4 under processes, lest something finds the core code responsible for hiding S4 process and adressing that in code, directly.
If someone has a recommendation as to what HGWC bypass I should use, you're welcome to tell me. Also, I hope this method is not completely obsolete.
Other than that, I have one final question: does Se!mons bypass work if S4 process is not hidden for only 2-5 seconds, or does it too, fail?
Thanks again.