OK, so we agree that MS-DOS and Windows command/cmd translate "dir *" to
dir"*.*"
Not only only is a compatibility thing, also is logic * means "any
possible filename", not "any
possible filename without extension".
So there is a small bug. I would say a very minor detail, and anyway,
on DOS i
On Mon, May 12, 2008 at 11:13 PM, Claude (Wayne) Smith <[EMAIL PROTECTED]>
wrote:
> I am an old time programmer - Programmed many things.
>
> At one time, I programmed most of the common UNIX commands into the 16
> and 32 bit DOS world -
>
> Could I be of some help?
>
We used to have a HOWTO-Cont
"Alain M." wrote:
> Robert Riebisch escreveu:
> > Jim Hall wrote:
> >> But I don't recall MS-DOS wildcards that way. I remember "DIR *" was
> >> the same as "DIR *." not "DIR *.*". I guess I'm wrong.
> >
> > Yes, you are wrong. ;-) Tested on MS-DOS 5.00 and 6.22.
>
> Can you be more specific?
IIRC "DIR *" was not the same as "DIR *.", and also were not allways the
same in all versions/flavors od DOS
Robert Riebisch escreveu:
> Jim Hall wrote:
>> But I don't recall MS-DOS wildcards that way. I remember "DIR *" was
>> the same as "DIR *." not "DIR *.*". I guess I'm wrong.
>
> Yes, yo
Jim Hall wrote:
> But I don't recall MS-DOS wildcards that way. I remember "DIR *" was
> the same as "DIR *." not "DIR *.*". I guess I'm wrong.
Yes, you are wrong. ;-) Tested on MS-DOS 5.00 and 6.22.
Robert Riebisch
--
BTTR Software
http://www.bttr-software.de/
On Wed, May 14, 2008 at 4:45 AM, Eric Auer <[EMAIL PROTECTED]> wrote:
>
>> On ms-dos 6.22 using dir * is the same as use dir *.*
>> On Freedos dir * is the same as dir *.
>
> Maybe related to a FreeCOM command.com issue: MS DOS command.com
> has some extra handling for "implicit wildcards", see Bug
Hi Marco,
> On ms-dos 6.22 using dir * is the same as use dir *.*
> On Freedos dir * is the same as dir *.
Maybe related to a FreeCOM command.com issue: MS DOS command.com
has some extra handling for "implicit wildcards", see Bugzilla:
http://bugzilla.freedos.org/cgi-bin/bugzilla/show_bug.cgi?i
