Re: [Freedos-devel] Source code distribution

2024-09-28 Thread Steve Nickolas via Freedos-devel
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

2024-08-21 Thread Steve Nickolas via Freedos-devel
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

2024-08-16 Thread Steve Nickolas via Freedos-devel
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#

2024-07-31 Thread Steve Nickolas via Freedos-devel
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

2024-07-12 Thread Steve Nickolas via Freedos-devel
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

2024-06-10 Thread Steve Nickolas via Freedos-devel
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

2024-06-09 Thread Steve Nickolas via Freedos-devel
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

2024-05-30 Thread Steve Nickolas via Freedos-devel
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

2024-05-28 Thread Steve Nickolas via Freedos-devel
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

2024-05-22 Thread Steve Nickolas via Freedos-devel
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

2024-05-10 Thread Steve Nickolas via Freedos-devel
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

2024-05-07 Thread Steve Nickolas via Freedos-devel
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

2024-05-04 Thread Steve Nickolas via Freedos-devel
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

2024-05-03 Thread Steve Nickolas via Freedos-devel
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

2024-05-03 Thread Steve Nickolas via Freedos-devel
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

2024-05-02 Thread Steve Nickolas via Freedos-devel
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

2024-05-02 Thread Steve Nickolas via Freedos-devel
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

2024-04-30 Thread Steve Nickolas via Freedos-devel
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

2024-04-30 Thread Steve Nickolas via Freedos-devel
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

2024-04-28 Thread Steve Nickolas via Freedos-devel
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

2024-04-26 Thread Steve Nickolas via Freedos-devel
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

2024-04-26 Thread Steve Nickolas via Freedos-devel
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?

2024-01-24 Thread Steve Nickolas via Freedos-devel
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

2023-12-26 Thread Steve Nickolas via Freedos-devel
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?

2023-11-13 Thread Steve Nickolas via Freedos-devel
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

2023-11-02 Thread Steve Nickolas via Freedos-devel
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!

2023-11-02 Thread Steve Nickolas via Freedos-devel
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

2023-10-05 Thread Steve Nickolas via Freedos-devel
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

2023-08-10 Thread Steve Nickolas via Freedos-devel
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

2023-08-08 Thread Steve Nickolas via Freedos-devel
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

2023-08-06 Thread Steve Nickolas via Freedos-devel
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

2023-08-06 Thread Steve Nickolas via Freedos-devel
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

2023-07-30 Thread Steve Nickolas via Freedos-devel
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

2023-07-28 Thread Steve Nickolas via Freedos-devel
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

2023-07-23 Thread Steve Nickolas via Freedos-devel
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

2023-06-18 Thread Steve Nickolas
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

2023-06-14 Thread Steve Nickolas
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)

2023-04-08 Thread Steve Nickolas
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?

2023-03-12 Thread Steve Nickolas
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

2023-03-08 Thread Steve Nickolas
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

2023-03-07 Thread Steve Nickolas
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

2023-03-06 Thread Steve Nickolas
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)

2023-03-01 Thread Steve Nickolas
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

2023-02-22 Thread Steve Nickolas
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

2023-02-19 Thread Steve Nickolas
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

2023-02-15 Thread Steve Nickolas
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?

2023-01-29 Thread Steve Nickolas
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?

2023-01-27 Thread Steve Nickolas
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?

2023-01-24 Thread Steve Nickolas
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?

2023-01-23 Thread Steve Nickolas
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?

2023-01-22 Thread Steve Nickolas
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?

2023-01-15 Thread Steve Nickolas
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

2023-01-13 Thread Steve Nickolas
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

2023-01-13 Thread Steve Nickolas
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

2023-01-13 Thread Steve Nickolas
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

2022-11-12 Thread Steve Nickolas
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

2022-11-11 Thread Steve Nickolas
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

2022-10-28 Thread Steve Nickolas
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)

2022-09-14 Thread Steve Nickolas
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?

2022-08-29 Thread Steve Nickolas
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?

2022-08-25 Thread Steve Nickolas
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

2022-07-29 Thread Steve Nickolas
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

2022-07-12 Thread Steve Nickolas
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

2022-07-12 Thread Steve Nickolas
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

2022-07-12 Thread Steve Nickolas
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

