Loader

Mmm. That's a pretty common problem when using the wrong version, believe me when I say that it's doing you a favor in not connecting. Just downgrade back to the old version until the server updates, that's it.

I'm kinda hoping the log you put up will shed some light on it, maybe indicate something it's doing wrong in minecraft at your end. Just kinda waiting for that.

Out of virtual memory implies it's actually using a fair bit of pagefile - that seems like a likely cause, even a fast SSD has a transfer rate of ~500MB/s when average modern RAM has somewhere in the vicinity of 13,000MB/s, if it's trying to do that job in virtual memory it'll take a few seconds for sure. How much RAM does it have?

Please post here http://forums.technicpack.net/tracker/project-1-technic-launcher/ with the launcher log in; %AppData%.techniclogs and the right people should see it and be able to help you.

It's probably the exact same problem, you're losing connection to the server somehow. The different errors are in relation to when - one error when you're trying to send info to the server, one error when you're waiting for info from the server (that never arrives). These are all the end result though, we need to get to the cause - it's like these are "the car won't start" and we need to find out why (there can be a lot of causes).

1. Doesn't work as in how? This option should have no chance of failing unless you've already been into a world with the new version, which shouldn't have been possible with this error. Do you mean more figuratively, as in it's an unacceptable outcome, rather than it actually doesn't work when you try to change it? This is important, as it might indicate something wrong. 2. That's why I mentioned the Mavericks option in there, it's not a great situation you're in, and that's the only free option out - if your Mac will support it. 3. It worries me a little that if you struggled with option 1 and you didn't look into option 2 you went onto option 3 - it's the most complicated with the possible exception of the OS upgrade, and it's the most difficult. What exactly did you do when you say "I did all that"? Can you run me through the steps you took to make sure there's nothing missed? Are we going with trying 3? That's how it seems, I just want to be sure.

Make certain Java is updated to within at least a couple years of now (Java 7 ), and that should fix projectred issues. Some people have an older MacOS which doesn't support Java 7, some people are having problems with multiple versions being installed, but at the end of the day every issue I've seen with PR so far has been simply that it's not using Java 7 (for whatever reason) and it needs to. Deleting it is a very temporary fix, as more mods are likely to take this angle as time goes on.

Please post a log, you can find them in; %AppData%.technicmodpacksattack-of-the-bteamcrash-reports I'm not sure whether client or server log will be better to get info from, so please post both on pastebin.

Ignore all the minecraft version numbering, that doesn't have a lot to do with the modpack (for players, at least, it's a pretty big deal to the people making it obviously ). You can pick which version you're running in the technic launcher, underneath the menu option for attack of the b-team on the left you'll notice a gear, click that and you'll get a bunch of options. The option you want is "Manually Select Build" which you pick using those radio buttons at the top, when you pick that you'll be able to pick whichever b-team version you like from the drop down box.

1.0.9c's recommended now - it brings with it a fun new set of problems http://www.technicpack.net/article/view/attack-of-the-b-team-109c-is-now-recommended.71

You can try limiting what NEI does by typing some garbage into the search bar in your inventory - that should pause for a second when you first do it but after that it'll just do a quick check that there's no match and leave it there (which if it's CPU lag from the search and accessing that list should be bypassed). That's my best guess from what you've put, the NEI search is quite CPU intensive, so if you've got an old laptop it could easily cap out there if it's running minecraft too (especially singleplayer).

Cool, can you paste whats in that notepad file on this site and link it to me, please? http://paste.ubuntu.com Hopefully it's got some helpful info in it, it'll be a place to start at least. (The new message is a similar thing, by the way, it's usually caused by a TCP timeout which means the connection is getting stopped somewhere, which we kinda knew but it's nice to see some more confirmation).

Did you follow the rest of the steps? (ran minecraft through the launcher, tried to connect to a server, then quit?)

That's unfortunate timing, that's fixed in 1.0.9c

Yeah, rename it anything you like (output-client2.log is fine), and it'll make its own fresh one when you run the program next.

Ah crap, >I was too slow. Ok, you have three options; 1: Go back to an earlier version of B-Team (not so great as you don't know what'll be in future versions and you might want that stuff, also stops multiplayer most likely). 2: Upgrade to OSX Lion or newer (not so great as your Mac might not support it, it also costs money if you can't run the Mavericks version). 3: Use a workaround to install java 1.7 on snow leopard anyway. I provided an example you can try in this post;

Be aware you're on MacOS Snow Leopard and it doesn't support Java 1.7, so if you're happy with the modpack don't update it (it'll no longer work unless you do a workaround to get Java 1.7 installed on there).

You'll have a file called output-client.log, it'll be a list of all the information that's ever been output to the client since you've been playing b-team, every item you've ever spawned, every server message or chat message you've seen, anything like that. If you rename it (output-client2.log, for example), then it'll make a new, empty version of output-client.log which it'll then fill with information about that time you run it. This means no-one can mix up the current problem with old ones, and keeps the size down to a minimum for you uploading and people scrolling through.

Portable tanks work a bit like that, though you'll still need to put the stuff into them from a bucket. It goes like this; 1: Place down portable tank (cheapest one carries 8 buckets worth of liquid) 2: Use a bucket to shift liquid from a source into the tank. 3: Pick up the tank using the crescent hammer (shift right-click).

Ah ok, in the technic launcher in the top right there's a little gear icon, click it and one of the options in there is logs. You should have a crashlog for client if you're playing online, and both client and server if you're playing SP. If you still can't find it, they're in this folder %AppData%.technicmodpacksattack-of-the-bteamcrash-reports Please post the contents of the newest client and server ones here http://paste.ubuntu.com/ and give us the links so we can look at them.

The crash report for java crashes are in the main b-team client directory, go up one from the crash reports folder. It's usually got some weird name starting with ha_err_pid and a number.

Could be a lot of things - what graphics card do you have? How much RAM is set in the launcher for use? What CPU do you have?

Try this pastebin instead; http://paste.ubuntu.com/ It allows larger files. The bit that's most useful (though often lots of it is useful) is the bit arriej posted as an example, right after the --- Minecraft Crash Report --- line. If you post the whole thing there though it won't matter, we can check it all.

hafsteinmd, out of curiosity which version of MacOS are you on?

No worries Be aware that it can give strange behaviour if you're playing on someone elses singleplayer world that's open to LAN, other than that it should be that straightforward once it's grown.