Re: [Freedos-devel] DO FreeDOS in the Cloud

[Jerome Shidel]

Hi all, 

Some significant improvements were made to the LiveCD Type-1 today. So, if 
you’ve been building the early 1.3 release pre-beta versions, you should pull 
the latest GitLab source and do a clean rebuild. More or less like so...

git pull
make clean translate all
make cdrom release

Or...
git pull
make clean translate cdrom all

At present, the “Normal” CD has not been chosen. So, the makefile does not 
automatically create the Standard CD or LiveCD Type-1. Only the Legacy CD is 
automatically created. Once the LiveCD Type-2 has been added, community testing 
will help determine which LiveCD type will become the Normal CD. The Types that 
are not chosen will remain available in the makefile. 

FYI, I am aware that highlighting the Russian language in FDI (the installer) 
makes the screen text look garbled and displays a couple DOS error messages. I 
just haven’t made a final decision on how to handle it. But, I probably will 
just load a temporary font and prevent the missing file errors. Probably.

Jerome


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[TK Chia]

Hello Jim,


Github pages aren't working for me at the moment, but maybe that's a
network resolution problem on my end? I'm looking for release notes or
similar that I could use to announce your  updated gcc-ia16 toolchain on
the FreeDOS website. Or should I just use the notes you included here:

Besides fixing the package descriptions to make them fit onto single
lines, I have also included in the packages some compiler optimizations
and other minor features that I recently implemented.


I think these notes will be fine, as I feel the changes I made (since my 
earlier release announcement in October) were indeed quite minor.


However, in case they are needed, I have also uploaded a second copy of 
the release notes _and_ package files to my GitLab account, here: 
https://gitlab.com/tkchia/build-ia16/tags/20190101 .


Thank you!

--
https://github.com/tkchia


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

> On Jan 2, 2019, at 4:05 PM, stecdose  wrote:
> 
> 
>>> * If the installation language is Russian, the text is garbled, no
>>> Cyrillic letters are displayed.
>> Yeah, that’s a known issue. Cant really think of a “good” way to solve it.
>> 
>> Here’s the problem.
>> 
>> Language and translation change when that language is highlighted on the 
>> menu. However, the Language settings, Codepage and font are not set until 
>> that language is actually selected.
>> This requires loading some TSRs. They may be a way to unload them. But, I 
>> don’t know if or what it is.
>> 
>> I have a bunch of stuff I’ve written over the years that can load fonts. 
>> Most recently are the QFONT tools included with PGME. They can convert 
>> to/from simple bit fonts, load qfonts temporarily, or turn them into a TSR. 
>> I may do something there to temp load/unload the Russian font on the menu.
> 
> Maybe storing the codepage and font information are stored along with the 
> langua/keyboard layout is good.
> 
> This way a small utility ("loadfont") can be called when changing language. 
> This would be good for all languages that have special letters.

Not a bad idea. But, not necessary. FDI is already designed to run a language 
specific SETLANG.BAT that has any settings and programs needed for a selected 
language. 

The issue is switching temporarily to highly different possibilities prior to 
selection. More specifically, unloading settings made from the previous 
highlight. 

Mostly,it is not an issue for most of the languages supported by FDI. However, 
Russian requires it.

So, each time you scroll onto and off of the language, you would end up loading 
one codepage on top of another, and another and another.

As a native English speaker, I really never had to mess around with those. 
There may be a way to unload one. But I am unaware of it. I don’t have the time 
or desire to RTFM it. 

It would just be quicker and easier to just extract the required fonts from 
their codepage, convert to my QFONT format, and use my loader to temporary load 
any font using no TSR or memory. 

That solution has one drawback, either limit fonts to only EGA or VGA sizes... 
Or, provide two sets for each language and detect/select the appropriate one.

> 
>> 
>> I still need to do some more work in FDI to be able to handle installation 
>> from LiveCD-Type2.
>> 
>> LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and 
>> Community to decide which will be the LiveCD.
>> 
> Looking forward to it :)
> 

:-)

> 
> Nils
> 

Jerome


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[stecdose]

* If the installation language is Russian, the text is garbled, no
Cyrillic letters are displayed.

Yeah, that’s a known issue. Cant really think of a “good” way to solve it.

Here’s the problem.

Language and translation change when that language is highlighted on the menu. 
However, the Language settings, Codepage and font are not set until that 
language is actually selected.
This requires loading some TSRs. They may be a way to unload them. But, I don’t 
know if or what it is.

I have a bunch of stuff I’ve written over the years that can load fonts. Most 
recently are the QFONT tools included with PGME. They can convert to/from 
simple bit fonts, load qfonts temporarily, or turn them into a TSR. I may do 
something there to temp load/unload the Russian font on the menu.


Maybe storing the codepage and font information are stored along with 
the langua/keyboard layout is good.


This way a small utility ("loadfont") can be called when changing 
language. This would be good for all languages that have special letters.




I still need to do some more work in FDI to be able to handle installation from 
LiveCD-Type2.

LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and Community 
to decide which will be the LiveCD.


Looking forward to it :)


Nils



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi,

> On Jan 2, 2019, at 12:38 PM, thraex  wrote:
> 
> 
> 2.01.2019 02:30 tarihinde Jerome Shidel yazdı:
>> 
>> Sorry, I didn’t notice. Displaying the found translations is a new feature 
>> in the build environment. I know there are a couple missin from the German 
>> translations. So, I figured it might be nice that you were shown during that 
>> phase.
> 
> Good idea indeed, thank you. I noticed that XDEL had neither French
> nor Turkish translations and that FDIMPLES was machine translated in
> these two languages therefore I added these translations to the archive
> containing CuteMouse files, so forget about the previous link, just
> download them all from
> .

