- Joined
- May 26, 2007
- Messages
- 5,545
- Reaction score
- 1,315
Hashing records, and hashing passwords are two different things. A hash match can speed up a record search, it isn't used as the only means of identifying a password, as that would effectively mean that more than one password would work to access the account. Encryption of passwords is used, and the encryption will be performed in accordance with a key, which may or may not be a hash value of some other indeterminate data.
Buy MySQL is no good for PT, and will interfere with it's operation.
If you use SQL.dll then ODBC isn't used (apparently) as SQL.dll accesses the database via MDAC... if you don't use SQL.dll (or it's not configured correctly) then the server will fall back to ODBC.
ODBC, MDAC and NCLI are APIs for database access, and allow you to use an external database rather than programming your own into your application.
What "account" are you trying to log in to? Your game account, PC account, ISP account, Server account, GM account, SQL account? ... hell you could be talking about a hotmail account.
If (as I suspect) you mean logging in to SQL via MS-SQL-SMS (SQL Management) then the most common reason for not being able to log in via the password you set is because that account has been locked out, and on modern hardware the most common reason for a root (administrator) account being locked out of SQL is the ODBC control panel described in this, and many older guides.
The only cure I know of is to roll back and try again, except that I would always apply the ODBC connection directly in the registry without the ODBC "Database Sources" applet.
Buy MySQL is no good for PT, and will interfere with it's operation.
If you use SQL.dll then ODBC isn't used (apparently) as SQL.dll accesses the database via MDAC... if you don't use SQL.dll (or it's not configured correctly) then the server will fall back to ODBC.
ODBC, MDAC and NCLI are APIs for database access, and allow you to use an external database rather than programming your own into your application.
What "account" are you trying to log in to? Your game account, PC account, ISP account, Server account, GM account, SQL account? ... hell you could be talking about a hotmail account.
If (as I suspect) you mean logging in to SQL via MS-SQL-SMS (SQL Management) then the most common reason for not being able to log in via the password you set is because that account has been locked out, and on modern hardware the most common reason for a root (administrator) account being locked out of SQL is the ODBC control panel described in this, and many older guides.
The only cure I know of is to roll back and try again, except that I would always apply the ODBC connection directly in the registry without the ODBC "Database Sources" applet.