It sounds like there are files left over from the previous base version 8.5...

it also looks like you chose to replace teh individual plugins instead of replaceing the entire folder.

I assume you upgraded base IN the plugin folder...
The better method is to

Delete the existing C:\cdinst\REATOGO-240\plugin\DriverPacks.net
(you could just move \DriverPacks.net\BASE to c:\BASE)
Install from any folder that is NOT a plugin (IE C:\dp_base\DPs_BASE.exe)

i think you will find that there are some .inf files @ C:\cdinst\REATOGO-240\plugin\DriverPacks.net\*.inf 
those should not exist with base 8.12. wink

2,852

(5 replies, posted in DriverPack Graphics)

Driverpacks does not redistribute files from MS sources... or any other licensed software smile

If there is a link to freely download it - then we can help you!

I just ran a test with exactly the same setup you used...

either you have a bad source or your burning software is killing you...
did you test it on another machine or in a VM?

Be sure to select the subscribe link below so you get notified when there is a response wink

waht about opening the txtsetup file in notepad or whatever ?

I think it is Excellent! big_smile

2,856

(38 replies, posted in BartPE - UBCD4Win - WinPE)

Yes - Well done !

Very intuitive of you! you have been a PE user for a while wink

Jeff

Welcome to DriverPacks and have a great day!

@EvilBetty... Done. wink

@chipzoller

KTD = Keep The Driver
An out dated method of making drivers available on the machine permanently.
This currently requires over two gig of disk space for drivers that probably will never be used.
And if they were used then they would be out of date.
KTD has been made obsolite by our SAD (Stand Alone Driver) platform

We are still working on a solution for SysPrep... ATM OffLine SysPrep by Galapo is your best option (yes he uses the DriverPacks)... big_smile

are you able to access the file on your disc?

are you able to open it before you burn it?

can we please see your DPs_BASE.log?

done... welcome to the team ... you will find a new forum is visible to you now !

Please use the search feature of our forum....

did you start over... from the beginning

1 copy the original OEM win xp to hdd...

then you have a bad cd... try again...

did you verify the md5 checksum on the mass pack? (changelog for mass from the home page)

Did you try to reslipstream ?

corrupted mass storage pack re-download please

md5 and files sizes are provided on the ChangLog pages to confirm your downloads.
http://driverpacks.net/DriverPacks/download.php?pag=m

Welcome to DriverPacks and thanks for posting!

I edited #3 for you

you still don't seem to understand that the entire section between the first and second reboot is the WinPE stage wink

I would not make it the size of the screen... that is wall paper not a bill board wink

If you google the hwid it will almost always return a description of the device in question.

OR you could use the SAD feature of DriverPacks BASE to install them and then look to see what they are wink

Thanks for retesting and confirming absolutely that we have found the answer.
We are here to help, and I am elated that we were finally able to do so.

I also took a couple of shots at you in frustration,
perhaps we are somewhat alike in that respect. wink
that may also be the reason we finally were able to work together to succeed.

Thank you for your time and effort.
By sharing your situation here in the forum you have helped to make DriverPacks better for everyone.
That makes you part of our team!

Welcome to DriverPacks and I hope we see you again!


PS You can look forward to getting credit for code similar to the following showing up soon wink

SET TAGFILE=\OEM
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%\bin\un7zip.exe" IF EXIST "%%i:%TAGFILE%\DP*.7z" SET CDDRIVE=%%i:&GOTO DPsFound)
Start Echo OK, Who's the joker who hid the DriverPacks? & GOTO OUT
:DPsFound

Sounds great see waht you can do and i will figure out how to "billboard" it wink

know anybody who is good with graphics... wink

2,871

(17 replies, posted in Installation Platforms)

RE "DP must know which files it has updated and altered in txtsetup.sif"

we call that file DriverPack_MassStorage_wnt5_x86-32.ini (it is in the pack) wink

Speaking of cleaning that up...
I wonder what happened to Twig123...
haven't seen much of him lately...
he was doing such a fabulous job in this forum.
I hope everything is OK with him. big_smile

2,873

(6 replies, posted in Universal Imaging)

nope ROE launches the finisher
the finisher does not install drivers...
the finisher adds complimentary programs to already installed drivers.
IE if an ATI driver is installed it will finish by installing the control panel, but only if the driver is already installed smile

Please reread the excellent skinlayers tutorial... especially #10b

too funny this guy has duplicated most of the features of base...
including a finisher and finisher ini and a fake setup and presetup.cmd...

Basicaly he took the driverpacks as an example and wrote something that does the same steps.

also his package includes copywrited software

1 a copy of the windows boot sector...

2 CDIMAGE CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2000.  All rights reserved.

maybe more, I just took a quick look at it...

we do not support Warez... go legit or go home...

Closed... Warez are not supported

2,875

(6 replies, posted in Universal Imaging)

moved from 'mass storage' to the correct forum 'Universal imageing'...

I don't see where you added the DriverPacks mass storage drivers to the sysprep.inf

-bsmd only copys the original windows drivers to sysprep.inf... wink