Will do

> 
>>> I managed to build it locally with Fedora 28 in VirtualBox thanks to
>>> your video. That said, I noticed several problems, just to bring them to
>>> your attention:
>> 
>> Neat eh? Super easy to build one. :-)
> 
> :-)
> 
>>> * When I choose Turkish in the installer, some letters are changed, for
>>> instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
>>> still legible and understandable though.
>> 
>> I think that may be my fault. The I’ve been unable to figure out what DOS 
>> character set is correct in BBEdit. So, it refuses to save them unless I 
>> change them. I had to do a bunch of adjustments to frame sizes and line 
>> breaks for all of the translations so they displayed properly.
>> 
>> If you fix them in the versions that are in the source tree, I can update 
>> them so they aren’t mangled. Just avoid any changes that would require me 
>> needing to adjust them.
> 
> The problem is worse than I thought: even after the installation the
> charset problem remains, and it also affects characters like İ. Let's
> see what we can do when you get back on FreeDOS 1.3.

Hmmm. 

> And just so that I don't forget it, when the chosen keyboard in the
> installer is the French layout, I get the Spanish one (I think) instead.
> I have to type mkeyb fr after the installation to get the correct AZERTY
> layout.

It could be a minor bug in FDI or build process that may have occurred when I 
incorporated the Russian translations. 

> 
>>> * A ver command returns the following:
>>> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
>>> whereas FreeCOM 0.84-pre6 has been released in September (see
>>> ). Wouldn't it make sense to
>>> use this more recent version?
>>> 
>>> That's all for now, as I couldn't install FreeDOS 1.3 Beta. Hopefully
>>> when I'm able to install I'll have more stuff to bother you with. :-P
>> 
>> If you would like a pleasant surprise... run
>> make cdrom release
>> :-)
> 
> Hey that's a neat FreeDOS 1.3 Beta LiveCD! :) If anyone wants to play
> with it, it can be downloaded from .
> The corresponding md5 sum is "177a9f511a664a5a51d2d749b0f753bf" and the
> sha256 sum is
> "f0d2ef4d00ce24049ef60107326071061701db0bea1b1a284901817c5969afd4". It
> installs just fine in AQEMU

There are a couple final touches I need to make to LiveCD-Type 1 and was going 
to wait until both Type1 & 2 were ready before having everyone play around with 
them. But, it’s ok. Everyone is welcome to start playing with LiveCD Type-1. 

Using the LiveCD part requires 128mb ram at present.

Also, There are a couple known bugs and unresolved issues at preset. This is 
early beta. 

Live portion will get installer eventually and probably automatic networking 
support under VirtualBox and VMware.

One main issue is under VirtualBox, the installer will complain about not being 
supported and drop out. Easy fix when I get to it. But, for now, after that 
happens, just relaunch it manually with setup.bat

Jerome


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[thraex]

2.01.2019 02:30 tarihinde Jerome Shidel yazdı:
> 
> Sorry, I didn’t notice. Displaying the found translations is a new feature in 
> the build environment. I know there are a couple missin from the German 
> translations. So, I figured it might be nice that you were shown during that 
> phase.

Good idea indeed, thank you. I noticed that XDEL had neither French
nor Turkish translations and that FDIMPLES was machine translated in
these two languages therefore I added these translations to the archive
containing CuteMouse files, so forget about the previous link, just
download them all from
.

>> I managed to build it locally with Fedora 28 in VirtualBox thanks to
>> your video. That said, I noticed several problems, just to bring them to
>> your attention:
> 
> Neat eh? Super easy to build one. :-)

:-)

>> * When I choose Turkish in the installer, some letters are changed, for
>> instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
>> still legible and understandable though.
> 
> I think that may be my fault. The I’ve been unable to figure out what DOS 
> character set is correct in BBEdit. So, it refuses to save them unless I 
> change them. I had to do a bunch of adjustments to frame sizes and line 
> breaks for all of the translations so they displayed properly.
> 
> If you fix them in the versions that are in the source tree, I can update 
> them so they aren’t mangled. Just avoid any changes that would require me 
> needing to adjust them.

The problem is worse than I thought: even after the installation the
charset problem remains, and it also affects characters like İ. Let's
see what we can do when you get back on FreeDOS 1.3.

And just so that I don't forget it, when the chosen keyboard in the
installer is the French layout, I get the Spanish one (I think) instead.
I have to type mkeyb fr after the installation to get the correct AZERTY
layout.

>> * A ver command returns the following:
>> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
>> whereas FreeCOM 0.84-pre6 has been released in September (see
>> ). Wouldn't it make sense to
>> use this more recent version?
>>
>> That's all for now, as I couldn't install FreeDOS 1.3 Beta. Hopefully
>> when I'm able to install I'll have more stuff to bother you with. :-P
> 
> If you would like a pleasant surprise... run
> make cdrom release
> :-)

Hey that's a neat FreeDOS 1.3 Beta LiveCD! :) If anyone wants to play
with it, it can be downloaded from .
The corresponding md5 sum is "177a9f511a664a5a51d2d749b0f753bf" and the
sha256 sum is
"f0d2ef4d00ce24049ef60107326071061701db0bea1b1a284901817c5969afd4". It
installs just fine in AQEMU (but not in VirtualBox).


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jim Hall]

Hi

