3,201

(4 replies, posted in Other)

wow gigabyte with intel and a 8600GTS

that is very nice hardware sir...
GigaByte MBs are rock solid and GB is pleasant to deal with if the need arises.

my guess is fake setup may be the cause of this issue.
IDK why it only shows up on your rig though...
have you tried reseting BIOS settings to default (or clear CMOS jumper)
they allow you to tweak almost everything in the bios
some user settings can adversely affect your experience.
some of which you have to hit ctrl f1 to even view...

I agree that the changed

Addreg=Inst.AddReg

is the issue - we need to get that fixed!

updating OP's title

Galapo wrote:

Lancelot, what happens if you modify DP JRAID_I.inf [JM] section to that of the OEM [JM] section given above?

I am quite certain that fixes it... let's wait and see

Look,
This forum ( Feedback and Support ) is for Feedback and support of DriverPacks...
  Not only are you not useing DriverPacks you are not useing it in a supported manner...
all that aside... we don't troubleshoot code for noobs...

HOWEVER: Since it (on the surface) seems like such a Blatant and Obvious mistake here you go...

you wrote
SET DRV=%SystemDrive%\Drivers
.\7za.exe x -y -aoa -o"%SystemDrive%\Drivers" ".\Drivers.7z"
)


the Syntax is
7z [source] [destination]
not
7z [destination] [source]


so you should have written
IF EXIST Drivers.7z (
SET DRV=%SystemDrive%\Drivers
.\7z.exe -y -aoa ".\Drivers.7z" -o"%SystemDrive%\Drivers"
)

Let us know if you get it to work wink

IDK if we can help since this is a little off topic,
but your welcome to ask...
and i know we would love to hear that you got it to work

jeff

Moved to "Other"

PS that artical is over 4 years old... and much has happened since then...

take a look in our FAQ about SAD (To be renamed SoFI)
I belive SAD created with M2 will be a better solution for you.
SAD still has a few glitches we are ironing out but you can check it out by clicking on the link on our homepage
http://driverpacks.net
it is the second news item on the page

So it would seem making the BT drivers ala carte is the best thing...

That seems very doable
- each set
- or each individual driver (if neccessary)

in multiple packs. In this way a user cold select just the one or more packs they need.

Excellent idea!

Please let us know!

3,206

(18 replies, posted in Other)

so if you would have taken my advise from my first response above...
"
DriverPacks works (nearly) every time... and doesn't stop for user input at all...

the best thing for you to do is to use DriverPacks "disc" method to integrate your drivers into your source.
"

we could have resolved this the first day you posted? ... wink big_smile LOL

Glad you finaly got there - and have now discovered why we get a million downloads a month.

And why all these intelligent guys want to write addons for our software...
remember the addons are not supported - we simply enjoy haveing quality people share thier ideas.

perhaps you have learned something -
always try something out right out of the box
before you rip it apart to see how it ticks !

do i need fbwf to make DIPE function correctly?

I use 2k3 for my source does that matter? or is this XP only?

(I only build PE useing a 2k3 source)

UBCD is a dos based tool i doubt you did that wink I am almost positive you used UBCD4Win

(UBCD and UBCD4Win are two totally different projects!) tongue wink big_smile

i think i understand teh question....

Base is designed to work as a plugin once you have used base to add your plugin to bartpe
(The UBCD4Win has team has already added DriverPacks BASE for you, in advance, so this step is done right out of the box)
IF you have a non UBCD4Win BartPE NBD jsut run base and point it at the plugin folder of BartPE...
then you will have exactly the same experience as with UBCD4Win.

Once the plugin is installed by DriverPacks BASE you can update the packs simply by adding them to the
\BartPE\plugin\DriverPacks.net\BASE\DriverPacks
folder and then hitting the configure button in PEbuilder (from the plugins page)

if you want to update the existing Base program simply install base (outside of the PE folder structure)
run base selecting the bartpe platform and the proper location to create the updated plugin
\BartPE\plugin\   folder
and hit the slipstream button this will delete the existing plugin and create a new one ready to go!

the link is in the second news artical on the homepage wink

however there is a newer version out now... (released today)
http://driverpacks.sytes.net/driverpack … 1102RC.exe
this is a release candidate... please report good or bad results!!! TIA

Welcome and thanks for the excellent questions...

I used UBCD4Win... that should work, yes?

I was right the HWIDs did yeild the culprit...

Nvidia... Man i wish those guys would learn to write a driver... jeesh

try the nightly mass and DriverPack Graphics A see if that is any better
http://driverpacks.sytes.net/driverpack … 32_810F.7z
http://driverpacks.sytes.net/driverpack … _810n23.7z

SAD - Stand Alone Drivers (to be renamed SoFI - Software First Installer)

Because acronis has many shortcomings that Ghost does not have... most people use Ghost wink

almost nobody uses acronis - perhaps that is a clue... wink

Look at the SoFI feature of base (I am changeing the name from SAD (Stand Alone Drivers ))
it is featured in the FAQ and the home page... That should give you what your looking for.

