Full install, that takes all of 30 seconfs doesn't it?

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"Alex Coleman" <coalie RemoveThis @nomail.com> wrote in message news:96ED84635687531E75@204.153.244.170...
>> In microsoft.public.windowsxp.general Alex Coleman
>> <coalie RemoveThis @nomail.com> wrote:
>>
>>> When I tried version 7 it had the two middle options (out of
>>> four options) for boot optimization grayed out.
>>> So I uninstalled 7 and went back to 6. Maybe those two options
>>> were grayed out because my ProcessIdleTasks was set to OFF.
>>> Could you confirm this happens.
>
>
> On Tue 11 Oct 2005 20:49:05, wrote:
> <news:11ko5ph491paj43@corp.supernews.com>
>>
>> my middle two are greyed out too; interesting...
>> seems maybe "you can't go back..."
>> it's most likely this PD reg setting
>>
>> HKEY_LOCAL_MACHINE\SOFTWARE\Raxco\PerfectDisk\7.0
>> \PDManageLayoutIni=3
>>
>> I didn't experiment further...
>
>
> From what you posted earlier in this thread I gather the key is not
> necessarily the one you list above but this one:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
> CurrentVersion\OptimalLayout
>
> The value of 'EnableAutoLayout' is '1' or '0' depending on what is
> set manually or using either:
>
> TweakUI > General > Optimize Hard Disk When idle.
> CachemanXP > Tweaks > Defragment Hard Disk When Idle
>
> I observe that the reg key change gets made without any rebooting.
>
> Is there any chance you can change your:
> 'EnableAutoLayout' from '0' to '1'
> to see if PerfectDisk v7 permits all four boot optimization options
> rather than just two.
>
> I would appreciate it as it will save me doing a full install of V7
> only to find that I still can't get to those options despite reg key
> settings.
>
> Thank you.

Full install, that takes all of 30 seconfs doesn't it?

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"Alex Coleman" <coalie.RemoveThis@nomail.com> wrote in message news:96ED84635687531E75@204.153.244.170...
>> In microsoft.public.windowsxp.general Alex Coleman
>> <coalie.RemoveThis@nomail.com> wrote:
>>
>>> When I tried version 7 it had the two middle options (out of
>>> four options) for boot optimization grayed out.
>>> So I uninstalled 7 and went back to 6. Maybe those two options
>>> were grayed out because my ProcessIdleTasks was set to OFF.
>>> Could you confirm this happens.
>
>
> On Tue 11 Oct 2005 20:49:05, wrote:
> <news:11ko5ph491paj43@corp.supernews.com>
>>
>> my middle two are greyed out too; interesting...
>> seems maybe "you can't go back..."
>> it's most likely this PD reg setting
>>
>> HKEY_LOCAL_MACHINE\SOFTWARE\Raxco\PerfectDisk\7.0
>> \PDManageLayoutIni=3
>>
>> I didn't experiment further...
>
>
> From what you posted earlier in this thread I gather the key is not
> necessarily the one you list above but this one:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
> CurrentVersion\OptimalLayout
>
> The value of 'EnableAutoLayout' is '1' or '0' depending on what is
> set manually or using either:
>
> TweakUI > General > Optimize Hard Disk When idle.
> CachemanXP > Tweaks > Defragment Hard Disk When Idle
>
> I observe that the reg key change gets made without any rebooting.
>
> Is there any chance you can change your:
> 'EnableAutoLayout' from '0' to '1'
> to see if PerfectDisk v7 permits all four boot optimization options
> rather than just two.
>
> I would appreciate it as it will save me doing a full install of V7
> only to find that I still can't get to those options despite reg key
> settings.
>
> Thank you.

On Wed 12 Oct 2005 15:07:11, David Candy wrote:
<news:uEJEEZzzFHA.2884@TK2MSFTNGP09.phx.gbl>

>
> Full install, that takes all of 30 seconfs doesn't it?
>
>

Hi David. An uninstall and then a manual sweep of the later
version's registry keys takes a little longer than 30 seconds.

Sometimes earlier versions will refuse to re-install if a later
version has been installed and left behind its marker. I had this
with O&O's defrag software.

On Wed 12 Oct 2005 15:07:11, David Candy wrote:
<news:uEJEEZzzFHA.2884@TK2MSFTNGP09.phx.gbl>

>
> Full install, that takes all of 30 seconfs doesn't it?
>
>

Hi David. An uninstall and then a manual sweep of the later
version's registry keys takes a little longer than 30 seconds.

Sometimes earlier versions will refuse to re-install if a later
version has been installed and left behind its marker. I had this
with O&O's defrag software.

