iPhone 3GS from AT&T. Free Shipping
Mac OS X 10.3.3 (#15): Epson 740 driver; Printing through a networked Mac OS X 10.3.3 system; more
Epson 740 driver Last week we reported problems printing to the Epson 740 under Mac OS X 10.3.3.
First, it should be noted that some Epson drivers are located on the third CD of the Mac OS X 10.3.x (Panther) installation set.
Knowledge Base article #25588 notes Epson drivers located on the second and third Panther installation discs (in /Packages/EpsonPrinterDrivers1.pkg and /Packages/EpsonPrinterDrivers2.pkg respectively).
John Stagaman notes that selecting specific drivers from the various offerings allowed proper printer operation "My sister-in-law had the same problem and Apple support was able to fix it (I couldn't after trying several approaches). In this particular instance, we could print neither when directly connected with USB nor through an Airport connection.
"There are apparently multiple Epson 740 drivers in 10.3--when selected using Rendezvous the incorrect driver was selected. When Apple helped, they had us manually select the USB drivers, then select the corresponding Epson 740 driver. It resolved the problem. It struck me as weird, but it worked."
Glenn Heilemann's case, all that was required to resolve this issue as a simple unplugging then re-connecting his printer:
"I had the problem with the Epson 740 printer not showing up in 10.3. The fix for me, after running permission repair, was to unplug the printer and plug it back in. All was fine after a simple work around such as this."
Printing through a networked Mac OS X 10.3.3 system MacFixIt reader Eric reports a problem printing from a system running Mac OS 9.2.2 through a Mac OS X-connected shared printer since updating to Mac OS X 10.3.3.
"Have a G5 running Mac OS X 10.3.3. My printer problem has to do with my other older Mac's running 9.2. I originally set the computers up using help topic "Printing to a Mac OS X shared printer from Mac OS 9 via LDP/LPR". This had been working great since 10.3.2. Now the OS 9 computers can verify the printer but when attempting to print I get a dialog screen stating the printer on the G5 is unavailable. I can print from the G5 with error."
Command (Key) not working in Finder Tim Murray reports a problem where the Command key, used in conjunction with other keys to execute shortcuts, does not function correctly.
"At times, some command-type keyboard shortcuts do nothing. For example, at this moment, in the Finder, Command Delete and Option Command O don't do anything, yet others, such as Cmd W, work okay. In the case of Cmd O, it is not as though the command key is simply ignored, as no navigation occurs as if I had pressed only the letter O.
"It's limited to the Finder, as the same command keys work in other apps that support them. [...]
"I posted this on the comp.sys.mac.system newsgroup (same subject as this e-mail dated 03/22), and found others are experiencing it too. In the case of some other individuals, they can get their keys back by Command clicking a file to get a contextual menu. In my case, I have to reboot. Some of use have compared startup items have found no correlation."
If you are experiencing a similar issue, please drop us a line at late-breakers@macfixit.com.
Resources
:%20Epson%20740%20driver;%20Printing%20through%20a%20networked%20Mac%20OS%20X%2010.3.3%20system;%20more%20%7C%20MacFixIt%20-%20CNET%20Reviews&srcUrl=http://reviews.cnet.com/8301-13727_7-10344002-263.html){kind=small}
Panther uses the CUPS (Common Unix Printer System) drivers that are now
included with the operating system. If you click on the Show Info button in
Printer Setup Utility, you will see the type of driver that Panther uses.
This may be problematical with those who use the color management
function because it is not available under CUPS. To get this functionality back,
the actual Epson 740 printer drivers have to be installed from the 3rd install
disk. Then, you need to delete the Epson 740 printer running under CUPS and
add the Epson 740 printer back once again, but now, you should consciously
select the actual Epson printer driver file, instead of letting the system select
it for you.
working in Finder," I might add a few observations:
One trigger for causing certain command key shortcuts to stop working is to
enable authentication when waking from sleep or exiting the screen saver as
set in the Security preference pane. While logged into an account, activate
the Screen Saver (via a hot corner or automatically) or put the computer to
sleep, then exit the screen saver or wake the computer up. After
authenticating as the currently logged-in user, some command keys will no
longer work as expected. For example, pressing [command]+[o] may not
invoke the Open command, but pressing [command]+[down arrow]
will.
My solution has simply been to relaunch the Finder via the Force Quit
panel.
I'm pretty certain that this is a Finder-specific bug, and that it has nothing to
do with what startup items are loading from /System/Library/StartupItems/
at boot time. I have observed this problem in Mac OS X 10.3.2 and 10.3.3.
accessibility standards -- if you just open each menu once (just going
through the whole menu bar sliding through), EVERYTHING SHOULD THEN
WORK AGAIN. At least, that's what I've found, without fail. No restarting or
force-quitting necessary.
Hope this helps!
Jeff
However, I do have a work-around for the command-key problem.
I have been able to work around the command-key problem by hitting return
on the file as if I'm going to rename it, then hit return again and then do the
command key I want.
If there is more than one file selected, I arrow to one so one is highlighted,
then do the above return, return then use my keyboard to select the other
files again and do the command key.
- by Jakacmar April 5, 2004 12:45 PM PDT
- Regarding key combos stopping to function. I've been experiencing this
- Like this Reply to this comment
-
(5 Comments)since 10.3.0 and have submitted numerous bug reports to Apple in addition
to discussing this more than once in the Panther threads at Apple
Discussions. I've found that there are two ways to get the command-
whatever key combos working again.
1) Click the File menu in the Finder. No need to open EVERY menu, just the
file menu as these are the only shortcuts that become unresponsive. Next
time you have the shortcuts stop working, try hitting command-a, chances
are everything will be selected since this is an Edit menu command. Strange.
2) Change view from whatever you're using (in my case it's always column
view) to something else, and back again. This can be done using Command
-1, 2, or 3 for Icon, List, and Column view respectively. Note that these key
combos still work. Unfortunately, if what you're trying to do is close a
window (cmd-w) this won't fix that, you need to click the File menu to get
that one working. Stranger.
Lastly, often times, even though say cmd-w won't work to close a window,
hitting cmd-option-w WILL work to close all window. Similarly, cmd-o may
be unresponsive, but cmd-option-o will work to open the file while closing
the Finder window.