You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 207 of 213)
Topics by OverFlow User defined search
Posts found [ 5,151 to 5,175 of 5,307 ]
QSC is primarily useful for M1
Method one is considered obsolete for the most part and is rarely used and not discussed much anymore.
since m2 uses around 300 meg and m1 uses over 500 meg (on the destination) with full selection of the driverpacks.
M1 also exceeds the 4096 character limit for a search path in winnt.sif. so all folders past this limit are ignored.
most people opt for the disk space savings and full availability of all the drivers in the driverpacks by using M2.
If QSC is used for M2 it only affects textmode mass storage drivers. Since the mass storage driverpack is so small it doesn't have a huge benefit. I recomend turning it off unless M1 is needed.
the driverpacks base will automaticaly use the highest version found in DriverPacks or QSC so deleting the files in the QSC folder are not absolutely neccessary. Unless you are trying to use an older version AFTER you have used a newer version or if you are low on disk space.
QSC keeps a copy of the cabbed driverpacks to save time.
This was helpful only if more than one disc was going to be slipstreamed.
extracting the near solid archive 7zip DriverPacks and then cab compressing them is very processor and disk intensive.
if multiple slipstreams are done useing M1 this can save 30~60 minutes on all slipstreams done after the first one.
if your not useing M1 turn it off and forget it.
We probably will be phaseing M1 and QSC out and documentation will become a non issue. in the mean time Mr_Smartepants will probaly see this and add it to the help file he's working on.
Since you are useing QSC. I wanted to make sure you knew this...
The Quick Stream Cache folder is not self maintaining.
You need to manualy delete the files in this folder anytime you switch driverpacks.
\DPs_BASE\QSC\wnt5_x86-32_uni_DP_MassStorage_*.*
if you missed this step then we dont have a valid result.
If you have trouble post your hwids and laptop model well se what we can do
I'll be glad to do it once i have the bart stuff on the run and sp1 should be soon
@Bâshrat the Sneaky nope but i do agree with your assessment of the issue
neither changed mass nor any disk sections of mod_slip_wnt5_x86-32_any_uni_dpm.au3
@Kurt_Aust can we see the logs from the failed build, the log from the working one is not much help?
I suspect it is an issue with the "SP5" for 2000 read his post at the link he attached.
your source should not be slipstreamed for bartpe for two reasons
one - pebuilder will not copy any files other than the ones that are on its internal list of files. so slipstreamed drivers will not be copied.
two - drivers that are "upgraded" by slipstreaming my cause issues during the build process.
use a non driver pack modified source and use the base to create a plugin. then make sure the plugin is enabled from the pebuilder plugin screen. the drivers will be added to the destination during the build process. (and yes you have to select BartPE to get a BartPE plugin)
if you have done this correctly you will have a mass storage plugin in PEBuilder that is enabled.
(all the other packs will be greyed out for bartpe because only mass storage is supported so far.)
good thinking and nice effort JTDoom
yeah that is what i expected the two unknown devices are probaly the fixed feature buttons (like the internet explorer button on the laptop) the monitor driver will need to be from the laptop manufacurer same with fingerprint reader and modem. although the modem driver may be in the third party modem driver pack.
the wireless and dlan need to be investigated to see if teh HWID's are in the existing packs
I see the HWID's above what about the list of devices that didn't install correctly?
well, there is often a domino effect -
If the chipset driver fails then the nic and vid may also since they are connected to a device that is not working 100%.
useing vista as your workstation for the building of your disk has no known problems, so don't worry about that.
I expect you will be quite susccesful with a standard desktop.
can you give a list of the devices that failed to install properly and your HWID's (i know most of them are in the finisher log already)
thanks
I see the HWID's below what about the list of devices that didn't install correctly?
the answer is obvious after reviewing the Finisher log
You may be converting a laptop designed for Vista to XP? If not you are definately installing on a laptop.
Most laptops use very proprietary chipsets (they buy the rights to a chip then mod it for their needs.)
after they mod the chip the OEM drivers often will no longer be valid for them.
( the Toshiba satellite uses an ATI 200 M chipset but will not use the ATI reference driver from ATI for example. You MUST use the ATI 200M driver from toshiba)
this is why you are not being as successful as you might have expected. Laptops can be very finicky about drivers and often will only work with the manufacurers drivers.
jumz wrote:I stumbled upon this thread using the search function but I thought I would ask:
Where are the settings in this ini documented? i.e. How do we know what we are able to change and what the existing entries mean?
It's not documented... yet
example was provided by Muiz for "How To"
if you need help you can ask me too.
I am learning my way around the base pretty well.
Ah yes, i guess i was sleep typing.... Nice pickup jt.
Yes we certainly will!!!!!
No doubt about it
and your right it is mostly done - as posted above
adding will not be tough at all
I could do it in a day.
if i borrowed most of the code and gave some cudos to the authors.
I really am waiting for SP1 before I dive in I'm just trying to not have to do it twice. but since it' mostly done already.... just have to create a GUI page profile (some would exist like the update page) and add a module. its a couple of folders and files and the roughdraft above as a template for the new module
-I- wrote:apart from UBCD being way beyond illigal 
,
with any PE builder that makes you have to use your own windows cdrom,
it could (or maybe even should) be possible to add more drivers. the problem at this point IS though that adding these (uncompressed) drivers to your boot would almost completely kill all the space on your BootROM (dvd),
So overall, these 'cd' driverpacks might just be a real pain.
i wonder what would happen with a programm like PE builder when Storage drivers are cab'ed and then included in txtsetup.sif - and the pe-builder is given That (instead of a virgin cdrom) as its source..
Apparently you have not been following the progress of driverpacks and BartPE we do use cabbed drivers and add them to txtsetup.sif.
and it isn't a pain at all. Try it youll like it!
Slipstreaming drivers into the source fails because the new drivers are not on the "list of files to copy" from the source that PEBuilder uses. and wont end up on the destination. that is why we create a plugin.
the language in use for the forum is english only sorry ...
please post your base log and HWID's
usually the BSOD you describe is the 7b which means the incorrect disk drivers got used.
It does seem the modem is not in the list... it may not be plug and play compatable or may depend on a device that is not installed yet.
the PCI\VEN_1002&DEV_5A62&SUBSYS_13921043 should match the PCI\VEN_1002&DEV_5A62&SUBSYS_13921043&REV_00 device.
ATI Radeon Xpress 200M is the driver that should match the card but i suspect taht this is a laptop and it has a proprietary chipset provided by the distrubuter ( toshiba or dell or whoever it is)
ONE - please verify free space on your disk your useing - with QSC on you may need over 3 gig free
(the temp folder with the extracted drivers is around 1.2 gig the QSC cache folder will be around 500+ meg = 2 gig then add your source files and some room to work)
TWO your slipstream was NOT successful
THREE read this post - READ BEFORE YOU ASK!
http://forum.driverpacks.net/viewtopic.php?pid=4#p4
post your HWID's please
this usually happens when the driver for mass storage is a close match but not an exact match.
IE textmode works but plug and play fails
I have not heard of anyone else with this issue.
Is D: a mapped drive letter?
(ususally D is a CD ROM but certainly you didn't try to write it to a WORM device)
(try it on a local copy if so and then move it to the server after successful completeion)
more info -
are you only useing driverpacks alone?
are you useing nLight?
are you useing RVM?
WPI?
What is your source OS - 2000 - XP - 2003?
Exactly which options in DriverPacks did you use to get this result.
m1 or m2, KTD or no,
which base version
which driverpacks version.
may we see your logs
may we see your HWID's
If you want help you need to be specific and provide at least some basic info. (we are not mind readers)
if you are not sure what i mean read other peoples requests for help.
and of course read the one at the top of this forum called "READ BEFORE YOU ASK!"
http://forum.driverpacks.net/viewtopic.php?pid=4#p4
Posts found [ 5,151 to 5,175 of 5,307 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.125 seconds, 5 queries executed ]