Re: [Freedos-devel] Status of NightDOS kernel?

2022-01-16 Thread Mercury Thirteen via Freedos-devel
"Officially" Night is in fact still an ongoing project. The problem is that I haven't had much time to devote to it for a while now, and I know Maarten and Antony have a lot going on as well. After completing a handful of other projects that have popped up, I will definitely be going back to

[Freedos-devel] Status of NightDOS kernel?

2022-01-16 Thread Jim Hall
Does anyone know the current status of the NightDOS kernel effort? This is (was?) a project to create a 32-bit drop-in replacement for the FreeDOS kernel. Mercury was a key developer on this. But the "official dev thread" discussion on Google Groups seems to have stalled out in 2020, although

Re: [Freedos-devel] Contemplations, Considerations and some Conclusions

2022-01-16 Thread Mercury Thirteen via Freedos-devel
On Sunday, January 16th, 2022 at 3:34 PM, Jim Hall wrote: > ... > I run Linux, and use Fedora on my PC. When I download a new version of > [Fedora Workstation](https://getfedora.org/en/workstation/download/), it > comes as a DVD ISO image. But my PC doesn't have a DVD drive (my previous >

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

Re: [Freedos-devel] REMember a bug

2022-01-16 Thread Jim Hall
On Sun, Jan 9, 2022 at 1:19 PM tom ehlert wrote: > > > > 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

Re: [Freedos-devel] Contemplations, Considerations and some Conclusions

2022-01-16 Thread Jim Hall
On Sat, Jan 15, 2022 at 6:33 AM Jerome Shidel wrote: > [..] > We come to UEFI and modern hardware. With modern hardware vendors dropping > support for Legacy BIOS and users wanting to run FreeDOS on modern > machines, I only see three solutions. > > First… Oh well, they can run it in a virtual

Re: [Freedos-devel] Contemplations, Considerations and some Conclusions

2022-01-16 Thread Jim Hall
On Sat, Jan 15, 2022 at 6:33 AM Jerome Shidel wrote: > [..] > A lot of users want to run FreeDOS from USB. As I see it, there are > several issues with that. > > First, you cannot guarantee that when booted from USB that drive will be > writable. Personally, I’ve never seen when it was write

Re: [Freedos-devel] Contemplations, Considerations and some Conclusions

2022-01-16 Thread Jim Hall
On Sat, Jan 15, 2022 at 6:33 AM Jerome Shidel wrote: > Hello all, > > I’ve got a couple thoughts regarding the OS release media I wanted to > throw out to you all. These are just things I was pondering and by no means > I’m I saying any of these are going to happen. They are just some ideas I’d

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

2022-01-16 Thread Jim Hall
Thanks to everyone for joining today's FreeDOS virtual get-together! I really appreciate getting to know everyone as more than just a name behind an email. Folks dropped in and out as they had time. I think we had a dozen folks during the get-together. We do these monthly, so if you weren't able

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

2022-01-16 Thread Jim Hall
On Sun, Jan 16, 2022 at 10:46 AM Ralf Quint wrote: > On 1/12/2022 12:58 PM, Jim Hall wrote: > > I'll share the meeting info here in the hour leading up to the meeting. > > Did you oversleep? ;-) > > No, but I completely forgot to share the invite an hour before the meeting. :-) Here's the

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

2022-01-16 Thread Ralf Quint
On 1/12/2022 12:58 PM, Jim Hall wrote: I'll share the meeting info here in the hour leading up to the meeting. Did you oversleep? ;-) Ralf -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus