04-12-2013, 07:06 AM
Hello guys of SRCDS,
I currently have an issue with running SRCDS TF2 Server on a Windows Server 2012 OS (a.k.a the Windows 8 Server).
This are my specs:
Server OS: Windows Server 2012
Processor: Intel® Xeon® CPU E3-1245 V2 @ 2.40GHz
Ram: 32GB
Game: Team Fortress 2
Start Up Command: "c:\HLserver\orangebox\srcds.exe -console -game tf -port 27015 +maxplayers 24 +map ctf_2fort"
*A basic start up command to just test if the server works in general
Admin Mods: None at the moment, since the server won't start up.
The issue per say is when starting up the server using the start up command, I receive this information in the log:
Of course since any smart person would be able to read this, it is an OS Reading error, so my question here is that: Is there a possibility to bypass this error, or do the admins know this error and are trying to update this for the new Windows Server. Any comments will be helpful, just please don't flame or cause intentional rage.
Thank you,
Nomulous
I currently have an issue with running SRCDS TF2 Server on a Windows Server 2012 OS (a.k.a the Windows 8 Server).
This are my specs:
Server OS: Windows Server 2012
Processor: Intel® Xeon® CPU E3-1245 V2 @ 2.40GHz
Ram: 32GB
Game: Team Fortress 2
Start Up Command: "c:\HLserver\orangebox\srcds.exe -console -game tf -port 27015 +maxplayers 24 +map ctf_2fort"
*A basic start up command to just test if the server works in general
Admin Mods: None at the moment, since the server won't start up.
The issue per say is when starting up the server using the start up command, I receive this information in the log:
Code:
Console Initialize.
Game.dll loaded for "Team Fortress"
osversion.cpp (186) : Assertion Failed : Unknown osvi.dwMinorVersion, assuming Windows2k8r2 : 2
Assert( Assertion Failed: Unknown osvi.dwMinorVersion, assuming Windows2k8r2: 2):osversion.cpp:186Of course since any smart person would be able to read this, it is an OS Reading error, so my question here is that: Is there a possibility to bypass this error, or do the admins know this error and are trying to update this for the new Windows Server. Any comments will be helpful, just please don't flame or cause intentional rage.
Thank you,
Nomulous
