reviving a somewhat older windows server, have some questions

[khalathas]

Hey all, I was running a private server for just a few select friends a year or so ago..interest waned and I shelved it for a while. Didn't delete anything, or move anything..but the server was running on my main machine, which I kept using and updating.

I decided I wanted to revive my server and play a bit again, but for whatever reason, the loginserver kept crashing within seconds of launching. I looked at version numbers and decided there were enough changes that rather than try to fix the problem, a full rebuild would be easier, so I went through the guide (again), compiled everything successfully, and got to the part where I set up the database. I know I could drop system and import the new one..but before I do that (yes I backed up as well), I wanted to just generally ask about how drastic the changes have been since roughly rev1900 to rev2500ish. Is it going to be relatively viable to move forward or should I just back up my account/character data and re-source the entire thing from scratch, then restore what I want? Also, should I be worried about client compatibility? I was using SoD prior.

[provocating]

At this point if it were me, I would backup everything. Install everything from scratch and make sure everything works with a new character, maybe even play a bit to make positive there are no issues. Then I would just create some SQL statements to move the accounts, characters and such over.

[khalathas]

Thanks, I think that's probably what I'm going to do. I've already backed up the database, and then I've gone further and selectively dumped individual tables (or in some cases, just specific data sets from those tables) to sql to restore. Was hoping not to have to do that, but it looks like the changes might be too much to easily just keep jumping upwards by upgrades/revision imports.

I am going to try to just drop the system and keep accounts intact first..unless there have been major changes to those tables as well?

[provocating]

Well the best thing to do is try it. It will tell you pretty quick if there are problems, monitor those error log files.

[khalathas]

Well, as it turns out, apparently the login server is still crashing when the world server finishes loading zones and connects to it.

Problem signature:
Problem Event Name: APPCRASH
Application Name: EQEmuLoginServer.exe
Application Version: 0.0.0.0
Application Timestamp: 4d03c97f
Fault Module Name: LIBMYSQL.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4f8bcacf
Exception Code: c0000005
Exception Offset: 00009b3a
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[khalathas]

I didn't rip out all the installs and reinstall them from scratch, so I am backing up the current db, ripping everything out from the roots, and going 100% from scratch this time around, then I'll just source my backup db which contains the updates.

[khalathas]

Welp, got stopped in my tracks. uninstalled (and even manual purged) mysql, in prep to reinstall the correct version..
Installed correct version, got to configure it, and it can't start the service. Can't start it manually either. I've even gone through it a couple times uninstalling, purging the data folders manually, purging the service registry keys manually, etc...still can't get it. I think this machine is hosed as far as mysql goes, unless I wipe and reinstall windows. I'm going to move the whole thing to a virtual server for now until I build my dedicated box for it I think. Unless anyone knows how to get around that service issue...

[provocating]

I do both of my servers as VM's, there are so many advantages to it.

[khalathas]

Honestly I'm hopefully on the verge of a new job where what i want will be possible...so if that happens I intend to actually build 3-4 physical machines that actually support vSphere, and then run VM servers for various purposes, and actually have the zoneservers spread across the physical machines as well. I guess this might end up being my solution for now and then it'll just be portable to the vSphere machines when they're built.

[khalathas]

Apparently I'm stopped in my tracks yet again. Brand new server 2008r2 standard VM, and mysql again refuses to start as a service. I'm at my wits end on this one, and I've done this successfully all before. Anyone know how to deal with this mysql error log?

131116 17:23:15 [Note] Plugin 'FEDERATED' is disabled.
131116 17:23:15 InnoDB: Initializing buffer pool, size = 2.0G
131116 17:23:15 InnoDB: Error: cannot allocate 2147500032 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 30993228 bytes. Operating system errno: 8
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: Note that in most 32-bit computers the process
InnoDB: memory space is limited to 2 GB or 4 GB.
InnoDB: We keep retrying the allocation for 60 seconds...
131116 17:24:15InnoDB: Fatal error: cannot allocate the memory for the buffer pool
131116 17:24:15 [ERROR] Plugin 'InnoDB' init function returned error.
131116 17:24:15 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
131116 17:24:15 [ERROR] Unknown/unsupported table type: INNODB
131116 17:24:15 [ERROR] Aborting

