delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/2003/12/01/03:06:46

X-Authentication-Warning: delorie.com: mail set sender to opendos-bounces using -f
Message-ID: <01FD6EC775C6D4119CDF0090273F74A4FD6C78@emwatent02.meters.com.au>
From: "da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
To: "'opendos AT delorie DOT com'" <opendos AT delorie DOT com>
Subject: RE: several technical problems [memory]
Date: Mon, 1 Dec 2003 17:58:35 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Reply-To: opendos AT delorie DOT com

Please see below ...

Joe.

> -----Original Message-----
> From:	DONALD PEDDER [SMTP:jims_son AT jedi DOT apana DOT org DOT au]
> Sent:	Saturday, November 29, 2003 2:11 PM
> To:	opendos AT delorie DOT com
> Subject:	Re: several technical problems
> 
>    Well, my message didn't make it through before because...
> 
> > Please edit out the PC-DOS graphics characters.  They make it look too
> > much like asian spam.
> 
>    ...so here we go again. :-)
> 
> 
> > If you still have Windows installed, you might be able to get rid of it
> > by right-clicking on the Recycle Bin and clicking Properties, selecting
> > "Configure drives independently" then tick the "Do not move files to the
> > Recycle Bin" box on the tab corresponding to the partition in question.
> 
>    I did that (even though I never delete anything on that partition when
> I'm in Windows), and then when I also did...
> 
	[Joe da Silva]  

	Well, if you configure a different drive/partition to hold the
	"Recycle Bin", it is safe to delete stuff from Windoze. It
	is _not_ safe to delete stuff from DR-DOS if there is any
	LFN stuff about (LFN support was never fully debugged
	unfortunately).

> > The easiest way to correct this problem is to run MS ScanDisk;
> 
>    It gave me the option of deleting the recycled directory. :-) I did
> that, and my problem was resolved.
> 
> 
> > Could you tell us more about 'this computer' (CPU, mainboard, BIOS,
> > memory, add-on cards, etc.)?
> 
>    Uh, I can try. :-) The CPU is a Celeron 466MHz, my system-board is
> "PC100 slot 1/socket 370 M741lmrt", AMIBIOS, memory is 64Mb,
> sound-cards,etc. are built-in to the system-board.
> 
> 
> > What is the GREEN command in your AUTOEXEC?
> 
>    It's just a little pascal program that sets my text-colour to green.
> Unfortunately, as soon as I use an app (like the editor) it reverts to
> white again. I've still not yet found out how to permanently set it to
> green.
> 
> 
> > Please try (1) with HIMEM.SYS instead of EMM386; (2) with EMM386, but
> > without NWCDEX.
> 
>    Using HIMEM.SYS worked, but there's still one bug. I can swap sessions
> okay with multiple editors open, but if I am logged on and swap from that
> session it hangs up the modem. :-( If I can sort out my memory shortage
> though then it's not a problem.
> 
> 
> > Could you redirect the output of MEM /A to a file (MEM /A > MEM.LST) and
> > post it to the list?
> 
>    Asian-spam looking stuff deleted. :-)
> 
>    Address    Name         Size                Type
>     0:0000  --------   A0000h, 655,360  ------------- RAM -----
>     0:0000  --------     400h,   1,024  Interrupt vectors
>    40:0000  --------     100h,     256  ROM BIOS data area
>    50:0000       DOS     200h,     512  DOS data area
>    70:0000      BIOS     900h,   2,304  Device drivers
>    70:0023  CON                          System device driver
>    70:0035  AUX                          System device driver
>    70:0047  PRN                          System device driver
>    70:0059  CLOCK$                       System device driver
>    70:006B  COM1                         System device driver
>    70:007D  COM2                         System device driver
>    70:008F  COM3                         System device driver
>    70:00A1  COM4                         System device driver
>    70:00C7  LPT1                         System device driver
>    70:00D9  LPT2                         System device driver
>    70:00EB  LPT3                         System device driver
>    70:016E     A:-F:                     System device driver
>   100:0000       DOS    1400h,   5,120  System
>   100:0048  NUL                          System device driver
>   100:00CC       DOS     10Fh,     271   HANDLES=3D, FCBS=3D  5 total
> blocks
>   240:0000       DOS    6B30h,  27,440  System
>   242:0000       DOS      A5h,     165   HANDLES=, FCBS= 3 total blocks
>   24F:0000  EMMQXXX0     2F0h,     752   DEVICE  installed device driver
>   27F:0000  DPMSXXX0     630h,   1,584   DEVICE = installed device driver
>   2E3:0000  SETVERXX     1F0h,     496   DEVICE = installed device driver
> =B3
>   303:0000  MSCD000     5240h,  21,056   DEVICE = installed device driver
> =B3
>   828:0000       DOS     98Ch,   2,444   HANDLES=, FCBS=  46 total blocks
> =B3
>   8F3:0000   COMMAND     1F0h,     496  Program
>   912:0000   COMMAND     210h,     528  Environment
>   933:0000   TASKMGR     140h,     320  Data
>   947:0000    NWCDEX      E0h,     224  Environment
>   955:0000    NWCDEX    1C50h,   7,248  Program
>   B1A:0000   TASKMGR      E0h,     224  Environment
>   B28:0000   TASKMGR     2A0h,     672  Program
>   B52:0000   COMMAND     140h,     320  Data
>   B66:0000    BITCOM      E0h,     224  Environment
>   B74:0000    BITCOM   49C10h, 302,096  Program
>  5535:0000   COMMAND      E0h,     224  Data
>  5543:0000   COMMAND     1F0h,     496  Program
>  5562:0000   COMMAND     210h,     528  Environment
>  5583:0000       MEM      E0h,     224  Environment
>  5591:0000       MEM   15C20h,  89,120  Program
>  6B53:0000  --------   346C0h, 214,720  FREE
>  9FBF:0000       DOS   28410h, 164,880  System
>  9FC0:0000  --------     400h,   1,024  Extended ROM BIOS data area
>  C000:0000  --------    8000h,  32,768  ------------- ROM -----
>  C800:0000  --------   24000h, 147,456  ---------- Upper RAM --
>  C800:0000    EMM386     340h,     832  XMS Upper Memory Block
>  C834:0000       DOS     D50h,   3,408  System
>  C909:0000   NWCACHE    15C0h,   5,568  XMS Upper Memory Block
>  CA65:0000   NWCACHE    4010h,  16,400  XMS Upper Memory Block
>  CE66:0000  DRMOUSE     1990h,   6,544  Program
>  CFFF:0000   TASKMGR    3960h,  14,688  XMS Upper Memory Block
>  D395:0000   COMMAND    2090h,   8,336  Data
>  D59E:0000  --------   16620h,  91,680  FREE
>  EC00:0000  --------    4000h,  16,384  ------------- ROM -----
>  F800:0000  --------    1000h,   4,096  ---------- Shadow ROM -
>  FFFF:00E0   COMMAND    2080h,   8,320  Program
>  FFFF:2240       DOS     F70h,   3,952  DOS BIOS code
>  FFFF:31B0       DOS    7280h,  29,312  DOS kernel code
>  FFFF:A430       DOS    1F2Ch,   7,980   BUFFERS=  15 disk buffers
>  FFFF:C35C  --------     D37h,   3,383  FREE
>  FFFF:EE96     SHARE    115Ah,   4,442  Program
> 
>  Memory Type             Total Bytes ( Kbytes  )  Available For Programs
>  Conventional             654,336 (    639K )         304,064 (    297K )
>  Upper                    147,456 (    144K )          91,680 (     90K )
>  High                      65,520 (     64K )           3,383 (      3K )
>  Extended              57,606,144 ( 56,256K )               0 (      0K )
>  Extended via XMS            --------              48,076,800 ( 46,950K )
>  Largest executable program:  304,048 ( 297K )
>  Total Free DOS memory:       395,744 ( 386K )
> 
> 
>    This looks very handy. :-) This says I have 46Mb available via XMS -
> how do I make the programs use that? Also, for something that terminates
> without staying resident, how would I find out how much memory it is
> using?
> 
	[Joe da Silva]  

	Well, as others have pointed out, that's not easy. However,
	you can find out how much they need (_before_ allocating
	extra stuff, if any), using a utility called "minload", available
	somewhere on Simtel.Net.

