Jump to content
  • 0

Launcher, Technic, Tekkit, and Tekkit Server all extremely unstable


Question

Posted

Launcher Version: 1.0.1.3

Operating System: Windows 7 64 bit

Java Version: 1.7.0_05

Antivirus Program: The Technic Launcher, the modded Minecrafts, and the Tekkit Server are all extremely unstable (as in, they cannot be played). They crash within minutes of starting up. The launcher fails to connect to Minecraft.net about half the time. I've tried all the fixes listed, and they didn't work. I've also tried reinstalling Java, which also did not help.

Description of Problem:

The Technic Launcher, the modded Minecrafts, and the Tekkit Server are all extremely unstable (as in, they cannot be played). They crash within minutes of starting up. The launcher fails to connect to Minecraft.net about half the time. I've tried all the fixes listed, and they didn't work. I've also tried reinstalling Java, which also did not help.

Error Messages:

None

Error Log:


(Had to cut out a whole bunch of stuff so the forum would take it)



[21:42:57] [sEVERE]	------------------------------------------

[21:42:57] [sEVERE]	Launcher is starting....

[21:42:57] [sEVERE]	Launcher Build: '1.0.1.3'

[21:42:57] [sEVERE]	Allocated 910.25 Mb of RAM

[21:42:57] [sEVERE]	Java VM: '1.7.0_05-b05'

[21:42:57] [sEVERE]	OS Version: '6.1'

[21:42:57] [sEVERE]	Is 64-bit: 'true'

[21:42:57] [sEVERE]	[info] Downloading 'mirrors.yml' from 'http://mirror.technicpack.net/Technic/mirrors.yml'.

[21:42:58] [sEVERE]	Starting download of 'http://mirror.technicpack.net/Technic/CHECKSUM.md5', with 3 trie(s) remaining

[21:42:58] [sEVERE]	Copying: \temp\file8150294619934420631.tmp to: \launcher\CHECKSUM.md5

[21:42:58] [sEVERE]	File Downloaded: \launcher\CHECKSUM.md5

[21:42:58] [sEVERE]	MD5 hash not found for 'hackslashmine/resources/favicon.png'

[21:42:58] [sEVERE]	[MD5 Mismatch] File '\launcher\hackslashmine\resources\favicon.png' has md5 of '6ac510b04af406f19c3ad8ea40c16090' instead of 'null'

[21:42:58] [sEVERE]	MD5 hash not found for 'hackslashmine/resources/logo.png'

[21:42:58] [sEVERE]	[MD5 Mismatch] File '\launcher\hackslashmine\resources\logo.png' has md5 of 'c8245a967bdbb9560bd3668327a738ba' instead of 'null'

[21:42:58] [sEVERE]	MD5 hash not found for 'hackslashmine/resources/icon.png'

[21:42:58] [sEVERE]	[MD5 Mismatch] File '\launcher\hackslashmine\resources\icon.png' has md5 of 'dba1052dab8409764e40cc81aa010f6f' instead of 'null'

[21:42:58] [sEVERE]	Starting download of 'http://mirror.technicpack.net/Technic/hackslashmine/resources/logo.png', with 3 trie(s) remaining

[21:42:58] [sEVERE]	Starting download of 'http://mirror.technicpack.net/Technic/hackslashmine/resources/icon.png', with 3 trie(s) remaining

[21:42:58] [sEVERE]	Starting download of 'http://mirror.technicpack.net/Technic/hackslashmine/resources/favicon.png', with 3 trie(s) remaining

[21:42:58] [sEVERE]	Copying: \temp\file5727917737065412909.tmp to: \launcher\hackslashmine\resources\favicon.png

[21:42:58] [sEVERE]	Copying: \temp\file623907704577123532.tmp to: \launcher\hackslashmine\resources\icon.png

[21:42:58] [sEVERE]	File Downloaded: \launcher\hackslashmine\resources\favicon.png

[21:42:58] [sEVERE]	File Downloaded: \launcher\hackslashmine\resources\icon.png

[21:42:59] [sEVERE]	Copying: \temp\file1360027862472561200.tmp to: \launcher\hackslashmine\resources\logo.png

[21:42:59] [sEVERE]	File Downloaded: \launcher\hackslashmine\resources\logo.png

[21:42:59] [sEVERE]	[MD5 Mismatch] File '\launcher\tekkit\modpack.yml' has md5 of 'e16f7f6f0454999313947b0cb9a880d0' instead of '1b40ec4a42ec16ecf5407bb6e418c9ba'

[21:42:59] [sEVERE]	[info] Downloading 'modpack.yml' from 'http://mirror.technicpack.net/Technic/tekkit/modpack.yml'.

[21:42:59] [sEVERE]	[info] Downloading 'minecraft.yml' from 'http://mirror.technicpack.net/Technic/minecraft.yml'.

3 answers to this question

Recommended Posts

  • 0
Posted

You're not the only one having this problem right now, a lot of people with different OS, different everything are still having the "cannot connect to minecraft.net" and booting you off when it does connect. I think it's something on their end, not anything client-side. You'll just have to wait for them to fix it.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...