Hacking Check/Verify installed version of Boot9strap?

  • Thread starter Thread starter AndrewH
  • Start date Start date
  • Views Views 49,633
  • Replies Replies 26
  • Likes Likes 1
Try the one attached here. This one just reads the FIRM header instead of the r2 lie.

If you run a non-release version of b9s, it will say "Boot9strap Nightly".
Also, should a new version of b9s be released, it will also show as "Boot9strap Nightly". Someone tag me when > 1.3 releases so the app can be updated (if I forget to do it).
B9S just got updated so here I am tagging you so the app can be updated :)
Thank you for the previous release! :grog:
 
B9S just got updated so here I am tagging you so the app can be updated :)
Thank you for the previous release! :grog:
And thank you for reminding me :)
I've never really liked how the older b9s_check was made so I rewrote most of it.
This new version will check for b9s 1.4 and a lot of other stuff too.

https://github.com/zoogie/b9s_check/releases
And yay, source code at last.
 
  • Like
Reactions: zoogie
And thank you for reminding me :)
I've never really liked how the older b9s_check was made so I rewrote most of it.
This new version will check for b9s 1.4 and a lot of other stuff too.

https://github.com/zoogie/b9s_check/releases
And yay, source code at last.
was able to compile:

1655830060684.png
 
  • Like
Reactions: zoogie
What's the difference between FIRM0 and FIRM1?
In both cases "boot9strap_1.4.firm" is detected...
Is this correct?

Thanks a lot!
 
What's the difference between FIRM0 and FIRM1?
In both cases "boot9strap_1.4.firm" is detected...
Is this correct?

Thanks a lot!
That's both fine and typical.
FIRM1 is a backup to FIRM0, should FIRM0 become corrupted. They should be identical (but don't have to be).
If both FIRMs are corrupted, then "bluescreen" of death.

I think you'll find there's quite a bit of difference to the latest stable release, 2.0. I should publish a new release.
 
  • Like
Reactions: alcab

Site & Scene News

Popular threads in this forum