VB.NET and Users

[M15t3r M4g1c]

All

I have an issue with a deployment of VB.NET I'd be interested in your
thoughts please.

I have rolled out VB.NET onto a box running W2K Advanced Server in
standalone mode running TSWeb. This box is a Dual Xeon 800+ with 3GB of
RAM.

Users connect to the box via the w3 interface and are happy with running
VB.NET for approx 18 users

As soon as more than 25+ users connect to the box and use VB.NET the box
grinds to a complete halt.

These are not *advanced* users of VB.NET and are simply creating simple code

How much RAM per users should I be spec'ing. MS tells me 64MB per user for
a TS connection and VB.NET will run inside 160MB. To be honest I feel this
a little on the lite side. W98 will run on a DX2/66 but you wouldn't want
to run it on type of hardware

Any help would be appreciated
--

If all you have is an axe, every problem looks like hours of fun.

[Lucas Tam]

"M15t3r M4g1c" <no*****@all.com> wrote in
news:0k***************@newsfe1-win.ntli.net:

All

I have an issue with a deployment of VB.NET I'd be interested in your
thoughts please.

I have rolled out VB.NET onto a box running W2K Advanced Server in
standalone mode running TSWeb. This box is a Dual Xeon 800+ with 3GB
of RAM.

Users connect to the box via the w3 interface and are happy with
running VB.NET for approx 18 users

As soon as more than 25+ users connect to the box and use VB.NET the
box grinds to a complete halt.

These are not *advanced* users of VB.NET and are simply creating
simple code

How much RAM per users should I be spec'ing. MS tells me 64MB per
user for a TS connection and VB.NET will run inside 160MB.

Out of curiousity, what database are you running?

And how much RAM does your application use?

You can always check if you need more ram on the server by checking the
performance monitor or the Windows task manager to see the amount of RAM
used on the server.
--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Bob Hollness]

"M15t3r M4g1c" <no*****@all.com> wrote in message
news:0k***************@newsfe1-win.ntli.net...

All

I have an issue with a deployment of VB.NET I'd be interested in your
thoughts please.

I have rolled out VB.NET onto a box running W2K Advanced Server in
standalone mode running TSWeb. This box is a Dual Xeon 800+ with 3GB of
RAM.

Users connect to the box via the w3 interface and are happy with running
VB.NET for approx 18 users

As soon as more than 25+ users connect to the box and use VB.NET the box
grinds to a complete halt.

These are not *advanced* users of VB.NET and are simply creating simple
code

How much RAM per users should I be spec'ing. MS tells me 64MB per user
for
a TS connection and VB.NET will run inside 160MB. To be honest I feel
this
a little on the lite side. W98 will run on a DX2/66 but you wouldn't want
to run it on type of hardware

Any help would be appreciated
--

If all you have is an axe, every problem looks like hours of fun.

Have you added the switch to tell windows to address more than 2GB of RAM in
one go?

--
Bob Hollness

-------------------------------------
I'll have a B please Bob

[M15t3r M4g1c]

Hi Bob

This is a new one on me. I've never heard of this setting before. Where is
this setting please. Windows is happy to display it has 3Gb of RAM installed

"Bob Hollness" <bo*@blockbuster.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

"M15t3r M4g1c" <no*****@all.com> wrote in message
news:0k***************@newsfe1-win.ntli.net...

All

I have an issue with a deployment of VB.NET I'd be interested in your
thoughts please.

I have rolled out VB.NET onto a box running W2K Advanced Server in
standalone mode running TSWeb. This box is a Dual Xeon 800+ with 3GB of
RAM.

Users connect to the box via the w3 interface and are happy with running
VB.NET for approx 18 users

As soon as more than 25+ users connect to the box and use VB.NET the box
grinds to a complete halt.

These are not *advanced* users of VB.NET and are simply creating simple
code

