Daily Archive for September 22nd, 2009

Proxmox OpenVZ Server 2 NICs 2 Gateways

Published on 2:00 pm - Tuesday 22 September 2009 in Hints and Tips, Resources and Time of the Time. 0 Comments Tags: , , , .

These are two solutions that worked for me. They are by no means the only solutions.

My Predicament.
A server (a Dell SC440), with two physical network interfaces. Our office has two ISP connections (DSL broadband). We have the one internal network range (192.168.1.0/24) with two gateways (1.254 and 1.221).

I have installed Promox on the server. I wanted to be able to choose which gateway the guest containers used, instead of them being locked into using the same gateway as the host server. Some of the guest OS containers will host services via the first ISP, and the others will host services via the second ISP. (obviously with firewall rules etc configured in our gateways). So the container gateway entries need to point to their respective ISP/Gateway.

Note: While the security advantage of venet over veth is certainly worthwhile in a hosting environment (and others as well), in my case, we have two hardware firewalls that haven’t let us down yet, and there is little to no concern for the possibility of an internal hacker (there are only three of us!)

Continue Reading Proxmox OpenVZ Server 2 NICs 2 Gateways

Share This:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • email
  • Slashdot

Sacred 2 on Windows 7

Published on 12:00 pm - Tuesday 22 September 2009 in Hints and Tips and Time of the Time. 37 Comments Tags: , , , , , , , , .

Kudos go to my girlfriend for sussing this one out.

Recently, we came across a conundrum concerning the computer game Sacred 2 running under Windows 7. Long story short, it just wouldn’t work. It should be noted that the reason for this not working, has nothing to do with Nvidia / ATI Graphics cards, but it is related to Physx/Ageia. Make sure you have the latest version of Physx installed. Sacred 2 does come with the last version of Physx known as Ageia Physx (before nvidia bought it and rebranded it to just Physx). You can also obtain the latest stand alone Physx package from the nvidia website. Even if you have an ATI graphics card, you still need to have this installed to play Sacred 2 and any other games that require Physx. So long as your CPU supports it and it is powerful enough, you’ll get CPU powered physics, instead of physics powered by your graphics card. Some people call this “Software Physics” or “Software” mode. I’ve noticed no performance difference between a computer playing Sacred 2 with an Nvidia graphics card and a computer with an ATI graphics card.

This fix should work for owners of Sacred 2 under Windows 7, regardless of the version  you have (Steam, Impulse, Stand alone or whatever).

  1. Create a shortcut to the Sacred 2 executable. You’ll find it in the game directory, in another directory called ‘system’. For me, it is: D:\Games\Steam\SteamApps\Common\Sacred 2\System\Sacred2.exe
  2. Put the shortcut on your desktop, or somewhere handy.
  3. Right click the shortcut and select properties
  4. Click the Shortcut tab
  5. In the Target field, you need to add the following: -skipopenal -nocpubinding. The contents of my Target field look like this: "D:\Games\Steam\SteamApps\common\sacred 2\system\sacred2.exe" -skipopenal -nocpubinding
  6. Click Apply and Click OK.
  7. Double click the shortcut and play Sacred 2!

Still can’t get it to work? Leave a comment and I’ll see what I can do to help you out. Further comments and suggestions are welcome. These are just simply the steps that worked for us. In case you are wondering, we are using the RTM (Release To Manfacture) version of Windows 7 (we are Microsoft Technet Partners). This is the same version that is available to consumers and end users as of mid October 2009.

Share This:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • email
  • Slashdot