Error Message from Brother MFC Printer

Question

Level 5

4,755 points

Error Message from Brother MFC Printer

I have a Brother MFC-5460CN attached to my Mac (B&W G3 with G4/600 upgrade, 10.4.11) via USB. When I start up my Mac or when I plug in the printer or turn it on, I get the following error message:

Failed to connect to the device.

- Check the I/F cable connection between the device and your computer.
- Please turn OFF the device once, and then turn ON the device again.

Then try again.

[MTW005]

The error message has an "OK" box, but you can't click on it. All I can do is move it off to the corner of the desktop.

The same thing happens on my daughter's eMac with a different Brother MFC, also running 10.4.11, and also happens if I boot my B&W into 10.3.9.

Anybody know what this means and how I can get rid of it?

B&W G3 w G4/600; eMac 700; Performa 6400; eMate 300, Mac OS X (10.4.11)

Posted on Feb 17, 2009 7:21 PM

Reply

Answer 1

Best reply

BDAqua

Level 10

239,219 points

Feb 17, 2009 7:41 PM in response to Bill W

Hi Bill,

Look for a "TwainBridge" driver in Activity Monitor, then kill it/force quit it. That will get rid of that Window.

Maybe try reinstalling it...

http://www.brother.com/E-ftp/macosxdownloadscn.htm

I've heard that just reinstalling was needed, so I'd try that first, if it doesn't work you can delete it.

Reply

Answer 2

Bill W Author

Level 5

4,755 points

Feb 18, 2009 1:22 PM in response to BDAqua

Thanks, BDAqua.

Killing the TwainBridge did indeed get rid of the error message, but reinstalling the driver had no effect- the error returned.

I have an answer from Brother support as well- I'll try their suggestion when I get home tonight.

Reply

Answer 3

Feb 23, 2009 1:57 AM in response to BDAqua

My MFC235C has this bug and as you say the window can only be killed by quitting Twain Bridge. Reinstalling Brother's software won't stop it; the most irritating feature is that it's random; sometimes it does, sometimes it doesn't.
The whole setout of Brother's Control Centre application suggest that their programmers have just ignored Apple's developer guidelines, or treated the App. as an aferthought to the "Windows" version.

Reply