Re: [Freedos-devel] Interim FreeDOS Build T2208

Hi Eric, > On Aug 1, 2022, at 2:18 PM, Eric Auer wrote: > >  > Hi! Trying to sort through the log on > >> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/changes.log > > it seems that most changes are NLS updates, build infrastructure, > documentation and

Re: [Freedos-devel] Interim FreeDOS Build T2208

Hi, > On Aug 1, 2022, at 10:51 AM, tom ehlert wrote: > > Hallo Herr Jim Hall, > > am Montag, 1. August 2022 um 16:08 schrieben Sie: > >>> Hi! I agree it would be good to have a changelog visible before >>> downloading those 100s of megabytes >> [..] > I think it's pretty rude behaviour

Re: [Freedos-devel] Interim FreeDOS Build T2208

n we can keep as many old ones around as we want. > > >> On Mon, Aug 1, 2022, 5:19 AM Jerome Shidel wrote: >> Hi Jim and All, >> >> The 1st FreeDOS interim test build is up and available for download at: >> >> https://www

[Freedos-devel] Interim FreeDOS Build T2208

Hi Jim and All, The 1st FreeDOS interim test build is up and available for download at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ :-)

Re: [Freedos-devel] MS-DOS compatibility issue

Hi, > On Jul 31, 2022, at 5:46 AM, tom ehlert wrote: > > >> interesting find. did you try any of the alternatives DRVLOAD, DEVLOD, >> DDL ... > > a compilation of devload, drvload, loadsys > http://toogam.com/software/archive/drivers/dosstart/dosstart.zip > > Tom Ok, this is interesting….

Re: [Freedos-devel] MS-DOS compatibility issue

Hi, > On Jul 31, 2022, at 3:49 AM, TK Chia wrote: > > Hello Jerome, > >>> Generally, I would not include an attachment. However, this is a >>> tiny zip and includes the test source, build scripts and the compiled >>> version. > > Well... I found that your ansitest.com still works with the

Re: [Freedos-devel] MS-DOS compatibility issue

Hi again, > On Jul 30, 2022, at 4:51 PM, Jerome Shidel wrote: > > Hi, > >> On Jul 30, 2022, at 3:03 PM, TK Chia wrote: I just created a boot floppy with 1.3’s Kernel, Command, NANSI and the Test program. Loaded Command and NANSI to low memory with nothing else

Re: [Freedos-devel] MS-DOS compatibility issue

Hi, > On Jul 30, 2022, at 3:03 PM, TK Chia wrote: > > Hello Jerome, > >> The test works correctly under at least the most recent versions of MS-DOS >> (6.x), PC-DOS and DR-DOS. > > Thanks. Well, I could not reproduce whatever failure you were getting > with your routine under FreeDOS.

Re: [Freedos-devel] MS-DOS compatibility issue

HI, > On Jul 30, 2022, at 2:15 AM, TK Chia wrote: > > Hello Ralf Quint, > >> 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

[Freedos-devel] MS-DOS compatibility issue

Hi All, While recently performing a re-install of everything (System Commander Multiple DOS, Windows, Linux booting) on my Pentium Pro, I discovered a minor compatibility issue regarding ANSI.SYS support. Without digging into it more, I cannot say if the issue is NANSI.SYS or elsewhere in

Re: [Freedos-devel] FreeDOS Unstable - interim development builds

how people will (mis)interpret the "FreeDOS >>> Unstable" name. I wonder if "FreeDOS Test" might be a better name for >>> this. > > On Wed, Jun 22, 2022 at 1:22 PM Jerome Shidel jer...@shidel.net wrote: > >> I don’t think “Unstable" would cause much con

[Freedos-devel] Online Get-Together

It’s well past 11am CT. I guess there is not going to be an online get-together today. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Another implementation of GRAFTABL

Hi, > On Jul 12, 2022, at 6:19 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. I haven’t looked at the code for either. But, there are some things in general to

