Memory problem
Hello,
i have purchased a gigabyte motherboard (GA-5aa) and a AMD k6/2 350
cpu and 64 mb of pc 100 memory. It all installed correctly except
that the "Boot to OS/2" option in the BIOS had to be disabled or I
could not see any extended memory in OS/2. I'm very happy with this
combination. Yesterday I purchased another 64 mb RAM from a different
supplier and I cannot get OS/2 to "see" the second set of RAM. The
BIOS sees it and (gasp) even Win 95 sees it but OS/2 refuses. We
borrowed another 32 mb ram and OS/2 still refuses to see above 64 mg
irrespective of the combination. the 2 64 are different speeds(only 1
nano) but the 32 is the same speed as one of them. OS/2 does not
"trap" error it just doen't see it!!!
Fustrated in Canberra
Paul Clarke
ApprenticeRating: 0%, 0 votes
limitations. It's because some BIOSes report memory over 64MB in a
different wayand OS/2 used (in earlier versions) to use one way,
and the BIOS another. Fixpacks later cured this.
Please don't post inaccurate replies; keep quiet if you don't
understand the true technucal issues.
A pointless statement. OS/2 is just as much a real 32 bit OS as either
of these.
--
Bob Eager
rde at tavi.co.uk
PC Server 325; PS/2s 8595*3, 9595*3 (2*P60 + P90), 8535, 8570, 9556*2,
8580*6,
8557*2, 8550, 9577, 8530, P70, PC/AT..
Was this solution helpful? Show your Appreciation by rating it:
ApprenticeRating: 0%, 0 votes
help the original poster whatsover with your yahoo anonymous response, and
I think I'll now construct that "*@yahoo.com" filter I used to have in
ProNews.
Good luck,
Buddy
Buddy Donnelly
Was this solution helpful? Show your Appreciation by rating it:
ApprenticeRating: 0%, 0 votes
limitation, shockingly similar to DOS. So much for a 32-bit OS, but some
BIOSes have a " Sounds like that junk you bought (I'm not an AMD fan for any number of
reasons but the problem here is your motherboard) doesn't have the
parameter.
I'm sure there's a fixpak for Warp 4 (who uses Warp 3?) that solves this
issue.
Or go get a real 32-bit OS like BeOS or WinNT.
Was this solution helpful? Show your Appreciation by rating it:
ApprenticeRating: 0%, 0 votes
said:
Not sure if this is applicable, but is the memory over 64M cached? Some
MBs ( mine for instance...Intel HX chipset) required the installation of
tag ram (a very cheap $5 chip) in order to cache the memory. OS2 sees all
96 mb of ram on my machine which is made by several generic manufacturers.
Monroe Chasson
MR2ICE reg#51 and OS2
Was this solution helpful? Show your Appreciation by rating it:
ApprenticeRating: 0%, 0 votes
please excuse this if it a second attempt but the last one does don't
seem to have stuck.
I'm running W4 with FP 9. I have tired THESEUS since my last posting
and it also reports 64 meg.
and I won't mention the cricket if you don't.
Regards
Paul
Was this solution helpful? Show your Appreciation by rating it:
ApprenticeRating: 0%, 0 votes
Which version of OS/2? Warp 3 may require fixpack 17 or higher to be
applied before it'll see more than 64MB (some BIOS calls were added at
this level that let it detect these fixes in straight out of the box.
Second, what are you using to determine that OS/2 doesn't "see" the
memory? The Netfinity client (System Information Tool in Warp 3) has a bug
that makes it always report a maximum of 66175Kb even when more is present
and in use.
Trevor Hemsley, London, UK
( or )
Was this solution helpful? Show your Appreciation by rating it:
Post a New problem for IBM 64MB DDR NVIDIA Quadro NVS 280
Email this problem
Can you Help with these Graphics Cards problems?
Tags | Blog | Repair Directory | Extended Warranty | Partners | Jobs |
