Could I be fighting a "To much memory" problem?

I've been running my P5W DH Deluxe with 4 gig of ram for the last year and I
have been running into some strange problems that I think may well be a
conflict with the excessive ram I have installed on my mobo running XP
(32bit). Such as:

1) When I want to start my Hauppauge HVR-1800 tuner on my secondary monitor
I get a memory access error and the program errors out. It starts fine on
the primary monitor. I can drag the open window over to the secondary
monitor with no problem at all. But I must drag it back to the primary when
I exit the program or the next time I start the program it will error out on
the secondary monitor again.

2) I just upgraded my dual-monitor setup (Analogue VGA) with two Samsung
T220's (Digital) and when I move the MagicTune Premium program from the
primary monitor to the secondary monitor the program errors out with a
memory access error.

I have a feeling that the problem is the set-aside memory used for
exchanging data between the cpu and gpu in upper memory is conflicting with
the installed excess ram. I also believe this problem is due to sloppy
programming or resource calls to said memory that is causing the problem.

Does anyone have any ideas on this? Am I crazy or sound on this idea?

Help

William

What happens when you lower RAM to 2 GB?
I assume you have tried this.

"William" <nospam@pacifier.com> wrote in message
news:BZmdnUtGeMbWi_7VnZ2dnUVZ_hadnZ2d@posted.palin acquisition...
> I've been running my P5W DH Deluxe with 4 gig of ram for the last year and
> I have been running into some strange problems that I think may well be a
> conflict with the excessive ram I have installed on my mobo running XP
> (32bit). Such as:
>
> 1) When I want to start my Hauppauge HVR-1800 tuner on my secondary
> monitor I get a memory access error and the program errors out. It starts
> fine on the primary monitor. I can drag the open window over to the
> secondary monitor with no problem at all. But I must drag it back to the
> primary when I exit the program or the next time I start the program it
> will error out on the secondary monitor again.
>
> 2) I just upgraded my dual-monitor setup (Analogue VGA) with two Samsung
> T220's (Digital) and when I move the MagicTune Premium program from the
> primary monitor to the secondary monitor the program errors out with a
> memory access error.
>
> I have a feeling that the problem is the set-aside memory used for
> exchanging data between the cpu and gpu in upper memory is conflicting
> with the installed excess ram. I also believe this problem is due to
> sloppy programming or resource calls to said memory that is causing the
> problem.
>
> Does anyone have any ideas on this? Am I crazy or sound on this idea?
>
> Help
>
> William
>
>
>

go trying lowering to 2 or 3 GB as suggested by ytrewq

you can also look into configuring your GPU, main board with regard to
memory
or if you don't have any device driver problem with xp pro 74 and your
program works with within xp 64, you can try out xp pro 64 bit on another
partition.

"William" <nospam@pacifier.com> wrote in message
news:BZmdnUtGeMbWi_7VnZ2dnUVZ_hadnZ2d@posted.palin acquisition...
> I've been running my P5W DH Deluxe with 4 gig of ram for the last year and
I
> have been running into some strange problems that I think may well be a
> conflict with the excessive ram I have installed on my mobo running XP
> (32bit). Such as:
>
> 1) When I want to start my Hauppauge HVR-1800 tuner on my secondary
monitor
> I get a memory access error and the program errors out. It starts fine on
> the primary monitor. I can drag the open window over to the secondary
> monitor with no problem at all. But I must drag it back to the primary
when
> I exit the program or the next time I start the program it will error out
on
> the secondary monitor again.
>
> 2) I just upgraded my dual-monitor setup (Analogue VGA) with two Samsung
> T220's (Digital) and when I move the MagicTune Premium program from the
> primary monitor to the secondary monitor the program errors out with a
> memory access error.
>
> I have a feeling that the problem is the set-aside memory used for
> exchanging data between the cpu and gpu in upper memory is conflicting
with
> the installed excess ram. I also believe this problem is due to sloppy
> programming or resource calls to said memory that is causing the problem.
>
> Does anyone have any ideas on this? Am I crazy or sound on this idea?
>
> Help
>
> William
>
>
>

ytrewq and gg:

Thank you for your input. Samsung just released an update to MagicTune
program today, version 1.0.56. It works wonders on a dual display system
now. So this only leaves me having problems with the Hauppauge tuner for
now. Hauppauge hasn't updated their program since I purchased the card, at
the first of this year. I really do believe it is a function call problem
to higher memory. Perhaps I will send an e-mail to Hauppauge and see if
they care to do anything about it. I doubt it though.