Github pages aren't working for me at the moment, but maybe that's a
network resolution problem on my end? I'm looking for release notes or
similar that I could use to announce your  updated gcc-ia16 toolchain on
the FreeDOS website. Or should I just use the notes you included here:

On Tue, Jan 1, 2019 at 7:08 AM TK Chia  wrote:

> Hello all,
>
> >> On my end, I have tweaked my gcc-ia16 toolchain build files, to avoid
> multi-line descriptions in the .lsm's for now.  I guess though that it is a
> bit late into the FreeDOS 1.3 release schedule to have this change
> included...
> > The 1.3 release is a little behind schedule and RC1 hasn’t shipped yet.
> Once it does, from that point on, only bug fixes for the release will be
> made. So, you update may make it into 1.3. After all, it’s a (not really)
> “bug fix” and not a new package.
>
> Thank you!  I have uploaded new packages for the gcc-ia16 toolchain, at
> https://github.com/tkchia/build-ia16/releases/tag/20190101 .
>
> Besides fixing the package descriptions to make them fit onto single
> lines, I have also included in the packages some compiler optimizations
> and other minor features that I recently implemented.
>
> I look forward to trying out the FreeDOS 1.3rc1 distribution.
>
> Thank you!
>
> --
> https://github.com/tkchia
>
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

> On Jan 1, 2019, at 6:30 PM, Jerome Shidel  wrote:
> 
> 
> 
>> On Jan 1, 2019, at 1:31 PM, thraex  wrote:
>> 
>> 
>> 
>> 29.12.2018 18:18 tarihinde Jerome Shidel yazdı:
>> 
>> 
 Finally, if there is other stuff that can be translated for FreeDOS,
 feel free to yell at me.
>>> 
>>> :-)
>> 
>> Well, you should have yelled :-P Looking at all this scrolling text, I
>> noticed that CuteMouse wasn't translated in Turkish (it wasn't listed on
>>  so I missed it). You can grab the archive
>> containing the Turkish and French translations (there's only a couple of
>> typo fixes for the file in French) from
>> . The
>> encoding and line endings should be correct. If there are other such
>> packages, I would happily translate them too. Just give me some pointers.
> 
> Sorry, I didn’t notice. Displaying the found translations is a new feature in 
> the build environment. I know there are a couple missin from the German 
> translations. So, I figured it might be nice that you were shown during that 
> phase.
> 
>> 
>>> Generally, I build it locally in VirtualBox using openSUSE Leap. I
>>> quickly go over the process on the builder wiki
>>> https://gitlab.com/FreeDOS/builder/wikis/home at gitlab. But other than
>>> initial creation of the VM, it is exactly the 
>>> same as building it on the cloud. 
>> 
>> I managed to build it locally with Fedora 28 in VirtualBox thanks to
>> your video. That said, I noticed several problems, just to bring them to
>> your attention:
> 
> Neat eh? Super easy to build one. :-)
> 
>> * If the installation language is Russian, the text is garbled, no
>> Cyrillic letters are displayed.
> 
> Yeah, that’s a known issue. Cant really think of a “good” way to solve it.
> 
> Here’s the problem.
> 
> Language and translation change when that language is highlighted on the 
> menu. However, the Language settings, Codepage and font are not set until 
> that language is actually selected. 
> This requires loading some TSRs. They may be a way to unload them. But, I 
> don’t know if or what it is.
> 
> I have a bunch of stuff I’ve written over the years that can load fonts. Most 
> recently are the QFONT tools included with PGME. They can convert to/from 
> simple bit fonts, load qfonts temporarily, or turn them into a TSR. I may do 
> something there to temp load/unload the Russian font on the menu.
> 
> I still need to do some more work in FDI to be able to handle installation 
> from LiveCD-Type2. 
> 
> LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and 
> Community to decide which will be the LiveCD. 
> 
>> * When I choose Turkish in the installer, some letters are changed, for
>> instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
>> still legible and understandable though.
> 
> I think that may be my fault. The I’ve been unable to figure out what DOS 
> character set is correct in BBEdit. So, it refuses to save them unless I 
> change them. I had to do a bunch of adjustments to frame sizes and line 
> breaks for all of the translations so they displayed properly.
> 
> If you fix them in the versions that are in the source tree, I can update 
> them so they aren’t mangled. Just avoid any changes that would require me 
> needing to adjust them.
> 
>> * It wasn't possible to install FD13LGCY.ISO in VirtualBox which said
>> "Unfortunately, this method of installation is not supported on this
>> hardware platform. Please try a different installation method".
> 
> Yes, this was an issue on 1.2 as well. VirtualBox really doesn’t seem to like 
> booting FreeDOS using the original/classic el torito specification.
> So, the installer checks to see if it is on VB on that media and drops out. 
> It could then be rerun manually. But, it will fail. 

Correction.

It may be the other way around. It’s been two years. I forget which was which.

> 
>> It
>> seemed to work with AQEMU though until the "Gathering some information
>> to prepare for the installation..." step. Then I got "Unable to locate
>> the installation packages. A reboot may help" and it becomes a loop.
> 
> Not really much of a qemu user. I’ll have to investigate.
> 
>> The
>> same is also true for FD13FLOP.IMG with VirtualBox.
> 
> Hmmm, should work. I have tested the actual install for a little while. I may 
> have broken something.
> 

Yeah, I broke the installer. Well, technically, I forgot about something the 
installer checked in 1.2. That file is not present on 1.3. So, took about 10 
seconds to fix.

If you run “make fresh fdi”, it will clear out most of the cached info (keeping 
settings, translated packages and repo cdrom iso) and update the FDI sources.