131116 17:24:15 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete

[khalathas]

Ok, after making my 2nd vm and testing it yet again on a fresh install of win7...I'm forced to conclude that the problem is with mysql-5.1.72
I've found a copy of the 5.1.68 installer (since it isn't available on oracle's official site), and am trying that next.

[provocating]

They have most all of there old GA releases available on the MySQL site so you should have no issues finding old versions.

[khalathas]

weird, because I went to the old GA archives and it only offered me .72
either way I've got a fresh VM now, with a snapshot AT its immediate post-install state so I don't have to uninstall, I'll just revert to snapshot on failure...but I'm going to figure out why mysql hates me.

[provocating]

Snapshots rock.

[khalathas]

wow...I clearly have something wrong. Fresh vm, fresh 5.1.68, still have the "cannot start service" error on install. No clue at this point, and on the verge of giving up.

[provocating]

I am of limited help since my server is on Debian, but what O.S. is this and is it a fresh install? Where did you snapshot? Before or after the MySQL install?

[khalathas]

Incidentally, just to give specs, I'm currently running vmware workstation 10, windows 7 ultimate x64 with sp1, allocating 8gb of ram to the vm, with 2x dualcore cpus to the vm (I have plenty of hardware on the host machine). 60gb virtual hard drive. I am not patching in any way before the install of mysql. This is as fresh as it gets off the win7 install disc (an ISO I got through my MSDN subscription).

[khalathas]

The snapshot is immediately after win7 itself finishes its install. There isn't a single bit of post-install modification on it.

[provocating]

x32 or x64?

[khalathas]

OS is x64, I need that for the amount of RAM I'm allocating. I'm using the 32bit installer per the instructions in the server guide.

[provocating]

I see no reason to use the x32 bit of MySQL unless I am missing something. Revert your snapshot, install the x64 and try again. Also just for giggles disable the Windows Firewall.

[khalathas]

I'll give those a shot. I ONLY used the 32bit versions because the guide said to, and I've successfully used the guide to set up the server before (and had quite a bit of enjoyable playtime out of it). I do prefer using 64 bit when I can unless there's a specific reason not to.

[khalathas]

Hah. 64bit worked first try. I guess the 32 bit installer truly hates 64bit windows. I think I will keep the server as a vm and proceed with the rest then.

[khalathas]

speaking of ram, I wonder how much ram would be necessary cumulatively to run every single zone as a static, and only have dynamics for instanced content...

[provocating]

My personal findings, and this is just me....I had problems with static zones. Memory wise they did not tax my server at all, it was an issue with the day/night cycles and maybe a few old peq scripts that need TLC, the zone logs got huge and that told me the server was constantly having to write to these log files. Other zones would randomly shutdown and I think it was script problems, I run vanilla PEQ. I run a pseudo dynamic / static zone thing where the zones stay open for maybe an hour, then close if they are vacant.

[khalathas]

hmm..well what I was running was statics that contained any valid rare/named/group/raid targets that my friends and I were actively interested in. If it were too high or too low, I just kept 'em dynamic. Then again I'm also planning on those vsphere boxes and spreading the zoneservers out across them.

[provocating]

I may go back to statics but this time I will start with classics and run them for a while and weed out the bad zones, then go from there.

[khalathas]

Gah I could kick myself right now. In my frustrations last night to reinstall mysql I backed up the peq database, but I was still using the older system that used a separate peqlogindb database and forgot to back up my accounts. I still have all the character data, but now I gotta rebuild the accounts in the correct order so they attach to the character data properly >.<

[provocating]

Unless you have a ton, it should not be a major endeavor.

[khalathas]

*sigh* any ideas? Yes I put the login tables directly into peq instead of peqlogindb like they used to be.