frodo DeleteThis @theshire.org wrote:

> [PerfectDisk does] its own version of the prefetch optimize whenever
> you trigger perfect disk to defragment - it does not do any
> "background" or "when idle" defrag in place of defrag c: -b. IMHO it
> does a slightly better job, because it moves the bootup files to the
> front of the disk (the purple files in its display), rather than to
> just any open place as defrag c: -b does. But it only does it for the
> boot partition (the one w/ \windows), and not any others (PD 7 at
> least). So, if you're in the habit of using a diff partition for
> your \Progam Files directory the it won't benefit. You can use defrag
> d: -b for it (d: or whatever its letter).

This isn't true. I run PerfectDisk 7, and when I analyze a non-Windows
drive, I see purple "Boot" files indicated. And I've verified that the
ones so colored are actually used by programs that run during startup.

For example, I use Copernic Desktop Search, but I have it configured to
keep its data on a secondary drive. PerfectDisk (correctly) identifies
Copernic Desktop Search's huge Keywords.ksb file as being part of the
boot process. And not surprisingly, this is because the Keywords.ksb
file is listed in Layout.ini.

Anything listed in Layout.ini will be flagged as "Boot" by PerfectDisk,
and will be optimized, just the same as the files on the boot drive.
But if it's a small file (unlike Keywords.ksb), it won't show up in
PerfectDisk's display. But PerfectDisk will still process it.

You can prove this to yourself by identifying a file in Layout.ini that
is on a non-boot drive, renaming it temporarily, then creating a
same-named file, and filling it with enough data to make it large in
size (100-200 MB or so). Then, after re-analyzing the drive in
PerfectDisk, the file will appear in its display as a "Boot" file,
because it now occupies enough sectors to warrant being colored as such.
You can use the View | "Find File" function in PerfectDisk to ensure
what you see is in fact the correct file.

And, of course, if you let PerfectDisk defrag that drive, the "Boot"
file(s) will be moved to the front.

frodo.RemoveThis-AT-theshire.org wrote:

> [PerfectDisk does] its own version of the prefetch optimize whenever
> you trigger perfect disk to defragment - it does not do any
> "background" or "when idle" defrag in place of defrag c: -b. IMHO it
> does a slightly better job, because it moves the bootup files to the
> front of the disk (the purple files in its display), rather than to
> just any open place as defrag c: -b does. But it only does it for the
> boot partition (the one w/ \windows), and not any others (PD 7 at
> least). So, if you're in the habit of using a diff partition for
> your \Progam Files directory the it won't benefit. You can use defrag
> d: -b for it (d: or whatever its letter).

This isn't true. I run PerfectDisk 7, and when I analyze a non-Windows
drive, I see purple "Boot" files indicated. And I've verified that the
ones so colored are actually used by programs that run during startup.

For example, I use Copernic Desktop Search, but I have it configured to
keep its data on a secondary drive. PerfectDisk (correctly) identifies
Copernic Desktop Search's huge Keywords.ksb file as being part of the
boot process. And not surprisingly, this is because the Keywords.ksb
file is listed in Layout.ini.

Anything listed in Layout.ini will be flagged as "Boot" by PerfectDisk,
and will be optimized, just the same as the files on the boot drive.
But if it's a small file (unlike Keywords.ksb), it won't show up in
PerfectDisk's display. But PerfectDisk will still process it.

You can prove this to yourself by identifying a file in Layout.ini that
is on a non-boot drive, renaming it temporarily, then creating a
same-named file, and filling it with enough data to make it large in
size (100-200 MB or so). Then, after re-analyzing the drive in
PerfectDisk, the file will appear in its display as a "Boot" file,
because it now occupies enough sectors to warrant being colored as such.
You can use the View | "Find File" function in PerfectDisk to ensure
what you see is in fact the correct file.

And, of course, if you let PerfectDisk defrag that drive, the "Boot"
file(s) will be moved to the front.

"R. McCarty" <PcEngWork-NoSpam_.TakeThisOut@mindspring.com> wrote in message
news:ORnOm9L2FHA.3720@TK2MSFTNGP14.phx.gbl...
>I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple) to
> be placed at the beginning of the volume you have to change PDisk's
> Tools, Advanced Configuration to "Let Perfect Disk Manage all the
> Layout.Ini Files", which is not the default setting. On my non-XP disk
> partitions all the Purple (Boot) files are placed at the start of the
> volume.

Same here!

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple) to
be placed at the beginning of the volume you have to change PDisk's
Tools, Advanced Configuration to "Let Perfect Disk Manage all the
Layout.Ini Files", which is not the default setting. On my non-XP disk
partitions all the Purple (Boot) files are placed at the start of the
volume.

