Topic: FILE NOT FOUND in TXTmode
Dear Gentlebeings,
yesterday we was bughunting and we learned about some peculiarities.
I have the habit of slipstreaming DriverPacks into new copies of source.
When I didn't, it usually was with a newer testfile on the same OS, and I am in the habit of clearing QSC folder.
Now, without explaining all of the things we found out, I will advise all users that they clear QSC cache between slipstream, and that they use source copies that had no previous mass storage slipstreamed into them.
Of course, you can store copies of Nlited/RVM'd source on hard disk and we can call that the "clean source", but I will advise you slipstream DriverPacks into a new copy of that..
What is the issue?
Well, for instance; you have copies of the various sources without DriverPacks on hard disk, and you slipstream XP with QSC ON, and next you slipstream a copy of 2003 with QSC ON. Well, 2003 setup will come up with a file not found during TXTmode.
The file will get found when you slipstream a clean source of 2003 after you clearded QSC cache.
This happens when you do 2000 as second OS as well. If you do not clear QSC cache, then 2000 will halt on file not found. (different file)
It was like chasing ghosts. What we fixed unglued itself?
Anyway, the thing you should remember is that I advise, for the time being, that when you slipstream with QSC ON, that you do so with TXTmode folder removed from QSC folder. AND, that you should NOT slipstream mass storage into a source that was already slipstreamed with another version of Mass storage. Please use a new copy of source.
QSC ON does not add much time for TxTmode, and method one slipstream has a bug when you turn it OFF.
It usually works for you in Method two with QSC OFF.
(I will run a series of tests on M2 with QSC OFF tomorrow.)
I have to thank Jeff for the long sessions in which we discovered this peculiarity.
---------
OK, it is edit time.
The tests with method 2 and QSC OFF worked just fine.
When I started to advise to always turn QSC ON in Method Two, it was because we got reports about failed slipstreams.
When we told them to turn it ON, the user had success.
However, we have now learned that this advice is probably not the best advice.
It is still mandatory that you turn ON QSC in Method ONE.. So you better CLEAN that cache (remove mass/txtmode) when you next do another Operating System.
It is still best paractice to use a clean source. This can already have SP and hotfixes and so on..
When you use another version of mass storage, you had better use a copy of the clean source that has no DriverPacks streamed in.
----------
Jeff is coding DpsBase, and we had many sessions in MSN where we banged heads together.
One of the reasons some people have a messed up install source is that many users were led to believe that Base cleans up previous slipstreams quite nicely.
Well, that is NOT a fact. To the contrary. It left behind files from the old slipstream which can mess up the new slipstream and most often this is undetected because it still works.
The people reporting issues and many (if not all) experienced testers would start fresh when they felt that they needed a clean fresh source, and I assumed all experienced users know that it is not a good idea to repeatedly slipstream different packs to a previously slipstreamed source.
Base is not bad when it is used with prudence.
Mass storage has seen drastic changes, and we all learned.
What I learned yesterday has had me make new test files.
The latest I have was extensively tested in method 2.
(Textmode is same in M2 and M1.. The methods differ in how the drivers are made ready for Windows PnP.)
The Tut in my signature will get updated.
Last edited by Jaak (2008-02-10 11:04:39)
Kind regards, Jaak.
