r3b00t3r
New Member
- Joined
- Dec 7, 2009
- Messages
- 39 (0.01/day)
- Location
- Alverca / Lisboa / Portugal
Processor | Intel Q9550 E0 @ 3825MHz |
---|---|
Motherboard | Asus P5Q Deluxe |
Cooling | Thermalright Ultra Extreme 120 Black + 10 X Noctua P12 |
Memory | 2X2GB GSkill Ripjaws 1200MHz 1.9V @ 5-5-5-15 |
Video Card(s) | 2 X EVGA GTX260 Core 216 55 nm SuperClocked @ SLI |
Storage | 1 X SSD GSKILL FALCON I 128GB + 1 X Samsung F3 2TB + 2 X Samsung F3 1TB @ RAID1 |
Display(s) | Samsung 223BW |
Case | modded Lian Li A77 |
Audio Device(s) | Creative X-Fi Xtreme Music |
Power Supply | Corsair HX620 |
Software | Windows 7 Ultimate x64 |
Benchmark Scores | about P22000 in 3DMark Vantage |
Good morning!
It is my first post in this forum. I used to just read a lot here, and now here I am...
I successfully enabled SLI in my Asus P5Q Deluxe, with 2 EVGA GTX260 Core 216 55 nm SuperClocked, but only in the second or third try. I'm using Windows 7 Ultimate x64.
Just running SLI string and halmod didn't make it for me. I had to run install.cmd of halmod in the command prompt to see that new hal.dll was not replacing the old one. I had to boot in repair mode, use the command prompt and then replacing hal.dll. After that, no problem at all.
Now I want to remove the watermark. I tried that "testsigning off" command, but that messes with drivers and boot. It's a definitely a no-go.
If anyone has a solution for this, I would apreciate!
Thanks!
It is my first post in this forum. I used to just read a lot here, and now here I am...
I successfully enabled SLI in my Asus P5Q Deluxe, with 2 EVGA GTX260 Core 216 55 nm SuperClocked, but only in the second or third try. I'm using Windows 7 Ultimate x64.
Just running SLI string and halmod didn't make it for me. I had to run install.cmd of halmod in the command prompt to see that new hal.dll was not replacing the old one. I had to boot in repair mode, use the command prompt and then replacing hal.dll. After that, no problem at all.
Now I want to remove the watermark. I tried that "testsigning off" command, but that messes with drivers and boot. It's a definitely a no-go.
If anyone has a solution for this, I would apreciate!
Thanks!