RockRaiderZulu

Launcher Version: Launcher Build: '1.0.1.3' Operating System: 64-bit Windows 7 SP1 Java Version: Java VM: '1.6.0_14-b08' Straight from the log. Java 6.0.140.8 Antivirus Program: Today I started up the launcher, after checking to see if a 1.2.5 Bukkit sever I work on was up (it was not) with the normal MC launcher, to find that the Technic launcher will not connect. Subsequent attempts either prompted for me to play offline or claimed that a connection was found when it actually was not. After Take Two of the connection I redownloaded the launcher. Two of, I think four attempts with the "new" launcher file, had the updater crash after that. I changed back to the "old" file to have it not crash at all, but still there is no connection. I am using a system of batch files, and when trying to use the "working" launcher without one, it failed to download and did not retry. Rather it launched and crashed. I saw it tried to download the wrong version of Minecraft (1.2 instead of 1.1). I think that had something to do with that failure. Does the launcher rely upon Mojang having an archive? Description of Problem: Today I started up the launcher, after checking to see if a 1.2.5 Bukkit sever I work on was up (it was not) with the normal MC launcher, to find that the Technic launcher will not connect. Subsequent attempts either prompted for me to play offline or claimed that a connection was found when it actually was not. After Take Two of the connection I redownloaded the launcher. Two of, I think four attempts with the "new" launcher file, had the updater crash after that. I changed back to the "old" file to have it not crash at all, but still there is no connection. I am using a system of batch files, and when trying to use the "working" launcher without one, it failed to download and did not retry. Rather it launched and crashed. I saw it tried to download the wrong version of Minecraft (1.2 instead of 1.1). I think that had something to do with that failure. Does the launcher rely upon Mojang having an archive? Error Messages: The only error is a failed connection. Error Log: Since there were no exceptions, there are no logs.

It could also be that there is only that amount of working memory available. In which case you need to terminate a background task.

Um, that is not how to state a problem. Can you actually state what happened to break the launcher?

The "problem" I have with the way it is set up is that it clears files that it does not back up, such as the minimap files in the minimap folder, which holds the waypoints, all of which can be corrected manually, making it pointless to clear them. I think it may be better to have it look for modified files (this can be done by comparing the replacement files, which are going to have to be downloaded anyways, to the old ones) and ask which ones to replace. It will be a pain in wrench to implement, but a lot less rage will occur if that method is used.