C contains the XP system.
D contains data
E is empty
I usually need to copy approx 10GB from D to E. I want the data to
be stored on E as unfragmented as possible.
Would running an application on C at the same time somehow mess up
the copy of data from D to E in such a way as to make the data on E
more fragmented?
(Maybe affecting the numbers of simultaneous "streams" of data or
maybe affecting the buffers being used or something like that.)
> I use Windows XP and I have these partitions:
> C contains the XP system.
> D contains data
> E is empty
> I usually need to copy approx 10GB from D to E.
> I want the data to be stored on E as unfragmented as possible.
Why ?
> Would running an application on C at the same time
> somehow mess up the copy of data from D to E in
> such a way as to make the data on E more fragmented?
Nope.
> (Maybe affecting the numbers of simultaneous "streams" of data
> or maybe affecting the buffers being used or something like that.)
Those doent affect fragmentation.
Non of your business, just answer the question or leave.
>> Would running an application on C at the same time
>> somehow mess up the copy of data from D to E in
>> such a way as to make the data on E more fragmented?
>
> Nope.
As helpful as we can expect from Rod.
>>> I use Windows XP and I have these partitions:
>>> C contains the XP system.
>>> D contains data
>>> E is empty
>>> I usually need to copy approx 10GB from D to E.
>>> I want the data to be stored on E as unfragmented as possible.
>> Why ?
> Non of your business,
Wrong, as always.
> just answer the question or leave.
Go and fuck yourself, again.
>>> Would running an application on C at the same time
>>> somehow mess up the copy of data from D to E in
>>> such a way as to make the data on E more fragmented?
>> Nope.
> As helpful as we can expect from Rod.
Just how many of you are there between those ears, child ?
>GT wrote
>> Rod Speed <rod.sp...@gmail.com> wrote
>>> Why ?
>
>> Non of your business,
>
>Wrong, as always.
>
>> just answer the question or leave.
>
>Go and fuck yourself, again.
>
>>>> Would running an application on C at the same time
>>>> somehow mess up the copy of data from D to E in
>>>> such a way as to make the data on E more fragmented?
>
>>> Nope.
>
>> As helpful as we can expect from Rod.
>
>Just how many of you are there between those ears, child ?
>
I want a refund of my purchase price, you didn't include a
wet paper bag this time.
>>>> Why ?
>>> Non of your business,
>> Wrong, as always.
>>> just answer the question or leave.
>> Go and fuck yourself, again.
>>>>> Would running an application on C at the same time
>>>>> somehow mess up the copy of data from D to E in
>>>>> such a way as to make the data on E more fragmented?
>>>> Nope.
>>> As helpful as we can expect from Rod.
>> Just how many of you are there between those ears, child ?
> I want a refund of my purchase price,
You dont qualify, so fuck off.
Now come on Rod, you've got better insults than that - we know you have as
you use them everyday when your insane judgement and advice is challenged!
Knob Speed is hilarious, please don't scare him away. He's almost as
entertaining as Frank Ifield.
Doesn't the OS write systemv olume information to that partition and
perhaps it des that whilst copying data from one partition to another?
>> Fragmenting on E only occurs when more programs try to write to it
>> at the same time, so only when the C program tries to write E at the
>> same time, will fragmentation take place.
>> The time slicing between you and the C progam in itself will not
>> cause fragmentation.
> Doesn't the OS write system volume information to that partition
Yes.
> and perhaps it des that whilst copying data from one partition to another?
Nope, nothing gets written to any partition that isnt being copied to.
And that 'system volume information' doesnt affect fragmentation of files on that volume anyway.
It would only be a matter of discountinous writes, that it
seeks between writing each volume. It still picks up at the
next contiguous block of free space.