2022-07-12 Thread Steve Nickolas
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

2022-07-12 Thread Steve Nickolas
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

2022-07-12 Thread Steve Nickolas
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

Re: [Freedos-devel] Another implementation of GRAFTABL

2022-07-12 Thread Steve Nickolas
On Wed, 13 Jul 2022, TK Chia wrote: Hello Bret Johnson, [me:] GRAFTABL basically just needs to install a 1024-byte glyph table somewhere in conventional memory, and point the int 0x1f vector at it. (The glyph table can then be used to display "extended ASCII" characters in a CGA graphics mode

Re: [Freedos-devel] Another implementation of GRAFTABL

2022-07-12 Thread Steve Nickolas
On Wed, 13 Jul 2022, TK Chia wrote: Well, this is GRAFTABL we are discussing here, so it probably does qualify as one of the "simplest TSRs". :-) GRAFTABL basically just needs to install a 1024-byte glyph table somewhere in conventional memory, and point the int 0x1f vector at it. (The glyph ta

Re: [Freedos-devel] Another implementation of GRAFTABL

2022-07-12 Thread Steve Nickolas
On Tue, 12 Jul 2022, Ralf Quint wrote: On 7/12/2022 3:01 AM, Steve Nickolas wrote: For some reason I don't understand (me am n00b) the footprint is 144 bytes larger than the MS-DOS 5/6 version, but the binary is smaller. Most commonly, these kind of things are due to a different a

Re: [Freedos-devel] Another implementation of GRAFTABL

2022-07-12 Thread Steve Nickolas
On Tue, 12 Jul 2022, Jerome Shidel wrote: I haven’t looked at the code for either. But, there are some things in general to consider with TSRs. I would assume the memory footprint difference may be related to optimization of the executables layout and data storage. Basically, when you return

[Freedos-devel] Another implementation of GRAFTABL

2022-07-12 Thread Steve Nickolas
I've been working on this for my own project, and it's only useful for the rare CGA or Tandy users out there (which is probably why MS-DOS 6 relegated it to the Supplemental disk and PC DOS 6 removed it). GRAFTABL hooks INT1F to provide the upper half of the charset in graphics mode on a CGA o

Re: [Freedos-devel] Historical vs. Hysterical Edlin Versions

2022-05-12 Thread Steve Nickolas
On Thu, 12 May 2022, Gregory Pietsch wrote: FreeDOS Mavens, I'm thinking of editing Edlin to match historical behavior after downloading a 1982 IBM DOS manual and a 1987 Microsoft OS/2 manual I found floating around the 'Net. I want to make Edlin still the small program it has always been wi

Re: [Freedos-devel] How to work with FAT12 in FreeDOS 1.3

2022-04-23 Thread Steve Nickolas
On Sat, 23 Apr 2022, richardkolacz...@hotmail.com wrote: I cannot find a way to reformat just the D:\ partition into a FAT12 - neither via Windows, CMD or so far by FreeDOS. I was aiming for a 256 MB FAT12, but if this is not possible then a 32 MB FAT12 will do. Both of those are too big for

Re: [Freedos-devel] "FreeDOS Next" packages

2022-04-02 Thread Steve Nickolas
If you want my personal opinion, just distribute what more or less reproduces MS-DOS/PC DOS/DR DOS functionality as part of the release proper. -uso. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/li

Re: [Freedos-devel] FreeDOS virtual get-togethers in 2022

2022-02-11 Thread Steve Nickolas
On Fri, 11 Feb 2022, Jim Hall wrote: ** In January, we used Zoom as a test. For February, we're back to using BlueJeans (I use them for my training/consulting business). The BlueJeans support folks have given me a few pointers to improve performance, so I'm hoping this session will work better.

Re: [Freedos-devel] REMember a bug

2022-01-16 Thread Steve Nickolas
On Sun, 16 Jan 2022, Jim Hall wrote: I have a paper copy of a few original MS-DOS manuals. My MS-DOS 4 manual says the only separators allowed in a comment are whitespace but didn't mention redirection. But the MS-DOS 5 manual specifically says *not* to use redirection in REM. So this was a kno

Re: [Freedos-devel] is there anyway i can contribute to freedos's development with C++?

2022-01-11 Thread Steve Nickolas
On Tue, 11 Jan 2022, Tyson Oswald wrote: I found C++ at least with Watcom to not support the standards, at least current ones. I had to rollback to C as I didn’t want to get used to non-standard C++. DJGPP might be better I do not know. Well, I have a DJGPP install from some time ago and it h

Re: [Freedos-devel] Pushing source code to Github

2022-01-09 Thread Steve Nickolas
On Sun, 9 Jan 2022, Jim Hall wrote: When you edit with Pico, you're really editing with an email composer. Pico stands for the Pine Composer. Pine was an email client that replaced another email client called Elm. Pine stands for Pine Is Not Elm. And "nano" is a clone of "pico". I still use

Re: [Freedos-devel] REMember a bug

2022-01-08 Thread Steve Nickolas
On Sat, 8 Jan 2022, Jerome Shidel wrote: Hi all, As everyone knows and the docs clearly state, everything after a REM is ignored. However, I recently noticed an issue with a batch file that had something like: REM this thing [[x|4]] or later in one of its remarks. Every time the batch was ex

Re: [Freedos-devel] Wordy - a word puzzle game (sample code)

2022-01-07 Thread Steve Nickolas
On Fri, 7 Jan 2022, Jim Hall wrote: Hi everyone I wrote a quick sample game that is kind of fun, so wanted to share it. Wordy is a word puzzle game for DOS. You have six attempts to guess the mystery five-letter word. After each guess, the game highlights your letters: black if that letter doe

Re: [Freedos-devel] The FreeDOS Orphanage

2021-12-01 Thread Steve Nickolas
On Wed, 1 Dec 2021, Liam Proven wrote: Fair. For me, I left the IBM reseller that was my first job and moved to a much smaller company, so I stopped working with a mixture of PC DOS and MS-DOS and switched to mostly MS-DOS, with a little DR DOS. Meanwhile I started out with PC DOS 3.2, and mos

Re: [Freedos-devel] The FreeDOS Orphanage

2021-12-01 Thread Steve Nickolas
On Wed, 1 Dec 2021, Liam Proven wrote: On Wed, 1 Dec 2021 at 02:27, Steve Nickolas wrote: The division actually happened earlier - after 5.0. So Wikipedia said. I have not personally seen PC DOS after 4 but before 6.3, so I can't say from direct personal knowledge. I have a boxed co

Re: [Freedos-devel] The FreeDOS Orphanage

2021-11-30 Thread Steve Nickolas
On Tue, 30 Nov 2021, Liam Proven wrote: On Tue, 30 Nov 2021 at 22:35, Steve Nickolas wrote: On Tue, 30 Nov 2021, Deposite Pirate wrote: PC-DOS is also strictly better than MS-DOS. Don't know of a valid reason for anyone to bother with the latter anymore. For the most part, PC DOS *i

Re: [Freedos-devel] The FreeDOS Orphanage

2021-11-30 Thread Steve Nickolas
On Tue, 30 Nov 2021, Deposite Pirate wrote: On Tue, 30 Nov 2021 16:31:00 +0100 Liam Proven wrote: Lest anyone accuse me of spamming: this isn't mine; I make nothing from it; I do not work for IBM or any part of it. I'm just sharing info. PC-DOS is also strictly better than MS-DOS. Don't kno

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

2021-10-06 Thread Steve Nickolas
On Wed, 6 Oct 2021, tom ehlert wrote: users will have FAR more than 60 GB disk size and you can have only 24 drive letters from C: to Z: Up to 32 under some DOS/Windows versions: https://en.wikipedia.org/wiki/Drive_letter_assignment#Common_assignments while technically true, it just doesn

[Freedos-devel] The "choice.asm" I was talking about on the FD chat

2021-09-19 Thread Steve Nickolas
I did this a couple weeks ago but didn't think it was important enough to mention, plus it's not actually an improvement over the current version. I was talking about how I had just entered the world of 8088 ASM coding, and had been thinking about creating minimalist versions of DOS utilities.

Re: [Freedos-devel] List of blocking issues for FreeDOS 1.3

2021-08-28 Thread Steve Nickolas
On Sat, 28 Aug 2021, thraex wrote: Finally, I would like to ask a question: if memory serves me well, there was an automatic network detection in FreeDOS 1.2 in VirtualBox. A message beginning with "Good new everyone" announced it. Would it be possible to keep that feature for FreeDOS 1.3? II

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for Fr eeDOS 1.3]

