You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
Ghost images are made after windows install is finished.
Driverpacks are applied during windows installation by setup.
You would need to have a ghost image for each HAL and Primary HDD (boot partition) controler type that you have.
If all of your machines are the same type (HAL and mass storage) you can use ghost.
Otherwise you must have one ghost image per machine type.
RIS is an option that may work for you. If you wish to use DriverPacks with RIS I suggest RogueSpear's AutoImage
OK, it's now 5 lines - your wish is my command...
although i seem to do pretty well with just one line?
it seems to me that offline sysprep is useful for moving a drive to a new system in which case you will only need to "add" one driver and then not have a problem.
if it is your desire to create / modify an image that could be loaded onto multiple machines (the true intent of sysprep) then the better way to go would be to use a driverpacks slipstreamed source to begin with (one of the few times KTD is useful). in that way all of the mass storage drivers would always be available. (or any other drivers that were Kept by Keep The Driver (KTD).
@ Helmi
I added some more room for signatures.
the max length has been raised from 400 to 600 but i left the total lines limit of 4 in place.
you were right on the edge at 381 char.
i also added a donate link to the menubar at the top
according to your log you did not slipstream the driverpacks.
this seems to be a problem with powerpacker
the mass storage textmode drivers were not added (per your log)
it is also likely that the base ini you sent is the one in its folder an not the one referenced in the log.
sounds nice!!!!
i was condsidering buying one too... but since intel always releases their new chips in June i was going to wait till then so i can save a few bucks on the "old" stuff (well it will be "old" stuff then)
cdob makes a good point about compressed vs non compressed drivers. uncompressed they may take a lot more ram.
furthermore i belive with your method the support files also get loaded. if this is true it is much different than textmode setup where they are not needed or loaded into ram. Support files are eventually loaded by PNP in PE and then we don't have the memory limit and only the files required for a needed controler are loaded instead of all of the drivers. so if there are support files with the same name it will not matter (to us at driverpacks for slipstreaming) since they are loaded only if needed on the current installation.
Somebody stomped on my username over at 911 i had to register with an alternate name 
(and that person has a whopping 2 posts since 2005 - unfortunately they did visit as recently as last week - so it's not a dead account)
it corupted my local copy
It mentioned something about conflicts brought up a merge window i made my selections and commited them and afterwards my local copy was overwritten by the remote version.
I was quite upset about it. In fact i put the whole mess on the back burner for over a week now...
there is a copy of rc2 under "branches" since i was not able to make a copy normaly...
i am considering useing another brand other than tortois svn i said it was 20 hours
but it may be more like 30 hours that got flushed.
Since i am the only one useing it there should not have been anything to merge... therefore it is blown up somehow.
ICH7 is in the packs
Read before you post in my signature below
read before you post in my signature below...
the number of drivers is not as signifigant as the size - IE one driver may be 120k but others may be 360k...
you could have three more 120 in place of one 360 if it were a size limit...
link above is dead
if you belived it was size then you could total the size of the listed *.sys files and see what the totals are for each group.
you may have to allow some slack space (each driver may occupy slightly more ram than its actual size)
if the size theory was correct it wouldnt matter which drivers where included only thier cumulative sizes.
test and report ill see what i can tell you
the latest version of UBCD4win includes Driverpacks and mass storage pack.
you must go into pebuilder and click the plugins button and highlight base and click the configure button.
this will create the mass storage plugin and enable it - build your PE and test.
the tutorial for mass storage for bartpe (or UBCD4win) is in my signature below
what is the name of your pack ?
what folder is it in ?
what is the folder structure of your pack?
what drivers are contained?
toss us a bone here we are not mind readers 
RC2 I always intended for public testing...
I thought i had a link directly to it in my news artical for a while...
now that link is changed to a thread in the semi-private testing team forum.
i wont mention jaaks name or anything... ahem...
The best reason to have it out is; to make sure that no uglies pop up with SP3
the fact that QSC and the double D\D error are fixed is just a bonus.
this is the link to DPs_BASE_801RC2
Link has been updated in first post (home page)
I dont think i want to release it yet - as helmi said we don't want a flood of support issues
But a broader testing group is very desirable at this point.
I tried to sync my local copy of rc3 with the SVN server last week and it blew up, and instead of an offline backup i got garbage.
more than 20 hours of codeing went in the toilet... ironicly while trying to backit up. on the up side it should not take me as long to do it the second time as it did the first.
wow - you have a sticky and you dont even have ten posts yet...
You da man!
strange...
the beta that was up briefly was a test of the PROXY feature of base which was broken...
it was intended for a single individual to let me know if my fix for the failed "Proxy settings import" code would work.
I got the feeed back that my fix was valid and pulled it.
It was a snapshot of what i was in the middle of working on at the time... (a quick and dirty test)
i lost about 20 hours of work i did on base last week and became sad... or 8.02.RC would be out already.
Disable is an exclusivly windows 2000 feature
although you could use SKIP and get the desired result
or set the driver count to 0 (zero)
Wonderful!
Thanks for being here PJ!
Which version of base are you useing?
Base does rename to 8.3 internaly and it always has...
perhaps your local copy of base is corrupted
you cant use nlite to add drivers to a BartPE disk
In fact the problem may be you have made your source no good for bartpe by useing nlite on it
Only Use a CLEAN source for bartpe
divide and conquer.
split the groups in half untill the offending unit is found.
I am sticking to my conflict theory.... the memory limit is not yet attained...
you are welcome to prove me wrong
the error they refer to is based on previus experience we have with windows 2000...
the memory limit for 2000 was reached years ago and occasionally we breach it by accident when we add new drivers.
We have not been able to acheive this limit in XP or 2K3 (yet).
I belive (without any real proof) that the drivers do not in of themselfs (totaling thier cumulative sizes) achive the undiscovered limit.
the most likely cause of this is a corruption of RAM - IE a driver is burning more than its share or is loaded more than once.
IE a conflict that corupts RAM...
this is an easy theory to prove - remove a few dozen drivers and run a test.
your welcome in adanvce! well see if the guys step up to the plate - I will do it for base...
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.190 seconds, 5 queries executed ]