I can further expand on what is happening. For each 250 bytes (or less) of data I am trying to read using either GPKFileUtilityService or GPKFileSystemService I get back a nine character code similar to: [B@61d36b If the attempt was to be read 400 bytes the output might look like [B@61d36b[C@31d34d. It appears to be similar to the java object name that your get when doing toString() on an object. The data can be read fine using GPKPilot. The same results are happening when reading the default files on the card (such as :3F00:0200:0004). For this file (4000 bytes).. I get back 16 x 9 character codes. This is occuring when using the exact same file path as was used in the line above to create the file. I hope this helps clarify the problem I am having. Chris Kesik > >Any insights? > >I am writing a 20 byte file to the GPK8000 card using the OFC. When I read >it back I get a totally different set of bytes. One would think that I am >not writing the data correctly, but, looking in GPKPilot I see the correct >data in the file. Anyone seen this before? > >The code I am using is. > > bytes = "44444444445555555555".getBytes(); > fus.update(cf.getPath(), 0, bytes, 0, bytes.length); > > byte verify[] = fus.read(ef_BEEB, 0, bytes.length); > > > > --- > Visit the OpenCard web site at http://www.opencard.org/ for more > information on OpenCard---binaries, source code, documents. > This list is being archived at http://www.opencard.org/archive/opencard/ ! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email ! to ! [EMAIL PROTECTED] ! containing the word ! unsubscribe ! in the body.
