RegExp to find hex value 0D fails

I started this in the VBScript group and after much furious head-scratching,
one of the respondents suggested that I try this group, on the offhand
chance that it is a Vista problem.

I'm running a Czech OEM version of Vista on a Fujitsu Siemens Amilo
notebook, SP1 installed a few months ago.

The problem I'm having is using a regular expression in VBScript. My match
string includes \x8D, that is, chr(141), but the regexp function fails to
locate occurrences that I know are there. The problem appears to be
specifically with the \x parameter and the 8D value. When I use \x with
other values, it works fine, and when I examine the file I'm scanning with
INSTR, the 141 character is there, but the combination doesn't work. I've
tried switching locales in the script, no help, and all the people who
responded to me says it works fine on their English-speaking machines - only
mine is uncooperative. Does this ring any bells with anyone?

Petr



--
This e-mail address is fake, to keep spammers and their address harvesters
out of my hair. If you need to get in touch personally, I am 'pdanes' and I
use yahoo mail. But please use the newsgroups whenever possible, so that all
may benefit from the exchange of ideas.

Petr

I do not know who suggested this vista group but they were off by a mile. You need
to repost this to the following newsgroup that works with vbscript in all MS
Operating Systems

news://msnews.microsoft.com/microsof...ipting.vbscipt

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Petr Danes" <> wrote in message
news:%...
>I started this in the VBScript group and after much furious head-scratching, one of
>the respondents suggested that I try this group, on the offhand chance that it is a
>Vista problem.
>
> I'm running a Czech OEM version of Vista on a Fujitsu Siemens Amilo notebook, SP1
> installed a few months ago.
>
> The problem I'm having is using a regular expression in VBScript. My match string
> includes \x8D, that is, chr(141), but the regexp function fails to locate
> occurrences that I know are there. The problem appears to be specifically with the
> \x parameter and the 8D value. When I use \x with other values, it works fine, and
> when I examine the file I'm scanning with INSTR, the 141 character is there, but
> the combination doesn't work. I've tried switching locales in the script, no help,
> and all the people who responded to me says it works fine on their
> English-speaking machines - only mine is uncooperative. Does this ring any bells
> with anyone?
>
> Petr
>
>
>
> --
> This e-mail address is fake, to keep spammers and their address harvesters out of
> my hair. If you need to get in touch personally, I am 'pdanes' and I use yahoo
> mail. But please use the newsgroups whenever possible, so that all may benefit
> from the exchange of ideas.
>
>

Hi Peter,

yes, that is the natural group for scripting isues, and as I wrote, that was
where I started the discussion. After several days of discussion, with no
resolution, someone suggested that I try the Vista group, since all the
people who responded had English OSs, and the regexp problem does not occur
on their machines, whereas I have a Czech version, and the best that any of
us were able to determine was that it seemed to be related to locale and
nationality somehow. So the thought was that maybe there is something
peculiar about the Czech version of Vista, and maybe someone here might know
of it. I realize that this is not scripting group, and am not asking for
help debugging my script. It works fine on English-speaking machines, and is
written correctly according to all the documentation that anyone was able to
find. It just doesn't work on my Czech machine.

Petr