[Debug] [11.17.13 - 23:55:46] Logging System Init.
[Debug] [11.17.13 - 23:55:46] Config System Init.
[Debug] [11.17.13 - 23:55:46] MySQL Database Init.
[Database] [11.17.13 - 23:55:47] Failed to connect to MySQL database. Error: ÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝ ÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝ ÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝÝ


[database]
host = localhost
port = 3306
db = peq
user = root
password = <edited out>
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5998
local_network = 192.168.1.

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = tblLoginServerAccounts
world_registration_table = tblWorldServerRegistration
world_admin_registration_table = tblServerAdminRegistration
world_server_type_table = tblServerListType

[khalathas]

I'm also getting a TON of errors in every single zone launch and on other files:

queryserv:
---------------------------------------------
[11.17. - 23:56:07] Starting Log: logs/eqemu_error_queryserv_3732.log
[11.17. - 23:56:07] Failed to connect to database: Error: #2003: Can't connect to MySQL server on 'localhost' (0)


Various zone errors, all the same it seems:

---------------------------------------------
[11.17. - 23:56:17] Starting Log: logs/eqemu_error_zone_3584.log
[11.17. - 23:56:17] Error in Zone::LoadTickItems: SELECT it_itemid, it_chance, it_level, it_qglobal, it_bagslot FROM item_tick (#1146: Table 'peq.item_tick' doesn't exist)

[lerxst2112]

Try 127.0.0.1 rather than localhost.

[khalathas]

lerxst thanks, that got me a bit further. Still having issues but I think that's from losing the login database and having to rebuild it by hand, slowly.

[khalathas]

ok new stumbling block. I redid my eqemu_config.xml and login.ini because my old versions were out of date and missing stuff for queryserv and what not. After fiddling with IPs and account names, I'm now to this in the login server window. Everything else seems to be functional at this point. ALL of my internal IPs are now 127.0.0.1, because using the computer's own address of 192.168.1.5 would get rejected for some strange reason.


[Debug] [11.18.13 - 23:28:45] Logging System Init.
[Debug] [11.18.13 - 23:28:45] Config System Init.
[Debug] [11.18.13 - 23:28:45] MySQL Database Init.
[Debug] [11.18.13 - 23:28:45] Encryption Initialize.
[Debug] [11.18.13 - 23:28:45] Encryption Loaded Successfully.
[Debug] [11.18.13 - 23:28:45] Server Manager Initialize.
[Network] [11.18.13 - 23:28:45] ServerManager listening on port 5998
[Debug] [11.18.13 - 23:28:45] Client Manager Initialize.
[Network] [11.18.13 - 23:28:45] ClientManager listening on Titanium stream.
[Network] [11.18.13 - 23:28:45] ClientManager listening on SoD stream.
[Debug] [11.18.13 - 23:28:45] Server Started.
[Network] [11.18.13 - 23:28:58] New world server connection from 127.0.0.1:49613
[Network Error] [11.18.13 - 23:28:58] Handle_NewLSInfo error, remote address was null, defaulting to stream address 127.0.0.1.
[World] [11.18.13 - 23:28:58] Server Tallon Zek Reborn(TZR) did not attempt to log in but this server requires a password.

[khalathas]

EDIT: nevermind. Solved it. I had the password for the server login table encrypted SHA like accounts are, put it into plaintext and it worked fine. :)

[khalathas]

Ok, I think this might be the last step to getting the server reanimated from the grave. I had forgotten that the old login db was a separate db, so in my fury to delete/reinstall mysql a few times a couple days ago, I deleted the whole directory after dumping peq, but forgetting about peqlogindb. I didn't empty recycle bin, recovered the raw data files, but don't have the server instance or anything in registry left. What's the easiest way to attach those raw data files to a server to extract whats in them? If I can get access, I can just migrate the data easy enough.

Edit: don't have the account data file..only had the adminregistration table and serverlisttype >.< by hand it is.

[wolfwalkereci]

Sounds like you have really been thrown some bad luck here.
Hope you figure it out, I'll watch this thread for a few days in case you have more issues that I might be able to assist with.

