Read that some motherboards are incapable of caching memory > 64MB ;
Are dell dimension/optiplex okay in this respect ?
Thanks,
-Ram
Read that some motherboards are incapable of caching memory > 64MB ;
Are dell dimension/optiplex okay in this respect ?
Thanks,
-Ram
Really kinda tough to say, especially since it could very wellQuote:>Read that some motherboards are incapable of caching memory > 64MB ;
>Are dell dimension/optiplex okay in this respect ?
Now, to be a bit more specific about this, if you want to know
for certain whether your motherboard will cache more then 64MB of
memory, you'll have to open up the case and check to see what chipset
your motherboard has. If it's an Intel 430FX, 430VX or 430TX chipset,
or a SiS 5571 chipset, then no, it's not capable of caching more then
64MB of memory. The Intel VX and TX chipsets are particularly common
among consumer grade systems, and AFAIK nearly everyone except Compaq
uses one of those two chipsets for most of their systems. Compaq,
however, uses the Via VP2 chipset, which is capable of cache more then
64MB of memory, with sufficient tag ram (which probably is not
provided). The Intel 430HX (used almost exclusivly on Pentium class
workstation and server type systems, but rarely in prebuilt consumer
type systems) and the Ali Aladdin IV chipset are in the same boat, and
I believe the earlier Via chipset (the VP1 and VPX) are as well. That
pretty much sums up all the chipsets you're likely to find in your
system, although it's certainly possible that there is some lesser
known one in there, such as an Opti chipset, in which case I can't be
of too much help. Anyway, if you do determine that the chipset used
is capable of caching more then 64MB of memory, then you'll have to
determine if you've got sufficient tag ram, which is most likely not
the case.
Anthony Hill | Sig files? SIG FILES?! What the
Hi Shell Gurus:
I am all confused here. Consider the following two commands:
$ cmd 2>&1 | tee logfile
$ cmd 2>&1 > logfile
In the first case both stderr and stdout go to the logfile but not in the
second case. Can someone explain me the reason. This is ksh 93. Is the
shell smart to look ahead of 2>&1 construct to see if the output is
actually going to a pipe??
Thanks
-Ajay
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ajay Matai Email: matai<at>bigfoot<dot>com
2. Auto-ping or keep-alive utility?
3. &&&&----Looking for a unix shell------&&&&&
5. ppp && PPPoE && ADSL && net && buffer(s)
7. 没有人用中文吗?
9. Q: 128 MB, 64MB cachable -> 64MB RAM disk, swap space?
10. HELP: 2>&1 > /dev/null != 2>&- > /dev/null ???
11. &&&&&& SUGGESTION ??? &&&&&&&&
12. *&& << 1GB >> Flash Memory Drive (&(*