"Peter Foldes" <> pí¹e v diskusním pøíspìvku
news:...
> Petr
>
> I do not know who suggested this vista group but they were off by a mile.
> You need to repost this to the following newsgroup that works with
> vbscript in all MS Operating Systems
>
> news://msnews.microsoft.com/microsof...ipting.vbscipt
>
> --
> Peter
>
> Please Reply to Newsgroup for the benefit of others
> Requests for assistance by email can not and will not be acknowledged.
>
> "Petr Danes" <> wrote in message
> news:%...
>>I started this in the VBScript group and after much furious
>>head-scratching, one of the respondents suggested that I try this group,
>>on the offhand chance that it is a Vista problem.
>>
>> I'm running a Czech OEM version of Vista on a Fujitsu Siemens Amilo
>> notebook, SP1 installed a few months ago.
>>
>> The problem I'm having is using a regular expression in VBScript. My
>> match string includes \x8D, that is, chr(141), but the regexp function
>> fails to locate occurrences that I know are there. The problem appears to
>> be specifically with the \x parameter and the 8D value. When I use \x
>> with other values, it works fine, and when I examine the file I'm
>> scanning with INSTR, the 141 character is there, but the combination
>> doesn't work. I've tried switching locales in the script, no help, and
>> all the people who responded to me says it works fine on their
>> English-speaking machines - only mine is uncooperative. Does this ring
>> any bells with anyone?
>>
>> Petr
>>
>>
>>
>> --
>> This e-mail address is fake, to keep spammers and their address
>> harvesters out of my hair. If you need to get in touch personally, I am
>> 'pdanes' and I use yahoo mail. But please use the newsgroups whenever
>> possible, so that all may benefit from the exchange of ideas.
>>
>>
>

Sorry Petr but I cannot help you out here. VBS does work on Vista but I cannot help
you out with script issues on the Czech Vista. Are you scripting it in the Czech
language ? Maybe try scripting it in Eng and do a direct back at the end .That is a
possibility

The other VBS newsgroups that is available are 1 in Chinese and one in the inetsdk
environment

But there is many available in the public.scripting in Italian,German,French and
English


--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Petr Danes" <> wrote in message
news:...
> Hi Peter,
>
> yes, that is the natural group for scripting isues, and as I wrote, that was where
> I started the discussion. After several days of discussion, with no resolution,
> someone suggested that I try the Vista group, since all the people who responded
> had English OSs, and the regexp problem does not occur on their machines, whereas
> I have a Czech version, and the best that any of us were able to determine was
> that it seemed to be related to locale and nationality somehow. So the thought was
> that maybe there is something peculiar about the Czech version of Vista, and maybe
> someone here might know of it. I realize that this is not scripting group, and am
> not asking for help debugging my script. It works fine on English-speaking
> machines, and is written correctly according to all the documentation that anyone
> was able to find. It just doesn't work on my Czech machine.
>
> Petr
>
>
>
> "Peter Foldes" <> pí¹e v diskusním pøíspìvku
> news:...
>> Petr
>>
>> I do not know who suggested this vista group but they were off by a mile. You
>> need to repost this to the following newsgroup that works with vbscript in all MS
>> Operating Systems
>>
>> news://msnews.microsoft.com/microsof...ipting.vbscipt
>>
>> --
>> Peter
>>
>> Please Reply to Newsgroup for the benefit of others
>> Requests for assistance by email can not and will not be acknowledged.
>>
>> "Petr Danes" <> wrote in message
>> news:%...
>>>I started this in the VBScript group and after much furious head-scratching, one
>>>of the respondents suggested that I try this group, on the offhand chance that it
>>>is a Vista problem.
>>>
>>> I'm running a Czech OEM version of Vista on a Fujitsu Siemens Amilo notebook,
>>> SP1 installed a few months ago.
>>>
>>> The problem I'm having is using a regular expression in VBScript. My match
>>> string includes \x8D, that is, chr(141), but the regexp function fails to
>>> locate occurrences that I know are there. The problem appears to be specifically
>>> with the \x parameter and the 8D value. When I use \x with other values, it
>>> works fine, and when I examine the file I'm scanning with INSTR, the 141
>>> character is there, but the combination doesn't work. I've tried switching
>>> locales in the script, no help, and all the people who responded to me says it
>>> works fine on their English-speaking machines - only mine is uncooperative. Does
>>> this ring any bells with anyone?
>>>
>>> Petr
>>>
>>>
>>>
>>> --
>>> This e-mail address is fake, to keep spammers and their address harvesters out
>>> of my hair. If you need to get in touch personally, I am 'pdanes' and I use
>>> yahoo mail. But please use the newsgroups whenever possible, so that all may
>>> benefit from the exchange of ideas.
>>>
>>>
>>
>