XPost: alt.comp.os.windows-11   
   From: nospam@needed.invalid   
      
   On Sat, 4/5/2025 12:23 PM, Carlos E.R. wrote:   
   > On 2025-04-05 15:14, Java Jive wrote:   
   >> On 2025-04-05 11:47, Carlos E.R. wrote:   
   >>>   
   >>> On 2025-04-05 01:20, Java Jive wrote:   
   >>>>   
   >>>> On 2025-04-04 21:52, Carlos E.R. wrote:   
   >>>>>   
   >>>>> Huh, I have an idea. If this box in the end is not valid, I could rip it   
   out and insert usb2sata connectors on the back of each disk. Use only the   
   power supply and the iron. It would be ugly and impose a delay on my project,   
   and waste of money, but    
   would work.   
   >>>>   
   >>>> Wouldn't it be easier to try to solve the firmware problem?  If you're   
   going to destroy the innards, invalidate the warranty, and so not be able to   
   return it anyway, why not try installing a fixed firmware first?   
   >>>   
   >>> But someone has to provide the fixed software file.   
   >>   
   >> Paul gave you a big clue in his post of 2025-04-04, 04:33.  He didn't want   
   to give actual links because he couldn't verify their sources, but you can   
   search on the file names he gave, for example:   
   >>   
   >> https://duckduckgo.com/?q=jms578fwupdater.tgz   
   >>   
   >   
   > It has to be an update of the Yottamaster model F55 specifically, and I   
   didn't see any.   
   >   
      
   I don't think there are that many firmwares out there.   
      
   The "NVRAM" whether emulated or not, there are bytes   
   in there that control the controller operating mode,   
   and the NVRAM is not protected by a checksum.   
      
     https://helmet.kafuka.org/bboard/thread.php?id=259   
      
   And some of these discussion threads, seem to indicate   
   the firmware size is a lot smaller than the flasher flash file   
   size. the uncompressed firmware might be 4MB, but if you   
   do a backup of an existing firmware, it's on the order of 50668 bytes.   
   Which is a more reasonable or believable value. When you get your   
   flasher package, you may want to pop the "firmware file" into   
   a hex editor, and see if large portions of it are zero. The SPI   
   chip inside your box, may not be a matching 4MB, but could be   
   a lot smaller, like maybe 128KB (to hold a 50668 byte file).   
      
   When we did two controllers (having entirely different functions),   
   the firmware for those fit in 3KB of code. That's why I had trouble   
   believing a firmware needed 3MB to work. And the 50668 bytes or whatever,   
   is still large, but isn't too much of a multiplier over 3KB.   
      
      Paul   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)