couple stupid questions about 32bit vs 64bit platforms

  • Thread starter Thread starter David
  • Start date Start date
D

David

I recall back when first 64bit chip was released by AMD that is also
supported 32bit windows and 32bit applications via a 32bit mode of some
sort.... please correct me it I'm wrong on that...

my question is kind of the reverse of that... do 64bit operating systems
such as XP and Server 2003 64bit editions support 1) being installed on a
32bit processor?, and 2) running 32 bit programs?
 
David said:
I recall back when first 64bit chip was released by AMD that is also
supported 32bit windows and 32bit applications via a 32bit mode of some
sort.... please correct me it I'm wrong on that...

my question is kind of the reverse of that... do 64bit operating systems
such as XP and Server 2003 64bit editions support 1) being installed on a
32bit processor?, and 2) running 32 bit programs?

The 64-bit (x64 specifically) versions have to be installed on 64-bit
hardware, but do run most 32 programs without problems.

Carl
 
thanks

Carl Kaufmann said:
The 64-bit (x64 specifically) versions have to be installed on 64-bit
hardware, but do run most 32 programs without problems.

Carl
 
Is this the XP home or the Presario hardware? After about 1 hour it will
finally boot.

Is this COMPAQ PRESARIO S5100NX 2.6 Ghz; MB (Mother board) broken?
It stops at reboot with these 3 lines in the BIOS;

1. Award Medallion Biox v 6.0

2. REV 3.7

3. Intel Celeron 1600 Mhz
Memory Test 1040448K + 8192 K Shared Memory

It just hangs there. At the borron of the screen are 2 options; 1. Enter F1
for Setup. 2. Press Escape to skip Memory Test.

Hitting F1 and/or the Esc key has no effect. Nothing happens. Which MB test
would you run on the MB ? With a bootable FLoppy Disc or a Bootable CD ?

After about 1 hour it will finally boot.

Thanks @ Novice @ New Orleans
 
I have PC Doctor which runs tests on the MB and/or memory. Which should run
and what is usally the problem?
 
Hardware, Windows isn't even in the picture yet. You might try removing
some of the memory, and try again.
 
Back
Top