Nvidia Video problem when installing XP via RIS
I am tring to deploy XP in my organisation using RIS and it has taken some time but I have got everything working - almost.
The kit :
Motherboard : Winfast 6100K8MB with Semperon 3ghz
Onboard Video - Nvidia C51G (GeForce 6100)
Network Card : Allied Telesyn 2916T Gigabit copper with PXE 2.1
The problem :
The installation goes smoothly - all OEM drivers have been included in the image and are detected, the graphics are detected during installation - in fact the screen resolution changes on the fly during installation to 1024x768 as specified in my sif file.
When the machine makes its final reboot however, the system comes up in 800x600 and there is an exclaimation mark in the device manager next to the vga adapter which suggests that the device driver should be re-installed.
If I then uninstall the driver and reinstall it from the video driver directory on the RIS server - it installs fine and everything is great.
I have tried 3 different versions of the driver
Nvidia 84.21 WHQL
Nvidia 84.56 WHQL ForceWare Ultra (guru3d)
Nvidia 81.10 (C51G driver shipped with motherboard)
every version does exactly the same thing.
My question is - what can I do to troubleshoot this problem ?
The kit :
Motherboard : Winfast 6100K8MB with Semperon 3ghz
Onboard Video - Nvidia C51G (GeForce 6100)
Network Card : Allied Telesyn 2916T Gigabit copper with PXE 2.1
The problem :
The installation goes smoothly - all OEM drivers have been included in the image and are detected, the graphics are detected during installation - in fact the screen resolution changes on the fly during installation to 1024x768 as specified in my sif file.
When the machine makes its final reboot however, the system comes up in 800x600 and there is an exclaimation mark in the device manager next to the vga adapter which suggests that the device driver should be re-installed.
If I then uninstall the driver and reinstall it from the video driver directory on the RIS server - it installs fine and everything is great.
I have tried 3 different versions of the driver
Nvidia 84.21 WHQL
Nvidia 84.56 WHQL ForceWare Ultra (guru3d)
Nvidia 81.10 (C51G driver shipped with motherboard)
every version does exactly the same thing.
My question is - what can I do to troubleshoot this problem ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's part of the SIF.
http://technet2.microsoft.com/WindowsServer/en/Library/62649611-a6f9-4757-bf41-194e95a989641033.mspx
This can be done using Setup Manager to create the sif as well.
http://technet2.microsoft.com/WindowsServer/en/Library/62649611-a6f9-4757-bf41-194e95a989641033.mspx
This can be done using Setup Manager to create the sif as well.
ASKER
Ok I got it - the only problem is that I want the whole process to be totally automatic but I havent found a way of making the nvidia setup.exe run unattended. There is a file called setup.iss (install shield silent) which is some kind of response file - but I still cant get get it to run unattended do you have any ideas about this or do I have to post a second question ?
Ah, it launches but requires some clicking - correct?
When you launch setup manually, do you see it extracting somewhere? If so, when you get the first screen from the install then minimize it and see if you can find the extracted files to use in your OEM folder. My guess is there is an ini file that might be usable to automate.
When you launch setup manually, do you see it extracting somewhere? If so, when you get the first screen from the install then minimize it and see if you can find the extracted files to use in your OEM folder. My guess is there is an ini file that might be usable to automate.
ASKER
We are working with the extracted files !
We have an iss file 'setup.iss' & an ini file 'setup.ini' but can't work out how to get it to pick up the answers from it.
We have an iss file 'setup.iss' & an ini file 'setup.ini' but can't work out how to get it to pick up the answers from it.
Make sure this is in the SIF:
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ign
Can you post the contents of the ISS?
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ign
Can you post the contents of the ISS?
Hi roseward
What switches have you tried using already?
I gather that you have already extracted the contents of the downloaded file, hence you knowing about the setup.exe and setup.iss
1. try run the setup with the s switch.
1.1For a Standard project, the command Setup.exe /s runs the installation in silent mode, by default based on the responses contained in a response file called Setup.iss in the same directory
2. If this does not work you can setup a temp system, using the r switch
2.1Running a Standard installation program with the command Setup.exe /r displays all the run-time dialog boxes, and stores the data in a file called Setup.iss, generated inside the system's Windows folder
If you prefer to specify a new .iss file use the /f1 arguement in either of the above two steps
use in the first step will create a new iss file
use in the seccond step will use the specified iss file
Setup.exe /s /f1"C:\Temp\Setup.iss".
3. If this still doesnt work, you can try creating a seperate log file in the RunOnceEx location, this has been known to work when done from CD installations.
Setup.exe /s /f2"C:\Setup.log
I hope this helps
What switches have you tried using already?
I gather that you have already extracted the contents of the downloaded file, hence you knowing about the setup.exe and setup.iss
1. try run the setup with the s switch.
1.1For a Standard project, the command Setup.exe /s runs the installation in silent mode, by default based on the responses contained in a response file called Setup.iss in the same directory
2. If this does not work you can setup a temp system, using the r switch
2.1Running a Standard installation program with the command Setup.exe /r displays all the run-time dialog boxes, and stores the data in a file called Setup.iss, generated inside the system's Windows folder
If you prefer to specify a new .iss file use the /f1 arguement in either of the above two steps
use in the first step will create a new iss file
use in the seccond step will use the specified iss file
Setup.exe /s /f1"C:\Temp\Setup.iss".
3. If this still doesnt work, you can try creating a seperate log file in the RunOnceEx location, this has been known to work when done from CD installations.
Setup.exe /s /f2"C:\Setup.log
I hope this helps
ASKER
iss file
[InstallShield Silent]
Version=v7.00
File=Response File
[File Transfer]
OverwrittenReadOnly=NoToAl
[{EFB7D050-CAD2-11D4-B34D-
Dlg0={EFB7D050-CAD2-11D4-B
Count=2
Dlg1={EFB7D050-CAD2-11D4-B
[{EFB7D050-CAD2-11D4-B34D-
Result=1
[{EFB7D050-CAD2-11D4-B34D-
Result=6
BootOption=3
[InstallShield Silent]
Version=v7.00
File=Response File
[File Transfer]
OverwrittenReadOnly=NoToAl
[{EFB7D050-CAD2-11D4-B34D-
Dlg0={EFB7D050-CAD2-11D4-B
Count=2
Dlg1={EFB7D050-CAD2-11D4-B
[{EFB7D050-CAD2-11D4-B34D-
Result=1
[{EFB7D050-CAD2-11D4-B34D-
Result=6
BootOption=3
Is this the newly created iss file? or the defualt one?
have you tried to use it in your RIS installation yet?
have you tried to use it in your RIS installation yet?
ASKER