WIN 7 Major USB Hardware Incompatibilities ?

[Char Jackson]

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.

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

Who forced you to change your Operating System? If all of your devices
worked with XP, why not stay with XP?

In short, you're flat out wrong about where the responsibility lies
here.

 

[Trimble Bracegirdle]

I'm finding some suggestions that having more than 4 Gig RAM in
a Windows 7 64Bit install leads to greater problems.

Hardware uses addresses at the top of memory
with 64bit & greater than 4Gig RAM those addresses can be off what the
device driver can cope with.
(\__/)
(='.'=)
(")_(") mouse ( You could install Win 95 1st Issue in 40 MB's)

 

[Nil]

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.

Is it? How do you know that? Did the hardware manufacturer tell you
that? It's their code, so I guess they would know. (hint: the drivers
were not written by Microsoft.)

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

I agree with you there. It's a game the software and hardware
manufacturers play with each other. That's how they stay in business.
But there's a solution: don't upgrade anything. I stuck with Windows
2000 until 2006, because it worked fine for me. I only upgraded to XP
when I wanted to run a program that required it, so I built a new
computer from the ground up, researching all the hardware to make sure
everything was compatible. And it still works.

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

Oh, darn, my engine crank doesn't work with my 2001 Prius. Call the
Attorney General!

Oh, dear, the engine from my '75 Cadillac won't fit in my Kia Rio!
Curse you, Henry Ford!

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.

Here's where your analogy falls apart: there are alternatives. Go buy a
Mac (but I bet you'll have similar problems there) or get onea them
free OSs that only supports about 10 different hardware devices, or...
just stay with what you have that already works. You don't have to jump
on the moving Microsoft train, you know.

You must be a recent Windows user, because EVERY Microsoft OS upgrade
has left some hardware in the dust. If this is the first time you ever
noticed it, you're lucky.

 

[mikeyhsd]

why should MS care.
they did not sell you the scanner.

and epson does not care since they already have your money.



--

(e-mail address removed)

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-

 

[mike]

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.


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


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


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


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.
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.

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.

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...which obsoletes their old hardware...which
forces users to buy new peripherals to go with their new OS.

They get you coming and going.

Who forced you to change your Operating System? If all of your devices
worked with XP, why not stay with XP?

Microsoft forced me to update the OS because the tools they provided
to software vendors made it expensive to support older operating
systems...So there's new software that REQUIRES the new OS. Ditto
for new hardware.

They get you coming and going.

 

[John McGaw]

I'm finding some suggestions that having more than 4 Gig RAM in
a Windows 7 64Bit install leads to greater problems.

Hardware uses addresses at the top of memory
with 64bit& greater than 4Gig RAM those addresses can be off what the
device driver can cope with.
(\__/)
(='.'=)
(")_(") mouse ( You could install Win 95 1st Issue in 40 MB's)

The amount of memory should not be a problem as long as there is enough.
Having 4gB+ is a good thing. A driver is either compatible with the OS or
it isn't. If it is then it will handle as much memory as the OS supports
and having less memory is not going to make the incompatible magically
compatible. I've not found any USB hardware with incompatible drivers on my
W7-64bit beyond my old HP ScanJet. But given that the hardware is about ten
years old that is probably to be expected.

 

[milt]

You're welcome to your bend-over-and-take-it attitude.

No, that is a realistic attitude. MS doesn't write drivers. If anyone is
beinding you over, its the hardware makers that want people to buy new
hardware every couple of years because its the only way they make money,
so they refuse to write drivers for the new OSes that are on all the new
machines.

If XP could run my hardware device, there's no reason that W7 can't.
The code is already written. It works just fine.

But Windows 7 isn't Windows XP. So why would that work? Oh, you must be
one of those people that actually believes the people that say Windows 7
is Vista Service Pack 3.

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 never made the driver in the first place, so how how could they
have caused something to quit working? It was intentional, and its also
NOT their fault that hardware they DO NOT MAKE does not work with THEIR
software. You should be bitching at the hardware vendors, NOT MS!

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

Why, so you can whine, cry and complain about something esle? Wait, 9
gig? No install of Windows takes 9 gigs!

Oh wait, I think I get it now, you're just an anti-MS troll.

Yes, I'm sure there are all kinds of excuses. I don't want excuses.

No, you want to whine and cry like a little bitch.

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

Once again, blame the hardware makers, THEY are the ones that cause the
"throw everything away and start over" you are bitching about. Here is
another idea, keep the old OS that works with your old hardware, NO ONE
is forcing you to upgrade your version of Windows!

Dear valued customer,

*snips argument that has a terrible analogy* Get a clue.

 

[Char Jackson]

Microsoft provides tools, processes, techniques, interfaces that
vendors use to write drivers.
When microsoft arbitrarily CHANGES these base processes, the drivers fail.
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.

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.

OK, you've made your desires known. They don't match the reality of
the situation, though, so I suspect you're going to continue to be
disappointed. My best advice is to stop changing your OS just because
a new one comes along. The existence of a new OS doesn't make your old
OS suddenly stop working.

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...which obsoletes their old hardware...which
forces users to buy new peripherals to go with their new OS.

Sorry, I'm not buying what you're selling. Wouldn't you have to look
long and hard to find a peripheral that only works with Win7 and not
with XP, for example? Again I ask, how are you being forced to upgrade
your OS? Just stay with what you had.

 

[Gene E. Bloch]

I found one for my 1650 Scanner that works great.

So look here: (this is one very long URL)

http://<infinitely long> snipped

Have you heard of TinyURL.com?

Look into it, it's useful. There are other similar sites too.

I love them.

 

[Gene E. Bloch]

On 2/22/2010 4:02 PM, mike wrote:

Why, so you can whine, cry and complain about something esle? Wait, 9 gig? No
install of Windows takes 9 gigs!

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.

 

[Patrick Keenan]

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

 

[Patrick Keenan]

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.

 

[Patrick Keenan]

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

 

[Patrick Keenan]

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

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

 

[Tinkerer]

I found one for my 1650 Scanner that works great.

So look here: (this is one very long URL)

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

 

[Gordon]

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

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

 

[Gordon]

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.

 

[Maurice Batey]

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!

 

[kony]

I found one for my 1650 Scanner that works great.

So look here: (this is one very long URL)

http://www.kvaz.com/index.php?q=epson+perfection+1260+vista+x64
+driver.rar&search2=Search+files!&stype=all&S1=%3Ca+target%3D%22_blank%
22+href%3D%22http%3A%2F%2Fwww.kvaz.com%22%
3EThe+best+Rapidshare+Search+Engine+for+epson+perfection+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%2Bvista%2Bx64%
2Bdriver.rar.html]epson+perfection+1650+vista+x64+driver.rar[%2Furl]
&forum=%3Ca+href%3D%27http%3A%2F%2Fwww.kvaz.com%2Ffile_epson%
2Bperfection%2B1650%2Bvista%2Bx64%2Bdriver.rar.html%27+title%3D%
27epson+perfection+1650+vista+x64+driver.rar%27%3Eepson+perfection+1650
+vista+x64+driver.rar%3C%2Fa%3E&forum=http%3A%2F%2Fwww.kvaz.com%
2Ffile_epson%2Bperfection%2B1650%2Bvista%2Bx64%2Bdriver.rar.html

lol

Longest link ever?

 

[kony]

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.