Re: Curious fact about Windows vs. Mac

On Fri, 30 Mar 2007 16:43:31 -0700, Alan Baker wrote
(in article <alangbaker-665F9D.16433130032007@xxxxxxxxxxxxxx>):

In article <1175298045.809456.129540@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Jesus" <rustybucket666@xxxxxxxxx> wrote:

On Mar 30, 6:28 pm, Alan Baker <alangba...@xxxxxxxxx> wrote:
In article <lq2r03tu3ojt2430rv6urkplkpoe294...@xxxxxxx>,



tom_e...@xxxxxxxxxxxxx wrote:
On Fri, 30 Mar 2007 15:00:33 -0700, George Graves
<gmgrav...@xxxxxxxxxxx> wrote:

On Fri, 30 Mar 2007 11:37:52 -0700, tom_e...@xxxxxxxxxxxxx wrote
(in article <rilq039411iju587h0gevcvtb7b30eo...@xxxxxxx>):

With Win 95 and even Win 2000 the command line sometimes came in
handy. Yes, the commands were obscure, but they fixed problems. In
Win XP and Vista the command line is still an option, but seldom used,
at least in this shop. I cannot remember the last time I had to open
the CLI in XP or Vista. Mac users, touting the "superiority of Mac
OS, often criticized the Windows user use of the command line, stating
that "Everything should be accessible from the GUI."

Mac OS up to OS X did not even have a command line. Now, with OS X
the UNIX command line (AKA Terminal) has become a way of repairing
numerous issues by hacking files that the OS X system folder that is
off limits to the normal Mac user. The commands needed are as cryptic
and obscure and the old DOS commands in Windows. But now Mac users
think that the command line is REALLY NEAT.

Examples:

1. Server connection drops A number of users are reporting problems
with general network transfers after the update to Mac OS X 10.4.9,
receiving the error message "Server Disconnected" in the middle of
file transfers or experiencing inordinately slow transfers.

This problem generally affects transfers to mounted network volumes.
Transfers from mounted network volumes back to the client Mac are
generally successful.

In some cases, these network bottleneck can be resolved by modifying
the delayed_ack parameter of Mac OS X's TCP/IP configuration by
entering the following command in the Terminal (located in
Applications/Utilities):

sudo sysctl -w net.inet.tcp.delayed_ack=0

2. Frozen windows We've received reports from readers of an issue
where windows become immobile or "frozen" after updating to Mac OS X
10.4.9. When this issue manifests, the windows are generally still
active. In other words, items within the windows can be manipulated,
the scroll bars still work, etc. However, the windows themselves
cannot be dragged to other parts of the screen.

One reader offers a case example:

"I have had problems with some programs that seem to have frozen
windows. That is, I can type in them, but I cannot move them. If I
quit the program and restart it, all works as it should."

In some cases, this issue can be resolved on a semi-permanent basis by
deleting the following file:

/Library/Preferences/com.apple.windowserver.plist

3. Desktop icons missing Some users have reported a problem where
icons on the Desktop are missing after the update to Mac OS X 10.4.9.

In some cases this issue can be resolved by deleting the following
file:

/Library/Preferences/com.apple.finder.plist [The tilde (~) represents
the current home user directory]
then restarting.

Tom Elam

God, is that raft of bull*** that you're floating around on sinking
that
fast that you have grasp at straws like this? Ask 99% of all Mac users
and
they'll go: "What command line?" Or "What Terminal Window?" Macs don't
need
no stinking command line and pretty much everything IS addressable via
the
GUI.

Just out of curiosity, how do you delete files in the System folder?

Tom Elam

First of all, neither of the files you mentioned is *in* the System
folder. But if you really want to delete a file in /System, you double
click on /System and then delete the file. But since there's nothing in
there you'd ever need to delete, let's talk about the /Library folder,
as I assume you actually meant.

You do precisely the same: in your example 2, double-click your HD,
double-click Library, double-click Preferences, and then drag
"com.apple.windowserver.plist" to the trash. If you're not running as an
administrator (as most people probably shouldn't be running), you'll
need to authenticate with an administrator's userid and password.

Don't you need to authenticate regardless?

Nope. I checked just to be sure and at least on my system, you don't.


Not if you log-in as administrator - which I should think that anyone would
do for THEIR OWN, PRIVATE, computer.

.

Quantcast