On Mon, Jan 3, 2022 at 6:46 PM richardkolacz...@hotmail.com <
richardkolacz...@hotmail.com> wrote:
> Jim
>
> Fair enough NOT to have "additional buttons" on the first web page.
>
> It would be nice (for me) to identify by a -mmm-dd text as to the
> update status of the development build, so fo
Jim
Fair enough NOT to have "additional buttons" on the first web page.
It would be nice (for me) to identify by a -mmm-dd text as to the update
status of the development build, so for example :-
With the (pink) Download FreeDOS button - the button also has the text in
smaller print, "Last
On Mon, Jan 3, 2022 at 5:58 PM richardkolacz...@hotmail.com <
richardkolacz...@hotmail.com> wrote:
> Suggestion...
>
> On the first website page, have
>
> Download Stable build 1.2 (created -mmm-dd)
> Download Development build RC5 (last updated -mmm-dd)
>
> buttons
>
> I personally use th
Suggestion...
On the first website page, have
Download Stable build 1.2 (created -mmm-dd)
Download Development build RC5 (last updated -mmm-dd)
buttons
I personally use the date format -mmm-dd, for example 2022-Mar-02, to avoid
confusion with having a two-digit month value.
To me,
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
there are three different keyboard drivers that all work in FDOS. keyb supports tr and tr440 (assume this is tr2), mkeyb does not support turkish at all and xkeyb supports tr only. it is your choice which of the three keyboard you want to use in your environment. --Diese Nachricht wurde von me
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
Hello Jerome,
> 2 янв. 2022 г., в 23:32, Jerome Shidel написал(а):
>
> Hi Emir,
>
> Since I haven’t got around to making a doc for creating the V8F font files,
> here is the easiest way…
> Anyhow, it’s not hard to do. :-)
>
> Let me know if you run into any problems or have any questions.
Hello,
If I understand this right, this is about moving the Turkish layouts from KEYB2
to the main driver, right? Would this cause any compatibility issues with other
programs?
Anyway, I will be happy to provide any assistance needed whilst testing the F
layout.
Best,
Emir
Отправлено с iPhon
Hi everyone
I wanted to share that I'm still working on an update to the FreeDOS
website. I shared in an email to the list some time ago the issues
with the current website, but the short version is certain parts of
www.freedos.org are hard to navigate, and it's not very easy for folks
who are new
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
On 3.01.2022 17:18, tom ehlert wrote:
Hi,
>> But I still think about adding turkish layouts in mkeyb.
> why? obviously thraex has had a turkish keyboard driver
> for the last 30 years. what is the problem ou are trying to solve?
>
> and thraex hasn't complained himself, so it's not up to you t
in doubt both tr versions. I will talk with thraex and others about this theme.Why I?vecho is tricky, so I had to run tests with turkish files and with turkish keyboard layouts. e.g. they use two different i characters, i found only one on my keyboard, but this is only one problem. i used mkey
> But I still think about adding turkish layouts in mkeyb.
why? obviously thraex has had a turkish keyboard driver
for the last 30 years. what is the problem ou are trying to solve?
and thraex hasn't complained himself, so it's not up to you to
complain.
> It would make much things easier.
what
Hi Ralf,
you are right. I checked it, all three keyboard layouts have the same basic system, so even if it would work it would require to modify all three keyboard programs.
That is nonse. I admit this hereby officially. Sorry Tom, I have to excuse myself!
Nevertheless it is weird that two di
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
If you run Windows install imdisk. This supports a lot of virtual machines, even the diskette versions used by FD and is simple to handle via context menu (Explorer, right mouse click, mount / unmount) - and in some cases it also supports r/w (read-write). Of course vhd is supported by Windows vers
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
20 matches
Mail list logo