Re: [Freedos-devel] FreeDOS Edlin 2.21 is here!

Hi Gregory, > On Jun 26, 2022, at 9:22 PM, Gregory Pietsch wrote: > > After I released FreeDOS Edlin 2.20 onto an unsuspecting world, I noticed a > couple of items I needed to address in the source code. In an effort to > produce a more perfect FreeDOS Edlin, I have addressed those issues

Re: [Freedos-devel] FreeDOS interim development build

Hi, > On Jun 25, 2022, at 4:41 PM, Aitor Santamaría wrote: > > Hello, > > Thanks for the answers! Your Welcome. > On Sat, 25 Jun 2022 at 22:32, Jerome Shidel <mailto:jer...@shidel.net>> wrote: > For example, if KEYB on the GitLab archive has a commit pus

Re: [Freedos-devel] FreeDOS interim development build

Hi Aitor, > On Jun 25, 2022, at 3:22 PM, Aitor Santamaría wrote: > [...] > How do these logs build up? (I am assuming logs in an user-readable format). > Every time someone updates a tool, do we need to fill in somewhere? > Ideally, the implemented bugs and enhancements from GitLab would go to

[Freedos-devel] FreeDOS interim development build

Hi Jim and all, Well, the work I wanted to do to the RBE and release media is finished. I’ve replaced the downloads on my server with the new versions. You can fetch them, or view the report information at https://fd.lod.bz/releases/unstable/ Mostly,

[Freedos-devel] FreeDOS Unstable - CHANGES.LOG

Hi, > On Jun 22, 2022, at 6:26 PM, Eric Auer wrote: > > > Hi! > >> Changes since FreeDOS 1.3 release >> 2022-06-22 10:02:08 project_RBE (shidel): Adjust interim build file names >> 2022-06-22 09:13:23 project_RBE (shidel): Automatic Unstable Build Versioning >> 2022-06-21 09:21:37

Re: [Freedos-devel] FreeDOS Unstable - interim development builds

leases/ <https://fd.lod.bz/releases/> I have not added a boot warning yet or implemented the black background in the installer. There are several aspects to look at and discuss before doing the official interim development releases. For example, the report includes in document links to cha

[Freedos-devel] FreeDOS Unstable - interim development builds

Hi Jim and the Dev group, I’m in the process of wrapping up some minor improvements to the RBE (Release Build Environment) that I wanted to make for creating the interim development builds of FreeDOS. For example: * Automatic interim build versioning. That way we can easily verify

Re: [Freedos-devel] Thinking about FreeDOS test releases

Hi, > On May 16, 2022, at 7:24 PM, Louis Santillan wrote: > > Any thoughts about the ability to build (more than kernel, FreeCOM, ISO) from > source? > The release build process does not compile individual programs. It pulls pre-compiled versions staged in package format from the Official

Re: [Freedos-devel] Thinking about FreeDOS test releases

Hi, Based on the discussion during the online get-together and the tool-chain and release processes used to maintain packages and deploy release media, this is what I’m thinking… The pipeline used to assemble all the different aspects into a release is very capable. It can handle multiple OS

Re: [Freedos-devel] Testing translations

Hi, > On May 11, 2022, at 11:44 AM, Daniel D. wrote: > > Hi, again! > > Thank you very much for the swift reply! > You welcome. > [..] > Thanks, I didn't know about this software. No problem. It’s still very new and only works on the Package Description Lists at present. Support for

Re: [Freedos-devel] Testing translations

Hi, > On May 11, 2022, at 3:56 AM, Daniel D. wrote: > > Hi! > > I hope this is the correct mailing list to contact. > > Recently, I've done some Norwegian translations of the language files > of FreeDOS, which have been merged into this repository > https://github.com/shidel/fd-nls (is this

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Just a thought about the next version of FreeDOS… It does not seem that it has yet been decided if the next version of FreeDOS should be 1.3.1, 1.3-SR1, 1.4 or 2.0. However, there is no technical reason it needs to be just one line. The current RBE (release build environment) and package

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi, > On Apr 2, 2022, at 10:20 PM, David Ormand wrote: > > In the discussion about what version to assign to the next release: > It has been my understanding that the version number code x.y is defined as: > x is the major number, which indicates a change in interface or function or > some