[khalathas]

Thanks Wolf, I think I actually managed to figure out most of it. I had to rebuild the login table by hand, which ended up making the tblLoginAccounts ID field out of sync with Accounts.lsaccount_id, so a simple query to rewrite that id to match the login table data made the rest sync up. Successfully logged in with multiple accounts now, characters, tested fights...I did briefly encounter a "invulnerable to melee" issue, but haven't since a reboot.

I do believe that unless unforeseen issues come up, the server is ready for play again, and luckily, all character and valuable player data is intact. :)

[wolfwalkereci]

Thats good to hear. Also you made sure, double checked & triple checked, to run all the SQL that match up with the version of source you are updating to?

[khalathas]

Yep, did that successfully. I'm still being very alert to other possible bugs popping up as a result of this transfer, but I'd rather have the headaches than lose all the progress the server has on its 50 or so characters, most of whom are max level (but horribly under-geared). :)

[khalathas]

Just because I know a couple people are watching and have helped me a lot already, I just wanted to report everything looks smooth so far, and thank you for the assistance! :)

[khalathas]

Ok I'm back. System works great on LAN...will not work for clients outside the router. They can get logged in and get to the server select screen..but they can't get character select. Black screen and dump to login screen. I know I have the port forwards needed (I did 7000-7100, 9000, and 5990-5999, to catch any ranges the server might want). I've gone so far as to temporarily DMZ the server machine itself. The OS firewall is completely disabled (and wouldn't matter since local works fine), and antivirus is not interfering either.

The only two things I can think of at this point would be either a config file being wrong somewhere, or Verizon FIOS blocking the world server's incoming ports, but not the login server's. When I watch the command windows on the server, internally I see the login server catch and resolve the login, then disconnect as it hands the client off to the world server, which I see clearly pick it up and proceed happily. When the client is remote instead of local, I see the login server pick up, resolve, and hand off...but the world server never receives the handoff.

To clarify, I'm using the SoD client, and it works internally perfectly...just does not work externally...and the server at this point is DMZ'd.

I shall include my eqemu_config.xml and login.ini files for scrutiny.

eqemu_config.xml:

<?xml version="1.0"?>
<server>
<world>
<shortname>TZR</shortname>
<longname>Tallon Zek Reborn</longname>

