Actually, I did decide not to do this after sending the other message. Often changing settings like this can make windows unstable which I would rather avoid, smile. Until there is a fix, I will simply send files to the unit from my work computer. ----- Original Message ----- From: "Walt Smith" <walt@xxxxxxxxxx> To: <bookport@xxxxxxxxxxxxx> Sent: Thursday, October 07, 2004 7:20 AM Subject: [bookport] Re: Feeling a bit sheepish > Don't do this. If you do and you connect a USB 2.0 device, it won't work. As > I said yesterday, 2.0 is backward-compatible with 1.1, so when set up for > 2.0, both USB formats will function, but not vice-versa. > > ----- Original Message ----- > From: "Mike Arrigo" <n0oxy@xxxxxxxxxxx> > To: <bookport@xxxxxxxxxxxxx> > Sent: Wednesday, October 06, 2004 9:05 PM > Subject: [bookport] Re: Feeling a bit sheepish > > > You know there is a setting in my bios that controls USB, of course, it's > currently set for 2.0. However, there is a 1.1 setting also, I wonder if > changing that would make a difference. The computer that the book port does > work on at work is using 1.1 I think. I'll have to try changing that setting > that I have a bit of sighted help, since that does not talk. > ----- Original Message ----- > From: "ROB MEREDITH" <rmeredith@xxxxxxx> > To: <bookport@xxxxxxxxxxxxx> > Sent: Wednesday, October 06, 2004 7:35 AM > Subject: [bookport] Re: Feeling a bit sheepish > > > > The Book Port is a USB 1.1 device. This is very interesting! > > > > >>> jerry.neufeld@xxxxxxxxxx 10/05/04 10:28PM >>> > > Playing with hardware for as long as I have, I should have guessed, I = > > should > > have known. Cables. About cables. Well, some just break, some perform > > intermittently, others are inappropriate. Recently, I have joined the = > > group > > of users of BookPort whose computers no longer recognize the device as of > > the most recent version of the firmware. Only one of my six pc's saw the > > BookPort as it should. As it turned out, that one machine had its own u s > = > > b > > cable, I having used another for the remaining five, a cable that has = > > worked > > flawlessly since I bought it. Well, it don't perform no good no more, or, > = > > at > > least, not with the BookPort. When I moved to another cable, this one said > > to be appropriate for u s b2 devices, all computers saw the b p without > > trouble. I must apologize to the a p h people for having added to their > > headaches. I always change my cables, just in the wholly improbable event > > that they are the cause of a problem. > > > > Although I assume the BookPort to be a u s b1 device, the x p operating > > system does not identify them as such with my computers, all equipped with > > the new, faster u s b2 ports. Does anyone at a p h or on this list know if > > the u s b 1 versus 2 can be at issue here? The cable that has proved = > > faulty > > became so only as of implementation of the newest firmware, a tad > > coincidental in my view. Tomorrow, I will check the integrity of my > > seemingly faulty cable with a known u s b1 device working from a u s b1 > > port. > > > > Again, my apologies for having added to the headaches. > > > > Regards to everyone, > > > > Jerry > > > > > > > > > > >