Re: [Freedos-devel] Thinking about FreeDOS 2.0

> On Apr 1, 2022, at 7:42 AM, Paul Dufresne via Freedos-devel > wrote: > >  > Activé jeu., 31 mars 2022 21:42:12 -0400 Michael Brutman > écrit > > Please forgive me for getting lost on this thread, but what exactly is the > problem that we are trying to solve? > > Are we

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi Adam, > On Mar 29, 2022, at 9:24 AM, Adam Peart wrote: > > If you had the base install by default, and gave the option to install the > separate categories as options that would work. If you wanted go go into > more details then you could list each item in each category and let people >

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Per Jim’s recent post, I went ahead and split the repositories (no symlink’d repos) as well as created a new one for the eventual upcoming 2.0. Also, I added a simple index file to help visitors browsing those repositories more easily navigate to the HTML pages.

Re: [Freedos-devel] Thinking about FreeDOS 2.0

> On Mar 28, 2022, at 6:04 PM, Eric Auer wrote: > > > Hi! > >> Jim has mentioned the possibility of slimming down the release some for 2.0. >> At present we have the options of BASE, BASE + SOURCES, FULL, FULL + SOURCES >> durning installation. >> But with how easy package installation is

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi Jim, > On Mar 28, 2022, at 1:40 PM, Jim Hall wrote: > > On Mon, Mar 28, 2022 at 10:41 AM Paul Dufresne via Freedos-devel > > wrote: >> >>> The branches that receive updates (1.2, 1.3, latest) contain the latest >>> version of the packages that we

Re: [Freedos-devel] Thinking about FreeDOS 2.0

> On Mar 28, 2022, at 11:40 AM, Paul Dufresne via Freedos-devel > wrote: > > The branches that receive updates (1.2, 1.3, latest) contain the latest > version of the packages that we have created. I don’t see a reason to add a > new branch. If we decided to change package file extensions

Re: [Freedos-devel] Thinking about FreeDOS 2.0

> On Mar 28, 2022, at 10:20 AM, Paul Dufresne via Freedos-devel > wrote: > > Activé lun., 28 mars 2022 08:24:15 -0400 Jerome Shidel > écrit >> But with how easy package installation is after the initial install using >> FDIMPLES, I wonder >>

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi, Back to the FreeDOS 2.0 topic… Jim has mentioned the possibility of slimming down the release some for 2.0. At present we have the options of BASE, BASE + SOURCES, FULL, FULL + SOURCES durning installation. But with how easy package installation is after the initial install using

[Freedos-devel] 50,000 feet

Hi all, Fairly often we get asked, whats new. This is usually difficult to answer because it is usually a lot of smaller things. There are updates to the installer, changes to the media, additions and removals of utilities, package updates and more. To help answer this “what’s new” question, I

Re: [Freedos-devel] Lost in translation

Hi, Well, that’s step 1 (package descriptions) of the FreeDOS NLS Desktop application. (FD-NLS app) macOS - https://up.lod.bz/FDNLS_OSX Linux - https://up.lod.bz/FDNLS_LNX Windows - https://up.lod.bz/FDNLS_WIN

Re: [Freedos-devel] Lost in translation

Hi, Update… The Windows cross-compiled version seems to be working now. https://up.lod.bz/FDNLS_WIN Mac version at https://up.lod.bz/FDNLS_OSX Just leaves the Linux version of step 1. Probably tomorrow. :-)

Re: [Freedos-devel] Lost in translation

