Jump to content











Photo
- - - - -

Add a driver


  • Please log in to reply
40 replies to this topic

#26 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 09:04 AM

I've found a little program named "SetVideo", which allow me to change the resolution on-the-fly.

Of course, i launched the driver, but i still have no more resolutions ...

Edit : i have a question : where does the "original display driver" look for drivers ? I have the feeling it is on system, but what if we want to add a driver of a chipset we don't have ?

For exemple, i have an Intel chipset (fortunately, as clients of PXE). What if i want to add nVidia drivers ?

Edited by neeko, 15 June 2011 - 09:21 AM.


#27 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 15 June 2011 - 09:28 AM

I've found a little program named "SetVideo", which allow me to change the resolution on-the-fly.

Of course, i launched the driver, but i still have no more resolutions ...

Edit : i have a question : where does the "original display driver" look for drivers ? I have the feeling it is on system, but what if we want to add a driver of a chipset we don't have ?

For exemple, i have an Intel chipset (fortunately, as clients of PXE). What if i want to add nVidia drivers ?


Think it looks here:
C:\Windows\System32\DriverStore\FileRepository

#28 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 09:46 AM

Ok. For the example, the script looks for the folder "igdlh.inf_x86_neutral_2d255f193700d214".

Why this one in particular ?

And in my computer, i've got "igdlh.inf_a8ba7c9c". Should i replace it in the script ?

#29 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 15 June 2011 - 10:02 AM

Ok. For the example, the script looks for the folder "igdlh.inf_x86_neutral_2d255f193700d214".

Why this one in particular ?

And in my computer, i've got "igdlh.inf_a8ba7c9c". Should i replace it in the script ?

Not sure. I’m no “expert” or familiar with this script.
But why not give it a try?
You should probably change in four places:
Line 30, 57, 76 & 116.

#30 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 784 posts
  •  
    France

Posted 15 June 2011 - 10:28 AM

Neeko,

For the script, you must look in driverstore of Install.wim
In my "Fr" or "En" dvd, i have the Intel graphics adapter in :
igdlh.inf_x86_neutral_2d255f193700d214 (x86)
igdlh.inf_amd64_neutral_54a12b57f547d08e (x64)

but then you can add your own and others drivers with the Driver Integration script and try.

In my config, With “ResolutionChanger”, i can change to any resolution, even 16/9. I did not try to force a 16/9 resolution in PEShell.ini (Display Width and Height parameter) to see if it works at startup.

#31 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 11:28 AM

Neeko,

For the script, you must look in driverstore of Install.wim


Ok, i've found it.

I've already tried to put a driver with the driver integration script, but it didn't work.

#32 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 15 June 2011 - 11:39 AM

neeko, i think by now, that there is something fundamentally going wrong.

Firstly, you should have the display dialog in your PE, to change the resolution. No need for 3rd party tools.
Second, the 'graphic card' will not show up as chipset in 'device manager'. Even if it is an integrated one, but as graphics adapter.

"original display drivers" script does exactly, what it says, it copies the original display drivers to your build. Original in this case means, those drivers that your Win7 source came with.
Did the graphics work right out of the box, without installing drivers for it? If not, that script won't help you.

You have never said, what happens, if you try to run the setup.exe in your PE?


To get all the needed files for your graphics card, assuming you have Win7 installed on the coputer in question.
Go to device manager - right click on your graphics card choose properties - choose tab drivers - click on driver details. Write down all the files listed there, you will need to collect them.
Now use windows search, to search in the inf folder, for any file containing any filename, you had previously written down. (Best use a *.sys file.)
That is your inf!

Now use any of the privously outlined methodes, to add the whole shebang to your PE.


:cheers:

#33 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 11:56 AM

The PC i'm working on and the PXE client are not the same one.

I don't have the resolution changer, that's right. It wasn't in the Project when i downloaded it.

I've never try to install directly the drivers, good idea :cheers:

#34 ChrisBA

ChrisBA
  • Members
  • 8 posts
  •  
    Germany

Posted 26 October 2011 - 02:47 PM

Third day, third post... sorry to bother you guys!

it seems I'm stuck with a similar problem as "neeko" above: I wanna integrate Intel Video Drivers (946GZ and Q35 Express, each on a different PC of course) into my Win7PE_x86 so that they are loaded automatically after startup of the ISO and I'm able to set a 1366x768 resolution by cmdline.

status quo:
  • Win7PE starts up with "hardware default" display driver (not Intel) and only 4:3 display resolutions available in the "Resolution Changer SX2"
  • Clicking the Start Menu icon to install the Original Intel drivers (which are present in ...system32driverstorefilerepository... ) leads to a yellow exclamation mark in the device manager on the graphics board entry. The details tab shows a "Code 37: the driver could not be initialised" (my translation from German)
I have done:
  • "orignal display drivers" script activated - since both of the above mentioned drivers are listed in the respective .inf-File of the original Intel drivers that comes with the Win7-DVD.
  • also tried the "Driver Integration" script, thus downloading and extracting the appropriate driver package mentioned earlier in this thread - same results: driver could not be initialised.
Further info:
  • @MedEvil: The "Display"-Dialog in my PE doesn't work - nothing happens when I click it.
Any suggestions on what I might be doing wrong are highly appreciated!

Regards,
Chris

