rilex

Let's not forget the giant security hole that Oracle is (the only way Oracle is "excellent" is due to the forced usage if you want PeopleSoft). This is one of the /last/ databases MaNGOS should support. Hell, I'd rather see JET Red support first.

Yes, thank you! It was pretty nice stuff you did

I'm not sure how Mangolin handles RA. I used a Flash-based add-on to do RA, however SOAP is now the preferred method (another person built the SOAP interface on MicroManager). Send me your email address and I'll send you the source.

I should say I do have a copy (of course!) of the final commit in zip format. This is source only, but if you have VS 2010 you can certainly build it.

Yes, I killed it. A) Didn't want it associated with other projects I'm working on. B) After the whole WoWScape thing (yes even though it was a default judgment, etc. and so forth), I thought it would be best if the project were taken down. C) I hadn't worked on it in at least a month. D) Beyond translations (and thanks to all those who did them!), I wasn't getting any true assistance with the project. While the project isn't /huge/, it was certainly could have benefited from someone who knew VB.NET better than I do/did. I consider myself a perpetual amateur developer. E) The project wasn't hugely popular anyways with no real use (at least public facing use )

Sounds like you have Visual Studio installed on the machine. What I'd do is go into Options -> Debugging -> Just-In-Time and disable Native and Managed debugging (and optionally Script, but MaNGOS doesn't use that).

If you have to hack it to get it to work properly and well, the devs have failed. Right, because if Microsoft released highly insecure, unstable platforms, they would: 1) Be the dominate server platform 2) Wouldn't have shareholders breathing down their backs 3) Be highly successful Oh wait...They're all of those things! My bad. :rolleyes: By the way, you could run MaNGOS on Microsoft Hyper-V Server, which is also free.