Then you can run make again to rebuild the with that issue fixed. The others 
will have to wait a few days. Kinda busy at the moment. 

>> 
>> * A ver command returns the following:
>> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
>> 

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

> On Jan 1, 2019, at 1:31 PM, thraex  wrote:
> 
> 
> 
> 29.12.2018 18:18 tarihinde Jerome Shidel yazdı:
> 
> 
>>> Finally, if there is other stuff that can be translated for FreeDOS,
>>> feel free to yell at me.
>> 
>> :-)
> 
> Well, you should have yelled :-P Looking at all this scrolling text, I
> noticed that CuteMouse wasn't translated in Turkish (it wasn't listed on
>  so I missed it). You can grab the archive
> containing the Turkish and French translations (there's only a couple of
> typo fixes for the file in French) from
> . The
> encoding and line endings should be correct. If there are other such
> packages, I would happily translate them too. Just give me some pointers.

Sorry, I didn’t notice. Displaying the found translations is a new feature in 
the build environment. I know there are a couple missin from the German 
translations. So, I figured it might be nice that you were shown during that 
phase.

> 
>> Generally, I build it locally in VirtualBox using openSUSE Leap. I
>> quickly go over the process on the builder wiki
>>  https://gitlab.com/FreeDOS/builder/wikis/home at gitlab. But other than
>> initial creation of the VM, it is exactly the 
>> same as building it on the cloud. 
> 
> I managed to build it locally with Fedora 28 in VirtualBox thanks to
> your video. That said, I noticed several problems, just to bring them to
> your attention:

Neat eh? Super easy to build one. :-)

> * If the installation language is Russian, the text is garbled, no
> Cyrillic letters are displayed.

Yeah, that’s a known issue. Cant really think of a “good” way to solve it.

Here’s the problem.

Language and translation change when that language is highlighted on the menu. 
However, the Language settings, Codepage and font are not set until that 
language is actually selected. 
This requires loading some TSRs. They may be a way to unload them. But, I don’t 
know if or what it is.

I have a bunch of stuff I’ve written over the years that can load fonts. Most 
recently are the QFONT tools included with PGME. They can convert to/from 
simple bit fonts, load qfonts temporarily, or turn them into a TSR. I may do 
something there to temp load/unload the Russian font on the menu.

I still need to do some more work in FDI to be able to handle installation from 
LiveCD-Type2. 

LiveCD-Type1 is mostly ready. My plan is to put both to the Devs and Community 
to decide which will be the LiveCD. 

> * When I choose Turkish in the installer, some letters are changed, for
> instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
> still legible and understandable though.

I think that may be my fault. The I’ve been unable to figure out what DOS 
character set is correct in BBEdit. So, it refuses to save them unless I change 
them. I had to do a bunch of adjustments to frame sizes and line breaks for all 
of the translations so they displayed properly.

If you fix them in the versions that are in the source tree, I can update them 
so they aren’t mangled. Just avoid any changes that would require me needing to 
adjust them.

> * It wasn't possible to install FD13LGCY.ISO in VirtualBox which said
> "Unfortunately, this method of installation is not supported on this
> hardware platform. Please try a different installation method".

Yes, this was an issue on 1.2 as well. VirtualBox really doesn’t seem to like 
booting FreeDOS using the original/classic el torito specification.
So, the installer checks to see if it is on VB on that media and drops out. It 
could then be rerun manually. But, it will fail. 

> It
> seemed to work with AQEMU though until the "Gathering some information
> to prepare for the installation..." step. Then I got "Unable to locate
> the installation packages. A reboot may help" and it becomes a loop.

Not really much of a qemu user. I’ll have to investigate.

> The
> same is also true for FD13FLOP.IMG with VirtualBox.

Hmmm, should work. I have tested the actual install for a little while. I may 
have broken something.

> 
> * A ver command returns the following:
> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
> whereas FreeCOM 0.84-pre6 has been released in September (see
> ). Wouldn't it make sense to
> use this more recent version?
> 
> That's all for now, as I couldn't install FreeDOS 1.3 Beta. Hopefully
> when I'm able to install I'll have more stuff to bother you with. :-P

If you would like a pleasant surprise... run
make cdrom release
:-)

> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[thraex]

29.12.2018 18:18 tarihinde Jerome Shidel yazdı:


>> Finally, if there is other stuff that can be translated for FreeDOS,
>> feel free to yell at me.
> 
> :-)

Well, you should have yelled :-P Looking at all this scrolling text, I
noticed that CuteMouse wasn't translated in Turkish (it wasn't listed on
 so I missed it). You can grab the archive
containing the Turkish and French translations (there's only a couple of
typo fixes for the file in French) from
. The
encoding and line endings should be correct. If there are other such
packages, I would happily translate them too. Just give me some pointers.

> Generally, I build it locally in VirtualBox using openSUSE Leap. I
> quickly go over the process on the builder wiki
>  https://gitlab.com/FreeDOS/builder/wikis/home at gitlab. But other than
> initial creation of the VM, it is exactly the 
> same as building it on the cloud. 

I managed to build it locally with Fedora 28 in VirtualBox thanks to
your video. That said, I noticed several problems, just to bring them to
your attention:

* If the installation language is Russian, the text is garbled, no
Cyrillic letters are displayed.

* When I choose Turkish in the installer, some letters are changed, for
instance ı becomes an i, ğ becomes a g, ş becomes an s. The text is
still legible and understandable though.

