freedos-user Mailing List for The FreeDOS Project

Thomas Desi:

> looking for text editor vi (clones) for (Free-)DOS, using
> the GERMAN language keyboard/setting.
> [...]
> Elvis is too large, needs extention, and vim 72 needs a
> runtime file and so on.

What about earlier Vim versions, e.g.:

   2.0 <https://archive.org/download/vim-2.0-msdos>
   3.0 <https://vetusware.com/download/VIM%203.0/>
   5.0 <https://archive.org/details/vim50-msdos>

Vetusware requiers registration, but it is a great and
ethical resource.  I highly recommend it.  Where is 4.0?

-- 
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments

Mart Zirnask:

> Fellow umlaut user here -- thanks from me also.

Thou art welcome.

> After a superficial googling, the only available repo for
> Oak Hill Vi seems to be archive.org:
> https://archive.org/details/msdos_VI60A1_shareware

Avoid Google.  It is findable in a lot of interesting
places via Marginalia:

      <https://old-search.marginalia.nu/search?query=%22Oak+Hill+Vi%22>
e.g.: <http://cd.textfiles.com/simtel/simtel0101/simtel/editor/00_index.htm>

including newer version 7.0!  It also found its old
homepage:

   <https://web.archive.org/web/20001003152040/http://home.att.net/~leeperd/ohvimain.html>

-- 
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments

Fellow umlaut user here -- thanks from me also.
After a superficial googling, the only available repo for Oak Hill Vi
seems to be archive.org:
https://archive.org/details/msdos_VI60A1_shareware

Best,
Mart

On Fri, 12 Jun 2026 at 23:54, Thomas Desi via Freedos-user
<fre...@li...> wrote:
>
> excellent!
> thx!
>
>
> > Am 12.06.2026 um 22:48 schrieb Anton Shepelev via Freedos-user <fre...@li...>:
> >
> > Thomas Desi:
> >
> >> looking for text editor vi (clones) for (Free-)DOS,
> >> using the GERMAN language keyboard/setting.
> >
> > Try Oak Hill Vi.  Its manual says:
> >
> >        While in the input mode, you may enter any ASCII character into
> >        your text by holding down the <alt> key and entering the decimal
> >        value of the character from the number keypad portion of the
> >        keyboard.  For example pressing <alt>128 and then releasing the
> >        <alt> key will produce the character Ђ.  If you are typing in a
> >        language other than English you may have frequent need for some of
> >        these characters.  They may be mapped with the ":map!" command into
> >        function key or other keystroke combinations that you find useful.
> >        For example, the command sequence
> >
> > Perhaps, you could add Genman-specific mapping for insert mode via :map!
> > in that editor.
> >
> > --
> > ()  ascii ribbon campaign -- against html e-mail
> > /\  www.asciiribbon.org   -- against proprietary attachments
> >
> >
> >
> > _______________________________________________
> > Freedos-user mailing list
> > Fre...@li...
> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user

excellent!
thx!


> Am 12.06.2026 um 22:48 schrieb Anton Shepelev via Freedos-user <fre...@li...>:
> 
> Thomas Desi:
> 
>> looking for text editor vi (clones) for (Free-)DOS,
>> using the GERMAN language keyboard/setting.
> 
> Try Oak Hill Vi.  Its manual says:
> 
>        While in the input mode, you may enter any ASCII character into
>        your text by holding down the <alt> key and entering the decimal
>        value of the character from the number keypad portion of the
>        keyboard.  For example pressing <alt>128 and then releasing the
>        <alt> key will produce the character Ђ.  If you are typing in a
>        language other than English you may have frequent need for some of
>        these characters.  They may be mapped with the ":map!" command into
>        function key or other keystroke combinations that you find useful.
>        For example, the command sequence
> 
> Perhaps, you could add Genman-specific mapping for insert mode via :map!
> in that editor.
> 
> -- 
> ()  ascii ribbon campaign -- against html e-mail
> /\  www.asciiribbon.org   -- against proprietary attachments
> 
> 
> 
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user

Thomas Desi:

