[CN2012] windows 10 support/odbc

[Anquietas]

so ive seen some people are able to run this on windows 10/8. and id really like to know how. (im only using a hamachi server)

ive seen on that, other forum, about not using odbc at all, would that solve this issue? or create a whole set of other ones.

if anyone who is able to run CN2012 files on windows 10, care to share how they did it, thatd be great. especially since windows 7 is going the way of the dodo.

 

[RayT]

Eh i have no idea why you would have a problem with this, i didin't do anything to the client when i upgraded to windows 10 and am running just fine

 

[Anquietas]

Eh i have no idea why you would have a problem with this, i didin't do anything to the client when i upgraded to windows 10 and am running just fine

Server. Not client. I've had mixed replies. Some say it runs and connects. Majority say it doesn't. But I don't wanna keep my large pc running Windows 7 anymore. And dual boot annoys the crap put of me

 

[hannesa]

Test it on your own, try using direct sql connection instead of odbc.

example of connection string (normally at the end of _ServerInfo.txt):

"DRIVER={SQL Server};SERVER=MachineName\InstanceName;UID=YourSQLUser;PWD=YourPass"

instead of:

"DSN=Account;        UID=YourSQLUser;    PWD=YourPass"

let us know if you tried and it works, i don't have Win10, don't like that "Spy" product.

 

[Anquietas]

Test it on your own, try using direct sql connection instead of odbc.

example of connection string (normally at the end of _ServerInfo.txt):

"DRIVER={SQL Server};SERVER=MachineName\InstanceName;UID=YourSQLUser;PWD=YourPass"

instead of:

"DSN=Account;        UID=YourSQLUser;    PWD=YourPass"

let us know if you tried and it works, i don't have Win10, don't like that "Spy" product.

Yeah, I'll definitely try it on one of my laptops with 10. If anyone feels willing to try it too, maybe updated versions of management studio,etc. That'd be good.

 

[sei]

Test it on your own, try using direct sql connection instead of odbc.

example of connection string (normally at the end of _ServerInfo.txt):

"DRIVER={SQL Server};SERVER=MachineName\InstanceName;UID=YourSQLUser;PWD=YourPass"

instead of:

"DSN=Account;        UID=YourSQLUser;    PWD=YourPass"

let us know if you tried and it works, i don't have Win10, don't like that "Spy" product.

Tried it even though I was fairly sure it couldn't possibly be so easy, and nooo, of course it wasn't. So let's get the facts straight (taken from 10 minutes of searching through help section):

- Main problem has something to do with the IOCP which was apparently changed with Win 8 and thus Win 10 as well. "Solution" to that:

Maybe you guys should use Google more.............

To view the content, you need to sign in or register

If you don't know how to fix the issue still maybe you should update your computer to the latest service pack, or you can RE your winsock/acceptex dll's. I personally had this issue resolved a long time ago by RE the dll's. Wasn't that hard to do.

Service pack isn't an option on W10 - and unfortunately, I don't know crap about reverse engineering. Furthermore, I read once or twice that this IOCP stuff was not the only problem that people encountered.

Any other ideas maybe? Cause I would really like to be able to run the server on W10 as well.