Which versio nto run on 64-bit windows?

I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

On 09/20/2016 2:42 AM, micky wrote:
I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

In some cases you do not have a choice, some 32 bit programs will not
run on a 64 bit CPU.

If both will run, except in a few places, I always run the version that
matches my CPU.

In article , NONONOmisc07
@bigfoot.com says...

I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

A 64-bit hardware system can run Windows, and apps, which are either 64-
bit or 32-bit. There is a great advantage in running 64-bit Windows: it
means you can use more than 4GB of memory (I have 20GB in one system),
keeping your machine running fast when heavily loaded. When you boot
from CD, what's on the CD will determine what's loaded - if the CD is
32-bit, then that's what's loaded and run. If the running version of
Windows is 32-bit, you can't load 64-bit applications.

It's a bit different with applications. Microsoft recommend that for
"most users" it's better to install the 32-bit version of Office, even
on a 64-bit Windows installation. See:
http://bit.ly/2cQ14kS

That's because you're more likely to run into compatibility issues with
add-ins, etc, than you are to benefit from the larger data-holding
capacity (you'd need to be using gynormous spreadsheets, for example, to
hit the limit in 32-bit Excel.)

However, some specialist applications are starting to drop the 32-bit
version. Corel Painter 16 had 32 and 64-bit versions; Painter 17 has
only a 64-bit version available.

So, I tend to install the 32-bit version of any application that is
likely to need to interwork with extensions or add-ins, but otherwise
I'll install the 64-bit versions (e.g. Webdrive, which is a networking
client).

Not sure I understand your comments about the HDD you're trying to fix.
If the hardware it'll be returning to is 32-bit,then everything should
be 32-bit or it won't run.

In summary: It's only on 64-bit hardware that you have a choice of
using 32-bit or 64-bit Windows, and the latter is overwhelmingly the
better choice. Applications on the 64-bit installation can be 64-bit or
32-bit as seems more convenient.

--

Phil, London

micky wrote:
I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

Generally speaking, disk drives and file systems, are independent
of 32 bit or 64 bit CPUs.

64-bit processors support 32-bit and 64-bit instructions. Where
it gets messy sometimes, is when software has plug-ins, the kernel
has hardware drivers. There may be matching requirements there,
or limitations on data structures that prevent mixing and matching
of everything.

Some of your boot media, simply isn't meant to run on everything.
Older media is expecting to boot in a legacy BIOS environment.
A newer machine in UEFI or UEFI with Secure Boot enabled, might
not work with such media. A UEFI BIOS with CSM (legacy BIOS) module
installed and enabled might work, to boot an older media.

On Windows, there is Winload.exe and Winload.efi and the latter
works with UEFI setups when loading the OS. Not all Windows media
has UEFI support. If you had a motherboard in UEFI mode with
no CSM, inserted your Win2K installer CD, it wouldn't boot.
Whereas some of the later Windows install media, has both
UEFI and legacy support.

*******

You missed a subtle detail on this page.

http://www.midiox.com/index.htm?http...toprestore.htm

The 2010 release is available in a 64-bit only version.

The 2014 release sports:

"New dual mode installer. Contains x64 and x86 versions."

and that would work on either a 32-bit or a 64-bit OS installation.
So in fact, the 2010 version isn't needed at all, because the
2014 supports both.

There are even softwares smart enough to:

contain 32 bit and 64 bit code inside the same EXE

program unpacks itself, and "elevates" itself to the
64-bit code version on demand.

Some of the Sysinternals programs do that, which I
think is pretty cool.

When one of the Sysinternals programs did that, I
captured the 64-bit code it unpacked and labeled
it as "toolname64.exe" for later. And I can run
the 64 bit version without the unpacking ceremony.
There was some reason for doing that at the time,
perhaps because the 64-bit version could handle
larger data structures in RAM. And I wanted to
guarantee it could only run the 64-bit code.

*******

You can fix your hard drive on either a 32-bit or
a 64-bit computer. They're designed to hide their
bit-ness, when working with disks. The developers
make sure it "just works".

Paul

On 20/09/2016 11:26, Philip Herlihy wrote:
In article , NONONOmisc07
@bigfoot.com says...

I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

A 64-bit hardware system can run Windows, and apps, which are either 64-
bit or 32-bit. There is a great advantage in running 64-bit Windows: it
means you can use more than 4GB of memory (I have 20GB in one system),
keeping your machine running fast when heavily loaded. When you boot
from CD, what's on the CD will determine what's loaded - if the CD is
32-bit, then that's what's loaded and run. If the running version of
Windows is 32-bit, you can't load 64-bit applications.

It's a bit different with applications. Microsoft recommend that for
"most users" it's better to install the 32-bit version of Office, even
on a 64-bit Windows installation. See:
http://bit.ly/2cQ14kS

That's because you're more likely to run into compatibility issues with
add-ins, etc, than you are to benefit from the larger data-holding
capacity (you'd need to be using gynormous spreadsheets, for example, to
hit the limit in 32-bit Excel.)

However, some specialist applications are starting to drop the 32-bit
version. Corel Painter 16 had 32 and 64-bit versions; Painter 17 has
only a 64-bit version available.

So, I tend to install the 32-bit version of any application that is
likely to need to interwork with extensions or add-ins, but otherwise
I'll install the 64-bit versions (e.g. Webdrive, which is a networking
client).

