WIN 7 Major USB Hardware Incompatibilities ?
in [Hardware]
|
From: mike on 22 Feb 2010 19:36 Char Jackson wrote: > On Mon, 22 Feb 2010 14:02:06 -0800, mike <spamme0(a)go.com> wrote: > >> Nil wrote: >>> On 22 Feb 2010, mike <spamme0(a)go.com> 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. 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. > >> 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? 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. > > In short, you're flat out wrong about where the responsibility lies > here. >
From: John McGaw on 22 Feb 2010 20:01 On 2/22/2010 5:42 PM, Trimble Bracegirdle wrote: > 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.
From: Char Jackson on 22 Feb 2010 20:20 On Mon, 22 Feb 2010 16:36:32 -0800, mike <spamme0(a)go.com> wrote: >Char Jackson wrote: >> On Mon, 22 Feb 2010 14:02:06 -0800, mike <spamme0(a)go.com> wrote: >> >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.
From: Patrick Keenan on 22 Feb 2010 21:34 "Trimble Bracegirdle" <no-spam(a)never.spam> wrote in message news:hlq823$lil$1(a)news.eternal-september.org... > 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
From: Patrick Keenan on 22 Feb 2010 21:48
"mike" <spamme0(a)go.com> wrote in message news:hlv816$pli$1(a)news.eternal-september.org... > Char Jackson wrote: >> On Mon, 22 Feb 2010 14:02:06 -0800, mike <spamme0(a)go.com> wrote: >> >>> Nil wrote: >>>> On 22 Feb 2010, mike <spamme0(a)go.com> 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. |