I have been thinking about trying out a different tuner card after the first
of the year when NTSC goes off the air. Both ATI and AverMedia have nice
new tuner cards out that interest me.

William



"gg" <gg@Edm.noMail.net> wrote in message news:ERS8k.368$1o6.216@edtnps83...
> go trying lowering to 2 or 3 GB as suggested by ytrewq
>
> you can also look into configuring your GPU, main board with regard to
> memory
> or if you don't have any device driver problem with xp pro 74 and your
> program works with within xp 64, you can try out xp pro 64 bit on another
> partition.
>
> "William" <nospam@pacifier.com> wrote in message
> news:BZmdnUtGeMbWi_7VnZ2dnUVZ_hadnZ2d@posted.palin acquisition...
>> I've been running my P5W DH Deluxe with 4 gig of ram for the last year
>> and
> I
>> have been running into some strange problems that I think may well be a
>> conflict with the excessive ram I have installed on my mobo running XP
>> (32bit). Such as:
>>
>> 1) When I want to start my Hauppauge HVR-1800 tuner on my secondary
> monitor
>> I get a memory access error and the program errors out. It starts fine
>> on
>> the primary monitor. I can drag the open window over to the secondary
>> monitor with no problem at all. But I must drag it back to the primary
> when
>> I exit the program or the next time I start the program it will error out
> on
>> the secondary monitor again.
>>
>> 2) I just upgraded my dual-monitor setup (Analogue VGA) with two Samsung
>> T220's (Digital) and when I move the MagicTune Premium program from the
>> primary monitor to the secondary monitor the program errors out with a
>> memory access error.
>>
>> I have a feeling that the problem is the set-aside memory used for
>> exchanging data between the cpu and gpu in upper memory is conflicting
> with
>> the installed excess ram. I also believe this problem is due to sloppy
>> programming or resource calls to said memory that is causing the problem.
>>
>> Does anyone have any ideas on this? Am I crazy or sound on this idea?
>>
>> Help
>>
>> William
>>
>>
>>
>
>

So did the Hauppauge issue go away with 2GB memory?
======================
"William" <nospam@pacifier.com> wrote in message
news:cbCdnZJBne_9lfnVnZ2dnUVZ_oDinZ2d@posted.palin acquisition...
> ytrewq and gg:
>
> Thank you for your input. Samsung just released an update to MagicTune
> program today, version 1.0.56. It works wonders on a dual display system
> now. So this only leaves me having problems with the Hauppauge tuner for
> now. Hauppauge hasn't updated their program since I purchased the card,
> at the first of this year. I really do believe it is a function call
> problem to higher memory. Perhaps I will send an e-mail to Hauppauge and
> see if they care to do anything about it. I doubt it though.
>
> I have been thinking about trying out a different tuner card after the
> first of the year when NTSC goes off the air. Both ATI and AverMedia have
> nice new tuner cards out that interest me.
>
> William
>
>
>
> "gg" <gg@Edm.noMail.net> wrote in message
> news:ERS8k.368$1o6.216@edtnps83...
>> go trying lowering to 2 or 3 GB as suggested by ytrewq
>>
>> you can also look into configuring your GPU, main board with regard to
>> memory
>> or if you don't have any device driver problem with xp pro 74 and your
>> program works with within xp 64, you can try out xp pro 64 bit on another
>> partition.
>>
>> "William" <nospam@pacifier.com> wrote in message
>> news:BZmdnUtGeMbWi_7VnZ2dnUVZ_hadnZ2d@posted.palin acquisition...
>>> I've been running my P5W DH Deluxe with 4 gig of ram for the last year
>>> and
>> I
>>> have been running into some strange problems that I think may well be a
>>> conflict with the excessive ram I have installed on my mobo running XP
>>> (32bit). Such as:
>>>
>>> 1) When I want to start my Hauppauge HVR-1800 tuner on my secondary
>> monitor
>>> I get a memory access error and the program errors out. It starts fine
>>> on
>>> the primary monitor. I can drag the open window over to the secondary
>>> monitor with no problem at all. But I must drag it back to the primary
>> when
>>> I exit the program or the next time I start the program it will error
>>> out
>> on
>>> the secondary monitor again.
>>>
>>> 2) I just upgraded my dual-monitor setup (Analogue VGA) with two Samsung
>>> T220's (Digital) and when I move the MagicTune Premium program from the
>>> primary monitor to the secondary monitor the program errors out with a
>>> memory access error.
>>>
>>> I have a feeling that the problem is the set-aside memory used for
>>> exchanging data between the cpu and gpu in upper memory is conflicting
>> with
>>> the installed excess ram. I also believe this problem is due to sloppy
>>> programming or resource calls to said memory that is causing the
>>> problem.
>>>
>>> Does anyone have any ideas on this? Am I crazy or sound on this idea?
>>>
>>> Help
>>>
>>> William
>>>
>>>
>>>
>>
>>
>
>

