Modcraft - The community dedicated to quality WoW modding!

Wrath of the Lich King Modding => Miscellaneous => Topic started by: Mr. DK on December 10, 2015, 12:57:30 am

Title: CMD Error
Post by: Mr. DK on December 10, 2015, 12:57:30 am
Hello Modcraft,

After a wile of beein inactive I decided to resetup my modding stuff.
When I was using some of the general CMDStuff like offsetfix or fileinfo I just get a black CMD Screen. Nothing seems to be working and after a while I get the Error message shown. I translate it to english:

"The Application could not be run. (0xc000012d) Click Okay to close application."

Ill include a pic:

(http://www.imagr.eu/up/7Jn1C_bug.png) (http://www.imagr.eu/7Jn1C)

Btw same cmd stuff works perfectly fine on my laptop so no files not corrupt.
Task manager also tells me it uses a huge amount of my Ram...
Anyone know what this is? Really need these stuff :(
Tanks for help.
Title: Re: CMD Error
Post by: Valkryst on December 10, 2015, 03:41:14 pm
Assuming it's an issue with windows, I'd normally say to pop open the terminal and use the sfc /scannow command, but I'm not sure if it can be run without the terminal...
Title: Re: CMD Error
Post by: schlumpf on December 10, 2015, 04:51:46 pm
It is very unlikely to be a windows error. As of what I know, 0xc000012d is STATUS_COMMITMENT_LIMIT, meaning the application tried to allocate a shitload of RAM. As you probably have enough RAM for the few files you want to process, you probably rather pass the files wrong which causes the poorly programmed tools to somehow read invalid things, without validation, and thus determine the size to allocate wrongly (i.e. "reading" the error code -1 would be an allocation of 2^32 bytes).

Did you try running the tools in an interactive shell? Did you try to ECHO the exact commands executed by the script and try them manually? Are the files you try to process valid input for the applications?
Title: Re: CMD Error
Post by: Mr. DK on December 10, 2015, 08:11:30 pm
Quote from: "schlumpf"
Did you try running the tools in an interactive shell? Did you try to ECHO the exact commands executed by the script and try them manually? Are the files you try to process valid input for the applications?

What I did:

1. Downlaod the tutorial modding environment.
2. Opened the Adt Adder.
3. Created 3 fiels with the template provided.
4. Run the offsetfix.
5. Error occured.

Thing is did the same on my laptop and there it works propperly...
Title: Re: CMD Error
Post by: Corvus on January 13, 2016, 02:06:19 pm
Did you find a solution? I have exactly the same problem since a few weeks.
>fix.bat/offsetfix.exe => black window, nothing happens, computer sunddenly very busy, impossible to quit.

I don't understand why... it used to work like a charm a few weeks ago, on the same computer!
Title: Re: CMD Error
Post by: Amaroth on January 13, 2016, 04:32:23 pm
I think Skarn said something about very similiar or exactly the same problems, related to latest Windows updates. You can check this topic (http://www.model-changing.net/forums/topic/104-solution-for-crashing-software-caused-by-windows-update/) and see if it helps you.
Title: Re: CMD Error
Post by: Skarn on January 14, 2016, 08:38:32 am
Yeah, thie thing that Valkryst linked should be a solution to your problem. Though, the bug in your case seems to be a bit different. But give it a try anyway.
Title: Re: CMD Error
Post by: Corvus on January 14, 2016, 12:21:12 pm
It worked! Thank you guys!  :D