Defragmenting 'System'

L

Lieutenant Scott

Lieutenant said:
Lieutenant Scott wrote:
Why? It doesn't fall over because the system disc is too small. It falls
over because the way I use it can cause bits of the system to become
corrupted. Occasionally, it's the HD failing that causes the problems.

I normally leave between 15 and 20% free space on the system disc, and
I've not noticed any greater stability by leaving more free space.
I wasn't referring to your "system falls over", I was just surprised you have a system that doesn't increase in size.
 
L

Lieutenant Scott

Have you ever worked in a small business where you were not the owner /
guy who has the power to buy newer computer equipment? It is common in
small business environments to wring every last bit of usefulness out
of a given piece of equipment before upgrading or replacing it. Lower-
level employees especially learn to "make do" with what they have,
deleting the oldest files to make room for the new, learning when to
start a particular long-running process so that they take a coffee
break / lunch break or even leave for the day so it is done when they
return. Not everyone has the luxury of upgrading or replacing computer
equipment on demand, in fact, few in the business world do.
The most expensive thing in any business is the staff wages. It never makes sense to scrimp on something as cheap as a computer part and make the staff work longer hours.
BTW, you should consider setting the line length on your newsreader to
something shorter, say 72 characters, so that it breaks lines in your
posts at more reasonable length.
Been discussed before. I have no desire to limit my length to a specific value, it's meant to be auto-wrapping at your end, look up the "format flowed" RFC.

