I finished reading the "Why We Love FreeDOS" book a few nights ago. A
really good read, and led myself to a similar conclusion, DOS/FreeDOS is a
really good platform for learning and implementing initial experimental
engineering for experimental or working hardware due to simplicity and bare
metal
I love FreeDos and it s the only operating system on my opd msi computer
running a quad core 2.66ghz cpu amd 4gb of ram. My main use is just
programming in PowerBasic or FreeBasic, and I may sometime try C thanks to
the great videos Mr Hall has on youtube. I do rarely play games, or play
mp3 or m
Hi Jim!
My favorite example of someone running FreeDOS was years ago, probably
around 2005. They built pinball machines, and FreeDOS ran the scoring
system, lit the lights, and played sound effects from a sound bank...
Maybe they used some type of lab control or GPIO type ISA or PCI card?
My
On June 29, 2024, FreeDOS will turn THIRTY YEARS OLD!
I'm writing some articles about FreeDOS for places like
https://allthingsopen.org/ and https://www.both.org/ - and I'm
currently writing more articles to submit elsewhere.
If anyone out there wants to write an article about FreeDOS, this is
th
Roger wrote:
> >> Would be really interesting to hear, how people continue actively using
> >> DOS today, including their hardware/software environment. Of course, not
> >> including testing environments, as these can get really exquisite! And,
> >> I already realize one of the environments DOS is
Hi!
Not sure whether I can reproduce the problem...
If I have a directory with files 1.2, 3, 4.5 and 6,
DIR and DIR *.* shows all files and DIR * only shows
the files without extension: 3 and 6. DIR *. does
the same. So everything seems to work as expected?
Tested on FAT12, FAT16, FAT32 and D
Nope, not just FreeDos. I have tried about four flavours of DOS with the
same result. Same with XCOPY or XXCOPY with /L option. Almost like the
DIR and related utility programs "file matching code" share similar
source code. I know zero about DOS internals ;-) I just stumbled across
this issue
Nope, not just FreeDos. I have tried about four flavours of DOS with the
same result. Same with XCOPY or XXCOPY with /L option. Almost like the
DIR and related utility programs "file matching code" share similar
source code. I know zero about DOS internals ;-) I just stumbled across
this issue
On Mon, 03 Jun 2024 17:05:13 +0200, hms--- via Freedos-user wrote:
> The point I am trying to make is about the unexpected behaviour of the
> DIR command [...]
The sources are available, no? Fix it yourself?
I just tried it in Dosbox and it seems to stop even earlier, not
listing any deeper file
Actually, I'd say that's better behavior than I get from a command line
in windows 10.
When I create the structure you showed below, I do indeed get all the
files/directories (made them all directories except the .asm files),
then I get output equivalent to your first listing.
When I change
The point I am trying to make is about the unexpected behaviour of the
DIR command and that is if a directory exists with the same name as the
file one is searching for, the directory listing is terminated early
without error.
In my example, if the Q directory is renamed to Q4 and the command
Regardless of whether they're files or directories, if there is no file
extension, then don't put on the second star, just a *. will do the
search for you. By placing the second star, you're making the os search
for extensions by default. Leave it out, and it will search for just
files w/o th
12 matches
Mail list logo
