yes if you want to be able to install TO the array it must be created first by the hardware (bios)...
Not all controllers support this in the firmware.

you didn't have to unstick it...
i was just saying it is deserving of so much more !

sorry what i said did not translate well!

the entries in mass storage INI are for txtmode only...
and txtmode does not use the infs... so waht they are named is not relevant

yes you can install to an array...
as long as you can set up the array in the PC's hardware setup

But we all knew nothing at one point... smile

your catching up wink

NO!

Use the provided host!
- that is why we provide it!

Yes the empty DriverPacks folder on your HDD was getting found first...

and you were being told there was nothing to extract (because there were no DriverPacks files in that folder)

new base uses the first folder if finds
old base uses the last folder it finds...

Solved! User error...

2,883

(15 replies, posted in Hardware)

yeah you missed the target they go into the subfolder named DriverPacks wink

yes base extracts them if needed...

2,884

(15 replies, posted in Hardware)

I am going to guess you extracted them... and you were not supposed to
or you did not put them in the DriverPacks folder in the same location as DriverPacks BASE

LOL... it IS a tag folder... good point

but that does not cure either issue sad

I am so glad that we are now helping each other... that is the spirit of what we are about.

did you run a test after you found the stray OEM folder?
Was the E:\OEM\ folder missing the DriverPacks? ... big_smile tongue (that would definitely cause this issue)

presetup would find the folder on E:\OEM\ before finding the OEM folder on your DVD F:\OEM\
if the E:\OEM\ folder contained no packs then that would generate your "no files to extract" error every time...

That seems like the most reasonable explanation to date...

Card reader issues are more commonly reported than this issue...
I must include the exit for the loop to address the more common issue...

therefore the line needs to be written so it will exit when the source is found...

I want to fix both issues... your feedback is the single most important part of me achieving that goal.

Thank you for taking the time to try different things and reporting your results
this takes time and effort on your part, I recognize and appreciate this effort.

I will consider some more options and report back... (i hope you used the "subscribe to this topic" button below wink)

Do you have a Folder named OEM on any of your HDDs?... hmm
IE C:\OEM or D:\OEM

Yeah he said they get copied and renamed so he put them in the 3rd party DriverPack folder...

Can you tell us more specificaly what device was not installed and it's hwid's (SOP)

2,889

(15 replies, posted in Hardware)

Um... you are going to have problems

adding DriverPacks HAS to be the last step. If you added drivers then added sp3 you now have garbage... sorry

please read the tutorial (in my signature)

Welcome to DriverPacks and thanks for the kind words!

I thought about that too... if you were useing his PE method you could just backup the data while your there wink

PS Helmi i think you missed the boat on this one...
This should not only be stickied IMHO
- it's final version should be moved to the FAQ forum
- this should not be forgotten if/when we add attended installation support.

Only one suggestion...

you incorrectly refer to the WinPE phase of setup as GUI portion.

the three stages are Txt, WinPE, and GUI. GUI mode is the final stage after the second reboot.

WinPE (Windows Preinstallation Environment) is the stage after txt mode reboots... and is when presetup.cmd runs wink
(BartPE was developed based on this stage of setup)

But i knew what you meant big_smile

Make that two ... sorry!

this is a variation of a standard "parallel installation"  http://support.microsoft.com/kb/316941 (method 4)
(you refer to this as leave filesystem intact - which is descriptive but not accurate technically)
That would be a good thing to point out at the very beginning
people who are savvy will have the general idea already in their head from the beginning  wink 
Including the keyword will also make your instructions findable to people who might use the search feature. wink big_smile
Changing the title is probably not necessary but i think saying
How To use DriverPacks when doing a parallel installation (without the mess!)
Would be helpful for finding your info and it's much more descriptive / technically accurate terminology!



Oh... and - WOW! Excellent Job!

Welcome to DriverPacks and we're delighted you posted
I second the opinion of your first post
I have not seen a better one than this!

It does help...

did you try (as i suggested above) putting the SATA 1 and SATA 2 HDD's on two different controllers?
Since the drives do not match in speed this can cause timing issues... and may reduce performance also.

Unneeded suggestions removed....

WAIT!!! I lost my focus in the confusion above...     I said this before too...
(wake up Jeff...)
"un7zip is in the same location as the packs... it can find the program but not the packs... hmmm..."

That line CAN NOT BE the problem... if it was then it would not find UN7ZIP   (DUH...)

BRB

One other line was changed (to try to improve speed) change this line

Start /wait /realtime /separate "" "%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\

to

%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\

That has to be it. It is the only other difference between the two versions... wink
I could revert this line in the code. I have had no feedback that it actually does speed up the extraction.

