WIN 7 Major USB Hardware Incompatibilities ?

"Trimble Bracegirdle" wrote in message
...
WINDOWS 7 Major USB Hardware Incompatibilities ?

I'm trying out Win 7 64 Bit. on the same Hardware (but separate Hard
Drive)
as my established Win XP .

A big issue for me & the main thing I'm testing is the ability to use my
existing Hardware.

The standard basic stuff....Hard Drives...DVD Drive ...USB Memory Sticks
...Graphics Card ...centronics port printer ...
is all OK.

BUT I have a number of USB Hardware devices that are fine under XP ...
THAT MUST FOR ME, WORK ! in Win 7 & won't

a USB ADSL MODEM ...

The fix for that one is easy if the modem has an ethernet port.

Stop using the USB port and connect your modem either directly to your PC
via ethernet cable, or into a router or switch, also via Ethernet.
Uninstall any USB drivers for the modem.

You'll likely find that you get better performance, lower overhead, and
greater reliability; and if you use a router, the NAT features will increase
your online protection.

As to the other devices, it's the manufacturer's responsibility to write
drivers, and not really reasonable to expect a 3rd party to do it for them.
Writing device drivers requires skill and access to hardware details that
only the manufacturer will have. It's an expensive task that often doesn't
produce any return for the manufacturer.

HTH
-pk

"mike" wrote in message
...
Char Jackson wrote:
On Mon, 22 Feb 2010 14:02:06 -0800, mike wrote:

Nil wrote:
On 22 Feb 2010, mike wrote in alt.windows7.general:

It's Microsoft's responsibility to make their new OS compatible
with the hardware I already have. I'm sure they have a lot of
excuses. I don't want excuses. I want my (*(*& hardware to
continue to work!!! It may not support new features, but it should
do at least what it used to do.
Period!!!
Sorry, but you're living in a fantasy world - that's not the way it
goes. Unless Microsoft makes an explicit claim that a certain piece of
hardware will work, out-of-the-box with Windows, then it's up to the
manufacturer to supply the device driver. That's the way it has ALWAYS
worked with EVERY version of Windows. That's probably the way it will
always work. Get used to it... and urge the hardware vendor to release
updated drivers. You're more liable to get results doing that than
complaining here or to Microsoft.

I just built myself this handy dandy digital butt-scratcher with a USB
interface. Do you suppose Windows 7 supports it?
You're welcome to your bend-over-and-take-it attitude.
If XP could run my hardware device, there's no reason that W7 can't.

If that were true, your devices would continue to run just as they
did. Since they don't, there must be a reason. The reason is that the
hardware driver is not compatible with the new OS. You have things
bass ackwards if you think the OS needs to be compatible with 3rd
party hardware. It's the responsibility of the 3rd party hardware
vendors to provide drivers that work with the OS, not the other way
around. You don't have to like it, but that's the way it is.

The code is already written. It works just fine.

If it worked fine, you wouldn't be here complaining.

M$ CHOSE to change things in a manner that caused a perfectly working
driver to quit working. I don't care WHY they did it. I want them
to continue to include the support they already had.

They do. Just continue to use the OS you were using.

My C: drive is 9gigabytes of M$ bloat. Another bit of bloat for legacy
support wouldn't have killed them.

No thanks, I don't want tens of thousands of unneeded drivers
cluttering up my system.

Yes, I'm sure there are all kinds of excuses. I don't want excuses.
I want those M$ geniuses to figger out how to make it work.
You can bet if it had been a priority, it would have happened.

You can also bet if it was Microsoft's responsibility it might have
happened, but the truth (whether you want to believe it or not) is
that hardware vendors are responsible for providing drivers for their
equipment. Period.

Microsoft provides tools, processes, techniques, interfaces that
vendors use to write drivers. When microsoft arbitrarily CHANGES these
base processes, the drivers fail.

Who says OS changes are arbitrary?

I'm not sure that the word means what you think it means.

If M$ did not change the processes, but supported them for legacy code,
drivers written by vendors for legacy products would continue to provide
whatever functionality they provided before the OS change.

Manufacturers get plenty of notice of OS changes, and choose to either
update their drivers or not. It's neither trivial or cheap to write
device drivers.

I get the impression that you've never worked with people who write such
code professionally.

It is MOST DEFINITELY a M$ responsibility to allow old drivers to continue
to work and coexist with drivers written using the new
tools/processes/techinques/interfaces provided with the new OS.

