Search options (Page 194 of 213)

I sincerely hope it works great for you again!

it was my hope that you would try using driverpacks base to add the driverpacks to your install!

This might just cure your driver problems permanently!

I did not consider your post as misuse or abuse - i just felt the need to clarify ...

and you did state "I did come across a test driverpack but am unsure how to use it."
So i was trying to lead you to that answer as well...

Give a man a fish and feed him for a day - teach a man to fish and feed him for life!

We are glad your here! your posts are clear polite and contain excellent descriptions!

please feel free to visit us anytime.

one other thing that may help you if you are not really interested in slipstreaming the packs is this alternate method of useing the packs
Can a Drivers Only CD be created with DriverPacks?

jeff

welcome to driverpacks and thanks for being here!

you did not mention what OS you were using as the source for your build XP or 2003?

it looks as though you closed the base program without htting the slipstream button.
that is what your log indicates anyway...

it should look like this

2007-11-17 02:22:50 : <INIT> DriverPacks BASE 7.05.2 initialized in API mode by UBCD4WIN Configuration Utility.
2007-11-17 02:22:50 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2007-11-17 02:22:50 : <INIT> Created temporary working directory.
2007-11-17 02:22:50 : <INIT> Imported proxy settings from Internet Explorer.
2007-11-17 02:22:58 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-11-17 02:22:58 : <INIT> 	Detected DriverPack MassStorage 7.09.2!
2007-11-17 02:22:58 : <INIT> 	Could not detect any 3rd party DriverPacks.
2007-11-17 02:22:58 : <INIT> 	Finished scanning.
2007-11-17 02:22:58 : <INIT> Detected settings file "C:\UBCD4Win\plugin\DriverPacks.net\BASE\DPs_BASE.ini".
2007-11-17 02:22:58 : <INIT> The platform wnt5_x86-32_bartpe will be used (which is the 'bartpe' installation platform for the OS family 'wnt5_x86-32').
2007-11-17 02:22:58 : <INIT> Imported settings from settings file.
2007-11-17 02:22:58 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2007-11-17 02:22:58 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2007-11-17 02:22:58 : <INIT> [OptionalSettings]\KTD default (false) was set.
2007-11-17 02:22:58 : <INIT> [OptionalSettings]\QSC default (no)    was set.
2007-11-17 02:22:58 : <SEL>  Selected module: mod_slip_wnt5_x86-32_bartpe.
2007-11-17 02:22:58 : <PREP> Existing BASE won't be changed.
2007-11-17 02:22:59 : <PREP> MassStorage.inf header info written.
2007-11-17 02:23:10 : <PREP> Extracted DriverPack MassStorage to a temporary working directory.
2007-11-17 02:23:11 : <SLIP> Processing the files now. This may take a minute.
2007-11-17 02:24:13 : <SLIP> Copied DriverPack MassStorage text mode driver files to BartPE Plugin folder.
2007-11-17 02:24:41 : <SLIP> Updated the MassStorage.ini [SetValue] sections to support DP MassStorage text mode drivers.
2007-11-17 02:24:41 : <SLIP> MassStorage.inf header info written.
2007-11-17 02:24:41 : <SLIP> Saved settings!
2007-11-17 02:24:46 : <SLIP> Slipstream finished in 1 minutes and 47 seconds.
2007-11-17 02:24:59 : <CLNP> Temporary working directory successfully deleted.
2007-11-17 02:24:59 : Program terminated.

see the bartpe tutorial in my sig below

ps since you do have the driverpacks in the correct folder (in plugins) you could use the plugins screen in pebuilder
hit config on # driverpacks.net - base -  hit config to enable
then hit refresh and you should then see ---> Yes # driverpacks.net - MassStorage 
in your plugins list.

I realize that you indicated you were a long time user of UBCD4win - but i am going by the log you posted.
I apologize in advance if i have not given you enough credit.

thanks for posting your INI and LOG and HWID's and a very good description
it is so nice to get such excellent detail from a new member!

Did you remove all the other mass storage drivers before useing the driverpacks
(removeing them from plugins and drivers folders?)

it may be to your advantage to get the latest build from UBCD4win
Creating a fresh source OS folder and fresh UBCD4win folder and starting "clean"

your version 3.06 has been replaced by 3.10

sorry this was so long in getting attn...

Hello and Thank you so much for taking the time to provide the details leading to your request.
We are always open to new ideas and ways to improve the driverpacks. 

There are a number of free programs available for setting display resolutions. 
One such program is included with WPI. "Reschange.exe" 
Others can be found with a Google Search. 

Any of these programs can be called from runonceexe or guirunonce. 

