To: opendos AT delorie DOT com Message-Id: Organization: Inst. of Evolutionary Physiology & Biochemistry, St.Petersburg From: pavel AT insect DOT ief DOT spb DOT su (Pavel Ozerski) Date: Thu, 7 May 98 10:56:01 +0300 Reply-To: pavel AT insect DOT ief DOT spb DOT su Subject: next bug in COMMAND.COM Precedence: bulk I found a small bug in DR-DOS COMMAND.COM (DIR internal command). Symptom: not always correct LONGNAME interaction. I load LONGNAME.EXE. Then I create a test file with long name: copy con "test file name" ------------------------ OK! Then I ask for files in the current subdirectory: dir /l ------ Result: TESTFI~1 18 7/05/98 10:09 test file name ========================================================= OK! Then I try: dir /l TESTFI~1 --------------- Result: TESTFI~1 18 7/05/98 10:09 TESTFI~1 =================================================== As it shown, in the second result the file name is not expanded. I assume that the bug is localized in the COMMAND.COM. This (7.02) version has at least 2 additional problems: 1. Too big resident size wich causes problems while loading into HMA (DOS BIOS CODE cannot be loaded into HMA if COMMAND is loaded using HISHELL SIZE=2160); 2. HILOAD/BAT conflict. If exist available UMBs then trying to execute HILOAD myfile.bat causes message: Batch files nested too deeply. I understand that LONGNAME is only beta version and its support can be not complete. But beta-testing exists for searching for bugs. But the COMMAND.COM is included into the official DOS release. That is too much bugs for the final version!!! I think, all DR-DOS users are waiting for the update of COMMAND.COM and possibly kernel. Does CALDERA message anything about next release or update of DR-DOS? Are 7.02 kernel sources available? -- Pavel V. Ozerski | Inst. of Evolutionary Physiology & Biochemistry, office +7 (812)552-6870(291)| Russian Academy of Sciences, FAX +7 (812)552-3012 | Thorez pr. 44, St.Petersburg, 194223, Russia home +7 (812)528-5576 | E-mail: pavel AT insect DOT ief DOT spb DOT su