plowmanplow

It's possible to allocate too much RAM. You don't say how much RAM your PC has, but if you have 4G you wouldn't want to allocate more than 2, and maybe only 1.5. Even 1.5G is enough to run very large modpacks with mostly complete 64x texture packs.

That is the launcher log. You need the FML log and crash report. Post links to your pack page and/or your download URL.

This post needs to be moved to Platform Pagoda You need to include links to your pack page and/or download URL.

/me shakes the Magic 8-Ball... "Signs point to yes" Seriously, though, we cannot help you if you don't provide logs and links to your pack page and/or download URL.

The Flan folder you have in mods should be at the top level of your archive. You have not properly installed MoCreatures. Visit the author's thread/site again and redo the installation. You have placed the MetaWorlds installer in your mods folder. This is not the correct installation method. See the author's thread/site and follow their instructions. Please note that it has specific incompatibilities with NEI and many mods which place tile entities in the world (of which many of your other mods do). You have included TConstruct Library. This is unneeded and should be removed. You have not included any config files. For this collection of mods that is a fatal problem for the pack as the default config files have ID conflicts. However, one should always include config files.

You must have mistyped that URL as it does not work.

If you look in your modpack folder (%APPDATA%.technicmodpacksyourmodpack) you will see a config folder. You need to include this whole folder in your modpack. Config files do a lot more than just assign IDs to blocks/items/entities/biomes/potions/enchants/etc. They provide a way to balance your mods against each other, to tweak energy production, to balance worldgen ore and liquids, etc. You should always be including them in your pack.

The message you have quoted in your post is inconsequential. It just means that the mod author has a bit of work to do before the mod will work in Forge/MC 1.7+ The log you have posted is incomplete and of little value. Please provide links to your pack page and/or your download URL.

18.04 09:16:02 [Server] SEVERE java.lang.IllegalArgumentException: Slot 178 is already occupied by ee.BlockEETorch@2f40a3f5 when adding codechicken.enderstorage.BlockEnderChest@3ccc420f This means that you have a block ID conflict between those two mods. If you are seeing this with a "frozen" pack like TekkitClassic then the implication is that you do not have the proper config files on the server.

You are going to need a better formatted log output. That wall of text is way too hard to interpret.

The short answer is: Add a modpack to the launcher and start it once Download additional mods and drop them into the modpack's mods folder (%APPDATA%.technicmodpacks<modpackname>mods) Start pack again. If it fails to launch by dropping back to the launcher or giving error messages about conflicts or missing mods you wlil need to address those by adding the required mods or adjusting IDs in the new mods' config files. The long answer is... it's complicated. One must make sure to only get mods from the author's preferred distribution channels as this ensures one has the proper installation procedures, the current/correct version of the mod as well as any dependencies on which the mod relies. Resolving ID conflicts (1.6.4-) can be challenging. If your client crashes to the launcher when you try to start the pack you'll need to check the ForgeModLoader client log and the crash-report to identify where the problem is originating. This can be confusing for folks starting out. If you want an example of the exact procedure/process for adding a specific mod or two to a specific pack provide links here to the pack and mods and I'll walk you through it.

Changing recipes by using one mod to overload/override another (ala GregTech) can be problematic both from a technical standpoint as well as being able to maintain it across varying versions of mods. Usually not worth it.

I highly recommend including config files in order to provide a way to balance interactions between mods, worldgen, energy settings, explosions, etc.

(chases Bunni1337 around fixing faulty advice on necrotic posts) For future searchers of fixes: Simply download the correct version of Optifine (OptiFine_1.6.4_HD_U_D1.jar) for 1.6.4 and drop it in your mods folder.

Please disregard previous post. The "current" version of Optifine (OptiFine_1.6.4_HD_U_D1.jar) for 1.6.4 works fine with TekkitMain 2.0.9e. Just drop it into your mods folder. I only post this here to put folks on the right track if they search for optifine and tekkit.

All of those crash logs look like they are caused by the same problem (they are functionally the same). Without links to your pack page and/or download URL it will be difficult to provide any additional assistance.

Going from 1.6.2 to 1.6.4 should be doable if there haven't been too many mods removed. You'll just need to make sure your configs are correct and that things are as synchronized as possible between the old and new versions.

Your pack is not set to use a direct link URL. You need to add "?download=1" to your copy.com link (without the quotes). If you are going to run IC2 I highly recommend checking out this link. You will want at least the IC2Fixes mod to fix recipes (very small mod, no performance impact): I would recommend updating MagicBees to the current version (2.1.12 as of this post) You should always include the config folder and contents in your modpack. WIth so few mods you are getting by without it but you can't adjust settings/balance/integration/interaction for mods without doing so. Try setting your launcher to use 768M of memory and see if that gets you anywhere.

A couple notes: Your bin folder has extra, unneeded files. It should only contain modpack.jar and should never contain minecraft.jar (violation of Mojang terms of service). If you are going to include IC2 in your pack I highly recommend checking this link out. The version you have included has a number of serious bugs.

Or, just for giggles mind you, you could follow the author's instructions and: Download Optifine and put it into your mods folder: http://optifine.net/download.php?f=OptiFine_1.6.4_HD_U_D1.jar Play Tekkit. Seems a bit simpler than the previous, necroposted, needlessly complicated machinations.

Yes, copy.com works fine. Once you upload your modpack archive ZIP file you simply need to share it through their interface and add "?download=1" to the public link they provide. As for making the pack, you'll need an archive making program like 7zip. Just make sure that you make the archive in ZIP format and not 7z, rar, etc. Make a new folder somewhere on your hard drive and name it what you want to name your modpack. I will refer to this as MODPACK Make a folder called "bin" in MODPACK. Put "modpack.jar" into your newly created bin folder. Copy your entire config folder into MODPACK. If your config folder is empty then you have not successfully started/tested the pack and need to stop here until that is complete. Copy your entire mods folder into MODPACK. If you have extra folders (i.e. Flan, Chocolate, etc.) copy those into MODPACK. Select the contents of MODPACK, right-click and create a new ZIP archive. (should be an option in your shell extension dialog) Upload this ZIP archive to copy.com. Share the newly uploaded file. Copy the public link and add "?download=1" (without the quotes). This is your modpack's download URL.

You simply need to download the correct version ( http://optifine.net/download.php?f=OptiFine_1.6.4_HD_U_D1.jar ) and put it in your mods folder.

If you provide relevant information (FML logs, crash reports, download URLs, pack page links, system configuration, etc.) we can help you. Otherwise, not so much.

Verifique se você está usando a sua conta minecraft para entrar no lançador e não a conta Technic.

Always post links to the Technic pack page and/or download URL when requesting help for a modpack. How much physical RAM does your PC have. How much are you allocating in the launcher? Which Java are you using? 64bit or 32bit? The missing textures are inconsequential and have no impact on pack/memory performance.