"ytrewq" <ytrewq@uiop.com> wrote in message
news:UfWdnXnJvKz9KfnVnZ2dnUVZ_gqdnZ2d@supernews.co m...
> So did the Hauppauge issue go away with 2GB memory?


ytrewq:

I'm too lazy to pull out two sticks of memory just to check the Hauppauge.
This reminds me of an old joke my grandfather enjoyed telling......

Their was this man standing in the Out House. He was throwing large coins
down the toilet hole from his pocket. A man went up to him and asked why he
was throwing good money into the toilet. He said " You don't think I am
going down their just for a nickel do you?"

Well, this joke is sort of like the memory problem. You don't think I am
going to pull out two sticks of memory just for a tuner problem on a
secondary monitor do you? I will need a few more problems before I do that.

I was hoping that some of the people who posted having 4 gig of memory
causes problems with 32 bit os's would know something about this. I have
never seen anyone post exactly what those problems are. Still haven't, but
this sounds like it might be one of them.

William

Somewhere on teh intarweb "William" typed:
> "ytrewq" <ytrewq@uiop.com> wrote in message
> news:UfWdnXnJvKz9KfnVnZ2dnUVZ_gqdnZ2d@supernews.co m...
>> So did the Hauppauge issue go away with 2GB memory?
>
>
> ytrewq:
>
> I'm too lazy to pull out two sticks of memory just to check the
> Hauppauge. This reminds me of an old joke my grandfather enjoyed
> telling......
> Their was this man standing in the Out House. He was throwing large
> coins down the toilet hole from his pocket. A man went up to him and
> asked why he was throwing good money into the toilet. He said " You
> don't think I am going down their just for a nickel do you?"
>
> Well, this joke is sort of like the memory problem. You don't think
> I am going to pull out two sticks of memory just for a tuner problem
> on a secondary monitor do you? I will need a few more problems
> before I do that.
> I was hoping that some of the people who posted having 4 gig of memory
> causes problems with 32 bit os's would know something about this. I
> have never seen anyone post exactly what those problems are. Still
> haven't, but this sounds like it might be one of them.

Whu post all that? You could have just said that you're too **** lazy to try
it and prefer to waste other people's time instead.
--
Shaun.

DISCLAIMER: If you find a posting or message from me
offensive, inappropriate, or disruptive, please ignore it.
If you don't know how to ignore a posting, complain to
me and I will be only too happy to demonstrate... ;-)

"~misfit~" <misfit61nz@hooya.com.au> wrote in message
news:4865869a$1@news2.actrix.gen.nz...
> Somewhere on teh intarweb "William" typed:
>> "ytrewq" <ytrewq@uiop.com> wrote in message
>> news:UfWdnXnJvKz9KfnVnZ2dnUVZ_gqdnZ2d@supernews.co m...
>>> So did the Hauppauge issue go away with 2GB memory?
>>
>>
>> ytrewq:
>>
>> I'm too lazy to pull out two sticks of memory just to check the
>> Hauppauge. This reminds me of an old joke my grandfather enjoyed
>> telling......
>> Their was this man standing in the Out House. He was throwing large
>> coins down the toilet hole from his pocket. A man went up to him and
>> asked why he was throwing good money into the toilet. He said " You
>> don't think I am going down their just for a nickel do you?"
>>
>> Well, this joke is sort of like the memory problem. You don't think
>> I am going to pull out two sticks of memory just for a tuner problem
>> on a secondary monitor do you? I will need a few more problems
>> before I do that.
>> I was hoping that some of the people who posted having 4 gig of memory
>> causes problems with 32 bit os's would know something about this. I
>> have never seen anyone post exactly what those problems are. Still
>> haven't, but this sounds like it might be one of them.
>
> Whu post all that? You could have just said that you're too **** lazy to
> try it and prefer to waste other people's time instead.

Shawn:

You having a reading comprehension problem again? Did I hurt you
feelings?.... Read your own tag line again. Troll..... You started this.