Hi, > On Mar 21, 2022, at 7:21 PM, Jim Hall wrote: > > On Mon, Mar 21, 2022 at 5:41 PM Mark Olesen wrote: >> >> Is it not possible to create maco wrappers around the new api to >> retain compatibility with the old? Sorry for my ignorance, I never >> used FD-NLS libraries. I would think it

Re: [Freedos-devel] Lost in translation

Hi Mark, > On Mar 21, 2022, at 1:27 PM, Mark Olesen wrote: > > https://www.gnu.org/software/gettext/ > > Port then migrate your current translations to PO format That’s not going to happen. We can’t even find enough people to fix some minor years-old bugs. Expecting someone to rewrite all of

[Freedos-devel] Lost in translation

Hi all, As many of you are probably already aware, a while back I started coordinating language translations for FreeDOS and related projects over on GitHub in the FD-NLS project[1]. The translators that have been contributing do a great job. But with all the various formats and methods used

Re: [Freedos-devel] Thinking about FreeDOS 2.0

> On Mar 3, 2022, at 10:42 AM, Adam Peart wrote: > > Personally in the test stream I would like an updated LiveCD, and a way of > updating the files for an already installed FreeDos. For an existing > installed version, I don't like the idea of having to re-install everything > every time

Re: [Freedos-devel] Thinking about FreeDOS 2.0

> On Mar 3, 2022, at 5:33 AM, richardkolacz...@hotmail.com wrote: > [..] > So with your plans on more frequent releases - (USB only wise) - where does > it leave me? Although, your using a USB stick. Your using it as your HD. So, I’d consider that installed and not Live. You would probably

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi, > On Mar 3, 2022, at 1:13 AM, Jim Hall wrote: > > On Sun, Feb 20, 2022 at 4:16 PM Jim Hall wrote: > [..] >> I'm sure we'll want to discuss "1.4" or "2.0" or whatever version >> comes after 1.3. (I can start a new conversation next week to talk >> about that.) > > > Now that FreeDOS 1.3

Re: [Freedos-devel] freedos 1.3 at german magazine heise

> On Feb 25, 2022, at 8:00 PM, Ralf Quint wrote: > > On 2/25/2022 4:02 AM, Jim Hall wrote: >> https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html > > Just had a quick read over that one and noticed one strange thing mentioned. >

[Freedos-devel] 1.3 Final

Hello All, I think all of the most important issues, features, improvements and testing regarding FreeDOS 1.3 final have been wrapped up. So, 1.3 should be released very soon. Possibly even this weekend sometime. And there is even more good news. With the work on 1.3 winding down, it gave me

Re: [Freedos-devel] RAMdrive install problem (on bare metal)

Hi, First, if you load the driver in the FDCONFIG.SYS you need to provide the full path to the driver. If you remove the line you have added to that file, then you can simply add this to the end of the FDAUTO.BAT or even create a separate batch file to only start the RAM disk when needed. (

Re: [Freedos-devel] Any package updates for FreeDOS 1.3?

Hi, > On Feb 15, 2022, at 10:59 PM, Michael Brutman wrote: > > I'm working on a new mTCP version, and this thread reminded me to ask about a > problem. > > I update mTCP more often than FreeDOS gets updated; it's under active > development and I need to get fixes out. Where this becomes a

Re: [Freedos-devel] Sea Code by the C Shore

> On Feb 8, 2022, at 7:34 PM, Mark Olesen > wrote: > > are you familiar with it? I had heard of it. But, wasn’t familiar. > The file can be embedded straight into C > code. Once the xpm file is created you can translate it into other > data structures of a

Re: [Freedos-devel] Sea Code by the C Shore

> On Feb 8, 2022, at 8:50 AM, Mark Olesen wrote: > > Have you ever considered using xpm file format? Not specifically. At present, it has full support for simple bitmap raster fonts like those in the GNUFONTS package. Danger Engine native formats like fonts (current max 32x32), Graphics

[Freedos-devel] Sea Code by the C Shore

Hi everyone, I’m not really much of a C (pick your flavor) user. Mostly I work in Assembly, Pascal and other languages. However as I’m well aware, C is very popular for development in FreeDOS. So, I have a favor to ask of one of the C gurus. One of the programs that I’ve made recently is a

Re: [Freedos-devel] LiveCD boot from floppy

Hi Willi, > On Jan 19, 2022, at 10:25 AM, Wilhelm Spiegl wrote: > > OK, if the diskette is kept, what about the following idea: > > Simply add a sentence in the readme file that the diskette will not start a > live environment but only an installation. This says everything even to >

Re: [Freedos-devel] LiveCD boot from floppy

realize it would break there current operating system. But, it is now the year 2022 and based on how most people run and use FreeDOS and other DOS platforms, such additional measures just are not warranted. A single warning by the installer is sufficient. > Willi > > :-) Jerom