Edited by ChrisBA, 26 October 2011 - 02:54 PM.


#35 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 26 October 2011 - 03:59 PM

If you miss the display dialog, you must have unselected one of the scripts dealing with display. (Not display drivers though!)
If you use Win7PESE, like it comes off the server or from the archive, display dialog should work by default.

The exclamation mark appears under exactly two circumstances.
The driver isn't compatible after all. (A lot of people had this problem with the "orignal display drivers" script, though usually in regard to nVidia graphic cards.)
The default driver was properly installed. (Windows does not allow to change drivers without restart, but that problem was already fixed months ago.)

My advice, start out fresh without tinkering with any settings, if that works and you have on the computer, you run the PE on, Win7 installed, try loading the graphic card drivers from the host Win7. (those are known to work)
If things still do not work for you, post back.

:cheers:

#36 ChrisBA

ChrisBA
  • Members
  • 8 posts
  •  
    Germany

Posted 27 October 2011 - 09:32 AM

@MedEvil: Thx for your reply!

I did as you said:
  • downloaded the WinBuilder.exe as well as the Win7PESE project plus the additional "OriginalDriversScript" from the built-in download manager - contrary to my first attempt, I used the Win7-x64-Sources this time for the build, since I have WIN7 x64 installed on a different HDD partition on that computer, which has an operating graphics driver.
  • only settings I changed were in "Finalize4- Create Iso" - there I unchecked the "enable press any key to boot option", since I wanna boot the ISO from HDD without user interaction and in "Drivers" I activated the "Original Display Drivers Script" (leaving the load at startup box unchecked)
Still, I got the same problems as mentioned before:
  • Installing the Intel drivers from the start menu leads again to a yellow exclamation mark in the device manager as well as a "code 37" in the driver properties
Then, having WIN7 x64 installed on he same PC, I booted this one and did the following:

To get all the needed files for your graphics card, assuming you have Win7 installed on the coputer in question.
Go to device manager - right click on your graphics card choose properties - choose tab drivers - click on driver details. Write down all the files listed there, you will need to collect them.
Now use windows search, to search in the inf folder, for any file containing any filename, you had previously written down. (Best use a *.sys file.)
That is your inf!


After that I copied a folder containing these files to %GlobalTemplates%Drivers_x64 in order to integrate them into my PE. Unfortunately, when booting the ISO, the problem remains the same, though exactly the same drivers work on that PC.

By the way, the "Display" option in the desktop context menu still doesn't work when being clicked on.

Any more ideas?

Thx very much!

#37 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 27 October 2011 - 07:08 PM

Making a 64bit PE, when you have a 64bit Win7 installed was a good move. :thumbup:

Please try to create a PE without the original display drivers script. I don't trust that thing. ;)
Also do not include the drivers, you gathered from the host computer.

Create a plain build. Boot it up and check if display dialog works. If that's not working, there is little use in working on the driver problem, since obviously something goes wrong with the build.

If display dialog should work, open device manager, double click on the graphic card and choose to install a new driver. Select that you manually give the location. Go to the HDD where your Win7 is installed and select the folder "windows\system32\driverstore\filerepository".

:cheers:

#38 ChrisBA

ChrisBA
  • Members
  • 8 posts
  •  
    Germany

Posted 04 November 2011 - 10:19 AM

Create a plain build. Boot it up and check if display dialog works. If that's not working, there is little use in working on the driver problem, since obviously something goes wrong with the build.


I've checked on this now (after a had to focus on different matters last week - sorry for the late reply) - and even on a plain build the display dialog doesn't work. Would it be helpful if I attached some kind of project logfile for you?

Could there be something wrong with the WIN7 sources?

Edited by ChrisBA, 04 November 2011 - 10:20 AM.


#39 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 04 November 2011 - 12:25 PM

You're in luck, i have some free time today. If you attach the log, i'll have a look. Maybe it's something obvious.
A problem with the source is always a possibility, unless it has already worked fine for another project. Best source is an untouched retail DVD.

btw. You never said, what your source is.

:cheers:

#40 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 474 posts
  •  
    India

Posted 04 November 2011 - 01:26 PM

I don't know if this will help : I recently started building 7pese rather than livexp. I have a AMD 4350 gcard so I included the catalyst drivers in the "Driver Integration" script at %GlobalTemplates%Drivers_x86 .
It worked perfectly.
My cousin has a Intel G31 based system so I wanted to test it there too. I also included the G31 display drivers at %GlobalTemplates%Drivers_x86. When I booted the 7pe there the screen resolution did not change so I assumed the G31 driver did not install properly. But I then ran HwPnP and the screen was then set at the correct resolution ( 1600x900x32 ).
So try HwPnP.

#41 ChrisBA

ChrisBA
  • Members
  • 8 posts
  •  
    Germany

Posted 05 January 2012 - 01:49 PM

I finally got time to get to work on this topic once again and in fact found the solution for the problem where the display dialog didn't appear in my 7PE build: I just included the script "TweaksControl Panel Display & Aero" which was initially downloaded but not included/checked in my project by default (which I thought it would be).

Now my display driver gets installed properly and I can apply 16:9 screen resolutions on appropriate display panels.

Maybe this info is helpful to someone else.

Sorry to anyone whom I might have caused a headache and thanks again for your support!




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users