RE: CentOS 4.x Cabal releases

Maybe someone can help with this?

Trying to build on CentOS 6.x (64bit or 32bit doesnt matter)
SQL = Server 2008 R2 (32 or 64) w/ SQL 2008 (32 or 64)

these are the issues in the quote below. (and yes the ports are effing forwarded lol)

One of the problems is being able to create accounts, so we can't even really tell if the server is working other then "Login Incorrect blah blah at login...due to md5 driver issue*see below), which combined with "service cabal status" all checking OK, tells me it is. Obviously login has not been possible. GM Tools do not work (various errors from framework [which is either N/A or built in OS], to weird duplicate row problems.

One thing I have noticed is that in the ACCOUNT DB, the column in auth password is set to char(30).....md5 hash's generate (vchar), and often times more then 30 in length which can cause the errors. Changing this in the DB's is not possible without destroying the data within.

is anyone using Cabal on a newer OS server combo? let me know the OS and bit...and maybe a link to any additional drivers or baseurl's (centos) needed.

Maybe a revised 64bit release can be done to catch up with the newer OS's (If I can get these things)

Quote:

I have some questions about your old Cabal releases.. To get straight to the point, older versions of CentOS have become obsolete and live support for them is no longer available. This is no big deal, I know how to redirect the baseurl to vault.centos, so thats no issue. What the issue I am coming across is installing your files into a newer CentOS shell (32 and 64), and then using it with newer versions of SQL (Standalone Datacenter 2008R2 x64 w/ MSSQL 2008 R2 x86 x64) lol actually I am having 2 issues, however only one of them is truly relevant to you. What is the difference in installation to a newer version of CentOS? There must be some little thing I am missing, that you as the originator would know of. Basically the issue is that the server is totally seeing the sql, and they talk fine, however they I continue to get an error in regards to a DSN (cabalgame) after successfully connecting to 5 of 6 DB's all of the information is 100% correct (this error comes mostly from the DBAgent(s), which leads me to believe a settings error, either somewhere serverside or sql side....

Now my second error is a very interesting one, and very annoying as well. I am finding it impossible to set a path to the xp_md5 drivers. No matter how I try, it will not save the file path to the dll. I have tried through script, I have tried through file placement directly into the binn with a schema switch from dbo to sys (this was microsofts idiot advice), I have even tried with the stupid little "Visual Aids" tool they have that lets you simply click and drag....no matter what you do, everytime you come back to check, it has not saved the file location ...lol...now that is pissing me off...but, I will figure it out im sure...

Basically what I need to know is are there any super important and uncommon things that need to be done for a migration to a newer OS? Or is it really just as simple as running the correct install (as in your guide for 4.x[7 i think])?

Thanks in advance for any random info or ideas you may give