So, I'm running a 3 core unmanaged VDS, and the processors appear as Xeon x5690's. I went to go download .NET framework 4.0 (I need to it to run Srcds admin program) and I don't know if I need the x64 version or the IA64.
This is the link I'm talking about: http://www.microsoft.com/download/en/de ... en&id=3556
As far as I can tell it's an Itanium processor and the OS is x64, but I don't know if it falls under this new ship architecture (I think hexacore?) that would use IA64 drivers.
Drivers specific-to-Processor
-
- New to forums
- Posts: 11
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Mon Dec 05, 2011 11:01 am
Re: Drivers specific-to-Processor
I guess I answered my own question, I ran the windows update and it said x64. I just wanted to make sure since I'm leery of windows updates anyways haha.
Re: Drivers specific-to-Processor
Yes, just x64 should be appropriate.
Re: Drivers specific-to-Processor
(didn't want to start a new thread)
Okay new question for you guys - I'm trying to access the desktop remotely with a website called logmein. Basically a website-based RDC. I'm logging in using the same credentials as when I remote desktop in, so I can see the servers running. But when I do it through the logmein website, it logs me in under a different windows user session, so consequently I can't access the servers/programs running under the normal admin account.
Any thoughts?
Okay new question for you guys - I'm trying to access the desktop remotely with a website called logmein. Basically a website-based RDC. I'm logging in using the same credentials as when I remote desktop in, so I can see the servers running. But when I do it through the logmein website, it logs me in under a different windows user session, so consequently I can't access the servers/programs running under the normal admin account.
Any thoughts?
Re: Drivers specific-to-Processor
A new thread is usually best for any new topic.
Are you running Windows 2003? If so, Windows does this automatically, and when using remote desktop, too. To reuse a session, you'll need to make sure that the remote desktop window is closed. It should then reconnect to that session when you log in again (if it doesn't, try using the task manager->users options to reconnect).
Are you running Windows 2003? If so, Windows does this automatically, and when using remote desktop, too. To reuse a session, you'll need to make sure that the remote desktop window is closed. It should then reconnect to that session when you log in again (if it doesn't, try using the task manager->users options to reconnect).
Re: Drivers specific-to-Processor
Thanks for the response.
I could only get it to work if I logged in to the machine and started up the servers first on the logmein remote connection. Then when I close that out, and I do a remote connection from within windows, it would connect to the same admin account. Otherwise, it creates a second user session for the default Admin account.
And yes, it's Windows 2003.
I could only get it to work if I logged in to the machine and started up the servers first on the logmein remote connection. Then when I close that out, and I do a remote connection from within windows, it would connect to the same admin account. Otherwise, it creates a second user session for the default Admin account.
And yes, it's Windows 2003.