..... And you want the cost for this service passed on to you?

Additionally, M$ keeps changing the tools so that it is inconvenient or
expensive for writers of new drivers to support older operating systems
without a complete rewrite. This FORCES users to update the OS go get
drivers/support for NEW devices

So don't buy them. Make do with what you already have.

...which obsoletes their old hardware...which
forces users to buy new peripherals to go with their new OS.

They get you coming and going.

One might note that Apple does exactly the same thing.

In the real world, it is not reasonable to expect support for all legacy
devices.

"Al Smith" wrote in message
...
mike wrote:

It's Microsoft's responsibility to make their new OS compatible with the
hardware I already have. I'm sure they have a lot of excuses.
I don't want excuses. I want my (*(*& hardware to continue to work!!!
It may not support new features, but it should do at least what it used
to do.
Period!!!
Microsoft has let us down in that area. Sorry for any inconvenience,
my A$$.


Tell me about it. I've got a perfectly good Epson Perfection Photo 1260
flatbed scanner, and it won't run under Windows 7 x64. No driver for it.

Excuse me, Al, but taking a look at the Epson site, I don't see any mention
of Epson ever providing any 64-bit drivers for that product.

What I do see is a FAQ that clearly states that Epson wrote no 64-bit Vista
drivers, and that implies that there were no 64-bit XP drivers either.

So, the OS you previously ran this on was almost certainly 32-bit, not 64.
This isn't a trivial detail.

Epson does point to a 3rd party product (Hamrick VueScan) whose 64-bit
drivers *might* work, but Epson wasn't providing or supporting those
drivers.

And that 3rd party application was and is not free. It may, however, get
you the support you want, and there is a free trial, so here is the link for
it:
http://www.hamrick.com/vsm.html


Epson can't be bothered writing one,

Epson apparently couldn't be bothered to write a 64-bit version at any time
in the past, either, so this isn't really a change.

and Microsoft just doesn't care.

More properly, your Epson scanner is not an MS product and drivers for it
are not Microsoft's responsibility.

It can be surprising what isn't supported under 64-bit OS's.

I would have thought that ProTools, an industry-standard professional level
audio recording software would want the extended memory in a 64-bit system.
And I would have been wrong, because it didn't support or run on 64-bit
anything until very recently. It's still not officially supported, it's
only the latest releases, it's still 32-bit code and requires that the audio
interface have 64-bit drivers.

-pk


-Al-

"Frank" wrote in message ...
Al Smith wrote:
mike wrote:

It's Microsoft's responsibility to make their new OS compatible with the
hardware I already have. I'm sure they have a lot of excuses.
I don't want excuses. I want my (*(*& hardware to continue to work!!!
It may not support new features, but it should do at least what it used
to do.
Period!!!
Microsoft has let us down in that area. Sorry for any inconvenience,
my A$$.


Tell me about it. I've got a perfectly good Epson Perfection Photo 1260
flatbed scanner, and it won't run under Windows 7 x64. No driver for it.
Epson can't be bothered writing one, and Microsoft just doesn't care.

-Al-

Hummm...MS has nothing to do with Epson drivers.

And Epson didn't provide any 64-bit drivers in the past, either.

"Zaidy036" wrote in message
...
In article ,
says...

mike wrote:

It's Microsoft's responsibility to make their new OS compatible with
the
hardware I already have. I'm sure they have a lot of excuses.
I don't want excuses. I want my (*(*& hardware to continue to work!!!
It may not support new features, but it should do at least what it used
to do.
Period!!!
Microsoft has let us down in that area. Sorry for any inconvenience,
my A$$.


Tell me about it. I've got a perfectly good Epson Perfection Photo
1260 flatbed scanner, and it won't run under Windows 7 x64. No
driver for it. Epson can't be bothered writing one, and Microsoft
just doesn't care.

-Al-

I found one for my 1650 Scanner that works great.

So look he (this is one very long URL)


And here is the same URL made shorter
http://tinyurl.com/ydp43u9
--
Tinkerer

"Maurice Batey" wrote in message
news

Running W7 'Home Premium' (i.e. one of the 'crippled' versions),

There's only one "crippled" version and that's 7 Starter....

"mike" wrote in message
...

It's Microsoft's responsibility to make their new OS compatible with the
hardware I already have.

Sure. Like they can test it with MILLIONS of different appliances
peripherals and internal hardware.