<frodo.DeleteThis@theshire.org> wrote in message
news:11lq5ddlfva5pb3@corp.supernews.com...
> In microsoft.public.windowsxp.general null <u0ak51t02.DeleteThis@sneakemail.com>
> wrote:
>> frodo.DeleteThis-AT-theshire.org wrote:
>
>>> [PerfectDisk does] its own version of the prefetch optimize whenever
>>> you trigger perfect disk to defragment - it does not do any
>>> "background" or "when idle" defrag in place of defrag c: -b. IMHO it
>>> does a slightly better job, because it moves the bootup files to the
>>> front of the disk (the purple files in its display), rather than to
>>> just any open place as defrag c: -b does. But it only does it for the
>>> boot partition (the one w/ \windows), and not any others (PD 7 at
>>> least). So, if you're in the habit of using a diff partition for
>>> your \Progam Files directory the it won't benefit. You can use defrag
>>> d: -b for it (d: or whatever its letter).
>
>> This isn't true. I run PerfectDisk 7, and when I analyze a non-Windows
>> drive, I see purple "Boot" files indicated. And I've verified that the
>> ones so colored are actually used by programs that run during startup.
>
> That is true, but you should also notice that it did not move those purple
> files to the front of the volume, as it does for the windows volume.
> Hence my remark.
>

In microsoft.public.windowsxp.general null <u0ak51t02.TakeThisOut@sneakemail.com> wrote:
> frodo.TakeThisOut-AT-theshire.org wrote:

>> [PerfectDisk does] its own version of the prefetch optimize whenever
>> you trigger perfect disk to defragment - it does not do any
>> "background" or "when idle" defrag in place of defrag c: -b. IMHO it
>> does a slightly better job, because it moves the bootup files to the
>> front of the disk (the purple files in its display), rather than to
>> just any open place as defrag c: -b does. But it only does it for the
>> boot partition (the one w/ \windows), and not any others (PD 7 at
>> least). So, if you're in the habit of using a diff partition for
>> your \Progam Files directory the it won't benefit. You can use defrag
>> d: -b for it (d: or whatever its letter).

> This isn't true. I run PerfectDisk 7, and when I analyze a non-Windows
> drive, I see purple "Boot" files indicated. And I've verified that the
> ones so colored are actually used by programs that run during startup.

That is true, but you should also notice that it did not move those purple
files to the front of the volume, as it does for the windows volume.
Hence my remark.

R. McCarty wrote:

> <frodo.RemoveThis@theshire.org> wrote:
>> null wrote:
>>> frodo.RemoveThis-AT-theshire.org wrote:
>>
>>>> [PerfectDisk does] its own version of the prefetch optimize
>>>> <snip> But it only does it for the boot partition (the one
>>>> w/ \windows), and not any others (PD 7 at least). <snip>
>>
>>> This isn't true. I run PerfectDisk 7, and when I analyze a
>>> non-Windows drive, I see purple "Boot" files indicated. And I've
>>> verified that the ones so colored are actually used by programs
>>> that run during startup.
>>
>> That is true, but you should also notice that it did not move those
>> purple files to the front of the volume, as it does for the windows
>> volume. Hence my remark.
>
> I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple)
> to be placed at the beginning of the volume you have to change PDisk's
> Tools, Advanced Configuration to "Let Perfect Disk Manage all the
> Layout.Ini Files", which is not the default setting. On my non-XP disk
> partitions all the Purple (Boot) files are placed at the start of the
> volume.

Same here. I have the same option enabled, and always have. I
overlooked that setting, but it does explain the difference in the
behavior we're noting here.

I wrote to Raxco support some time ago to obtain clarification on this
setting, and the reason it isn't "recommended" is simply because if it
is enabled, defrags can take longer--because PerfectDisk needs to move
more stuff (i.e. "Boot" files) around.

"R. McCarty" <PcEngWork-NoSpam_ RemoveThis @mindspring.com> wrote in message
news:ORnOm9L2FHA.3720@TK2MSFTNGP14.phx.gbl...
>I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple) to
> be placed at the beginning of the volume you have to change PDisk's
> Tools, Advanced Configuration to "Let Perfect Disk Manage all the
> Layout.Ini Files", which is not the default setting. On my non-XP disk
> partitions all the Purple (Boot) files are placed at the start of the
> volume.

Same here!

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

R. McCarty wrote:

