chkinf bug: No )'s in the path so no DirectX in the path

Hi,
Running chkinf gives me:
\Utilities\Bin\x86 was unexpected at this time.

This is part of a DirectX install which adds the following to the path:
C:\Program Files\Microsoft DirectX SDK (April 2007)\Utilities\Bin\x86

I'm guessing the problem is this "for" line (about line 27):
for %%I in (%PATH%) do (
if exist %%~fsI\chkinf.bat (
set PLibPath=-I%%I
goto runit
)
The "if" may become a problem too.

I worked around the problem by modifying the path variable to not have
that directory in the path. I did this by:
1. Typing "echo %path%"
2. Copying the path to notepad
3. Deleting the problematic directory
4. Coping the new text for the path variable
5. typing "path=" followed by pasting the new list of directories

I'm not sure, but it appears another work around is to add the chkinf
directory to the beginning of the path variable.

I'm not sure where to report this issue, and my quick check doesn't show
any documentation on this issue. I hope this is the appropriate way to
get this fixed or at least documented. If not, please advise me.

Thanks,

Drew Daniels

Colin
Tue Jun 05 02:36:12 CDT 2007

This problem has been around for a while - its acknowledged by MS (they were
the ones who told me about it), just not fixed yet. There was another post
on this the other day by someone - I think they fixed it by using quotes
around the directx path spec.
(I was told its the spaces which cause the problem).

Most DTM bugs aren't documented, except here.....

"ddaniels@Linear Systems" <ddaniels@newsgroups.nospam> wrote in message
news:eHTfTXrpHHA.2372@TK2MSFTNGP02.phx.gbl...
> Hi,
> Running chkinf gives me:
> \Utilities\Bin\x86 was unexpected at this time.
>
> This is part of a DirectX install which adds the following to the path:
> C:\Program Files\Microsoft DirectX SDK (April 2007)\Utilities\Bin\x86
>
> I'm guessing the problem is this "for" line (about line 27):
> for %%I in (%PATH%) do (
> if exist %%~fsI\chkinf.bat (
> set PLibPath=-I%%I
> goto runit
> )
> The "if" may become a problem too.
>
> I worked around the problem by modifying the path variable to not have
> that directory in the path. I did this by:
> 1. Typing "echo %path%"
> 2. Copying the path to notepad
> 3. Deleting the problematic directory
> 4. Coping the new text for the path variable
> 5. typing "path=" followed by pasting the new list of directories
>
> I'm not sure, but it appears another work around is to add the chkinf
> directory to the beginning of the path variable.
>
> I'm not sure where to report this issue, and my quick check doesn't show
> any documentation on this issue. I hope this is the appropriate way to get
> this fixed or at least documented. If not, please advise me.
>
> Thanks,
>
> Drew Daniels

Colin
Tue Jun 05 02:38:33 CDT 2007

Just realised you may have actually hit this problem independantly rather
than from within DTM - chkinf is used there too though.

"ddaniels@Linear Systems" <ddaniels@newsgroups.nospam> wrote in message
news:eHTfTXrpHHA.2372@TK2MSFTNGP02.phx.gbl...
> Hi,
> Running chkinf gives me:
> \Utilities\Bin\x86 was unexpected at this time.
>
> This is part of a DirectX install which adds the following to the path:
> C:\Program Files\Microsoft DirectX SDK (April 2007)\Utilities\Bin\x86
>
> I'm guessing the problem is this "for" line (about line 27):
> for %%I in (%PATH%) do (
> if exist %%~fsI\chkinf.bat (
> set PLibPath=-I%%I
> goto runit
> )
> The "if" may become a problem too.
>
> I worked around the problem by modifying the path variable to not have
> that directory in the path. I did this by:
> 1. Typing "echo %path%"
> 2. Copying the path to notepad
> 3. Deleting the problematic directory
> 4. Coping the new text for the path variable
> 5. typing "path=" followed by pasting the new list of directories
>
> I'm not sure, but it appears another work around is to add the chkinf
> directory to the beginning of the path variable.
>
> I'm not sure where to report this issue, and my quick check doesn't show
> any documentation on this issue. I hope this is the appropriate way to get
> this fixed or at least documented. If not, please advise me.
>
> Thanks,
>
> Drew Daniels