Hallo Herr Jim Hall,
>> >> How (also when) will this patch (and other patches) make it into the
>> >> official freecom repo?
>>
>> I have no idea about if, where and when.
>>
>> Maybe ask the project coordinator?
>>
> We'll get it in there.
>> >> The kernel is *the* core component of an OS. Th
On Mon, Jan 3, 2022 at 2:57 PM Robert Riebisch wrote:
>[..]
> For me (!) it doesn't matter, if it's on GitLab or GitHub (or even
> Codeberg.org), as long as I know, how to find it. My primary source for
> such information would be the freedos.org site.
>
I just checked the FreeDOS website and ht
Hi Jim,
> I think we should merge the kernel back into the new FreeDOS GitLab
> repo, now that we have one. But that's a separate discussion I'll
> start with Perdition.
For me (!) it doesn't matter, if it's on GitLab or GitHub (or even
Codeberg.org), as long as I know, how to find it. My primary
Hi,
> On Jan 3, 2022, at 1:35 PM, Jim Hall wrote:
> [..]
> That's a cynical and disingenuous statement. Development happens all
> over, and some folks prefer using different tools. Perdition set up
> his kernel repo in GitHub because that was his tool. And he did that
> before we set up the GitLa
On Sun, Jan 2, 2022 at 3:13 PM tom ehlert wrote:
>
>
> >> How (also when) will this patch (and other patches) make it into the
> >> official freecom repo?
>
> I have no idea about if, where and when.
>
> Maybe ask the project coordinator?
>
We'll get it in there.
> >> The kernel is *the* core c
If you want to put stuff into or take stuff out of a Virtual Machine hard
drive, you should stick with a Flat Fixed Size VMDK. That is one that is not
split into pieces and is pre-allocated to the entire size. You end up with two
files for the Virtual Machines hard drive. One is a descriptor/con
>> however I'm not able to extract files out of cut.vhd. is it a raw image?
> It's usually a Windows VirtualPC or Hyper-V hard disk file: *V*irtual
> *H*ard *D*isk.
thank you very much;)
> Attach it to an existing VM with an OS that can read multiple disk
> formats -- i.e. Linux.
I asked bec
versions (I think except home edition) itself.
https://sourceforge.net/projects/imdisk-toolkit/
Willi
Sent: Monday, January 03, 2022 at 1:09 PM
From: "Liam Proven"
To: "Technical discussion and questions for FreeDOS developers."
Subject: Re: [Freedos-devel] dir /od
On Sun, 2 Jan 2022 at 10:58, tom ehlert wrote:
> however I'm not able to extract files out of cut.vhd. is it a raw image?
It's usually a Windows VirtualPC or Hyper-V hard disk file: *V*irtual
*H*ard *D*isk.
Attach it to an existing VM with an OS that can read multiple disk
formats -- i.e. Linux
>> How (also when) will this patch (and other patches) make it into the
>> official freecom repo?
I have no idea about if, where and when.
Maybe ask the project coordinator?
>> (I'm still confused by all the different private, public, official,
>> semi-official repos. So no offense. I'm just c
Hi all,
> How (also when) will this patch (and other patches) make it into the
> official freecom repo?
> (I'm still confused by all the different private, public, official,
> semi-official repos. So no offense. I'm just curious.)
>
> https://gitlab.com/FreeDOS/base/kernel#still-actively-develope
Hi Tom,
> I reproduced the bug.
>
> I fixed the bug.
>
> in CMD\DIR.C, line 972+ change
>
> static int orderFunction(const void *p1, const void *p2)
> {
> ...
> case ORDER_BY_NAME:
> rv = strcmp(f1.ff_name,f2.ff_name);
> break;
> }
>
Hallo Herr tom ehlert,
am Sonntag, 2. Januar 2022 um 10:57 schrieben Sie:
> Hi Paul,
>>> Here is the result of one "dir /od" that I did with
>>> Freedos 1.5 RC5. As you can see, it didn't get
>>> into sorted order.
>> Apologies for the typo, should have been 1.3.
>> Anyway, I do not have DIRCM
Hi Paul,
>> Here is the result of one "dir /od" that I did with
>> Freedos 1.5 RC5. As you can see, it didn't get
>> into sorted order.
> Apologies for the typo, should have been 1.3.
> Anyway, I do not have DIRCMD set, and I have produced
> the image I am using so that the result can be reprodu
Here is the result of one "dir /od" that I did with
Freedos 1.5 RC5. As you can see, it didn't get
into sorted order.
Apologies for the typo, should have been 1.3.
Anyway, I do not have DIRCMD set, and I have produced
the image I am using so that the result can be reproduced.
http://pdos.org/t
On Wed, Dec 29, 2021 at 2:03 PM Jim Hall wrote:
[SNIP]
> But don't forget that FreeDOS 1.3 RC5 also sets a DIRCMD environment
> variable, so you need to consider that too:
>
> C:\>echo %DIRCMD%
> /P /O:GN /Y
>
About this...this default %DIRCMD% "slowed" me down while I've been playing
with FD 1.
> On 12/29/2021 1:58 AM, Paul Edwards wrote:
> > Here is the result of one "dir /od" that I did with
> > Freedos 1.5 RC5. As you can see, it didn't get
> > into sorted order.
> >
> > BFN. Paul.
On Wed, Dec 29, 2021 at 11:43 AM Ralf Quint wrote:
> I just tried this and can NOT confirm this (Virtu
On 12/29/2021 1:58 AM, Paul Edwards wrote:
Here is the result of one "dir /od" that I did with
Freedos 1.5 RC5. As you can see, it didn't get
into sorted order.
BFN. Paul.
I just tried this and can NOT confirm this (Virtual Box of 1.5RC5)...
It just sorts all folders and files in the proper
Here is the result of one "dir /od" that I did with
Freedos 1.5 RC5. As you can see, it didn't get
into sorted order.
BFN. Paul.
Volume in drive C is FREEDOS
Volume Serial Number is 2E4E-17F3
Directory of C:\DEVEL\PDOS\SRC
INSTMBR C 5,613 12-28-21 9:21p
SUPPORT OBJ 8
19 matches
Mail list logo
