COPYP2V ERROR

User discussion and information resource forum for the TeraByte OS Deployment Tool Suite.
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

ostapvoip wrote:
> 1. I thought that installing the lsi_sas driver was required, as it was in Windows 7

Not neccesary with Windows 10. It is normally pre-installed. That's why I'm asking why you are installing it.
Thanks for your report.
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

In the second test, I do not install this driver.
But the result is still negative.
Eric, what am I doing wrong?
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

It's the installation of the lsi_sas driver that is making confusion inside the registry. You don't need to install it, it's already in there.
If you install it again, another configuration of the driver is created inside the regsitry (with same structure than the standard one), and references are replaced. The cleaning of drivers detects this new structure and delete it (however, there is a bug in osdtool that deletes more things that it should do in that case - will be corrected).
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

ostapvoip wrote:
> In the second test, I do not install this driver.
> But the result is still negative.
> Eric, what am I doing wrong?
True. In the 2nd test, it was because the stornvme was installed (but it was not needed because it was already there), and due to the bug in osdtool, too many things were removed from the configuration.
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

I will be glad to test the corrected version ;)

Also wanted to ask about using OSDTOOL – Automated Mode.
https://i.vgy.me/2r8dSl.png

1) Can this be used with a filter key?
Example :
InstDrv=lsi_scsi.inf -critical -filter
2) Can this be used for windows 8.1\10?
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

ostapvoip wrote:
> I will be glad to test the corrected version ;)
There: https://www.dropbox.com/s/e1ober9y9itw8 ... l.tbs?dl=0

> Also wanted to ask about using OSDTOOL – Automated Mode.
> https://i.vgy.me/2r8dSl.png
>
> 1) Can this be used with a filter key?
Yes (only for physical drive).

> 2) Can this be used for windows 8.1\10?
Yes. But we are correcting so it won't create confusion in the registry.
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

Thank you very much! I will definitely test.

>Yes. But we are correcting so it won't create confusion in the registry.
Is this already implemented in version OSDTOOL 4.36?

You can give an example .tbs script to get a list storage drivers provided by Windows.
Thanks in advance.
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

ostapvoip wrote:
> Is this already implemented in version OSDTOOL 4.36?
No.

> You can give an example .tbs script to get a list storage drivers provided by Windows.
You can copy/paste the list directly from the UI.
TeraByte Support
Posts: 3035
Joined: Thu May 05, 2011 10:37 pm

Re: COPYP2V ERROR

Post by TeraByte Support »

it should be noted that 1.92 is out and fixes another regression and scripts updated to handle dual installs.
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

> But we are correcting so it won't create confusion in the registry.

Thank.
Please indicate in which version this problem will be solved.

At the moment, more or less normal, but more thorough correction is required.
Post Reply