box killing drives?

[Arno Wagner]

It doesnt work like that with informal communications like
newsgroup posts when talking about room temp, as he was.

It does work like this with everybody that wants to be understood
in an international context and not be sitting on his/her own,
historically defined, island.

In other words, an educated person sticks to the international
standards when talking to people that may have another local frame of
reference, e.g. in an international forum like this. One of these
standards is SI. Another is that you allways give the units anyways, as
redudnancy. I learned these things in school. Did you not?

If you cannot do that, than you are not a modern, educated person and
you should correct that problem.

If you are unwilling to do that, then you are arrogant and potentially
not worth talking to.

Arno

 

[123]

It does work like this with everybody that wants to
be understood in an international context and not be
sitting on his/her own, historically defined, island.

Then there's the real world with informal communication...

In other words, an educated person sticks to the international
standards when talking to people that may have another local
frame of reference, e.g. in an international forum like this.

Pity about the real world with informal communication...

One of these standards is SI. Another is that you
allways give the units anyways, as redudnancy.

Pity about the real world with informal communication...

I learned these things in school. Did you not?

You're confusing formal and informal communication.

If you cannot do that, than you are not a modern,
educated person and you should correct that problem.

Pity about the real world with informal communication...

If you are unwilling to do that, then you are
arrogant and potentially not worth talking to.

You're always welcome to do whatever you like in that regard.

And anyone with a clue realises the difference
between formal and informal communication too.

 

[alfredeneumann]

Ok, here is what I've learned thus far.

I found a few MS programs in the startup config which I removed; including
a rather klunky version of Kaspersky and will use them on demand. This speeded
things up, but did not solve the problem. On some directories when moving them
to either another disk or same disk it takes many seconds for even a small
directory, up to 10 seconds for the move; on others it works as it should-fast.
I can only think this must have something to do with their relative locations
on the drives. This is all happening under win98 explorer windows; with nothing
else running.

Re Rod's recommendation I ran memtest-no errors in memory. Below are some specs
from Everest (a very good program thus far): (BTW, does memtest just keep running
without a summary at end?)

CPU Type Intel Pentium IIIE, 800 MHz (8 x 100)

BIOS Type Phoenix
System BIOS Date 03/22/00 Video BIOS Date 03/18/99

Motherboard Name Intel Seattle II SE440BX-2
Memory Benchmarks:

PIII-E 800 MHz Intel Seattle II SE440BX-2 i440BX
PC100 SDRAM 513 MB/s READ

Celeron 900 MHz MSI 815EP Pro i815EP
PC100 SDRAM 180 MB/s WRITE

PIII-E 800 MHz Intel Seattle II SE440BX-2 i440BX
PC100 SDRAM 2-2-2-? 120.7 ns


[ WDC WD Drive 0 (20GB)) ]

01 Raw Read Error Rate 51 200 200 0 OK:
Value is normal
03 Spin Up Time 0 101 99 4000 OK:
Always passing
04 Start/Stop Count 40 98 98 2059 OK:
Value is normal
05 Reallocated Sector Count 112 200 200 0 OK:
Value is normal
09 Power-On Time Count 0 83 83 12733 OK:
Always passing
0A Spin Retry Count 51 100 100 0 OK:
Value is normal
0B Calibration Retry Count 51 100 100 0 OK:
Value is normal
0C Power Cycle Count 0 99 99 1129 OK:
Always passing
C4 Reallocation Event Count 0 200 200 0 OK:
Always passing
C5 Current Pending Sector Count 0 200 200 0 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 200 200 0 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK:
Always passing
C8 Write Error Rate 51 200 200 0 OK:
Value is normal

[ WDC -Drive 1 8GB ]

01 Raw Read Error Rate 51 200 200 0 OK:
Value is normal
04 Start/Stop Count 40 100 100 609 OK:
Value is normal
05 Reallocated Sector Count 1 108 108 184 OK:
Value is normal
09 Power-On Time Count 0 88 88 9053 OK:
Always passing
0A Spin Retry Count 51 100 100 0 OK:
Value is normal
0B Calibration Retry Count 51 100 100 0 OK:
Value is normal
0C Power Cycle Count 0 100 100 520 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 1 1 293 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK:
Always passing
C8 Write Error Rate 51 113 111 296 OK:
Value is normal

Also have SMART data which reports ok, if needed. Since I am pretty much a
novice in interpreting this information, possibly there are those in this group
that can give me a clue as to why this system takes so long to move directories,
independent of their size, but maybe not of their location? Along this line
of thinking can anyone advise as to the flow steps taken when copying a directory
to a new location, either same drive and/or different drive? IOW, how does
it go? OS-CPU-Memory-Drv0-Os-etc-etc? Maybe if I understood what components
are involved and their order I could figure out what is wrong with this system.
I also have other info from Everest if there is anything relevant I haven't
mentioned.

 

