32 bit vs 64 bit Comparison

[jerrypc1]

Thanks lordbob I have 64 bit but I didn't know what the differences were until now. Jerry

 

[Lordbob75]

I dont think 64bit requires atleast 2GB ram as i ran 64bit Windows 7 on a laptop with 1GB :sarc:

It will run, but the minimum requirement is listed as 2Gb RAM.
Source: Windows 7 system requirements - Microsoft Windows

Thanks Lordbob

You're welcome.

Thanks lordbob I have 64 bit but I didn't know what the differences were until now. Jerry

No problem. The guide needed to be written. No idea why it hadn't been yet...

~Lordbob

 

[iphone]

I dont think 64bit requires atleast 2GB ram as i ran 64bit Windows 7 on a laptop with 1GB :sarc:

It will run, but the minimum requirement is listed as 2Gb RAM.
Source: Windows 7 system requirements - Microsoft Windows

Oh! thanks for clearing that

 

[Lordbob75]

I dont think 64bit requires atleast 2GB ram as i ran 64bit Windows 7 on a laptop with 1GB :sarc:

It will run, but the minimum requirement is listed as 2Gb RAM.
Source: Windows 7 system requirements - Microsoft Windows

Oh! thanks for clearing that

Welcome.

~Lordbob

 

[luckylukevn]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

 

[kucing13]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

I don't think so. And mind telling me how do you know certain virus 32 or 64. Just Asking . Thanks

 

[zzz2496]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

That depends on the virus, if the virus is compiled directly to a binary format that is not compatible with WoW, it won't infect Win64. If it does compatible, and can link to a 64bit compiled library, it can infect Win64.

If the virus is created by an intermediary language (.net/java), if the perquisite requirement is there, it can infect Win64.

Then again, there's a lot going on in the "infecting" stage, we can't really know for sure until we looked at the memory stack in action...

zzz2496

 

[luckylukevn]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

That depends on the virus, if the virus is compiled directly to a binary format that is not compatible with WoW, it won't infect Win64. If it does compatible, and can link to a 64bit compiled library, it can infect Win64.

If the virus is created by an intermediary language (.net/java), if the perquisite requirement is there, it can infect Win64.

Then again, there's a lot going on in the "infecting" stage, we can't really know for sure until we looked at the memory stack in action...

zzz2496

Thanks!

 

[Lordbob75]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

Interesting question actually. Not something I ever thought about before.

In general, I would expect hackers to write universal code as much as possible.

~Lordbob

 

[zzz2496]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

Interesting question actually. Not something I ever thought about before.

In general, I would expect hackers to write universal code as much as possible.

~Lordbob

There is a "universal" code, that is by using intermediary runtime, like .net/java. But the downside of that road is the program will rely on that intermediary runtime, and the intermediary runtime MUST HAVE ACCESS to the core OS's functions to do it's harm.

An alternative would be to modify the kernel and segment the binaries, making one binary contains 2 completely different datastreams. This method was used by Apple's Mac OS X in the transition between PPC and x86, one binary package contains two datastreams, one for PPC, another for x86.

The last alternative, this will need you to modify the kernel and set the flag in the binary manually so that when it runs, it will invoke the processor's x86 legacy mode, and run it accordingly, but this has many downsides, too complex to explain...

zzz2496

 

[Lordbob75]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

Interesting question actually. Not something I ever thought about before.

In general, I would expect hackers to write universal code as much as possible.

~Lordbob

There is a "universal" code, that is by using intermediary runtime, like .net/java. But the downside of that road is the program will rely on that intermediary runtime, and the intermediary runtime MUST HAVE ACCESS to the core OS's functions to do it's harm.

An alternative would be to modify the kernel and segment the binaries, making one binary contains 2 completely different datastreams. This method was used by Apple's Mac OS X in the transition between PPC and x86, one binary package contains two datastreams, one for PPC, another for x86.

The last alternative, this will need you to modify the kernel and set the flag in the binary manually so that when it runs, it will invoke the processor's x86 legacy mode, and run it accordingly, but this has many downsides, too complex to explain...

zzz2496

Thanks for the explanation. I am not sure how they would do it, I just figured they would want it to work on as many systems as possible.

~Lordbob

 

[luckylukevn]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

I don't think so. And mind telling me how do you know certain virus 32 or 64. Just Asking . Thanks

it's shown in virus's name e.g Win32.Kido, Win32/Pacex. Win32/Conficker

 

[kucing13]

does 64bit OS mean it cannot be infected by virus because virus is 32 bit ?

I don't think so. And mind telling me how do you know certain virus 32 or 64. Just Asking . Thanks

it's shown in virus's name e.g Win32.Kido, Win32/Pacex. Win32/Conficker

silly me,I never thought of that. Thanks mate

 

[luckylukevn]

silly me,I never thought of that. Thanks mate

Don't be ashamed. We learn something new everyday. You're welcome.

 

[zzz2496]

Keep in mind, even if the description said Win32/xxx, it can still infect Win64 (the WoW subsystem). Unless you kill the WoW subsystem completely...

zzz2496

 

[pallesenw]

"-A 64bit OS can address up too 8Tb of RAM (128 in 64 bit Vista, and 192Gb in Seven)."

That is a mix of virtual and physical address space limitations. 8 TB is the current user/kernel space limitation. 128/192 is the physical limitation.

 

[Hoods]

Thanks, Bob - that's EXACTLY what I wanted to know and clearly and well explained! Kudos ++

This week I accidentally bought a 32-bit copy (!@#@!#%@!) to upgrade from Vista x64 and was considering installing it (because having it is burning a hole on my desk!) but after reading your article I think I'll estrain myself and trade it back for the 64-bit, even though there are no big specials (here) on it at the moment!

Cheers
Hoods

 

[Lordbob75]

Thanks, Bob - that's EXACTLY what I wanted to know and clearly and well explained! Kudos ++

This week I accidentally bought a 32-bit copy (!@#@!#%@!) to upgrade from Vista x64 and was considering installing it (because having it is burning a hole on my desk!) but after reading your article I think I'll estrain myself and trade it back for the 64-bit, even though there are no big specials (here) on it at the moment!

Cheers
Hoods

Your welcome.

If you bought the 32bit, the key is the same, you just need a x64 bit disk.

~Lordbob

 

[Hoods]

If you bought the 32bit, the key is the same, you just need a x64 bit disk.

Aaaaaaaaaargh - wish I'd known that a couple of hours ago when I bought 64 bit. LOL. No harm done, will give the 32-bit to my son.



Hoods

 

[Lordbob75]

If you bought the 32bit, the key is the same, you just need a x64 bit disk.

Aaaaaaaaaargh - wish I'd known that a couple of hours ago when I bought 64 bit. LOL. No harm done, will give the 32-bit to my son.



Hoods

Well, that works

~Lordbob