If we were to consider providing someone else's software to reset screen resolution;
we would need to get permission from that provider to redistribute it
and also burden us with support of the software.

If a driver incorrectly sets the monitor resolution
that would be an issue that should be taken up with the drivers provider. 

If we implemented this "feature" it would certainly cause more problems than it solved

What you wish to accomplish is quite easy to do without it being an included feature of the driverpacks.
and I personally believe is beyond the scope of what we do - which is to slipstream the drivers.

Hello L38Crow,

Thank you for reporting in - you have helped us to help you - it is always nice to get feedback on the packs!
i belive we may already be working on your issue.

Please see this other thread
http://forum.driverpacks.net/viewtopic.php?id=2277

please read the "read before you post" in my sig
you didn't include your relevant hwid which is neccessary to properly help you in this case
Your log and ini are probably not needed at this point but are always a good idea to include
your DPs_BASE.log would have told us what OS and SP you are installing  - you omitted that info in your post
the search function would have yeilded that this issue has (i belive) been reported already and you could have chimed in there.

have a great day, we are glad you are here and contributing to the community!

thanks i am looking at this still

thank you! looking at it now

Welcome to DriverPacks

Thanks for reporting your problem.

I think i may know what is wrong but i need your HWID for your raid controller
or at least a good description of it IE manufacturer, model, bios version, etc.

Ideally  we would like to have all the above info to give you the best support.

I am positive that sp3 is not your problem. but i am compelled to give you the canned answer.

canned answer:
"If you have DriverPacks BASE 7.5.2 or previous version then sp3 is not supported (you didn't mention which base you used)
beta's are not supported (Release Candidates are still beta) if Microsoft don't support it we don't either"

again i am positive that sp3 is not your problem. so don't sweat that right now.

give us the above requested details and i think i already know what to do to get you up and running
But i cannot fix it without knowing which driver we are talking about.

please read the "read before you post" to help with any future issues you may have.

I see you updated your post and cross posted with my post
But you didn' give your hwid's or hdd controler description

very interesting, but not a compliment to the scope of the driverpacks

the main idea of DriverPacks is slipstreaming drivers into an OS installation.

if i understand the tool you describe above correctly.
it makes copies of drivers on an existing system and it makes that copy on the local HDD.
That is not very useful:

what if the HDD driver is the one that is blown up?

what if the existing driver was the problem to begin with?
If my driver is blown up first thing i am going to do is get the newest one available from the net.

In my experience if a driver is blown up i have a virus or a bad hdd
it is very rare a driver will become corrupted and even more rare that simply re-installing the original driver is the fix. 

the only scenario where i think this may help is if the NIC driver were to become corrupt. that is a very small window of opportunity for this tool to be useful.

Thanks for your continued input here at DriverPacks.
Please don't stop bringing us your thoughts and ideas.
We are always interested in new ideas like the ones you bring to the forum.

we ARE glad your are here...

I have to agree with Bâshrat the Sneaky in the other thread this is not something that I personally will be adding.

sysprep is not one of my strengths although I am always eager to listen and to learn.

I have always used alternate methods like ghost. In my experience sysprep is just a PITA compared to the other choices available.

However I enjoy seeing other people banging their heads against the wall, so, here I am. LOL

To reasure you I knew very little about BartPE when I wrote that code.
Hilander and CDOB from UBCD4Win gave me the coaching I required to win that game, and in retrospect it was a shutout! 
I learn fast and have an excellent memory,  IF you can get my interest,  and you are at least that far. I'm interested.
If you and JakeLD are willing to coach me i will see what i can do about adding the sysprep platform to base.

One more note have you seen AutoImage.exe by rougespear? his program integrates RVM nLite DriverPacks and WPI and supports RIS?
More clues may be gleaned from his code as well.

  Jeff

you might but then there is the wraith of Bâshrat the Sneaky who doesn't wish this to be done to deal with...

your main issue is duplicated hwids

in pe this is not a problem but with sysprep it is a show stopper.

JakeLD is our resident sysprep guru perhaps he will jump in here. Even if he doesn't look at his stuff posted here already and i think you will find many clues to your eventual success.

I may be able to do this for you as it is so closely related to my work on BartPE.

Which also brings up sysprep we have gained quite a following form people who use the packs for this too.

Sysprep is also very similar and i think together we might be able to add this internally. as Bâshrat the Sneaky pointed out some of this code is UGLY i have been cleaning / rewriting it as i have to. there are tens of thousands of lines in base so it is not feasible to do it all at once and backward compatibility must also be considered.

But small steps taken in the right direction will eventually lead us to out destination. please feel free to contact me at any time.