Jump to content

Torezu

Retired Staff
  • Posts

    6945
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Torezu

  1. That AV shouldn't do anything like this. I'd vote for a reinstall of the pack (back up worlds & waypoints, as usual).
  2. I would: 1) Remove all older versions of Java and get 7u5. 2) Reinstall Technic (back up worlds/waypoints/bags) 3) Post your launcher log on pastebin, since it's too large for code tags.
  3. Ignore any of these steps if you have already successfully done them. 1) Install Java 7u5 64-bit. 2) Remove all older versions of Java. 3) Download the launcher .jar 4) Right-click on the launcher .jar and select "Run with Java" 5) If the cmd window pops up for a second and nothing else happens, add Java to your system path variable. No, I won't tell you how - Google it. 6) If it still doesn't work, come back and fill out a complete bug report.
  4. You could try the EE -> zEE file rename fix that's mentioned in the stickies in the Bug Boards.
  5. Use the .jar instead - the .exe often doesn't cooperate well with 32-bit systems.
  6. Have you tried a reinstall (with backups made)? Did you do anything mod-related before the pickaxe thing? Do you have any older versions of Java installed?
  7. I'm trying to decide whether to call troll or not. This, and mention of a Technic server, are almost to the level of So Dumb It's Gotta Be A Troll. Either way, more info needed before troubleshooting can occur. :)
  8. My idea would be to open your eyes and see the button that lets you create a bug report. Then notice the few (read: lots) of threads on EE in 7.1.0, and realize that the Forge versions differ, and that's probably why you're getting errors. Live without EE, or read those threads and work through it. You're trying to play a dev. build, and expecting it to work nicely when you modify it.
  9. Remove the JDK unless you really need it (i.e. are actually programming in Java). Make sure you have the appropriate version of OptiFine installed. Other than that, you're not providing enough information to troubleshoot with, if indeed there's anything actually wrong.
  10. Your render distance in Video Settings is too low. Increase it. Fyi, right in the middle of the bar is "Far".
  11. Please learn to read.
  12. Okay, next check your AV/firewall - what are you using?
  13. Use the .jar instead of the .exe, and run with a batch file and "pause" if you can't read the error message.
  14. Something is busted. The last time I saw this error, several of our alchemy bags were corrupted. I had to pull backups. It's usually the result of a server crash at the same time it happens to be saving chunk data.
  15. - Do you have any older versions of Java installed? - What's your AV? - Have you also tried deleting your .minecraft folder and allowing the launcher to fetch you a new one, just to clear out lingering issues?
  16. Disable/uninstall your AV, and/or use the .jar instead of the .exe launcher. And yes, he's suggesting using the search bar.
  17. You're using a version of Windows from the future. There's your problem. In all seriousness, it's probably an OptiFine problem. Get the version of OptiFine Standard that matches whatever Minecraft version your Tekkit is running (probably 1.2.5), and drop the contents in the appropriate modpack.jar with 7zip or WinRAR.
  18. You will need at least Java 6 (7 is preferred) to run Technic. Then I believe you need to prioritize Java versions or something like that (not a Mac expert by any stretch).
  19. Pictures would be helpful. It's possible your render distance is set too low, but there are a number of other things that could be wrong.
  20. Don't do this. You will break your Technic world. You're going to have to download and use MCEdit to remove the offending pipe, most likely. That's unless, and possibly in addition to, barnaby's fix.
  21. Millenaire appears to be causing your problem. I'd consider disabling it. If you're really invested in it, try pulling a backup world, or doing a modpack reinstall (save your world/waypoints/bag contents).
  22. Launcher log? Java version number? Modpack version number? Antivirus? Those are the most useful pieces of info, yet somehow they are the ones that get left out the most frequently...
  23. I'd update to Java 7, regardless. This error is most likely caused by Mo' Creatures putting its config file in your .minecraft folder, though. Either delete .minecraft entirely (make backups), or just go find the config file and kill it. Then, in the future, when you'd like to edit the config, edit the file directly instead of using the in-game configuration buttons.
  24. Don't do this. It looks like you need to reinstall Java. Might as well get 7u5 while you're at it.
  25. Norton's likely the problem, but your bug report leaves som...scratch that, almost everything to be desired.
×
×
  • Create New...