From Tronics

Tronics thoughts about the new boot.
I thought I would create a thread about my concerns about the new boot files that have been released recently.

First I think the work done by Ukronic, Fwank etc is good and this is not meant to in any way cast their contributions in any negative light whatsoever.

My concern is basically in regard to the naming convention for the new boot files.

First for any who are not already aware, the puff code is not specific to FTA or anything like that. It is a small footprint (meaning compiles to a smaller size and therefore takes up less space) version of the GZip inflate code and was created by a guy named Mark Adler who was/is a major contributer to the creation of the GZip compression algorithm. So the major point here is that PUFF DECOMPRESSES GZIP COMPRESSED FILES.

Now the new boots contain a different decompression routine. They contain code to decompress files that have been compressed with LZMA compression.
The new boots do not use the puff code at all, and this brings me to my concern/point.

In my opinion calling a LZMA boot PUFF version 1.0.2 or 1.0.3 or anything with PUFF in the title is wrong and does nothing but create unnecessary confusion. Most people have a hard enough time as it is figuring out what files go with what boot and how to convert between them. There has been a history of poor naming conventions with respect to the boot files so far and we have all seen the confusion it has caused. I understand why the b75_m boot was named as it was but it has caused confusion between the modified version of the b75 boot which included the lh5 decompress code and the original b75 from blacklist that contains no decompression code. Then came the Puff boot which I think was named well. There was no confusion between the puff boot and either of the b75 boots. If you were running the PUFF boot then it was obvious that you were to run puff bins (aka Gzip compressed bins). Now with the new boot being called PUFF version 1.0.2 or PUFF 1.03 it is now unclear if you are running PUFF bins(GZip compressed files) or LZMA bins( bins compressed with LZMA). I realize that the LZMA version has the periods set on the display but I think that most people do not pay enough attention to details like that and it would be so much easier to just have the LZMA boot be called LZMA and not PUFF. I suspect that they called it PUFF version 1.0.2/3 because of the whole "team puff" brand if you will that has been created but I think that it is not the right way to go here.

It would be easy to make the new boot say something like LZLZBOOT or the like and if people agree with me then I could make such a boot available.

I am sure that my posting of this will generate some feedback and I would like to hear what people think. If people think I am making too big a deal over this point then I will say nothing more. I am not trying to force anything here I am just stating why I think that things should be different and why.

So what do you guys think? Do I make a good point or am I making too big a deal over this? These are just my thoughts on the matter and that is what having a forum is all about.

I look forward to hearing some of your thoughts on the matter.

Regards,
Tronics

From Tronics


he boot says PUFF 1.0.2 or PUFF1.0.3 but they cannot take PUFF bins they must have LZMA bins because despite the name of the boot it is actually using LZMA.

If you load a PUFF(GZip) bin to a reciever that has the LZMA boot (the boot currently named either PUFF 1.0.2 or PUFF 1.0.3) then it will not boot and will be stuck at (F.)

If you load a LZMA bin to a receiver using the PUFF(GZip) boot (the file named PUFF 1.0.1) then it will also not boot and will be stuck at (F)

This is why I say you should call the new boots that use LZMA, LZMA boot and not PUFF because they do not use the PUFF code at all and will not boot a PUFF(GZip) bin

Just to be clear I think the filename should be something like LZMA boot but since the 7segment displays cannot represent an M I suggested having it say LZLZBOOT on the front instead of P.U.F.F.P.U.F.F. as it does currently. This is just one idea for the front text off the top of my head but the main thing here is to create an obvious distinction between the boot that uses the puff code and the boot that uses the LZMA code.

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

Tired of waiting days for fixes? Click here to get 3000 channels.. NO DOWNTIME, Guaranteed!

Steve, the naming of the boot fies you suggest makes perfect sense. If I am reading this right then the tronics bin convertor will not work with lzma boot file? If this is right are there any plans for a tronics bin mod to lzma program? Sorry for the questions I am just trying to understand the system a little better.
Thanks again

__________________
Their not listening still, perhaps they never will

yes tronics is working on a new bin mod to use lzma boot file and lzma files

__________________
Testing,:Fortec Ultra,: Digiwave 7000,: Viewsat Extreme 2000,: Extremeview Magnum 3300,: Xrica-X5,: Satopia ST1100-UT,:Visionsat IV 200 Pvr Plus,: Spacestar 700S,: CaptiveWorks 800S,: XFactor X-1,:CNX Duo,: True Free To Air,; Proud Member Of The Elite Fourhorsemen ''Giverhell'' 4 Life


*****WWW.MARITIMEFTA.COM*****



R.I.P Bojac - The Fta community will Always Remember You - Deceased December 30, 2008

R.I.P brat6990 The Fta community will Always Remember You - Deceased March 9th 2009

I converted one of my FLU to puff_282_bin and use bin/mod/loader with
X-87BL_090122_B75_V207_api_femu. and it works, puff_bins only, not lzma_bins

Thanks Tronics

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

After I convert one of my FLU to puff_282 Then used bin/mod/loader with
X-87BL_090217_B75_V208_api_femu. and it works, puff_bins only, not lzma_bins

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

With one of my FLU use the puff_bins and with Tronics bin/mod/loader using
X_87BL_090226_V209_api_femu file all is up no freezing

Thanks Tronics

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

With one of my FLU use the puff_bins and with Tronics bin/mod/loader using X_87BL_090328_V211_api_femu, set key default and showed scramble off/on until got new keys all is up don't show any freezing or scramble so far
Thanks Tronics

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

Is the 211 avail here, Stevega? If so, where?

whodunit

If you box has puff bin and not lzma bin, you use the 2700 BL_211 bin, the file is in the pansat 2700 file section

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

Here the file 2700 you use

http://www.fortecfiles.com/pansat-27..._api_femu.html (X_87BL_090328_V211_api_femu)

__________________
Testing convert FLU to 2700, CW800, Visionsat IV200 & SV-360 Elite
http://www.maritime-fta.com/

Tired of waiting days for fixes? Click here to get 3000 channels.. NO DOWNTIME, Guaranteed!