🚀 go-pugleaf

"LarryJ" <LarryJ33@ev1.net> wrote in message
news:408ae02c$1@newsgroups.borland.com...

> I convert the unsigned long into an AnsiString using IntToStr()
> and then show the number in an Edit box. The problem I am
> having is that the hard drive serial number sometimes show up
> in the edit box as a negative number which should not be
> possible using an unsigned long.

IntToStr() does not directly support unsigned values at all, so any unsigned
value will get implicitally converted to a signe values instead.  As such,
any unsigned value above 2,147,483,647 will appear as negative.

Which version of BCB are you actually using?  In BCB 5 and 6, IntToStr()
supports __int64 as well as int, so you can cast the unsigned value to
__int64 to order to prevent negative values.  Otherwise, don't use
IntToStr() to begin with, but instead pass the unsigned value to the edit
box directly since AnsiString has always had a constructor that accepts
unsigned values.

> Why are some people getting these bad results?

Because you are misusing the value.

> CompNum = IntToStr(volser);

Change that to this instead:

    CompNum = IntToStr((__int64)volser);

Or just:

    CompNum = volser;


Gambit