PCI\VEN_1180&DEV_0843&SUBSYS_022A1028&REV_12\4&B216F0A&0&09A4: Ricoh SD/MMC Host Controller

Since I am using both packs I also posted this here:
http://forum.driverpacks.net/viewtopic. … 590#p27590

Thanks

EDIT: The Host adapter DID install:

PCI\VEN_1180&DEV_0822&SUBSYS_022A1028&REV_22\4&B216F0A&0&08A4: Ricoh SD Bus Host Adapter

kingskawn wrote:

Do you have something for ricoh cardreaders?

RICOH SD/MMC driver
RICOH SmartMedia/XD driver
RICOH Memory Stick driver

The 7z folder isn't accessible anymore

http://forum.driverpacks.net/viewtopic.php?id=3070

Thanks

Do you have something for ricoh cardreaders?

RICOH SD/MMC driver
RICOH SmartMedia/XD driver
RICOH Memory Stick driver

The 7z folder isn't accessible anymore

http://forum.driverpacks.net/viewtopic.php?id=3070

RICOH SD/MMC driver
RICOH SmartMedia/XD driver
RICOH Memory Stick driver

The 7z folder isn't accessible anymore

As you already included some fingerprint drivers, please also integrate the fingerprint driver for device
USB\Vid_08ff&Pid_2580&Rev_0623
since it's very common in IBM Thinkpads/Lenovo, HP Pavillon, etc laptops.

Download (whole pack):
http://www-307.ibm.com/pc/support/site. … MIGR-67845

Download (drivers only):
http://rapidshare.com/files/119383550/L … e.rar.html

i think the mod should close the topic out when finalizing - this would force new posts for requests...

I would not pop a warning shot in the kneecap when they do 'tag a request after final', but I will ask that the topic gets a post when it was put in the sticky. (which is like finalising a pack in third party.) so that the user knows he should start a new topic for a REQ.. (and not tag ..)

When you develop a third party pack, please make our lives easy, and update the supported device list in the changelog.txt.
Some of the 3rd party DriverPacks have been so succesful that I recently  started thinking about requesting that a few of these become main DriverPacks. *
You probably have no idea how the changelogs for those are done, and how much time they take to update.. So it may be better we have 3rd party the way they are.

BUT, a txt about what is in the pack is useful.

( * I started thinking that because we see the need for some "exceptions" in a few drivers here, which means an INI, and 3rd party packs have no INI.)

We have no structured REQuest handling here, and yet I see people check into DriverPacks 3rd party for things they was interested in, and when something moves, they remind us of an old "request".

My bookmark to DriverPacks is simple, I let it look at all new posts for the last 24 hours.
http://forum.driverpacks.net/search.php?action=show_24h

I occasionally look at topics with NO reply.
http://forum.driverpacks.net/search.php … unanswered

The only thing this cannot see is edits to existing posts.
[which is why I once got on a soap box and raved about edits. Edits force a guy to re-read the entire topic, and we all know it can get seriously out of sequence when (par example) one reads some older posts on old modem 3rd party pack where everybody tagged along their own requests long after the pack had been released.]

Anyway, we have some cool people here, and I figure that errors come out anyhow.
Sooner or later, but they always do.

Thanks for the work you put in this.
You helped us help them.

(hehe, I edited. My Flemishness has always had me use unconventional grammar.)

new o2micro smartcard driver v3.0.1.5 released