audio driver detection not working if drivers not in image

Hi,

here's Hoping I could get help on this topic please.

Using LiveXP and DRVImp AE 69, I can successfully add all drivers to an image, (liveXP using the WIM option) and the drivers get detected and install without any problems.

I'd wish to decrease the size of the WIM image thereby decreasing the loading startup time of LXP.

The problem comes in, where I create a folder called "drivers" in the root of the drive where the WIM image of LiveXP is run from, however, only audio drivers are not being installed when the search for drivers take place.

I can, however, search for drivers using driver autosearch, on the installed OS on the hard drive and the audio drivers install successfully.

If anyone could help with this problem, I'd really be appreciated.

Regards,

Using LiveXP and DRVImp AE 69, I can successfully add all drivers to an image, (liveXP using the WIM option) and the drivers get detected and install without any problems.

--
The problem comes in, where I create a folder called "drivers" in the root of the drive where the WIM image of LiveXP is run from, however, only audio drivers are not being installed when the search for drivers take place.

I can, however, search for drivers using driver autosearch, on the installed OS on the hard drive and the audio drivers install successfully.

Hi TheRookie,

Happy to help, let's try to figure this out

This seems odd because there is is no difference between how drivers are detected/installed inside the image vs. outside; the only requirement is that the drive be visible to the OS at startup (and in this case it would be). Please give more detail on how you've set this up, e.g. what kind of drive is the 'drivers' folder at the root of? Is the drive fixed (internal) or removable (usb), virtual etc. Will it work if the drivers folder is at the root of C: (internal hdd) or at the root of a UFD (plugged in at startup of course) etc.


--

...only audio drivers are not being installed when the search for drivers take place.

Does this mean other drivers in the same folder get installed? If so, the problem is specific to the audio drivers (obviously) but I don't see why they would behave differently... limit on free space, requirement of 'double pass' (some drivers require this) etc. Have you tried with/without 'RunOnce autostart' option (just curious)?

Hi TheRookie,

Happy to help, let's try to figure this out

This seems odd because there is is no difference between how drivers are detected/installed inside the image vs. outside; the only requirement is that the drive be visible to the OS at startup (and in this case it would be). Please give more detail on how you've set this up, e.g. what kind of drive is the 'drivers' folder at the root of? Is the drive fixed (internal) or removable (usb), virtual etc. Will it work if the drivers folder is at the root of C: (internal hdd) or at the root of a UFD (plugged in at startup of course) etc.


--

Does this mean other drivers in the same folder get installed? If so, the problem is specific to the audio drivers (obviously) but I don't see why they would behave differently... limit on free space, requirement of 'double pass' (some drivers require this) etc. Have you tried with/without 'RunOnce autostart' option (just curious)?

Hi Amalux,

Firstly, I must say thanks much for taking an interest and trying to help with my problem that I am having.

It seems as though, I've spoken too soon, and that the problem is rather worse.

Yesterday, I decided to boot up LiveXP with only my 16gUFD connected. so, I've disconnected my hdd containing the host OS.
To my surprise, DRVImp never detected anything.
However, if I manually do an autosearch, it asks me whether I'd like to search in the drivers directory which is found in the root of the UFD.
So I think, that autosearch at startup only works for host OS if found, and installs some of the drivers (graphics and chipset) which had originally made me believe that drivers were being installed if they were in the image.

When I did the test with my Host OS drive connected, it automatically installed the video and chipset drivers, but then I had to go in to driver import PE, select the Host OS installed, it found the Host drive, gave me a list of drivers, I then checked the audio driver which is (via High definition audio) and clicked on import and the driver installed fine.

my settings for DRVImp are as follows, all checked boxes for the below options are checked:
add HDAudio for full support.
pnp multimedia script is enabled
autorun at PE startup
autorun w/dipe at startup
include:
drivers link
run once at startup.

As always, your help would really be appreciated.

Regards,

OK, some basics, the 'autorun w/dipe at startup' and Smart Driver Import (stand alone) only works if there is a host OS to scan for drivers

The DriverImport GUI is separate from the auto-import options which run the program via batch commands. It's a good sign that DIPE GUI can find and install the correct drivers (again, this would only work if your host OS is present) but for auto-import you need to get those drivers into your drivers store at the root of the UFD (or any drive). The drivers you currently have in that folder are almost certainly the problem and you need to do some research to determine which drivers are correct. You can start by using Smart Driver Backup (included in the project or stand alone here) which will backup your host drivers. See options in the program for selecting ALL, non-M$ etc. Sometimes you need to select all and hand pick the ones you need (takes some trial and error testing), this method works best if your host is 'matched' to your PE e.g. 2000/XP/2003 with LiveXP; Win7/Vista with W7PE etc. The other option is DriverPacks; use the drivers that match your PE (not host). The auto import routine of the script will scan either loose driver folders (like Smart Driver Backup creates) or packed 7z/zip archives (like DriverPacks).

