PC Review Forums Newsgroups Windows XP Windows XP Embedded Re: Strange behavior INF file and Component Designer (0/1)

Reply

Re: Strange behavior INF file and Component Designer (0/1)

 
Thread Tools Rate Thread
Old 28-08-2003, 04:13 PM   #1
Brad Combs
Guest
 
Posts: n/a
Default Re: Strange behavior INF file and Component Designer (0/1)


Pieter,

I tried to import the inf, and got hte same results. If manually changing it
worked I'd just leave it as is. If you want CD to get it right the first
time jsut choose "custom" from the parsing options and add the needed
sections of the .inf to the list under it's appropriate category. Make sure
to leave the [] off of the entry. Then click the import as usual. I tried
this with some success with your inf, so you should be able to make it work.
HTH,

Brad Combs
Imago Technologies

"Pieter" <Pieter@noemail.invallid> wrote in message
news:78srkvgt9j4d2jijf8k5bs9n5bfj8okfnl@4ax.com...
> Hi,
>
> Attached are two files: snxpcip.inf and snxpcip.sld.
> The SLD file is created by importing de INF file in Component
> Designer.
> The INF file contains settings and drivers for both Windows 2000 and
> Windows XP.
>
> After importing the file a PCI Serial Port driver is created. However
> one file and two recourses are wrong.
> The file in the component is SNXPSER.SYS. This is the windows 2000
> driver. The XP driver is SNXPSERX.SYS.
> In the resource Service Data the ServiceBinairy is SNXPSER.SYS. This
> should be SNXPSERX.SYS. and the ServiceName is SNXPSER. This should be
> SNXPSERX.
> In the resource PnP Device ID the ServiceName is SNXPSER. This should
> be SNXPSERX.
> All these items are imported from the win2000 sections in the INF
> file.
>
> When I changed these items in de SLD file the component is installed
> correct.
>
> Is this a bug in Component Designer or is the INF file not correct?
>
>
> Regards,
>
> Pieter
>



  Reply With Quote
Old 28-08-2003, 06:15 PM   #2
Andy Allred [MS]
Guest
 
Posts: n/a
Default Re: Strange behavior INF file and Component Designer (0/1)

This is a known issue with CD.

What's happening is that when the manufacturer name has a comma in it, CD
ignores everything past the comma and only sees one entry in this case it
sees "DeviceList" and doesn't see this "DeviceList,NTx86.5.1". The XP
driver/service info is under this section "[DeviceList.NTx86.5.1]", so CD
only processes the section it did see which is the Win2k stuff under
"[DeviceList]". I've copied the sections i'm referring to at the bottom of
my message pointing out the sections i'm referring to.
To work around this, either modify the inf so the manufacturer section reads
"%MFGNAME%=DeviceList.NTx86.5.1" notice the dot in place of the comma?
Or you can do a custom import in CD and tell it the manufacturer section it
should process with the comma like this: "DeviceList,NTx86.5.1", then CD
will process it.
-Andy


[Manufacturer]
NOTE the COMMA===>>> %MFGNAME%=DeviceList,NTx86.5.1

NOTE, now there is no COMMA===>>> [DeviceList.NTx86.5.1]
%S_DESCRIPTION%=SDriverInstall_XP, SNXPCARD_SERP
%P_ECP_DESCRIPTION%=PDriverInstall_XP, SNXPCARD_PARPECP
%P_SPP_DESCRIPTION%=PDriverInstall_XP, SNXPCARD_PARPSPP

[DeviceList]
%S_DESCRIPTION%=SDriverInstall, SNXPCARD_SERP
%P_ECP_DESCRIPTION%=PDriverInstall, SNXPCARD_PARPECP
%P_SPP_DESCRIPTION%=PDriverInstall, SNXPCARD_PARPSPP

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


"Brad Combs" <brad@imagotechnologies.com> wrote in message
news:e4cX0YXbDHA.1940@TK2MSFTNGP10.phx.gbl...
> Pieter,
>
> I tried to import the inf, and got hte same results. If manually changing

it
> worked I'd just leave it as is. If you want CD to get it right the first
> time jsut choose "custom" from the parsing options and add the needed
> sections of the .inf to the list under it's appropriate category. Make

sure
> to leave the [] off of the entry. Then click the import as usual. I tried
> this with some success with your inf, so you should be able to make it

work.
> HTH,
>
> Brad Combs
> Imago Technologies
>
> "Pieter" <Pieter@noemail.invallid> wrote in message
> news:78srkvgt9j4d2jijf8k5bs9n5bfj8okfnl@4ax.com...
> > Hi,
> >
> > Attached are two files: snxpcip.inf and snxpcip.sld.
> > The SLD file is created by importing de INF file in Component
> > Designer.
> > The INF file contains settings and drivers for both Windows 2000 and
> > Windows XP.
> >
> > After importing the file a PCI Serial Port driver is created. However
> > one file and two recourses are wrong.
> > The file in the component is SNXPSER.SYS. This is the windows 2000
> > driver. The XP driver is SNXPSERX.SYS.
> > In the resource Service Data the ServiceBinairy is SNXPSER.SYS. This
> > should be SNXPSERX.SYS. and the ServiceName is SNXPSER. This should be
> > SNXPSERX.
> > In the resource PnP Device ID the ServiceName is SNXPSER. This should
> > be SNXPSERX.
> > All these items are imported from the win2000 sections in the INF
> > file.
> >
> > When I changed these items in de SLD file the component is installed
> > correct.
> >
> > Is this a bug in Component Designer or is the INF file not correct?
> >
> >
> > Regards,
> >
> > Pieter
> >