> > Please tell us more about your system configuration.
> 
>    Like? I'm not really into the technical side, so if you want to find
> something out you need to tell me what commands to run or where I'm
> looking. e.g. I had never used the mem command until just now.
> 
> 
> > There is at least a few experienced TASKMGR users on the list, and I
> > hope you'll finally get multitasking to work.
> 
>    It's working okay now, other than the hanging up the modem issue. I had
> it running on an older computer (might've also been an older version), so
> it's frustrating that when I "upgrade" it's not working properly anymore
> (however, I encounter this all the time at work - every single "upgrade"
> we have ever had has made life more difficult in fact).
> 
	[Joe da Silva]  

	You can use the command "AT&D0" to tell the modem
	to ignore DTR (just add "&D0" to its initialization string).
	As someone else mentioned, that's probably what's
	causing this problem for you.

> > Remember, as far as anything running in *any* DOS is concerned, you
> > hsave no more than 640k of RAM (768 if you play certain games).
> 
>    I didn't think that would be an issue, but having done "mem /a" now, I
> can see that I've already used up half my (640k) memory. I guess I need to
> do some fine-tuning of my memory usage?
> 
> 
> > Well, you should move any files you need to another directory, then
> > remove the hidden attribute (use the attrib command) and then remove the
> > directory.
> 
>    I went into the recycled directory and did "attrib -h *.*", but it
> didn't find anything. I then went back to the root directory and did
> "attrib -h recycled" and it tells me "file not found".
>    So, I wasn't able to clear it in DOS, but the Windows approach worked.
> 
>    Is there a DOS utility I can run which'll make sure I don't have any
> LFN's hanging around on the disk? I want to keep it clean so that I can
> run delwatch/diskopt on it.
> 
> 
> thanks,
>    DONALD.
> 
> E-mail               - donaldp AT au DOT mensa DOT org
> BIG DON's Home-page  - http://jedi.apana.org.au/~jims_son
> Pedder Passer Rating - http://jedi.apana.org.au/~jims_son/PPR
> AusNFL mailing-list  - http://jedi.apana.org.au/mailman/listinfo/ausnfl
> 
> "What I always wanted is to be accepted, not understood" - MAN RAY
> ------- End of forwarded message -------

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019