> looking for text editor vi (clones) for (Free-)DOS,
> using the GERMAN language keyboard/setting.

Try Oak Hill Vi.  Its manual says:

        While in the input mode, you may enter any ASCII character into
        your text by holding down the <alt> key and entering the decimal
        value of the character from the number keypad portion of the
        keyboard.  For example pressing <alt>128 and then releasing the
        <alt> key will produce the character Ђ.  If you are typing in a
        language other than English you may have frequent need for some of
        these characters.  They may be mapped with the ":map!" command into
        function key or other keystroke combinations that you find useful.
        For example, the command sequence

Perhaps, you could add Genman-specific mapping for insert mode via :map!
in that editor.

-- 
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments

Hi :-)

Glad you noticed that FDAPM APMDOS uses less RAM than DOSIDLE :-)

> Maybe "FDAPM /apmdos" is not included as default because it can slow 
> down some application, am I correct?

In that case, you could use the ADV:xyz options instead of APMDOS,
see the documentation, but I have another theory ;-)

The FreeDOS kernel includes the IDLEHALT config sys option to
get some basic "idle" power saving without using any extra RAM.

So whether you use FDAPM or IDLEHALT depends on how much RAM
you want to spend. Also, as with LBACACHE, CDRCACHE and possibly
Jack's caches and disk drivers (UHDD, UDVD2, UIDE, etc.) there
MIGHT be side effects of loading those high into UMB, so given
how little RAM is used by FDAPM, you MAY prefer to load it low.
Things will work fine when loaded high on MOST systems anyway :-)

Regards, Eric

Not a problem. That's what the freedos-user email list is for -- to
ask questions. :-)


On Thu, Jun 11, 2026 at 1:24 PM Franco Martelli wrote:
>
> Ah, well, nothing to say more. Yes I modified my FDAUTO.BAT and
> FDCONFIG.SYS files to load a customized setup, thank you all for the
> good job with FreeDOS 1.4, I apologies for the noise!