* It wasn't possible to install FD13LGCY.ISO in VirtualBox which said
"Unfortunately, this method of installation is not supported on this
hardware platform. Please try a different installation method". It
seemed to work with AQEMU though until the "Gathering some information
to prepare for the installation..." step. Then I got "Unable to locate
the installation packages. A reboot may help" and it becomes a loop. The
same is also true for FD13FLOP.IMG with VirtualBox.

* A ver command returns the following:
FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
whereas FreeCOM 0.84-pre6 has been released in September (see
). Wouldn't it make sense to
use this more recent version?

That's all for now, as I couldn't install FreeDOS 1.3 Beta. Hopefully
when I'm able to install I'll have more stuff to bother you with. :-P


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[TK Chia]

Hello all,


On my end, I have tweaked my gcc-ia16 toolchain build files, to avoid 
multi-line descriptions in the .lsm's for now.  I guess though that it is a bit 
late into the FreeDOS 1.3 release schedule to have this change included...

The 1.3 release is a little behind schedule and RC1 hasn’t shipped yet. Once it 
does, from that point on, only bug fixes for the release will be made. So, you 
update may make it into 1.3. After all, it’s a (not really) “bug fix” and not a 
new package.


Thank you!  I have uploaded new packages for the gcc-ia16 toolchain, at 
https://github.com/tkchia/build-ia16/releases/tag/20190101 .


Besides fixing the package descriptions to make them fit onto single 
lines, I have also included in the packages some compiler optimizations 
and other minor features that I recently implemented.


I look forward to trying out the FreeDOS 1.3rc1 distribution.

Thank you!

--
https://github.com/tkchia


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi

> On Dec 31, 2018, at 11:51 AM, Ivan Ivanov  wrote:
> 
> I do not trust clouds since many of them have been compromised
> already, and all those Snowden revelations etc... So I sincerely hope
> that it will be always possible to build FreeDOS locally. Happy coming
> New Year ! :)
> 
> Best regards,
> Ivan

It can and does. I build and test them inside VirtualBox running openSuSE. 

Mostly that video just is to demonstrate two things. First, how super easy it 
is to build the release. And that if you really want, you could build on a 
Cloud VPZ.

:-)

Jerome


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi,

> On Dec 31, 2018, at 8:44 AM, TK Chia  wrote:
> 
> Hello Jerome,
> 
>> The short answer is — At present, the online repo management tools do not 
>> support multi-line descriptors. Everything after the first line is ignored.
>> So, stuff on additional lines is excluded from the automatically generated 
>> web pages, rss feed and listing.csv files. This is mostly do to shear 
>> laziness on my part.
>> Eventually, I will get around to making version 3 of the repo management 
>> utilities. Partly for performance, partly for multi-platform support, partly 
>> to make it easier for others to use, partly due to some other stuff. Lots of 
>> little reasons. But, I keep procrastinating and putting it off.
>> :-)
> 
> Well, thank you for the information. :)
> 
> On my end, I have tweaked my gcc-ia16 toolchain build files, to avoid 
> multi-line descriptions in the .lsm's for now.  I guess though that it is a 
> bit late into the FreeDOS 1.3 release schedule to have this change included...

The 1.3 release is a little behind schedule and RC1 hasn’t shipped yet. Once it 
does, from that point on, only bug fixes for the release will be made. So, you 
update may make it into 1.3. After all, it’s a (not really) “bug fix” and not a 
new package.




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Ivan Ivanov]

I do not trust clouds since many of them have been compromised
already, and all those Snowden revelations etc... So I sincerely hope
that it will be always possible to build FreeDOS locally. Happy coming
New Year ! :)

Best regards,
Ivan

пн, 31 дек. 2018 г. в 16:45, TK Chia :
>
> Hello Jerome,
>
> > The short answer is — At present, the online repo management tools do not 
> > support multi-line descriptors. Everything after the first line is ignored.
> > So, stuff on additional lines is excluded from the automatically generated 
> > web pages, rss feed and listing.csv files. This is mostly do to shear 
> > laziness on my part.
> > Eventually, I will get around to making version 3 of the repo management 
> > utilities. Partly for performance, partly for multi-platform support, 
> > partly to make it easier for others to use, partly due to some other stuff. 
> > Lots of little reasons. But, I keep procrastinating and putting it off.
> > :-)
>
> Well, thank you for the information. :)
>
> On my end, I have tweaked my gcc-ia16 toolchain build files, to avoid
> multi-line descriptions in the .lsm's for now.  I guess though that it
> is a bit late into the FreeDOS 1.3 release schedule to have this change
> included...
>
> Thank you!
>
> --
> https://github.com/tkchia
>
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[TK Chia]

Hello Jerome,


The short answer is — At present, the online repo management tools do not 
support multi-line descriptors. Everything after the first line is ignored.
So, stuff on additional lines is excluded from the automatically generated web 
pages, rss feed and listing.csv files. This is mostly do to shear laziness on 
my part.
Eventually, I will get around to making version 3 of the repo management 
utilities. Partly for performance, partly for multi-platform support, partly to 
make it easier for others to use, partly due to some other stuff. Lots of 
little reasons. But, I keep procrastinating and putting it off.
:-)


Well, thank you for the information. :)

On my end, I have tweaked my gcc-ia16 toolchain build files, to avoid 
multi-line descriptions in the .lsm's for now.  I guess though that it 
is a bit late into the FreeDOS 1.3 release schedule to have this change 
included...


Thank you!

--
https://github.com/tkchia


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi, 

