prpr
Well-Known Member
You've missed the point, which was in the latter part of the post.the Fan package may be scripts rather than MIPS code.
You've missed the point, which was in the latter part of the post.the Fan package may be scripts rather than MIPS code.
I saw that too, different version of MIPS processor like I said. I thought you were pointing out a script based package might work ported from one box to the other.You've missed the point, which was in the latter part of the post.
It's a bit more than that. One is big-endian, the other is little-endian. It's effectively a complete architecture change.different version of MIPS processor like I said.
It might, all other things being equal. But all other things aren't equal. If they were, don't folks think the 'port' would've been done and the package put in the repository?I thought you were pointing out a script based package might work ported from one box to the other.
Oh wow. Well I wrote code that got compiled for MIPS Magnum workstations back in the late 1990s among many other unix variants, and when I asked "why is the MIPS binary twice the size of the binary for any other processor?" work stopped and we spent the afternoon on a deep dive into the stupidities (as I saw it) of the MIPS architecture at the time. The main issue being up to half the binary ends up being NOPs that the compiler has to put in because the processor had no register score boarding. MIPS thought that would be a performance enhancement, and pretty much proved the opposite. If half the code is NOPs, half of the cache is full of NOPs for a start.It's a bit more than that. One is big-endian, the other is little-endian. It's effectively a complete architecture change.
Really?I thought I would give fan.opk a go anyway
It's effectively a complete architecture change.
Maybe you'll work it out and stop being so...incompatible with the architectures configured
so ? - it was still worth a try , I am inquisitive and wanted to try it myself and see what happened - even at the point of thinking i might brick it by trying to load a opk package for a fox T2 on it - I thought at least I would give it a go.Really?
Maybe you'll work it out and stop being so...
No, it wasn't worth a try. Do you try to load Apple Mac drivers on a Windows PC? That's the level of incompatibility here.so ? - it was still worth a try , I am inquisitive and wanted to try it myself and see what happened - even at the point of thinking i might brick it by trying to load a opk package for a fox T2 on it - I thought at least I would give it a go.
Correct, and it's still going (much to my surprise, because I didn't spend big). Previously I killed them quite quickly. I don't think there is a significant difference in the workload between a HD-FOX and a Foxsat – and I am running it 24/7 with TSR enabled.I believe @Black Hole has been trying and failing to kill a USB stick in an HD Fox T2. Not quite the same I know.
of course its not the same - Apple Mac and Windows are totally 2 different things . A Foxsat and Fox T2 HDR are from the same company (Humax) the insides are nearly technically the same, they both use .opk packages. Why would I not give it a go . your remark seems more crazy than my attempt to try an .opk file from the Fox T2 freeview HDR on the Foxsat S2 freesat HDRNo, it wasn't worth a try. Do you try to load Apple Mac drivers on a Windows PC? That's the level of incompatibility here.
But inside the Foxsat and HDR Fox T2 are about as different as an Apple Mac and a Windows PC. Just because they both say Humax on the case and both record TV doesn't make them compatible. Both a Mac and a PC can browse web sites.of course its not the same - Apple Mac and Windows are totally 2 different things . A Foxsat and Fox T2 HDR are from the same company (Humax) the insides are nearly technically the same, they both use .opk packages. Why would I not give it a go . your remark seems more crazy than my attempt to try an .opk file from the Fox T2 freeview HDR on the Foxsat S2 freesat HDR
Cant believe I am being drawn into this but they are so similar the Foxsat and Fox T2 boxes and share so many parts and (I think) were manufactured round about the same time I think werent they? - you skipped past the bit where I said they both had package files and that they end in the same extension (.opk) .But inside the Foxsat and HDR Fox T2 are about as different as an Apple Mac and a Windows PC. Just because they both say Humax on the case and both record TV doesn't make them compatible. Both a Mac and a PC can browse web sites.