Rev 9958 Microsoft Visual Studio 2010 Ultimate 32bit Release build Revision: * * 9958 b49cc67e86846ebbeefe71593ad539796fa91695 Date 22:5:2010. Time 21:45 //===================================================== *** Hardware *** Processor: Intel(R) Pentium(R) III CPU - S 1400MHz Number Of Processors: 2 Physical Memory: 3997184 KB (Available: 3188276 KB) Commit Charge Limit: 4194303 KB *** Operation System *** Microsoft Windows Server 2003 Enterprise Edition Service Pack 2 (Version 5.2, Build 3790) //===================================================== Exception code: C000001D ILLEGAL_INSTRUCTION Fault address: 0064876B 01:0024776B C:\\ManGOS\\mangosd.exe Registers: EAX:000072A4 EBX:6DA0E45C ECX:6DA0E080 EDX:00000001 ESI:6DA87F90 EDI:00000022 CS:EIP:001B:0064876B SS:ESP:0023:09E89C5C EBP:09E89C68 DS:0023 ES:0023 FS:003B GS:0000 Flags:00010212 Call stack: Address Frame Function SourceFile 0064876B 00000000 ?HandleAuraModIncreaseHealth@Aura@@QAEX_N0@Z+6B 006470F6 00000000 ?ApplyModifier@Aura@@QAEX_N0@Z+26 004B39CB 00000000 ?AddAura@Unit@@QAE_NPAVAura@@@Z+3FB 0052E472 00000000 ?_LoadAuras@Player@@IAEXPAVQueryResult@@I@Z+362 005579ED 00000000 ?LoadFromDB@Player@@QAE_NIPAVSqlQueryHolder@@@Z+1ABD 007B6D13 00000000 ?HandlePlayerLogin@WorldSession@@QAEXPAVLoginQueryHolder@@@Z+E3 007B793C 00000000 ?HandlePlayerLogin@WorldSession@@QAEXPAVLoginQueryHolder@@@Z+D0C 007B33D2 00000000 ?HandleEquipmentSetDelete@WorldSession@@QAEXAAVWorldPacket@@@Z+142 00476786 00000000 ?SetAura@Aura@@QAEX_N@Z+5F66 00444C94 00000000 ?RemoveMItem@Player@@QAE_NI@Z+3D24 00453744 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+1114 00985AB4 00000000 ?invoke@ACE_OS_Thread_Adapter@@UAEKXZ+74 78AFC6DE 00000000 _endthreadex+3A 78AFC788 00000000 _endthreadex+E4 77E6482F 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C82860C 00000000 KiFastSystemCallRet+0 7D1F5EDB 00000000 LookupPrivilegeValueW+114 7D1F5F82 00000000 LookupPrivilegeValueW+1BB 7D247667 00000000 StartServiceCtrlDispatcherA+93 00452B56 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+526 004410FE 00000000 ?RemoveMItem@Player@@QAE_NI@Z+18E 00446EB3 00000000 ?at_exit@MaNGOS@@YAXP6AXXZ@Z+693 77E6F23B 00000000 ProcessIdToSessionId+209 Call stack: Address Frame Function SourceFile 7C82860C 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 0093A553 00000000 ?__ace_assert@@YAXPBDH0@Z+363 009AC511 00000000 ?wait_task@ACE_Thread_Manager@@QAEHPAVACE_Task_Base@@@Z+1E1 009A82EF 00000000 ?wait@ACE_Task_Base@@UAEHXZ+F 00452AE4 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+4B4 7D1F5E91 00000000 LookupPrivilegeValueW+CA 77E6482F 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C82860C 00000000 KiFastSystemCallRet+0 77E424FD 00000000 Sleep+F 00452E5D 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+82D 00455F54 00000000 ?step@barGoLink@@QAEXXZ+1F24 00453744 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+1114 00985AB4 00000000 ?invoke@ACE_OS_Thread_Adapter@@UAEKXZ+74 78AFC6DE 00000000 _endthreadex+3A 78AFC788 00000000 _endthreadex+E4 77E6482F 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C82860C 00000000 KiFastSystemCallRet+0 77E424FD 00000000 Sleep+F 00452E5D 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+82D 00455F54 00000000 ?step@barGoLink@@QAEXXZ+1F24 00453744 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+1114 00985AB4 00000000 ?invoke@ACE_OS_Thread_Adapter@@UAEKXZ+74 78AFC6DE 00000000 _endthreadex+3A 78AFC788 00000000 _endthreadex+E4 77E6482F 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C82860C 00000000 KiFastSystemCallRet+0 77E424FD 00000000 Sleep+F 00452E5D 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+82D 00455F54 00000000 ?step@barGoLink@@QAEXXZ+1F24 00453744 00000000 ?GetStringDefault@Config@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PBD0@Z+1114 00985AB4 00000000 ?invoke@ACE_OS_Thread_Adapter@@UAEKXZ+74 78AFC6DE 00000000 _endthreadex+3A 78AFC788 00000000 _endthreadex+E4 77E6482F 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C82860C 00000000 KiFastSystemCallRet+0 09E88D00 00000000 0000:00000000 64A015FF 00000000

This is what you need. Unfortunately it doesn't look like it has been implemented.

This is where sprocs are a much better idea

Are you running SCSI-1 on that box?

VC++ is a language (Microsoft's implementation of C++). Visual Studio is an IDE. When you're using Visual Studio and MaNGOS, you're using MS VC++. VC++ can compile in either 32bit or 64bit modes (extra work needed with VS Express to be able to do so). While MaNGOS does have multiple threads, it doesn't have it where it "counts". Map code, IIRC, is not multithreaded. While a dual core processor will help, it is doubtful a Nehalem would have a significant performance gain over, say, a Core 2 Duo when it comes to running MaNGOS. If you're packing MaNGOS, MySql, and IIS or Apache on one machine, then it would probably help to have > 2 cores.

The 4GB limit is intentional (so they can divide up the space, although 64bit Windows Vista/Windows 7 can address something like 128GB of RAM). The 3.5-ish limit was not originally in place. It was done because of poor driver manufactures (i.e. nVidia, ATi, Creative). Yes, device address space is also placed at 4GB and working on down (that is why with the more graphics card RAM, the less available physical RAM there is to the OS). Windows Internals, 5th Edition: http://www.amazon.com/Windows%C2%AE-Internals-Including-Windows-PRO-Developer/dp/0735625301/ref=sr_1_1?ie=UTF8&s=books&qid=1273894225&sr=8-1

LAA has nothing to do with RAM. Please don't confuse RAM and VAS. Windows uses AWE. But AWE can only address certain data types. It isn't worth it to implement AWE at this point. No, lower bound is app, upper bound is kernel. There are no "gaps".

Your INNODB buffer looks fine (read hit at 99%).