panicnot42

First off, please, no all caps. Second, never, ever, use modloader! That site is pure evil.... Your log says you need 1.4.7, go download the 1.4.7 pre-release from Mojang

Read the EAQ You need the 1.4.7 pre-release

First off, delete META-INF, the install. Forge will add a META-INF. Second, 1.4.7 is available: http://assets.minecraft.net/1_4_7/minecraft.jar

Yeah, I figured that out! Could you be a bit more technical, perhaps? I'm familiar with how java signing works, not the internals of forge, or liteloader, however.

Ahh, ok! Would you care to explain why it is this happens?

Try again without NEI, see if that helps.

No problem! I would suggest you report this bug to the Millenaire developers, as it could help them to fix this error. And, yes, having played Millenaire in 1.8.1, it is an awesome mod!

While Ubuntu is a great, easy to use, Linux distribution, I'd recommend, if you want serious performance, using a different distribution. If all you're doing is running minecraft, start with something like Arch, or, even Tiny Core Linux. Less to the actual OS, more available to minecraft. They require a bit more know-how and skill to operate, but the payoff is worth it,

Ideally, a tool like mIDas should be put into Forge. Currently, I'm taking an NEI id dump from my old world, and one from my new, then using *nix's sort and uniq commands to get a list of problem ids. Perhaps I'll post something about it on the Forge suggestion board.

Basically, the issue with you're dealing with is one of your mods trying to do bad things with threads (to put it simply). I can't tell which mod id is from the error, but, I would suspect it's millenaire. Trying removing it and see if stability improves.

You aren't, believe me. I suspect most are just tossing their maps, though. For me, not an option, I've had the same map since 1.7.3, no way I'm tossing it now!

Yes, it should. What you're wanting to do is update all the old ids in your map to new ids. If you don't, you'll get forge errors, as you saw, and if you keep going, you will lose blocks/items.

Do not delete your old config. Keep IC2.cfg. You need to change the ids on the map. Google "minecraft mIDas-gold". It is a tool for changing ids in maps.

You have an ID conflict. Millenaire wants to use slot 1515, buildcraft is already using it. Open the millenaire config, and change 1515 to something else.

Looks like the mod jar file is corrupted. Have you tried redownloading it?

Can you clarify? What do you mean by "chests don't work"? Logs?

I had a similar problem, albeit, with much less impressive specs on my server. My solution was to ramdisk the server executable, lib, mods, and coremods. I believe there may be an article on doing it on the minecraft wiki

http://ken.wingedboot.com/forgemirror/files.minecraftforge.net/fmllibs/ Dowanload these files into /lib in your .minecraft folder. If you had spent 5 minutes googling, you would have found a similar question answered yesterday.

Yes, I did. I've tried basically every possible combination of deleting META-INF. I've removed it from minecraft, forge, forge and minecraft, minecraft and all of the mods, minecraft, forge and all mods. Most caused different crash bugs. I'm going to try running it as a server and client, and I will post crash logs from both ends.

You are trying to install Forge for 1.4.7 into a 1.4.6 jar. Try using 1.4.7: http://assets.minecraft.net/1_4_7/minecraft.jar