> On 11/06/26 at 18:55, Jim Hall via Freedos-user wrote:
> > Actually, FDAPM should be loaded in the :DOSHIGH section of
> > FDAUTO.BAT. I didn't type the "LH" command before it, in my example,
> > but this is what's in the default FDAUTO.BAT file:
[..]
> >
> > If you modified your FDAUTO.BAT, you should check that FDAPM is
> > loaded. (Note: the slash in the FDAPM command line option is optional
> > .. that's the same as FDAPM /APMDOS or FDAPM APMDOS)

Hi,

On Tue, Jun 2, 2026 at 8:19 PM tsiegel--- via Freedos-user
<fre...@li...> wrote:
>
> I don't remember exactly, but there is indeed a set of programs that can
> do that.  If I recall correctly, they were called mark and release.  You
> would run the mark program first, load any tsrs or other programs you
> wanted, and after you were done with them, you would run the release
> program, and it would clear memory up to the point where you placed the
> mark.
>
> It's been many many years since I used them, so I don't remember where I
> got them, but a search of garbo or simtelnet might locate them for

* http://cd.textfiles.com/somuch/smsharew4/UTILS/TSRCOM35.ZIP
* https://ftp.lip6.fr/pub/pc/garbo/pc/memutil/tsrcom35.zip

On 11/06/26 at 18:55, Jim Hall via Freedos-user wrote:
> Actually, FDAPM should be loaded in the :DOSHIGH section of
> FDAUTO.BAT. I didn't type the "LH" command before it, in my example,
> but this is what's in the default FDAUTO.BAT file:
> 
> 
> :DOSHIGH
> 
> lh fdapm APMDOS
> lh ctmouse
> REM lh share
> 
> if not exist %DOSDIR%\BIN\DOSLFN.COM goto NOLFN
> lh %DOSDIR%\BIN\DOSLFN.COM
> REM - Add other stuff here once LFN is loaded..
> 
> 
> 
> If you modified your FDAUTO.BAT, you should check that FDAPM is
> loaded. (Note: the slash in the FDAPM command line option is optional
> .. that's the same as FDAPM /APMDOS or FDAPM APMDOS)

Ah, well, nothing to say more. Yes I modified my FDAUTO.BAT and 
FDCONFIG.SYS files to load a customized setup, thank you all for the 
good job with FreeDOS 1.4, I apologies for the noise!

kind regards,
-- 
Franco Martelli

On Thu, Jun 11, 2026 at 11:17 AM Franco Martelli via Freedos-user
<fre...@li...> wrote:
>
> On 11/06/26 at 16:40, Jim Hall via Freedos-user wrote:
> > Out of curiosity, did FDAPM not prevent high CPU usage? Typically, you
> > would run this in your FDAUTO.BAT
> >
> > FDAPM /apmdos
> >
> >
> > For example, that's what I use in my FDAUTO.BAT, and FDAPM /STATS
> > shows the CPU is idle about half the time:
>
> Yes, sadly my web search result omitted FDAPM, it seems to work well
> here, like DOSidle does and it takes only 1K of RAM despite of DOSidle
> that it takes 3K of RAM.
>
> So, is there any drawback to add that line (FDAPM /apmdos) together the
> other lines related to FDAPM that already exist in FDAUTO.BAT?
> ...
> alias reset=fdisk /reboot
> alias reboot=fdapm warmboot
> alias halt=fdapm poweroff
> ...
>
> Maybe "FDAPM /apmdos" is not included as default because it can slow
> down some application, am I correct?
>


Actually, FDAPM should be loaded in the :DOSHIGH section of
FDAUTO.BAT. I didn't type the "LH" command before it, in my example,
but this is what's in the default FDAUTO.BAT file:


:DOSHIGH

lh fdapm APMDOS
lh ctmouse
REM lh share

if not exist %DOSDIR%\BIN\DOSLFN.COM goto NOLFN
lh %DOSDIR%\BIN\DOSLFN.COM
REM - Add other stuff here once LFN is loaded..



If you modified your FDAUTO.BAT, you should check that FDAPM is
loaded. (Note: the slash in the FDAPM command line option is optional
.. that's the same as FDAPM /APMDOS or FDAPM APMDOS)

Emerson Moura replied to this, but used a different subject line, so
I'm copying/pasting that reply into this thread so it's in one place:


> DOSIDLE is the program most commonly used with virtual machines.
> However, MS-DOS 6.x already includes a power management utility
> called POWER. Nevertheless, FDAPM, which is included with FreeDOS,
> is generally the preferred solution because it is more modern and
> also compatible with MS-DOS.

On 11/06/26 at 16:40, Jim Hall via Freedos-user wrote:
> Out of curiosity, did FDAPM not prevent high CPU usage? Typically, you
> would run this in your FDAUTO.BAT
> 
> FDAPM /apmdos
> 
> 
> For example, that's what I use in my FDAUTO.BAT, and FDAPM /STATS
> shows the CPU is idle about half the time:

Yes, sadly my web search result omitted FDAPM, it seems to work well 
here, like DOSidle does and it takes only 1K of RAM despite of DOSidle 
that it takes 3K of RAM.

So, is there any drawback to add that line (FDAPM /apmdos) together the 
other lines related to FDAPM that already exist in FDAUTO.BAT?
...
alias reset=fdisk /reboot
alias reboot=fdapm warmboot
alias halt=fdapm poweroff
...

Maybe "FDAPM /apmdos" is not included as default because it can slow 
down some application, am I correct?

regards,
-- 
Franco Martelli

*DOSIDLE* is the program most commonly used with virtual machines.
However, *MS-DOS
6.x* already includes a power management utility called *POWER*.
Nevertheless, *FDAPM*, which is included with *FreeDOS*, is generally the
preferred solution because it is more modern and also compatible with
*MS-DOS*.

Em qua., 27 de mai. de 2026 às 15:56, Sabina Zelená. via Freedos-user <
fre...@li...> escreveu:

> G‎reetings.
> I am using DOS(both,FreeDOS & MS-DOS) also on various semi-modern
> laptops,thin clients,etc.,mostly with Intel Atom CPU.
> I wish to lower CPU frequency,while in DOS(i have usually multiboots with
> Windows) to conserve power & reduce heat stress from CPU.
> It is nonsense to let run CPU @ 1.6GHz,while in DOS,i would wish to lower
> the frequency to 100MHz for DOS,i heard about CPU Throttle,is it
> stable/safe?
> Has some1 real experiences?
> Has it some dangers?
> What is the right configuration(ideally Config & Autoexec examples)?
> For example my Intel Atom laptop Asus Eee PC 901 can run on battery for 4
> hrs.,w‎hen running Windows 7 Super Lite,but when running
> DOS(regardless,which,i have both,MS-DOS 6.22 & FreeDOS 1.3 on it),battery
> is dead within 1.5hrs.
> & can it be also used in MS-DOS,or it is exclusively for FreeDOS?
> Thanx for any advices/experiences.
> Live long & prosper.
> With best regards Sabina Zelená(=Green).
> Sent from my BlackBerry Passport,RIM OS 10 smartphone.
> Veganism is the base of Vulcan Wisdom.
> ...
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


-- 
Emerson W.S.Moura

Out of curiosity, did FDAPM not prevent high CPU usage? Typically, you
would run this in your FDAUTO.BAT

FDAPM /apmdos


For example, that's what I use in my FDAUTO.BAT, and FDAPM /STATS
shows the CPU is idle about half the time:

C:\>fdapm /stats
Performing action: STATS
Found resident FDAPM / POWER driver version 1.0
Savings mode: BIOS APM plus interrupt hooks (MAX setting)
 CPU was idle 51% of the time


But if I run an app (like As-Easy-As, to run a few calculations and a
line-fit of some x-y data) then the CPU has more real work to do, so
the CPU is idle only one-third the time after I exit the spreadsheet:

D:\APP$\ASEASY>fdapm /stats
Performing action: STATS
Found resident FDAPM / POWER driver version 1.0
Savings mode: BIOS APM plus interrupt hooks (MAX setting)
 CPU was idle 33% of the time




On Thu, Jun 11, 2026 at 8:06 AM Franco Martelli wrote:
>
> Hi everybody,
>
> I was affected by high CPU usage on my FreeDOS 1.4 virtual machine so,
> after a web search, I found the utility DOSidle ¹ and after executed in
> my FDAUTO.BAT it dramatically reduced the CPU usage of almost ten times.
>
> I think that DOSidle ¹ should be a must have for all machines that run a
> DOS operating system on real or virtualization hardware.
>
> How about to bundle it in FreeDOS? Do you agree with my considerations?
> Any criticism?
>
> regards,
>
> ¹
> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.1/html/en/util/dosidle/20120922.4/index.html

Hi everybody,

I was affected by high CPU usage on my FreeDOS 1.4 virtual machine so, 
after a web search, I found the utility DOSidle ¹ and after executed in 
my FDAUTO.BAT it dramatically reduced the CPU usage of almost ten times.

I think that DOSidle ¹ should be a must have for all machines that run a 
DOS operating system on real or virtualization hardware.

How about to bundle it in FreeDOS? Do you agree with my considerations? 
Any criticism?

regards,

¹ 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.1/html/en/util/dosidle/20120922.4/index.html
-- 
Franco Martelli

Hi Jim,
Perhaps, it will depend on if anyone even knows that freedos exists.
Might also post it at DOS ain't dead.
has been quite a while since a DOS port of Lynx was actually  compiled.
Kare



On Tue, 9 Jun 2026, Jim Hall wrote:

> Hi Karen
>
> I think that is a great idea, to see if anyone on the Lynx development
> list would like to compile a DOS version. The Lynx developers would
> know best how to do it, so that seems like the right group.
>
> On Tue, Jun 9, 2026 at 3:36 PM Karen Lewellen <kle...@sh...> wrote:
>>
>> Hi Jim,
>>   I am no software coder, so cannot contribute in that way.
>> Would you  like me to post this on the Lynx development list, in case a
>> member is interested?
>>
>

Hi Karen

I think that is a great idea, to see if anyone on the Lynx development
list would like to compile a DOS version. The Lynx developers would
know best how to do it, so that seems like the right group.

On Tue, Jun 9, 2026 at 3:36 PM Karen Lewellen <kle...@sh...> wrote:
>
> Hi Jim,
>   I am no software coder, so cannot contribute in that way.
> Would you  like me to post this on the Lynx development list, in case a
> member is interested?
>

  - [fix] case-less file name comparisons when checking packages for 
conflicting files on hard disk
  - [new] you can now press a or 3 to abort the installation of a 
package with files on disk
  - [fix] updated translations


get it here

https://git.gay/sparky4/fdnpkg16/releases/download/0.99.8254c/fdnpkg16.zip

or any of the release places


a note for Jerome:
The error levels is what i am going to focus next but i need to be in a 
voice chat with you or someone and discuss the error levels for the program

because i never actually implemented error levels in any program before. 
so this is exciting

i know where to implement them is in src/fdnpkg16.c
with the QUIT(0) code lines

Hi Jim,
  I am no software coder, so cannot contribute in that way.
Would you  like me to post this on the Lynx development list, in case a 
member is interested?

Best,



On Tue, 9 Jun 2026, Jim Hall via Freedos-user wrote:

> I mirrored the Lynx code release to ibiblio, although I see Lynx 2.9.3
> doesn't have a DOS exe (but the sources include a DOS makefile). If
> someone out there wants to contribute, it would be great to compile
> (and share) a DOS exe for others to use.
>
>
> On Fri, May 29, 2026 at 7:37 PM Karen Lewellen via Freedos-user
> <fre...@li...> wrote:
>>
>> Hi,
>> Since someone  indicated that lynx had not been updated since 2021, I
>> wanted  to share the below.
>> Was updated this week.
>> Karen
>>
>>
>>
>> On Wed, 27 May 2026, Thomas Dickey wrote:
>>
>>> The current version of lynx is 2.9.3
>>>
>>> It's available at
>>>       https://lynx.invisible-island.net/
>>>       https://invisible-island.net/archives/lynx/
>>> Development & patches:
>>>       https://lynx.invisible-island.net/current/index.html
>>>
>>> (I'll update the win32 installers page "soon")
>>>
> [..]
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

I mirrored the Lynx code release to ibiblio, although I see Lynx 2.9.3
doesn't have a DOS exe (but the sources include a DOS makefile). If
someone out there wants to contribute, it would be great to compile
(and share) a DOS exe for others to use.


On Fri, May 29, 2026 at 7:37 PM Karen Lewellen via Freedos-user
<fre...@li...> wrote:
>
> Hi,
> Since someone  indicated that lynx had not been updated since 2021, I
> wanted  to share the below.
> Was updated this week.
> Karen
>
>
>
> On Wed, 27 May 2026, Thomas Dickey wrote:
>
> > The current version of lynx is 2.9.3
> >
> > It's available at
> >       https://lynx.invisible-island.net/
> >       https://invisible-island.net/archives/lynx/
> > Development & patches:
> >       https://lynx.invisible-island.net/current/index.html
> >
> > (I'll update the win32 installers page "soon")
> >
[..]

On Wed, Apr 22, 2026 at 11:32 AM <per...@gm...> wrote:

>
>
> On Wed, Apr 22, 2026, 9:18 AM drohde--- via Freedos-user <
> fre...@li...> wrote:
>
>> Ralf,
>>
>>
>>
>> Thanks for the response.
>>
>>
>>
>> Lantastic:   It installs fine and can trying to map a drive to a server
>> but gets “unimplemented internal dos function INT 2F/121a”   Any thoughts
>> on that one?   It can map a printer fine.
>>
>>
>>
> ...

For anyone using Lantastic, please try this test kernel.  It has the
unimplemented functions, works to CD on remote mapped drives, and if LPT#
is mapped to remote device then "NET PRINT file.ext LPT#" should work.  All
in all, just some minor changes, all in git.

https://github.com/FDOS/kernel/releases/download/ke2045/test.zip   (note:
this is post 2045 version, but this is just a handy place to make available
since the changes are minimal)

Please reply if you are able to test.  I am interested in if now works for
you [whereas before it didn't] as well as, and more importantly something
doesn't work [that did before].  I would really appreciate it if those with
other network stacks could test as well.

Thank you,
Jeremy

the latest version is found on the gits

i need help testing the stuff you mentioned no error levels yet

https://git.gay/sparky4/fdnpkg16/raw/branch/main/fdnpkg16.zip


On 5/30/26 6:56 AM, Jerome Shidel via Freedos-user wrote:
> Hi,
>
>> On May 28, 2026, at 7:23 PM, victoria crenshaw via Freedos-user 
>> <fre...@li...> wrote:
>>
>> https://git.gay/sparky4/fdnpkg16/releases/download/0.99.8254b/fdnpkg16.zip
>>
>> https://4ch.mooo.com/freedos/repos/1.4/html/en/net/fdnpkg16/
>>
>>
>> get it here or use fdnpkg16.exe to update to it
>>
>>
>> change log:
>>
>>
>> * 0.99.8254b: fixed a bug with downloading a file not existing in 
>> repository
>> * added a feature when downloading a package it will ask if the user 
>> wants to override the existing file on disk with same name.
>> * the documented features not in help are in the help now.
>
> I had a few minutes to test out the new/improved features.
>
> It has improved a lot over previous versions.
>
> I did not notice any major issues with the new changes.
>
> However, there were some things which I think could improve user 
> experience.
>
> 1) When using /DL (download package) or /DU (download updates), it 
> first downloads the package. Then, if a file already exists with the 
> same name, it prompts to Overwrite. I think it would be better to 
> check for the conflicting file name before downloading. That way, if 
> the user does not want to overwrite the local file, they do not waste 
> time downloading it. Sometimes, these files are pretty big and can 
> take several minutes for a download to complete.
>
> 2) It would be nice to provide the option to “Abort”, when a 
> conflicting file name already exists.
>
> 3) When downloading a package or available updates, it shows the 
> message “An update was found… Update in progress”. It should really 
> say “Download in progress” or since the next line says “Downloading…”, 
> that “Update in progress” could simply be removed when just downloading.
>
> 4) After downloading a package and wanting to update it, the command 
> to do this could be a little confusing to the end user. For example, 
> the was an update to DOSLFN. After it was downloaded, a user may thing 
> running “fdnpkg16 update doslfn.zip” would update it. But, that will 
> issue an error message that “DOSLFN.ZIP is not installed". So, they 
> may then try to run “fdnpkg16 install doslfn.zip” which shows the 
> error “DOSLFN is already installed! You may want to use ‘update’ action.”
> This may confuse a user who does not know about the RI option to 
> reinstall a package.
>
> 5) After downloading all of the updates, it would be nice be able to 
> update them all at once. While they could be done one at a time, if it 
> has been a while since the packages were updated, there can be a lot 
> of them. For example, this machine had 13 updates. It can be tedious 
> to do one at a time. Using something like “fdnpkg16 ri *.zip” would be 
> awesome when there are a couple dozen packages to (re)install or update.
>
> :-)
>
>
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user

