At the moment, the big "thud" in memory usage is games. Few games can take
advantage of more than 4gb of memory and some actually quit working if there
is more than 4gb of memory available to them. So it may not benefit you to
add more memory now and you might even see things that are working ... quit
working.


"Noel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> I am putting together a new build and since PC-6400 DDR2 is sooo cheap I
> thought I might consider 8GB on an X38 board.
>
> I already have 2x2GB dimms, and was guessing if I went to 8GB it might
> be nice to have 4 identical DIMMS, which are still available (ie,
> another 2x2gb of the pair I have now).
>
> Anyone have wisdom about this? My main uses NOW are MS Flight
> Simulator, Gigastudio, and both of those benefit from at least 3GB,
> beyond that I don't know. I don't forsee video editing . . .
>
> Thanks for your replies,
>
> Noel
>
>
> --
> Noel

Like I said, try it with pc5300, not pc6400. By the way, dual booting XP
and Vista on a production or primary home computer is not a good idea. All
of the VSS files used by Vista's recovery facilities are wiped out on each
boot into XP. That means restore points, previous versions files,
CompletePC Backup images, and backup files made by the new file backup
program just vanish. If you are testing or gaming this is not a big deal,
but if you are into videos and photos and such you might not want to risk
your capability of recovering from a file problem.

"Noel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> 'Richard G. Harper [MVP Wrote:
>> ;578589']At the moment, the big "thud" in memory usage is games. Few
>> games can take
>> advantage of more than 4gb of memory and some actually quit working if
>> there
>> is more than 4gb of memory available to them. So it may not benefit you
>> to
>> add more memory now and you might even see things that are working ...
>> quit
>> working.
>>
>> I guess everything will be on a case by case basis. I am def going to
>> dual boot to Vista 64 & XP 32, and so will just have to experiment and
>> see how it goes. The take home message everywhere I ask this question
>> is basically, "It all depends . . ." I wish to use 8GB for Gigastudio
>> primarily, on Vista 64, for which there is a new release.
>
>
> --
> Noel

In article <B490804C-0F36-42EF-B5D1-(E-Mail Removed)>, Colin Barnhorst
<(E-Mail Removed)> says...
> Like I said, try it with pc5300, not pc6400. By the way, dual booting XP
> and Vista on a production or primary home computer is not a good idea. All
> of the VSS files used by Vista's recovery facilities are wiped out on each
> boot into XP. That means restore points, previous versions files,
> CompletePC Backup images, and backup files made by the new file backup
> program just vanish. If you are testing or gaming this is not a big deal,
> but if you are into videos and photos and such you might not want to risk
> your capability of recovering from a file problem.

It's a good idea to use a 3th party bootmanager.

--
Met vriendelijke groeten, Jawade. Weer veel vernieuwd!
http://jawade.nl/ Met een mirror op http://jawade.fortunecity.com/
Bootmanager (+Vista), ClrMBR, DiskEditors, POP3lezer, Filebrowser,
Kalender, Webtellers en IP-log, Linux-Diskeditor, USB-stick tester

That has been tried since early in the beta test program and did no good.
None of the favorites among boot managers hide the Vista volume in such a
way as to prevent the problem.

"Jawade" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <B490804C-0F36-42EF-B5D1-(E-Mail Removed)>, Colin
> Barnhorst
> <(E-Mail Removed)> says...
>> Like I said, try it with pc5300, not pc6400. By the way, dual booting XP
>> and Vista on a production or primary home computer is not a good idea.
>> All
>> of the VSS files used by Vista's recovery facilities are wiped out on
>> each
>> boot into XP. That means restore points, previous versions files,
>> CompletePC Backup images, and backup files made by the new file backup
>> program just vanish. If you are testing or gaming this is not a big
>> deal,
>> but if you are into videos and photos and such you might not want to risk
>> your capability of recovering from a file problem.
>
> It's a good idea to use a 3th party bootmanager.
>
> --
> Met vriendelijke groeten, Jawade. Weer veel vernieuwd!
> http://jawade.nl/ Met een mirror op http://jawade.fortunecity.com/
> Bootmanager (+Vista), ClrMBR, DiskEditors, POP3lezer, Filebrowser,
> Kalender, Webtellers en IP-log, Linux-Diskeditor, USB-stick tester

