Troubles Adding/Importing Drivers
Posted 06 March 2012 - 12:40 PM
- downloaded WinBuilder 080
- downloaded DriverPacks http://driverpacks.n...verpacks/latest for Windows 2000/XP/2003 (x86)/ and placed it in my USB flash drive in Drivers folder.
- I checked Drivers/Other/Driver Import PE AE in my LiveXP Project
- Next, I pressed Blue button and burned my bootable DVD disk with compiled ISO file
- I plug USB Flash drive
- When I booted with DVD disk, I saw Import PE AE shortcut. When I started it I saw warning: "Description of storage media (X:) is not possible".
My question: I can put drivers folder in my DVD bootable media but how can I set up LiveXP/WinBuilder environment to automatically use driver folder?
Thanks for answers.
Posted 06 March 2012 - 01:58 PM
Dipe (the program, not the script) throws up that error when you attempt to run it from a non-writable system drive (X:); there is a warning about it in the script. Try using WimBoot (or BootDI) or add FBWF to CreateISO, this should alleviate your issue.
Posted 06 March 2012 - 06:59 PM
P.S. Yes, you give a lot of materials (and thank you a lot!) but I want to understand some basic things (like what is FBFW and BootSDI. Yes, I read materials for beginners but I must order and collect all given information).
Posted 06 March 2012 - 09:52 PM
Posted 07 March 2012 - 08:10 AM
Edited by dm07, 07 March 2012 - 08:11 AM.
Posted 07 March 2012 - 02:43 PM
Yes, in fact, adding drivers automatically after boot should be kept to a minimum anyway or you'll be waiting a long time for drivers to load at each boot (you can always load them later if needed). Experiment with external Drivers folder to see what drivers are really needed and work best; only include in image, drivers needed at every boot. Usually a LAN DP (DriverPack) should cover most NICs and selected audio drivers as needed for expected hardware; avoid DP for this, only use manually backed up drivers from host machines. Normally this shouldn't amount to more than 20MB and unused drivers are deleted after boot to free up more room on your system drive. Other drivers, like mass storage, should be handled by their respective scripts.
Is it right that if I choose SDI and include specified folder (for ex. Drivers folder) I should limit size of this folder to RAM's size?
Yes, 256MB RAM is bare minimum for BootDI (or WimBoot), any less than this you should use CreateISO with FBWF; uses less RAM because whole PE image isn't loaded in memory, only the amount of RAM you allocate for writable space is used. Of course, you'll lose the performance of a fully RAM loaded PE; this is the trade off you'll have to weigh. I usually keep a non-RAM loading disc handy just in case I need it for an older machine or one where RAM is faulty
I mean, if a computer has 256 Mb RAM and suppose SDI is 200 Mb this is OK, but if a computer has 128 Mb RAM then it will be fail? Should I use FBFW instead of SDI if I have data which greater than size of RAM?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users