This is a multi-part message in MIME format.
------=_NextPart_000_0009_01C86644.2594B0D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
"CADaholic" <CADaholic@[EMAIL PROTECTED]
> wrote in message =
news:014fce77-1373-4da3-beef-8b97ad7d93e0@[EMAIL PROTECTED]
I second that. I used the 3 gig switch for over a year and it worked
very well.
> Ben's comments show that a 64 bit system is a good way of =
eliminating the memory restrictions built into 32 bit systems. But also =
consider setting the 3 gig switch in the XP boot.ini file. It extends =
useable memory. The Microsoft website has intructions for how to do =
this. You may also find the XP Help on "bootcfg" useful. Or Google this =
NG for 3 gig switch as this topic has come up before, but not recently.
>
> David Janes
I've had good experience with it, too. As is Bertil, I was bumping into =
the memory ceiling, everything slowing down, freezing, cra****ng. Then IT =
installed the maximum 4 gigs of RAM, thinking this would cure the =
problem. It helped a little, but not enough until they set the /3G =
switch. It can have its down side as it reassigns a gig of system memory =
to user memory, but all the memory problems, slowness and cra****ng went =
away.
That said, it's the cheap and dirty way of extending the life of a =
system. And, if it doesn't work, if you're still hitting the ceiling, =
you are buying the 64 bit system. So, if it works, great, but recognize =
that it could be a tem****ary fix if your memory demands keep growing. =
Since memory has always come at a premium on the big, expensive =
workstations, Pro/e built in a lot of memory management tools that help =
greatly with the memory restrictions. I'm thinking of Simp Reps and =
shrinkwrapped assemblies for space claim objects and even the use of =
surface models which tend to be much lighter weight that hundreds of =
features. IOW, balancing the brute force method of bigger, faster =
hardware with some sophisticated techniques. The latter is where I have =
to most room to grow, the fewest people to convince, the most initiative =
and often, the biggest payoff.
David Janes
------=_NextPart_000_0009_01C86644.2594B0D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"CADaholic" <<A=20
href=3D"mailto:CADaholic@[EMAIL PROTECTED]
">CADaholic@[EMAIL PROTECTED]
>> wrote =
in message=20
<A=20
=
href=3D"news:014fce77-1373-4da3-beef-8b97ad7d93e0@[EMAIL PROTECTED]
">news:014fce77-1373-4da3-beef-8b97ad7d93e0@[EMAIL PROTECTED]
>...</DIV>I=20
second that. I used the 3 gig switch for over a year and it=20
worked<BR>very well.<BR><BR><BR>> Ben's comments show that a 64 bit =
system=20
is a good way of eliminating the memory restrictions built into 32 bit =
systems. But also consider setting the 3 gig switch in the XP boot.ini =
file.=20
It extends useable memory. The Microsoft website has intructions for =
how to do=20
this. You may also find the XP Help on "bootcfg" useful. Or Google =
this NG for=20
3 gig switch as this topic has come up before, but not=20
recently.<BR>><BR>> David Janes<BR></BLOCKQUOTE>
<DIV>I've had good experience with it, too. As is Bertil, I was bumping =
into the=20
memory ceiling, everything slowing down, freezing, cra****ng. Then IT =
installed=20
the maximum 4 gigs of RAM, thinking this would cure the problem. It =
helped a=20
little, but not enough until they set the /3G switch. It can have its =
down side=20
as it reassigns a gig of system memory to user memory, but all the =
memory=20
problems, slowness and cra****ng went away.</DIV>
<DIV> </DIV>
<DIV>That said, it's the cheap and dirty way of extending the life of a =
system.=20
And, if it doesn't work, if you're still hitting the ceiling, you are =
buying the=20
64 bit system. So, if it works, great, but recognize that it could be a=20
tem****ary fix if your memory demands keep growing. Since memory has =
always come=20
at a premium on the big, expensive workstations, Pro/e built in a lot of =
memory=20
management tools that help greatly with the memory restrictions. I'm =
thinking of=20
Simp Reps and shrinkwrapped assemblies for space claim objects and =
even the=20
use of surface models which tend to be much lighter weight that hundreds =
of=20
features. IOW, balancing the brute force method of bigger, faster =
hardware with=20
some sophisticated techniques. The latter is where I have to most room =
to grow,=20
the fewest people to convince, the most initiative and often, the =
biggest=20
payoff.</DIV>
<DIV> </DIV>
<DIV>David Janes</DIV></BODY></HTML>
------=_NextPart_000_0009_01C86644.2594B0D0--
|