Is this true if the OSs are on two different HDDs as well as when in 2
partitions on the same HDD?

"Colin Barnhorst" <(E-Mail Removed)> wrote in message
news:B490804C-0F36-42EF-B5D1-(E-Mail Removed)...
> Like I said, try it with pc5300, not pc6400. By the way, dual booting XP
> and Vista on a production or primary home computer is not a good idea.
> All of the VSS files used by Vista's recovery facilities are wiped out on
> each boot into XP. That means restore points, previous versions files,
> CompletePC Backup images, and backup files made by the new file backup
> program just vanish. If you are testing or gaming this is not a big deal,
> but if you are into videos and photos and such you might not want to risk
> your capability of recovering from a file problem.
>
> "Noel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> 'Richard G. Harper [MVP Wrote:
>>> ;578589']At the moment, the big "thud" in memory usage is games. Few
>>> games can take
>>> advantage of more than 4gb of memory and some actually quit working if
>>> there
>>> is more than 4gb of memory available to them. So it may not benefit you
>>> to
>>> add more memory now and you might even see things that are working ...
>>> quit
>>> working.
>>>
>>> I guess everything will be on a case by case basis. I am def going to
>>> dual boot to Vista 64 & XP 32, and so will just have to experiment and
>>> see how it goes. The take home message everywhere I ask this question
>>> is basically, "It all depends . . ." I wish to use 8GB for Gigastudio
>>> primarily, on Vista 64, for which there is a new release.
>>
>>
>> --
>> Noel
>

Volsnap.sys enumerates VSS files systemwide. It doesn't care about the
configuration. It does not distinguish between partitions or drives. It
only cares about volumes (things with drive letters).

"Curious" <(E-Mail Removed)> wrote in message
news:2978F06B-7BE7-4AA0-BE2A-(E-Mail Removed)...
> Is this true if the OSs are on two different HDDs as well as when in 2
> partitions on the same HDD?
>
> "Colin Barnhorst" <(E-Mail Removed)> wrote in message
> news:B490804C-0F36-42EF-B5D1-(E-Mail Removed)...
>> Like I said, try it with pc5300, not pc6400. By the way, dual booting XP
>> and Vista on a production or primary home computer is not a good idea.
>> All of the VSS files used by Vista's recovery facilities are wiped out on
>> each boot into XP. That means restore points, previous versions files,
>> CompletePC Backup images, and backup files made by the new file backup
>> program just vanish. If you are testing or gaming this is not a big
>> deal, but if you are into videos and photos and such you might not want
>> to risk your capability of recovering from a file problem.
>>
>> "Noel" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>
>>> 'Richard G. Harper [MVP Wrote:
>>>> ;578589']At the moment, the big "thud" in memory usage is games. Few
>>>> games can take
>>>> advantage of more than 4gb of memory and some actually quit working if
>>>> there
>>>> is more than 4gb of memory available to them. So it may not benefit you
>>>> to
>>>> add more memory now and you might even see things that are working ...
>>>> quit
>>>> working.
>>>>
>>>> I guess everything will be on a case by case basis. I am def going to
>>>> dual boot to Vista 64 & XP 32, and so will just have to experiment and
>>>> see how it goes. The take home message everywhere I ask this question
>>>> is basically, "It all depends . . ." I wish to use 8GB for Gigastudio
>>>> primarily, on Vista 64, for which there is a new release.
>>>
>>>
>>> --
>>> Noel
>>
>

In message <2978F06B-7BE7-4AA0-BE2A-(E-Mail Removed)>
"Curious" <(E-Mail Removed)> wrote:

>Is this true if the OSs are on two different HDDs as well as when in 2
>partitions on the same HDD?

Yes. Anything that mounts the drive will cause this issue.

It makes no difference which OS is installed first.

This is all by design in the sense that both XP and Vista are running as
designed. They just aren't designed to be run together on the same box
without measures to isolate Vista from XP.

Let me offer a partial analogy. Let's say you have been parking your
standard sized car in your garage for years. Now you decide to trade in the
sedan for a Hummer. You get home and discover that the Hummer won't fit in
the garage. Is it because the garage was poorly designed? No. Is it
because the Hummer was poorly designed? No. Each was designed OK and
neither malfunctions. The problem comes up when you try to combine the two.

