Jump to content

slypher

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by slypher

  1. How did you get your install so small. I'm using a 74GB Raptor for my install partition, so i'm trying to be as tight with the space as possible. Gonna set up a dual boot with XP pro. Thanks -s
  2. I also noticed some slow down, i'm gonna try this out. Thanks for the heads up. On a side note, i noticed that when scrolling on web pages that the screen does not move very smoothly at times with Vista. Turns out that this is some sort of IE7 issue, because the same thing happens with IE7 in Win XP. -s
  3. After you enable the Administrator account following neo_matrix.rs's directions, you will also have to adjust the permissions on the "system32" folder. You will not be able to edit anything in the folder. First make the Administrator account the owner of the folder, then enable all of the rights and you will be good after that. -s
  4. I have only used Vista for about two weeks, and when i switch back to my other pc which has XP, something is missing. I am really liking the "feel" of Vista. I don't know if its the rush of having "something new" or what. But i am really feeling Vista, especially Aero. Yes i agree that the OS is bloated as all heck. Plugging in my pocket pc phone, opens a sync page and brings everything to a crawl, which i hate! But still i really like the feel. So yes there is definitely more to an OS than its look, but deep down, why did anyone upgrade to XP from 2000 (the only real difference is the look) Count me in mostly for looks (i'm working on the other reasons to upgrade as we speak, such as security, stability, etc) my two cents -s
  5. Agreed, i have tested and the xp drivers will work for Vista 64. The big thing you have to do to avoid issues with booting into Vista is turn off the Driver signature enforcement. This checks to make sure that you are only using digitally signed 64 bit drivers (i think) with Vista, and will halt the boot process if it sees non signed drivers. There is a way to do it during every boot sequence, F8 i believe brings up the option. Another more effective way to do it is by doing the following: Setting the boot configuration. A boot configuration setting is available for prerelease builds that allows the suppression of the enforcement module in Windows to be persisted across boot sessions. Windows Vista includes a command-line tool, BCDedit, which can be used to set this option. To use BCDedit, the user must have Elevated User or Administrator privileges on the system. The most straightforward approach is to create a desktop shortcut to cmd.exe, and then right-click -> Run Elevated. The following shows an example of running BDCedit at the command prompt: // Disable enforcement - no signing checks Bcdedit.exe -set nointegritychecks ON // Enable enforcement - signing checks apply Bcdedit.exe -set nointegritychecks OFF // Disabling integrity check on an alternate OS // specified by a GUID for the system ID Bcdedit.exe -set {4518fd64-05f1-11da-b13e-00306e386aee} nointegritychecks ON
  6. I had the same issue with Vista 64 Bit. I ended up using the XP 64 bit drivers, because the so called "Vista Beta 64 bit" drivers on the ATI site never installed properly. The other poster has the right idea, install the basic video drivers (Standard VGA), reboot, then when prompted for new hardware found, point Vista to the ATI folder where the XP 64 bit drivers are located (the extracted files, not the .exe file) and you will be gaming in no time The only thing that is keeping me from using Vista 64 more often is the fact that i was never able to load Daemon tools on it. Kept getting stupid errors. Has anyone gotten this to work yet? -s
×
×
  • Create New...