If you were the system builder, how can you ensure the compatibility and
provide the support? Let you know how the items were purchased. The friend
bought a computer together with Microsoft Windows XP x64 Edition on day 1.
Then the friend bought the multi-function printer on day 2. The Bluetooth-USB
adapter was tested with the x64 windows on day 3.
It is a fact the the OEM license is purchased from a local computer shop.
It is understood that there is no downgrade path from x64 to 32-bit. I
request for a creation of the path..
There are many printers and bluetooth adapters available in the market, few
of them support 64-bit windows. Supporting 64-bit windows is not the only
criteria in considering a product. Taking printer into consideration, I would
calculate the cost of ink, laser toner. I know that HP provides 64-bit
drivers, but the ink of HP printers is very expensive comparing with other
products in the market. The bluetooth adapter supports bluetooth headset, it
requires Windows XP. It works fine in 32-bit XP, never in 64-bit XP.
It is intuitive to regard the x64 edition as a member of the "Microsoft
Windows XP" series. I do not observe the requirements of the peripherals
distinguishing between 32-bit edition and 64-bit edition. Who know that they
are incompatible in some sense?
It is a serious problem of "Microsoft Windows XP x64 Professional Edition"
including the brand "Microsoft Windows XP", because the x64 edition is not
compatible with other members of the Microsoft Windows XP family.
Don't put your customer's trouble as a mean to encourage the hardware
manufacturer to support 64-bit windows.
Jeremy Wong
"Charlie Russel - MVP" wrote:
> 1.) Read the license. There IS NO retail product for x64. The OEM product is
> NOT a retail product, it is tied to the hardware. It is forever linked to
> the hardware it was bought with. It is the responsibility of the system
> builder (in this case the person who assembled it) to ensure compatibility
> and provide support for it.
> 2.) There is no downgrade path. None. You may, of course, buy a 32-bit
> license and install it, either OEM or Retail. If it's OEM, it's tied to the
> computer it's bought for/with. If it's retail, it is not, you may remove it
> from one machine and install it on another.
> 3.) There are perfectly good bluetooth adapters and printers that work fine
> with x64 Edition. I know, because I'm running both here. Again, it is the
> responsibility of the OEM to ensure compatibility.
>
> --
> Charlie.
> http://msmvps.com/xperts64
>
> Jeremy Wong ??? wrote:
> > It is a self-assemble computer. The OEM license was obtained when I
> > purchased the hardware in a computer shopping centre. It is a common
> > practice to have the OEM license in this way.
> >
> > That means that there is no other hardware manufacturer. The end-user
> > obtained the OEM license in a shop. The product I bought is "Microsoft
> > Windows XP", having the brand name "Microsoft". I would say that it is an
> > improper use of the brand "Microsoft Windows XP" as it misleaded me, at
> > least, that the "Microsoft Windows XP x64 Professional Edition" is
> > compatible with other products sold under the brand name of "Microsoft
> > Windows XP".
> >
> > Sorry that I do not want to argue whatever license it is. I only want to
> > have the problem solved. A consumer paid for a product, but the product
> > did not work as expected. Why should the consumer pay for the product?
> >
> > It is reasonable to downgrade from x64 to its 32-bit counterpart as we pay
> > for each license. We are not using any pirate copy...
> >
> > It is irresponsible to sacrifice the end-user as a mean to "encourage" the
> > hardware manufacturers producing 64-bit drivers. I urge you to provide
> > free courses for porting drivers to 64-bit Windows, especially to those
> > hardware manufacturers owning a large market segment. Another mean is to
> > have Intel and AMD announcing not to ship 32-bit CPU any more. The
> > hardware manufactuers may then start to consider a support of the 64-bit
> > windows.
> >
> >
> > Jeremy Wong
> >
> > "NoNoBadDog!" wrote:
> >
> >>
> >> "Jeremy Wong ???" <> wrote in message
> >> news:E9D676CF-B0D7-4D16-BDBD-...
> >>> My friend has a x64 OEM license of Microsoft Windows XP for her new
> >>> computer.
> >>> However, it is found that the product is not compatible with many
> >>> computer peripherals in the market. For example, it does not work with a
> >>> USB-Bluetooth
> >>> adapter (OMIZ OMB509) and a multi-function printer (Canon MF5650). I can
> >>> foresee that there are more peripherals x64 is incompatible with.
> >>>
> >>> I hope to download the x64 OEM license to its 32-bit counterpart.
> >>>
> >>> However, there is no mechanism of the downgrade process. From the view
> >>> of a
> >>> consumer, it is misleading to purchase "Microsoft Windows XP x64" as a
> >>> member
> >>> of the "Microsoft Windows XP" series.
> >>
> >> There are two problems with your scenario;
> >>
> >> Your friend has an OEM license, not one from Microsoft. If there is to
> >> be any "downgrade", it will come from the manufacturer and not Microsoft.
> >>
> >> Your issue is with the hardware manufacturer, not with Microsoft. Let
> >> Canon and the others know that will no longer buy their products. Let
> >> them know how dissatisfied you are with their lack of support for a
> >> shipping OS.
> >>
> >> Downgrading would only encourage the OEMs to not produce drivers for
> >> WinXP Pro x64.
> >>
> >> Bobby
>
>
>