That's how it is with XP and Vista. It is not because of a bug suddenly
appearing in XP. It hasn't. It isn't because of a bug in Vista. Nothing
like this happens when you run Vista by itself. The problem only appears
when you combine the two.

MS has made the decision not to do to XP what it would take to make XP's VSS
driver Vista compatible. It turns out that VSS is so pervasive that a
serious rewrite to XP would be required. Since multibooting is extremely
rare (only a tiny fraction of 1% of the Windows user base of hundreds of
millions do it), it just is not cost-effective for MS to do the rewrite when
the impact is so negligible. Of course a disproportiate number of users who
visit this newsgroup are technology enthusiasts so when you read this ng it
appears to be a bigger issue than it really is. It is our ox that has been
gored.

Obviously you can do as you like, but at least make an informed decision
based on what you use Vista for and the risks to your important data that is
involved when using XP on the same machine. For example, if you are into
things like photo-editing then the shadowcopies feature (the new Previous
Versions tab on the file properties page) may be very important to you.

The decision I made was to run XP on a different box. Another alternative I
use is to run XP in a virtual machine using Virtual PC 2007 on my Vista
machine. It just depends of what I want to do in XP as to which alternative
I use to do it.

"Noel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Colin Barnhorst;579100 Wrote:
>> Like I said, try it with pc5300, not pc6400. By the way, dual booting XP
>> and Vista on a production or primary home computer is not a good idea.
>> All
>> of the VSS files used by Vista's recovery facilities are wiped out on
>> each
>> boot into XP. That means restore points, previous versions files,
>> CompletePC Backup images, and backup files made by the new file backup
>> program just vanish.
>
> Ouch, how evil is that?! That is truly an awful design plan, and how
> could that not be intentional? Obviously I know very little about the
> whole issue, but from what you say Colin I can't of a more aweful design
> behavior to force people into Vista to stay. Sick!
>
> I keep reading all over the place of people dual booting this, but I
> haven't dug deep enough to discover what the pitfalls are. I HAVE a
> loosely formed impression that this issue occurs when you install Vista
> first. Is there anything to this? If what you say is true then I guess I
> will not be dual booting, and will just do the build with XP, and wait
> until XP is no longer EVER required. Guess I'll park my other 4gb of
> PC-6400 in a cool dry place until happier days. That's pathetic . . .
>
>
> --
> Noel

In article <415B1C40-FE9D-4C1E-8072-(E-Mail Removed)>, Colin Barnhorst
<(E-Mail Removed)> says...
> That has been tried since early in the beta test program and did no good.
> None of the favorites among boot managers hide the Vista volume in such a
> way as to prevent the problem.

I believe you don't have to hide the Vista volume if you use an
other bootmanager. On my site I present my bootmanager, but it is
in the Dutch language. It can hide with every startup by choice.

--
Met vriendelijke groeten, Jawade. Weer veel vernieuwd!
http://jawade.nl/ Met een mirror op http://jawade.fortunecity.com/
Bootmanager (+Vista), ClrMBR, DiskEditors, POP3lezer, Filebrowser,
Kalender, Webtellers en IP-log, Linux-Diskeditor, USB-stick tester

I don't know how yours works but all the ones tried could hide a volume from
user programs but could not hide the volume from XP's volsnap.sys. Be sure
you have verified that Vista VSS files persist after booting into XP in
other than safe mode (the problem does not occur if booting XP in safe mode
because volsnap.sys is one of the drivers not loaded in safe mode).

"Jawade" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <415B1C40-FE9D-4C1E-8072-(E-Mail Removed)>, Colin
> Barnhorst
> <(E-Mail Removed)> says...
>> That has been tried since early in the beta test program and did no good.
>> None of the favorites among boot managers hide the Vista volume in such a
>> way as to prevent the problem.
>
> I believe you don't have to hide the Vista volume if you use an
> other bootmanager. On my site I present my bootmanager, but it is
> in the Dutch language. It can hide with every startup by choice.
>
> --
> Met vriendelijke groeten, Jawade. Weer veel vernieuwd!
> http://jawade.nl/ Met een mirror op http://jawade.fortunecity.com/
> Bootmanager (+Vista), ClrMBR, DiskEditors, POP3lezer, Filebrowser,
> Kalender, Webtellers en IP-log, Linux-Diskeditor, USB-stick tester