> >         You don't. For example many storage devices use the
> "mass storage" driver,
> > most modern OS's have the driver and therefore you don't need to install
> > anything. Devices can also be "HID" which also don't require
> new drivers.
>
> But I still have to load a -driver- for each and EVERY device.
> With Firewire there is ONE driver and each app ties to it
> as needed (and as expected).


        A prof of mine once said: you NEVER get something for nothing. The "one
driver" approach of firewire means all the hardware needs to be a certain
complexity, USB was developed to be cheap if you don't need the speed.

> And every MP3 player I've tried in the last month requires
> that it's OWN driver be loaded. None seem to support the generic
> 'storage' device type (e.g. Yepp, IRiver, WaveX, Rio...).
> It's been a royal PITA, especially since the Yepp install
> nuked my USB connectivity and it took many many hours to purge the
> registry after the uninstall royally messed up.
> It will be a cold day in hades before Samsung gets another
> dollar out of me.

        You have to blame the RIAA for that. It's their insistence on "protecting"
their IP that results in stupid and hacked implementations like what you're
seeing.

> > > And if one has used a few dozen different devices over time,
> > > one is stuck with ALL those drivers being loaded by Winblows,
> > > even if the device is now in the dumpster.
> >
> >         Any device worse a dollar has drivers with an uninstall
> feature, you get
> > what you pay for.
>
> The Yepp wasn't cheap, and it came from a supposedly reputable
> company. It went back untested.

        Blame the RIAA for forcing the companies to come up with "secure" ways of
doing things, ways that go beyond the spirit of the technologies used.

> > > And of course USB works every time, and is EASY to implement
> > > on embedded processors like the PIC (NOT!).
> >
> >         And firewire is? I don't think there is a PIC with
> firewire, there is a PIC
> > with USB.
>
> I don't know of many PIC applications that need the 400mbs pipe
> firewire gives, but it looks to be LOT easier to code for.

        And that's my point. With firewire you either have all or nothing, you
CAN'T do firewire cheap and slow. Why? It was NEVER meant for that, USB is.

> > USB-serial devices out there it's just a matter of time before
> working with
> > USB is easier then with the legacy ports.
>
> PLEASE point me in the right direction. I have just been told

        Reread what I said.

> >         I used to be like you, I think you should give USB a
> try again, today's
> > devices and drivers are approaching flawless. TTYL
>
> It looks like I'm not going to have a choice. By amazing coincidence
> my boss has ordered that we "MUST HAVE" USB on our stimulator
> for the clinical trials phase. I now get to dig through the
> archives to find Novembers "PIC USB" thread and try to 'make it go'...
>
> Any idea where to get those 'micro USB' PCB connectors,
> suitable drivers/chips, PIC code and my life back?

        After the tone and way you have treated my opinion I hope you don't expect
help from me, but for the record: you won't be receiving any.

----------------------------------
Herbert's PIC Stuff:
http://repatch.dyndns.org:8383/pic_stuff/

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body