Win7 x64 build7100 ends up as Win7 x32 build7000

[pjd1952]

I've had no luck with this in Installation & Setup so I thought I'd try here.

I'm running an Abit I45-c MB (all documentation tells me it is 64-bit capable) with an Intel Pentium D 945 3.2GHz CPU (again 64-bit capable), with 4GB of Ram and during boot my Bios reports an "EM64T CPU".

I have downloaded the 64-bit Win7 RC image "7100.0.090421-1700_x64fre_client_en-us_retail_ultimate-grc1culxfrer_en_dvd.iso" twice and burned both versions to DVD. Both give the same results: Install reports that it is installing Build7000. After a successful install I end up with Build7000 (ver. 6.1) at 32-bit. How is that possible? My last attempt included the second downloaded image and partion destruction, partition recreation, and format, all to no avail.

Paul D.

 

[mxosder16]

Did you get it via MS or torrents?

 

[mxosder16]

Oh, and a way to find out if it's 64 bit capable is to go to:
Start -> right click on computer -> left click properties -> left click on your windows experience index -> left click on view and print detailed preformance and system information (under your wei number) -> and you can see it here:




Nobody laugh and my wei, thats not the point

 

[pjd1952]

Absolutely downloaded from MS, wouldn't try it any other way.

As for 64-bit capability, I will have to boot up Win 7 and check it, XP-Pro does not give me that info.

But regardless, if my machine was not capable I would expect an error or the inability to run the OS. How could the install program know and then adjust itself and install "Build7000 x32"? The install files have different names and different sizes.

 

[pjd1952]

Interestingly I can't run the Windows Experience Index successfully. I mean it seems like it runs...it runs through the whole process and posts "Assessment Complete" but immediately pops up another dialogue box stating that the Assessment cannot complete due to a problem with some driver. It figures. So, I cannot get Win7 to tell me whether my machine is 64-bit capable. That begs the question though of how running the Build7100 x64 install ends up installing Build7000 x32.

 

[Avien]

You could download cpuz and look under the instructions section on the first window. If it is 64bit it will say x86-64.

 

[mxosder16]

CPUZ link

 

[bobtran]

What is the size of your download. My x64 from Microsoft is 3,194,168 KB and earlier today I downloaded x86 on a friends pc which came in at approx 2.6+ gb (I think it was, but know for sure it was less than 3gb). The name you give is the one I have for x64. Check the following:

cntl-panel/Performance Info & Tools/Advanced tools/view advanced system details in system Information.

Find "Version" Mine shows 6.1.7100 Build 7100
Find "System Type" Mine shows x64-based PC

By the way Build 7000 is the "Beta 1" version not the RC

I downloaded from here: Windows 7 Release Candidate

 

[mxosder16]

a few screens probably wouldn't hurt either

http://www.sevenforums.com/general-...ed-method-uploading-posting-screen-shots.html

 

[pjd1952]

Okay, as I suspected, I downloaded the x32 RC from the MS site and I end up with Build7100 32-bit. I ran the WEI (haven't figured out out to paste it in here but I tadded it as an attachment) and it tells me my computer is 64-bit capable.

So, here's the mystery, why when I boot up to the "7100.0.090421-1700_x64fre_client_en-us_retail_ultimate-grc1culxfrer_en_dvd" DVD does the install screen tell me that it is installing Build7000? I've downloaded the image twice and used three different DVD burns. Is the image at the site misnamed?

 

[Avien]

Not sure what to say. If it is from here; http://www.microsoft.com/windows/windows-7/download.aspx

And you select 64bit, everything should work fine. Just install it and see.

 

[pjd1952]

I am currently burning a freshly downloaded x64 image to DVD from within Win7 Build7100 x32 from that site (which is where I have always gotten my installs). I'll see if there's any difference.

 

[mxosder16]

FYI this is a much faster way of installing if you want

 

[copernicus]

It's possible you're accidentally renaming the file when you download it by clicking on the erroneous file by overwriting.

 

[pjd1952]

That could happen although I don't want to believe it . Anyway, I finally resolved the issue. I downloaded the x64 image from within Win7 Build7100 x32 and burned the image with "ISO Burner".

Having said that, one of the reasons I decided to play around with the 64-bit version was that I had upgraded from 2 to 4 GB of memory and understood that 32-bit systems could not see beyond about 3.25GB. So what do I get? Well, I ran the Windows Experience Index and it only reports 3.25GB of Ram. When I look at the System info via START/RC Computer/Properties I see nothing reported under "Installed Memory". Oh well, I didn't have anything to do this weekend anyway. So now that I finally got x64 installed I will proceed to find out what's up with the memory usage.

Thanks for the help everyone.

 

[Avien]

Sometimes your BIOS also limits what your OS sees. My BIOS only recognizes i have more then 4gb by an extended memory mapping and my motherboard is only 2 months old.

Glad you got it to work though.

 

[pjd1952]

Just checked for a memory mapping option on my I-45CV Abit board and there is no such option. The MB spec states it can utilize 4GB (2-2GB sticks) and the BIOS counts up the full 4GB.

 

[Cyberwolf]

Does your graphics card share physical memory? As in, doesnt have dedicated onboard memory?

 

[pjd1952]

ATI Radeon PCIe X1300 with 256MB of onboard memory.

 

[zigzag3143]

pid1952
You 32bit? 32 and recognize 4gig but must use a portion of that to map (PAE) and if you video car uses shares the highest I have seen is 3317K. Mine looks like this
Ken