<!-- Only specify these two if you really think you need to. (read: You don't) -->
<address>96.252.231.59</address>
<localaddress>192.168.1.25</localaddress>

<!-- Loginserver information. Defaults shown -->
<loginserver>
<host>192.168.1.25</host>
<port>5998</port>
<account>(scrubbed for forum)</account>
<password>(scrubbed for forum)</password>
</loginserver>

<!-- Server status. Default is unlocked -->
<!--<locked/>-->
<!-- <unlocked/> -->

<!-- Sets the ip/port for the tcp connections. Both zones and console (if enabled). Defaults are shown -->
<tcp ip="192.168.1.25" port="9000" telnet="disable"/>

<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>(scrubbed for forum)</key>

<!-- Enable and set the port for the HTTP service. Defaults are shown -->
<http port="9080" enabled="false" mimefile="mime.types" />
</world>

<!-- Chatserver (channels) information. Defaults shown -->
<chatserver>
<host>channels.eqemulator.net</host>
<port>7778</port>
</chatserver>

<!-- Mailserver (in-game mail) information. Defaults shown -->
<mailserver>
<host>channels.eqemulator.net</host>
<port>7778</port>
</mailserver>

<zones>
<defaultstatus>20</defaultstatus>

<!-- Sets port range for world to use to auto configure zones -->
<ports low="7000" high="7100"/>
</zones>

<!-- Database configuration, replaces db.ini. Defaults shown -->
<database>
<host>192.168.1.25</host>
<port>3306</port>
<username>root</username>
<password>(scrubbed for forum)</password>
<db>peq</db>
</database>

<qsdatabase>
<host>192.168.1.25</host>
<port>3306</port>
<username>root</username>
<password>(scrubbed for forum)</password>
<db>peq</db>
</qsdatabase>

<!-- Launcher Configuration -->
<launcher>
<!-- <logprefix>logs/zone-</logprefix> -->
<!-- <logsuffix>.log</logsuffix> -->
<!-- <exe>zone.exe or ./zone</exe> -->
<!-- <timers restart="10000" reterminate="10000"> -->
</launcher>

<!-- File locations. Defaults shown -->
<files>
<!-- <spells>spells_us.txt</spells> -->
<!-- <opcodes>opcodes.conf</opcodes> -->
<!-- <logsettings>log.ini</logsettings> -->
<!-- <eqtime>eqtime.cfg</eqtime> -->
</files>
<!-- Directory locations. Defaults shown -->
<directories>
<!-- <maps>Maps</maps> -->
<!-- <quests>quests</quests> -->
<!-- <plugins>plugins</plugins> -->
</directories>
</server>


login.ini:

[database]
host = 192.168.1.25
port = 3306
db = peq
user = root
password = (scrubbed for forum)
subsystem = MySQL

[options]
unregistered_allowed = FALSE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5998
local_network = 192.168.1.

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = tblLoginServerAccounts
world_registration_table = tblWorldServerRegistration
world_admin_registration_table = tblServerAdminRegistration
world_server_type_table = tblServerListType

[khalathas]

Ok guys, figured it out I believe.
I have one of Verizon's newest ActionTec routers. I DO have the ports forwarded correctly, but for some lame reason, on the new models, the firewall inbound policy overrides the port forwards, whereas on previous models, the forwards overrode the global policy. I had to kill that policy and suddenly it works. Take note for anyone else with a similar issue. :)

[Fangb0n3r]

I'm currently the one working with Khalathas, trying to connect to his server from my home PC via internet, OUTSIDE his LAN. I log in just fine, server select works fine, but when I get to Character Select, nothing works. I can see (and select between) my characters that were already there from when the server was active before. None of the buttons are responsive at all: Create New Character, Delete Character, Enter World, Quit... None of them trigger anything when clicked. Also, the character models seem glitchy and unstable.

I'm running Windows 10 (not activated), AMD FX 9370 8-core CPU, 32 GB DDR3 RAM, Dual MSI GTX660 Ti's in SLI

I have EQ operating from a single core on my CPU and I have Windows Firewall turned off. I'm using the EXACT SAME client file as Khalathas is using to connect locally.

[Uleat]

Do you have a way of testing on a non-win10 machine?

[Fangb0n3r]

If I have time tomorrow, I'll try to get it set up on my Win7 laptop.

[Fangb0n3r]

We just wiped my system and went back to Win7. Installed dxredist 2005 to get the client to run. Made sure d3dx9_30.dll was present. Same exact result. Buttons on char select do not respond to mouse. Can log in if I hit enter instead, but all the npcs and my character seem "jittery", like constantly shaking. Walking speed is extremely fast as well.

Have also ruled out WAN/firewall issues, by bringing pc to LAN and connecting. Server VM has firewall completely disabled. Other pcs on both LAN AND WAN able to play without problems, on both win7 and win10. This rules out the server and firewall/router.

Same exact copy of client from working machine being used, so this rules out the client as well. Clearly the issue is with the pc itself. Client version from logs below.

If anything else might be helpful in diagnostics, let me know.

[Sat Jul 30 17:16:08 2016]00000:Starting EverQuest (Built May 10 2013 23:30:08)
[Sat Jul 30 17:16:08 2016]00001:EverQuest Configuration Type: RELEASE_NON_AVATAR
[Sat Jul 30 17:16:08 2016]00002:Timezone: UTC-5h00m
[Sat Jul 30 17:16:08 2016]00003:Loading graphics DLL.
[Sat Jul 30 17:16:08 2016]00004:Parsing INI file .\defaults.ini
[Sat Jul 30 17:16:08 2016]00005:INI file .\defaults.ini loaded.
[Sat Jul 30 17:16:08 2016]00006:Parsing INI file .\eqclient.ini
[Sat Jul 30 17:16:08 2016]00007:INI file .\eqclient.ini loaded.
[Sat Jul 30 17:16:09 2016]00008:Graphics DLL Configuration Type: GraphicsDLL9
[Sat Jul 30 17:16:09 2016]00009:Graphics DLL Version 2.00.70657
[Sat Jul 30 17:16:09 2016]00010:Initializing timers.
[Sat Jul 30 17:16:12 2016]00011:Psh (4197).

[khalathas]

After much much MUCH testing, and even OS reinstalls, and using other machines as controls...even a VM with the client in it...I'm forced to come to the conclusion that the problem is either his motherboard, cpu, or gpu. The game performs flawlessly in every case that doesn't involve his physical hardware, but the moment it runs on HIS machine, even inside the VM, the hyper-fast glitching occurs.

[Nightrider84]

Hey Fang I actually know what your problem is and your not going to like the answer at all. So basically if you have an amd processor or intel with 4.2Ghz or higher speed it causes a "hyper speed" glitch with eq where everything runs at warp speed. There is no fix for it, its related to the multiplier set by your cpu on your motherboard. Only temporary fix is to underclock your processor to make it run correctly. since your cpu runs at 4.7ghz your screwed basically. You gotta go into bios and drop your multiplier down. Also windows 10 doesn't have anything to do with how the game runs. I have multiple dual log os's setup on a few pcs and don't run into any kind of compatibility issues.

[blackdragonsdg]

The hyper run issue has been around for a while. Older AMD dual cores had similar issues. They basicly needed to be optimized so that older applications would stay sync'd. For those processors there was a program released by AMD that remedied the problem or you could alter the processor affinity which is talked about in the following link.
http://www.eqemulator.org/forums/showthread.php?t=25327

[DanCanDo]

I run nothing but amd chips (loyal for 20 years now). I can't speak for anyone else,
but I've never had problems running eq (client or server) on my boxes. I've never
used win 10, been sticking mostly with win 7.
This last box I built, 4 Ghz (8-core) chip, purring like a kitten, especially in eq on win 7.
I always run defaults with no need to OC. But thats a preference :P

[Nightrider84]

The optimizer fix and the compatibility fix don't work for the newer cpu's because of how high their multiplier is. You can try the software fixes but it won't do any good. Also if you have any amd chip newer than a 8350 its clocked higher than 4.2 ghz which is what causes the problem. I run a 8350 myself clocked to 4.2ghz anything higher and it causes the issue. Also the previous multicore issue is already patched into any client newer than UF.

[Uleat]

You can check dbg's website to see if anything has been said..

..usually it's fixed in a patch - and, unfortunately, we don't support any newer clients currently...

[khalathas]

Thanks for the answers all, I'll make sure he sees these.

In an offtopic note, but on the same server subject, this thing has been dormant for 3 years. Looking to update the db a bit, but not sure how much this might screw things up. How do I even tell what version I have sourced, and if I did a system dump/load (preserve player data), were there massive changes that might bite me?

[khalathas]

udpate, found version in variables table: 070_pop_cvs

[blackdragonsdg]

How do I even tell what version I have sourced, and if I did a system dump/load (preserve player data), were there massive changes that might bite me?

About two years ago the player profile was moved from a blob to normal database which will impact your attempts at saving/restoring character data. If I were you I would focus on getting your database schema current then worry about data updates like spawns and items.

Be sure to backup your database before you start updating.

[Fangb0n3r]

I found a workaround for the Warping issue. AMD's Overdrive utility allows me to set affinities/ adjust clock speeds and whatever else I might want to do to my CPU. I'm running an FX 9370 at 4.4Ghz base. Overdrive lets me constrain all that to roughly 3.9-ish on the fly so I can play EQ without issue. We do appreciate all the input, though. Source: https://forums.daybreakgames.com/eq/index.php?threads/eq-amd-fx-help-or-fix-please.212991/