It's nice to know you are reading all my posts just hoping for me to say
something wrong. Is this the best you can do? I've caught you posting a
number of zingers. I just don't want to get into a flame war with you and
give you a free education.

As long as you don't recommend something damaging to someone else's
equipment, I don't care what you post. It's obvious you have little
experience with computers or people.

William

> --
> Shaun.
>
> DISCLAIMER: If you find a posting or message from me
> offensive, inappropriate, or disruptive, please ignore it.
> If you don't know how to ignore a posting, complain to
> me and I will be only too happy to demonstrate... ;-)
>

Your computer uses up lower areas of memory mapping the bios of
various cards into the memory scheme and for all intents and purposes
pushes everything else up. It's a little difficult to explain how it
is done, but if your motherboard or operating system can only handle
32 bits and you have more memory that 4GB you lose what is on the high
end. So you start out with your motherboard BIOS which can take up to
4MB depending on how new it is. Then your video card can take another
32 to 512Mb depending on the card. If you have 2 memory cards multiply
that number by 2. You usually have a video card aperture setting in
the bios that can affect just how much memory the card consumes.
Changing this setting also has performance implications especially if
you are a gamer, but that will definitely affect how much total memory
the system will show usable on boot up. Other cards such as TV tuner
cards can also consume lower memory depending on their design,
drivers, etc. So the end result is that you snap in 4GB of memory and
when your computer boots up in 32 bit mode it says you only have 3.3GB
or some other value below 4GB. That's because 32 bits can only address
4GB and if you add some on the lower end before the system starts
using your memory sticks the address register runs out of bits before
it reaches the top.

If for some reason the bios or memory on all your devices and the
motherboard are not allocated, or are allocated in such a way that
they overlap, you are going to have problems. While pulling out 2GB
might solve the problem, I don't think that's the way to solve it. The
correct way to solve it is to make sure that each device that needs a
window into memory gets allocated properly and that they don't
interfere with each other. (Easy for me to say). But how do you do
that. In the old days they had switches on the cards so you could set
memory ranges, but now it may take a software of motherboard bios
setting. But if you do it right you will probably end up with
somewhere around 3GB of usable memory instead of 2 and you will still
have your dual channel intact.


On Fri, 27 Jun 2008 18:28:41 -0700, "William" <nospam@pacifier.com>
wrote:

>
>"~misfit~" <misfit61nz@hooya.com.au> wrote in message
>news:4865869a$1@news2.actrix.gen.nz...
>> Somewhere on teh intarweb "William" typed:
>>> "ytrewq" <ytrewq@uiop.com> wrote in message
>>> news:UfWdnXnJvKz9KfnVnZ2dnUVZ_gqdnZ2d@supernews.co m...
>>>> So did the Hauppauge issue go away with 2GB memory?
>>>
>>>
>>> ytrewq:
>>>
>>> I'm too lazy to pull out two sticks of memory just to check the
>>> Hauppauge. This reminds me of an old joke my grandfather enjoyed
>>> telling......
>>> Their was this man standing in the Out House. He was throwing large
>>> coins down the toilet hole from his pocket. A man went up to him and
>>> asked why he was throwing good money into the toilet. He said " You
>>> don't think I am going down their just for a nickel do you?"
>>>
>>> Well, this joke is sort of like the memory problem. You don't think
>>> I am going to pull out two sticks of memory just for a tuner problem
>>> on a secondary monitor do you? I will need a few more problems
>>> before I do that.
>>> I was hoping that some of the people who posted having 4 gig of memory
>>> causes problems with 32 bit os's would know something about this. I
>>> have never seen anyone post exactly what those problems are. Still
>>> haven't, but this sounds like it might be one of them.
>>
>> Whu post all that? You could have just said that you're too **** lazy to
>> try it and prefer to waste other people's time instead.
>
>Shawn:
>
>You having a reading comprehension problem again? Did I hurt you
>feelings?.... Read your own tag line again. Troll..... You started this.
>
>It's nice to know you are reading all my posts just hoping for me to say
>something wrong. Is this the best you can do? I've caught you posting a
>number of zingers. I just don't want to get into a flame war with you and
>give you a free education.
>
>As long as you don't recommend something damaging to someone else's
>equipment, I don't care what you post. It's obvious you have little
>experience with computers or people.
>
>William
>
>> --
>> Shaun.
>>
>> DISCLAIMER: If you find a posting or message from me
>> offensive, inappropriate, or disruptive, please ignore it.
>> If you don't know how to ignore a posting, complain to
>> me and I will be only too happy to demonstrate... ;-)
>>
>