Re: [Freedos-user] DOS Actively Used Scenarios
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 access. With the low-boot times of older hardware, can imagine likely has a constant foothold within certain areas. Albeit, more so within the private/civilian sector nowadays. No wonder I had such a difficult time with DOS, DOS was a morphed incarnation of CP/M. Main difference, instead of a ready prompt, put the user at the C:\ prompt. I more so enjoy the Unix/Linux platform, all the software tends to co-exist more peacefully than the intricate parts of DOS. On the flip, DOS is assembly, whereas Unix/Linux is primarily C programming language. Unix/Linux, when using the command line, typing just flows far better than typing DOS commands. However, have an open mind and would likely spend some time in DOS/FreeDOS, if I can find some purposeful use besides just using Word Perfect. I rarely ever waste time playing games. You'll readily realize, if you find me wasting time playing a DOS game, it'll likely be because I'm sitting in a retirement home after having my computer/Internet confiscated, trying to patiently await for my funeral. And there's an idea, pretty sure prisons likely allow prisoners to use DOS without Internet, for playing games... Roger On Mon, Jun 3, 2024 at 8:23 PM Norby Droid via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > 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 midi files for some fun. Personally I prefer to use an old computer > running FreeDos than a new computer running Linux. I am no pro programmer, > but I do love to program and see what I can create. > > On Mon, Jun 3, 2024 at 20:11 Eric Auer via Freedos-user < > freedos-user@lists.sourceforge.net> wrote: > >> 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 favorite example before that was a nebulous one. Someone from NASA >> > emailed me in the late 1990s to say they were using FreeDOS on some of >> > their computers. They never provided details, so I don't know what it >> > was doing - but how cool that NASA was using FreeDOS!? >> >> I remember somebody asking whether FreeDOS had contributions from people >> from evil countries, because they wanted to use it to run some type of >> in-flight entertainment system with some media player app for DOS :-) >> >> More recently, during a small demoscene event, I noticed that one of >> the presented demos was a 256 byte demo running on FreeDOS. The boot >> message was only visible for a moment, so I do not know what type of >> virtual hardware that FreeDOS instance was running on. >> >> Cheers, Eric >> >> >> >> >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS Actively Used Scenarios
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 midi files for some fun. Personally I prefer to use an old computer running FreeDos than a new computer running Linux. I am no pro programmer, but I do love to program and see what I can create. On Mon, Jun 3, 2024 at 20:11 Eric Auer via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > 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 favorite example before that was a nebulous one. Someone from NASA > > emailed me in the late 1990s to say they were using FreeDOS on some of > > their computers. They never provided details, so I don't know what it > > was doing - but how cool that NASA was using FreeDOS!? > > I remember somebody asking whether FreeDOS had contributions from people > from evil countries, because they wanted to use it to run some type of > in-flight entertainment system with some media player app for DOS :-) > > More recently, during a small demoscene event, I noticed that one of > the presented demos was a 256 byte demo running on FreeDOS. The boot > message was only visible for a moment, so I do not know what type of > virtual hardware that FreeDOS instance was running on. > > Cheers, Eric > > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS Actively Used Scenarios
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 favorite example before that was a nebulous one. Someone from NASA emailed me in the late 1990s to say they were using FreeDOS on some of their computers. They never provided details, so I don't know what it was doing - but how cool that NASA was using FreeDOS!? I remember somebody asking whether FreeDOS had contributions from people from evil countries, because they wanted to use it to run some type of in-flight entertainment system with some media player app for DOS :-) More recently, during a small demoscene event, I noticed that one of the presented demos was a 256 byte demo running on FreeDOS. The boot message was only visible for a moment, so I do not know what type of virtual hardware that FreeDOS instance was running on. Cheers, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Anyone want to write an article about FreeDOS?
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 the perfect time! You don't have to be an expert - just write about your experience. A few examples: * If you are a developer, write about "one cool trick" that's useful for writing DOS programs - could be assembly, C, Pascal .. anything! * If you are a user, write about "one cool thing" you did with FreeDOS. Maybe you set up FreeDOS on an old PC. Maybe you figured out how to get FreeDOS to recognize a CD-ROM drive on a system that didn't "see" the drive before. * Write about why you like using FreeDOS, or why you first started contributing to FreeDOS, or why you are interested in FreeDOS today. Maybe you write documentation. Maybe you translate messages. Maybe you maintain a program. Whatever you do, people will want to read about it. Jim ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS Actively Used Scenarios
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 still used, for > >> engineering and bare-metal programming projects. [..] > >> More so curious, does anybody use DOS/FreeDOS for daily office work? > >> We've all heard of one writer doing so. Mercury Thirteen wrote: > >Actually, a book exists which is all about that question! :) > > > >Check out Why We Love FreeDOS available at https://freedos.org/books/ Roger wrote: > Just what I was looking for. Thanks! > I'll add that I met with someone last year who uses FreeDOS to drive a CNC router to make actual products. (CNC = "Computer Numerical Control" .. that is the fancy term for "a machine controlled by a computer.) I recall that the CNC was running from a Dell PC, and they had a serial selector that let the PC control two (or three?) different CNC routers .. but one at a time. I also found a video on YouTube from a few years ago, about some trainspotters in Russia (I think) who found a PC in some remote booth next to a rail line that ran the communications systems. I don't think it was "train signal control" but "announcements sent to the trains, like for an automated voice to read over the speaker." (Probably boring stuff like "Staff will check for valid tickets" or "Trains will run slow on Wednesday due to the holiday" or "No smoking aboard trains" or whatever.) The PC was off, so they turned it on to see what it did .. and if you paused the video at the right time, you could see it was booting FreeDOS. 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. I have no idea how that was hooked up, but I've always imagined that each element (bumpers, etc) provided input on a keyboard bus, and then a DOS application read the keyboard to know what was happening. But that was a long time ago, and I'm sure they aren't doing that anymore. My favorite example before that was a nebulous one. Someone from NASA emailed me in the late 1990s to say they were using FreeDOS on some of their computers. They never provided details, so I don't know what it was doing - but how cool that NASA was using FreeDOS!? For myself, I usually run FreeDOS in a virtual machine. I like QEMU because it's easy - but mostly because it's already installed by default on my Linux desktop system, so I don't have to install some other package like VirtualBox or PCem. More recently, I bought a Pocket386 micro laptop, and now that's running FreeDOS (see other email thread). That's $200 for the laptop, $20 for the CF card reader, and another $20 for the PS/2 keyboard. Not bad! And while I don't use FreeDOS for daily work, I do use it almost daily. One thing I do is play DOS games to take a break. I purchased legit copies of classic DOS games from GOG.com (for like $5 each) and I installed those on FreeDOS. I loved replaying Jill of the Jungle. I'm replaying Commander Keen now. I also use FreeDOS as a demonstration when I teach a university class. That class is basically two parts: "How computers work (plus a history of technology)" and "How to use Word & Excel." These are freshmen students, so almost no one has used a spreadsheet before. When I start the Excel unit, I bring in FreeDOS and show them some classic spreadsheets: I show them VisiCalc, Lotus 1-2-3, As Easy As, and then Quattro Pro. And then the students understand that spreadsheets just haven't changed that much over time. The interface has changed (graphical) and modern spreadsheets support more functions, but the core features of "letters for columns, numbers for rows, cells are A1, .. and so on" haven't changed since 1979 (VisiCalc on the Apple II was the first desktop spreadsheet that we would recognize as a "spreadsheet"). I love As Easy As. That saw me through my physics undergrad program. And it does so much that modern spreadsheets can do - just differently (like conditional formatting). I sometimes think that if I didn't need to share spreadsheets with others, As Easy As could meet more than 95% of my spreadsheet needs in 2024. That's one reason I keep showing off As Easy As in the videos on our YouTube channel. *We have links to VisiCalc and As Easy As on the website: https://www.freedos.org/about/apps/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
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 DOSEMU2-redirects, with FreeCOM version 0.84-pre2 XMS_Swap Aug 26 2006. Regards, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
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 and was puzzled why I couldn't locate files that I knew existed. On 2024/06/03 17:37, Tomas By via Freedos-user wrote: 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 files or directories. But I suspect you are right and this is a bug in Freedos. /Tomas ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
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 and was puzzled why I couldn't locate files that I knew existed. On 2024/06/03 17:37, Tomas By via Freedos-user wrote: 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 files or directories. But I suspect you are right and this is a bug in Freedos. /Tomas ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
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 files or directories. But I suspect you are right and this is a bug in Freedos. /Tomas ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
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 q4 to q, and run it again, I get the second listing (twice) with a file not found error between the two listings. (very odd). So, I think that freedos handles it better than MSDOS does, so I'd have to call this one expected behavior. Interesting enough though, if I do the DIR Q4 /S /B, after renaming Q to Q4, I do indeed get the whole structure as expected, so not sure what's going on there. Perhaps it's a problem with single letter nested directory names? On 6/3/2024 3:05 PM, h...@iafrica.com wrote: 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 "DIR Q /S /B " issued, all occurrences of Q file are found. Eg. f:\a12\Q.A f:\a12\j\Q f:\a12\q.a\Q f:\a12\q.a\Q.A f:\a12\q1\Q f:\a12\q1\Q.A f:\a12\q4\Q f:\a12\q4\Q.A f:\a12\q4\Q.ASM f:\a12\ts\Q f:\a12\ts\Q.A f:\a12\ts\Q.ASM With the Q directory in place and issuing the command "DIR Q /S /B ", only files in the Q directory are displayed. Eg. f:\a12\q\Q f:\a12\q\Q.A f:\a12\q\Q.ASM f:\a12\q\Q1 f:\a12\q\Q12 I suspect that if there are deeper levels of directories and Q files are at levels prior to the Q directory, these Q files will be displayed until the Q directory is encountered and the then listing will stop. Further Q files will not be found/ displayed. I have not verified this. Is this expected behaviour, an anomaly or a bug? On 2024/06/03 15:10, tsie...@softcon.com wrote: 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 them. I only said before that typically directories don't have extensions, so that's an easy way to find them. but in your case, The same thing applies for files without extensions. On 6/3/2024 6:19 AM, h...@iafrica.com wrote: Hi I am looking for files named Q and not directories named Q. In my case I have thousands of assembler text files without filename extensions. It comes from early days starting out with TSC Flex and Uniflex followed by the Mark Williams Coherent operating systems. John On 2024/06/02 22:29, tsie...@softcon.com wrote: Don't know if it helps, but I've found that if you want *just* directory names, and you don't have a directory program that allows you to set flags, so it only shows directories, then the best way to get them is to do something like: dir *. Since most directory names don't have extensions, this only picks out the directory names (and of course, any files without extensions, but those are rare), so that should find the q directory for you with little to no trouble. On 6/2/2024 5:34 PM, hms--- via Freedos-user wrote: Hi All It appears that if a directory exists with the same name as the file one is searching for, the directory listing is terminated early without error. I was searching for a files named "Q" with no extension. I used the commands "DIR Q /S /B" and "DIR Q. /S /B", but it only revealed files in a directory named "Q". An example directory structure is shown below. Note that most of the file names below do not have extensions. The file named "Q" appears in all the subdirectories. I was puzzled and decided to dig a little further. Is this correct behaviour for the DIR command or a misunderstanding on my part about file name matching? Perhaps an anomaly or a bug? I have tried various DOS's with the same result, the DIR command being an internal one. I have also tried XCOPY and XXCOPY with the "/L" option and it also only finds the files in the "Q" directory. Any thoughts as to what's going on? John Directory of f:\a12\*.* [.] [..] [J] [Q] [Q.A] [Q1] [TS] Directory of f:\a12\j\*.* [.] [..] Q Directory of f:\a12\q\*.* [.] [..] Q Q.A Q.ASM Q1 Q12 Directory of f:\a12\q.a\*.* [.] [..] Q Q.A Directory of f:\a12\q1\*.* [.] [..] Q Q.A Q99 Directory of f:\a12\ts\*.* [.] [..] Q Q.A Q.ASM Entering the command below gives the following result. F:\>DIR Q /S /B f:\a12\q\Q f:\a12\q\Q.A f:\a12\q\Q.ASM f:\a12\q\Q1 f:\a12\q\Q12 The Q file is only found in the Q directory. Same result as above with:- F:\>DIR Q. /S /B Typing
Re: [Freedos-user] Unexpected results from DIR command
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 "DIR Q /S /B " issued, all occurrences of Q file are found. Eg. f:\a12\Q.A f:\a12\j\Q f:\a12\q.a\Q f:\a12\q.a\Q.A f:\a12\q1\Q f:\a12\q1\Q.A f:\a12\q4\Q f:\a12\q4\Q.A f:\a12\q4\Q.ASM f:\a12\ts\Q f:\a12\ts\Q.A f:\a12\ts\Q.ASM With the Q directory in place and issuing the command "DIR Q /S /B ", only files in the Q directory are displayed. Eg. f:\a12\q\Q f:\a12\q\Q.A f:\a12\q\Q.ASM f:\a12\q\Q1 f:\a12\q\Q12 I suspect that if there are deeper levels of directories and Q files are at levels prior to the Q directory, these Q files will be displayed until the Q directory is encountered and the then listing will stop. Further Q files will not be found/ displayed. I have not verified this. Is this expected behaviour, an anomaly or a bug? On 2024/06/03 15:10, tsie...@softcon.com wrote: 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 them. I only said before that typically directories don't have extensions, so that's an easy way to find them. but in your case, The same thing applies for files without extensions. On 6/3/2024 6:19 AM, h...@iafrica.com wrote: Hi I am looking for files named Q and not directories named Q. In my case I have thousands of assembler text files without filename extensions. It comes from early days starting out with TSC Flex and Uniflex followed by the Mark Williams Coherent operating systems. John On 2024/06/02 22:29, tsie...@softcon.com wrote: Don't know if it helps, but I've found that if you want *just* directory names, and you don't have a directory program that allows you to set flags, so it only shows directories, then the best way to get them is to do something like: dir *. Since most directory names don't have extensions, this only picks out the directory names (and of course, any files without extensions, but those are rare), so that should find the q directory for you with little to no trouble. On 6/2/2024 5:34 PM, hms--- via Freedos-user wrote: Hi All It appears that if a directory exists with the same name as the file one is searching for, the directory listing is terminated early without error. I was searching for a files named "Q" with no extension. I used the commands "DIR Q /S /B" and "DIR Q. /S /B", but it only revealed files in a directory named "Q". An example directory structure is shown below. Note that most of the file names below do not have extensions. The file named "Q" appears in all the subdirectories. I was puzzled and decided to dig a little further. Is this correct behaviour for the DIR command or a misunderstanding on my part about file name matching? Perhaps an anomaly or a bug? I have tried various DOS's with the same result, the DIR command being an internal one. I have also tried XCOPY and XXCOPY with the "/L" option and it also only finds the files in the "Q" directory. Any thoughts as to what's going on? John Directory of f:\a12\*.* [.] [..] [J] [Q] [Q.A] [Q1] [TS] Directory of f:\a12\j\*.* [.] [..] Q Directory of f:\a12\q\*.* [.] [..] Q Q.A Q.ASM Q1 Q12 Directory of f:\a12\q.a\*.* [.] [..] Q Q.A Directory of f:\a12\q1\*.* [.] [..] Q Q.A Q99 Directory of f:\a12\ts\*.* [.] [..] Q Q.A Q.ASM Entering the command below gives the following result. F:\>DIR Q /S /B f:\a12\q\Q f:\a12\q\Q.A f:\a12\q\Q.ASM f:\a12\q\Q1 f:\a12\q\Q12 The Q file is only found in the Q directory. Same result as above with:- F:\>DIR Q. /S /B Typing command: F:\>DIR Q.? /S /B Gives this result. f:\a12\Q f:\a12\Q.A f:\a12\j\Q f:\a12\q\Q f:\a12\q\Q.A f:\a12\q.a\Q f:\a12\q.a\Q.A f:\a12\q1\Q f:\a12\q1\Q.A f:\a12\ts\Q f:\a12\ts\Q.A The Q file is now found in all the subdirectories. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR 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 them. I only said before that typically directories don't have extensions, so that's an easy way to find them. but in your case, The same thing applies for files without extensions. On 6/3/2024 6:19 AM, h...@iafrica.com wrote: Hi I am looking for files named Q and not directories named Q. In my case I have thousands of assembler text files without filename extensions. It comes from early days starting out with TSC Flex and Uniflex followed by the Mark Williams Coherent operating systems. John On 2024/06/02 22:29, tsie...@softcon.com wrote: Don't know if it helps, but I've found that if you want *just* directory names, and you don't have a directory program that allows you to set flags, so it only shows directories, then the best way to get them is to do something like: dir *. Since most directory names don't have extensions, this only picks out the directory names (and of course, any files without extensions, but those are rare), so that should find the q directory for you with little to no trouble. On 6/2/2024 5:34 PM, hms--- via Freedos-user wrote: Hi All It appears that if a directory exists with the same name as the file one is searching for, the directory listing is terminated early without error. I was searching for a files named "Q" with no extension. I used the commands "DIR Q /S /B" and "DIR Q. /S /B", but it only revealed files in a directory named "Q". An example directory structure is shown below. Note that most of the file names below do not have extensions. The file named "Q" appears in all the subdirectories. I was puzzled and decided to dig a little further. Is this correct behaviour for the DIR command or a misunderstanding on my part about file name matching? Perhaps an anomaly or a bug? I have tried various DOS's with the same result, the DIR command being an internal one. I have also tried XCOPY and XXCOPY with the "/L" option and it also only finds the files in the "Q" directory. Any thoughts as to what's going on? John Directory of f:\a12\*.* [.] [..] [J] [Q] [Q.A] [Q1] [TS] Directory of f:\a12\j\*.* [.] [..] Q Directory of f:\a12\q\*.* [.] [..] Q Q.A Q.ASM Q1 Q12 Directory of f:\a12\q.a\*.* [.] [..] Q Q.A Directory of f:\a12\q1\*.* [.] [..] Q Q.A Q99 Directory of f:\a12\ts\*.* [.] [..] Q Q.A Q.ASM Entering the command below gives the following result. F:\>DIR Q /S /B f:\a12\q\Q f:\a12\q\Q.A f:\a12\q\Q.ASM f:\a12\q\Q1 f:\a12\q\Q12 The Q file is only found in the Q directory. Same result as above with:- F:\>DIR Q. /S /B Typing command: F:\>DIR Q.? /S /B Gives this result. f:\a12\Q f:\a12\Q.A f:\a12\j\Q f:\a12\q\Q f:\a12\q\Q.A f:\a12\q.a\Q f:\a12\q.a\Q.A f:\a12\q1\Q f:\a12\q1\Q.A f:\a12\ts\Q f:\a12\ts\Q.A The Q file is now found in all the subdirectories. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
Look at python for dos - http://www.caddit.net/pythond/ If it has the os module, I'll bet you could do it. On Sun, Jun 2, 2024, at 11:19 PM, hms--- via Freedos-user wrote: > Hi > I am looking for files named Q and not directories named Q. In my case I > have thousands of assembler text files without filename extensions. It > comes from early days starting out with TSC Flex and Uniflex followed by > the Mark Williams Coherent operating systems. > John > > On 2024/06/02 22:29, tsie...@softcon.com wrote: >> Don't know if it helps, but I've found that if you want *just* >> directory names, and you don't have a directory program that allows >> you to set flags, so it only shows directories, then the best way to >> get them is to do something like: >> >> dir *. >> >> Since most directory names don't have extensions, this only picks out >> the directory names (and of course, any files without extensions, but >> those are rare), so that should find the q directory for you with >> little to no trouble. >> >> >> On 6/2/2024 5:34 PM, hms--- via Freedos-user wrote: >>> Hi All >>> It appears that if a directory exists with the same name as the file >>> one is searching for, the directory listing is terminated early >>> without error. >>> I was searching for a files named "Q" with no extension. I used the >>> commands "DIR Q /S /B" and "DIR Q. /S /B", but it only revealed files >>> in a directory named "Q". >>> An example directory structure is shown below. Note that most of the >>> file names below do not have extensions. The file named "Q" appears >>> in all the subdirectories. >>> I was puzzled and decided to dig a little further. Is this correct >>> behaviour for the DIR command or a misunderstanding on my part about >>> file name matching? Perhaps an anomaly or a bug? I have tried various >>> DOS's with the same result, the DIR command being an internal one. I >>> have also tried XCOPY and XXCOPY with the "/L" option and it also >>> only finds the files in the "Q" directory. Any thoughts as to what's >>> going on? >>> John >>> >>> >>> Directory of f:\a12\*.* >>> [.] [..] [J] [Q] [Q.A] >>> [Q1] [TS] >>> >>> Directory of f:\a12\j\*.* >>> [.] [..] Q >>> >>> Directory of f:\a12\q\*.* >>> [.] [..] Q Q.A Q.ASM >>> Q1 Q12 >>> >>> Directory of f:\a12\q.a\*.* >>> [.] [..] Q Q.A >>> >>> Directory of f:\a12\q1\*.* >>> [.] [..] Q Q.A Q99 >>> >>> Directory of f:\a12\ts\*.* >>> [.] [..] Q Q.A Q.ASM >>> >>> Entering the command below gives the following result. >>> F:\>DIR Q /S /B >>> f:\a12\q\Q >>> f:\a12\q\Q.A >>> f:\a12\q\Q.ASM >>> f:\a12\q\Q1 >>> f:\a12\q\Q12 >>> >>> The Q file is only found in the Q directory. >>> >>> Same result as above with:- >>> F:\>DIR Q. /S /B >>> >>> Typing command: >>> F:\>DIR Q.? /S /B >>> Gives this result. >>> f:\a12\Q >>> f:\a12\Q.A >>> f:\a12\j\Q >>> f:\a12\q\Q >>> f:\a12\q\Q.A >>> f:\a12\q.a\Q >>> f:\a12\q.a\Q.A >>> f:\a12\q1\Q >>> f:\a12\q1\Q.A >>> f:\a12\ts\Q >>> f:\a12\ts\Q.A >>> >>> The Q file is now found in all the subdirectories. >>> >>> >>> >>> >>> ___ >>> Freedos-user mailing list >>> Freedos-user@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VICTORY! How I got networking operational in 86Box
Very good explanation, I'm hoping these findings make it to the release build of FreeDos as it will bring in more users if internet is available after all we all love tinkering with it and DOS does make it much easier -Ed EdzUp On Mon, 3 Jun 2024, 01:36 Brandon Taylor via Freedos-user, < freedos-user@lists.sourceforge.net> wrote: > I've been agonizing over the question of why I can't connect an 86Box > virtual machine powered by FreeDOS to the Internet. But now, it seems, I > have found a fix, or at least a preliminary one. > > Using a fine-toothed comb (as it were), I went over the FDAUTO.BAT file > and found that it referenced another batch file that handled all of the > networking stuff, namely, C:\FREEDOS\BIN\FDNET.BAT. So, going over THAT, I > arrived at what I figured was a critical line in the second batch file, > which was vinfo /m. Typing this into the command line didn't seem to do > anything, but when I typed vinfo /m | echo %errorlevel%, lo and behold, > FreeDOS returned the number 5. So, going back into FDNET.BAT, I eventually > arrived at this piece of code: > ``` > :hw086 > :hw186 > :hw286 > :hw386 > :hw486 > :hw586 > :hw686 > :NoHardware > vecho /t %_FDNET.LANG% ERROR.HARDWARE > goto End > ``` > and that's why it told me that Physical hardware networking is not > supported at this time. > > Well... > > Not willing to admit defeat, I continued going through FDNET.BAT to find > out what it was about VirtualBox and VMware that made the network go... > > ...and both of them branched to :vmGeneric. > > From THERE, I discovered that FreeDOS supports three network card > families: AMD PCnet, Realtek RTL8139, and NE2000-compatibles – the same > ones used by VirtualBox, VMware, and (though I haven't used FreeDOS on > this) QEMU! > > So, going back to the physical hardware section of the batch file, I > simply added a branching line after :hw686, so that the code block now > reads: > ``` > :hw086 > :hw186 > :hw286 > :hw386 > :hw486 > :hw586 > :hw686 > goto vmGeneric > > :NoHardware > vecho /t %_FDNET.LANG% ERROR.HARDWARE > goto End > ``` > and opened the 86Box configuration to install an AMD PCnet-FAST III into > an emulated PCI slot, which triggered a hard reset. > > And wouldn't you know? The network worked! > > I was able to ping www.google.com and get a pong sent back to me. I'm > kinda having a little bit of difficulty with fdnpkg though, so maybe > there are still some kinks to work out. But for right now, I can declare at > least a preliminary victory! > > Brandon Taylor > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unexpected results from DIR command
Hi I am looking for files named Q and not directories named Q. In my case I have thousands of assembler text files without filename extensions. It comes from early days starting out with TSC Flex and Uniflex followed by the Mark Williams Coherent operating systems. John On 2024/06/02 22:29, tsie...@softcon.com wrote: Don't know if it helps, but I've found that if you want *just* directory names, and you don't have a directory program that allows you to set flags, so it only shows directories, then the best way to get them is to do something like: dir *. Since most directory names don't have extensions, this only picks out the directory names (and of course, any files without extensions, but those are rare), so that should find the q directory for you with little to no trouble. On 6/2/2024 5:34 PM, hms--- via Freedos-user wrote: Hi All It appears that if a directory exists with the same name as the file one is searching for, the directory listing is terminated early without error. I was searching for a files named "Q" with no extension. I used the commands "DIR Q /S /B" and "DIR Q. /S /B", but it only revealed files in a directory named "Q". An example directory structure is shown below. Note that most of the file names below do not have extensions. The file named "Q" appears in all the subdirectories. I was puzzled and decided to dig a little further. Is this correct behaviour for the DIR command or a misunderstanding on my part about file name matching? Perhaps an anomaly or a bug? I have tried various DOS's with the same result, the DIR command being an internal one. I have also tried XCOPY and XXCOPY with the "/L" option and it also only finds the files in the "Q" directory. Any thoughts as to what's going on? John Directory of f:\a12\*.* [.] [..] [J] [Q] [Q.A] [Q1] [TS] Directory of f:\a12\j\*.* [.] [..] Q Directory of f:\a12\q\*.* [.] [..] Q Q.A Q.ASM Q1 Q12 Directory of f:\a12\q.a\*.* [.] [..] Q Q.A Directory of f:\a12\q1\*.* [.] [..] Q Q.A Q99 Directory of f:\a12\ts\*.* [.] [..] Q Q.A Q.ASM Entering the command below gives the following result. F:\>DIR Q /S /B f:\a12\q\Q f:\a12\q\Q.A f:\a12\q\Q.ASM f:\a12\q\Q1 f:\a12\q\Q12 The Q file is only found in the Q directory. Same result as above with:- F:\>DIR Q. /S /B Typing command: F:\>DIR Q.? /S /B Gives this result. f:\a12\Q f:\a12\Q.A f:\a12\j\Q f:\a12\q\Q f:\a12\q\Q.A f:\a12\q.a\Q f:\a12\q.a\Q.A f:\a12\q1\Q f:\a12\q1\Q.A f:\a12\ts\Q f:\a12\ts\Q.A The Q file is now found in all the subdirectories. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
