cerbie
1000+ Head-Fier
- Joined
- Mar 12, 2005
- Posts
- 1,219
- Likes
- 12
Quote:
Yes, but you can, with vigilance, get around that.
Driver Signature Enforcement Overrider Downloads
Even with it, I have to use the boot menu option to not need signed drivers on each boot, but it makes it possible[size=xx-small] (without it, I can't use unsigned drivers even when using the boot menu option for it)[/size]. There are apparently other ways around it, but that's the only one that worked for me. I do think it should be easier, and that it does represent Microsoft's general desire to remove control from users, as well. A permanent toggle requiring a UAC prompt would be enough to handle 99% of the security reasons for requiring signed drivers. Or, even a prompt each time an unsigned driver wishes to load, to handle that other 1%. Absolute refusal should only be able to be applied in a managed business setting, IMO.
Also, for music playback, I would recommend disabling CPU power management[size=x-small] (or at make the min and max the same in the performance profile)[/size]. It randomly skips all the time, otherwise[size=xx-small] (less so using WASAPI, but it still will do it)[/size], though I'm sure playing everything back over a network doesn't help.
For 32 v. 64: running 32-bit software in the 64-bit OS can be up to around 10% slower, and most software will run the same speed as in the 32-bit OS. I've yet to find a 32-bit Windows app that wouldn't run just fine, though some have needed Vista or XP compatibility modes set. Also, I love running in 8GB w/o swap.
As you might guess, Windows 7 is not replacing Linux for my main desktop--even PulseAudio is pretty reliable, if a CPU hog, and a config PITA, thanks to ALSA[size=xx-small] (Vista's WM features still can't touch my customized Compiz, too)[/size]. I don't really hate running it, though.
Originally Posted by terrymx /img/forum/go_quote.gif I don't know anything about 64bit OS so I can't help you there, but if you plan to use more than 4gb of ram it may be a consideration. I'm not 100%, but isn't 64bit Windows OS only accept signed drivers? That would be pointless for me. (...) |
Yes, but you can, with vigilance, get around that.
Driver Signature Enforcement Overrider Downloads
Even with it, I have to use the boot menu option to not need signed drivers on each boot, but it makes it possible[size=xx-small] (without it, I can't use unsigned drivers even when using the boot menu option for it)[/size]. There are apparently other ways around it, but that's the only one that worked for me. I do think it should be easier, and that it does represent Microsoft's general desire to remove control from users, as well. A permanent toggle requiring a UAC prompt would be enough to handle 99% of the security reasons for requiring signed drivers. Or, even a prompt each time an unsigned driver wishes to load, to handle that other 1%. Absolute refusal should only be able to be applied in a managed business setting, IMO.
Also, for music playback, I would recommend disabling CPU power management[size=x-small] (or at make the min and max the same in the performance profile)[/size]. It randomly skips all the time, otherwise[size=xx-small] (less so using WASAPI, but it still will do it)[/size], though I'm sure playing everything back over a network doesn't help.
For 32 v. 64: running 32-bit software in the 64-bit OS can be up to around 10% slower, and most software will run the same speed as in the 32-bit OS. I've yet to find a 32-bit Windows app that wouldn't run just fine, though some have needed Vista or XP compatibility modes set. Also, I love running in 8GB w/o swap.
As you might guess, Windows 7 is not replacing Linux for my main desktop--even PulseAudio is pretty reliable, if a CPU hog, and a config PITA, thanks to ALSA[size=xx-small] (Vista's WM features still can't touch my customized Compiz, too)[/size]. I don't really hate running it, though.