> <frodo.TakeThisOut@theshire.org> wrote:
>> null wrote:
>>> frodo.TakeThisOut-AT-theshire.org wrote:
>>
>>>> [PerfectDisk does] its own version of the prefetch optimize
>>>> <snip> But it only does it for the boot partition (the one
>>>> w/ \windows), and not any others (PD 7 at least). <snip>
>>
>>> This isn't true. I run PerfectDisk 7, and when I analyze a
>>> non-Windows drive, I see purple "Boot" files indicated. And I've
>>> verified that the ones so colored are actually used by programs
>>> that run during startup.
>>
>> That is true, but you should also notice that it did not move those
>> purple files to the front of the volume, as it does for the windows
>> volume. Hence my remark.
>
> I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple)
> to be placed at the beginning of the volume you have to change PDisk's
> Tools, Advanced Configuration to "Let Perfect Disk Manage all the
> Layout.Ini Files", which is not the default setting. On my non-XP disk
> partitions all the Purple (Boot) files are placed at the start of the
> volume.

Same here. I have the same option enabled, and always have. I
overlooked that setting, but it does explain the difference in the
behavior we're noting here.

I wrote to Raxco support some time ago to obtain clarification on this
setting, and the reason it isn't "recommended" is simply because if it
is enabled, defrags can take longer--because PerfectDisk needs to move
more stuff (i.e. "Boot" files) around.

In microsoft.public.windowsxp.general null <u0ak51t02 RemoveThis @sneakemail.com> wrote:
> frodo RemoveThis @theshire.org wrote:

>> [PerfectDisk does] its own version of the prefetch optimize whenever
>> you trigger perfect disk to defragment - it does not do any
>> "background" or "when idle" defrag in place of defrag c: -b. IMHO it
>> does a slightly better job, because it moves the bootup files to the
>> front of the disk (the purple files in its display), rather than to
>> just any open place as defrag c: -b does. But it only does it for the
>> boot partition (the one w/ \windows), and not any others (PD 7 at
>> least). So, if you're in the habit of using a diff partition for
>> your \Progam Files directory the it won't benefit. You can use defrag
>> d: -b for it (d: or whatever its letter).

> This isn't true. I run PerfectDisk 7, and when I analyze a non-Windows
> drive, I see purple "Boot" files indicated. And I've verified that the
> ones so colored are actually used by programs that run during startup.

That is true, but you should also notice that it did not move those purple
files to the front of the volume, as it does for the windows volume.
Hence my remark.

I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple) to
be placed at the beginning of the volume you have to change PDisk's
Tools, Advanced Configuration to "Let Perfect Disk Manage all the
Layout.Ini Files", which is not the default setting. On my non-XP disk
partitions all the Purple (Boot) files are placed at the start of the
volume.

<frodo.RemoveThis@theshire.org> wrote in message
news:11lq5ddlfva5pb3@corp.supernews.com...
> In microsoft.public.windowsxp.general null <u0ak51t02.RemoveThis@sneakemail.com>
> wrote:
>> frodo.RemoveThis-AT-theshire.org wrote:
>
>>> [PerfectDisk does] its own version of the prefetch optimize whenever
>>> you trigger perfect disk to defragment - it does not do any
>>> "background" or "when idle" defrag in place of defrag c: -b. IMHO it
>>> does a slightly better job, because it moves the bootup files to the
>>> front of the disk (the purple files in its display), rather than to
>>> just any open place as defrag c: -b does. But it only does it for the
>>> boot partition (the one w/ \windows), and not any others (PD 7 at
>>> least). So, if you're in the habit of using a diff partition for
>>> your \Progam Files directory the it won't benefit. You can use defrag
>>> d: -b for it (d: or whatever its letter).
>
>> This isn't true. I run PerfectDisk 7, and when I analyze a non-Windows
>> drive, I see purple "Boot" files indicated. And I've verified that the
>> ones so colored are actually used by programs that run during startup.
>
> That is true, but you should also notice that it did not move those purple
> files to the front of the volume, as it does for the windows volume.
> Hence my remark.
>

In microsoft.public.windowsxp.perform_maintain R. McCarty <PcEngWork-NoSpam_.TakeThisOut@mindspring.com> wrote:
> I use Perfect Disk 7.0 and for the Boot/App defined modules (Purple) to
> be placed at the beginning of the volume you have to change PDisk's
> Tools, Advanced Configuration to "Let Perfect Disk Manage all the
> Layout.Ini Files", which is not the default setting. On my non-XP disk
> partitions all the Purple (Boot) files are placed at the start of the
> volume.

Mine is set that way, and it doesn't move the purple files to the front
for the non-system volumes. Hum.... I will investigate further...
Thanks for the tip.