What a STUPID statement.
That's the purpose of BETA and RC releases so the MANUFACTURER can test
their own products.
Complain to the manufacturer of your hardware if it doesn't work.

On Mon, 22 Feb 2010 22:17:59 -0500, Patrick Keenan wrote:

It can be surprising what isn't supported under 64-bit OS's.

I was amazed that this 64-bit W7 Home Premium not only had a
driver for my ancient HP5150 deskjet, but installed it on the fly!

--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

On Mon, 22 Feb 2010 16:05:28 -0500, Zaidy036
wrote:


I found one for my 1650 Scanner that works great.

So look he (this is one very long URL)

http://www.kvaz.com/index.php?q=epso...1260+vista+x64
+driver.rar&search2=Search+files!&stype=all&S1=%3 Ca+target%3D%22_blank%
22+href%3D%22http%3A%2F%2Fwww.kvaz.com%22%
3EThe+best+Rapidshare+Search+Engine+for+epson+per fection+1650+vista+x64
+driver.rar+-+over+12+488+551+links!%3C%2Fa%3E&forum=[url%3Dhttp%3A%2F%
2Fwww.kvaz.com%2Ffile_epson%2Bperfection%2B1650%2 Bvista%2Bx64%
2Bdriver.rar.html]epson+perfection+1650+vista+x64+driver.rar[%2Furl]
&forum=%3Ca+href%3D%27http%3A%2F%2Fwww.kvaz.com%2 Ffile_epson%
2Bperfection%2B1650%2Bvista%2Bx64%2Bdriver.rar.ht ml%27+title%3D%
27epson+perfection+1650+vista+x64+driver.rar%27%3 Eepson+perfection+1650
+vista+x64+driver.rar%3C%2Fa%3E&forum=http%3A%2F% 2Fwww.kvaz.com%
2Ffile_epson%2Bperfection%2B1650%2Bvista%2Bx64%2B driver.rar.html


lol

Longest link ever?

On Mon, 22 Feb 2010 14:02:06 -0800, mike
wrote:


This "throw away everything and start over" every few years has gotta
stop!!!



Why not just call the police so the person holding a gun to
your head, forcing you to use Win7 instead of XP, is hauled
away?

Remember, you're the one who chooses what OS to use, based
on its merits. I agree MS should take greater measures to
support backwards compatibility with drivers but we can't
expect it since they have a monopoly position in the PC OS
market.

"kony" wrote in message
...
On Mon, 22 Feb 2010 14:02:06 -0800, mike
wrote:


This "throw away everything and start over" every few years has gotta
stop!!!



Why not just call the police so the person holding a gun to
your head, forcing you to use Win7 instead of XP, is hauled
away?

Remember, you're the one who chooses what OS to use, based
on its merits. I agree MS should take greater measures to
support backwards compatibility with drivers but we can't
expect it since they have a monopoly position in the PC OS
market.

Instead of Microsoft being responsible for backwards compatibility with
outdated hardware, why shouldn't the hardware manufacturer be responsible
for providing updated drivers? It would certainly be cheaper in the long run
for each manufacturer to write new drivers than it would be for Microsoft to
insure it, but then, HP and the rest wouldn't be selling anything new if
their 20 year old printer has Windows 7 drivers. Are you willing to pay the
extra big bucks for Windows to be compatible with every piece of hardware
ever made? Can you even imagine what that cost would be? I can't. All I
could see would be "You can have the latest Windows version, Windows 2015,
for only $3,917 for the Home Starter Edition, with guaranteed backwards
compatibility through Windows3.11." Ain't gonna happen in our lifetimes :-)
--
SC Tom

This new update might be helpfull :

http://support.microsoft.com/KB/976264

On 2/22/2010 7:49 PM, Gene E. Bloch wrote:
On 2/22/10, milt posted:
Oh wait, I think I get it now, you're just an anti-MS troll.

Note that mike seems to be unable to type "MS" without using a dollar
sign. In my view, that totally corroborates your remark.


Yup, I noticed that as well, that was the obvious clue right there. As
if making money is a BAD thing!

"mike" wrote in message
...
Nil wrote:
On 22 Feb 2010, mike wrote in alt.windows7.general:

It's Microsoft's responsibility to make their new OS compatible
with the hardware I already have. I'm sure they have a lot of
excuses. I don't want excuses. I want my (*(*& hardware to
continue to work!!! It may not support new features, but it should
do at least what it used to do.
Period!!!