>
>



  Reply With Quote
Old 28-08-2003, 06:38 PM   #3
Andy Allred [MS]
Guest
 
Posts: n/a
Default Re: Strange behavior INF file and Component Designer (0/1)

FYI, Lynda wrote a great tip article that discusses this issue:
http://www.microsoft.com/windows/em...rivererrors.asp

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


"Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
news:e6YjCgYbDHA.1128@tk2msftngp13.phx.gbl...
> This is a known issue with CD.
>
> What's happening is that when the manufacturer name has a comma in it, CD
> ignores everything past the comma and only sees one entry in this case it
> sees "DeviceList" and doesn't see this "DeviceList,NTx86.5.1". The XP
> driver/service info is under this section "[DeviceList.NTx86.5.1]", so CD
> only processes the section it did see which is the Win2k stuff under
> "[DeviceList]". I've copied the sections i'm referring to at the bottom of
> my message pointing out the sections i'm referring to.
> To work around this, either modify the inf so the manufacturer section

reads
> "%MFGNAME%=DeviceList.NTx86.5.1" notice the dot in place of the comma?
> Or you can do a custom import in CD and tell it the manufacturer section

it
> should process with the comma like this: "DeviceList,NTx86.5.1", then CD
> will process it.
> -Andy
>
>
> [Manufacturer]
> NOTE the COMMA===>>> %MFGNAME%=DeviceList,NTx86.5.1
>
> NOTE, now there is no COMMA===>>> [DeviceList.NTx86.5.1]
> %S_DESCRIPTION%=SDriverInstall_XP, SNXPCARD_SERP
> %P_ECP_DESCRIPTION%=PDriverInstall_XP, SNXPCARD_PARPECP
> %P_SPP_DESCRIPTION%=PDriverInstall_XP, SNXPCARD_PARPSPP
>
> [DeviceList]
> %S_DESCRIPTION%=SDriverInstall, SNXPCARD_SERP
> %P_ECP_DESCRIPTION%=PDriverInstall, SNXPCARD_PARPECP
> %P_SPP_DESCRIPTION%=PDriverInstall, SNXPCARD_PARPSPP
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no

rights.
> ==========================================================
>
>
> "Brad Combs" <brad@imagotechnologies.com> wrote in message
> news:e4cX0YXbDHA.1940@TK2MSFTNGP10.phx.gbl...
> > Pieter,
> >
> > I tried to import the inf, and got hte same results. If manually

changing
> it
> > worked I'd just leave it as is. If you want CD to get it right the first
> > time jsut choose "custom" from the parsing options and add the needed
> > sections of the .inf to the list under it's appropriate category. Make

> sure
> > to leave the [] off of the entry. Then click the import as usual. I

tried
> > this with some success with your inf, so you should be able to make it

> work.
> > HTH,
> >
> > Brad Combs
> > Imago Technologies
> >
> > "Pieter" <Pieter@noemail.invallid> wrote in message
> > news:78srkvgt9j4d2jijf8k5bs9n5bfj8okfnl@4ax.com...
> > > Hi,
> > >
> > > Attached are two files: snxpcip.inf and snxpcip.sld.
> > > The SLD file is created by importing de INF file in Component
> > > Designer.
> > > The INF file contains settings and drivers for both Windows 2000 and
> > > Windows XP.
> > >
> > > After importing the file a PCI Serial Port driver is created. However
> > > one file and two recourses are wrong.
> > > The file in the component is SNXPSER.SYS. This is the windows 2000
> > > driver. The XP driver is SNXPSERX.SYS.
> > > In the resource Service Data the ServiceBinairy is SNXPSER.SYS. This
> > > should be SNXPSERX.SYS. and the ServiceName is SNXPSER. This should be
> > > SNXPSERX.
> > > In the resource PnP Device ID the ServiceName is SNXPSER. This should
> > > be SNXPSERX.
> > > All these items are imported from the win2000 sections in the INF
> > > file.
> > >
> > > When I changed these items in de SLD file the component is installed
> > > correct.
> > >
> > > Is this a bug in Component Designer or is the INF file not correct?
> > >
> > >
> > > Regards,
> > >
> > > Pieter
> > >

> >
> >

>
>



  Reply With Quote
Old 29-08-2003, 12:00 PM   #4
Pieter
Guest
 
Posts: n/a
Default Re: Strange behavior INF file and Component Designer (0/1)

OK.

Thanks for the information

Pieter


On Thu, 28 Aug 2003 10:38:13 -0700, "Andy Allred [MS]"
<andyall@online.microsoft.com> wrote:

>FYI, Lynda wrote a great tip article that discusses this issue:
>http://www.microsoft.com/windows/em...rivererrors.asp
>
>Andy


  Reply With Quote
Reply



Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off