Re: [Freedos-devel] List of Exitcodes

On Thu, 29 May 2025, Aitor Santamaría via Freedos-devel wrote: Even more, I have to admit that when I wrote KEYB long time ago I used the same exit codes as MS-DOS KEYB (plus some extended codes that MS-DOS KEYB did not have), but it was so long ago that I can't even remember where I took the li

Re: [Freedos-devel]  Re: Kernel package question

On Tue, 27 May 2025, Jim Hall via Freedos-devel wrote: As a workaround, EDR-DOS added a copy of an email (I think from Bryan Sparks) that said it was okay to use code derived from CP/M. And from that, the EDR-DOS developers claimed that gave them a loophole to keep working on EDR-DOS without wor

Re: [Freedos-devel] alias - bug or feature?

FWIW: doskey keeps track through its own internal buffers, and the MS-DOS command.com calls out to doskey through a documented interface (falling back onto int21/0Ah if that doesn't work). That way, aliases persist from instance to instance because it's handled by a separate TSR app. -uso.

Re: [Freedos-devel] SETVER support

On Mon, 28 Apr 2025, Bret Johnson via Freedos-devel wrote: Unfortunately, not all programs are that simple. Many of the MS utility programs are looking for a very specific version of DOS, but some are looking for "categories". On some of my programs, e.g., I have a "GetDOSVersion" subroutine

Re: [Freedos-devel] FreeDOS 1.4

On Mon, 17 Mar 2025, Ralf Quint via Freedos-devel wrote: On 3/16/2025 3:36 PM, Jim Hall via Freedos-devel wrote: On Sun, Mar 16, 2025 at 4:29 PM Jerome Shidel via Freedos-devel wrote: [..] PS: I will call Jenny to let her know. Just send me her number. (You would have had to be present during

Re: [Freedos-devel] What the AI says about the problem of Out of memory

Replying here since I'm having trouble finding the place where exemod was actually mentioned. On Wed, 19 Feb 2025, Bernd Böckmann via Freedos-devel wrote: I agree with Tom that changing the EXE header should be to way to go. I wrote a replacement for exemod last year, but I never got around

Re: [Freedos-devel] Proposal: replace FreeDOS Edit with SvarDOS Edit

Weird semi-related thought... I wonder if IBM could be convinced to open up either E (their full editor which is used in PC DOS 6 and 7), or T (a smaller rewrite of E that they own the rights to). Neither of those are exactly CUA, although the last version of E kindasorta fits that, and I kno

Re: [Freedos-devel] Proposal: remove FDTUI

On Mon, 17 Feb 2025, tom ehlert via Freedos-devel wrote: I think that every program beyond the default MSDOS programs raises some level of noise. They might be useful, but having hundred of unknown (to me) programs thrown into the same \BIN\ directory doesn't motivate me to search HELP on all

Re: [Freedos-devel] Proposal: remove FDTUI

On Sun, 16 Feb 2025, Jim Hall via Freedos-devel wrote: I think we need to drop FDTUI, and not include it in FreeDOS 1.4. ACTION: I'm looking for consensus. Please release with "+1" if you agree or comments if not. +1 Don't we already have ViewMax which is literally DR DOS's counterpart of D

Re: [Freedos-devel] Search all text file contents in directories recursively

On Fri, 7 Feb 2025, tom ehlert via Freedos-devel wrote: It's a port of GNU grep 2.0 (1992). It does not support recursion by itself yet (-r). Therefore one would need a real mode port of GNU or BSD find, which unfortunately does not seem to be available for FreeDOS. Couple options then:

Re: [Freedos-devel] Search all text file contents in directories recursively

On Fri, 7 Feb 2025, Bruno Ribeiro via Freedos-devel wrote: It's a port of GNU grep 2.0 (1992). It does not support recursion by itself yet (-r). Therefore one would need a real mode port of GNU or BSD find, which unfortunately does not seem to be available for FreeDOS. Not sure at what point

Re: [Freedos-devel] Search all text file contents in directories recursively

On Fri, 7 Feb 2025, Bruno Ribeiro via Freedos-devel wrote: On 7/2/2025 11:42, Steve Nickolas via Freedos-devel wrote: That makes sense. It's on keel with MS-DOS 6.22, which is FreeDOS' intention. I see. But that's more like the minimum goal of FreeDOS, right? To be at leas

Re: [Freedos-devel] Search all text file contents in directories recursively

On Fri, 7 Feb 2025, Bruno Ribeiro via Freedos-devel wrote: Hi Steve, On 7/2/2025 10:51, Steve Nickolas via Freedos-devel wrote: On Fri, 7 Feb 2025, Bruno Ribeiro via Freedos-devel wrote: What's the DOS equivalent of the Unix find-grep combo for searching recursively within a director

Re: [Freedos-devel] Search all text file contents in directories recursively

On Fri, 7 Feb 2025, Bruno Ribeiro via Freedos-devel wrote: What's the DOS equivalent of the Unix find-grep combo for searching recursively within a directory all files matching a given criteria for strings within them matching a given expression? Put in other words, more simply, how do I find w

Re: [Freedos-devel] Costa GUI (MIT license), written in Visual Basic for DOS

On Wed, 22 Jan 2025, Liam Proven via Freedos-devel wrote: On Tue, 21 Jan 2025 at 16:02, Steve Nickolas wrote: While it's easy as cake to do UIs with VBDOS, there's no way to port to anything else. That makes sense, yes. What I do not know, but that Jacob's comments imply,

Re: [Freedos-devel] Costa GUI (MIT license), written in Visual Basic for DOS

On Tue, 21 Jan 2025, Liam Proven via Freedos-devel wrote: How will any version of a BASIC compiler help port a BASIC app to any C compiler? While it's easy as cake to do UIs with VBDOS, there's no way to port to anything else. QBX, on the other hand, is not that different to C; pretty much

Re: [Freedos-devel] Costa GUI (MIT license), written in Visual Basic for DOS

On Mon, 20 Jan 2025, Liam Proven via Freedos-devel wrote: On Mon, 20 Jan 2025 at 22:57, Steve Nickolas via Freedos-devel wrote: On Mon, 20 Jan 2025, Liam Proven via Freedos-devel wrote: I was wrong. One module is in Turbo Pascal but the rest is indeed VB DOS or MS Basic PDS 7.1. I must

Re: [Freedos-devel] Costa GUI (MIT license), written in Visual Basic for DOS

On Mon, 20 Jan 2025, Liam Proven via Freedos-devel wrote: I was wrong. One module is in Turbo Pascal but the rest is indeed VB DOS or MS Basic PDS 7.1. Hm. Converting from QBX 7 to something like Watcom or DJGPP would be a LOT easier than converting from VBDOS (safe insofar as VBDOS code can

Re: [Freedos-devel] Ré : Use Links rather than Lynx

On Thu, 16 Jan 2025, Paul Dufresne via Freedos-devel wrote: But Links in 1.4-RC1 under VirtualBox 7.1.4 seems to "always" work. Could it be that the other browsers don't understand "http vhost" ? -uso. ___ Freedos-devel mailing list Freedos-devel@

Re: [Freedos-devel] Costa GUI (MIT license), written in Visual Basic for DOS

On Wed, 15 Jan 2025, Danilo Pecher via Freedos-devel wrote: To be honest, it looks like just another student project cobbled together while flunking math lessons. I've written at least two of those in the nineties and soon learned I was going nowhere. To be frank, we shouldn't try to bloat FreeD

Re: [Freedos-devel] Free to use code project 2024

I started to write an Apple ][ emu in ASM but my CPU code is braindead. There is "apl2em" which has a 65C02 core, but that's some ancient masm code with heavy macros. C's a lot easier to find (I have source to several cores with MIT licenses) but you're going to need a mid-range 486 minimum ev

Re: [Freedos-devel] muefircate: a plan for a BIOS loader for UEFI

On Mon, 23 Dec 2024, Volkert via Freedos-devel wrote: Also, muefircate (and its predecessor BiEFIrcate) have been mentioned in threads in freedos-devel before, but there hasn't been much engagement on it. That's really unfortunate, since this project seems

Re: [Freedos-devel] Interim Releases: switching to current Kernel and FreeCOM?

On Sat, 21 Dec 2024, Eric Auer via Freedos-devel wrote: As Win3 came bundled with MS HIMEM and MS EMM386, people only need a compatible FreeDOS kernel to use Win3 in 386enh mode without needing MS DOS. Of course it would be interesting to have compatible open source HIMEM and EMM386 alternatives

Re: [Freedos-devel] Contributing

On Fri, 20 Dec 2024, Liam Proven via Freedos-devel wrote: On Tue, 17 Dec 2024 at 21:35, Steve Nickolas via Freedos-devel wrote: IBM. They owned the copyright jointly from version 3.1 onward (note that they specifically said they had to get the OK from IBM to release the 4.0 sources). IBM

Re: [Freedos-devel] Contributing

On Tue, 17 Dec 2024, Liam Proven via Freedos-devel wrote: On Mon, 16 Dec 2024 at 19:23, Steve Nickolas via Freedos-devel wrote: Part of the problem there was MS didn't have full copyright. [[citation needed]] Who else? IBM. They owned the copyright jointly from version 3.1 onward

Re: [Freedos-devel] Contributing

Cell phone - harder to be "proper". On Mon, 16 Dec 2024, Liam Proven via Freedos-devel wrote: I think you misinterpret me. I think there is basically zero chance MS will make Windows 1, 2 or 3 FOSS. (I suspect it's ashamed of the code, if it still has it at all. FOSS MS-DOS 4 only happened be

Re: [Freedos-devel] Contributing

On Mon, 16 Dec 2024, Liam Proven via Freedos-devel wrote: On Sun, 15 Dec 2024 at 07:25, Steve Nickolas via Freedos-devel wrote: I mean, something like a free Windows 3.0 or a free Desqview/X would be nice, but eh. It would indeed. The thing is, it more or less exists: it's PC

Re: [Freedos-devel] Contributing

On Sun, 15 Dec 2024, Danilo Pecher via Freedos-devel wrote: I don't think you'll find too many 8086 machines these days, let alone 80186. I fact I saw such a thing once in my entire life. A Triumph-Adler with an amber monochrome monitor, which I found so cool, I still change the font settings to

Re: [Freedos-devel] Contributing

On Sat, 14 Dec 2024, Ben Collver via Freedos-devel wrote: Thanks for the explanation. Reminds me of folks who made grand plans for programming projects and perhaps wrote some scaffolding code, but never finished anything. A whole new GUI or multitasking system built on top of DOS would be gr

Re: [Freedos-devel] Contributing

On Sat, 14 Dec 2024, Ben Collver via Freedos-devel wrote: A lot of FreeDOS novices seem to want to turn it into Linux, the same way a lot of Linux novices seem to want to turn it into Windows - and I think it probably galls some of the old-timers here. Seems to me there is an old tradition of

Re: [Freedos-devel] Contributing

On Sun, 15 Dec 2024, tom ehlert via Freedos-devel wrote: Hallo Herr Steve Nickolas via Freedos-devel, am Sonntag, 15. Dezember 2024 um 01:09 schrieben Sie: Also for what it's worth, if Microsoft ever opens the 5.0 sources (this isn't a non-zero chance) that may be enough to use i

Re: [Freedos-devel] Contributing

On Sun, 15 Dec 2024, Danilo Pecher via Freedos-devel wrote: Tom, what's the joke with the references to Linux? Not that I would mind. I've run Linux since 1994. Took home an early Slackware system on 64 floppy disks, had to write an X11 driver for my weird-ass 512K Realtek SVGA card and then rui

Re: [Freedos-devel] Source code distribution

On Fri, 27 Sep 2024, Michael Brutman via Freedos-devel wrote: There isn't much that can be done about the binaries getting stale, as a distribution is a snapshot of what was available at the time. But I'd love to find a way where FreeDOS doesn't have to take responsibility for shipping source c

Re: [Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

On Wed, 21 Aug 2024, Ralf Quint via Freedos-devel wrote: On 8/16/2024 1:43 AM, Steve Nickolas via Freedos-devel wrote: Is the EMM386 in MS-DOS 4.x new enough for that? I haven't specifically looked for that, but given that the source code released is likely an early version of MS-DO

Re: [Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

On Fri, 16 Aug 2024, Aitor Santamaría via Freedos-devel wrote: Hi, On Wed, 8 May 2024 at 04:19, Ralf Quint via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: What could be however of value is to look at the source for some of the "trouble spots". For example, for me, the wit

Re: [Freedos-devel] convert ms-dos code to C#

On Thu, 1 Aug 2024, magic-girl--- via Freedos-devel wrote: Sorry i can't make C# code for this, which is exactly my question. Can you give me C# code that reads the THF file and prints the same as the screenshot ? You might do better to use a C compiler for your target platform instead of C

Re: [Freedos-devel] development and advertising plan

Tell me you know nothing about FreeDOS without telling me you know nothing about FreeDOS. -uso. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] 16-bit Windows development

On Tue, 11 Jun 2024, Chelson a via Freedos-devel wrote: Yes obviously the legal side of things prevents using that code, it's also a good reference of how it all works and you could build from scratch. Do that and you'll be sued into the ground faster than you can say "Chinese wall". -uso.

Re: [Freedos-devel] 16-bit Windows development

On Sun, 9 Jun 2024, daniel silva ferreira bruno via Freedos-devel wrote: Hi, people. What about the ArcaOS? It can run Windows 16-bit applications among other applications. Cheers, Daniel, An enthusiastic for DOS from Brazil. OS/2 is the rights snarl to end all rights snarls. Also, it runs

Re: [Freedos-devel] Back at it with DOG

On Thu, 30 May 2024, Wolf Bergenheim via Freedos-devel wrote: I'm using Borland C++ 3.1 for now as that's the compiler I used 22 years ago... Looks like porting to Watcom will require a bit of work... It is something I want to do eventually, I think. Just need to read up on the inline assembler

Re: [Freedos-devel] Email test

On Mon, 27 May 2024, Jim Hall via Freedos-devel wrote: My email to the list bounced as undeliverable, but I'm sending this test just in case it was a temporary hiccup. Can someone reply to this thread if you can see this message? *sent May 27 11:20pm Second attempt - first one immediately g

Re: [Freedos-devel] zoo

On Wed, 22 May 2024, tom ehlert via Freedos-devel wrote: it seems that no knowledgable person finds zoo interesting enough to fix it. and those who care about zoo have no clue. I regret that I have to say this. Tom Was zoo even popular in its heyday? I feel like when it comes to DOS, for th

Re: [Freedos-devel] still can't find the source code

On Fri, 10 May 2024, Green Fog via Freedos-devel wrote: There you go. The 2 requirements for free dos being a thing are just not there. not ease of use. I need to use an antique mail list for communication and wiki/documentation. It's absurd and very not efficient. I am very busy, and I can't af

Re: [Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

On Tue, 7 May 2024, Ralf Quint via Freedos-devel wrote: I don't think there is really a point in trying to get the whole thing compiled with FOSS tools. This is just a Sisyphos task, for no or very little gain. There is a reason why they included the old, matching tools in the release. I thi

Re: [Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

On Sat, 4 May 2024, Bernd Böckmann via Freedos-devel wrote: Hello Steve, Some of the code's pretty braindead, too.  Especially what looks to have come from IBM.  I mean...house styles vary, but Algolization is still just hideous-looking.  But it goes beyond that - think some of the utilities

Re: [Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

On Fri, 3 May 2024, Jim Hall via Freedos-devel wrote: On Fri, May 3, 2024, 10:53 PM Steve Nickolas via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: So I've had some thoughts regarding the MS-DOS 4 source drop, regarding [...] (The obvious question: Why not use w

[Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

So I've had some thoughts regarding the MS-DOS 4 source drop, regarding things I'd like to do with the code. I'm not really that good of a coder and probably would only be able to do some of them myself. (I'd kill for a 3.3 drop - would obviate a lot of these things! And 5 and 6.2 even more.

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

On Thu, 2 May 2024, Liam Proven via Freedos-devel wrote: On Fri, 26 Apr 2024 at 08:25, Steve Nickolas via Freedos-devel wrote: Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, apparently. I got most of it compiled using the tools in the archive. That being the case, is

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

On Thu, 2 May 2024, Eric Auer via Freedos-devel wrote: Hi! I have no life - I can devote the time and energy to it, just don't have the brainpower I'd like to think I have. I hope that will get better :-o Eric Well, I certainly know more about C, 8088 ASM, and MS-DOS than I did going in

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

On Tue, 30 Apr 2024, tom ehlert via Freedos-devel wrote: I have no idea why I would recompile old MS stuff, but as a hobby it's ok. 6.21 would be much more useful and no doubt a lot more people would want to do what I'm trying to do for 4.01 with a 6.21 source drop. (Even 5.0 would be more

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

On Tue, 30 Apr 2024, Bernd Böckmann via Freedos-devel wrote: Sadly not. Only the binaries are released under MIT through the repository. Does that mean we finally have a genuinely open sourced OMF linker? -hpa It's my opinion that including them was more of a fortuitous accident than actua

Re: [Freedos-devel] FreeDOS Windows for Workgroups howto

On Sun, 28 Apr 2024, Eric Auer via Freedos-devel wrote: - Use the Microsoft versions of HIMEM and EMM386 and SMARTDRV (bundled with Windows, alternatively from MIT-released MSDOS 4?) so update your config and autoexec accordingly HIMEM 2.04 is included in 4.0, but it wasn't in the source d

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

On Fri, 26 Apr 2024, Eric Auer via Freedos-devel wrote: As mentioned by DOSEMU2 people, this is a somewhat exotic, but interesting MS DOS 4.00, not the once widespread 4.01: Actually, apart from having the io.sys sources to the multitasking 4, this is the regular 4.x line from 1988. Most of

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

On Fri, 26 Apr 2024, Bernd Böckmann via Freedos-devel wrote: Microsoft and IBM released the source code of MS-DOS 4.0 under MIT license [1]. To me, it looks fairly complete. Everything but himem, dosshell, gwbasic, and parts of xmaem/xma2ems, apparently. I got most of it compiled using the t

Re: [Freedos-devel] Is there an open source fmt clone for DOS?

On Wed, 24 Jan 2024, Jim Hall via Freedos-devel wrote: I'm looking for a way to keep my text files (like README.TXT) tidy and easy to read. One problem is that if I modify a plain text file in a regular text editor, and change the line length in the middle of a paragraph, now I have to fix all t

Re: [Freedos-devel] Learning DOS assembly programming

On Tue, 26 Dec 2023, Jim Hall via Freedos-devel wrote: I actually never learned DOS assembly programming, but decided I'd like to start. What assembler do you recommend, and where is a good place to start learning about DOS assembly programming? Start with a "Hello world" program and eventually

Re: [Freedos-devel] VME broken on Ryzen CPU, autodetection useful?

On Mon, 13 Nov 2023, Rugxulo via Freedos-devel wrote: Ryzen (Zen 1) was brand new in 2017, redesigned from scratch. I doubt the current Zen 4 (2022) has that bug, but who knows. (Now that the BIOS and CSM are dead, they may not care to fix it. And the whole "x86-S" rumors imply legacy is going a

Re: [Freedos-devel] i have a tech question about 286 and XMS

On Thu, 2 Nov 2023, Deposite Pirate via Freedos-devel wrote: You should read again what he said. A 286 running a DOS doesn't need "maintained drivers". If fdxms286 works on a 286, there is no reason it's not going to work or in a lesser way now. DOS is not Linux/BSD. People forget that it's p

Re: [Freedos-devel] FreeDOS Phishing attack - warning!

On Thu, 2 Nov 2023, Harald Arnesen via Freedos-devel wrote: Jim Hall via Freedos-devel [02/11/2023 11.12]: So now phishers are pretending to be FreeDOS emails. That's pretty targeted phishing (aka "spear phishing" where attackers customize the email to be very specific to the recipient). Th

Re: [Freedos-devel] FreeDOS Interim Build T2310 - no free space on CD

On Thu, 5 Oct 2023, Liam Proven via Freedos-devel wrote: On Thu, 5 Oct 2023 at 10:29, Danilo Pecher via Freedos-devel wrote: The best solution would be three disks: BaseCD - no bigger than 300MB, only basic tools ApplicationCD - Editors, Gemes, Utilities - the lot DeveloperCD I agree wit

Re: [Freedos-devel] dir issues

On Thu, 10 Aug 2023, Liam Proven via Freedos-devel wrote: On Wed, 9 Aug 2023 at 00:13, Rugxulo via Freedos-devel wrote: (DJGPP v1 SDK) What does DV have to do with DJGPP? I'm not sure it was *DJGPP*. It *was* based on GCC - and I do think it was GCC 1 - but that's the extent of my k

Re: [Freedos-devel] dir issues

On Tue, 8 Aug 2023, Rugxulo via Freedos-devel wrote: Long story short: I don't think FreeDOS not having a DOSshell clone is a significant omission. Nobody will write the "program switcher" code (too complex), and we already have file managers. So I don't see what else it would offer. Feel free t

Re: [Freedos-devel] CD-ROMs was ANSI for DOS

On Mon, 7 Aug 2023, Danilo Pecher via Freedos-devel wrote: Yeah, around 1993 was when the first ones arrived. I know I was hearing about CD-ROM drives connected to the Apple IIgs when I was still in grade school (so no later than mid-1990)... -uso.

Re: [Freedos-devel] CD-ROMs was ANSI for DOS

On Mon, 7 Aug 2023, Danilo Pecher via Freedos-devel wrote: The first one I can remember was the Mitsumi CRMC-LU005S single speed drive, which was the one I had. It had its own card because it was non-IDE despite the fact that the cable and plug looked exactly like IDE. They did use a proprietary

Re: [Freedos-devel] Interesting behavior with PC Tools

On Sun, 30 Jul 2023, Jim Hall via Freedos-devel wrote: *Aside: I thought QBASIC would only run on MS-DOS, but I checked the screenshot the user sent me; it's really MS-DOS QBASIC, not QuickBASIC or something else. And the series of screenshots they sent indicated QBASIC was running on FreeDOS. S

Re: [Freedos-devel] dir issues

On Fri, 28 Jul 2023, Jose Senna via Freedos-devel wrote: While I am just an user, I also think that a GUI for DOS is not an important improvement. As Liam Proven, I think that a shell that is a good app launcher, file manager and provides fast task switching with a small memory footprint would b

Re: [Freedos-devel] dir issues

On Sun, 23 Jul 2023, tom ehlert via Freedos-devel wrote: ISTM that all the other graphical shells in FreeDOS are even less useful than GEM, and it would be no loss to remove them... but adding GEOS would be a win. in what way is GEOS even related to FreeDOS which runs on PC's? unless wikipe

Re: [Freedos-devel] Reminder: FreeDOS virtual get-together on June 18

On Sun, 18 Jun 2023, Jim Hall wrote: Yes, 11am Central Time is just under two hours from now. :⁠-⁠) And just shy of an hour from now, 11 Eastern. -uso.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/l

Re: [Freedos-devel] EXIST NUL

On Wed, 14 Jun 2023, Mercury Thirteen via Freedos-devel wrote: Unfortunately, in many cases, it has to be an absolute rule. I totally get the mindset (and semi-subscribe to it myself)of wanting FreeDOS to be a kind of MS-DOS but improved in every way possible including fixing Microsoft's bugs

Re: [Freedos-devel] Minor problems FreeDOS 1.3 (Spanish translation)

On Sat, 8 Apr 2023, Andrew Bird via Freedos-devel wrote: I think I can shorten the Spanish text, which fixes both the alignment problem and the lack of a space. I'll send a PR but I'd be grateful if somebody can check the text there as my Spanish is mostly beginner level. es_ES in PC DOS 6.

Re: [Freedos-devel] DOS 44h (Get Device Information) - CD-ROM marked as remote?

On Mon, 13 Mar 2023, Aitor Santamaría wrote: Hello, A quick question, if I query device information on CD-ROM (int 21h, AX=4409h), will I get that a CD-ROM drive is remote? (bit 12 = 1). I am getting this under XP's ntvdm, and it sounds as a correct thing (the filesystem is not FAT), but I wo

Re: [Freedos-devel] DOS Swappable Data (SDA) Area

On Wed, 8 Mar 2023, Michael Brutman wrote: Sorry, we have a terminology issue here. (Again.) A Virtual Machine for the rest of us is something like VMWare, Qemu, VirtualBox, etc. - something that simulates a real machine. You load a real operating system in it and the operating system general

Re: [Freedos-devel] DOS Swappable Data (SDA) Area

On Tue, 7 Mar 2023, Rugxulo wrote: Maybe you mean something like this? "Apple’s MS-DOS Compatible 486 Macintosh from 1995!" -- LGR "The Power Macintosh 6100/66 DOS Compatible is a fascinating machine. For $2,199 in 1995 you got MS-DOS and Mac OS in one computer, thanks to an Intel 486 and a Po

Re: [Freedos-devel] 386MAX

On Mon, 6 Mar 2023, Bret Johnson wrote: Or just take some of the important stuff that Bob Smith and Qualitas discovered about Windows/GEMMIS/EMM386 and import it into something like JEMM. There's some knowledge embedded in 386MAX about what MS did that you will never directly get out of MS.

Re: [Freedos-devel] MS-DOG (was Re: [Freedos-user] FSF)

On Wed, 1 Mar 2023, Ralf Quint wrote: On 3/1/2023 6:12 AM, tom ehlert wrote: Hallo Herr Rugxulo, am Mittwoch, 1. März 2023 um 10:22 schrieben Sie: Hi again, It's entirely possible that Richard dislikes DOS that much. I also dislike Richard. we can leave it at that. That makes two of us.

Re: [Freedos-devel] Proposal: remove Graphical Desktops from next FreeDOS

On Wed, 22 Feb 2023, Liam Proven wrote: On Sun, 19 Feb 2023 at 17:52, Jim Hall wrote: It's been a few days since the last comment on this thread, so I think those who have an opinion on this have voiced it. Just seen it. I've moved house recently and have no broadband at my new place. The

Re: [Freedos-devel] FreeDOS package issues

On Sun, 19 Feb 2023, Jim Hall wrote: On Wed, Feb 15, 2023 at 4:30 PM Steve Nickolas wrote: Would it be something not too hard to bang out with a decent C compiler? I've never written a CD player interface per se, but if all the information can be retrieved, and all the commands c

Re: [Freedos-devel] FreeDOS package issues

On Wed, 15 Feb 2023, E. Auer wrote: Well, you can tell a CD drive to play track X using my minimalist cdrom2ui, but I think that would be sort of an INdecent open source alternative because it is too minimal :-D On the other hand, a QuickBasic solution sounds like something needing FreeBASIC in

Re: [Freedos-devel] Google Summer of Code?

On Sun, 29 Jan 2023, tom ehlert wrote: but I think the black box with the command prompt in Windows is indead often called the DOS VM or DosBox. DOS Virtual Machine, yeah. -uso. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net ht

Re: [Freedos-devel] Google Summer of Code?

On Fri, 27 Jan 2023, tom ehlert wrote: this argument is nonsense. many/most people don't care about the 'open source' part as long as it's free. This. most care more if this OS supports big disks or much memory. after all, an OS is not an end target: people need the OS to run their applicat

Re: [Freedos-devel] UEFI, virtual BIOS and virtual hardware - was: Goo gle Summer of Code?

On Tue, 24 Jan 2023, Bret Johnson wrote: For purposes we're discussing here, I don't think DOSBox (or any of its forks, including vDOS) is a viable solution. DOSBox really isn't DOS. It's an environment designed to run certain DOS applications. A lot of stuff is missing in DOSBox that's nee

Re: [Freedos-devel] UEFI, virtual BIOS and virtual hardware - was: Google Summer of Code?

On Mon, 23 Jan 2023, E. Auer wrote: Depending on how thin the glue and VM layer will be, you will be able to run fewer or more DOS apps with it. You can run some DOS apps in CTTY serial consoles if they only use int 21 for user I/O. There are support modes for simple DOS apps in some boot mana

Re: [Freedos-devel] Google Summer of Code?

On Sun, 22 Jan 2023, Jerome Shidel wrote: Assuming Google does not scrap GSoC amidst the layoffs, I have a thought. Perhaps it could be used to solve one of the most frequent problems I hear. Running FreeDOS on modern UEFI hardware. As we are all well aware, this cannot be directly accompli

Re: [Freedos-devel]  Re: Where to start and continue?

My comments here are directed to the OP, but build off the message to which I am replying. On Sun, 15 Jan 2023, jer...@shidel.net wrote: I don’t think your ready to tackle assembly under DOS yet. Not only do you need to know some variant of assembly language. That really does require some u

Re: [Freedos-devel] Linking asm with C

On Fri, 13 Jan 2023, Knedlik wrote: To be honest, I’m just following a tutorial that said it’s better to do it in asm - but it’s in Pascal, so I’m translating it into C. Only reason you'd want to use ASM rather than C is to try to optimize it beyond what the compiler can do. -uso.__

Re: [Freedos-devel] Linking asm with C

On Fri, 13 Jan 2023, Knedlik wrote: void clearScreen(char color) { int i; for (i = 0xa000; i < 0xfa00; i++) { char* byte = i; *byte = color; } } This is completely wrong. Mode 0x13, right? void clearScreen (char color) { char far *screen; unsigned int i; screen=MK_

Re: [Freedos-devel] Linking asm with C

On Fri, 13 Jan 2023, Knedlik wrote: To be fair, I myself am not sure about this. It’s the default options, so I would assume the watcom linker and whatever memory model open watcom is using. The default for OpenWatcom is the small model. I happen to know how to do this only for the specific

Re: [Freedos-devel] Toggling directories

On Sat, 12 Nov 2022, tom ehlert wrote: maybe even one of our assembler gurus looks at published sources of msdos 2.01 The 2.11 sources won't say anything here, as the DIRCMD stuff wasn't introduced to MS-DOS until 5.0. I checked the behavior with PC DOS 2000 since that was my preferred ver

Re: [Freedos-devel] Toggling directories

On Fri, 11 Nov 2022, tom ehlert wrote: virtually all options toggle, but someone probably noted that /P should not toggle, because even after set DIRCMD=/P DIR /P should still pause. MSDOS probably has not toggling at all (I'm not sure; someone who is not named Tom should test this), and o

Re: [Freedos-devel] New version of text editor (and image viewer) Blocek

On Fri, 28 Oct 2022, Rugxulo wrote: Hi, On Fri, Oct 28, 2022 at 6:14 AM Eric Auer wrote: I noticed that Jim's TRCH only translates one char at a time, do we already have a variant which is as powerful as Linux "TR", supporting for example TR 'a-z' 'A-Z' or TR -d '\n' and so on? DJGPP's Tex

Re: [Freedos-devel] CLS reimplementation (Re: VERIFY reimplementation)

On Wed, 14 Sep 2022, Bitácora de Javier Gutiérrez Chamorro (Guti) wrote: Dear Jim,   There is no practical purpose on my mind, just the challenge of rapidly and efficiently convert it. As you said, both CLS and VERIFY are internal commands. What surprised me about your ANSI fallback is that D

Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?

On Mon, 29 Aug 2022, Bret Johnson wrote: I'll try to search for an appropriate license and e-mail it to you. I've been searching though a little bit of licensing info and really didn't know that even declaring that something is "public domain" doesn't necessarily mean what you think it means.

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

For what it's worth: I have a 286 I still use. A 286 is enough for the Win95 version of EDIT.COM (it uses some 186 opcodes), so that's usually what I go with. It's still important to *me* to be able to support 8086 and 286 PCs. But with that said, I've felt that that's best done by me codin

Re: [Freedos-devel] MS-DOS compatibility issue

On Fri, 29 Jul 2022, Ralf Quint wrote: Well, not having comments to understand what you are doing is pretty tough when you don't have the time to analyze the code line by line. But IIRC, the common way to check for the presence of an ANSI device driver was to check via an INT 2Fh (multiplexer)

Re: [Freedos-devel] Another implementation of GRAFTABL

On Tue, 12 Jul 2022, Aitor Santamaría wrote: Once solved the "legal issues", one way to go could be to enrich DISPLAY instead of making a new driver. DISPLAY is organised as having "sub-drivers": DISPLAY CON = (EGA,437,2) where "EGA" is used to select the sub-driver, 437 is to declare the code

Re: [Freedos-devel]  Re: Another implementation of GRAFTABL

On Tue, 12 Jul 2022, Wilhelm Spiegl wrote: Hi, I just looked at my website http://home.mnet-online.de/willybilly/fdhelp-108a-internet/en/hhstndrd/base/graftabl.htm and noticed that the documentation for graftabl from 2007 is extremely short, strictly speaking: there is none. As I never learned

Re: [Freedos-devel] Another implementation of GRAFTABL

On Tue, 12 Jul 2022, C. Masloch wrote: On at 2022-07-12 15:45 -0400, Steve Nickolas wrote: I haven't uploaded a copy of the new source anywhere yet - it'll probably be in the next DOSLITE source batch along with my work on a few other DOS commands, but I don't want to replac

Re: [Freedos-devel] Another implementation of GRAFTABL

On Tue, 12 Jul 2022, C. Masloch wrote: Your technique is the default way to do this, most TSRs ever written did it that way. The SMC is just a small optimisation over it. Codegolfing is good, when done right. :D If you really want to continue to use the free software release of Microsoft's D

Re: [Freedos-devel] Another implementation of GRAFTABL

I haven't uploaded a copy of the new source anywhere yet - it'll probably be in the next DOSLITE source batch along with my work on a few other DOS commands, but I don't want to replace the copy I've already uploaded, and DOSLITE isn't ready to go onto anything like github or gitlab yet. As I

Re: [Freedos-devel] Another implementation of GRAFTABL

On Tue, 12 Jul 2022, C. Masloch wrote: (Only replied-to portions copied) Further, you calculate the size of the PSP block to keep resident by using test, add, and shifts: mov dx, trans ; Allow everything preceding the test dx, 0x000F ; transie

  1   2   3   4   >