Not sure I understand your comments about the HDD you're trying to fix.
If the hardware it'll be returning to is 32-bit,then everything should
be 32-bit or it won't run.

In summary: It's only on 64-bit hardware that you have a choice of
using 32-bit or 64-bit Windows, and the latter is overwhelmingly the
better choice. Applications on the 64-bit installation can be 64-bit or
32-bit as seems more convenient.


It's not usually relevant these days but 64 bit Windows doesn't run any
16 bit software (DOS programs or Windows 3.x programs) without help from
extra, not so convenient to use, third party software.

Although you can run 32 bit applications fine on 64 bit Windows all
drivers need to be 64 bit. This can be a restriction you need to be
aware of in a few cases.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

On Tue, 20 Sep 2016 06:04:10 -0400, Keith Nuttle
wrote:

On 09/20/2016 2:42 AM, micky wrote:
I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

In some cases you do not have a choice, some 32 bit programs will not
run on a 64 bit CPU.



That's true of *some* programs, but very few--mostly utilities and
games.

On 20/09/2016 11:04, Keith Nuttle wrote:
On 09/20/2016 2:42 AM, micky wrote:
I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

In some cases you do not have a choice, some 32 bit programs will not
run on a 64 bit CPU.

If both will run, except in a few places, I always run the version that
matches my CPU.

Some 32 bit programs that include components implemented as drivers will
not run on 64 bit Windows.

But a 64 bit CPU will run a 32 bit version of Windows which in turn will
run any 32 bit software.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

In alt.comp.os.windows-10, on Tue, 20 Sep 2016 09:08:48 -0400, Paul
wrote:

micky wrote:
I have a 64-bit version of win10 but It comes up often that programs are
offered in 32 and 64 bit

For example, Desktop Restore, that David Mullen recommended recently,
had unspecified and 64-bit versions and the 64 bit version was from
2010, 4 years older than the other. It seemed to me I'd be better off
with the 2014 version, but it wasn't 64 bit. If I didn't need 64-bit,
why was he still offering it when he had a version 4 years newer?

Also: I have 64-bit version of win10, but I'm trying to fix a HDD that
was made on a 32-bit computer. When the software has two versions, 32
and 64 bit, which am I supposed to use? Can I use both, that is,
either?

Finallly, I sometimes run Mini-XP, which boots from a CD and it must be
32 bits or it wouldn't have worked on my previous computers. Does t
hat mean I must run 32 bit programs even though the computer itself was
64-bit (which iiuc is how/why it accepted the 64 bit version of
windows.)

Thanks.

Thanks everyone. It's sinking in pretty well.

Paul, your're right that I missed that line, even though it was the line
just below the program name. Bad habit I have to get rid of. (Left
over maybe from my sojourn in law school, where after the case name
there were 3 or 4 lines of what books and what pages the case was
reported in. I used to waste time readilng and thinking about them,
and finally got in the habit of just skipping those lines.)

Something like this but even for a single case, which is reported in at
least two different volumes of Westlaw and iirc maybe the state's own
reporting volumes: (People v O'Hara, 96 NY2d 378, 385 [2001], quoting
Matter of Ferguson v McNab, 60 NY2d 598, 600 [1983]). " (O'Hara, 96 NY2d
at 385, quoting Matter of Gallagher v Dinkins, 41 AD2d 946, 947 [2d Dept
1973], affd 32 NY2d 839 [1973])

Thank you, your bitness.


Generally speaking, disk drives and file systems, are independent
of 32 bit or 64 bit CPUs.

64-bit processors support 32-bit and 64-bit instructions. Where
it gets messy sometimes, is when software has plug-ins, the kernel
has hardware drivers. There may be matching requirements there,
or limitations on data structures that prevent mixing and matching
of everything.

Some of your boot media, simply isn't meant to run on everything.
Older media is expecting to boot in a legacy BIOS environment.
A newer machine in UEFI or UEFI with Secure Boot enabled, might
not work with such media. A UEFI BIOS with CSM (legacy BIOS) module
installed and enabled might work, to boot an older media.

On Windows, there is Winload.exe and Winload.efi and the latter
works with UEFI setups when loading the OS. Not all Windows media
has UEFI support. If you had a motherboard in UEFI mode with
no CSM, inserted your Win2K installer CD, it wouldn't boot.
Whereas some of the later Windows install media, has both
UEFI and legacy support.

*******

You missed a subtle detail on this page.

http://www.midiox.com/index.htm?http...toprestore.htm

The 2010 release is available in a 64-bit only version.

The 2014 release sports:

"New dual mode installer. Contains x64 and x86 versions."

and that would work on either a 32-bit or a 64-bit OS installation.
So in fact, the 2010 version isn't needed at all, because the
2014 supports both.

There are even softwares smart enough to:

contain 32 bit and 64 bit code inside the same EXE

program unpacks itself, and "elevates" itself to the
64-bit code version on demand.

Some of the Sysinternals programs do that, which I
think is pretty cool.

When one of the Sysinternals programs did that, I
captured the 64-bit code it unpacked and labeled
it as "toolname64.exe" for later. And I can run
the 64 bit version without the unpacking ceremony.
There was some reason for doing that at the time,
perhaps because the 64-bit version could handle
larger data structures in RAM. And I wanted to
guarantee it could only run the 64-bit code.

*******

You can fix your hard drive on either a 32-bit or
a 64-bit computer. They're designed to hide their
bit-ness, when working with disks. The developers
make sure it "just works".

Paul