Jump to content

Search the Community

Showing results for tags '64 bit'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The Highlands
    • Announcements
    • Bruno's All Things Linux
    • All Things Windows
    • All Things Mac
    • Hardware
    • Mobility
    • Security & Networking
    • Social Media
    • The Restaurant at the Edge of the Universe
    • Forum Feedback

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 2 results

  1. I have a Windows 7 (64 bit) Dell Inspiron One infected with the "FBI lock screen virus (REloadit Pack Scam)" I'm unable to boot into Safe Mode. When I hold F12 on boot up I get the following boot options: - Hard Disk - DVD/CD drive - Diagnostics - BIOS Setup None of those help me. (The "Diagnostics" option results in the Dell "ePSA Pre-boot System Assessment" which simply checks all the hardware (cables, OS Boot Path, drives, video card, CPU fan, processor and memory) with no outlet to a Command Prompt or anything . . . so useless.) So the problem via this method is getting to the desktop which I can not due. I ran Windows Defender Offline on the infected machine. It found 7 problems but not the ones related to the FBI ransomware because upon reboot the same situation existed. My safe machine is my Windows 7 (32 bit) laptop. Next I found HitMan Pro Malware Removal tool which specifically mentions the FBI ransomware. My problem now is how do I make a USB stick for the 64 bit infected machine from my 32 bit safe machine? (This is my actual question) Any other ideas on how to get this bugger out? Thanks, Steve
  2. I am trying to install Brother drivers on Mepis 64 bit and the .deb provided by manufacturer are 32 bit. The Brother Solutions Center lists these instructions Everything goes fine until I get to the install drivers step (3.) Following the Cupswrapper Driver Install instructions Command (for dpkg) : dpkg -i --force-all (lpr-drivername) Command (for dpkg) : dpkg -i --force-all (cupswrapper-drivername) First command runs fine and lpr driver installs. Second command I get the following error output [root@mepis1 Printer]# dpkg --force-all -i cupswrapperDCP7065DN-2.0.4-2.i386.deb dpkg: warning: overriding problem because --force enabled: package architecture (i386) does not match system (amd64) (Reading database ... 100170 files and directories currently installed.) Preparing to replace cupswrapperdcp7065dn 2.0.4-2 (using cupswrapperDCP7065DN-2.0.4-2.i386.deb) ... sh: Can't open /usr/local/Brother/Printer/DCP7065DN/cupswrapper/cupswrapperDCP7065DN-2.0.4 dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg - trying script from the new package instead ... sh: Can't open /usr/local/Brother/Printer/DCP7065DN/cupswrapper/cupswrapperDCP7065DN-2.0.4 dpkg: error processing cupswrapperDCP7065DN-2.0.4-2.i386.deb (--install): subprocess new pre-removal script returned error exit status 127 sh: Can't open /usr/local/Brother/Printer/DCP7065DN/cupswrapper/cupswrapperDCP7065DN-2.0.4 Errors were encountered while processing: cupswrapperDCP7065DN-2.0.4-2.i386.deb This is the step that creates the files to be moved in step 4, so it doesn't work. Been Googling off and on for a couple hours and finding lots of weird Ubuntu stuff, but nothing related to driver installs. Any ideas about what error 127 is and how to fix it.
  • Create New...