If you can work out what part of the RFC my newsreader breaks (I don't know if it's mine or yours that isn't following it correctly) then let me know and I'll pass it on to the programmers, because nobody's worked it out yet.

It only seems to upset the lesser known newsreaders like Gravity and Turnpike, while Agent and the dreaded Outhouse Distress read my posts ok. It could be that they're less fussy about incorrect formatting, or it could be that they follow a later RFC, I don't know.

But what makes no sense at all is how ANYTHING my newsreader does could stop yours from wrapping when it hits the edge of your screen.

--
http://petersparrots.com
http://petersphotos.com

Six stages of married life:
1: Tri-weekly
2: Try weekly
3: Try weakly
4. Try oysters
5: Try anything
6: Try to remember
 
J

John Williamson

Lieutenant said:
Lieutenant said:
On Wed, 14 Nov 2012 20:45:11 -0000, John Williamson

Lieutenant Scott wrote:
On Wed, 14 Nov 2012 20:27:32 -0000, Philip Herlihy
<[email protected]>
wrote:



I wasn't referring to your "system falls over", I was just surprised you
have a system that doesn't increase in size.
Why buy more than I need? The data held can easily be increased at any
time without touching the system by adding external drives. I know what
I want on the system disc before I build the system.

My systems do expand over time, though. This laptop started with a 160
Gig HD in it early this year, and now has double that. Another one I use
regularly started with a massive 80 Gig, (The biggest offered at the
time) and now has a puny 500 Gig. I don't trust the terabyte laptop
drives yet. They've both got rather more RAM than they came from the
factory with, too.
 
L

Lieutenant Scott

Why buy more than I need? The data held can easily be increased at any
time without touching the system by adding external drives. I know what
I want on the system disc before I build the system.

My systems do expand over time, though. This laptop started with a 160
Gig HD in it early this year, and now has double that. Another one I use
regularly started with a massive 80 Gig, (The biggest offered at the
time) and now has a puny 500 Gig. I don't trust the terabyte laptop
drives yet. They've both got rather more RAM than they came from the
factory with, too.
What I meant was the size of the system disk increasing, as opposed to the data disk. It's easier, and faster, to have a system disk double the size of what you need now.
 
J

John Williamson

Lieutenant said:
What I meant was the size of the system disk increasing, as opposed to
the data disk. It's easier, and faster, to have a system disk double
the size of what you need now.
I say again. My system discs are of adequate size and do not need to
grow during the working life of the system. They do not limit either the
number of programs I have installed or the size of the swapfile. I also
install enough RAM that a swapfile isn't really needed anyway for my
pattern of usage. The only improvement in speed would be from installing
an SSD instead of the HD, but that would probably mean disabling swap
and installing more RAM to compensate, unless SSD write life has
improved greatly since last time I looked.

I've only been building Wintel PCs on very limited budgets for 30 years,
after all.
 
G

Gene E. Bloch

On Wed, 14 Nov 2012 21:19:47 -0000, Zaphod Beeblebrox
The most expensive thing in any business is the staff wages. It never makes
sense to scrimp on something as cheap as a computer part and make the staff
work longer hours.
Been discussed before. I have no desire to limit my length to a specific
value, it's meant to be auto-wrapping at your end, look up the "format
flowed" RFC.
If you can work out what part of the RFC my newsreader breaks (I don't know
if it's mine or yours that isn't following it correctly) then let me know and
I'll pass it on to the programmers, because nobody's worked it out yet.
It only seems to upset the lesser known newsreaders like Gravity and
Turnpike, while Agent and the dreaded Outhouse Distress read my posts ok. It
could be that they're less fussy about incorrect formatting, or it could be
that they follow a later RFC, I don't know.
But what makes no sense at all is how ANYTHING my newsreader does could stop
yours from wrapping when it hits the edge of your screen.
I switch between two newsreaders. Currently MesNews, alternatively
40tude Dialog. Both are happy with your lines, even when I change the
width of the message pane.

In quoted text, things get messy in Dialog, but look OK in MesNews.
This is based on about 10 seconds each of changing the width of the
pane, so maybe it's not definitive.
 
Z

Zaphod Beeblebrox

The most expensive thing in any business is the staff wages. It never
makes sense to scrimp on something as cheap as a computer part and
make the staff work longer hours.
To you perhaps, but many business don't look at things that way. It is
unfortunately very common for staff to limp along with computer
equipment that was fully depreciated years ago and is barely able to
perform the functions asked of it. That, along with non-existent
maintenance, produces machines that benefit greatly from defragmenting
and other basic procedures.
Been discussed before. I have no desire to limit my length to a
specific value, it's meant to be auto-wrapping at your end, look up
the "format flowed" RFC.

If you can work out what part of the RFC my newsreader breaks (I
don't know if it's mine or yours that isn't following it correctly)
then let me know and I'll pass it on to the programmers, because
nobody's worked it out yet.

It only seems to upset the lesser known newsreaders like Gravity and
Turnpike, while Agent and the dreaded Outhouse Distress read my posts
ok. It could be that they're less fussy about incorrect formatting,
or it could be that they follow a later RFC, I don't know.

But what makes no sense at all is how ANYTHING my newsreader does
could stop yours from wrapping when it hits the edge of your screen.
Oh, it doesn't upset my reader in the least. When the text hits the
edge of the window, it line wraps. When my reader window is relatively
wide (as it often is for reasons I'll not go into), it makes it harder
to read.

Your desire notwithstanding, as I have always been taught and have read
in many, many places it is considered proper "Netiquette" to wrap long
lines, and as I understand RFC 2646
(http://www.ietf.org/rfc/rfc2646.txt)

Section 4.1 (Generating Format=Flowed) covers this, and, paragraph 5
specifically states:

A generating agent SHOULD:

1. Ensure all lines (fixed and flowed) are 79 characters or
fewer in length, counting the trailing space but not
counting the CRLF, unless a word by itself exceeds 79
characters.

The generating agent (your newsreader, when it posts an article or
follow-up) should do so. To me, it isn't at all hard to work out.
 
J

Jolly polly

Wolf K said:
On 14/11/2012 3:00 AM, Jolly polly wrote:
[...]
How would a Windows user defrag a drive in Linux? not easy at all
Boot Linux from a live CD/DVD, and use a defrag utility made to defrag
Windows system drive.

Search on "windows defragment from Linux live CD" for more.
I only know how to defrag an NTFS volume in Linux using cmd line, are you
able to name a Linux program that can do this?
 
L

Lieutenant Scott

I say again. My system discs are of adequate size and do not need to
grow during the working life of the system. They do not limit either the
number of programs I have installed or the size of the swapfile. I also
install enough RAM that a swapfile isn't really needed anyway for my
pattern of usage. The only improvement in speed would be from installing
an SSD instead of the HD, but that would probably mean disabling swap
and installing more RAM to compensate, unless SSD write life has
improved greatly since last time I looked.
Don't get an OCZ, they suck. Corsair are 4 times more reliable.
I've only been building Wintel PCs on very limited budgets for 30 years,
after all.
I've never tried separating the system that much from the data (installed programs have always gone on the system disk for example), so a fixed system disk size is impossible for me.
 
B

Bob I

No you haven't - the speed "increase" has been due to something else.
I've been using Windows ever since 3.1 and /I've/ never noticed any
speed increase...
Either you don't significantly fragment the drive, or you don't notice
much. I went a purchased DiskKeeper for Windows 2000 because of
fragmentation due to problems caused by files created by a scanner
littering the HD with files and then timeouts occurring. Each time the
issue came up, defragging the HD restored the speed.
 
L

Lieutenant Scott

To you perhaps, but many business don't look at things that way. It is
unfortunately very common for staff to limp along with computer
equipment that was fully depreciated years ago and is barely able to
perform the functions asked of it. That, along with non-existent
maintenance, produces machines that benefit greatly from defragmenting
and other basic procedures.
Fortunately I've always worked where managers listen to my recommendation to spend more on IT. An extra £50 won't break the bank. It's less than a day's wages for most users.
Oh, it doesn't upset my reader in the least. When the text hits the
edge of the window, it line wraps. When my reader window is relatively
wide (as it often is for reasons I'll not go into), it makes it harder
to read.
I don't seem to have a problem reading lines [counts] 180 characters wide, which is what my screen shows. Can your eye not dart back along something that long?
Your desire notwithstanding, as I have always been taught and have read
in many, many places it is considered proper "Netiquette" to wrap long
lines, and as I understand RFC 2646
(http://www.ietf.org/rfc/rfc2646.txt)

Section 4.1 (Generating Format=Flowed) covers this, and, paragraph 5
specifically states:

A generating agent SHOULD:

1. Ensure all lines (fixed and flowed) are 79 characters or
fewer in length, counting the trailing space but not
counting the CRLF, unless a word by itself exceeds 79
characters.

The generating agent (your newsreader, when it posts an article or
follow-up) should do so. To me, it isn't at all hard to work out.
That doesn't make sense to me. I thought the whole idea of format flowed was that it displays at the width the READER desires. For example, I see Gene E. Bloch's text at the width of my screen. If that doesn't suit you, then there's nothing to stop you changing the width you see. I'mnot forcing anything on you.
 
L

Lieutenant Scott

I switch between two newsreaders. Currently MesNews, alternatively
40tude Dialog. Both are happy with your lines, even when I change the
width of the message pane.

In quoted text, things get messy in Dialog, but look OK in MesNews.
This is based on about 10 seconds each of changing the width of the
pane, so maybe it's not definitive.
I incorrectly assumed Zaphod had the trouble some Turnpike users have, in that my text goes off the edge of the screen. It seems he just has poor eyesight.
 
G

Gene Wirchenko

[snip]
I don't seem to have a problem reading lines [counts] 180 characters wide, which is what my screen shows. Can your eye not dart back along something that long?
Sure, but with shorter lines, I can read the entire line with
very little eye movement. This reduces the possibility of losing sync
considerably.

[snip]

Sincerely,

Gene Wirchenko
 
Z

Zaphod Beeblebrox

Fortunately I've always worked where managers listen to my
recommendation to spend more on IT. An extra £50 won't break the
bank. It's less than a day's wages for most users.
You are indeed fortunate then. Fact remains that defragmenting the
drive can produce performance benefits for many users.
Oh, it doesn't upset my reader in the least. When the text hits the
edge of the window, it line wraps. When my reader window is relatively
wide (as it often is for reasons I'll not go into), it makes it harder
to read.
I don't seem to have a problem reading lines [counts] 180 characters
wide, which is what my screen shows. Can your eye not dart back along
something that long?

There is a reason newspapers and other printed media use narrow columns
of text - it is easier to scan. Has nothing to do with eyesight.
That doesn't make sense to me. I thought the whole idea of format
flowed was that it displays at the width the READER desires.
You asked for the relevant reference from the RFC, I provided it.
Whether or not you understand the reasoning, if you choose to ignore it
then you are not being a good "netizen".

For example, I see Gene E. Bloch's text at the width of my screen. If
that doesn't suit you, then there's nothing to stop you changing the
width you see. I'm not forcing anything on you.
But you are. I have to adjust my reader window width from the
configuration I prefer if I want your posts to display properly.

I'm not going to argue the point any further. The RFC is clear, what
you do with it is certainly your choice but if you choose to flout
convention, netiquette and the RFC then you are just being stubborn.

--
Zaphod

Pan-Galactic Gargle Blaster: A cocktail based on Janx Spirit.
The effect of one is like having your brain smashed out
by a slice of lemon wrapped round a large gold brick.
 
W

Wolf K

[snip]
I don't seem to have a problem reading lines [counts] 180 characters wide, which is what my screen shows. Can your eye not dart back along something that long?
Sure, but with shorter lines, I can read the entire line with
very little eye movement. This reduces the possibility of losing sync
considerably.

[snip]

Sincerely,

Gene Wirchenko
Lt Scott's comment displays ignorance of ergonomics. I trust it was a
mere momentary lapse.
 
L

Lieutenant Scott

[snip]
I don't seem to have a problem reading lines [counts] 180 characters wide, which is what my screen shows. Can your eye not dart back along something that long?
Sure, but with shorter lines, I can read the entire line with
very little eye movement. This reduces the possibility of losing sync
considerably.

[snip]

Sincerely,

Gene Wirchenko
Lt Scott's comment displays ignorance of ergonomics. I trust it was a
mere momentary lapse.
It displays first hand experience. If you don't like wide lines, then change your display to suit your eyes. We are not all equal.

I can display your lines and everyone else's at any width I choose.
 
L

Lieutenant Scott

I don't seem to have a problem reading lines [counts] 180 characters wide, which is what my screen shows. Can your eye not dart back along something that long?
Sure, but with shorter lines, I can read the entire line with
very little eye movement. This reduces the possibility of losing sync
considerably.
Half the darts, twice the length of dart. Sync problem equal. Non-existent in both cases for me. Are you 90 years old with specs?
 
L

Lieutenant Scott

On Wed, 14 Nov 2012 21:29:52 -0000, "Lieutenant Scott"
<[email protected]>
wrote in article <op.wnr8n2gzytk5n5@i7-940>...
BTW, you should consider setting the line length on your newsreader to
something shorter, say 72 characters, so that it breaks lines in your
posts at more reasonable length.

Been discussed before. I have no desire to limit my length to a
specific value, it's meant to be auto-wrapping at your end, look up
the "format flowed" RFC.

If you can work out what part of the RFC my newsreader breaks (I
don't know if it's mine or yours that isn't following it correctly)
then let me know and I'll pass it on to the programmers, because
nobody's worked it out yet.

It only seems to upset the lesser known newsreaders like Gravity and
Turnpike, while Agent and the dreaded Outhouse Distress read my posts
ok. It could be that they're less fussy about incorrect formatting,
or it could be that they follow a later RFC, I don't know.

But what makes no sense at all is how ANYTHING my newsreader does
could stop yours from wrapping when it hits the edge of your screen.

Oh, it doesn't upset my reader in the least. When the text hits the
edge of the window, it line wraps. When my reader window is relatively
wide (as it often is for reasons I'll not go into), it makes it harder
to read.
I don't seem to have a problem reading lines [counts] 180 characters
wide, which is what my screen shows. Can your eye not dart back along
something that long?
There is a reason newspapers and other printed media use narrow columns
of text - it is easier to scan. Has nothing to do with eyesight.
It's not easier for me. It's actually annoying having to switch lines every few words in narrow newspaper columns. A scan to the next line is the same amount of effort for me for any length of line.

The reason they have narrow columns is twofold - one because they want to cater for the old folk that read a lot of papers, and two because it's easier to lay out several stories on one page like that.
You asked for the relevant reference from the RFC, I provided it.
Whether or not you understand the reasoning,
I only wanted to know if Opera was doing something technically wrong so I could pass it on to them. I've yet to see this information.
if you choose to ignore it
then you are not being a good "netizen".
Netizen indeed. [rolls eyes]
But you are. I have to adjust my reader window width from the
configuration I prefer if I want your posts to display properly.
Why have your article pane width wider than the width you want to read? Why do you like having a blank white area to the right? Simply set the pane to the width you want to read, for everybody's articles. This will make no difference if the article is the same or narrower than what you want, and will make the wider ones your chosen width.
I'm not going to argue the point any further. The RFC is clear, what
you do with it is certainly your choice but if you choose to flout
convention, netiquette and the RFC then you are just being stubborn.
I'm doing what I consider sensible and I've explained why.
 
W

Wolf K

[snip]

I don't seem to have a problem reading lines [counts] 180 characters
wide, which is what my screen shows. Can your eye not dart back
along something that long?

Sure, but with shorter lines, I can read the entire line with
very little eye movement. This reduces the possibility of losing sync
considerably.

[snip]

Sincerely,

Gene Wirchenko
Lt Scott's comment displays ignorance of ergonomics. I trust it was a
mere momentary lapse.
It displays first hand experience. If you don't like wide lines, then
change your display to suit your eyes. We are not all equal.

I can display your lines and everyone else's at any width I choose.
OK, so you're an outlier.

The ergonomic _facts_ are that in general
a) people read columns of about 30-40 characters faster than lines of
70+ characters;
b) people make fewer reading errors (missed or misinterpreted words)
reading columns;
c) ragged edge columns are even easier to read than right justified columns.

Of course you can choose to do what you want.
 
W

Wolf K

On Thu, 15 Nov 2012 12:32:59 -0000, Zaphod Beeblebrox


It's not easier for me. It's actually annoying having to switch lines
every few words in narrow newspaper columns. A scan to the next line is
the same amount of effort for me for any length of line.

The reason they have narrow columns is twofold - one because they want
to cater for the old folk that read a lot of papers, and two because
it's easier to lay out several stories on one page like that.
Wrong on both counts, but a good illustration of how one draw a
reasonable inference based on insufficient and/or incorrect data.

Printing in columns goes back to before printing: larger books were
almost always written in columns.

Newspaper pages were wider than those of most books, but the composing
sticks used to set the lines of type one character at a time were too
narrow for those wide sheets. So they were printed in columns. Easy to
do, as the pages for most books (8, 12, or 16 at a time) were printed in
columns anyhow. The printed sheet was then folded, and cut to produce a
"gathering" of pages. Several such were combined into a book. Books
larger than octavo (1, 2, or 4 pages to a sheet) were usually printed in
columns for the same reason.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Apart from defragmenting 4
Defragmenting Hard Drive 28
Defragmenting Windows 7 20

Top