Add motherboard drivers into livexp and win7PE
Posted 25 May 2012 - 08:04 AM
Now i create LiveXP-Rec (LX.041412) and Win7PE_SE , My home got 2 different motherboard Z67 and Z77 model.
Now i want to build a livexp and win7PE with all the drivers included inside them.
Question 1: Can you teach and guide me, where to add those drivers ?
Question 2: Can I included the both 2 motherboard drivers inside livexp and win7PE together. so that livexp having both "z67 and z77 drivers inside "and win7pe having both" z67 and z77 driver inside".
Posted 25 May 2012 - 04:35 PM
I answered the LiveXP part in your other topic and the same goes for Win7PE, you shouldn't need to add specific MB drivers to any PE unless you're having trouble booting to a specific machine. In other words, every PE should boot any machine; on some machines you may have troubles and need to take additional steps. Are you having trouble booting a certain machine with a PE? If so, give us specific details, which PE on which machine.
Posted 25 May 2012 - 09:27 PM
I'm facing slow start up after reach the dekstop. The desktop icon somehow displaying out slow compare with another motherboard. Thats why i thinking of it might be missing some driver. Please advice, thanks
Posted 25 May 2012 - 11:45 PM
For example, everything loads much slower in Win7PE than in LiveXP, USB will sometimes load much slower on one machine than another even though all other factors are equal.
If you use ppApps from USB, on some machines, those desktop shortcuts take longer to load than built-in program shortcuts.
If the issue is specific to USB e.g. 1.1 speed vs 2.0 (or 3.0?), sometimes updating the BIOS and MB (chip) drivers will help (not always) and this is done independent of PE.
Posted 26 May 2012 - 02:55 AM
Posted 26 May 2012 - 06:14 AM
Consider booting ISO(s) from internal HDD, much better, faster (boot in seconds) in every way if you use PE a lot a real timesaver
Posted 26 May 2012 - 07:04 AM
Posted 26 May 2012 - 11:39 AM
DriverPack Graphics A 11.07 for Windows 2000/XP/2003 (x86)
DriverPack CPU 10.05 for Windows 2000/XP/2003 (x86)
DriverPack Sound B 11.11 for Windows 2000/XP/2003 (x86)
Where can i put them into which folder or script ?
Posted 26 May 2012 - 12:42 PM
Kaspersky scan out that dipe_console.exe is a trojan.win32.generic.......
Posted 27 May 2012 - 01:07 AM
Amalux. I still cannot get along with Adding/Importing Drivers to PE (after loading).
I still want learn how is the basic adding driver before loading. Do you having any idea of it?
Posted 27 May 2012 - 02:44 AM
LiveXP and Win7PE_SE are different so ask about one or the other at a time to keep things clear and understandable. Unless stated otherwise, my answers apply to my projects (linked in tutorial) since those are the ones I'm most familiar with but may also apply to official releases of LiveXP and Win7PE_SE.
I would not recommend adding any of the DriverPacks listed above using DriverImport (after loading) method. As stated in tutorial, this method is mainly for NIC (DP works well here) and audio but the audio DP is problematic because it's too large, takes too much time to scan and may cause driver conflicts or even BSOD (same for graphics pack). Audio drivers are tricky to begin with, not all audio hardware will be supported in PE. The best results (for me) have been from backing up audio from host with SDB and supplying those drivers or using DIPE GUI in PE to import system drivers directly where this is possible. Similar in Win7PE with drvload which works for me where other tools fail but only with drivers backup up with SDB (no archives, DPs or executable packages).
The other DPs you mentioned, chipset and CPU should not be required and again could cause conflicts or crashes. If you want to experiment with adding these DPs, try adding them (unpacked) via the Driver Integration script in Win7PE_SE or try the Processor Drivers script in LiveXP.
Adding drivers with DPInst (after loading) or DISM (packed to WIM during build) has been (surprisingly) unrewarding for me personally. Often, drivers which load properly via DrvLoad simply don't work when installed using these other methods. It seems counterintuitive that this would be the case but it is (at least for me). Anyway, ask your questions when ready
Posted 28 May 2012 - 11:22 PM
I second that! A PE with all sorts of drivers to try to make all sorts of potential HW work correctly is an elusive thing!
Adding drivers with DPInst (after loading) or DISM (packed to WIM during build) has been (surprisingly) unrewarding for me personally. Often, drivers which load properly via DrvLoad simply don't work when installed using these other methods. It seems counterintuitive that this would be the case but it is (at least for me).
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users