Re: dual boot - Nvidia device driver
- From: "KM" <konstmor@xxxxxxxxxxxxxxxx>
- Date: Wed, 4 Jan 2006 02:43:37 -0800
Eric,
Please see my comments inline...
> Thanks for the help. I did have a conflict with a componet that I created
> myself after the initial failure of the import of devices.pmq. After I
> deleted this initial attempt at a custom component for the NVidia Quadro FX
> 1400 from the Component DB and created an image without a device driver, I am
> able to install the nvidia driver manually after a boot of xpe. I then
> tried to create another custom component for the Nvidia driver using
> information in "Windows XP Embedded Advanced" by Sean D. Liming. I installed
> Incntl5 - then uninstalled the driver in regular xp pro - then capured the
With PnP drivers you don't need to mess with the InCtrl5 like tools. Your custom component just has to place all driver files in
appropritae windows folders (\windows\inf, \windows\system32\drivers, etc.).
> files that were installed. Then created a component and a package and added
> the to groups as the book mentions. However, I then still failed to install
> this custom package. I had a service resource problem looking at the
> setupapi.log so I disabled the service in the compenent designer in the
> resource and then recreated the pacakge and then failed at another point. I
Can we see you Setupapi.log?
Did you make sure all the driver dependencies are in your image?
> see the you were trying to help someone else with the same problem and you
> mentioned dependency walker which I intalled and tired on nvclp.dll - it said
> that msjava.dll was not there so I added this but it did not help.
In Dependency Walker the mising msjava.dll info is almost always a bogus message. You can safily ingore it.
> So I am thinking this is a lot of trouble and I am wondering if I need to
> componentize the driver anyway. I would probably be ok to run the driver
> install on the embedded image - as well as other drivers manually - then
> create an image for the factory.
Yup. You can use the manual reseal technique: http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconConfiguringResealPhase.asp
However, it doesn't save you from the missing dependencies problems. You will have to analyze and include required dependencies
anyway.
This is the reason I always prefer componentization rather then manual install of apps and drivers on XPe images.
Also, don't forget that the manual install of some packages will require the presense of heavy MSI support components in your image.
> I should say I am trying to evalulate Windows Embedded XP for a medical or
> biotech workstation that runs in a private subnet.
The main rule with XPe is - if it can technically be done with XP Pro, it can be done with XPe.
(the same binaries)
Only legal restrictions are there but from your device description it doesn't seem you are crossing the borders.
> Here are the requirements:
> 1) I am using a dual processor xeon Precision 670
> 2) I need dual graphics monitor - using Nvidia FX 1400 with two NEC monitors
> 3) The applications retain state so if I update I would have to migrate some
> configuration files besides replacing binaries
Registry based settings? Or INI files to store the application settings?
Unless by "update" you mean the entire image replacement. Then it would require you to move the data files to partition that will
stay untouched during such image update process.
> 4) I use DirectX 9.X
The component is there in XPe repository.
Aer you working with SP1 or SP2 database?
> 5) I want to lock down short cut keys (is this posible with Embedded XP ?)
Possible with most of the keys. But some key combinations may require more work.
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconBlockingCTRLALTDELETEKeyboardAccess.asp
> 6) I want to lock down the computer so it can only run this biotech
> application (group policy ??)
Well.. group policies here would really be helpful to lock down Explorer based shell.
If you implemented your own custom shell you could restrict the user as you'd want to.
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconShell.asp
> 7) We need to update applicaiton software, os service packs, drivers.
DUA, SUS, SMS, your custom client.
http://msdn.microsoft.com/library/en-us/dnxpesp2/html/XPESP2SERVServicingWithWindowsXPEmbeddedWithServicePack2.asp
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeoriRun-TimeImageManagementServicing.asp
> 8) Need to create image that can be deployed in factory then updated per
> customer options.
Use XPe cloning.
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeoriMassDeployment.asp
http://msdn.microsoft.com/library/en-us/xpehelp/html/xetbsCreatingMasterRun-TimeImageForCloning.asp
> Well so far:
> I can't see two processors in TaskManager
What does Device Manager show?
Make sure you are working with the right chipset drivers.
If you install XP Pro on the target are you able to see both processors?
> I am having problems with vidio card.
> The network card does not import (I could do this manually)
Again, go for componentization. Also, always analyze the SetupApi.log and FBALog.txt files.
> Questions:
> Is XPE a good choice ?
I don't see any reason why not. If XP Pro meets your device needs, XPe will likely do the same.
Although I would also recommend you to take a look at Microsoft Windows CE OS. Then, if acceptable, you could get much lower licence
costs.
> Can I manually install the drivers then create an image that I install in
> factory.
Yup. See the cloning/reseal link mentioned above.
> - what about the oem license id for xpe that needs to be different for every image ?
You just have to buy a license that covers all devices of the same type you plan to distribute.
You can create one image using just one PID number that you receive from XPe distributor. This is applicable to all the devices
covered by the license and sealed with the provided COA stickers.
An XPe distributor will explain you the process much better so do not hesitate to contact any of them.
=========
Regards,
KM
.
- Follow-Ups:
- Re: dual boot - Nvidia device driver
- From: ecoulson
- Re: dual boot - Nvidia device driver
- From: ecoulson
- Re: dual boot - Nvidia device driver
- References:
- RE: dual boot - Nvidia device driver
- From: ecoulson
- RE: dual boot - Nvidia device driver
- From: ecoulson
- RE: dual boot - Nvidia device driver
- Prev by Date: Re: GeForce 6200TC Compatible Driver
- Next by Date: IBM OPOS Software
- Previous by thread: RE: dual boot - Nvidia device driver
- Next by thread: Re: dual boot - Nvidia device driver
- Index(es):
Relevant Pages
|