> On Dec 29, 2018, at 4:50 PM, Thomas Mueller  wrote:
> […]
> Making the installation depend on having one of two Linux distributions is 
> severely limiting, I would say a show stopper.

There really is no technical reason it couldn’t be built on other Linux 
distros. 

However, the build process is not complete yet and I don’t want to dedicate any 
time to supporting other distros at present. 
Mostly it is the toolchain install script that only supports openSUSE and 
Fedora. What packages must be installed, what package 
manager to use, location of web server files, configuring the system to be able 
to build a release without requiring root privileges.
And as you know, all though their are all very similar, there are definitely 
differences. 

The actual build process relies heavily on make and bash. At least, that is 
mostly portable.

Once complete, I probably add support for some other main distros. Like Debian 
and CentOS. 

> Using FreeDOS 1.2 to build a release would be cool, but installation should 
> also be accessible to users-to-be who have no FreeDOS installation to start.

I agree. That could be done with the previous version. With 1.2, you need to 
boot the big install media. The drop out of the installer and run the 
FDIDEV.BAT. 
This turns the VM and/or Machine into a release build environment. It had some 
serious drawbacks though. Stuck with install media sizes. Pain to update or add 
new packages. Required making the ISOs elsewhere. So other issues. 

The new process solved all of that and more. 

However even with it’s limitations, I may add back the ability to build under 
FreeDOS in the future. It was really cool.

> Installation of FreeDOS should be feasible from any OS that can read and 
> write FAT32, meaning Linux, Haiku, *BSD, Mac OS, and even MS-Windows.

I’m not sure I understand your meaning.

The release media build process has absolutely nothing to do with an end users 
OS or the installation of FreeDOS. It makes the boot media that installs the 
OS. It does not install the OS itself. 

The actually OS installer FDI has not changed much. Mostly just some new 
language translations and other minor tweaks. 

Although, I would like to add an super slimmed down 8086 floppy based version 
to FDI and the release build process. 

:-)

Jerome

(anyhow, back to work on the release build process. I need to add creation of 
the LiveCD versions)




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Thomas Mueller]

Excerpt from Jerome Shidel:

> Requires only one local or remote machine running Linux and
> an internet connection to fetch packages and installer sources.
> (only OpenSUSE and Fedora supported at present)
> Uses the latest repo packages.
> Easily change USB stick sizes.
> Support for multi-language package meta-data
> NO extra steps for CD ISOs
> More Developer Friendly Package Lists
> Less tedious and mistake prone.
> (Multiple steps eliminated. One command builds an entire release)
> A couple more release customization settings
> Install media package location validation and adjusting
> Easier for a tinkerer to make a custom release
> 12x faster and more robust
> Support to add additional media types or sizes
> Some other minor stuff

> I think, that overall, the new process is far superior to the previous one.

> However with all of that being said, I thought that using FreeDOS to build a 
> FreeDOS release
> in 1.2 was really cool. As far as I could tell, except for one person, nobody 
> had any interest
> or used that ability. But, I thought it was awesome. Perhaps, I’ll 
> resurrect that ability in the
> future.

> Jerome

Making the installation depend on having one of two Linux distributions is 
severely limiting, I would say a show stopper.

Using FreeDOS 1.2 to build a release would be cool, but installation should 
also be accessible to users-to-be who have no FreeDOS installation to start.

Installation of FreeDOS should be feasible from any OS that can read and write 
FAT32, meaning Linux, Haiku, *BSD, Mac OS, and even MS-Windows.

Tom


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi again, 

>> On Dec 29, 2018, at 7:47 AM, thraex > > wrote:
>> […]
>> Looking at all this scrolling text (after the make clean translate all
>> command), I noticed that some packages (edict, fdtui and others) didn't
>> have their descriptions translated, so I updated the French and Turkish
>> versions of listing.csv. You can download the archive containing them
>> from > >
>> (As a side note, note that in the description in English of i16butil,
>> the closing parenthesis is missing.)
> 
> Cool. Thanks. I’ll go do that after I send this email. :-)

Done. 

>> Also, for paint2 and and testdisk, there are md5 and sha errors
>> ("contains invalid md5/SHA length for fr, 850" and so on). I must have
>> done something wrong somewhere, sorry for that -- and I couldn't figure
>> out where the mistake was and therefore how to fix it. Just wanted to
>> bring it to your attention.
> 
> […]
> I’ll figure out what’s up and let you know. 

Well, no need to look into it now. The new files do not generate any ERROR 
message.

Yay, less work for me. :-)

Jerome

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi, 

> On Dec 29, 2018, at 7:47 AM, thraex  wrote:
> 
> 
> Jerome Shidel wrote:
> 
>> Hi everybody. 
> 
> Hello Jerome,
> 
>> If you want to see 1.3 built in the cloud on DigitalOcean, check out
>> the https://youtu.be/XZoWCFJDdqY
> 
> Looking at all this scrolling text (after the make clean translate all
> command), I noticed that some packages (edict, fdtui and others) didn't
> have their descriptions translated, so I updated the French and Turkish
> versions of listing.csv. You can download the archive containing them
> from 
> (As a side note, note that in the description in English of i16butil,
> the closing parenthesis is missing.)

Cool. Thanks. I’ll go do that after I send this email. :-)

> Also, for paint2 and and testdisk, there are md5 and sha errors
> ("contains invalid md5/SHA length for fr, 850" and so on). I must have
> done something wrong somewhere, sorry for that -- and I couldn't figure
> out where the mistake was and therefore how to fix it. Just wanted to
> bring it to your attention.

Maybe, maybe not. 