[Freedos-devel] LiveCD boot from floppy

Hello all, The LiveCD menu also contains a Boot from floppy disk entry. Do we really need to keep this option on the menu? A user can just insert a floppy disk and boot it without having the CD inserted. I think the use case for this option is very low. Removing it would problem only be a

[Freedos-devel] LiveCD FloppyEdition

Hi Everyone (but mostly Jim), This is what I’m thinking for 1.3-Final regarding the LiveCD Boot menu. Leave everything as it is already. Except create an entry after “Install to harddisk” called “Install using the Floppy Edition”. Then for it’s descriptive text at the bottom of the screen,

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

Hi, > On Jan 17, 2022, at 4:05 PM, Liam Proven wrote: > > On Mon, 17 Jan 2022 at 20:15, Robert Riebisch wrote: >> >> Hi Jim, >> >>> I suspect the term is regional :-) It's the same thing as a USB thumb >>> drive or USB flash drive. >>> >>> USB flash drive is the more common term. >> >>

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

Hi, > On Jan 16, 2022, at 3:07 PM, Jim Hall wrote: > I think it's better not to hide features - so yes, the FloppyEdition > installer should get its own entry in the CD boot menu. But from your > description, maybe it needs a different name. Hi, > On Jan 16, 2022, at 3:07 PM, Jim Hall

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

Hi, > On Jan 16, 2022, at 3:34 PM, Jim Hall wrote: > > Something I've wondered is if we really need the USB installer at all. Not as > in "let's get rid of the USB installer for the sake of getting rid of it." I > know that some people do use the USB installer (comes up in questions on >

[Freedos-devel] Contemplations, Considerations and some Conclusions

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 like to share with you and get feedback on… As you know, the

Re: [Freedos-devel] Fwd: ACPI auto power ON

Hi, > On Jan 13, 2022, at 9:14 AM, Mercury Thirteen via Freedos-devel > wrote: > > This feature was nonstandard across various BIOS implementations, so it is > highly likely that if the BIOS does not support it via its built-in interface > (the "Press to enter SETUP" prompt) it is probably

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

Hi, > is there anyway i can contribute to freedos's development with C++? As a first step, I recommend reading the wiki on Contributing to FreeDOS. http://wiki.freedos.org/wiki/index.php/Contribute

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

> On Jan 10, 2022, at 4:54 PM, Tyson Oswald wrote: > > I wa able to create and mount/format a VMDK virtual hard disk with fixed size > 600MB file. I was able to mount I on MacOS. Thanks Jerome for the assist. > Maybe I will do a YT video on it. > > Now the fun begins. > > Tyson Your

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

mat the disk I get an error >>>> >>>> DOS Diver error (hex) 01 >>>> >>>> [Error 129] > >>>> On Jan 10, 2022, at 11:53 AM, Jerome Shidel wrote: >>> >>> Assuming it was renamed properly, and during boot the kernel displays the &g

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

