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.
COPYP2V ERROR
Re: COPYP2V ERROR
In the second test, I do not install this driver.
But the result is still negative.
Eric, what am I doing wrong?
But the result is still negative.
Eric, what am I doing wrong?
Re: COPYP2V ERROR
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).
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).
Re: COPYP2V ERROR
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.
> 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.
Re: COPYP2V ERROR
I will be glad to test the corrected version ![Wink ;)](./images/smilies/icon_e_wink.gif)
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?
![Wink ;)](./images/smilies/icon_e_wink.gif)
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?
Re: COPYP2V ERROR
ostapvoip wrote:
> I will be glad to test the corrected version![Wink ;)](./images/smilies/icon_e_wink.gif)
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.
> I will be glad to test the corrected version
![Wink ;)](./images/smilies/icon_e_wink.gif)
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.
Re: COPYP2V ERROR
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.
>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.
Re: COPYP2V ERROR
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.
> 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.
-
- Posts: 3625
- Joined: Thu May 05, 2011 10:37 pm
Re: COPYP2V ERROR
it should be noted that 1.92 is out and fixes another regression and scripts updated to handle dual installs.
Re: COPYP2V ERROR
> 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.
Thank.
Please indicate in which version this problem will be solved.
At the moment, more or less normal, but more thorough correction is required.