A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Instrument Flight Rules
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

KLN94 updates with Sandisk writer - unit-specific?



 
 
Thread Tools Display Modes
  #1  
Old January 29th 06, 03:02 PM posted to rec.aviation.ifr,rec.aviation.misc
external usenet poster
 
Posts: n/a
Default KLN94 updates with Sandisk writer - unit-specific?

wrote:

But is the compact flash card written with the Sandisk writer
similarly GPS unit specific? I cannot see how it could be. Is there
any way to write out a backup flash card for example (I have a spare
flash card from BK).


Yes, if I understand your question correctly, the card is BK-specific
because it has certain data (either topographical, man-made obstruction, or
both) on it that is placed there by BK, not by the process you will go
through every month when updating terminal data.

Also, the Sandisk reader requires special firmware for it to be able to
read and write BK data.

And finally, if you take the compact flash card out of the special-use
Sandisk reader and place it in another compact flash card reader, the OS
cannot access the card (as if it was not formatted).

--
Peter
  #2  
Old January 31st 06, 12:09 PM posted to rec.aviation.ifr,rec.aviation.misc
external usenet poster
 
Posts: n/a
Default KLN94 updates with Sandisk writer - unit-specific?

On Tue, 31 Jan 2006 09:38:12 +0000, Peter
wrote:


"Peter R." wrote:

And finally, if you take the compact flash card out of the special-use
Sandisk reader and place it in another compact flash card reader, the OS
cannot access the card (as if it was not formatted).


I wonder how that was achieved.

They are using standard retail CF cards; they must be relying on
retail packaged CF readers/writers to not be able to access certain
areas of the card. Somebody who can do a physical sector copy should
be able to duplicate one of these.


They also use special firmware for the SanDisk writer. It's
interesting that during the flash session, during the window that the
software is using the card, it can be explored with Windows Explorer,
but it becomes "device not ready" as soon as it closes the write.

Presuming the physical sector copy gets *everything*, including
however and wherever they've stored the card's serial number, it
should be feasible to have duplicates of the same card. Do the cards
themselves have unique identifying characteristics stored in a
non-writable area of the card? Serial number or anything?

What about the KMD550 card? That's a PCMCIA flash module made by
Intel.


Same deal, won't even open up in Windows. I believe that one uses a
special filesystem, but as they don't allow downloadable updates for
those devices I haven't futzd around with it enough to get past the
initial levels of "keep out" coding.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
UAV's and TFR's along the Mexico boarder John Doe Piloting 145 March 31st 06 06:58 PM
KLN94 updates with Sandisk writer - unit-specific? Peter Clark General Aviation 9 March 21st 06 06:58 PM
KLN94 updates with Sandisk writer - unit-specific? Peter Clark Instrument Flight Rules 9 March 21st 06 06:58 PM
KLN94 updates with Sandisk writer - unit-specific? Peter R. General Aviation 1 January 31st 06 12:09 PM
bush rules! Be Kind Military Aviation 53 February 14th 04 05:26 PM


All times are GMT +1. The time now is 01:06 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 AviationBanter.
The comments are property of their posters.