I haven’t gotten around to looking into it yet. It is quite probable that it is
just a compatibility issue and something more I need to write for my CSV
parser. 

Basically, those errors MD5 & SHA hash invalid length means that after 
it parsed that line it realized that the column it thinks is for those fields 
doesn’t have the proper number of characters to be a MD5 or SHA hash.

In other words, It doesn’t think the columns line up properly for those and 
that there was an error somewhere in the preceding fields. 

I’ll figure out what’s up and let you know. 

> Finally, if there is other stuff that can be translated for FreeDOS,
> feel free to yell at me.

:-)

> 
>> But if you only want to see the release build process, skip ahead to
>> 6:45. It takes the server about 10 minutes to build the Floppy, 2 USB
>> stick images and the Legacy CD. 
> 
> Heh, I tried to download the CD file just to fiddle around with it with
> VirtualBox but couldn't connect to http://157.230.50.141/ :)

LOL

That machine was created only to demonstrate building it in the cloud. So after 
making the video, I destroyed the VPS.

You could always watch the first 7 minutes of the video and build one yourself. 
:-)

The cloud build was on https://digitalocean.com  
using Fedora using their cheapest VPS. Their pricing is very reasonable. That 
temporary 
VPS cost $0.007/hour (max $5.00/month). So, creating and destroying it in under 
an hour cost me $0.01 USD. On top of that, 
they been making offers of $100.00 credit to new users in a couple podcasts 
commercials. I’m a couple weeks behind on my
listening. But, I think it was in either Mac Break Weekly or SecurityNow. Don’t 
know the offer code. I’ve been using DO for years.
So, I just skip those ads. 

Generally, I build it locally in VirtualBox using openSUSE Leap. I quickly go 
over the process on the builder wiki
 https://gitlab.com/FreeDOS/builder/wikis/home 
 at gitlab. But other than 
initial creation of the VM, it is exactly the 
same as building it on the cloud. 

There are a couple other commands for it’s make file I need to get around 
documenting sometime. Like how “make fresh” is more or 
less the same as “make clean” with the major exception that it does not purge 
the downloaded repo ISO and doesn’t purge the 
cached package translations. (Why keep re-downloading and rebuilding unchanging 
files?)

:-)

Jerome

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi, 

> On Dec 29, 2018, at 8:38 AM, TK Chia  wrote:
> [..]\
> The i16butil.zip description glitch (I just checked the packages I uploaded 
> onto GitHub) may be because the .lsm file in it has a multi-line description, 
> similar to this:
> 
> Description: GNU binary utilities, for ia16-elf target (on 32-bit DJGPP
> host)
> 
> I am not sure if FreeDOS's packaging tools have problems with parsing such 
> descriptions --- if indeed they do, please let me know.


The short answer is — At present, the online repo management tools do not 
support multi-line descriptors. Everything after the first line is ignored. 

So, stuff on additional lines is excluded from the automatically generated web 
pages, rss feed and listing.csv files. This is mostly do to shear laziness on 
my part. 

Eventually, I will get around to making version 3 of the repo management 
utilities. Partly for performance, partly for multi-platform support, partly to 
make it easier for others to use, partly due to some other stuff. Lots of 
little reasons. But, I keep procrastinating and putting it off. 

:-) 

Jerome

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[TK Chia]

Hello thraex,


Looking at all this scrolling text (after the make clean translate all
command), I noticed that some packages (edict, fdtui and others) didn't
have their descriptions translated, so I updated the French and Turkish
versions of listing.csv. You can download the archive containing them
from 
(As a side note, note that in the description in English of i16butil,
the closing parenthesis is missing.)


The i16butil.zip description glitch (I just checked the packages I 
uploaded onto GitHub) may be because the .lsm file in it has a 
multi-line description, similar to this:


Description: GNU binary utilities, for ia16-elf target (on 32-bit DJGPP
 host)

I am not sure if FreeDOS's packaging tools have problems with parsing 
such descriptions --- if indeed they do, please let me know.


Thank you!

--
https://github.com/tkchia


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[thraex]

Jerome Shidel wrote:

> Hi everybody. 

Hello Jerome,

> If you want to see 1.3 built in the cloud on DigitalOcean, check out
> the https://youtu.be/XZoWCFJDdqY

Looking at all this scrolling text (after the make clean translate all
command), I noticed that some packages (edict, fdtui and others) didn't
have their descriptions translated, so I updated the French and Turkish
versions of listing.csv. You can download the archive containing them
from 
(As a side note, note that in the description in English of i16butil,
the closing parenthesis is missing.)

Also, for paint2 and and testdisk, there are md5 and sha errors
("contains invalid md5/SHA length for fr, 850" and so on). I must have
done something wrong somewhere, sorry for that -- and I couldn't figure
out where the mistake was and therefore how to fix it. Just wanted to
bring it to your attention.

Finally, if there is other stuff that can be translated for FreeDOS,
feel free to yell at me.

> But if you only want to see the release build process, skip ahead to
> 6:45. It takes the server about 10 minutes to build the Floppy, 2 USB
> stick images and the Legacy CD. 

Heh, I tried to download the CD file just to fiddle around with it with
VirtualBox but couldn't connect to http://157.230.50.141/ :)
 



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi Tom, 

> On Dec 28, 2018, at 11:36 AM, Tom Ehlert  wrote:
> 
> Hi Jerome,
> 
> 
>> We are still hard at work on the upcoming FreeDOS 1.3.
> it would be cool to know who 'we’ is

That is a tricky one.

I guess it all depends on what part of 1.3 is being referenced. 