Exactly the same result.
My problem is that when I use the disk intensively—for example, when formatting a partition or copying a directory with a large number of files using the xcopy command—the disk hangs and causes an error. I have also seen sector errors during these operations sometimes.
It makes the system unreliable, so I've decided not to use them.


> El 3 jun 2026, a las 22:22, Louis Santillan <lps...@gm...> escribió:
> 
> Oh!!! That is so interesting.  If you use the stock FreeDOS 1.4 or
> Interim USB drive images, do you get the same result?
> 
> On Tue, Jun 2, 2026 at 11:48 PM Paco Oviedo via Freedos-user
> <fre...@li...> wrote:
>> 
>> Disk 1 is the Ventoy USB drive, and Disk 2 is the internal NVME disk.
>> 
>> 
>> 
>>> El 3 jun 2026, a las 5:21, Louis Santillan <lps...@gm...> escribió:
>>> 
>>> Oh....I'd love to see a pic of that.
>>> 
>>> If you boot FreeDOS from Ventoy using Legacy+CSM and do a "fdisk
>>> /status", what does it show?
>>> 
>>> On Tue, Jun 2, 2026 at 2:12 PM Paco Oviedo via Freedos-user
>>> <fre...@li...> wrote:
>>>> 
>>>> 
>>>> 
>>>> El 2 jun 2026, a las 16:14, Louis Santillan <lps...@gm...> escribió:
>>>> 
>>>> Generally speaking, NVMe storage drives are not accessible via BIOS
>>>> calls (they need to be communicated with via PCIe or UEFI).  FreeDOS
>>>> is only able to access storage mediums accessible via BIOS calls.  I'm
>>>> curious how you got your BIOS to make the NVMe drive visible to
>>>> FreeDOS in your initial install attempt.
>>>> 
>>>> I modified a Dell Optiplex 9020 to boot off NVMe but the drive isn't
>>>> visible to my FreeDOS USB install drive.  However, Linux will install
>>>> and boot off the NVMe.
>>>> 
>>>> 
>>>> Nothing special. I just turned on Legacy and CSM in the BIOS Startup menu, and FreeDOS found the NVMe disk right away.
>>>> I booted the FreeDOS installer using a Ventoy USB flash drive.
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Freedos-user mailing list
>>>> Fre...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
>> _______________________________________________
>> Freedos-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freedos-user

