Error in zone
 

I'm running 6.1dr1 and i'm getting this in the zone window Something about augslot1 and an opcode error and it keeps asking me if i'm connected to a minilogin server anyone have a fix?

---------------------------------------------
[05.23. - 16:13:39] Starting Log: logs/eqemu_error_world_3668.log
[05.23. - 16:13:39] Database::GetSharedBank(int32 account_id): #1054: Unknown column 'augslot1' in 'field list'
[05.23. - 16:24:55] Database::GetSharedBank(int32 account_id): #1054: Unknown column 'augslot1' in 'field list'

---------------------------------------------
[05.23. - 16:14:03] Starting Log: logs/eqemu_debug_world_3668.log
[05.23. - 16:14:03] Unable to convert EQ opcode 0x071e to an emu opcode.
[05.23. - 16:14:08] World: ClientList[0x004d4528]::FindByAccountID(0x00000002) iterator.GetData()[0x0038fb98]
[05.23. - 16:25:24] Unable to convert EQ opcode 0x071e to an emu opcode.
[05.23. - 16:25:43] World: ClientList[0x004d4528]::FindByAccountID(0x00000002) iterator.GetData()[0x0038fb98]

Originally i meant to use minilogin but couldn't get it to stop freezing on password entry so i decided to just use eqemulator.net How do i stop this code?

ERROR! ID is 0!!!
Is this server connected to minilogin?
Could not find a minilogin account, verify ip address logging into minilogin is
the same that is in your account table.


So far everythings fine but I keep getting dropped when zoneing and when i log back in i'm in the zone i zoned to.

Ok fixed the minilogin part "alter table accounts drop minilogin_ip;" npnp no more crashing while zoneing weee

But now I'm noticeing a new problem. No items save. Once I log out their gone poof!. And I can't delete char's from the char select menu i have to do it manually in the DB. I'm getting lots of access violations when using eqemu admin also.

I can't delete a char also with eq interface, i need to delete in Db..

Well, i don't know what my problem was but I found a post that someone had a 6.1 compatable database and I used their inv sharedbank and acct tables and so far no problems still testing.