Hi, > On Jan 10, 2022, at 10:57 AM, Tyson Oswald wrote: > > Alright I have tried to Crete a VMDK virtual hard disk in Box but when I go > to format the disk I get an error > > DOS Diver error (hex) 01 > > [Error 129] Assuming it was renamed properly, and during boot the kernel displays the

Re: [Freedos-devel] REMember a bug

Hi Robert, > On Jan 9, 2022, at 12:31 PM, Robert Riebisch wrote: > > Hi Jerome, > >> 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

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

Hi, > On Jan 9, 2022, at 12:51 PM, Tyson Oswald wrote: > > There is supposedly a way to mount the virtual disk on macOS when it is > unmounted from the VM but I haven’t been able to get it to work. VB comes > with MacFuse for that purpose but have never been able to get it to work. >

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

Hi, > On Jan 9, 2022, at 9:45 AM, Tyson Oswald wrote: > > Quick Question. > > I see Jim has placed several projects out on GitHub in the past few weeks, > cool. Maybe Jim should do a video on his DOS/GitHub workflow. :-) > I am developing on FreeDOS but how are others placing their code

Re: [Freedos-devel] REMember a bug

Hi Jose, > On Jan 8, 2022, at 7:46 PM, Jose Senna wrote: > > Jerome Shidel said: > >> REM this thing [[x|4]] or later >> in one of its remarks. Every time the batch >> was executed, it displayed a “4]]” command not found error. > > It is not a

[Freedos-devel] REMember a bug

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 executed, it displayed a “4]]” command not

Re: [Freedos-devel] Installer NLS Questions

Hello, > On Jan 7, 2022, at 7:12 AM, Emir SARI via Freedos-devel > wrote: > > Hello Jerome, > >> Boot to standard US English Codepage. > > Changed the codepage to 437, verified with broken Turkish display characters. > >> Then run them through the conversion program (mkvV8Font). You will

Re: [Freedos-devel] Installer NLS Questions

Hello Emir, > On Jan 6, 2022, at 3:32 AM, Emir SARI via Freedos-devel > wrote: > > Hello Jerome, > >> Let me know if you run into any problems or have any questions. > > I’ve tested the Turkish characters file with imgedit. As far as I can see, > the glyph ascenders and descenders for

Re: [Freedos-devel] dir /od

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

Re: [Freedos-devel] dir /od

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

Re: [Freedos-devel] Installer NLS Questions

Hi Emir, Since I haven’t got around to making a doc for creating the V8F font files, here is the easiest way… For Turkish, make sure you have a copy of the raw font from FD-NLS. https://github.com/shidel/fd-nls/blob/master/fdi/language/CP857.FNT

Re: [Freedos-devel] mkey keyboard

> On Dec 31, 2021, at 1:02 PM, tom ehlert wrote: > However I react supercritically when people that never contributed > anything suggest that I contribute some work. I hope you are not suggesting the Wilhelm does not contribute. While he may not write code, he has put a lot of work into

Re: [Freedos-devel] Installer NLS Questions

> >> While the installer (FDI) is not fast, the main issue is your whole VM is >> really slow. I could even see the initial boot menu drawing each line. I >> think most of the “slowness” your experiencing is video related. You really >> want to enable some sort of acceleration. Jim has shared

Re: [Freedos-devel] Installer NLS Questions

Hello, > On Dec 31, 2021, at 5:03 AM, Emir SARI via Freedos-devel > wrote: > > > Hello everyone, > > I have been making the final tests for the installer in Turkish, and have > some questions below. > > Also, the installation process seems to be pretty slow on QEMU. I have used >

Re: [Freedos-devel] Thank you Jerome

Hello All, You are welcome and Thank you. There just are not enough hours in a day. But what I can manage to squeeze in, I try to get done. :-) Jerome ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net

Re: [Freedos-devel] Bare Metal installation of FreeDOS

