Are you sure? It seems to me it's reporting the CPU bitness, not the OS bitness. When I run your original test it still reports bitness as '0'.
I may be wrong but I don't believe it's safe to assume that CPU bitness == OS bitness.
| [reply] |
I don't believe it's safe to assume that CPU bitness == OS bitness.
You cannot run a 64-bit build of an OS on a 32-bit processor.
You can run a 32-bit build of an OS on an (intel) 64-bit processor, but that is done by running the CPU in 32-bit compatibility mode, when for all intents and purposes, it is a 32-bit processor. So, whilst it may be possible to distinguish between the two scenarios, there is little benefit in doing so as none of the 64-bit facilities would be available to you.
Leastwise, none that I can think of.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
So the module returns 32-bit for a 64-bit CPU running a 32-bit OS?
| [reply] |
Hi davido,
A couple of questions:
- What's your Sys::Info::Driver::Windows::OS and Sys::Info and perl versions?
- ActivePerl, Strawbery or your own build of perl?
- What's your Windows version (XP, Vista, 7, etc)?
- How did you install Sys::Info::Driver::Windows? (ppm, gcc, cl)?
Thanks,
Burak
| [reply] |
| [reply] [d/l] [select] |