windows 64 bit

[gamerxx13]

What is the big advantage of having windows 64 bit compared to windows xp.

 

[Nothinman]

Right now? Bragging rights.

 

[kEnToNjErOmE]

None.

 

[KoolDrew]

As of right now I do not suggest using it because it is still in beta stages.

 

[kylef]

The biggest advantages will be for large database servers and high-end graphics workstations, where applications frequently need more than 3 gigabytes of virtual memory to cache data in RAM (for performance reasons).

Think along the lines of editing huge high-resolution uncompressed video feeds, or keeping a phone database of everyone in the US in memory.

For 95% of the population, 64-bit computing is currently unnecessary. The "killer 64-bit app" for the mainstream simply has not yet been identified.

 

[juspatrick]

Humm.....

I was under the impression that the one thing that the 64-bit would bring to everyone's door
would be a better door.

I read in one of my many weekly geek-mails that over half of XP's venerabilities regarding the
running of malicious code are due to buffer overruns, an inherent limitation of hardware the
32 bit code runs on ~ if the 64-bit edition will eliminate over half the known exploits ...?
I will happily give M$ and AMD my money.

and if I have this all wrong that's ok too...cept I'm out $500 for the SK8N and the 146 Opteron.

 

[kylef]

Originally posted by: juspatrick
I read in one of my many weekly geek-mails that over half of XP's venerabilities regarding the
running of malicious code are due to buffer overruns, an inherent limitation of hardware the
32 bit code runs on

It's not a 32-bit limitation. There are buffer overruns in 64-bit code too, and they are just as likely to occur using 64-bit processors.

The only difference is that newer 64-bit processors, such as the AMD64 series, have implemented an "NX" (no execute) flag for each page in memory. This allows the processor, with OS cooperation, to monitor system thread stacks, among other things, to prevent buffer overruns from easily hijacking your system.

It is important to emphasize that these NX features do NOT eliminate buffer overrun attacks! It is still quite possible to control and/or influence application behavior by overflowing buffers, and it is even possible given the right circumstances to execute arbitrary code despite the NX protection. It just makes such attacks much more difficult to achieve.

 

[bsobel]

It is important to emphasize that these NX features do NOT eliminate buffer overrun attacks! It is still quite possible to control and/or influence application behavior by overflowing buffers, and it is even possible given the right circumstances to execute arbitrary code despite the NX protection. It just makes such attacks much more difficult to achieve.

And there is nothing about the 64 bit environment that is special to the NX flag, you'll see it move into 32 bit CPU's too (Intel does have a P4 with EDB support now)

Bill

 

[juspatrick]

so much for the writers at Ziff Davis but more likely my misinterpretation.

maybe I could get some help with this:

I have downloaded the M$ XP 64-bit ISO twice.
Both copies produce the same stop errors.
Stop c00000135 error : Setup cannot copy the file : basesrv.dll

If I skip the file and continue installation, below is the list of
files that also cannot be copied.
basesvr.dll
makecab.exe
mmc.exe
qcap.dll
rsmui.exe
rsopprov.exe
tapiP.chm
wiadefui.dll
wiashext.dll
MSIMTF.DLL
wwmadmod.dll
wwnetmgr.dll

Trying all I could think of including different methods of burring to disk...all produced the same results.

So I installed standard XP 32 bit on one hard drive ~ completed
and rebooted several times ~ this installation is fine.

I next began installation of the 64-bit on the second hard drive.
I allowed it to copy all of the files, skipping the ones above that produced
errors and then allowed the installation to reboot the system.
The system continued the install and I got the BSOD.

I reset the system ~ this time I selected XP 32 bit from the duel boot menu.

I went in and copied these files above from the CD to the system32 folder
on the drive where I was installing XP 64-bit ~
I copied them in both forms i.e. BASESVER.DL_ & BASESVR.DLL
(copied and extension completed)
I rebooted and allowed the 64 bit installation to continue via the duel boot
menu.
It did.
I did not get the Stop c00000135 error : Setup cannot copy the file : basesrv.dll

The error message was "now" that it could find basesvr.dll but that it was
a "corrupt image"

Any Ideas?

 

[kylef]

Where are you getting the ISO from? My initial guess is a bad ISO, or a bad copy. There should be a way to validate the image using some checksum or hash.

 

[juspatrick]

Got it direct from M$
http://www.microsoft.com/windo...valuation/upgrade.mspx

The problem is solved, however there are 3 variables so I cannot attest to the solution.

1. I redownload the ISO for the third time using I.E. rather than my download manager
(which has never returned a corrput download)

2. I opend a brand new pack of disks instead of pulling from the 10 remaining on the spindle.

3. Microsoft may have corrected the files within the ISO, which is my contention as only
some of the images within the image were corrupt.

Now for a new question:
It has installed and it running, rather well from what I can tell so far except
there is no "Automatic Update" service listed in the services of the management consol.
It will not update ... not that updating is crutial as this is only a test, but a test is a test.
I would think that it should be there and running if for no other reason but to be tested.

 

[gflores]

So, if Windows XP64 isn't coming out until late 2005 (IIRC), then Longhorn will be out less than half a year later. Shouldn't they be developing a 64bit version of Longhorn, as well?

 

[Nothinman]

Shouldn't they be developing a 64bit version of Longhorn, as well?

What makes you think they're not?

 

[biostud]

aren't the NX flag activated in SP2?

 

[kylef]

Originally posted by: biostud666
aren't the NX flag activated in SP2?

Yes, which confused me at first because it actually requires an entire new level for page tables, and I couldn't see Microsoft making such a drastic change to the kernel for 32-bit X86. (They have to do it already for 64-bit addressing modes, so it's a no-brainer there.)

But it turns out that the old x86 "PAE" addressing mode similarly requires an extra level of page table lookup, so they have the extra bits necessary to add the NX flag. So, it is my current understanding that when Windows XP Professional in SP2 runs AMD64 processors, it runs them using 32-bit PAE mode so that it can use this NX bit.

 

[imported_michaelpatrick33]

I remember reading somewhere that they are going to release a 64bit Longhorn version.

Remember, the 64bit in of itself will not offer a great boost in daily operation. I mean how fast can Excel get. Encoding and encryption is where 64bit may well shine. I have seen some 64bit encoding betas that show massive performance boosts in 64bit.

I think another big boost will come when the extra 8 GPR's are utilized in 64bit Longmode that are currently sitting useless (they are not utilized in 32bit even in the 64bit OS) (along with all the other 64bit goodness [at least on the MS side of OS land])

 

[Nothinman]

Encoding and encryption is where 64bit may well shine. I have seen some 64bit encoding betas that show massive performance boosts in 64bit.

And that performance boost is probably more due to the extra cache and available registers on the AMD64 processor than with the fact that the app is 64-bit.

I think another big boost will come when the extra 8 GPR's are utilized in 64bit Longmode that are currently sitting useless (they are not utilized in 32bit even in the 64bit OS) (along with all the other 64bit goodness [at least on the MS side of OS land])

If they're sitting there useless you shouldn't have bought that CPU just yet. Linux runs on AMD64 with probably over 90% of the apps in a distribution running well in 64-bit mode, even once XP64 is released you'll have to wait quite some time before drivers and apps are ported.

 

[KJI]

Originally posted by: gflores
So, if Windows XP64 isn't coming out until late 2005 (IIRC), then Longhorn will be out less than half a year later. Shouldn't they be developing a 64bit version of Longhorn, as well?

I know for a fact they are. I know one of the beta testers who has their hands on a beta of it already.