Neither of these options is guaranteed to work for all your driver needs but they're good places to start. You can test the drivers by running DIPE GUI in PE and selecting your drivers folder manually instead of the System search option or by running the auto-import (shortcut on desktop) separate from the GUI and directing to that folder; either way will tell you if these drivers are correct.

Once you have the correct drivers in the drivers store, auto-import should work without issue

OK, some basics, the 'autorun w/dipe at startup' and Smart Driver Import (stand alone) only works if there is a host OS to scan for drivers

The DriverImport GUI is separate from the auto-import options which run the program via batch commands. It's a good sign that DIPE GUI can find and install the correct drivers (again, this would only work if your host OS is present) but for auto-import you need to get those drivers into your drivers store at the root of the UFD (or any drive). The drivers you currently have in that folder are almost certainly the problem and you need to do some research to determine which drivers are correct. You can start by using Smart Driver Backup (included in the project or stand alone here) which will backup your host drivers. See options in the program for selecting ALL, non-M$ etc. Sometimes you need to select all and hand pick the ones you need (takes some trial and error testing), this method works best if your host is 'matched' to your PE e.g. 2000/XP/2003 with LiveXP; Win7/Vista with W7PE etc. The other option is DriverPacks; use the drivers that match your PE (not host). The auto import routine of the script will scan either loose driver folders (like Smart Driver Backup creates) or packed 7z/zip archives (like DriverPacks).

Neither of these options is guaranteed to work for all your driver needs but they're good places to start. You can test the drivers by running DIPE GUI in PE and selecting your drivers folder manually instead of the System search option or by running the auto-import (shortcut on desktop) separate from the GUI and directing to that folder; either way will tell you if these drivers are correct.

Once you have the correct drivers in the drivers store, auto-import should work without issue

Hi there Amalux,

Thanks for the very imformative post, as it has helped me better understand how DRVImpe works. I didn't know about the w/dipe at startup being specific to find host OS drivers.

So what I have done to get the audio working is to include it in the build since even though I've tried with driverpacks in the root under the folder drivers, it still doesn't seem to detect it. If I may say, with regard to other devices sometimes I'm lucky if it finds it and other times I have to manually do an autosearch.
However, I wont bother you anymore on the driver import issues which is now ok. Its just that audio is really important to me.

Going off topic here if you wouldn't mind to answer another question of mine please?

Looking at your menu.lst structure which you created with regard to the LiveXP which you have made for us to use, (thanks a mill for the newcommers tutorial), I've not seen the:
[[hook1]]
and:
[[hook2]]
commands used in the wonderful grub tutorial I've read by Diddy.

What I'd like to do is, add the LiveXP.wim to another USB drive which I have. On this drive, I have grub installed along with windows XP which can be installed from USB (I made it with the multiboot USB tutorial.)
so, would LiveXP work if I copied the following files:
LiveXP.wim
PE.DRIVE
WINNT.SIF
and add the following menu entry?:
title LX
chainloader /I386/SETUPLDR.BIN

Are the hook commands vital in order for Lx to work as well?

I'm so sorry for all the newbe questions.

I really wish to appoligise for going off topiclike this and would really appreciate it if you could reply to my question please.
Once again, I'd like to say thanks much for your previous post.

Regards,

What I'd like to do is, add the LiveXP.wim to another USB drive which I have. On this drive, I have grub installed along with windows XP which can be installed from USB (I made it with the multiboot USB tutorial.)
so, would LiveXP work if I copied the following files:
LiveXP.wim
PE.DRIVE
WINNT.SIF
and add the following menu entry?:
title LX
chainloader /I386/SETUPLDR.BIN

Short: I don't know

Long: I have tried setups like this in the past but found them unreliable (probably because I couldn't remember how I set them up); I now use only ISOs for portability and simplicity e.g. I can setup the same (multi-boot) ISOs (LiveXP, W7PE etc.) on NTFS - USB, UFD, HDD etc. (alongside full install OS if wanted) without any special or complicated requirements. Installing XP/W7 from USB in this case is simple as well but maybe I mis-understand your intention or question. If you must use the setupldr.bin method, there are many here who know more about than I do and hopefully they'll help out

Hi Amalux,

Thanks once again.
I have originally used the ISO method of loading LiveXP but I just asked about having the image along with the other files and loading setupldr.bin directly as I think and I'm really not sure if there maybe a time difference when booting up from ISO. As aposed to loading just the image.
However, it doesn't bother me much and so I guess I'll stick with the ISO like you also suggested. I think for me, it would make my file structure more organized as well.

Thanks for all the posts and i'm glad to have received your input.

I have so many other questions concerning making of applications for PPApps more specificly with regard to the registry but unsure where to post them...

But anyways, cheers and thanks for the help!

I have so many other questions concerning making of applications for PPApps more specificly with regard to the registry but unsure where to post them...

You mean you find the layout of this forum confusing? No

I guese you could post those questions here (as good a place as any)

But anyways, cheers and thanks for the help!

Sure, anytime