2.30 Copy Protection Issues - Solution Here
Posted: Thu Sep 25, 2003 9:33 pm
Having noticed more then a few posts about patch 2.30 breaking peoples game, I thought I would repost the solution.
Uncommon Valor like a lot of games uses copy protection. The particular version of the copy protection gets upgraded when the game gets patched.
This particular flavour happens to have some issues running from CD/ROM drives configured as Slave devices within your computer.
All common PC's these days are IDE based, with capacity for 2 devices on 2 channels. Each Channel supports a Master and a Slave device.
If you have multiple CD/ROM/DVD/RW drives, you will probably find that one of them is configured as a Master, and putting the UV CD in that drive resolves your problem.
If you happen to be in the situation where you do not have a CD/ROM in your system that is configured as a Master, you need to adjust your devices around a little. In the worst case situation, you will have to go to your local computer store and buy a $10 IDE cable and shift your CD/ROM from the Slave position on the first channel to the Master position on the second channel.
Each of your devices (hard drive, cd/rom, dvd, etc) has some little jumpers that identify how to adjust between master and slave. If you cannot see a diagram on the unit, write down the part name/model and visit the manufacturers web site for the little chart of what the jumpers do.
Your first hard drive (the one your operating system is installed on) must be primary on channel 1. The other 3 can be mixed and matched as required as long as you do not configure a device as a slave with no master.
If this is too technical for you, you can find a local computer shop that can do the swap for a couple of bucks as it really is trivial for anyone who knows whats inside the case.
Just a FYI: This is not just a Matrix issue, Microsoft has the exact same problem as they use the same product for copy protection. Sooner or later you will have to have this fixed as you will buy a new game and find it does not work out of the box for this very same reason.
Hope this helps you folks who are stumbling through the 2.30 patch and finding that going back to 2.20 makes the game start working again...
Uncommon Valor like a lot of games uses copy protection. The particular version of the copy protection gets upgraded when the game gets patched.
This particular flavour happens to have some issues running from CD/ROM drives configured as Slave devices within your computer.
All common PC's these days are IDE based, with capacity for 2 devices on 2 channels. Each Channel supports a Master and a Slave device.
If you have multiple CD/ROM/DVD/RW drives, you will probably find that one of them is configured as a Master, and putting the UV CD in that drive resolves your problem.
If you happen to be in the situation where you do not have a CD/ROM in your system that is configured as a Master, you need to adjust your devices around a little. In the worst case situation, you will have to go to your local computer store and buy a $10 IDE cable and shift your CD/ROM from the Slave position on the first channel to the Master position on the second channel.
Each of your devices (hard drive, cd/rom, dvd, etc) has some little jumpers that identify how to adjust between master and slave. If you cannot see a diagram on the unit, write down the part name/model and visit the manufacturers web site for the little chart of what the jumpers do.
Your first hard drive (the one your operating system is installed on) must be primary on channel 1. The other 3 can be mixed and matched as required as long as you do not configure a device as a slave with no master.
If this is too technical for you, you can find a local computer shop that can do the swap for a couple of bucks as it really is trivial for anyone who knows whats inside the case.
Just a FYI: This is not just a Matrix issue, Microsoft has the exact same problem as they use the same product for copy protection. Sooner or later you will have to have this fixed as you will buy a new game and find it does not work out of the box for this very same reason.
Hope this helps you folks who are stumbling through the 2.30 patch and finding that going back to 2.20 makes the game start working again...