PHYLock Error 0007h

[aussieboykie]

I checked the knowledge base article http://www.terabyteunlimited.com/kb/article.php?id=551 but Error 0007h is not covered. I have tried increasing RAM cache to 10240 and Disk cache to 1112. Any advice on where to go from here? If it involves further increasing cache sizes, is there any upper limit on how far it's worth going?

My system is a Lenovo laptop with 8GB RAM running Windows 8. Relevant log file extract follows..

Image for Windows 2.77 (GUI)
Starting ...
imagew64.exe /b /d:w0@0x22 /f:"F:\Partition Images\T410\W8\Backup-w0-0x22-$~YYYY$-$~MM$-$~DD$-$~HHMM$"
PHYLock is waiting for drive writing to stop ...
PHYLock using drive C:
PHYLock Started
PHYLock Using Disk
PHYLock version 10
PHYLock Error 0007h
Backup: Drive 0 (C:) 64Pro Partition (22) 120000 MiB HPFS/NTFS
To: F:\Partition Images\T410\W8\Backup-w0-0x22-2012-12-30-0733.TBI
INFO: Total Sectors:245760000 Total Allocated:128961904
Deleting incomplete or failed backup.
Operation Completed with Error Code 204
PHYLock failed to cache all changes. Please increase the cache size in settings.
Stop

Regards, AB

[TeraByte Support]

Uninstall (don't need to reboot), Install again, Reboot.



"aussieboykie" wrote in message news:4192@public.image...

I checked the knowledge base article

[
http://www.terabyteunlimited.com/kb/article.php?id=551
](http://www.terabyteunlimited.com/kb/article.php?id=551)

but Error 0007h is not covered. I have tried increasing RAM cache to 10240
and Disk cache to 1112. Any advice on where to go from here? If it involves
further increasing cache sizes, is there any upper limit on how far it's
worth going?

My system is a Lenovo laptop with 8GB RAM running Windows 8. Relevant log
file extract follows..

Image for Windows 2.77 (GUI)
Starting ...
imagew64.exe /b /d:w0@0x22 /f:"F:\Partition
Images\T410\W8\Backup-w0-0x22-$~YYYY$-$~MM$-$~DD$-$~HHMM$"
PHYLock is waiting for drive writing to stop ...
PHYLock using drive C:
PHYLock Started
PHYLock Using Disk
PHYLock version 10
PHYLock Error 0007h
Backup: Drive 0 (C:) 64Pro Partition (22) 120000 MiB HPFS/NTFS
To: F:\Partition Images\T410\W8\Backup-w0-0x22-2012-12-30-0733.TBI
INFO: Total Sectors:245760000 Total Allocated:128961904
Deleting incomplete or failed backup.
Operation Completed with Error Code 204
PHYLock failed to cache all changes. Please increase the cache size in
settings.
Stop

Regards, AB

[aussieboykie]

Thanks. Uninstall then re-install did the trick. Is that the recommended approach when a new version comes out?

Regards, AB

[DrTeeth]

On Sun, 30 Dec 2012 13:55:47 PST, just as I was about to take a herb,
aussieboykie disturbed my reverie and wrote:

> Is that the recommended approach when a new version comes out?
Not as far as I am aware. I have been using IfW for nearly 6 years and
have never done that and never had any issues. I do always install
PHYLock just in case an updated one has been slipped in (the
occasional advise to reboot I think tells me it has).
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).

[mjnelson99]

We usually don't know if Phylock has been updated so it is
probably safer to just go ahead and reinstall it with new
versions of IFW.

I know I did that with 2.77
Mary

On 12/30/2012 4:29 PM, DrTeeth wrote:
> On Sun, 30 Dec 2012 13:55:47 PST, just as I was about to take a herb,
> aussieboykie disturbed my reverie and wrote:
>
>> Is that the recommended approach when a new version comes out?
> Not as far as I am aware. I have been using IfW for nearly 6 years and
> have never done that and never had any issues. I do always install
> PHYLock just in case an updated one has been slipped in (the
> occasional advise to reboot I think tells me it has).
> --
>
> Cheers
>
> DrT
> ______________________________
> We may not be able to prevent the stormy times in
> our lives; but we can always choose whether or not
> to dance in the puddles (Jewish proverb).
>
>

[TeraByte Support]

if you do some type of major windows upgrade or update it can reorder the
drivers which causes an issue, so normally, no.

"aussieboykie" wrote in message news:4212@public.image...

Thanks. Uninstall then re-install did the trick. Is that the recommended
approach when a new version comes out?

Regards, AB

[aussieboykie]

I had recently installed a Windows 7 to Windows 8 upgrade. From what you are saying, that would have been the trigger. Once again, thanks for the quick and accurate diagnosis.

Regards, AB