All right, I'm doing it. No, not that
I have another 2G of RAM on the way, so Win7 Professional x64 is going on the machine tonight. Wish me luck, and hopefully I'll be flight operational again in a few days
Taking the plunge.
Moderators: Staff, HR, Flight Ops
-
- Member with over 30 posts
- Posts: 562
- Joined: Tue Dec 04, 2007 6:28 am
- Location: Brisbane - Australia
- Contact:
Re: Taking the plunge.
RAM is so cheap these days
Have been running win 7 x64 since day dot with 4 g of ram
U will have no dramas
Have been running win 7 x64 since day dot with 4 g of ram
U will have no dramas
Mike Bridge
Brisbane, Australia - YBBN
#3316
Brisbane, Australia - YBBN
#3316
Re: Taking the plunge.
Yeah, it sure is. So much so, that I wish I was in the position to build a new machine using faster RAM and even more than 4G. BUT, I don't have a grand for the parts I want.
I'm thinking the install will be no trouble, of course, it's just the reinstalling of everything, PIREP software, aircraft.cfg file, etc. that will be a lot of work. I can't imagine it will have trouble seeing my old Sidewinder FF steering wheel for my racing games, but you never know........
I'm thinking the install will be no trouble, of course, it's just the reinstalling of everything, PIREP software, aircraft.cfg file, etc. that will be a lot of work. I can't imagine it will have trouble seeing my old Sidewinder FF steering wheel for my racing games, but you never know........
-
- Member with over 30 posts
- Posts: 562
- Joined: Tue Dec 04, 2007 6:28 am
- Location: Brisbane - Australia
- Contact:
Re: Taking the plunge.
It has been out for a while now mate - so should be no problem for drivers /)
Remember u can use vista x64 drivers if no win7 ones!
Remember u can use vista x64 drivers if no win7 ones!
Mike Bridge
Brisbane, Australia - YBBN
#3316
Brisbane, Australia - YBBN
#3316
Re: Taking the plunge.
John
Going by some of your posts you know more about it than I do but I feel I should warn you that W7 X 64 has a lots of "security" things built into it, most of which are a bloody nuisance, and prevent programs from "seeing" each other on the hard drive or worse, drives if you have more than one. I think it is known as UAC , "User Access Control" or something.
One thing I've learnt is to install everything with the "Run as Administrator" selection. Sometimes you don't get this selection in the origional downloaded .zip file. In this case, first unzip to a folder on your C drive. (I have created a couple called TEMP 1, and TEMP 2) or whatever you want to call them. Unzip into this and then right click on the "install.exe" or whatever it's called and select "Run as Admin.....".
This even applies to installing such things as FSUIPC.
Also when starting anything with a shortcut on the desk, or from the start menu, or wherever, - again right click and select the "Run as Admin...." to get it going. This came from Sascha Felix one of the owners of FS Commander, and it definitely works.
John
Going by some of your posts you know more about it than I do but I feel I should warn you that W7 X 64 has a lots of "security" things built into it, most of which are a bloody nuisance, and prevent programs from "seeing" each other on the hard drive or worse, drives if you have more than one. I think it is known as UAC , "User Access Control" or something.
One thing I've learnt is to install everything with the "Run as Administrator" selection. Sometimes you don't get this selection in the origional downloaded .zip file. In this case, first unzip to a folder on your C drive. (I have created a couple called TEMP 1, and TEMP 2) or whatever you want to call them. Unzip into this and then right click on the "install.exe" or whatever it's called and select "Run as Admin.....".
This even applies to installing such things as FSUIPC.
Also when starting anything with a shortcut on the desk, or from the start menu, or wherever, - again right click and select the "Run as Admin...." to get it going. This came from Sascha Felix one of the owners of FS Commander, and it definitely works.
John
Re: Taking the plunge.
Thanks for the info guys. As of last night, Windows is installed, as is FSX and all my addons. Now I just need to do my GCVA installs and configure everything again.
Re: Taking the plunge.
You were right John. Unless you run the PIREP as administrator, it freaks out and gives connection errors. Especially since my user account is part of the Administrator's group. It's kind of a pain, but it's too late now, hehe. Anyway, the only thing I have left is adding the liveries, and editing the .cfg files so they show up in the game.
On another irritating sidenote, the whole point of doing this (using more memory), seems to be pointless now. My motherboard only displays 3G of RAM installed, eventhough there is 4G installed. Windows even sees the 4G, but only says that 2.94G is "usable". So aggravating......now I have to figure out why my Asus P5B is being such a piece of $hit.
EDIT: Nice....thanks to some related posts on Tomshardware.com, I think I just found my answer. Which bugs me since I sent the original 2X1G back to Amazon thinking one of my DIMM slots was bad, and reordered a single 2G. Whatever, I'll just be happy if it works. What's funny is I thought about trying the setting in the BIOS, but the BIOS notes don't recommend enabling it......thanks a lot ya clowns
Yet another EDIT: The idiot reading the BIOS was the problem.....it doesn't say anything about not recommending it. Who's the clown now? Anyway, enabling that did the trick and I now have 4G RAM recognized.
On another irritating sidenote, the whole point of doing this (using more memory), seems to be pointless now. My motherboard only displays 3G of RAM installed, eventhough there is 4G installed. Windows even sees the 4G, but only says that 2.94G is "usable". So aggravating......now I have to figure out why my Asus P5B is being such a piece of $hit.
EDIT: Nice....thanks to some related posts on Tomshardware.com, I think I just found my answer. Which bugs me since I sent the original 2X1G back to Amazon thinking one of my DIMM slots was bad, and reordered a single 2G. Whatever, I'll just be happy if it works. What's funny is I thought about trying the setting in the BIOS, but the BIOS notes don't recommend enabling it......thanks a lot ya clowns
Yet another EDIT: The idiot reading the BIOS was the problem.....it doesn't say anything about not recommending it. Who's the clown now? Anyway, enabling that did the trick and I now have 4G RAM recognized.