Re: dual boot - Nvidia device driver
- From: "ecoulson" <ecoulson@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 13 Jan 2006 14:24:04 -0800
Hi all,
I just had a chance to work on this again. The Intel Pro/1000 Dual MT dual
Port Server Adapter proved to be much easier than the nvidia card. I found
the eight files necessary on the CD that came with the board. DVD Driver:
E:\PRO1000\WS03XP32 and put all the files in a component:
e1000msg.dll - C:\WINDOWS\system32
e1000325.inf - c:\windows\system32\inf
PROUnstl.exe - C:\WINDOWS\system32
e1000325.cat - c:\windows\system32\inf
e1000325.sys - c:\windows\system32\drivers
intelnic.dll - C:\WINDOWS\system32
created in Component Designer: component/repository/package/add group
according to the instructions in the "Windows XP Embedded Advanced" book by
Sean D. Liming. Then added to Componet Database and then target in target
analyzer.
I had tried to import the inf but got a message that e1000325.inf was
empty. I have seen that other people have had this same message when
importing into Componet Designer. However, the custom component with just
the 6 files seems to work.
I was worried that I didn't have any entries in Registry Data, Component or
Group Dependency, or Build Order Dependency, or Resources. But it did not
seem to matter.
I was also lucky because my mother board NIC is Intel Pro/1000 and that
worked also.
Now on to the DVD/CD driver - then try to install my applicaton.
Thanks, Eric
"KM" wrote:
> Eric,
>
> And again you should give us more info about the problem with network driver installation.
>
> FBALog.txt, SetupApi.log, Device Manager will provide you some insights on the issue.
>
>
> =========
> Regards,
> KM
>
>
> "ecoulson" <ecoulson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E4F63405-8B4D-40D2-8621-00A69AFFA7B9@xxxxxxxxxxxxxxxx
> >
> > Actually I was seeing two processors in task manager I was just too blind to
> > see. Then I turned on Hyperthreading in the bios and I saw four. Also 4 in
> > Device Manager. So this is one more hurdle down. However, none of my
> > network adapters took - neither my motherboard lan or my Intel Pro/100 MT
> > Dual Port Server Adapter. So I will work on this next. Well making some
> > progress is encouraging.
> >
> > "KM" wrote:
> >
> >> 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
> >>
> >>
> >>
>
>
>
.
- References:
- RE: dual boot - Nvidia device driver
- From: ecoulson
- RE: dual boot - Nvidia device driver
- From: ecoulson
- Re: dual boot - Nvidia device driver
- From: KM
- Re: dual boot - Nvidia device driver
- From: ecoulson
- Re: dual boot - Nvidia device driver
- From: KM
- RE: dual boot - Nvidia device driver
- Prev by Date: Re: File Ownership Lost After FBA... Please Help!
- Next by Date: Re: OCX registration
- Previous by thread: Re: dual boot - Nvidia device driver
- Next by thread: Update of Tutorial Version 3 for USB BOOT
- Index(es):
Relevant Pages
|
