RE: cardreaderprob.
a.tammer at hetnet.nl wrote:
> Hi Rudy,
>
> I plan to use it for demonstration-purposes,
> with clients, for whom I'm designing webpages.
> It's smaller than a CDR, you can erase and
> re-record. I have a 256Mb-card (Sandisk) with
> it, so there's lots of space, for taking people's
> pictures, or their office's look, if they want that
> on their home-page.
>
> Problem is not in drive-letter-assignment. I can find
> no interrrupt-conflicts, none of the standard
> trouble-shooting techniques seems to do any good.
>
> I'm half-sleepy, while answering this, so maybe not
> everything makes sense. I do nevertheless send it
> and hope someone can come up with a solution.
>
> Hope you have the information you want.
>
> a@t, antoine
>
>
>
hmm. you want to take the 'reader' with you but feel it would also show
up as a 'drive' letter but different than what you programmed your
demonstration for?
did you believe it would show up in your memory address space?
and you want to try to access it directly now?
years ago, on an old s100 system (pre ibm pc) a company created a memory
card that would respond as a regular drive on the system.
it did not show up in regular memory 'space' , but in the i/o address
space. it used 2 port addresses (bi-directional ports) whose functions
were for :
input - 1 port for receiving data, 1 for the receiving a status
output - 1 port for sending data, 1 for sending commands
you would send a write command setting a destination address then send a
data to that address. to read any data you first sent an address command
to set an address followed by a read data command so that the data on
the data port was from that address.
maybe your interface is designed to be i/o using only a few bytes of
memory (memory mapped) instead of actual taking up system address space.
or using actual i/o port addresses.
without any product infront of me i can only guess what you are
experiencing.
later
rudy
rltoews at ilos.net
lotterywars
|
Not Categorized, Please Help
|
|