Obviously, the OS is made up from software from many people 
and their contributions to the OS. Thank you for your personal
efforts.  

The FreeDOS Community providing language translations, testing 
and such things. 

Rugxulo does a lot of software mirroring and some package updates.

Jim does all of the high level stuff. OS goals and included package 
decisions. Things like deciding we will have a LiveCD for 1.3. Going 
over licenses and deciding what stays and what goes. It can be 
tedious and time consuming. 

Me, more package repo updates, installer and assembling the 
install media.  

>> But, I just couldn't help sharing something really cool about the
>> new version. It has a completely new release build process. It can
>> even create stock or custom releases on compatible cloud hosting.
> 
> after watching the video (mostly) I think this build process is
> somewhat over engineered.
> 
> I had expected some smart batches, that do some COPY, XCOPY, ZIP, and
> finally build a .ISO.
> 
> to learn that I need a cloud machine, some linux distro, pearl,
> python, and what not to build a DOS install medium is unexpected.
> 
> if this would be the UBUNTU distribution, fine.
> 
> FreeDOS 1.3, not so much.
> 
> Tom

The build process for 1.2 & 1.3 are / were dynamic. The release is configured 
and 
built based on settings in FDI. Things like OS name, version, packages and such
are configured there and used for creating the release. That requires quite a 
bit
of scripting somewhere. 

Excluding the ISO's, the build process for FreeDOS 1.2 was entirely DOS based.
In fact, some if the media for it includes a batch FDIDEV.BAT. That batch will 
convert 
the existing computer or virtual machine into a FreeDOS 1.2 release building
environment that could exactly reproduce the 1.2 release or build a custom 
release.

Since the FreeDOS installer is batch based, 1.2 required some extremely complex 
batch work powered mostly by V8Power Tools. A lot of stuff regarding 
multi-language, 
keyboards and packages are processed and converted during the release build. 
This
could be done on the fly by the batch installer. But, that would have a huge 
impact on
its performance. 

Using smart DOS batch files, from start to finish the Floppy and 2 USB images
would take roughly 2-3 hours to completely build the release. 

Unfortunately, it was a major pain to create the CD images. That step required 
an extra
machine or VM running Linux, some manual juggling, error prone, inflexible and 
really 
annoyed me.

There were also some major limitations with the 1.2 process in regards to the 
USB stick 
images. Using a different size image, let’s say going from a 32mb to a 64mb 
custom LITE 
image was down right cumbersome. 

Also, updating packages for the release was painful. This involved fetching 
them from the 
repo manually. Then, getting them into the correct places in the build 
environment. Then, 
telling the builder to parse there meta-data. 

All of those issue have been solved in the new build process. 

It may be a little over-engineered and could definitely use some streamlining 
in a few areas.
But, it is a completely automated and dynamic release building process. It’s 
also much faster.
The new process takes about 10-15 minutes. 

Basically, these are the improvements the new process provides:

Requires only one local or remote machine running Linux and
an internet connection to fetch packages and installer sources. 
(only OpenSUSE and Fedora supported at present)
Uses the latest repo packages.
Easily change USB stick sizes.
Support for multi-language package meta-data
NO extra steps for CD ISOs
More Developer Friendly Package Lists
Less tedious and mistake prone. 
(Multiple steps eliminated. One command builds an entire release)
A couple more release customization settings
Install media package location validation and adjusting
Easier for a tinkerer to make a custom release
12x faster and more robust
Support to add additional media types or sizes
Some other minor stuff

I think, that overall, the new process is far superior to the previous one. 

However with all of that being said, I thought that using FreeDOS to build a 
FreeDOS release
in 1.2 was really cool. As far as I could tell, except for one person, nobody 
had any interest
or used that ability. But, I thought it was awesome. Perhaps, I’ll resurrect 
that ability in the
future. 

Jerome



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Do FreeDOS in the Cloud

[Tom Ehlert]

Hi Jerome,


> We are still hard at work on the upcoming FreeDOS 1.3.
it would be cool to know who 'we' is

> But, I just couldn't help sharing something really cool about the
> new version. It has a completely new release build process. It can
> even create stock or custom releases on compatible cloud hosting.

after watching the video (mostly) I think this build process is
somewhat over engineered.

I had expected some smart batches, that do some COPY, XCOPY, ZIP, and
finally build a .ISO.

to learn that I need a cloud machine, some linux distro, pearl,
python, and what not to build a DOS install medium is unexpected.

if this would be the UBUNTU distribution, fine.

FreeDOS 1.3, not so much.

Tom



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] Do FreeDOS in the Cloud

[Jerome Shidel]

Hi everybody. 

We are still hard at work on the upcoming FreeDOS 1.3.

But, I just couldn't help sharing something really cool about the new version. 
It has a completely new release build process. It can even create stock or 
custom releases on compatible cloud hosting. 

If you want to see 1.3 built in the cloud on DigitalOcean, check out the 
https://youtu.be/XZoWCFJDdqY 

 video. The first 2:30 is the setup process for the cloud server. The next 4 
minutes is the release builder toolchain installation. 

But if you only want to see the release build process, skip ahead to 6:45. It 
takes the server about 10 minutes to build the Floppy, 2 USB stick images and 
the Legacy CD. 

Eventually, building of the LiveCD will be added to the release build process. 
It will be replacing the Normal CD. 

Hopefully, we will have the remainder of items needed for 1.3 wrapped up soon 
and get RC1 out the door. 

Anyhow, I hope you enjoy the video.

Jerome___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel