GithubHelp home page GithubHelp logo

Comments (4)

RobertBuhren avatar RobertBuhren commented on June 30, 2024

Sorry for the late reply. I believe there is something wrong with some of the entries of that image. Looking at the header of the entries that fail to decompress, I can see that the header says they're compressed (offset 0x48). However, the body data does not look compressed at all.

I have added a warning to PSPtool that allows to continue extracting entries regardless of a failed zlib decompression. If an entry can't be decompressed, the orginal bytes are extracted instead.

I'll keep this issue open for now, in case we stumble on other UEFI images with the same weird behavior.

Regards,

Robret

from psptool.

thehans avatar thehans commented on June 30, 2024

Thanks, I looked at the output from this latest change in a hex editor and it seems that there is still compressed data (magic bytes 78 DA), but it starts at 0x100 offset into what was extracted (eg file: 0x1100064_0.0.10.0)

I have mostly moved on from being interested in this BIOS, since I've replaced the board with a better model. But still willing to test out stuff if there's anything I can help with to make the tool more robust.

Edit:
Full list of warnings on this file, just for reference

Warning: ZLIB decompression faild on entry 0x1100064                                        
Warning: ZLIB decompression faild on entry 0x1100064                       
Warning: ZLIB decompression faild on entry 0x1400064                                        
Warning: ZLIB decompression faild on entry 0x1400064                       
Warning: ZLIB decompression faild on entry 0x1400065                                        
Warning: ZLIB decompression faild on entry 0x1400065                       
Warning: ZLIB decompression faild on entry 0x1100065                                        
Warning: ZLIB decompression faild on entry 0x1100065 

from psptool.

thehans avatar thehans commented on June 30, 2024

BTW not sure what it means but I see two files in output that start with "0x1100064"
0x1100064_0.0.10.0 mentioned above
and
0x1100064_0.0.18.5 which i guess is the part that's not compressed?

from psptool.

RobertBuhren avatar RobertBuhren commented on June 30, 2024

I just pushed some more fixes to psptool. The zlib decompression now works with this image too.

Thanks for reporting this issue.

from psptool.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.