> On Dec 27, 2021, at 11:16 PM, richardkolacz...@hotmail.com wrote: > [..] > In the above link, photo 002.jpg illustrates error with CD-ROM initialization > - attempting to use the UDVD2 CD driver -error 255 (failed). Any ideas how to > fix? My laptop has an internal DVD drive (laptop about 8

Re: [Freedos-devel] Two remarks about FreeDOS 1.3 RC5

Hi Juan, > Hello. > > I can access the site without any issues at all but anyway an > alternative location is: > ftp://ftp.fu-berlin.de/pc/languages/djgpp/current/v2tk/l290d10b.zip > ftp://ftp.fu-berlin.de/pc/languages/djgpp/current/v2tk/l290d10d.zip >

Re: [Freedos-devel] Bare Metal installation of FreeDOS

Hello, > On Dec 27, 2021, at 7:41 AM, richardkolacz...@hotmail.com wrote: > > Jerome > > > Thanks for your detailed instructions - HOWEVER nothing seemed to work for > me. > > > With my Windows 10 computer, I could not even get to any install screen (for > FD13 RC5), even IF I wanted to

Re: [Freedos-devel] Bare Metal installation of FreeDOS

Hi, > On Dec 26, 2021, at 5:32 AM, richardkolacz...@hotmail.com wrote: > > I am investigating installing FreeDOS 1.3 RC5 as a bare metal installation > (i.e. everything is on a 16 GByte USB stick) and will try to boot off the USB > stick (i.e. the USB stick becomes the C:\ drive and so the

Re: [Freedos-devel] Two remarks about FreeDOS 1.3 RC5

Hi, > The second issue is that the DJGPP port of lynx distributed with RC5 is > broken. As I have announced in: > https://www.delorie.com/archives/browse.cgi?p=djgpp/2021/12/02/18:54:50 > the fixed port is available as: > http://ftp.delorie.com/pub/djgpp/current/v2tk/l290d10b.zip >

Re: [Freedos-devel] Let me count the ways

Hi Tom, > On Dec 25, 2021, at 3:47 PM, tom ehlert wrote: > [..] > being a programmer, I had expected that ALL of these different methods > to install freedos would have resulted in 2 possible different > outcomes: normal mode, and advanced mode. The "normal ways to install list" makes it seem

[Freedos-devel] Let me count the ways

Thank you for your help in testing RC5. So far, testing has gone very well. Regarding installation and the media, there have been a few minor issues that have been already corrected. A couple that still need fixed and a few things that need investigated further. This of course is not

Re: [Freedos-devel] Two remarks about FreeDOS 1.3 RC5

> On Dec 24, 2021, at 5:27 PM, Juan Manuel Guerrero > wrote: > > I have been playing with the latestet FreeDOS 1.3 RC5 and I have > observed that the line: > if exist %dosdir%\LINKS\NUL set PATH=%path%;%dosdir%\LINKS > in FDAUTO.BAT does not work because LINKS and all the other network >

[Freedos-devel] The land that time forgot

Hello Everyone, Recently, I noticed we had translations for a program that was not in the online repositories. This caused me to to do some digging and I found out something rather interesting. Many years ago when FreeDOS 0.9 SR2 was released, it included several things we seem to forgotten

[Freedos-devel] RC4 Videos (was Testing FreeDOS 1.3 RC5)

Hi Louis, > On Dec 24, 2021, at 4:36 AM, Louis Santillan wrote: > > > An interesting (and series of very very long) "hot takes" of FD 1.3RC4 from > the "Temporarily Offline Retro Tech" youtube channel. I’ve seen all but part 4 (which I’m going to watch in a few minutes). I didn’t think to

Re: [Freedos-devel] Testing FreeDOS 1.3 RC5 (Games)

Hi, Jim Because, there are also VM’s like VMware, DOSBox, DOSBOX-X, Bochs, etc. It might be good for you to start a compatibility spead-sheet. Jerome ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net

[Freedos-devel] FDIMPLES support for BonusCD

Hello All, > On Dec 19, 2021, at 2:58 PM, Radek Krzyśków wrote: > [..] > > 1) How to use `FDIMPLES` with Bonus CD? > > Running `FDIMPLES` with "FD13BNS.ISO" shows "Package media not > found!", so I install additional software by

Re: [Freedos-devel] FDTUI and Minibox

It wouldn’t hurt to report it to our GitLab issues as well. Then, if the developer no longer wants to update it, we will at least have it listed and possibly get to it ourselves at some point. Also, it will let anyone who intends to report the bug on our tracker, know it has already been

Re: [Freedos-devel] FreeDOS 1.3-RC5

Hi, > On Dec 10, 2021, at 2:02 AM, thraex wrote: > > > > On 9.12.2021 18:35, Jerome Shidel wrote: > >> >>> * When launching PGME, I couldn't find the PGME.BAT file. So I can't >>> start FDIMPLES for instance. >> >> There is no such fi

Re: [Freedos-devel] FreeDOS 1.3-RC5

Hi, > On Dec 9, 2021, at 8:55 AM, thraex wrote: > > > > On 9.12.2021 01:15, Jerome Shidel wrote: >> Hello FreeDOS Community, >> >> The wait for 1.3-RC5 is over. It has arrived! > > Yay! Thank you! :-) > I gave it a quick try in Vi

