s32935k@taltta.hut.fi (Carl Torsten Stenholm) (07/12/89)
I just purchased an *livetti (I think the number was M380), anyway it has:
80386, 81 M harddisk, 20 MHz clock, 1 M memory.
The problem is this 1 M memory. The startup system check tells me:
Main memory 640 K OK
Dedicated Mem 384 K OK
I just cant use these 384K of "dedicated memory". I called the dealer
and he told me "I am sad to inform you, you just cannot use it".
I find this very hard to believe. The memory check reads and writes to
it -- so it must be possible to adress it. If it were not -- how can it
be called memory ?
Anyway -- If it is adressable, then it must be possible to use it as
a virtual disk par example. MS-D*S 3.3 vdisk and cacher both fail to find
this (Using the /E flag).
If anyone has some information on how to adress this memory from any
computer language - or where to get a vdisk program that can access it,
or perhaps even mail one to me, I would be easier. Refelections without
solutions are also welcome.
Thank you,
But tobacco in a tinwhistle I | Ctrl-C.Stenholm
have never seen before... | s32935k@taltta.hut.fi
(Trad.) |
leonard@bucket.UUCP (Leonard Erickson) (07/16/89)
s32935k@taltta.hut.fi (Carl Torsten Stenholm) writes:
<I just purchased an *livetti (I think the number was M380), anyway it has:
< 80386, 81 M harddisk, 20 MHz clock, 1 M memory.
<The problem is this 1 M memory. The startup system check tells me:
< Main memory 640 K OK
< Dedicated Mem 384 K OK
<I just cant use these 384K of "dedicated memory". I called the dealer
<and he told me "I am sad to inform you, you just cannot use it".
<I find this very hard to believe. The memory check reads and writes to
<it -- so it must be possible to adress it. If it were not -- how can it
<be called memory ?
<Anyway -- If it is adressable, then it must be possible to use it as
<a virtual disk par example. MS-D*S 3.3 vdisk and cacher both fail to find
<this (Using the /E flag).
Sorry, but many machines do this sort of thing. That memmory is addressed
the 640-1024k range. This area is already used by *other* things like video
boards, hard disk controllers, the BIOS ROMs, etc.
Since your machine tests it, rather than ignoring it, it may be mapping
the ROMs to this memory to improve performance. (RAM reads are faster
than ROM reads).
The Reason the /E option on vdisk didn't work is that it is for accessing
*extended* memory. Extended memory starts above the 1 meg mark.
In short, if it can be used for something, the system is already doing so.
--
Leonard Erickson ...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I'm all in favor of keeping dangerous weapons out of the hands of fools.
Let's start with typewriters." -- Solomon Short