View Single Post
      06-12-2014, 01:22 AM   #63
Frogman
Lieutenant Colonel
United_States
288
Rep
1,892
Posts

Drives: 2012 F30 328i
Join Date: Mar 2012
Location: SoCal

iTrader: (0)

Quote:
Originally Posted by pikcachu View Post
that one looks like the binary version... do you have the actual .hex one?
For what we are talking about, hex = binary. This is what you get when you decode a base64 encoded file. The binary file is what the FSC.exe generator requires as input.

The SWID_reader writes a base64 encoded file, so that's why the FSC generator program needs to decode that file into binary before it can be used.

I created the good binary file from your bad base64 file by converting it from base64 to binary, and then patching it by changing the embedded spaces to NUL bytes.

When I compare my base64 encoded file to the base64 encoded file you supplied above, the files are different (as expected).

So, I think when you originally encoded your binary FSC code extracted from E-Sys into base64, something went wrong and it produced an incorrect base64 file. Then, when you decoded the base64 file back into binary, the decode did not produce the correct binary file and the FSC generator failed.

If you are not familiar with base64 encoding/decoding, I suggest you look here: https://en.wikipedia.org/wiki/Base64


I created a base64 (printable) version of my good binary FSC file by encoding it with the same site that Aritaurus used: http://www.motobit.com/util/base64-decoder-encoder.asp

It's enclosed below. You should be able to feed it to the GUI and have it generate an FSC code for you.
Attached Files
File Type: txt Good-KS91992.txt (438 Bytes, 1372 views)
Appreciate 2