Search options (Page 195 of 213)

It was my belief that the DriverPacks mass storage plugin was solid and working.
it theory it would already do everything neccessary to funtion in PE as well.

what are you refering to?

I updated your Bug report assigned it to myself
I have fixed the error in my local copy of the code
the fix will be included in the next release (soon)

It helps tremendously - this is what Jaak and i have been talking about working towards for months...
Since you have made the pack compatible with PE you have saved me hundreds of lines of code in the base program itself!!!

This is a HUGE pickup - you have taken what would have taken me weeks to code and made it into a few hours work.
I will just need to create a double check routine in base to ensure that packs don't include duplicates and kick out a message if any are found.

Instead of having to create a routine to rename them and then programmatically update the infs with the base's internal code.
The brain is a much more powerful tool than anything I can write. although I had some ideas as to how it may have been possible it would obviously have been quite a task... as you now realize having done it yourself by hand.

Caveat - the LAN pack must be maintained this way from now on by the team.
if this is agreeable to everyone i can punch the LAN plug-in out in about a week give or take a few days.
Lets get this pack into the nightlies for testing - if this method doesn't break normal operation of the DriverPacks we are looking at pure gold!

Echo_Platoon since you are now on the DriverPacks Team You now have the permissions to be able to add this to nightlies yourself.
make sure that you give your pack a higher number than what is there like - DP_LAN_wnt5_x86-32_71230.7z
create a changelog and indicate which pack version (specificaly) you used as your starting point.

Congratulations on your promotion Corporal Echo_Platoon

Now that is what being a Team is all about - That's what I'm talkin about !
Everyone give themselves a big round of applause and a pat on the back!

Woo Hoo!!!

Quite simple to do

1) Run DriverPacks BASE as normal on any OS source folder useing Method 1 (M1).
    Doing so will create "Source Folder \$OEM$\$1\D\"

2) Burn any or all of the driver folders that are in the $OEM$\$1\D folder to a CD.

Notes:

It is not neccessary to select MassStorage Text-Mode for this and it will save a little time if you don't

Method One will cab compress the DriverPacks so they all will fit on a single CD.
     All of the DriverPacks when un-7zipped  will  require about  1.5 GB of disk space.
     All of the DriverPacks when cab compressed require about 500 MB of disk space.

The $OEM$\$1\D folder will contain a sub-folder for each type of DriverPack you select in dp-b.
     If you wish you may select individual sub folders of the D\ folder for your "Drivers Only" CD.

after finished do this:
1. find the device manager items without correct drivers.
2. click "Update driver" for one of those items
3. click "Install from a list or specific location"
4. checkbox "Search removable media" and click next

Second time this topic is stickied... please use the search feature
I have now added this to the FAQ thread as well and will update that version as needed.
no need to apogize for your english - we realize that not everyones native language is english.

also note that windows will run in 640 x 480 mode unless you tweak something.
once setup is finished a dialog box will come up and report that your screen resolution is too low and if clicked will attempt to set it to 800 x 600

these things all being true  -  We have no clue what you are refering to.

driverpacks in no way will set your screen res or refresh nor do we have plans to add that feature.

PS it is a lot easier to help you if you actually give us some information about what you did and how you did it
hwids - at te very least what video card it is and what monitor you have.
base (and version)
packs (including versions) used
how the problem can be reproduced
what other programs you are running (RVM, Hfslip, nLite, WPI)
ect...

I am also not aware of any OEM or reference video driver or monitor drivers that will by default select the highest setting available.

{confused} and quite certain your problem lies elsewhere - maybe the settings in winntsif Mr_smartepants refered to are set wrong (possably by you with nLite) or WPI can do this (also requireing you to set it that way) or perhaps some other program you are useing.

windows and all video and monitor drivers default to 640x480 and then suggest that this is to low and that 800x600 or better is recomended. and even then you must click on a dialog to acheive the higher setting.

IE the request you made is already the default - and is not now - and will not in the future be affected by DriverPacks

That is the way things are now... we know of no exception to this (unless ther is user intervention or some third party software is used)
If you can cite an exception to this then i belive you are alone in experiencing it. If you need help then you need to give a LOT more detail.

thanks for helping us to help you !

good info and feedback - we will keep at it till its gold!

thank you for the assist and the link -
yes it was relevant and helpful...

hi!
can we know which OS base and pack versions you used?

I know I have been using MS since DOS 1
it was just an FYI... for the masses

and post the hwid's

i emailed it to you ...

ps the pack is unchanged except it has been renamed to be 8.2 compatable filename in OEM folder just have to  rename it back to original name to reuse it with base or copy it over as is to OEM in new cd.