langev@cbnewse.att.com (steve.j.langevin) (05/24/91)
I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing
what looks like some discrepancies between chkdsk and mem about how
much memory I have available.
chkdsk (and PC TOOLS) say I have ~590KB available.
mem says I have ~613KB.
Which one is more "accurate"??
Anyone seen anything similar on their systems??
Thanks in advance.
===========================================================================
Steve Langevin att!iwddo1!langev (708) 979-5949
Ok -- so its not the best signature line. I'M WORKING ON IT!barnett@rex.cs.tulane.edu (Karey Barnett) (05/24/91)
In article <1991May23.231255.6520@cbnewse.att.com> langev@cbnewse.att.com (steve.j.langevin) writes: > >I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing >what looks like some discrepancies between chkdsk and mem about how >much memory I have available. > >chkdsk (and PC TOOLS) say I have ~590KB available. > >mem says I have ~613KB. > >Which one is more "accurate"?? I could be wrong, but chkdsk and PC Tools could be including the amount of memory each uses when each runs, in determining the ~590kb available amount. This logic would mean that mem doesn't include the amount of memory it uses.
ajai@sce.carleton.ca (Ajai Sehgal) (05/24/91)
langev@cbnewse.att.com (steve.j.langevin) writes: >I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing >what looks like some discrepancies between chkdsk and mem about how >much memory I have available. >chkdsk (and PC TOOLS) say I have ~590KB available. >mem says I have ~613KB. >Which one is more "accurate"?? Are you sure that chkdsk and PCtools aren't saying that you have about 598K available and mem is saying you have 613000 bytes available? Because 598K = 613000 bytes (ie 613000 / 1024 = 598.63). Just a shot in the dark. Regards, Ajai.
pclank01@ulkyvx.bitnet (Pat Lankswert) (05/29/91)
In article <1991May23.231255.6520@cbnewse.att.com>, langev@cbnewse.att.com (steve.j.langevin) writes: > > I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing > what looks like some discrepancies between chkdsk and mem about how > much memory I have available. > > chkdsk (and PC TOOLS) say I have ~590KB available. > > mem says I have ~613KB. > Dr. DOS could be reporting memory that is above the 640k barrier that PCTools and CHKDSK think are devices. This can especially be the case if you are running a '386 machine. Look for free memory in the 640-1024k range. Patrick Lankswert | Bitnet -> pclank01@ulkyvx System Manager | INTERNET -> pclank01%ulkyvx.bitnet@cunyvm.cuny.edu Brown Cancer Center | UUCP -> ...psuvax1!ulkyvx.bitnet!pclank01 U of Louisville |
frotz@dri.com (Frotz) (05/30/91)
pclank01@ulkyvx.bitnet (Pat Lankswert) writes: ]In article <1991May23.231255.6520@cbnewse.att.com>, langev@cbnewse.att.com (steve.j.langevin) writes: ]> ]> I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing ]> what looks like some discrepancies between chkdsk and mem about how ]> much memory I have available. ]> ]> chkdsk (and PC TOOLS) say I have ~590KB available. ]> ]> mem says I have ~613KB. ]> ]Dr. DOS could be reporting memory that is above the 640k barrier that PCTools ^^^^^^^ Uh... DR DOS, not (Doctor DOS...) ]and CHKDSK think are devices. This can especially be the case if you are ]running a '386 machine. Look for free memory in the 640-1024k range. Does this help? +- Address -+- Owner --+- Size -----------+- Type ----------------------------+ | 0:0000 | -------- | A0000h, 655360 | ------------- RAM --------------- | +-----------+----------+------------------+-----------------------------------+ | 0:0000 | -------- | 400h, 1024 | Interrupt vectors | | 40:0000 | -------- | 100h, 256 | ROM BIOS data area | | 50:0000 | DR DOS | 200h, 512 | DOS data area | | 70:0000 | DR BIOS | 18D0h, 6352 | Device drivers | | 70:052F | PRN | | Built-in device driver | | 70:0541 | LPT1 | | Built-in device driver | | 70:0553 | LPT2 | | Built-in device driver | | 70:0565 | LPT3 | | Built-in device driver | | 70:0577 | AUX | | Built-in device driver | | 70:0589 | COM1 | | Built-in device driver | | 70:059B | COM2 | | Built-in device driver | | 70:05AD | COM3 | | Built-in device driver | | 70:05BF | COM4 | | Built-in device driver | | 70:0659 | CLOCK$ | | Built-in device driver | | 70:0695 | CON | | Built-in device driver | | 70:06A7 | A:-F: | | Built-in device driver | | 1FD:0000 | DR DOS | 11B0h, 4528 | System | | 1FD:0048 | NUL | | Built-in device driver | | 318:0000 | DR DOS | 750h, 1872 | System | | 34B:0000 | EMMXXXX0 | | Loadable device driver | | 38D:0000 | COMMAND | 210h, 528 | Environment | | 3AE:0000 | -------- | 70h, 112 | FREE | | 3B5:0000 | HISTORY | E0h, 224 | Environment | | 3C3:0000 | HISTORY | 1DB0h, 7600 | Program | | 59E:0000 | MEM | A520h, 42272 | Environment | | FF0:0000 | MEM | 12D10h, 77072 | Program | | 22C1:0000 | -------- | 7D3E0h, 512992 | FREE | | 9FFF:0000 | EXCLUDED | 3E010h, 253968 | Upper system memory | +-----------+----------+------------------+-----------------------------------+ | C000:0000 | -------- | 8000h, 32768 | ------------- ROM --------------- | | C800:0000 | EMS | 10000h, 65536 | ---------- EMS memory ----------- | +-----------+----------+------------------+-----------------------------------+ | D800:0000 | EMM386 | 6000h, 24576 | EMM386 device driver code | +-----------+----------+------------------+-----------------------------------+ | DE00:0000 | -------- | 12000h, 73728 | ---------- Upper RAM ------------ | +-----------+----------+------------------+-----------------------------------+ | DE00:0000 | DR DOS | 1000h, 4096 | System | | DE01:0000 | CON | | Loadable device driver | | DF00:0000 | DR DOS | 30C0h, 12480 | System | | DF01:0000 | PC$MOUSE | | Loadable device driver | | E20C:0000 | DR DOS | 3280h, 12928 | System | | E20D:0000 | DR DOS | 1E00h, 7680 | 15 Disk buffers | | E534:0000 | COMMAND | 1330h, 4912 | Program | | E667:0000 | -------- | 9990h, 39312 | FREE | +-----------+----------+------------------+-----------------------------------+ | F000:0000 | -------- | 10000h, 65536 | ------------- ROM --------------- | +-----------+----------+------------------+-----------------------------------+ | FFFF:0000 | DR DOS | 96E0h, 38624 | DR DOS kernel code | +-----------+----------+------------------+-----------------------------------+ +--------------------------------------------------------------------------+ | |<------------------- Conventional memory ---------------------> | | 0h 10000h 20000h 30000h 40000h 50000h 60000h 70000h | | 0K 64K 128K 192K 256K 320K 384K 448K | | +-------+-------+-------+-------+-------+-------+-------+------- | | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ | | @@@@@@@@@@@@@@@@................****########...@@@@@@@@@******** | | +-------+-------+-------+-------+-------+-------+-------+------+ | | 512K 576K 640K 704K 768K 832K 896K 960K 1MB | | 80000h 90000h A0000h B0000h C0000h D0000h E0000h F0000h 100000h | | >-------------->|<-------------- Upper memory ---------------->| | +--------------------------------------------------------------------------+ Key: @=RAM *=ROM %=Shadow ROM #=EMS 655,360 bytes, ( 640K), conventional memory 632,320 bytes, ( 617K), largest available block 3,145,728 bytes, (3072K), extended memory 3,145,728 bytes, (3072K), extended memory used 0 bytes, ( 0K), extended memory available -- John "Frotz" Fa'atuai frotz@dri.com (email@domain) Digital Research, Inc. uunet!drivax!frotz (bang!email) c/o MIS Dept. 408/647-6570 or 408/646-6287 (vmail) 80 Garden Court, CompRm 408/649-3896 (phone) Monterey, CA 93940 408/646-6248 (fax)
thomasr@cpqhou.uucp (Thomas Rush) (05/30/91)
In article <1991May23.231255.6520@cbnewse.att.com>, langev@cbnewse.att.com (steve.j.langevin) writes: > > I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing > what looks like some discrepancies between chkdsk and mem about how > much memory I have available. > > chkdsk (and PC TOOLS) say I have ~590KB available. > > mem says I have ~613KB. > >Patrick Lankswert ...psuvax1!ulkyvx.bitnet!pclank01 Could it be that chkdsk is about 20K larger than mem? thomas rush uunet!cpqhou!thomasr compaq computer corporation their employee, deep in the hearth of texas not their opinions.
frotz@dri.com (Frotz) (06/01/91)
thomasr@cpqhou.uucp (Thomas Rush) writes: ]In article <1991May23.231255.6520@cbnewse.att.com>, langev@cbnewse.att.com (steve.j.langevin) writes: ]> ]> I just purchased DR DOS 5.0 and installed it on my hard disk. I'm seeing ]> what looks like some discrepancies between chkdsk and mem about how ]> much memory I have available. ]> ]> chkdsk (and PC TOOLS) say I have ~590KB available. ]> ]> mem says I have ~613KB. ]> ]>Patrick Lankswert ...psuvax1!ulkyvx.bitnet!pclank01 ]Could it be that chkdsk is about 20K larger than mem? Funny, I was just up in Tech.Sup. talking to someone about the future;-) Bradley Kerth (sorry, no net address guys;-{ mentioned that there was a bug problem with chkdsk. It is now EXEPACKed. This means that in order to decompress in memory, it CANNOT reside in segment 0000:ofs (where mem is loaded because it is NOT EXEPACKed). An bug report (SPR) has been submitted to the development group and their initial response has something to do with MEMMAX and disabling lower memory. No, I wasn't paying too much attention to the details...;-) Below is a quick map: MEM CHKDSK (not packed) (packed) ------------------------------ ------------------------------ Segment 0 MEM Segment 0 Free memory ... Segment 'n' Free memory Segment 'n' CHKDSK Segment 'm' Free memory Segment 'n' Free memory The bottom line is that CHKDSK is not smart enought to recognize the free memory in segment 0 (below itself). It only reports the amount of memory above itself. Since MEM is loaded as low as possible it reports the amount of free memory above it (which is the correct total). -- John "Frotz" Fa'atuai frotz@dri.com (email@domain) Digital Research, Inc. uunet!drivax!frotz (bang!email) c/o MIS Dept. 408/647-6570 or 408/646-6287 (vmail) 80 Garden Court, CompRm 408/649-3896 (phone) Monterey, CA 93940 408/646-6248 (fax)