Target Designer/SLX Error: 0x80070057 Bad Parameter

  • Thread starter Thread starter Stephen Medlin
  • Start date Start date
S

Stephen Medlin

Hello,

I just went back to open up my SLX and I am getting an error code 0x80070057
with a description of "The parameter is incorrect" when I try to open the
SLX. It appears that there is something wrong with the SLX and both of my
copies of the file seem to be "corrupt."

Any help on what this code means, how to correct it (if possible), and/or
how to get a listing of the components that are in the SLX would be
appreciated.

I have a previous version that I can open, it is the same size and almost
the same date as the newer one (with 10 minutes or so) and I don't recall
adding any components at the last minute (and I didn't document that I had
added any). But I would like to confirm if possible.

Any tools out there that repair the SLX or convert it into a text file that
can be read?

Stephen Medlin
 
Stephen Medlin said:
Hello,

I just went back to open up my SLX and I am getting an error code 0x80070057
with a description of "The parameter is incorrect" when I try to open the
SLX. It appears that there is something wrong with the SLX and both of my
copies of the file seem to be "corrupt."

Any help on what this code means, how to correct it (if possible), and/or
how to get a listing of the components that are in the SLX would be
appreciated.

I have a previous version that I can open, it is the same size and almost
the same date as the newer one (with 10 minutes or so) and I don't recall
adding any components at the last minute (and I didn't document that I had
added any). But I would like to confirm if possible.
Click to expand...

I'm surprised it's the same size - whenever I've had this happen the corrupt
file was tiny, and the problem caused by TD crashing after running out of
memory during a save.
 
That's what I would have thought also when I looked at the size/date.
Nothing had happened when I made the image (i.e., no crashes, etc.). I just
needed to add some new components to the latest version and that's when I
discovered this problem.

After I posted this message, I went to the previous version and re-compiled
my image and then compared the new log file with the one from the corrupt
SLX. They appear to be identical, so I'm hoping that my previous version ==
the last/corrupt version. It would still be nice to know what this error
means and how to fix it if possible.

Stephen
 
Back
Top