Kalbintion

I highly doubt BIOS (not "BOIS") settings were the answer. I guess we'll never know though without actually seeing the log and knowing exactly what was done.

Issues belong on the tracker, link at top of page or in signature below.

jwa1 - the only suggestion I can offer atm is to pull mods one by one until the issue is resolved, with whatever mod that was pulled last being the culprit.

What are the modpack API URLs? And post a launcher log. Getting Launcher Logs * Run Technic Launcher * Click on the Cog icon located on the top right of the launcher * Click on the "Logs" button * Provide relevant log files ----------------------------------------------------------------------------------------- Pasting Logs Use one of the following methods to show us your log files: * Attach file to posting * Use http://pastebin.com and paste the resulting URL in your post * Use http://paste.ubuntu.com and paste the resulting URL in your post For overly sized files, attaching or using the above URLs may not work, you can use one of the following for these types of cases * http://mediafire.com * http://dropbox.com

"color console program" being what exactly?

Honestly, haven't had any issues with MBAMs active scanning systems with the launcher in any shape or form, or really anything else. I wonder if it even works some times lol.

Neowulf, are you saying that section isnt intended for that type of thing with the server posting?

Since I'm sure plowmanplow will be around to this thread at some point. Post your modpack API URL. He'll need it and ask for it anyway.

Topics dont generally get removed unless they severely breach rules. Also, it'd be nice to see what you did to resolve your issue, just in case anyone else is having the same issue

Are you still able to replicate the original conflict issue though through using fresh copies of the pack and server? The command I would want you to run would be done in command prompt (WINDOWS KEY + R > type cmd > click ok): fc "%AppData%.technicmodpackshexxitconfig*" "ENTER_PATH_TO_SERVERconfig*" > "%userprofile%desktopconfig compare results.txt" Replace ENTER_PATH_TO_SERVER with the location to the install of the server files you were able to get the issue with still (not the fixed copy) - and ensure you enter that command entirely in command prompt or copy/paste it to a new batch file. Once the command has been ran, there should be a new text file on the desktop named "config compare results" - Post its contents somewhere. * Use http://pastebin.com and paste the resulting URL in your post * Use http://paste.ubuntu.com and paste the resulting URL in your post For overly sized files, attaching or using the above URLs may not work, you can use one of the following for these types of cases * http://mediafire.com * http://dropbox.com

Glad to see you got the issue resolved. I actually forgot about the loading order that was done for 1.5.2 (theres a reason it isnt supported anymore ) - anyway, I reported this thread for not being in the platform pagoda, perhaps this issue can at least help someone else once it does get moved there (I'm assuming a staff member will move it...)

See http://forums.technicpack.net/tracker/issue-3464-skins-arent-updating-properly/ in regards to my response to the skins not updating issue.

Post on the tracker, link at top of page, or in my signature below.

Issues belong on the tracker, skite. Link at top of page or in signature below.

Finally got around to recording Episode 2 of the series which will be available on YouTube soon. I will also be making textual guides for all episodes at some point and having them in this thread as a sub-spoiler of the appropriate episode spoiler tag. Also, just a note: Episode 2 has a shorter intro duration. Found the previous time to be too long and more cumbersome than really helpful. I'm also looking for feedback on these video tutorials as well since I haven't done many of them and my preferred tutorial/guide method is textual (if my aotb tutorials werent a hint toward that)

Have you looked at the documentation with PermEx and bCM? If their documentation doesn't provide enough information, their respective bukkit pages should have a comments section that may be able to get a quicker answer than here. Keep in mind though that the bukkit forums shouldnt have an issue with this type of question since it isnt related to having a problem with the modpack, but rather a question of getting two plugins to be compatible with each other, something that should be right up bukkits and its users alley.

Well, you might be interested to know that there has been quite a few white screen issues being reported, each of their logs I've requested contain the OpenGL lines seen here, or at least something very identical to them. Most of the time theres been a video driver update, in one case though it hasnt solved the issue so i'm not sure whats going on. I've also noticed a few reports of just crashing at the mojang screen after it takes some time to do whatever it doing at the white screen issue before closing. You can find out some of the info I've been wondering about @ http://forums.technicpack.net/tracker/issue-3529- Perhaps Val would be able to answer those questions posted on that tracker, but respond to them here. Edit: In the other cases of the drivers having available updates, they havent done it yet, have other technical issues getting the update to work, etc. So the other cases of updates available for video drivers are in the air atm in terms if the video driver update works or not for them.

initial, are you running Windows [if not ill need to look up the mac/*nix command] by chance and able to replicate this issue once more (preferably without undoing the fix you did)? There's a command that can be run in the windows command line that can compare files in folders and give differences, this would be the quickest way to see what didnt match up and would help figure out what went wrong.

"alienware" is not acceptable means of saying a solution only works for alienware. As there are many types of alienware machines, with varying hardware. Your solution isnt pre-destined to work on all alienware machines, and chances are it would work with other machines if your solution made more specific sense. To top it off, modifying BIOS settings shouldn't be necessary to resolve issues for a singular software case.

I know its possible to do it without overwriting base code, let alone making it so it had to be redist with the base game code, but its often too annoying for devs to improve on base code since it can affect too many things, unless their intentions is just that, improved base ____ for all mods, and expect some mod incompatibilities that expected the old behavior. Good to know about the Better Archery mod being the "culprit" Targren.

Issues belong on the tracker, link at top of page or in my signature below.

There may be some java flags that can be set to improve certain performances, but it would be on a case by case basis and isnt something you could just throw into a modpack as default settings and expect it to work 100% of the time for everyone.

Issues belong on the tracker. Link at top of page.

Yeah, don't want to be like this guy: http://forums.technicpack.net/tracker/issue-3534-technic-launch-then-close/ 16 GB of RAM assigned to a custom modpack...jeez