On 3/4/2010 10:00 AM, Greg Stark wrote:
> On Thu, Mar 4, 2010 at 2:14 PM, Justin Graf<justin@magwerks.com> wrote:
>
>> To pretty much anyone outside MS, a sane human would think 64 bit apps
>> in SysWoW64 and 32Bit apps in System32. :'(
>>
>>
> Ah, but you all are forgetting that the "32" here is to distinguish it
> from the default odbc interface which as i recall was a *16* bit
> interface. I'm not sure what exactly that means but as a result the
> 32-bit odbc configuration is entirely separate from the "regular" odbc
> configuration. It's not the instruction set that the dll uses it's
> which set of shared data structures it uses and which api it provides
>
ON the Way back machine we had System and System32. System32 came
about in Windows 3.1 if memory serves to separate where 16 and 32 bit
are placed. This time MS around is not doing that System32 is being
used for 64bit apps and SysWoW64 is where all the legacy 32 bits at
getting stuck.
32 bit apps in a directory with 64 in its name, and 64 bit apps in
directory thats intention was/is 32bit apps =-O
All legitimate Magwerks Corporation quotations are sent in a .PDF file attachment with a unique ID number generated by
ourproprietary quotation system. Quotations received via any other form of communication will not be honored.
CONFIDENTIALITY NOTICE: This e-mail, including attachments, may contain legally privileged, confidential or other
informationproprietary to Magwerks Corporation and is intended solely for the use of the individual to whom it
addresses.If the reader of this e-mail is not the intended recipient or authorized agent, the reader is hereby notified
thatany unauthorized viewing, dissemination, distribution or copying of this e-mail is strictly prohibited. If you have
receivedthis e-mail in error, please notify the sender by replying to this message and destroy all occurrences of this
e-mailimmediately.
Thank you.