PS it may be that it only fails on /realtime. Changing /realtime to /high probably will work too... not sure.

Start /wait /high /separate "" "%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\

perhaps un7zip is unable to handle the unbridled power of an AMD x64 in real time wink tongue

2,893

(4 replies, posted in Translations Team)

being as the translators can not put files on the server that means i must do still update the files manually...
(like any of our other packs)
Plus it would require new pages on the site and code in base itself.

Since this is true is it much easier for me to just add them and release a newer version of base wink
and i only have to update two lines (version number) on the existing web page wink

So it would be a lot of work to do this way and it is almost no work at all to do it as we are now...

However a link to the bug tracker might be cool...
that way a user could get the update themselves, if one exists..

It is quite easy for me to release a new version of base... and i will do a dlanguage only update... like i did with 8.12.2

Keep up the brainstorming... I love it!

Thanks again for everything you do!

2,894

(17 replies, posted in Installation Platforms)

i have not tried fly a kites version... IDK
it seemed like it was also an i386 folder to target from your descriptiion.

I would have to build one to be of more help... if i have a chance i will...
but someone may just show up with the answer first wink

His issue has solely to do with his machine not parsing that single multi-statement line correctly

I am guessing it read SET CDDRIVE=%%i:& GOTO DPsFound
and then set CDDRIVE to something like "D:& GOTO DPsFound" instead of setting it to "D:"

By enclosing the two statements in brackets and putting a CRLF instead of using an & sign as a separator I will get the same result, it just takes up an extra line and a few extra bytes in the file for no good reason whatsoever.

alternately i might have tried SET CDDRIVE=%%i:&& GOTO DPsFound

for some reason the line is not being parsed correctly on his platform...
could be the AMD processor, RAM or the ODD (resetting BIOS defaults is a valid suggestion lewxam)
I have seen even stranger things than this caused by a video card with RAM issues.

I don't think it is the HDD     BUT...
He did say it works if he uses an IDE drive...  That is the best clue we have     
I apply scientific parsimony here
If there are a number of explanations for observed phenomena, the simplest explanation is preferred.

Something with the HDD... perhaps a caching issue

if this were an Intel box i would suggest flashing the BIOS (which can update the microcode on the CPU too)

There just is not enough info provided to draw any kind of a valid conclusion,
and i don't expect anything to be voluteered,
It's like pulling teeth to get simple direct questions answered.
the questions he did answer, like the error message, he was not even able to copy into his post correctly.
So we may never know why his PC Fails to process a line that millions of other computers have no issue with...
my guess is he built it himself. wink

there was some issues with card readers and there needed to be an exit to the loop.
When a empty card reader is encountered the script will hang...
the change prevents this from happening as long as the ODD is found before the card reader.

besides it makes sense to stop searching when you have found what your looking for wink
(or, why is it that things are always in the last place you look, well who keeps looking after thay have found what the were searching for wink)

here is the thread that prompted that change
http://forum.driverpacks.net/viewtopic.php?id=2923

try this please (we are getting close now)

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" (SET CDDRIVE=%%i:
 GOTO DPsFound)
:DPsFound

That should do it...
But... I just don't see why this one machine alone would fail on this line when it works fine for all others...
It doesn't really matter i guess
if this fixes it let me know and i will update the code in the next release.

Like I said...  "I will also add code to save someone else from your issue, if it is possible."
and it would seem that it is possible...

But I am totally at a loss to understand why this particular machine is the only one affected...  hmmm

it did not report

"\OEM\" folder not found. all drive letters were searched

hmmm

try...

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:& GOTO DPsFound
start /wait Echo "\OEM\" folder not found. all drive letters were searched.
:DPsFound
start /wait dir %CDDRIVE%\OEM\.

and tell me if it lists the contents of the OEM folder on the Disc

Please verify that the ODD is correctly jumpered and cabled...
if it is alone on the IDE channel it should be jumpered as master
and at the end of the cable (not in the middle)
if it is jumpered as 'cable select' move it to the 'master' position.
or try a new cable and then a different ODD ...

try overwiting the un7zip.exe that was installed with the 8.12 with the un7zip.exe that came with base 8.05
(they are not the same) What language are you installing? I assume english but assuming is not good wink

2,898

(17 replies, posted in Installation Platforms)

you should also slipstream the third folder set... prar

dont do it manualy

Better late than never! thanks a million!

inappropriate answers or suggestions and sometimes off topic posts, are removed by our resident gremlins

His suggestion was well intentioned but it was misleading because it was incomplete
he suggested a workaround that would need to be repeated and must be done in a certain order
He did not offer those instructions or point out the down side
(fixing it for one user and only for one source)

the rest of us wish to resolve the problem permanently and for everyone.

wink