server 2003 only use 25% of processor

[Ken]

When I run my VB.NET application, it loads a large amount of data upon
startup. When I checked Task Manager, it showed that roughly 25% +/- of the
processor was being used. When I run the same program on an XP desktop,
processor usage goes to 100% until all of the data is loaded. I checked the
WSRM (Windows System Resource Manager) and the program is not being limited
in it's processor or memory usage. Can anyone tell me why this occurs? The
..NET framework does not have anything to do with this, does it?

The machine is a HP server running Windows Server 2003. 2-gigs memory, xeon
processor.

[m.posseth]

does your server run in application mode ??

if not switch it to that mode and try again

"Ken" <ks***@s32443t.com> schreef in bericht
news:O4**************@tk2msftngp13.phx.gbl...

When I run my VB.NET application, it loads a large amount of data upon
startup. When I checked Task Manager, it showed that roughly 25% +/- of
the
processor was being used. When I run the same program on an XP desktop,
processor usage goes to 100% until all of the data is loaded. I checked
the
WSRM (Windows System Resource Manager) and the program is not being
limited
in it's processor or memory usage. Can anyone tell me why this occurs? The
.NET framework does not have anything to do with this, does it?

The machine is a HP server running Windows Server 2003. 2-gigs memory,
xeon
processor.

[Brian Henry]

Is it a dual xeon with Hyper Threading? if so you'd have 4 processors listed
in task manager.. and each one of them displays as 25% of the total process
usage... so if you had a single threaded app and it ran at 100% of one of
the cpu's it would only show up as 25% of the total processing power.

[Ken]

Are you talking about "ADAM" (Active Directory Application Mode)?

I also found this, but I don't think it is what you are talking about. It
concerns remote connections.

"If the Licensing or Terminal Server Mode value is Remote Desktop for
Administration or Remote Administration, you're limited to two connections
(plus a local console in Windows 2003) when you're in Remote Administration
mode. If the Licensing or Terminal Server Mode value is Application or
Terminal Server, you're in Application mode and in that mode can have
multiple concurrent connections, depending on the number of existing
licenses."

The programs I have written have primarily been used on Desktop computers -
Server 2003 is somewhat new to me. When I check "Manage your Server", it is
listed as a File Server.

Any more help would be appreciated, but if not, thanks for the help so far.

"m.posseth" <po*****@planet.nl> wrote in message
news:OB**************@TK2MSFTNGP09.phx.gbl...

does your server run in application mode ??

if not switch it to that mode and try again

"Ken" <ks***@s32443t.com> schreef in bericht
news:O4**************@tk2msftngp13.phx.gbl...

When I run my VB.NET application, it loads a large amount of data upon
startup. When I checked Task Manager, it showed that roughly 25% +/- of
the
processor was being used. When I run the same program on an XP desktop,
processor usage goes to 100% until all of the data is loaded. I checked
the
WSRM (Windows System Resource Manager) and the program is not being
limited
in it's processor or memory usage. Can anyone tell me why this occurs? The .NET framework does not have anything to do with this, does it?

The machine is a HP server running Windows Server 2003. 2-gigs memory,
xeon
processor.