[Rod Speed]

Ok, here is what I've learned thus far.

I found a few MS programs in the startup config which I removed;
including
a rather klunky version of Kaspersky and will use them on demand.
This speeded things up, but did not solve the problem. On some
directories when moving them to either another disk or same disk it
takes many seconds for even a small directory, up to 10 seconds for
the move; on others it works as it should-fast. I can only think this
must have something to do with their relative locations
on the drives. This is all happening under win98 explorer windows;
with nothing else running.

Re Rod's recommendation I ran memtest-no errors in memory.
Below are some specs from Everest (a very good program thus far):

Yeah, tho it can be a tad strange with the cpu temp on some systems.

(BTW, does memtest just keep running without a summary at end?)

Yep, only reports problems when it finds any.

CPU Type Intel Pentium IIIE, 800 MHz (8 x 100)

BIOS Type Phoenix
System BIOS Date 03/22/00 Video BIOS Date
03/18/99

Motherboard Name Intel Seattle II
SE440BX-2
Memory Benchmarks:

PIII-E 800 MHz Intel Seattle II SE440BX-2 i440BX
PC100 SDRAM 513 MB/s READ

Celeron 900 MHz MSI 815EP Pro i815EP
PC100 SDRAM 180 MB/s WRITE

PIII-E 800 MHz Intel Seattle II SE440BX-2 i440BX
PC100 SDRAM 2-2-2-? 120.7 ns


[ WDC WD Drive 0 (20GB)) ]

01 Raw Read Error Rate 51 200 200 0
OK:
Value is normal
03 Spin Up Time 0 101 99 4000
OK: Always passing
04 Start/Stop Count 40 98 98 2059
OK:
Value is normal
05 Reallocated Sector Count 112 200 200 0
OK:
Value is normal
09 Power-On Time Count 0 83 83 12733
OK: Always passing
0A Spin Retry Count 51 100 100 0
OK:
Value is normal
0B Calibration Retry Count 51 100 100 0
OK:
Value is normal
0C Power Cycle Count 0 99 99 1129
OK: Always passing
C4 Reallocation Event Count 0 200 200 0
OK: Always passing
C5 Current Pending Sector Count 0 200 200 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 200 200 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0
OK: Always passing
C8 Write Error Rate 51 200 200 0
OK:
Value is normal

[ WDC -Drive 1 8GB ]

01 Raw Read Error Rate 51 200 200 0
OK:
Value is normal
04 Start/Stop Count 40 100 100 609
OK:
Value is normal
05 Reallocated Sector Count 1 108 108 184
OK:
Value is normal
09 Power-On Time Count 0 88 88 9053
OK: Always passing
0A Spin Retry Count 51 100 100 0
OK:
Value is normal
0B Calibration Retry Count 51 100 100 0
OK:
Value is normal
0C Power Cycle Count 0 100 100 520
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 1 1 293

Thats a bit high for my taste.

OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0
OK: Always passing
C8 Write Error Rate 51 113 111 296

Thats a bit high for my taste.

OK:
Value is normal

Also have SMART data which reports ok, if needed. Since I am pretty
much a novice in interpreting this information, possibly there are
those in this group that can give me a clue as to why this system
takes so long to move directories, independent of their size, but
maybe not of their location?

Yes, the ones I commented on could be the problem
previously, those are much too high for my taste and
it would be interesting to monitor the C6 293 number
over time and see if it increases.

The OK is what the drive reports, not what Everest decides for itself.

Along this line of thinking can anyone advise as to the flow
steps taken when copying a directory to a new location,
either same drive and/or different drive? IOW, how does
it go? OS-CPU-Memory-Drv0-Os-etc-etc?

The data goes from the source drive to memory to the destination drive.

Maybe if I understood what components are involved and
their order I could figure out what is wrong with this system.

I'd use the drive in a completely different system, not
running Win98 and see if you get any odd effect there.

Looks like it may well just be quirks of Win98 and at least one of the
ribbon cables is flakey and varys when its moved mechanically.

I also have other info from Everest if there
is anything relevant I haven't mentioned.

Nar, what you quoted is fine.

 

[J. Clarke]

It does work like this with everybody that wants to be understood
in an international context and not be sitting on his/her own,
historically defined, island.

In other words, an educated person sticks to the international
standards when talking to people that may have another local frame of
reference, e.g. in an international forum like this. One of these
standards is SI. Another is that you allways give the units anyways, as
redudnancy. I learned these things in school. Did you not?

If you cannot do that, than you are not a modern, educated person and
you should correct that problem.

If you are unwilling to do that, then you are arrogant and potentially
not worth talking to.

Said Saddam to the shrub.

While I agree that as a matter of courtesy and common sense when there is
possibility of confusion in the units one should state what system one is
using, however it does not strike me as a matter to be worthy of getting
one's knickers in a twist.