Has anyone tried to use the microsoft fingerprint reader to password
applications in Pick/Jbase? Does anyone out there know how to read and
access the data from the reader?

Richard Kann


--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

Fingerprint verification for pet food! What is this world coming to?

(just kidding Richard)

"Rick Kann" <him (AT) comp-ware (DOT) net> wrote

I'm guessing that the fingerprint reader has a dotnet interface
mewhere. - a quick google search shows a variety of third party
interfaces.

It should be easy to call a visual basic.net/c# or c++ code from data-basic
in jBASE to do the fingerprint lookup and return a user no or something from
a database. jBase has the ability to call a microsoft dotnet function
within a dll from within databasic.

Hope this gives you the framework to which you can add some code.
Regards
Simon
"Rick Kann" <him (AT) comp-ware (DOT) net> wrote

Yup, sounds like it's just an exercise, no specific experience
required.

T

"Simon Verona" wrote:

Yep!

You will find that the Microsoft reader is a somewhat cutdown version
of the "real thing". One of our Visage VAR's wanted to use the device
to idenify operators for his touch screen POS application. We made some
changes to accomodate the requirements, but ultimately bumped into a
limitation of the microsoft software.

We researched the options, contacted the originators of the technology,
and determined that the only way we could do what we wanted was to get
the "real" fingerprint readers, which are tad more expensive.

Obviously depends on your requirements - the Microsoft retail product
may work for you. We are looking at using the "real" product now in a
number of applications - if anyone is looking for a 21st century,
tamper proof time & attendance system, or an interesting twist to a
secure-entry system (photo verification based on fingerprint), then we
may have an off the shelf the shelf solution for you ....or you can
roll your own with Visage :-)

Ross Ferris
Stamina Software Pty Ltd
Visage > Better by Design

And getting the dogs and cats to touch the pad isnt that easy either!

Jeffrey Kaufman wrote:

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

Anyone out there want to tackle this for a price?

Richard

Simon Verona wrote:


--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

Anyone ouyt there want to tackle this for a price?

If it has to use another reader that is fine, but if it caould use the
Microsoft one (that I already have) it would be better.

Richard Kann

Simon Verona wrote:


--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

Rick Kann wrote:
As to be expected, I was just about to bite, but I did a little
preliminary research and came up with some tough to find info:

1) There is no Microsoft-supported SDK for these devices.
2) There are third-party SDKs but they have one-time licenses plus
there are runtime licenses for deployment.
http://www.griaule.com/ and http://www.payoon.com/
3) According to the product spec sheet, the MS reader is dependent on
DigitalPersonal drivers. A for-fee SDK is available to integrate with
this software. See
http://www.digitalpersona.com/developers/
That page links to a long list of developer companies, any one of
which might already have something that precludes new development.
4) This technology is very fragile. As with many devices, any VAR who
deploys it needs to be careful about claims for exactly what you
support and how. For example, if the end-user changes their windows
password it might break their fingerprint apps. Same goes for damaged
readers or corrupted authentication databases. Who's at fault for
these things? How much time will you commit to supporting the device
in conjunction with your app? Of course your app will break if the
device and related drivers falter, but does your warranty really cover
outside influences like this? Are you prepared to tell the user to
just go and buy a new $50 device to save you and the end-user several
hours of costly diagnostic time?
5) According to the spec sheet, the Microsoft reader also "requires"
the "MSN Internet Explorer" in addition to IE6. That might only be
for browser use, but anyone deploying this technology should look into
that - I sure don't want any MSN crap on my system.

I'll be happy to do development for anyone who will OK the purchase of
an SDK and related runtime licenses, but I wouldn't accept
responsibility for any of the factors discussed above.

This information has been brought to you courtesy of the Research
Division of Nebula Research and Development.

HTH
TG@ removethisNebula-RnD.com

Rick,

Didn't we write some credit card software for you using Accuterm scripts?
They should work for this too.

These readers usually attach to a com port and give rs232 ascii strings when
activated. Sometimes with additional characters (stx, etx, eot, etc). They
can be accessed via Accuterm scripts or a VB phantom.

Mark Brown
Drexel Management Services, Inc.


"Rick Kann" <him (AT) comp-ware (DOT) net> wrote