Uncle Meat wrote:
>
> Another possibility is that the video memory is taken from the ram (had one
> once that did that) and it's leaving a hole in memory.
Turned out to be one of those shared memory video cards. reduce my
mem=... statement by the appropriate amount did the trick. Belated
thank
Thanks to all who replied, you've given me a couple ideas to try.
Sorry if I don't quote you all here, but you know who you are.
> On 14-Oct-2000 Jonathan Wilson spoke something to the effect:
> > I could be very wrong, but I thought the proper thing was mem="128M".
> >
> > Did you check the lil
On 14-Oct-2000 Jonathan Wilson spoke something to the effect:
> I could be very wrong, but I thought the proper thing was mem="128M".
>
> Did you check the lilo docs?
>
> Other then that, I"d like to say that there's probably nothing worse then
> bad RAM. It very well may be bad - consider tryi
On Fri, 13 Oct 2000, Jonathan Wilson wrote:
> I could be very wrong, but I thought the proper thing was mem="128M".
>
> Did you check the lilo docs?
>
> Other then that, I"d like to say that there's probably nothing worse then bad RAM.
>It very well may be bad - consider trying a new stick. Ge
I could be very wrong, but I thought the proper thing was mem="128M".
Did you check the lilo docs?
Other then that, I"d like to say that there's probably nothing worse then bad RAM. It
very well may be bad - consider trying a new stick. Get PNY, Kensington or Corsair.
And do /not/ get ram with
PROTECTED]]On Behalf Of wyrd
> Sent: Friday, October 13, 2000 6:50 PM
> To: [EMAIL PROTECTED]
> Subject: odd memory access problem
>
>
>
> Hopefully someone here has seen something like the problem
> I'm having.
>
> In a moment of weakness my employer bought a c
Hopefully someone here has seen something like the problem
I'm having.
In a moment of weakness my employer bought a cheapo 450MHz PIII
system ( A Fry's special for those that might know what that means).
It ran NT until this week when I wiped it and installed Linux.
Unfortunately Linux can see
