dll file?
in [64 Bits Windows]
|
Prev: Slow Startup & Shutdown...
Next: Explorateur Windows7
From: R. C. White on 23 Feb 2010 21:42 Hi, Charlie. The biggest such naming mistake, it seems to me, is the new "Program Files (x86)". Why couldn't they have created a "Program Files (x64)"? They could have left 32-bit apps in "Program Files" - in both 32-bit and 64-bit Windows. They could even have used BOTH "Program Files (x86)" and "Program Files (x64)". That would have made for longer 32-bit pathnames, but it would have been a lot less confusing - especially for us dual-booters who run both 32-bit and 64-bit Windows on a single computer. (I was glad to finally meet you at the Summit last week.) RC -- R. C. White, CPA San Marcos, TX rc(a)grandecom.net Microsoft Windows MVP Windows Live Mail 2009 (14.0.8089.0726) in Win7 Ultimate x64 "Charlie Russel - MVP" <Charlie(a)mvKILLALLSPAMMERSps.org> wrote in message news:ObcHnWLtKHA.5496(a)TK2MSFTNGP04.phx.gbl... > I'd have to agree with the OP, however, that "system32" as the home for > 64-bit system files is perhaps not particularly intuitive. ;) The > SYSWOW64 designation, however, makes perfect sense. And I know why they > left system32 alone, I just think they shouldn't have. > > -- > Charlie. > > > "Bobby Johnson" <rjohnson(a)discussions.microsoft.com> wrote in message > news:OxMub5KtKHA.6124(a)TK2MSFTNGP04.phx.gbl... >> Except when you know what it means. WOW is Windows on Windows. So >> SYSWOW64 it the interface between 32-bit and 64-bit on a 64-bit system. >> What's illogical about that? >> >> Wow32 since Win95 is the interface between 16-bit and 32-bit on a 32-bit >> system. >> >> >> On 2010-02-23 12:21, Ghod Dhammit wrote: >>> "Charlie Russel - MVP"<Charlie(a)mvKILLALLSPAMMERSps.org> wrote in >>> message >>> news:ezbpUEFtKHA.4796(a)TK2MSFTNGP02.phx.gbl... >>>> Open a command prompt As Administrator, and copy. Note: System32 folder >>>> in >>>> 64-bit Windows is ONLY for 64-bit files. 32-bit files go in the >>>> SYSWOW64 >>>> folder. >>> >>> Don't you just love how they name things? Logic just goes out the >>> windows......
From: Charlie Russel - MVP on 24 Feb 2010 01:14 Yes, I agree, this was an unfortunate choice. But it's too late now, so we live with it. Good to finally meet you too. This was my 9th Summit (they had a three year stretch with only two Summits.) -- Charlie. http://msmvps.com/blogs/russel "R. C. White" <rc(a)grandecom.net> wrote in message news:uvLDqrPtKHA.5976(a)TK2MSFTNGP05.phx.gbl... > Hi, Charlie. > > The biggest such naming mistake, it seems to me, is the new "Program Files > (x86)". Why couldn't they have created a "Program Files (x64)"? They > could have left 32-bit apps in "Program Files" - in both 32-bit and 64-bit > Windows. They could even have used BOTH "Program Files (x86)" and > "Program Files (x64)". That would have made for longer 32-bit pathnames, > but it would have been a lot less confusing - especially for us > dual-booters who run both 32-bit and 64-bit Windows on a single computer. > > (I was glad to finally meet you at the Summit last week.) > > RC > -- > R. C. White, CPA > San Marcos, TX > rc(a)grandecom.net > Microsoft Windows MVP > Windows Live Mail 2009 (14.0.8089.0726) in Win7 Ultimate x64 > > "Charlie Russel - MVP" <Charlie(a)mvKILLALLSPAMMERSps.org> wrote in message > news:ObcHnWLtKHA.5496(a)TK2MSFTNGP04.phx.gbl... >> I'd have to agree with the OP, however, that "system32" as the home for >> 64-bit system files is perhaps not particularly intuitive. ;) The >> SYSWOW64 designation, however, makes perfect sense. And I know why they >> left system32 alone, I just think they shouldn't have. >> >> -- >> Charlie. >> >> >> "Bobby Johnson" <rjohnson(a)discussions.microsoft.com> wrote in message >> news:OxMub5KtKHA.6124(a)TK2MSFTNGP04.phx.gbl... >>> Except when you know what it means. WOW is Windows on Windows. So >>> SYSWOW64 it the interface between 32-bit and 64-bit on a 64-bit system. >>> What's illogical about that? >>> >>> Wow32 since Win95 is the interface between 16-bit and 32-bit on a 32-bit >>> system. >>> >>> >>> On 2010-02-23 12:21, Ghod Dhammit wrote: >>>> "Charlie Russel - MVP"<Charlie(a)mvKILLALLSPAMMERSps.org> wrote in >>>> message >>>> news:ezbpUEFtKHA.4796(a)TK2MSFTNGP02.phx.gbl... >>>>> Open a command prompt As Administrator, and copy. Note: System32 >>>>> folder in >>>>> 64-bit Windows is ONLY for 64-bit files. 32-bit files go in the >>>>> SYSWOW64 >>>>> folder. >>>> >>>> Don't you just love how they name things? Logic just goes out the >>>> windows...... >
From: Ghod Dhammit on 24 Feb 2010 17:51
"Bobby Johnson" <rjohnson(a)discussions.microsoft.com> wrote in message news:OxMub5KtKHA.6124(a)TK2MSFTNGP04.phx.gbl... > Except when you know what it means. WOW is Windows on Windows. So > SYSWOW64 it the interface between 32-bit and 64-bit on a 64-bit system. > What's illogical about that? If you don't understand it, it'll be up to you to figure it out, sorry. > Wow32 since Win95 is the interface between 16-bit and 32-bit on a 32-bit > system. Except when you know what it means (snark). MS-DOS ran as a 16-bit compatibility layer, when the Win95 GUI was running. Heh. It was argued that Win95 wasn't a real OS, because it ran on top of MS-DOS. Not actually true, but none of the explanations I saw back then were good enough to show why. I'm glad it's much easier to learn the facts these days. > On 2010-02-23 12:21, Ghod Dhammit wrote: >> "Charlie Russel - MVP"<Charlie(a)mvKILLALLSPAMMERSps.org> wrote in message >> news:ezbpUEFtKHA.4796(a)TK2MSFTNGP02.phx.gbl... >>> Open a command prompt As Administrator, and copy. Note: System32 folder >>> in >>> 64-bit Windows is ONLY for 64-bit files. 32-bit files go in the SYSWOW64 >>> folder. >> >> Don't you just love how they name things? Logic just goes out the >> windows...... >> >> |