Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

problem setting DWORD value with Component Designer

1 view
Skip to first unread message

Wolfgang Kaml

unread,
May 9, 2002, 12:07:18 PM5/9/02
to
I came up to a possible bug in the Component and Target Designer.

I have the need to set a registry value called "XlateXHigh" to type "DWORD"
and the data should have the value "0xffffe719". This is the value which I
see when I use my regular Windows XP box and the regedit on that machine to
view the variable and its setting.

I have the need to transfer that DWORD variable with the value "0xffffe719"
to my XPembedded machine. I use a custom component which I created in the
Component Designer and created that variable name. I set the type of the
variable to DWORD, but as soon as I type in the number 4294960921(which
represents "0xffffe719", I get the following error message:
The integer you have typed is out of range. Please type a number
between -2147483647 and 2147483647 (or 0x00000000 and 0x7FFFFFFF).

Any ideas of how I can set my registry variable to the DWORD value which I
need?


Thank you,
Wolfgang


Juergen Striegel

unread,
May 17, 2002, 7:11:31 AM5/17/02
to
> I have the need to set a registry value called "XlateXHigh" to type
"DWORD"
> and the data should have the value "0xffffe719". This is the value which I
> see when I use my regular Windows XP box and the regedit on that machine
to
> view the variable and its setting.

Seems to be the Elotouch Serial driver... :-)
0xfff... means a negative integer number. Try to enter it's decimal
counterpart in TD. It's not very amusant that TD and regedit doesn't speak
the same language...

MS Calculator:
- switch to Hex
- Set size to DWord
- enter the 0xfff number
- press +/-
- select Dez
- press +/-
that's the value to enter in TD...

Juergen

Jon Fincher (MS)

unread,
May 20, 2002, 4:56:23 PM5/20/02
to
"Juergen Striegel" <p...@jstriegel.nospam.de> wrote in
news:OIKGbOZ$BHA.2196@tkmsftngp04:

You've found the workaround, Juergen. This has been entered as a bug -
no idea if it will be in SP1 or not, but it's filed and in a dev's hands
now.

--
--Jon, MS

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

0 new messages