Memory conflict

We are installing a CTI 4 ports controller. We get a memory conflict at
all addresses but B0000. Which is video space. The installation works
but we get a video flash of trash as we call it during startup. What I
was looking for was a utility to look at memory to see what is
controlling what space. I am looking for something that I might be able
to move. We have disabled video caching.

Anybody got an idea? They are appreciated.


Thanks,


Larry

“Larry Sams” <imagine@galstar.com> wrote in message
news:3AC2CD61.263C2DF6@galstar.com…

We are installing a CTI 4 ports controller. We get a memory conflict at
all addresses but B0000. Which is video space. The installation works
but we get a video flash of trash as we call it during startup. What I
was looking for was a utility to look at memory to see what is
controlling what space. I am looking for something that I might be able
to move. We have disabled video caching.

You can use spatch and the memdev stuff available on QND to
read memory.

However that perticular area of memory is usually not control
by software, but by hardware. It is the user’s responsibility
to install all the hardware without conflict.

Anybody got an idea? They are appreciated.


Thanks,


Larry

“Mario Charest” <mcharest@antispam_zinformatic.com> wrote in message
news:99ve8q$gh3$1@inn.qnx.com…

“Larry Sams” <> imagine@galstar.com> > wrote in message
news:> 3AC2CD61.263C2DF6@galstar.com> …
We are installing a CTI 4 ports controller. We get a memory conflict at
all addresses but B0000. Which is video space. The installation works
but we get a video flash of trash as we call it during startup. What I
was looking for was a utility to look at memory to see what is
controlling what space. I am looking for something that I might be able
to move. We have disabled video caching.


You can use spatch and the memdev stuff available on QND to
read memory.

btw my spatch reports “Invalid Argument” error and after startup
dosn’t wanna to read /dev/shmem/Physical :confused:

However that perticular area of memory is usually not control
by software, but by hardware. It is the user’s responsibility
to install all the hardware without conflict.

// wbr

“ian zagorskih” <ianzag@novosoft-us.com> wrote in message
news:99vra3$ogh$1@inn.qnx.com…

“Mario Charest” <mcharest@antispam_zinformatic.com> wrote in message
news:99ve8q$gh3$> 1@inn.qnx.com> …


“Larry Sams” <> imagine@galstar.com> > wrote in message
news:> 3AC2CD61.263C2DF6@galstar.com> …
We are installing a CTI 4 ports controller. We get a memory conflict
at
all addresses but B0000. Which is video space. The installation
works
but we get a video flash of trash as we call it during startup. What
I
was looking for was a utility to look at memory to see what is
controlling what space. I am looking for something that I might be
able
to move. We have disabled video caching.


You can use spatch and the memdev stuff available on QND to
read memory.

btw my spatch reports “Invalid Argument” error and after startup
dosn’t wanna to read /dev/shmem/Physical > :confused:

I don’t beleive you can read /dev/shmem/Physical, it’s not a device

per se.

spatch uses read/write/open/close which /dev/shmem/Physical
doesn’t understand, that is why you must use the memdev program.

However that perticular area of memory is usually not control
by software, but by hardware. It is the user’s responsibility
to install all the hardware without conflict.


// wbr