about this i did fix this specific thing with the english version but 
now i have 28 files to update i need some help with these translations


On 5/30/26 6:56 AM, Jerome Shidel via Freedos-user wrote:

> 4) After downloading a package and wanting to update it, the command 
> to do this could be a little confusing to the end user. For example, 
> the was an update to DOSLFN. After it was downloaded, a user may thing 
> running “fdnpkg16 update doslfn.zip” would update it. But, that will 
> issue an error message that “DOSLFN.ZIP is not installed". So, they 
> may then try to run “fdnpkg16 install doslfn.zip” which shows the 
> error “DOSLFN is already installed! You may want to use ‘update’ action.”
> This may confuse a user who does not know about the RI option to 
> reinstall a package.

Oh!!! That is so interesting.  If you use the stock FreeDOS 1.4 or
Interim USB drive images, do you get the same result?

On Tue, Jun 2, 2026 at 11:48 PM Paco Oviedo via Freedos-user
<fre...@li...> wrote:
>
> Disk 1 is the Ventoy USB drive, and Disk 2 is the internal NVME disk.
>
>
>
> > El 3 jun 2026, a las 5:21, Louis Santillan <lps...@gm...> escribió:
> >
> > Oh....I'd love to see a pic of that.
> >
> > If you boot FreeDOS from Ventoy using Legacy+CSM and do a "fdisk
> > /status", what does it show?
> >
> > On Tue, Jun 2, 2026 at 2:12 PM Paco Oviedo via Freedos-user
> > <fre...@li...> wrote:
> >>
> >>
> >>
> >> El 2 jun 2026, a las 16:14, Louis Santillan <lps...@gm...> escribió:
> >>
> >> Generally speaking, NVMe storage drives are not accessible via BIOS
> >> calls (they need to be communicated with via PCIe or UEFI).  FreeDOS
> >> is only able to access storage mediums accessible via BIOS calls.  I'm
> >> curious how you got your BIOS to make the NVMe drive visible to
> >> FreeDOS in your initial install attempt.
> >>
> >> I modified a Dell Optiplex 9020 to boot off NVMe but the drive isn't
> >> visible to my FreeDOS USB install drive.  However, Linux will install
> >> and boot off the NVMe.
> >>
> >>
> >> Nothing special. I just turned on Legacy and CSM in the BIOS Startup menu, and FreeDOS found the NVMe disk right away.
> >> I booted the FreeDOS installer using a Ventoy USB flash drive.
> >>
> >>
> >> _______________________________________________
> >> Freedos-user mailing list
> >> Fre...@li...
> >> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user