View Single Post
      06-09-2014, 09:40 AM   #54
pikcachu
Major General
pikcachu's Avatar
1399
Rep
5,262
Posts

Drives: M235i (F22 Red angel)
Join Date: Jul 2011
Location: undisclosed

iTrader: (1)

Quote:
Originally Posted by Frogman View Post
So, you're good now, right?

Humm, questions:

1. When you read the FSC via E-Sys, it appears it's already in binary form (not base64 encoded), correct?

2. You are able to manually generate the correct short code with the original FSC extracted from the car via E-Sys, right?

If both are yes, then E-Sys is extracting the correct FSC file.

It looks like Aritaurus had you base64 encode the FSC to make the GUI happy and that encoded FSC is what is bad.

If so, I wonder if the issue is that somewhere along the way, the base64 encoding step somehow messed the file up and that E-Sys is working correctly.

The SWID reader technique reads the FSC and base64 encodes it automatically, so that step is skipped when generating the short code.
1) Yes the FSC from esys is already binary
2) Yes I can get the code if i run nbt.exe directly with the .fsc

well the Phonix129 generator won't work with the binary fsc... for that to work i had to use the base64 encoded one and in that case it shows the "fields!!" message...

but the nbt.exe takes the fsc from esys directly and works....

The other generator with the i8 pic didn't work either neither with the binary nor the base64.... but in both cases i was using the file that had the 0x20 instead of the 0x00

so maybe both generators work with the file sanitized with 0x00
Appreciate 1