From: SC Tom on

"Trimble Bracegirdle" <no-spam(a)never.spam> wrote in message
news:hlqdf1$di7$1(a)news.eternal-september.org...
> Yes .
> Very few Manufacturers of hardware are saying Win 7 Compat or not.
> All most none in the case of Devices more than a year or 2 out of
> production.
> (\__/)
> (='.'=)
> (")_(") mouse
>

When you ran the WUA, was all this hardware on and running? Did you get any
warnings about some of your hardware or software?
A few more particulars would be helpful, such as PC type/manufacturer, CPU,
RAM installed, etc. Are you using on-board USB ports, or are you hooking all
this stuff through an external box? If so, is it self-powered, or externally
powered?
So far, I haven't run into anything that I couldn't get to work with Win7,
USB or not, and some of my stuff is pretty old in computer years. Guess I've
been lucky. I have to use Vista drivers on my all-in-one printer, but it
works fine.
One suggestion was to hook your modem up with UTP instead of USB if it's
capable. I wholeheartedly agree with that, even if it means getting a $20
internal NIC. My speeds are much better with a more consistent connection
and fewer download errors.
--
SC Tom

From: Conor on
In article <hlq823$lil$1(a)news.eternal-september.org>, Trimble
Bracegirdle says...

> 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 ... a USB DIGITAL TV Box ...A USB SCANNER ...a USB
> GRAPHIC TABLET ..
>
Have you actually bothered going to the manufacturers website and seeing
if there are Vista or Win7 drivers for them?


--
Conor

I'm not prejudiced. I hate everybody equally.
From: Maurice Batey on
On Sun, 21 Feb 2010 07:52:32 -0500, SC Tom wrote:

> So far, I haven't run into anything that I couldn't get to work with Win7,
> USB or not,

Running W7 'Home Premium' (i.e. one of the 'crippled' versions), I
find that the Boot-US bootloader installer cannot write to diskette -
even when I run it as Administrator: "Access denied".

No problem formatting the diskette, Wordpad had no problem writing
a test file to it, and I had no problem then deleting it - even
running as ordinary user.

Guess the Boot-US code is trying to do something dodgy...

Found nothing relevant in a search on sysinternals.com.
--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)

From: SC Tom on


"Maurice Batey" <maurice(a)nomail.afraid.org> wrote in message
news:pan.2010.02.21.17.06.11.431304(a)nomail.afraid.org...
> On Sun, 21 Feb 2010 07:52:32 -0500, SC Tom wrote:
>
>> So far, I haven't run into anything that I couldn't get to work with
>> Win7,
>> USB or not,
>
> Running W7 'Home Premium' (i.e. one of the 'crippled' versions),

Why do you consider it "crippled"?
--
SC Tom


> I find that the Boot-US bootloader installer cannot write to diskette -
> even when I run it as Administrator: "Access denied".
>
> No problem formatting the diskette, Wordpad had no problem writing
> a test file to it, and I had no problem then deleting it - even
> running as ordinary user.
>
> Guess the Boot-US code is trying to do something dodgy...
>
> Found nothing relevant in a search on sysinternals.com.
> --
> /\/\aurice
> (Replace "nomail.afraid" by "bcs" to reply by email)
>
From: Nil on
On 20 Feb 2010, "Trimble Bracegirdle" <no-spam(a)never.spam> wrote in
alt.windows7.general:

> 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 ... a USB DIGITAL TV Box ...A USB SCANNER ...a
> USB GRAPHIC TABLET ..

Scanners are always the first things to be abandoned by driver writers
if it doesn't work now, I doubt it ever will. Especially for a 64-bit
OS - I think separate drivers are needed, I believe.

The hardware manufacturers are responsible for drivers, not Microsoft.
I wouldn't call it a a hardware incompatibility, not a "Win 7"
incompatibility.

> I tried Vista out (& did not like it) some time ago, same machine,
> & these Devices were all OK.

But was it 64-bit Vista? If not, I bet these devices wouldn't have
worked there, either.

A quick web search finds quite a few suggested remedies for similar
problems - installing the drivers as Administrator, updating the
motherboard chipset driver and/or BIOS, etc. So, there may be a
workaround.