as i said i tried it in vmware and it reported failure

Description of storage media X: is not possable (X: is the CD / ISO)

Lets see if i get it...

you can add drivers on the fly without rebuilding or increasing the size of the original ISO image?

If i am correct this is indeed a great tool!

I am sorry

i am still trying to figure out what it is you are trying to do ...

my bad... can you help me to understand, because i am still lost wink

This is way off topic... and posted in the wrong forum...

moved to BartPE...

Um... no i don't really know why his program doesn't work...

ours does work so why make it any harder than that.
the entire mass storage pack is 14 megabytes - how much space do you really hope to save?

the DriverPacks BartPE plugin works excellent and supports all mass storage controllers.
Why in the world would you want to reinvent the wheel?
to save ten meg? wink
Or just because you have nothing better to do? big_smile

edit...

as i look at this more it looks a lot like Galepos "Off Line SysPrep Tool"
Except i belive your app pulls drivers from a target machine
Galepos injects drivers to a target machine

it is a little lacking in PE function it should have a help when help is clicked in pebuilder and teh config button should respond with a dialog too wink I also saw no help files to read (google translator is not excellent  but it would have given me a clue)

edit...

Question... What is the difference between
the OEM Jmicron driver - that works and
the DriverPacks driver - that won't work
?

Edit...

I tried to run the tool in vmware and it fails with -
Description of storage media X: is not possable (X: is the CD / ISO)

so it passes textmode and reboots into winpe (gui setup) runs fine until shortly after network installation?

hmmm.... hwids may yeild a clue, may we please see them?

the log looks normal... although i think SoFI will make KTD obsolete wink

There were major problems with multiple bluetooth in one pack - there is a post about it around here somewhere...

it may be best to have seperate packs for BT - if you can get them to work together great! but i rmember that there was an issue when this was tried before...

Good news! 

Glad to be of service!

Yes i think you missed something.... wink tongue big_smile

RE: "why wouldn't you guys want to somehow work together so you could use a single .7z file and repurpose some of your efforts?"

UBCD4Win   USES  DriverPacks.net   as their official plugin! wink
so you get DriverPacks (DriverPacks.net) with your UBCD4Win download... then you get your update packs (.7z) here... big_smile
I could not have created the BartPE Plugin without the dedicated and readily available help provided by the UBCD4Win team. We worked together tirelessly to create the mass storage plugin.
Why wouldn't we?... Well that is exactly what we did!

I am suggesting to you that you do what I would do if I had a BartPE question...
I would ask the UBCD4Win team wink - those guys rock!

If you need help specificaly with the DriverPacks plugin then i am the man!
I have learned my lessons well in this niche of BartPE...
the rest of it I'm learning just like you


If you are brave... you can test the RC base that allows you to try to build the other packs as plugins too...

Jeff smile

Questions?


PS
RE:how else would you use the driver packs now, if you wanted to use them? tongue
our original target was Disc based Unattended OS installation...
and we are getting about a million downloads a month just based on that - but we're still growing wink lol

the dpinst tool will add drivers to add remove programs

so this would be true of wsnow jaws and SAD/SoFI

whether or not the uninstall works is dependent on the driver itself...

if you use DriverPacks BASE to add the DriverPacks to your installation you wont have this problem... wink


Drivers can always be removed from device manager wink

3,223

(18 replies, posted in Other)

did you ever try using the DriverPacks - IE not useing jaws/snow

you may find that if you use the DriverPacks that it works quite well ...

( As near as i can figure you have not used DriverPacks yet )

I assume you are talking about UBCD4Win and not UBCD?
(UBCD is a DOS based tool)


UBCD4Win includes DriverPacks... and is the best way to keep your bartpe tidy!

1
only mass storage plugin is currently supported... (i am sure it says that in the tutorial)
(that is to say we do not support general questions regarding bartpe and its setup and or maintanance
It is better to ask the guru's over at UBCD4Win)
you should not need any other mass storage plugins with DriverPacks (see my last post in this thread)
and how to configure and enable the DriverPack MassStorage bartpe plugin is covered in the tutorial

2
see 1 above - only mass storage plugin is currently supported... (i am sure it says that in the tutorial)
No, slipstreaming them into the source will make no difference... they will be ignored...

3 No... they will be ignored

try the Release Candidate (at your own risk) base 8.09.RC 
It's available from our home page, it's the second news item.
it will build the other plugins but they may or may not work...
the packs (other than mass) have not been fully prepared for use by PE

Well i don't recommend that you use KTD... SoFI (the feature formerly known as SAD) makes KTD obsolete

second your source seems to be corrupted it said that M1 was removed but txtsetup.ORG was not found...

that means you have garbage...  assuming you installed DriverPack MassStorage previously
please start over with a clean source

Remember DriverPacks is always the LAST step in your process of modifying the OS files
(its OK to update the  cmdlines.txt file or whatever just not the files in the I386 folder)