From: bashley101@gmail.com   
      
   On 9/24/23 12:19 PM, RinaldiJ wrote:   
   > On 9/24/23 13:38, The Real Bev wrote:   
   >> I won't go into any great detail unless somebody here knows A LOT about    
   >> this POS.   
   >>    
   >> The problem is probably with CUPS -- it simply doesn't see the printer,    
   >> which we have set to a static IP address.  Works fine with windows.   
   >>    
   >> Brother updates only .deb and .rpm files, and the conversions are    
   >> frequently FUBAR.  Nothing useful on the CD.   
   >>    
   >> Thanks for listening.   
   >>    
   > Years ago I downloaded the Brother's linux script which downloaded the   
   > rpm's.  Installed them; and pulled my hair out finding that one of the   
   > executables was a 32 bit elf.  Installed Alien's multilib packages   
   > (don't remember which one contains the magic) and all has been good since.   
      
   Hubby gripes about my need for multilib due to my requirement to use Picasa.   
      
   > I do recall the IP was a bit touchy - socket://192.etc works here.   
   >    
   > I read recently the .deb had 64 bit arch covered.  Dunno for sure.   
   >    
   > Here's my files:   
   >    
   > ls -A Printer/   
   > brscan-skey-0.2.4-1.x86_64.rpm     mfcj4510dwcupswrapper-3.0.1-1.i386.rpm   
   > brscan-skey-0.3.1-2.x86_64.rpm     mfcj4510dwlpr-3.0.1-1.i386.rpm   
   > brscan4-0.4.11-1.x86_64.rpm        uninstaller_MFCJ4510DW   
   > brscan4-0.4.8-1.x86_64.rpm         uninstaller_brscan-skey   
   > linux-brprinter-installer-2.2.1-1  uninstaller_brscan4   
      
   He ultimately solved the problem by NOT making the obvious choices in    
   the CUPS setup(s).  The solution was electing 'network printer' (or    
   similar generic;  I'm afraid to even LOOK now for fear of damaging the    
   installation), the IP address and a CERTAIN .ppd file (there are over a    
   dozen on my machine now, same name, sprinkled all over hell and gone).   
      
   I really hate the concept of sprinkling necessary files all over the    
   installation.  I can understand there being common libraries, but not    
   the need for program-specific files (sometimes identical files) located    
   in numerous locations.  Win3 did it right!   
      
   I did get the scanner working with xsane all by myself, though!   
      
   --    
   Cheers, Bev   
   \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\   
   "He who joyfully marches in rank and file has already   
   earned my contempt. He has been given a large brain by   
   mistake, since for him the spinal cord would suffice."   
                                        -- Albert Einstein   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)