Hi there,
I have been reading the HIMEM sources, and have these questions. I am
grateful to whoever can say something about these questions (which as
usual are plain questions with no critisizing):
(1) There is a /TEST option (not present in MS-HIMEM), and at the same
time, MS-HIMEM implements
Hi,
tom ehlert escribió:
Hello Aitor,
(1) There is a /TEST option (not present in MS-HIMEM), and at the same
time, MS-HIMEM implements a /TESTMEM:ON|OFF option to do this (defaults
to ON). /TEST does a nice test by allocating, filling, testing,
resizing,. to determine the reliability of
Hello Aitor,
Yes, but my question is how does kernel know where the device header
starts? MZ doesn't look like a correct pointer to the next device
driver inside the file...
'MZ' is only an envelope around 'the real thing', specifying e.g.
minimum space required, START POINT, size of
Hi,
tom ehlert escribió:
Hello Aitor,
Yes, but my question is how does kernel know where the device header
starts? MZ doesn't look like a correct pointer to the next device
driver inside the file...
'MZ' is only an envelope around 'the real thing', specifying e.g.
minimum space required,