[Freedos-devel] FreeDOS 1.3-RC5

Hello FreeDOS Community, The wait for 1.3-RC5 is over. It has arrived! There are so many changes, improvements and updates that it is not practical to go into it all. But, I’ll point out a couple special things to look forward to in RC5. New FreeCOM 0.85a New Kernel 2043 and an 8086 version

Re: [Freedos-devel] The FreeDOS Orphanage

Hi, > On Nov 29, 2021, at 11:10 PM, Mark Olesen wrote: > > A centralized location is very serious to me as a developer. I agree. Originally, the Orphanage was only a semi-official place I used to prepare and maintain packages that would be uploaded to the Repository. It took rather a long

[Freedos-devel] The FreeDOS Orphanage

Hi All, This a heads up notification. (Mostly) With the inclusion of every package that is provided with FreeDOS and for some additional reasons, the FreeDOS Orphanage has moved and been renamed. It could be called FreeDOS on GitLab, FreeDOS Projects or just plan FreeDOS, I went with the

[Freedos-devel] RC5 Status Update

Hi All, Well, I decided to spend more time off the computer during the holiday. I wanted to spend more time with family and relaxing. But, I did get a lot of things knocked off “The Schedule” for the upcoming 1.3-RC5 release since my last update. I won’t go into all the fine details for

Re: [Freedos-devel] 1.3-RC5

Hi all, I’ve decided to postpone the timeline/schedule a couple days in order to spend additional time updating packages and metadata for numerous other packages. Not a huge delay. But, I think one that is worthwhile. :-) Jerome ___

Re: [Freedos-devel] Upcoming 1.3-RC5

Hi Eric, > On Nov 8, 2021, at 4:42 PM, E. Auer wrote: > > > Hi Jerome, > >> Here is the NEW general logic used by the installer in NORMAL mode. >> if the MBR for the target hard disk DOES NOT CONTAIN any boot code in >> the MBR, then ASSUME YES and overwrite it. >> if the MBR for

[Freedos-devel] 1.3-RC5

Hi all, Partly, this is a TODO note to myself. Partly, it’s a heads-up RC5 is coming very soon. More or less this an over simplified version of my current timeline/schedule for RC5… Today… Updated installers with the MBR boot code check. The utility to check was done a

[Freedos-devel] Upcoming 1.3-RC5

Hi all, I’m currently making the changes to the OS installers regarding the overwriting of the MBR. The ADVANCED mode has always prompted wether or not to overwrite it. Here is the NEW general logic used by the installer in NORMAL mode. (There is more to it, like error and safety checks.

<    1   2   3   4   5   >