On Wed, 1 Nov 2006 06:19:03 +1100, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:
>And that indicates that either the shutdown or the boot
>process may well have been what corrupted the MFT, stupid.
That's what I said earlier.
>Pity you stupidly claimed that it wasnt possible to run chkdsk to
>determine whether corruption was occurring during normal ops or
>whether it was occuring during shutdown or boot. YOU WERE WRONG.
I just told you that running chkdsk without an F is useless because it
gives false information. I gave you one example of how it says that
the volume is corrupt yet it wasnt, and one example of how it says the
volume is not corrupt yet it is when I rebooted.
Therefore "it wasnt possible to run chkdsk to determine whether
corruption was occurring during normal ops"
>Lying, as always. I JUST RUBBED YOU NOSE
That's why you deliberately distort what I say. You do not have a
desire to help, you just like "rubbing my nose" into your
misinterpretations of what I say.
I never said you can't run chkdsk other than boot time. I said you
can't run chkdsk with an F to determine whether there is a corrupt
disk when Win2K is running. You need to pay closer attention to what I
say.
>> Next time listen to me.
>No way, you're so stupid that you couldnt even manage to work out how
>to run chkdsk at other than boot time to see if the MFT gets corrupted at
>other than reboot time
I just showed you that running chkdsk other than at boot time will not
tell you if the MFT gets corrupted.
>No wonder you got the bums rush, even they noticed how useless you are.
Once again you do not know what you are talking about.
When I bought the Enermax DynaBacker I asked the head of tech support
whether Directron knew if it would work properly. He said it was a new
product for Directron, so I told him to include a clause in my invoice
that stipulated that I could return it for a full cash refund anytime
within 1 year, which is the normal Directron warranty period.
When I started getting corrupt NTFS volumes with the DynaBacker I
contacted the Product Line Manager (PLM) at Enermax in California, who
is the importer/distributor. He told me to contact the PLM at Enermax
in Taiwan. He also gave me the link to the website of the OEM who
makes the unit, a company also in Taiwan not affiliated with Enermax.
I contacted the PLM at Enermax in Taiwan and she told me she was
involved with the development of the unit. She told me that she was
going to take the information I gave her and fix the problem. In the
meantime I took a look at the OEM's website and saw that it was the
company who developed the unit. The software on the website was
identical to the software that came with the unit. I wrote them twice
but no one responded.
Then after several exchanges of information with the PLM at Enermax
Taiwan she informs me that they are not going to fix anything. That
was the last I heard from her. I called Enermax in California and
talked to the Sales Manager and he told me I could return the unit.
I then called the head of tech support at Directron and he in turn
called Enermax California. Then he called me and advised me to return
the unit for a full cash refund because he found out that Enermax is
thinking about dropping the product. I returned the unit and got a
full refund.
Later I discovered that Directron dropped the unit from its product
offering, that Enermax California also dropped the unit from its
product offering, and that Enermax Taiwan also dropped the unit from
its product offering and that the OEM website disappeared altogether.
So much for getting the bum's rush. No such thing happened.
You have lost all credibility.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
Citizen Bob <spam@uce.gov> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote
>> And that indicates that either the shutdown or the boot
>> process may well have been what corrupted the MFT, stupid.
> That's what I said earlier.
And you had no basis for that claim UNTIL you had your nose rubbed
in the FACT that chkdsk can be run without the F switch to determine
whether the MFT is getting corrupted by other than a reboot.
>> Pity you stupidly claimed that it wasnt possible to run chkdsk to
>> determine whether corruption was occurring during normal ops or
>> whether it was occuring during shutdown or boot. YOU WERE WRONG.
> I just told you that running chkdsk without an
> F is useless because it gives false information.
LIar. And you havent established that it 'gives
false information' when the F switch isnt used.
> I gave you one example of how it says
> that the volume is corrupt yet it wasnt,
Irrelevant to whether its quite adequate to determine whether
you are getting MFT corruption at other than reboot time.
> and one example of how it says the volume
> is not corrupt yet it is when I rebooted.
Doesnt prove that it wasnt the reboot that produced the corruption, fool.
> Therefore "it wasnt possible to run chkdsk to determine
> whether corruption was occurring during normal ops"
Pity that claim is STILL a pig ignorant lie.
>> Lying, as always. I JUST RUBBED YOU NOSE
> That's why you deliberately distort what I say.
Lying, as always.
> You do not have a desire to help,
Have fun explaining how come I listed for you how to
TEST the various possibilitys of what is corrupting the
MFT, particularly with the most important possibility of
that being due to the hardware or your fucked OS install.
AND BOTH OF THOSE TESTS INVOLVE AN ABSOLUTE
MINIMUM OF EFFORT THAT EVEN A BONEHEAD LIKE
YOU SHOULD BE ABLE TO DO WITH LESS EFFORT
THAN EVEN A SINGLE MANUAL RECOVERY OF A
SINGLE INSTANCE OF MFT CORRUPTION YOU SEE.
And if that test shows that its the fucked OS install and
not a hardware problem, how to try a migration of those
apps to XP using the wizard which again would require a
minimal amount of effort to see if that will fix the problem.
> you just like "rubbing my nose" into your misinterpretations of what I say.
Presumably you actually are that stupid/bone headed.
No surprise that you got the bums rush from you last paid employment.
> I never said you can't run chkdsk other than boot time.
Yes you did.
> I said you can't run chkdsk with an F to determine
> whether there is a corrupt disk when Win2K is running.
And you havent even established that claim even
now, you pathetic excuse for a lying bullshit artist.
> You need to pay closer attention to what I say.
Nope, it remains pig ignorant mindless silly shit and lies no
matter how closely attention is paid to it as this pathetic
excuse for bullshit and lies of yours above proves in spades.
>>> Next time listen to me.
>> No way, you're so stupid that you couldnt even manage
>> to work out how to run chkdsk at other than boot time to
>> see if the MFT gets corrupted at other than reboot time
> I just showed you that running chkdsk other than at
> boot time will not tell you if the MFT gets corrupted.
No you didnt, ALL you did is prove to the world that you have
never ever had a fucking clue about anything at all, ever.
Even someone as stupid as you should have noticed by now that
only kony and I are even bothering with you at all. Presumably
everyone else who actually has a clue has decided that you are
such a terminal bone head that you're a complete waste of time.
Looks like even kony has given up on you now too.
>> No wonder you got the bums rush, even they noticed how useless you are.
> Once again you do not know what you are talking about.
Bet I do.
> When I bought the Enermax DynaBacker I asked the head of tech
> support whether Directron knew if it would work properly. He said
> it was a new product for Directron, so I told him to include a clause
> in my invoice that stipulated that I could return it for a full cash refund
> anytime within 1 year, which is the normal Directron warranty period.
> When I started getting corrupt NTFS volumes with the DynaBacker I
> contacted the Product Line Manager (PLM) at Enermax in California,
> who is the importer/distributor. He told me to contact the PLM at
> Enermax in Taiwan. He also gave me the link to the website of the OEM
> who makes the unit, a company also in Taiwan not affiliated with Enermax.
> I contacted the PLM at Enermax in Taiwan and she told me she
> was involved with the development of the unit. She told me that
> she was going to take the information I gave her and fix the problem.
And when she couldnt reproduce the problem, presumably
she decided that the problem must be with your system,
and it turns out that the problem actually is with your system.
> In the meantime I took a look at the OEM's website and saw
> that it was the company who developed the unit. The software
> on the website was identical to the software that came with
> the unit. I wrote them twice but no one responded.
Presumably they realised you are a terminal bonehead right from
the start and filed your crap in the round filing cabinet where it belongs.
> Then after several exchanges of information with the PLM at Enermax
> Taiwan she informs me that they are not going to fix anything. That
> was the last I heard from her. I called Enermax in California and
> talked to the Sales Manager and he told me I could return the unit.
> I then called the head of tech support at Directron and he in turn called
> Enermax California. Then he called me and advised me to return the unit
> for a full cash refund because he found out that Enermax is thinking
> about dropping the product. I returned the unit and got a full refund.
> Later I discovered that Directron dropped the unit from its product
> offering, that Enermax California also dropped the unit from its
> product offering, and that Enermax Taiwan also dropped the unit from
> its product offering and that the OEM website disappeared altogether.
> So much for getting the bum's rush.
I didnt make that comment about that particular fiasco, fool.
> No such thing happened.
Bet it did from your last paid employment.
> You have lost all credibility.
You never ever had a shred of that. Thats likely another reason you got the bums rush.
On Wed, 1 Nov 2006 10:06:31 +1100, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:
>And you had no basis for that claim UNTIL you had your nose rubbed
>in the FACT
That's enough.
You are the most colossal PRICK on the Internet. You think this thread
is for your sick perverted entertainment.
FOAD!
I will not be opening any more of yourposts
FOAD, PRICK!
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
On Tue, 31 Oct 2006 17:38:38 -0800, mhaase-at-springmind.com
<mhaase-at-springmind.com@> wrote:
>Wow! I can't believe you guys are STILL going on with this!
It just ended. I let it go far enough that everyone can see just what
a colossal prick he is.
>Try connecting the drive directly as Rod suggests. This will either
>fix the problem, or it won't.
I have no reason to try that. But, I did find the brackets so I can
mount the disk in a 5 1/4" bay and not have to re-arrange the cable
run. Maybe if I have nothing better to do I will try it. But like all
the rest of the suggestions, except reinstalling everything from
scratch, I do not believe it is going to work. If the removable bay
were the problem, it would be crashing the system, which does not
happen.
>If it DOES NOT, you will get to dance around and sing the
>"I-told-you-so" song.
I don't do silly things like that.
>You started off in this thread talking about how busy you are, but I
>gotta tell you -- if you had used the time that was wasted putting
>together just a few of these back & forth posts to actually DO some of
>the troubleshooting steps suggested, you might have had a fix already.
You still do not understand. I want to find the cause of this problem,
so I can prevent it happening again. If it's a rogue app, I certainly
do not want to install it again.
I mentioned that I ran into an app once that was supposed to run on
Win2K, but it didn't. I contacted the developers and they said it ran
fine on XP, but not Win2K because it was designed for XP and they did
not try to get it to run on Win2K. It should have run on Win2K they
said but there are incompatibilities (presumably with APIs).
My point is that there could be an app I am using that makes a call to
an API that is not quite up to snuff in Win2K/SP4. If so, I want to
know what that app is.
If I have to reinstall from scratch, and I do not know for sure that
an app was causing the problem, then I will be forced to install XP. I
would prefer not to.
>Anyway, that's the last I'll post on this. It seems that some people
>enjoy argiuing just for the sake of arguing , so I'll just stand back
>now & watch the flames.
Rod Speed has a notorous reputation of flaming for his enjoyment. He
likes to "rub people's noses in it". He is a colossal prick, and
everyone know it, except his sockpuppets.
He has a classic Justifiable Inferiority Complex caused by an
Overblown Ego. He imagines he is Mr. Know It All, and when he can't
solve a problem, all he can do is "rub people's nose in it".
His is one of the sickest perverts I have ever met in my 10 years on
Usenet - and I have run into some very sick personalities. He knows
the only solution to his mental illness is suicide but he is also a
narcississtic coward. It's a good thing he is a leftist queer, because
the world would be a much worse place if he were to spread his
screwed up genes.
Like you, that's the last I'll post on this.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
Citizen Bob <spam@uce.gov> wrote
> mhaase-at-springmind.com <mhaase-at-springmind.com@> wrote
>> Wow! I can't believe you guys are STILL going on with this!
> It just ended.
We'll see.
> I let it go far enough that everyone can see just what a colossal prick he is.
In fact all you ever did was prove in spades what a terminal bone head you are.
He noticed and likely so did plenty of others that havent bothered to comment.
>> Try connecting the drive directly as Rod suggests.
>> This will either fix the problem, or it won't.
> I have no reason to try that.
Pity about what you previously said.
> But, I did find the brackets so I can mount the disk in
> a 5 1/4" bay and not have to re-arrange the cable run.
So you have nothing to lose in proving that it isnt a problem with
the removeable drive bay except a minimal amount of time, less
than you piss against the wall every single week kludging around
the corruption of the MFT. In spades with your desperate
attempts to bullshit your way out of your predicament.
> Maybe if I have nothing better to do I will try it.
You dont have anything better to do, clearly no one has shown up
with a magic wand for you to wave to eliminate that MFT corruption.
> But like all the rest of the suggestions, except reinstalling
> everything from scratch, I do not believe it is going to work.
You belief is completely and utterly irrelevant. You're so stupid
that you couldnt even manage to work out how to run chkdsk
without rebooting, and so stupid that you cant even manage to
work out that when you have much SUCH a spectacular fool of
yourself with everyone laughing at your predicament, that the
only thing that makes any sense at all is to keep your stupid trap
shut and hope everyone forgets about it as quickly as possible.
> If the removable bay were the problem, it would be crashing the system,
Wrong. Even someone as stupid as you should be able to find countless
examples of removable drive bays which have caused problem which
dont crash the system, using groups.google, if someone was actually
stupid enough to lend you a seeing eye dog and a white cane.
> which does not happen.
Funny about the BSODs.
>> If it DOES NOT, you will get to dance
>> around and sing the "I-told-you-so" song.
> I don't do silly things like that.
You just did with the chkdsk F switch, liar.
>> You started off in this thread talking about how busy
>> you are, but I gotta tell you -- if you had used the time
>> that was wasted putting together just a few of these back
>> & forth posts to actually DO some of the troubleshooting
>> steps suggested, you might have had a fix already.
> You still do not understand.
Corse he does.
> I want to find the cause of this problem,
> so I can prevent it happening again.
Separate issue entirely to that comment of his.
> If it's a rogue app,
It cant be, you have proven that when you get MFT
corruption when JUST running ImPerfect Disk when you
also got MFT corruption before using ImPerfect Disk.
That means that its either a hardware
problem or a fucked OS install.
There are no other possibilitys, stupid.
> I certainly do not want to install it again.
Pathetic, really.
> I mentioned that I ran into an app once that was supposed to run on
> Win2K, but it didn't. I contacted the developers and they said it ran
> fine on XP, but not Win2K because it was designed for XP and they
> did not try to get it to run on Win2K. It should have run on Win2K
> they said but there are incompatibilities (presumably with APIs).
Irrelevant to your problem.
> My point is that there could be an app I am using that makes
> a call to an API that is not quite up to snuff in Win2K/SP4.
Nope, you have proven that when you get MFT
corruption when JUST running ImPerfect Disk when you
also got MFT corruption before using ImPerfect Disk.
> If so, I want to know what that app is.
There is no such app.
> If I have to reinstall from scratch, and I do not know for sure that
> an app was causing the problem, then I will be forced to install XP.
Nope. You can check for MFT corruption using
ImPerfect Disk after you have installed each app and
so identify which non existent app is the problem.
> I would prefer not to.
More fool you when the XP files and settings transfer wizard
provides and effortless way of avoiding reinstalling all those
apps and its completely trivial to try it on a spare hard drive
and see if you still get the MFT corruption after using that.
And if you dont, it leaves the sort of mindless manual
kludging around the problem you have been stupid
enough to persist with for over a YEAR now, having
to do that at least weekly and to do the cloning at
a higher frequency than that so you dont lose to much
when you have to step back to the previous clone.
>> Anyway, that's the last I'll post on this. It seems that
>> some people enjoy argiuing just for the sake of arguing ,
>> so I'll just stand back now & watch the flames.
> Rod Speed has a notorous reputation of flaming for his enjoyment.
Only with those so stupid that they havent even noticed that
I only ever do that with pathetic excuses for bullshit artists,
pathological liars, and terminal boneheads like you and your ilk.
<reams of your childish attempts at insults that any 2
year old could leave for dead, flushed where it belongs>
Citizen Bob <spam@uce.gov> wrote
> mhaase-at-springmind.com <mhaase-at-springmind.com@> wrote
>> Wow! I can't believe you guys are STILL going on with this!
> It just ended.
We'll see.
> I let it go far enough that everyone can see just what a colossal prick he is.
In fact all you ever did was prove in spades what a terminal bone head you are.
He noticed and likely so did plenty of others that havent bothered to comment.
>> Try connecting the drive directly as Rod suggests.
>> This will either fix the problem, or it won't.
> I have no reason to try that.
Pity about what you previously said.
> But, I did find the brackets so I can mount the disk in
> a 5 1/4" bay and not have to re-arrange the cable run.
So you have nothing to lose in proving that it isnt a problem with
the removeable drive bay except a minimal amount of time, less
than you piss against the wall every single week kludging around
the corruption of the MFT. In spades with your desperate
attempts to bullshit your way out of your predicament.
> Maybe if I have nothing better to do I will try it.
You dont have anything better to do, clearly no one has shown up
with a magic wand for you to wave to eliminate that MFT corruption.
> But like all the rest of the suggestions, except reinstalling
> everything from scratch, I do not believe it is going to work.
You belief is completely and utterly irrelevant. You're so stupid
that you couldnt even manage to work out how to run chkdsk
without rebooting, and so stupid that you cant even manage to
work out that when you have much SUCH a spectacular fool of
yourself with everyone laughing at your predicament, that the
only thing that makes any sense at all is to keep your stupid trap
shut and hope everyone forgets about it as quickly as possible.
> If the removable bay were the problem, it would be crashing the system,
Wrong. Even someone as stupid as you should be able to find countless
examples of removable drive bays which have caused problem which
dont crash the system, using groups.google, if someone was actually
stupid enough to lend you a seeing eye dog and a white cane.
> which does not happen.
Funny about the BSODs.
>> If it DOES NOT, you will get to dance
>> around and sing the "I-told-you-so" song.
> I don't do silly things like that.
You just did with the chkdsk F switch, liar.
>> You started off in this thread talking about how busy
>> you are, but I gotta tell you -- if you had used the time
>> that was wasted putting together just a few of these back
>> & forth posts to actually DO some of the troubleshooting
>> steps suggested, you might have had a fix already.
> You still do not understand.
Corse he does.
> I want to find the cause of this problem,
> so I can prevent it happening again.
Separate issue entirely to that comment of his.
> If it's a rogue app,
It cant be, you have proven that when you get MFT
corruption when JUST running ImPerfect Disk when you
also got MFT corruption before using ImPerfect Disk.
That means that its either a hardware
problem or a fucked OS install.
There are no other possibilitys, stupid.
> I certainly do not want to install it again.
Pathetic, really.
> I mentioned that I ran into an app once that was supposed to run on
> Win2K, but it didn't. I contacted the developers and they said it ran
> fine on XP, but not Win2K because it was designed for XP and they
> did not try to get it to run on Win2K. It should have run on Win2K
> they said but there are incompatibilities (presumably with APIs).
Irrelevant to your problem.
> My point is that there could be an app I am using that makes
> a call to an API that is not quite up to snuff in Win2K/SP4.
Nope, you have proven that when you get MFT
corruption when JUST running ImPerfect Disk when you
also got MFT corruption before using ImPerfect Disk.
> If so, I want to know what that app is.
There is no such app.
> If I have to reinstall from scratch, and I do not know for sure that
> an app was causing the problem, then I will be forced to install XP.
Nope. You can check for MFT corruption using
ImPerfect Disk after you have installed each app and
so identify which non existent app is the problem.
> I would prefer not to.
More fool you when the XP files and settings transfer wizard
provides and effortless way of avoiding reinstalling all those
apps and its completely trivial to try it on a spare hard drive
and see if you still get the MFT corruption after using that.
And if you dont, it leaves the sort of mindless manual
kludging around the problem you have been stupid
enough to persist with for over a YEAR now, having
to do that at least weekly and to do the cloning at
a higher frequency than that so you dont lose to much
when you have to step back to the previous clone.
>> Anyway, that's the last I'll post on this. It seems that
>> some people enjoy argiuing just for the sake of arguing ,
>> so I'll just stand back now & watch the flames.
> Rod Speed has a notorous reputation of flaming for his enjoyment.
Only with those so stupid that they havent even noticed that
I only ever do that with pathetic excuses for bullshit artists,
pathological liars, and terminal boneheads like you and your ilk.
<reams of your childish attempts at insults that any 2
year old could leave for dead, flushed where it belongs>
On Wed, 1 Nov 2006 15:25:53 +1100, "Fred" <fred@fred.com> wrote:
>> It just ended.
>We'll see.
Don't hold your breathe.
>> I let it go far enough that everyone can see just what a colossal prick he is.
>In fact all you ever did was prove in spades what a terminal bone head you are.
Here we go - the parade of the sockpuppets.
>He noticed and likely so did plenty of others that havent bothered to comment.
Plenty of others, eh. More sockpuppets.
Go troll somewhere else.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
On Wed, 1 Nov 2006 15:25:10 +1100, "Fred" <fred@fred.com> wrote:
>>> And you had no basis for that claim UNTIL
>>> you had your nose rubbed in the FACT
>> That's enough.
>You get no say what so ever on that or anything else at all, ever.
I get all the say I want to say.
><reams of your childish attempts at insults that any 2
>year old could leave for dead, flushed where it belongs>
>> I will not be opening any more of yourposts
>You've said that before you silly little pathological liar.
That comment is proof that you are a sockpuppet.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
On Wed, 1 Nov 2006 20:05:13 +1100, "Fred" <fred@fred.com> wrote:
>> Don't hold your breathe.
>Never that stupid, and we can all see that it didnt end, stupid.
Sockpuppet.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
On Wed, 1 Nov 2006 20:07:23 +1100, "Fred" <fred@fred.com> wrote:
>You quite sure you aint one of those rocket scientist pathological liars ?
Sockpuppet.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
On Thu, 2 Nov 2006 05:47:26 +1100, "Fred" <fred@fred.com> wrote:
>> Sockpuppet.
>Boneheaded terminal fuckwit.
Sckpuppet
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
On Thu, 2 Nov 2006 05:48:11 +1100, "Rod Speed"
<rod.speed.aaa@gmail.com> wrote:
>Citizen Bob <spam@uce.gov> wrote
>> Fred <fred@fred.com> wrote
>
>>> You quite sure you aint one of those rocket scientist pathological liars ?
>
>> Sockpuppet.
>
>Boneheaded terminal fuckwit.
<yawn>
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the
world."
--Clarence Darrow
After getting corrupt NTFS volumes a couple times a day, including a
BSOD, I have gone a couple days with nothing going wrong. That's
because I used Perfect Disk to defrag both online and offline. I have
noticed this before. I expect in about 3-5 days I will begin seeing
the lone corruption followed in intensity by more and finally a BSOD
or two before I defrag again and it all stops for about a week.
What does that tell you about the cause of this?
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or pen around what they have, and they fix the law so the fellow on the outside cannot get in. The laws are really organized for the protection of the men who rule the world. They were never organized or enforced to do justice. We have no system for doing justice, not the slightest in the world."
--Clarence Darrow
> After getting corrupt NTFS volumes a couple times a day, including a
> BSOD, I have gone a couple days with nothing going wrong. That's
> because I used Perfect Disk to defrag both online and offline. I have
> noticed this before. I expect in about 3-5 days I will begin seeing
> the lone corruption followed in intensity by more and finally a BSOD
> or two before I defrag again and it all stops for about a week.
> What does that tell you about the cause of this?
Nothing much. Your description is as vague as always, but it looks like its
mostly varying with disk activity which isnt that surprising and not new info.
Doesnt provide any useful information about the two obvious
possibilitys, hardware problem or fucked OS install.
The real test for those two possibilitys has been spelt out endlessly now.
On Thu, 02 Nov 2006 18:38:52 GMT, spam@uce.gov (Citizen Bob) wrote:
>After getting corrupt NTFS volumes a couple times a day, including a
>BSOD, I have gone a couple days with nothing going wrong. That's
>because I used Perfect Disk to defrag both online and offline. I have
>noticed this before. I expect in about 3-5 days I will begin seeing
>the lone corruption followed in intensity by more and finally a BSOD
>or two before I defrag again and it all stops for about a week.
>
>What does that tell you about the cause of this?
I have gone several days without any corruption. I have cycled all
three cloned disks. This is why I do not believe it's the removable
drive bays.
Here's what I did:
1) I changed the pagefile to 512MB/1500MB per Kony's recommendation.
2) I ran PerfectDisk defragment both online and offline. In the past
this has extended the period with no corruption.
3) I have run CHKDSK without the F several times each day.
4) I changed the signature on each clone with Win98SE fdisk/mbr. I
also deleted all the keys in HKLM/System/MountedDevices. Then I
Installed the "new device" when Win2K was rebooted.
That's it. Nothing else is different. I have run the same applications
I always run.
This does not mean that corruption won't occur sometime soon. But for
now there is absolutely no corruption whatsoever.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the world."
--Clarence Darrow
Citizen Bob <spam@uce.gov> wrote
> spam@uce.gov (Citizen Bob) wrote
>> After getting corrupt NTFS volumes a couple times a day, including
>> a BSOD, I have gone a couple days with nothing going wrong. That's
>> because I used Perfect Disk to defrag both online and offline. I have
>> noticed this before. I expect in about 3-5 days I will begin seeing
>> the lone corruption followed in intensity by more and finally a BSOD
>> or two before I defrag again and it all stops for about a week.
>> What does that tell you about the cause of this?
> I have gone several days without any corruption.
No new info, you've had that before.
> I have cycled all three cloned disks. This is why
> I do not believe it's the removable drive bays.
Thats a stupid way to test that possibility.
> Here's what I did:
> 1) I changed the pagefile to 512MB/1500MB per Kony's recommendation.
It wont be that, its already FAR bigger than you
need and wont be what is corrupting the MFT.
> 2) I ran PerfectDisk defragment both online and offline.
> In the past this has extended the period with no corruption.
You have previously claimed that you can get corruption
of the MFT just by running it. You cant have it both ways.
> 3) I have run CHKDSK without the F several times each day.
Presumably you mean that it doesnt report any problems.
Then you have confirmed that the corruption is occuring
at boot or shutdown time, except for the corruption you
claimed you produced by just running PD.
> 4) I changed the signature on each clone with Win98SE fdisk/mbr.
> I also deleted all the keys in HKLM/System/MountedDevices.
> Then I Installed the "new device" when Win2K was rebooted.
> That's it. Nothing else is different. I have
> run the same applications I always run.
We already know that the fault is intermittent.
> This does not mean that corruption won't occur sometime soon.
> But for now there is absolutely no corruption whatsoever.
Since you have gone that long without corruption in the past, that proves nothing.
You have to test intermittent faults more rigorously
than that, because they are intermittent.
You've now wasted FAR more time than it would have taken to
do the two basic tests that would at least distinguish between a
hardware problem and a fucked OS install, running with the drive
directly connected and trying a clean install of XP on a spare
hard drive using the files and settings transfer wizard.
If you find that say the XP install works fine, you dont necessarily
have to use it, you can decide that you have the proof that its a
fucked OS install and put more time into a clean 2K install if you want.
On Mon, 06 Nov 2006 15:20:34 GMT, spam@uce.gov (Citizen Bob) wrote:
>I have gone several days without any corruption. I have cycled all
>three cloned disks. This is why I do not believe it's the removable
>drive bays.
Now it's Nov. 11, and still no corruption NTFS partition.
The only significant change I can think of was making the pagefile
smaller - 512MB/1.5GB.
I have cycled all three removable hard disks, so it is not the
removeable bays causing the problem. At least I avoided that merry
chase.
Why does a larger pagefile cause a corrupt NTFS volume? I still
believe its tied in with those two devices per hard disk partition.
I am a bit surprised that no one has been able to figure out what is
causing two devices to show up for each partition. It sounds like
something to do with mirroring. There is a special kind of mounting
scheme used for mirroring but I forgot its name. Maybe that's what's
going on - the partition is being used in this special way.
--
"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the world."
--Clarence Darrow
Citizen Bob <spam@uce.gov> wrote
> spam@uce.gov (Citizen Bob) wrote
>> I have gone several days without any corruption. I have cycled all three
>> cloned disks. This is why I do not believe it's the removable drive bays.
> Now it's Nov. 11, and still no corruption NTFS partition.
Have you tried repeatedly using PD the way you used to
be able to produce corruption when JUST running that ?
> The only significant change I can think of was
> making the pagefile smaller - 512MB/1.5GB.
Very unlikely to have been due to that and even you should
be able to work out how to prove that now, by putting it back
to what it used to be when you were getting corruption.
> I have cycled all three removable hard disks, so it
> is not the removeable bays causing the problem.
You dont know that either. ALL you know is that is gone away for a week.
Not unusual with a hardware problem.
> At least I avoided that merry chase.
You dont know that either.
> Why does a larger pagefile cause a corrupt NTFS volume?
You dont know that it does and its completely trivial to prove whether its that.
> I still believe its tied in with those two devices per hard disk partition.
Based on absolutely nothing, as always.
ALL you actually know is that those shouldnt be there.
> I am a bit surprised that no one has been able to figure out
> what is causing two devices to show up for each partition.
Hardly surprising if it was what that fucked mirror hardware produced
when hardly anyone ever used that fucked hardware approach.
> It sounds like something to do with mirroring. There is a special kind
> of mounting scheme used for mirroring but I forgot its name. Maybe
> that's what's going on - the partition is being used in this special way.
And your nose was rubbed in how to prove if its that or not.
But you're such a terminal bone head that you wont do the obvious tests.
Re: Corrupt NTFS filesystem 
Linear Mode