How much RAM per users should I be spec'ing. MS tells me 64MB per user
for
a TS connection and VB.NET will run inside 160MB. To be honest I feel
this
a little on the lite side. W98 will run on a DX2/66 but you wouldn't
want
to run it on type of hardware

Any help would be appreciated
--

If all you have is an axe, every problem looks like hours of fun.

Have you added the switch to tell windows to address more than 2GB of RAM
in one go?

--
Bob Hollness

-------------------------------------
I'll have a B please Bob

[Bob Hollness]

"M15t3r M4g1c" <no*****@all.com> wrote in message
news:eO*************@newsfe3-win.ntli.net...

Hi Bob

This is a new one on me. I've never heard of this setting before. Where
is this setting please. Windows is happy to display it has 3Gb of RAM
installed

"Bob Hollness" <bo*@blockbuster.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

"M15t3r M4g1c" <no*****@all.com> wrote in message
news:0k***************@newsfe1-win.ntli.net...

All

I have an issue with a deployment of VB.NET I'd be interested in your
thoughts please.

I have rolled out VB.NET onto a box running W2K Advanced Server in
standalone mode running TSWeb. This box is a Dual Xeon 800+ with 3GB of
RAM.

Users connect to the box via the w3 interface and are happy with running
VB.NET for approx 18 users

As soon as more than 25+ users connect to the box and use VB.NET the box
grinds to a complete halt.

These are not *advanced* users of VB.NET and are simply creating simple
code

How much RAM per users should I be spec'ing. MS tells me 64MB per user
for
a TS connection and VB.NET will run inside 160MB. To be honest I feel
this
a little on the lite side. W98 will run on a DX2/66 but you wouldn't
want
to run it on type of hardware

Any help would be appreciated
--

If all you have is an axe, every problem looks like hours of fun.

Have you added the switch to tell windows to address more than 2GB of RAM
in one go?

--
Bob Hollness

-------------------------------------
I'll have a B please Bob

Yes, it displays it but it cannot address it in one chunk. This is because
a 32-bit operating system can only address 4gb of ram. The address space is
usually split so that 2 GB of address space is directly accessible to the
application and the other 2 GB is only accessible to the Windows executive
software. To change this, amend your boot.ini file to show this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="????" /3GB

Obviously, your boot.ini WILL be different to this as I did this from
memory. So you SHOULD only need to add the /3GB switch to the file. It
would be wise to have a good backup first as this file is fairly important.

Let me know how you get on. Also, if it does not work, please post your
eventlog errors immediately before the "overflow" user connects and
afterwards.

--
Bob Hollness

-------------------------------------
I'll have a B please Bob

[Bob Hollness]

"M15t3r M4g1c" <no*****@all.com> wrote in message
news:0k***************@newsfe1-win.ntli.net...

All

I have an issue with a deployment of VB.NET I'd be interested in your
thoughts please.

I have rolled out VB.NET onto a box running W2K Advanced Server in
standalone mode running TSWeb. This box is a Dual Xeon 800+ with 3GB of
RAM.

Users connect to the box via the w3 interface and are happy with running
VB.NET for approx 18 users

As soon as more than 25+ users connect to the box and use VB.NET the box
grinds to a complete halt.

These are not *advanced* users of VB.NET and are simply creating simple
code

How much RAM per users should I be spec'ing. MS tells me 64MB per user
for
a TS connection and VB.NET will run inside 160MB. To be honest I feel
this
a little on the lite side. W98 will run on a DX2/66 but you wouldn't want
to run it on type of hardware

Any help would be appreciated
--

If all you have is an axe, every problem looks like hours of fun.

IMO it would be better to give the users the remote desktop software rather
than using TSWEB as it is slower (and cannot be customised at all) than the
installed software version, you can get this free from the MS website, it is
called "Remote Desktop Connection". It also allows you to get IIS of the
server which slows it down and will only cause you problems with Terminal
Server licensing problems if they hotdesk.

--
Bob Hollness

-------------------------------------
I'll have a B please Bob