Hi,
the tutorial may seem badly out of date because the newer DriverPacks BASE has more functions than what is described in there, but it has a lot of information that never got outdated.
I figure it will be revised with new screenshots, and then we will be able to build newer pages about the functionality we have not yet described in the two forms it now has.
(There is a tut in FAQ in DriverPacks fora, the more elaborate form of same tut (which is, incidentally, also result of collaboration by team members.) is linked to in that FAQ and people's signatures. And yes, some dudes leeched to ours and used our work in their blog or site.)
When we update the screenshots, we have to apply KIS.
When I or another Main Team get a collaborator doing the write-ups for the new functions we cannot personally test/explain, we can seamlessly enhance what we have and use a few new links with information stored on a MT's private account (What we have used now proved a safe haven).
As a follow up to your very detailed story, the detail of which made my friends correctly answer you, I will add a "remark" about corrupted file error.
Let us suppose you had "file not found, or, file is corrupted" as title of this topic, and you only detail about file name and give no detail on what you did.
Had you done that, some of us would be inclined to ask more detail of you.
Some would get inclined to look at the filenames and run more tests in virtual machine.
Those that feel they have to run more tests to find the error may have been active on the developing side of this, and for "several" reasons not been able to test ALL variations of what can be done with DriverPacks BASE and DriverPacks.
(I know what that feels like. I know this is the way to burn out.)
You see, there may be versions of OS they did not have a licence to, or had not yet tried in live metal. Or they want to make comparison tests on a operating system service pack they had not yet fully tested all SP variants of, or there is some part of the DriverPacks BASE method they had not tested on all versions of all operating systems.).
Hmmm, I think I just explained how much fun it is to find out wether all permutations were covered while people get to test each new beta and release candidate before we risk a release of DriverPacks BASE and the DriverPacks.
In any case, there are many permutations while testing, and to make this worse than it already is, live metal can have an other result than virtual machine test.
File not found?
In one OS file is found in other OS not, can be a DriverPacks error. But we have also seen that it can be hardware error, and the worst were those few we have seen in server driver files and when it got fixed they kept coming back later on.
(A few of those had to be dropped. We compared ideas about why our hard work got messed up, and realised a few of these server drivers have an inbuilt fixed route to file so "file got mislaid" cannot be worked around.)
File corrupt? We will suggest a memory test and use new brand of media in your burner.
So, let me thank you for the detail, and for not wasting our time.
The answer was 42?
Kind regards, Jaak.