2021-08-10 Thread Steve Nickolas
On Tue, 10 Aug 2021, Bret Johnson wrote: The problem with this approach is something like Belgium. Somebody correct me if I'm wrong, but Belgium does not have its own language -- some parts of the country are French and other parts are German. There is a Belgian country code and a Belgian ke

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Steve Nickolas
On Sun, 8 Aug 2021, Volkert via Freedos-devel wrote: As you can see in his existing repositories on GitHub ( https://github.com/sudleyplace ), Bob seems partial to the GPLv3, so I guess that would be acceptable to FreeDOS, right? 🙂 My understanding is GPL3 is fine. Anyway, I opened an issue

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

2021-08-08 Thread Steve Nickolas
On Sun, 8 Aug 2021, Volkert via Freedos-devel wrote: It turns out that writing another EMM386 reimplementation from scratch might not be necessary after all. Do you remember this thread from 2012? I see you participated in it as well: https://sourceforge.net/p/freedos/mailman/freedos-devel/thr

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

2021-08-06 Thread Steve Nickolas
On Fri, 6 Aug 2021, tom ehlert wrote: Hi Robert, attaches the german resources to fdisk.exe, and makes german the default language for fdisk.exe. Minor note: AFAIK, correct spelling of "german" in English is "German" with a capital "G". Same for all other language "names". really? Like in

Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3?

2021-07-29 Thread Steve Nickolas
On Thu, 29 Jul 2021, thraex wrote: There's a saying in French, something like "The best is the enemy of good". As "Perfect is the enemy of good enough", it is almost a mantra in my circles. -uso. ___ Freedos-devel mailing list Freedos-devel@list

Re: [Freedos-devel] video FreeDOS running Windows 3.1

2021-07-24 Thread Steve Nickolas
Followup to my last comment, since I actually went and checked. On Sat, 24 Jul 2021, Steve Nickolas wrote: For what it's worth, Windows 3.x comes with its own versions of HIMEM and SMARTDRV. I *think* it also comes with EMM386, but I'm not so sure about that one. Have to chec

Re: [Freedos-devel] video FreeDOS running Windows 3.1

2021-07-24 Thread Steve Nickolas
On Sat, 24 Jul 2021, Eric Auer wrote: I see you are using the Microsoft HIMEM 3.07 (02/14/92), Microsoft EMM386 4.44 (1991) and Microsoft SMARTDRV, are all of those actually necessary? I would expect things to also work with HIMEMX or XMGR, as long as no free EMM386 is loaded at all? Why do you

Re: [Freedos-devel] Pacific C Shareware version at ibiblio

2021-07-02 Thread Steve Nickolas
On Fri, 2 Jul 2021, tom ehlert wrote: Not sure if anyone will be concerned but just found that ibiblio (https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/c/pacific/) is mirroring the shareware version of Pacific C (circa 1998), while during 2000 they release the same version as fr

Re: [Freedos-devel] Additional notes on Games

2021-06-16 Thread Steve Nickolas
On Thu, 17 Jun 2021, Eric Auer wrote: If you really worry about people getting confused by GNUCHESS, but really refuse to load NANSI by default, you could simply provide a batch file to first load NANSI, then GNUCHESS and bundle that batch file with GNUCHESS. You can even make that batch file

Re: [Freedos-devel] Additional notes on Games

2021-06-16 Thread Steve Nickolas
Here's the problem, as I see it. A lot of people misuse the terms "open source" and "public domain". They say "open source" when they mean source-available (it may not be open, if it is not as I describe "freedom-compliant"), and they say "public domain" when they mean freeware. When I say

Re: [Freedos-devel] FreeDOS 1.3 packages

2021-06-07 Thread Steve Nickolas
On Tue, 8 Jun 2021, Deposite Pirate wrote: June 8, 2021 4:46 AM, "Eric Auer" wrote: check? * Maybe not even both FREEDOOM and BOOM at the same time Freedoom is a free Doom compatible WAD and boom is a doom engine source port. You always need Freedoom along with a doom engine to have a full D

  1   2   3   4   >