Hello,
We have been successful in creating and downloading BartPe from a server via SDI images.
In addition, we so like the "test all hard drive" function that together, this has creating a minor issue for our BurnIn Test routine.
The SDI image is seen as a hard drive, no problem there but it complains " Not enough free disk space".
Obviously, we like to keep the sdi images as small as possible to reduce download time etc. Also I am looking for a way of not having to produce an additional set of bitcfg files merely to match this load method. In effect the only difference will be drive letter, BartPe always will be X:, whether loaded from CD, Hdd or sdi.
For example, I have approx 6.85Mb free and 1% should only be 68.5K which should be fine. Is there any other reason why this should fail?
Alternatively, is there any way BurnIn Test could detect an sdi image and not include as a "test all drives" item?
Regards,
SteveA
We have been successful in creating and downloading BartPe from a server via SDI images.
In addition, we so like the "test all hard drive" function that together, this has creating a minor issue for our BurnIn Test routine.
The SDI image is seen as a hard drive, no problem there but it complains " Not enough free disk space".
Obviously, we like to keep the sdi images as small as possible to reduce download time etc. Also I am looking for a way of not having to produce an additional set of bitcfg files merely to match this load method. In effect the only difference will be drive letter, BartPe always will be X:, whether loaded from CD, Hdd or sdi.
For example, I have approx 6.85Mb free and 1% should only be 68.5K which should be fine. Is there any other reason why this should fail?
Alternatively, is there any way BurnIn Test could detect an sdi image and not include as a "test all drives" item?
Regards,
SteveA
Comment