Sorry, but you're living in a fantasy world - that's not the way it goes.
Unless Microsoft makes an explicit claim that a certain piece of hardware
will work, out-of-the-box with Windows, then it's up to the manufacturer
to supply the device driver. That's the way it has ALWAYS worked with
EVERY version of Windows. That's probably the way it will always work.
Get used to it... and urge the hardware vendor to release updated
drivers. You're more liable to get results doing that than complaining
here or to Microsoft.

I just built myself this handy dandy digital butt-scratcher with a USB
interface. Do you suppose Windows 7 supports it?

You're welcome to your bend-over-and-take-it attitude.
If XP could run my hardware device, there's no reason that W7 can't.
The code is already written. It works just fine.
M$ CHOSE to change things in a manner that caused a perfectly working
driver to quit working. I don't care WHY they did it. I want them
to continue to include the support they already had.

My C: drive is 9gigabytes of M$ bloat. Another bit of bloat for legacy
support wouldn't have killed them.

Yes, I'm sure there are all kinds of excuses. I don't want excuses.
I want those M$ geniuses to figger out how to make it work.
You can bet if it had been a priority, it would have happened.

This "throw away everything and start over" every few years has gotta
stop!!!

Dear valued customer,
Toyoter motor company announces an exciting new line of motor vehicles
chock full of features you'll never use. In order to support these
exciting new features, we had to change some parameters.

Our new vehicles are no longer compatible with garages built prior
to 1998.

Some parking spaces no longer work. You'll find that out when you
reach your destination and try to park.

In order to use toll roads, you'll need to purchase the optional
toll upgrade that works...mostly...

Our vehicles are no longer permitted in school zones.

Standard gasoline from your corner filling station will still
work in compatibility mode with significantly reduced fuel mileage.

If you have any child car seats or personal electronic items that were
used in your car, you will need to replace them. Legacy snow tires are no
longer supported.
Any towable trailers will need to be replaced.

Our ULTIMATE upgrade is required for trips greater than 100 miles.

Please remember that Toyoter motor company is the ONLY option available
to you. We trust you will continue to buy our products...because
you have no other choice.

Sorry for any inconvenience.

Your analogy as a joke is actually the truth. We now have to use spark plugs
that are more refined and expensive, no longer use a single coil that you
can scavenge from one vehicle to another (most of the time), can't use that
extra carburetor sitting on the shelf, can't use a cheater bar to tighten
bolts down anymore--have to use a torque wrench. Can't check for spark by
holding a plug wire a short distance from spark plug, and on and on and on
and on. That's one of the reasons salvage yards get old vehicles, at some
point in time the manufacturers stop producing parts for them and the only
source is aftermarket, demand is so low that sources dry up, price goes way
up and finally no-one wants to fix it, they sell it for salvage. If you
think about this you can draw your own parallel to MS and hardware
manufacturers and drivers.
Sadly, you have to do the same with your old hardware. You can gently lay it
next to some of those old monochrome (green and amber) monitors, dot-matrix
printers and Intel 286 CPU motherboards. Or, if it makes you feel better,
you can mutilate it first in any manner you choose except water boarding it
as that's not PC. (Pun intended)
Dave

"SC Tom" wrote in message
...

"kony" wrote in message
...
On Mon, 22 Feb 2010 14:02:06 -0800, mike
wrote:


This "throw away everything and start over" every few years has gotta
stop!!!



Why not just call the police so the person holding a gun to
your head, forcing you to use Win7 instead of XP, is hauled
away?

Remember, you're the one who chooses what OS to use, based
on its merits. I agree MS should take greater measures to
support backwards compatibility with drivers but we can't
expect it since they have a monopoly position in the PC OS
market.

Instead of Microsoft being responsible for backwards compatibility with
outdated hardware, why shouldn't the hardware manufacturer be responsible
for providing updated drivers? It would certainly be cheaper in the long
run for each manufacturer to write new drivers than it would be for
Microsoft to insure it, but then, HP and the rest wouldn't be selling
anything new if their 20 year old printer has Windows 7 drivers. Are you
willing to pay the extra big bucks for Windows to be compatible with every
piece of hardware ever made? Can you even imagine what that cost would be?
I can't. All I could see would be "You can have the latest Windows
version, Windows 2015, for only $3,917 for the Home Starter Edition, with
guaranteed backwards compatibility through Windows3.11." Ain't gonna
happen in our lifetimes :-)
--
SC Tom


Epson has a Windows 7 driver for that scanner on their site. So, what's the
problem?