Print Finder Windows. How Hard Can It Be?

Joseph said:

I haven’t yet worked on Mac classic , but it has some advance feature .
http://www.atlanticcity.com/blog

Harvey said:

Here’s how:

<Run Terminal>

cd directory
ls > ~/Harvey/Desktop/List.txt

<Quit Terminal>

Harvey said:

I’ve never had a need, burning or otherwise, to print the list of files and folders in Finder. However, if I should ever develop such a need, I’d open the terminal, redirect the ls command to a file, then open the resulting file in an editor.

Mr Squid said:

It says absolutely nothing about my situation.  If an out-of-the-box notebook has an airport problem (as one of mine did)  then it is not a user problem, it is a problem that shipped with the notebook.  Remember, this is not an isolated problem.  I am not the only person who has reported it.  What is disturbing is the “not our problem” response that we are getting from Apple.

sister admin said:

I manage over 250 MacBooks and MacBook Pro’s on my schools multiple Airport networks. They’re all Airport, all the time.

Problems?

Almost none. Those problems I have are usually user related.

What does that say, Squidoo!!

Mr Squid said:

This is an Apple problem, not a user problem.  Airport on notebooks with Tiger installed work.  Airport on notebooks with Leopard installed has a 50-50 chance of working on the same network.  This is true on notebooks that come directly from the factory with no user changes at all.  I have had a notebook work under Tiger and fail to work an hour later after doing a clean install of Leopard.  Apple says that I need to update the firmware on the wireless router, but that will not work if I do not control the router, such as in a coffee shop or in a hotel.  It is easy to simply blame the user, but the reality is that Apple does have a problem with airport, and Apple does not seem to be interested in trying to fix it.  I will not use Leopard on a notebook.  It simply isn’t reliable.  Desktops, on the other hand, work great with Leopard.

dancing-danny said:

I’ve used Airport since the very beginning, back at the turn of the century, on a dozen different Macs in three locations and have ZERO problems. Configuring is a breeze, troubleshooting is easy, and it’s worked every time, right out of the box, even on Windows PCs, notebooks, desktops, and a couple of iPhones.

Sounds like there might be some other kind of problem besides Airport.

I’ve had people curse Apple and try to return their Macs because they had problems. Turns out they installed cheapo RAM which just didn’t do the job. It’s easy to blame Apple for ANY problem we encounter, but it’s not always the right direction for blame.

Mr Squid said:

The obvious thing that Apple forgot is to make airport work.  Right now it is completely unreliable, even with an out-of-the-box system.  If Vista had these sort of wireless problems there would be calls for blood.  For the most part Leopard works very well, but there is no point installing it on a notebook until the wireless problems are solved.  What use is a notebook that can not connect to half of the networks that it encounters.?