"Paul in Houston TX" <Paul@Houston.Texas> wrote
| Can windows 64 "read" 16 bit data? -run -running -convert
|
| Google Duck does not know.
|
| How about 8 bit?
Win64 can't run 16-bit executables. Reading data
is not limited. For example, a PNG file is 32-bit data.
A B/W BMP file is one-bit data. Data is data. The
context and/or file format determine how you read it.
With executables it's different. The file format is
different. Win64 can run a 32-bit executable because
it uses a go-between to translate, for the sake of
backward compatibility. If you look up PE format
(portable executable) you'll see it's very complex.
Different types will be different. A 32-bit EXE will be
dealing with 32-bit pointers and the format of the
file itself will be 32-bit.
For example, if you have a DLL and something wants
to use a function, it will walk 32-bit pointers in the
file header. X points to offset Y. Y points to offset Z.
Eventually it finds the function name and gets a pointer
to that offset. Then it runs the function by execuuting the
code at that offset in the DLL. A 64-bit DLL will be
similar, but based on 64-bit values. So it's gibberish for
32-bit software.
I don't understand what "-run -running -convert" means
but maybe I answered the question?
I copy / pasted my Google question and
included the boolean minuses so that Google would not return anything
related to run, running, and convert. It still works even though Google says that boolean term no longer works. It still works with Ducky.
Paul in Houston TX wrote:
I copy / pasted my Google question and included the boolean minuses so that Google would not return anything related to run, running, and convert. It still works even though Google says that boolean term no longer works. It still works with Ducky.
minus still works (and I think they say so) but plus no longer works, it returns results without the required term.
Newyana2 wrote:It still works with Ducky.
"Paul in Houston TX" <Paul@Houston.Texas> wrote
| Can windows 64 "read" 16 bit data? -run -running -convert
|
| Google Duck does not know.
|
| How about 8 bit?
   Win64 can't run 16-bit executables. Reading data
is not limited. For example, a PNG file is 32-bit data.
A B/W BMP file is one-bit data. Data is data. The
context and/or file format determine how you read it.
  With executables it's different. The file format is
different. Win64 can run a 32-bit executable because
it uses a go-between to translate, for the sake of
backward compatibility. If you look up PE format
(portable executable) you'll see it's very complex.
Different types will be different. A 32-bit EXE will be
dealing with 32-bit pointers and the format of the
file itself will be 32-bit.
  For example, if you have a DLL and something wants
to use a function, it will walk 32-bit pointers in the
file header. X points to offset Y. Y points to offset Z.
Eventually it finds the function name and gets a pointer
to that offset. Then it runs the function by execuuting the
code at that offset in the DLL. A 64-bit DLL will be
similar, but based on 64-bit values. So it's gibberish for
32-bit software.
  I don't understand what "-run -running -convert" means
but maybe I answered the question?
Thank you, Newyana.
Sorry for the confusion. I copy / pasted my Google question and included the boolean minuses so that Google would not return anything related to run, running, and convert. It still works even though Google says that boolean term no longer works.Â
On Win10 (and Win8, Win7, Vista)
x64 OS = run 64bit and 32bit programs
x86 OS = run 32bit and 16bit programs
The compatibility analysis, and telemetry, helps the staff
keep all that crap tipped upright.
Does using double quotes
smurf "father"
still work, to make "father" a mandatory term ?
Can windows 64 "read" 16 bit data? -run -running -convert
Google Duck does not know.
How about 8 bit?
On Win10 (and Win8, Win7, Vista)
x64 OS = run 64bit and 32bit programs
x86 OS = run 32bit and 16bit programs
I don't know whether + is completely meaningless now, or it just means something difference from "mandatory".
"Paul in Houston TX" <Paul@Houston.Texas> wrote
| Can windows 64 "read" 16 bit data? -run -running -convert
|
| Google Duck does not know.
|
| How about 8 bit?
Win64 can't run 16-bit executables. Reading data
is not limited. For example, a PNG file is 32-bit data.
A B/W BMP file is one-bit data. Data is data. The
context and/or file format determine how you read it.
On 24/09/2023 17:36, Newyana2 wrote:
"Paul in Houston TX" <Paul@Houston.Texas> wrote
| Can windows 64 "read" 16 bit data? -run -running -convert
|
| Google Duck does not know.
|
| How about 8 bit?
   Win64 can't run 16-bit executables. Reading data
is not limited. For example, a PNG file is 32-bit data.
A B/W BMP file is one-bit data. Data is data. The
context and/or file format determine how you read it.
It's worth noting that a lot of old programs have 16-bit installers even though the programs themselves are 32-bit - so would run on a 64-bit
system but you can't install them by conventional means.
You can sometimes get round that by copying the .exe and .dll files from
a working 32-bit system, and then patching the registry entries.
On 25/09/2023 17:34, Roger Mills wrote:
On 24/09/2023 17:36, Newyana2 wrote:
"Paul in Houston TX" <Paul@Houston.Texas> wrote
| Can windows 64 "read" 16 bit data? -run -running -convert
|
| Google Duck does not know.
|
| How about 8 bit?
   Win64 can't run 16-bit executables. Reading data
is not limited. For example, a PNG file is 32-bit data.
A B/W BMP file is one-bit data. Data is data. The
context and/or file format determine how you read it.
It's worth noting that a lot of old programs have 16-bit installers
even though the programs themselves are 32-bit - so would run on a
64-bit system but you can't install them by conventional means.
You can sometimes get round that by copying the .exe and .dll files
from a working 32-bit system, and then patching the registry entries.
If anyone reading this thread is interested in running 16 bit programs
on a modern PC search for Otvdm which uses Wine. It lets me run a couple
of ancient favourites (I think from Win 3.1 days) seamlessly on 64 bit Windows 11.
MikeS wrote:
On 25/09/2023 17:34, Roger Mills wrote:
On 24/09/2023 17:36, Newyana2 wrote:
"Paul in Houston TX" <Paul@Houston.Texas> wrote
| Can windows 64 "read" 16 bit data? -run -running -convert
|
| Google Duck does not know.
|
| How about 8 bit?
   Win64 can't run 16-bit executables. Reading data
is not limited. For example, a PNG file is 32-bit data.
A B/W BMP file is one-bit data. Data is data. The
context and/or file format determine how you read it.
It's worth noting that a lot of old programs have 16-bit installers
even though the programs themselves are 32-bit - so would run on a
64-bit system but you can't install them by conventional means.
You can sometimes get round that by copying the .exe and .dll files
from a working 32-bit system, and then patching the registry entries.
If anyone reading this thread is interested in running 16 bit programs
on a modern PC search for Otvdm which uses Wine. It lets me run a
couple of ancient favourites (I think from Win 3.1 days) seamlessly on
64 bit Windows 11.
How interesting! Thank you.
I will check it out and let the group know if it works.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:43:12 |
Calls: | 6,666 |
Calls today: | 4 |
Files: | 12,212 |
Messages: | 5,335,396 |