Torezu

You need a Java version and a launcher/error log.

What antivirus are you using? This could be an AV problem.

A few things: 1) The OP needs to post a launcher log. It's not a part of the bug report for nothing, and helps immensely with troubleshooting. 2) The new launcher is not what's being unstable right now. It's minecraft.net - give it a few days to a week, and they'll hopefully have it up to snuff again. 3) The launcher isn't at version 3 yet, so I'm going to assume you're on Tekkit 3. Samsung laptop isn't an operating system. And you didn't post an antivirus, a few of which will cause the problems you're describing. Get to it!

You want \bin, not \lib.

Add Java to your system path variable. It's likely that the launcher can't find your copy of Java for whatever reason. Otherwise, run the .jar with a batch file that includes the path to Java. Add "pause" as a 2nd line if you'd like to see the cmd window. Copy the batch file out of the server software and change the file name if you don't know how to create one yourself.

Remove your .minecraft folder, backing up anything you'd like to save. Common solution to this problem in the future: delete your lastlogin file - that will allow Minecraft to re-authenticate the login, and hopefully to self-correct. The minecraft.net authentication servers have been serving poorly of late.

Just post the log in pastebin. You don't need to message it.

Make sure you killed all older versions of Java, then post a new log (pastebin please).

Let's see...Mac...pipes crash... It's almost like this has happened to other people.

You don't need the start at the beginning. Then you just run the batch file. If Java doesn't have a defined location, you can either add it to your system path variable or include the path in the batch file. Either way, you should get some kind of error. Yes, an error log or other error message would be helpful.

You should not need a spout update if you have the newest version of the launcher. You have a 32-bit OS so you'll probably need to use the .jar instead of the .exe, as you mentioned. Wipe the .techniclauncher folder and the .minecraft folder, run the newest version of the launcher (grab a brand new one) .jar, and then give us the whole log (use pastebin if it doesn't fit).

I think I see your problem...

Two things: 1) What are you 3 using for antivirus software? Those like to interfere with downloads. 2) Check your version by selecting Tekkit in the launcher window and clicking Options. You want mod pack version 3.0.3 - if you don't have that, select "Always Use Recommended Build."

Either someone used "/reload" on your server, or your mod pack didn't get loaded correctly. I'd bet on the former. Also, to everyone else: after the minecraft.net servers are back up, delete your lastlogin file. That tends to fix the login problems (even if you have to type your password in again).

1) Remove AVG entirely. It often causes problems with the launcher even when disabled. 2) Run the launcher .jar instead of the .exe, using right-click > Run with Java.

I need the whole log to tell, but it's possible something decided to put a config file in your .minecraft folder. Try deleting that folder. Back up whatever you want out of it first, of course.

Try: 1) Running the launcher .jar instead of the .exe. 2) Upgrading to Java 7u5.

I would guess it's because the issue isn't completely disrupting their server access - just mostly disrupting it.

It's probably because the most recent version of Technic doesn't have a modloader.cfg. I'm assuming that's what you have. You can simply delete the mod zips you don't want from the mods folder.

Add c:\program files\java\jre7\bin (or whatever directory matches that approximate path and contains java.exe) to your system path variable. The alternative is that you don't have the correct version of Java for your system, but the system path addition usually fixes this error.

You missed this stickied thread at the top of the Technic Bug Board.

Yeah. Your render distance was set ultra-low. It defaults to that when you first launch Technic or Tekkit after reinstalling for some reason.

Your password can't be leeched from the launcher any more than it can be from a standard Minecraft login. I'm pretty sure you don't know what you're talking about.

Oh, that was being nice. Being mean would have been reporting the thread for a crappy bug report. Since SlimePig clearly didn't read either the rules or what would constitute a good bug report, and I've seen so many such threads that they're starting to blur together, I posted a semi-snarky response. You should not be surprised.

Fixed that.