On Tue, Jan 12, 2016 at 1:36 PM, Tom Ehlert <[email protected]> wrote: > Hi, > > just wondering what the 'official' most recent version of COMMAND.COM > is. > > is it http://sourceforge.net/p/freedos/svn/HEAD/tree/freecom/trunk/ ? > > I remember that Bart ported command.com 'mostly' to WATCOM; is the > port now finished, and working great? >
I checked and I have been using the Open Watcom v1.9 to build and run for a while. I have not found the OW compiled version to be any less stable than the Borland version [I wouldn't really consider either very stable if using DOS=HIGH and XMS-swap variant, though I have never tracked down if issue is FreeCom, memory manager (likely), kernel, or hardware (also likely) issues. Building with OW on Windows XP (32bit in a VM) works with current SVN source (after configuring config.bat & config.mak accordingly) as long as the mkfiles\watcom.mak line is changed from BINPATH = $(CC_BASE_PATH)\BINW to BINPATH = $(CC_BASE_PATH)\BINNT else weird faults occur. > just wondering because > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/0.84pre/ > has no source attached, but is from Aug 07 2006 00:05:31; i.e. can't have > Barts > changes. > > > the reason I'm asking this: > > DIR has some (minor) bugs (*)(**), that I'd like to fix. now where is the > source? > > > > Tom > > > (*) DIR %windir%\system32 /OE > will likely crash, as there are *many* files with identical extension. > that's how I detected the bug. > > filling a directory with ~550 files with identical .ext should also > crash > > sorting *only* by extension will return 0 to qsort, which is not a > good idea. add > > if (rv == 0) > rv = stricmp(f1.ff_name,f2.ff_name); > not testing in DOS, but via Windows NTVDM this does not crash for me using a just compiled from svn mirror source with OW v1.9. the current logic allows listing files sorted by extension then natural directory order, adding a forced sort by name would not allow listing by natural directory order [unsorted], but I'm not against the change if there is no compatibility issue. > > > (**) doing DIR on a directory with more then 4 GB, > > E:\FreeDos\src\freecpl6>a:\system\command /c dir x:\t6-*.sna > Volume in drive X has no label > Directory of X:\ > > T6-DDR SNA 158.420.480 11.07.06 16:51 .... > T6-F-1~2 SNA 4.133.511.168 13.10.15 16:51 > > 35 file(s) 3.372.614.144 bytes <<<<<< not true > 0 dir(s) 588.402.176 bytes free <<<<<< also wrong > > Tom > I think this will require using 64 bit ints and a change in how the free/used space is calculated, but would be great to see this fixed. If there is anything I can do to help, please let me know. Jeremy ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
