> My 2c cents here: USB printers, scanners and other
> peripherals that plug into the wall or are battery-powered
> typically don't draw power from the USB port so are not affected by
> the 500mA limit.
Unfortunately, this is not true. The power that is drawn from the USB
connection has nothing t
My 2c cents here: USB printers, scanners and other peripherals that plug
into the wall or are battery-powered typically don't draw power from the
USB port so are not affected by the 500mA limit.
The 7-in-1 card reader may be marginal in its power requirement, and some
motherboards are less robust
Hi!
If you can't read the BSOD error message, you need to set your machine NOT
to reboot after crashing. Control
Panel-System-Advanced-Startup/Recovery-Settings. UNCHECK "Automatically
Restart" and hit OK a lot.
Les
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version
I have three devices plus a seven-and-one card reader, all connected to
onboard USB ports. My trackball, an Epson 1640 scanner and R2400
printer work fine but the card reader fails to se the Compact Flash card
when it's inserted and a reboot is required - much like my older
machine, running win 2K
That's and Idea. Thanks! I usually check for updates but I haven't
checked the Asus website for the new board.
Jim
Tony Sleep wrote:
>On 03/06/2006 James L. Sims wrote:
>
>
>>These are USB devices, Tony.
>>
>>
>
>Ah, OK. That is weird, then. I've used USB & USB2 a lot and not had any
>problems
On 03/06/2006 Laurie Solomon wrote:
> If you have connected the devices to an unpowered hub
Oh yes, what Laurie says, in spades. I sometimes forget there are such
things as unpowered hubs. They're more or less completely useless. A
single USB port is specced at 0.5amps, and a large proportion of U
On 03/06/2006 Tony Sleep wrote:
> Is the controller on the motherboard? If so, it might
> be worth looking for updated motherboard drivers, or trying a PCI
> card USB
> adaptor instead.
Sorry, too much hurry. I could have been clearer. I meant 'updated BIOS
and chipset drivers' for the mobo. Back
If you have connected the devices to an unpowered hub, this can create
problems - especially if you have several devices that have power
requirements connected to the same hub directly or daisy chained to it.
Furthermore, despite the claims, two many devices and/or hubs daisy
chained of the same US
On 03/06/2006 James L. Sims wrote:
> These are USB devices, Tony.
Ah, OK. That is weird, then. I've used USB & USB2 a lot and not had any
problems like that. Is the controller on the motherboard? If so, it might
be worth looking for updated motherboard drivers, or trying a PCI card USB
adaptor ins
These are USB devices, Tony. I was told by a so-called computer guru
that this problem was corrected in XP. It could be that the device is
incorrectly installed - it's a USB 2 device but its speed, or slowness,
indicated that Win XP thinks it an early USB device. I've tried
uninstalling the USB
http://www.sysinternals.com/utilities/bluescreen.html
I have no first had knowledge of this program, but I can vouch for
sysinternals.com in general. See if it capture your BSOD.
[EMAIL PROTECTED] wrote:
> Thanks for this. I downloaded the expanded scanners.inf file and used
> it to load the Ni
On 03/06/2006 [EMAIL PROTECTED] wrote:
> But even with the Nikon LS-8000
> loaded
> using this new file, Vuescan still crashes the system immediately upon
> starting. I wish the blue screen of death didn't pass so quickly so I
> could read what the issue was. Loading the KM 5400 II and my Epson
Thanks for this. I downloaded the expanded scanners.inf file and used
it to load the Nikon LS-8000. I read scanners.inf file in Notepad and
saw the LS-8000 listed so it looked promising.
The scanner, again, loads fine. But even with the Nikon LS-8000 loaded
using this new file, Vuescan still c
On 02/06/2006 James L. Sims wrote:
> I have a 32-bit device on a
> computer running Windows XP 32-bit that regularly fails to see one
> device unless it's activated and the computer restarted - much like
> the
> behavior that I experienced with Win 2K.
That's normal and correct behaviour for SCSI.
On 02/06/2006 [EMAIL PROTECTED] wrote:
> So, the technique works for the KM Scan Elite 5400 II, but doesn't
> work
> for the Nikon LS-8000. Maybe Ed could find a fix for that.
Ed's reply:-
On 03/06/2006 [EMAIL PROTECTED] wrote:
> Here's a more complete scanners.inf file. I thought the extra ent
15 matches
Mail list logo
