You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(60) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(280) |
Feb
(411) |
Mar
(455) |
Apr
(367) |
May
(125) |
Jun
(155) |
Jul
(266) |
Aug
(131) |
Sep
(223) |
Oct
(76) |
Nov
(103) |
Dec
(132) |
2005 |
Jan
(70) |
Feb
(113) |
Mar
(57) |
Apr
(38) |
May
(110) |
Jun
(74) |
Jul
(365) |
Aug
(198) |
Sep
(116) |
Oct
(119) |
Nov
(184) |
Dec
(55) |
2006 |
Jan
(97) |
Feb
(70) |
Mar
(51) |
Apr
(16) |
May
(46) |
Jun
(176) |
Jul
(305) |
Aug
(427) |
Sep
(223) |
Oct
(121) |
Nov
(112) |
Dec
(48) |
2007 |
Jan
(16) |
Feb
(19) |
Mar
(67) |
Apr
(69) |
May
(48) |
Jun
(35) |
Jul
(26) |
Aug
(44) |
Sep
(33) |
Oct
(86) |
Nov
(15) |
Dec
(28) |
2008 |
Jan
(120) |
Feb
(7) |
Mar
(76) |
Apr
(47) |
May
(41) |
Jun
(24) |
Jul
(25) |
Aug
(34) |
Sep
(58) |
Oct
(7) |
Nov
(16) |
Dec
(40) |
2009 |
Jan
(17) |
Feb
(53) |
Mar
(121) |
Apr
(69) |
May
(28) |
Jun
(39) |
Jul
(12) |
Aug
(22) |
Sep
(25) |
Oct
(15) |
Nov
(53) |
Dec
(9) |
2010 |
Jan
(10) |
Feb
(30) |
Mar
(10) |
Apr
(44) |
May
(36) |
Jun
(14) |
Jul
(21) |
Aug
(19) |
Sep
(1) |
Oct
(6) |
Nov
(22) |
Dec
(11) |
2011 |
Jan
(10) |
Feb
(45) |
Mar
(6) |
Apr
(7) |
May
(38) |
Jun
(40) |
Jul
(248) |
Aug
(150) |
Sep
(124) |
Oct
(40) |
Nov
(36) |
Dec
(57) |
2012 |
Jan
(64) |
Feb
(22) |
Mar
(14) |
Apr
(20) |
May
(54) |
Jun
(27) |
Jul
(36) |
Aug
(63) |
Sep
(11) |
Oct
(4) |
Nov
(13) |
Dec
(33) |
2013 |
Jan
(49) |
Feb
(36) |
Mar
(8) |
Apr
(17) |
May
(34) |
Jun
(24) |
Jul
(45) |
Aug
(4) |
Sep
(14) |
Oct
(8) |
Nov
(3) |
Dec
(16) |
2014 |
Jan
(32) |
Feb
(10) |
Mar
(41) |
Apr
(35) |
May
(23) |
Jun
(9) |
Jul
(110) |
Aug
(9) |
Sep
(12) |
Oct
(6) |
Nov
(16) |
Dec
(77) |
2015 |
Jan
(249) |
Feb
(9) |
Mar
(95) |
Apr
(28) |
May
(126) |
Jun
(151) |
Jul
(11) |
Aug
(35) |
Sep
(258) |
Oct
(198) |
Nov
(123) |
Dec
(186) |
2016 |
Jan
(166) |
Feb
(100) |
Mar
(11) |
Apr
(4) |
May
(24) |
Jun
(13) |
Jul
(34) |
Aug
(18) |
Sep
(8) |
Oct
(49) |
Nov
(69) |
Dec
(33) |
2017 |
Jan
(20) |
Feb
(29) |
Mar
(2) |
Apr
(4) |
May
(33) |
Jun
(32) |
Jul
(16) |
Aug
(8) |
Sep
|
Oct
(67) |
Nov
(39) |
Dec
(4) |
2018 |
Jan
(29) |
Feb
(42) |
Mar
(2) |
Apr
(5) |
May
(13) |
Jun
(24) |
Jul
(160) |
Aug
(76) |
Sep
(64) |
Oct
(42) |
Nov
(47) |
Dec
(32) |
2019 |
Jan
(33) |
Feb
(29) |
Mar
(36) |
Apr
(11) |
May
(11) |
Jun
(18) |
Jul
(20) |
Aug
(11) |
Sep
(7) |
Oct
(16) |
Nov
(3) |
Dec
(20) |
2020 |
Jan
(10) |
Feb
|
Mar
(10) |
Apr
(13) |
May
(53) |
Jun
(26) |
Jul
(8) |
Aug
(20) |
Sep
(8) |
Oct
(60) |
Nov
(93) |
Dec
(119) |
2021 |
Jan
(20) |
Feb
(54) |
Mar
(26) |
Apr
(17) |
May
(200) |
Jun
(231) |
Jul
(124) |
Aug
(100) |
Sep
(25) |
Oct
(18) |
Nov
(17) |
Dec
(93) |
2022 |
Jan
(129) |
Feb
(59) |
Mar
(58) |
Apr
(70) |
May
(39) |
Jun
(22) |
Jul
(83) |
Aug
(110) |
Sep
(65) |
Oct
(80) |
Nov
(42) |
Dec
(19) |
2023 |
Jan
(145) |
Feb
(118) |
Mar
(179) |
Apr
(76) |
May
(46) |
Jun
(67) |
Jul
(76) |
Aug
(69) |
Sep
(31) |
Oct
(52) |
Nov
(82) |
Dec
(46) |
2024 |
Jan
(51) |
Feb
(97) |
Mar
(47) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jim H. <jh...@fr...> - 2024-03-10 15:56:29
|
I'll start the get-together in a few minutes, but here's the URL for anyone who needs it: FreeDOS virtual get-together (social) Sunday, March 10 · 11:00am – 12:30pm Time zone: America/Chicago Google Meet joining info Video call link: https://meet.google.com/eua-spwn-euy Or dial: (US) +1 347-305-6319 PIN: 692 124 151# More phone numbers: https://tel.meet/eua-spwn-euy?pin=5735754726737 |
From: Jim H. <jh...@fr...> - 2024-03-10 14:00:10
|
Hi everyone Don't forget about this morning's virtual get-together! We are on Daylight Saving Time in the US. It's 9:00am now, so that means the meeting is in two hours from now (11:00-12:00). See you then! |
From: Mercury T. <mer...@pr...> - 2024-03-09 21:19:46
|
Good to know that (Free)DOS has lspci support. Thanks for the info! And now, for my two cents lol My ListPCI application (https://mercurycoding.com/downloads.html) does essentially the same thing, although it shows only the manufacturer and device type, not the specific device name; e.g. "Intel Corporation IDE Mass Storage Controller" and not "Intel Corporation 82371AB/EB/MB PIIX4 IDE". This has proven to be good enough for my purposes (and hopefully other users' as well!) and results in a much smaller binary - 52.2 kB versus lspci's 191.5 kB. Sent with [Proton Mail](https://proton.me/) secure email. On Saturday, March 9th, 2024 at 8:14 AM, Bernd Böckmann via Freedos-devel <fre...@li...> wrote: > Hi Pali, > > I will forward your message regarding lspci to the FreeDOS mailinglist. Thanks for sharing this information! > > Greetings, Bernd > >> Anfang der weitergeleiteten Nachricht: >> >> Von: Pali Rohár <pa...@ke...> >> Betreff: lspci (pciutils) for freedos >> >> Datum: 9. März 2024 um 12:49:53 MEZ >> An: Bernd Boeckmann <ber...@bo...> >> >> Hello, >> >> I read the freedos wiki page contribute >> https://freedos.sourceforge.io/wiki/index.php/Contribute >> >> and I would like to let you know that the "lspci" tool known from the >> linux which lists and prints information about all PCI devices connected >> in the system, works also on freedos and the last version now has >> pre-compiled binaries in the pciutils project page. They are in windows >> download section, but are compiled with DJGPP toolchain. >> http://mj.ucw.cz/sw/pciutils/ >> >> I saw more questions from users if there is a lspci-like tool for >> freedos to list PCI devices, so I think that the original lspci can be >> useful for freedos. Would you consider including it into distribution CD? >> Note that pciutils library is used by flashrom which is already present. >> >> Pali |
From: <ro...@gm...> - 2024-03-09 13:54:18
|
Eric Auer via Freedos-devel <fre...@li...> wrote: > > > Hi! > > LSPCI relies on a rather large list of known PCI ID, > which is why I made PCISLEEP long ago: It just has > a small list of known vendors and types, to keep the > installation small :-) It also experiments with PCI > based standby and suspend modes, including VGA ones. > > But of course, having a full LSPCI for DOS would not > hurt either, for more detailed information :-) PCI.IDS is so large that can't even able to put it on a standard 1.44MB floppy uncompressed! > > Eric > > PS: PCISLEEP is written in Assembly language. For a > DOS version of LSPCI, I suggest using BIOS calls or > raw I/O and keeping the rest in original LSPCI style. > > > > > Hi Pali, > > > > I will forward your message regarding lspci to the FreeDOS mailinglist. Thanks for sharing this information! > > > > Greetings, Bernd > > > >> Anfang der weitergeleiteten Nachricht: > >> > >> Von: Pali Rohár <pa...@ke...> > >> Betreff: lspci (pciutils) for freedos > >> Datum: 9. März 2024 um 12:49:53 MEZ > >> An: Bernd Boeckmann <ber...@bo...> > >> > >> Hello, > >> > >> I read the freedos wiki page contribute > >> https://freedos.sourceforge.io/wiki/index.php/Contribute > >> > >> and I would like to let you know that the "lspci" tool known from the > >> linux which lists and prints information about all PCI devices connected > >> in the system, works also on freedos and the last version now has > >> pre-compiled binaries in the pciutils project page. They are in windows > >> download section, but are compiled with DJGPP toolchain. > >> http://mj.ucw.cz/sw/pciutils/ > >> > >> I saw more questions from users if there is a lspci-like tool for > >> freedos to list PCI devices, so I think that the original lspci can be > >> useful for freedos. Would you consider including it into distribution CD? > >> Note that pciutils library is used by flashrom which is already present. > >> > >> Pali > > > > > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |
From: Eric A. <e....@jp...> - 2024-03-09 13:20:59
|
Hi! LSPCI relies on a rather large list of known PCI ID, which is why I made PCISLEEP long ago: It just has a small list of known vendors and types, to keep the installation small :-) It also experiments with PCI based standby and suspend modes, including VGA ones. But of course, having a full LSPCI for DOS would not hurt either, for more detailed information :-) Eric PS: PCISLEEP is written in Assembly language. For a DOS version of LSPCI, I suggest using BIOS calls or raw I/O and keeping the rest in original LSPCI style. > Hi Pali, > > I will forward your message regarding lspci to the FreeDOS mailinglist. Thanks for sharing this information! > > Greetings, Bernd > >> Anfang der weitergeleiteten Nachricht: >> >> Von: Pali Rohár <pa...@ke...> >> Betreff: lspci (pciutils) for freedos >> Datum: 9. März 2024 um 12:49:53 MEZ >> An: Bernd Boeckmann <ber...@bo...> >> >> Hello, >> >> I read the freedos wiki page contribute >> https://freedos.sourceforge.io/wiki/index.php/Contribute >> >> and I would like to let you know that the "lspci" tool known from the >> linux which lists and prints information about all PCI devices connected >> in the system, works also on freedos and the last version now has >> pre-compiled binaries in the pciutils project page. They are in windows >> download section, but are compiled with DJGPP toolchain. >> http://mj.ucw.cz/sw/pciutils/ >> >> I saw more questions from users if there is a lspci-like tool for >> freedos to list PCI devices, so I think that the original lspci can be >> useful for freedos. Would you consider including it into distribution CD? >> Note that pciutils library is used by flashrom which is already present. >> >> Pali |
From: Bernd B. <ber...@bo...> - 2024-03-09 13:15:02
|
Hi Pali, I will forward your message regarding lspci to the FreeDOS mailinglist. Thanks for sharing this information! Greetings, Bernd > Anfang der weitergeleiteten Nachricht: > > Von: Pali Rohár <pa...@ke...> > Betreff: lspci (pciutils) for freedos > Datum: 9. März 2024 um 12:49:53 MEZ > An: Bernd Boeckmann <ber...@bo...> > > Hello, > > I read the freedos wiki page contribute > https://freedos.sourceforge.io/wiki/index.php/Contribute > > and I would like to let you know that the "lspci" tool known from the > linux which lists and prints information about all PCI devices connected > in the system, works also on freedos and the last version now has > pre-compiled binaries in the pciutils project page. They are in windows > download section, but are compiled with DJGPP toolchain. > http://mj.ucw.cz/sw/pciutils/ > > I saw more questions from users if there is a lspci-like tool for > freedos to list PCI devices, so I think that the original lspci can be > useful for freedos. Would you consider including it into distribution CD? > Note that pciutils library is used by flashrom which is already present. > > Pali |
From: Jim H. <jh...@fr...> - 2024-03-08 22:19:20
|
A quick status on migrating the wiki: I set up a new Wikimedia instance on a new wiki.freedos.org host this week, and yesterday I started to copy content from the old wiki into the new wiki. This is a copy/paste exercise for a few reasons that I've explained in another email, but here's a summary: [begin summary] Background: Long ago, SourceForge set up a shared Mediawiki environment for all projects hosted at SF. Every project used the same wiki system but had a different prefix. All SF users had a wiki login by default. Later, SF decided to stop hosting a shared wiki, so they made a data export available to every project and provided instructions to set up your own Mediawiki. We did that on the SF web host. In late-ish 2023, SF's website update meant our wiki can't use a stylesheet. I can't blame them, the wiki software was out of date (very difficult to update a website hosted at SF). I could export the data from SF and import it into a new wiki, but that would import *all* of the wiki users. And the SF database includes *all* SF users. I don't want to import all those unneeded accounts, so I'm setting up a fresh wiki. There aren't a ton of pages in our wiki, so I'm copy/pasting everything. [end summary] SF is planning another website update on March 18. There's no reason to think the old SF web hosting will stop working, but I am making that a self-imposed deadline; I want to get all of our wiki content moved by March 18. I think I'll make that deadline. So far, it's been very do-able. I made a lot of content updates on the "front" page of the wiki and the first few other pages I moved over. I think I've finished the pages that needed the most updating (out of date) so the most recent pages I've moved were a copy/paste exercise with very minimal edits for any obvious spelling/grammar. Dreamhost (the web hosting company) has very strict anti-spam measures in place, so sometimes I run against that when pasting long blocks of very technical text that might include commands. I think that's triggering the spam protection so those pages are taking more effort to get in (doing it in parts seems to help) but most are just copy/paste. As part of this exercise, I'm also making all the pages look more consistent. That usually means pages need to have a 1-line summary at the top, rather than starting with a long block of text. I'm also adding more links to things that should be in the wiki. Some of those will get "filled in" as part of the migration, others will be new pages. So if you see red links, don't panic. That's what a wiki is for. If you want to see the new wiki, it is at https://wiki.freedos.org/w/ (The "w" part will go away eventually, but for now it's basically a "hidden unless you know it's there" location.) Once I get all the content moved over, I'll set up wiki accounts for anyone who wants them. Jim |
From: Jim H. <jh...@fr...> - 2024-03-08 13:18:27
|
On Thu, Mar 7, 2024 at 3:53 PM Jim Hall <jh...@fr...> wrote: > > Just wanted to share that I'm (finally) migrating the FreeDOS Wiki > content. I've set up a new wiki instance on a new server, and I'm > going through the list of pages on the old wiki, and copy/pasting the > content on the new wiki. > [..] > *Unrelated: The shared hosting service is currently experiencing an > outage, so the website (and new wiki) is down. It should be working > again soon. I think we can assume this is a coincidence to my working > on the new wiki. :-) Turns out, not unrelated, and not a coincidence. The server has an uptime of over 49 days, so it wasn't a server failure. They looked into other causes for me. Short version: I had put in a few pages before I discovered the "Live preview" feature of the Wiki. I assumed it was a client-side visual editor or preview (it is not). After effectively spamming the server with traffic (new preview after I keep typing) the server temporarily blocked my IP. That's why all my websites on their shared hosting went "down." It resolved on its own when the block was lifted. So that was self-inflicted. I'll stop using "Live preview" but they've added my IP to a whitelist anyway. |
From: Mercury T. <mer...@pr...> - 2024-03-07 22:10:18
|
Nice, the new site is working for me. :) One (minor) thing I would suggest, however, is that the What's New items should each at the bottom span the entire width of the window in all cases. The do behave this way on small screens (or in small windows) but on large ones they show up side-by-side. In my mind, they have better logical flow when there's a single item per line. Sent with [Proton Mail](https://proton.me/) secure email. On Wednesday, March 6th, 2024 at 10:37 AM, Jim Hall via Freedos-devel fre...@li... wrote: > FYI that the www.freedos.org website has moved to new hosting. It's > still at the same website hosting company, but on a new server. (This > was the web hosting company doing a planned replacement of the old > hardware.) Things look like they have moved over okay, I don't see any > issues. > > They are keeping the old web server running for a while, to respond to > any requests on the old server (for example, with the old hostname in > your DNS cache). I've posted the announcement about the upcoming > get-together on both servers. > > If you're curious if you're accessing the new server or the old one, I > added this temporary file on the new server. It tells you if you are > using the new server or the old one: > https://www.freedos.org/new.txt > > If you can see the contents of that file, you're using the new web > server. If you get a "404" error, then you are using the old web > server (try again in a few days). > > Jim > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |
From: Jim H. <jh...@fr...> - 2024-03-07 21:54:09
|
Just wanted to share that I'm (finally) migrating the FreeDOS Wiki content. I've set up a new wiki instance on a new server, and I'm going through the list of pages on the old wiki, and copy/pasting the content on the new wiki. That sounds like a lot of work, but a lot of the content needs to be updated anyway, so this is a good opportunity to do that. -Jim *Unrelated: The shared hosting service is currently experiencing an outage, so the website (and new wiki) is down. It should be working again soon. I think we can assume this is a coincidence to my working on the new wiki. :-) |
From: Ralf Q. <fre...@gm...> - 2024-03-06 20:19:54
|
On 3/6/2024 12:08 PM, Bernd Böckmann via Freedos-devel wrote: > > On 06.03.2024 20:52, Ralf Quint via Freedos-devel wrote: >> Seems I am hitting the new server... 😎 > > Does anyone know what happened to bttr? Its down with http 500. Though > error page is graphically nice! Nope. But it seems it is only the main web site, the "DOS ain't dead forum" (which I mostly visit, if I remember a working password... :( ) seems to be just fine. Might wanna try and post a message in there to see what's up... An http error 500 is exactly what it says in the error message, a(ny) internal server error, which can be anything from no RAM, no/bad drive space, bad update, etc... Ralf |
From: Bernd B. <ber...@bo...> - 2024-03-06 20:08:29
|
On 06.03.2024 20:52, Ralf Quint via Freedos-devel wrote: > Seems I am hitting the new server... 😎 Does anyone know what happened to bttr? Its down with http 500. Though error page is graphically nice! Bernd |
From: Ralf Q. <fre...@gm...> - 2024-03-06 19:53:01
|
On 3/6/2024 7:37 AM, Jim Hall via Freedos-devel wrote: > If you're curious if you're accessing the new server or the old one, I > added this temporary file on the new server. It tells you if you are > using the new server or the old one: > https://www.freedos.org/new.txt > Seems I am hitting the new server... 😎 Ralf |
From: Jim H. <jh...@fr...> - 2024-03-06 15:38:14
|
FYI that the www.freedos.org website has moved to new hosting. It's still at the same website hosting company, but on a new server. (This was the web hosting company doing a planned replacement of the old hardware.) Things look like they have moved over okay, I don't see any issues. They are keeping the old web server running for a while, to respond to any requests on the old server (for example, with the old hostname in your DNS cache). I've posted the announcement about the upcoming get-together on both servers. If you're curious if you're accessing the new server or the old one, I added this temporary file on the new server. It tells you if you are using the new server or the old one: https://www.freedos.org/new.txt If you can see the contents of that file, you're using the new web server. If you get a "404" error, then you are using the old web server (try again in a few days). Jim |
From: Jim H. <jh...@fr...> - 2024-03-06 15:16:25
|
Hi everyone! I wanted to send a reminder of our upcoming FreeDOS virtual get-together on Sunday, March 10. Same time as usual: from 11am to noon US/Central (use your favorite timezone converter to find your local time). However, note that March 10 is also the start of US Daylight Saving Time, so clocks will be "ahead" one hour. If your region doesn't observe Daylight Saving Time, or has a different changeover date, please be aware of the time issue. I'll send an email to the list with the URL to join before the meeting starts. We will do the meeting again with Google Meet, since that has worked out well. We alternate topics on the get-together. Last month was 'technical' topics, this month is social time. We may still talk about technical items, but mostly this is an opportunity to get to know folks as more than just an email address. See you then! Jim |
From: <je...@sh...> - 2024-03-02 04:50:32
|
Attached is my proposed revisions to FDAUTO. |
From: <je...@sh...> - 2024-03-02 04:49:18
|
Hi Jim and All, This got me thinking about the startup files a little more. I realized there are several additional factors that were present during their development that are simply no longer relevant. One such factor was the simultaneous development and adjustments made between the installed config files and those used by the boot media(s). During the initial development and tests, bits and pieces would move back and forth between them adding additional complexity. Plus, the need for developing numerous skews for multiple platforms while developing the installers at the same time. That time has long since passed. The config files that get installed have nothing at all to do with the config files used to boot the various install media. The installer(s) base the config files installed on a decision hierarchy for the detected platform. This means we can simplify the installed config files even further by eliminating the CPU testing in them. At present these are the possible different config files installed. DOSBox - Dummy CFG, Platform specific AUTO. VirtualBox - Platform Specific CFG & AUTO. VirtualBox really doesn’t like the option 1 in the default CFG file, it only provides 4 boot options. Also (at least for me), VirtualBox will lockup when running FreeDOS after a few minutes when FDAPM is not loaded. So, I think “#4 - Safe Mode” should be removed or at lead have FDAPM loaded regardless. 286 - Platform Specific CFG, Default AUTO. (3 boot options, XMS Support, With & Without Drivers) 186 - Platform Specific CFG, Default AUTO. (2 boot options, With and without Drivers) 8086/8088 - Platform Specific CFG, Default AUTO. (2 boot options, With and Without Drivers) All others - Default CFG & Default AUTO (5 boot options) Looking at the current Default AUTO, it is missing a a test for option 3 (No Drivers) when running on a 286. I think the end user will be best served by getting rid of the platform tests in the installed config files. We can simple start with the default CFG & AUTO files. Then reduce/adjust those files for the specific platforms. Only testing for specific boot options and all CPU related items can be static. To the above list of different CFG & AUTO files, the only thing that would change would be custom versions of AUTO files for 286, 186 and 8086/88. And those would only need to be simplified versions of the default AUTO. Starting with the 386+ version you have been working on, we could do this… (I will also be sending a revised version of FDAUTO.TXT with my suggestions) > On Mar 1, 2024, at 7:16 PM, Jim Hall via Freedos-devel <fre...@li...> wrote: > [..] >> @ECHO OFF >> REM - Updated AUTOEXEC file REM - For i386 CPU or better hardware. >> >> REM - set basic environment >> >> set DOSDRV=C: >> set DOSDIR=%DOSDRV%\FREEDOS >> >> path %DOSDIR%\BIN >> if not exist %DOSDIR%\LINKS\NUL goto NOLINKS >> path %PATH%;%DOSDIR%\LINKS >> :NOLINKS >> >> set NLSPATH=%DOSDIR%\NLS >> set HELPPATH=%DOSDIR%\HELP >> >> set TEMP=%DOSDIR%\TEMP >> set TMP=%TEMP% >> >> if "%CONFIG%"=="5" goto END Side note, on VirtualBox this is option 4. >> >> set OS_NAME=FreeDOS >> set OS_VERSION=T2403 >> >> REM - cfgfile and autofile might be deprecated in future >> >> set CFGFILE=%DOSDRV%\FDCONFIG.SYS >> set AUTOFILE=%DOSDRV%\FDAUTO.BAT We can change this to simply… set AUTOFILE=%0 >> alias cfg=edit %CFGFILE% >> alias auto=edit %AUTOFILE% >> Remove this CPU Section! >> REM - detect CPU, load CPU-specific configs >> >> if not exist %DOSDIR%\BIN\VINFO.COM goto ENDCPU >> %DOSDIR%\BIN\VINFO.COM /m >> if errorlevel 3 goto CPU386 >> if errorlevel 2 goto CPU286 >> goto ENDCPU >> >> :CPU286 >> >> fdapm APMDOS >> ctmouse >> >> goto ENDCPU >> >> :CPU386 >> if "%CONFIG%"=="4" goto CPU286 >> {end of removed} if “%CONFIG%” == “4” goto DOSLOW >> lh fdapm APMDOS >> lh ctmouse >> REM lh share >> >> if not exist %DOSDIR%\BIN\DOSLFN.CON goto NOLFN >> lh %DOSDIR%\BIN\DOSLFN.CON >> REM - Add other stuff here once LFN is loaded.. >> :NOLFN >> >> if not exist %DOSDIR%\BIN\CDROM.BAT goto NOCDROM >> call %DOSDIR%\BIN\CDROM.BAT >> REM - Add other stuff here once CDROM is loaded.. >> :NOCDROM >> >> :ENDCPU Moving ENDCPU a little later. >> >> REM - load other configs using external BAT files >> >> if not exist %DOSDIR%\BIN\FDNET.BAT goto NONET >> call %DOSDIR%\BIN\FDNET.BAT >> REM - Add other stuff here once FDNET is loaded.. >> :NONET goto ENDCPU :DOSLOW REM - If we are loading some drivers low, we are probably having REM - Boot problems and may want to skip using FDAPM, LFN, REM - CDROM and NETWORKING. Just load the mouse driver. ctmouse :ENDCPU >> >> if not exist %DOSDIR%\BIN\FDASSIST.BAT goto NOASSIST >> call %DOSDIR%\BIN\FDASSIST.BAT >> :NOASSIST >> I really think “MEM /C /N” should before the welcome message. No drivers or TSRs are loaded by WELCOME.BAT and the amount of memory available will not change. Side note, the message the displays “CD-ROM configured as ?: drive (FDCDX001)” is performed by calling "CDROM.BAT status” which is not present here. Also, when the system does not configure a CD drive (either by boot option omission, or initialization failure), it displays “CD-ROM not configured" if not exist %DOSDIR%\BIN\CDROM.BAT goto NOCDSTATUS call %DOSDIR%\BIN\CDROM.BAT status :NOCDSTATUS >> if not exist %DOSDIR%\BIN\WELCOME.BAT goto NOHELLO >> call %DOSDIR%\BIN\WELCOME.BAT >> :NOHELLO >> >> MEM /C /N I think this should not appear after Welcome to FreeDOS, type Help, etc. >> >> REM - local settings >> >> set BLASTER=A220 I5 D1 H5 P330 >> set DIRCMD=/O:GNE /Y >> set COPYCMD=/-Y >> >> REM nlsfunc %DOSDIR%\BIN\COUNTRY.SYS >> REM display CON=(EGA,858,2) >> REM mode CON CP PREP=((858) %DOSDIR%\CPI\EGA.CPX) >> REM keyb US,858,%DOSDIR%\BIN\KEYBOARD.SYS >> REM chcp 858 >> REM mkeyb UK Not sure about the local stuff being loaded after the welcome messages. Personally, I feel that the very last text presented to the user should be the Cd-Drive letter and the Welcome, help and done processing messages. But, maybe thats just me. Also, I just realized there are no LANG or TZ settings. There are a couple programs that complain when TZ is not set. But, really need the LANG setting and very early in the config. >> >> alias reset=fdisk /reboot >> alias reboot=fdapm warmboot >> alias halt=fdapm poweroff >> alias shutdown=fdapm poweroff >> >> :END > > > > Personally, I'm not a fan of cfgfile and autofile since the user could > always rename FDCONFIG.SYS in favor of using CONFIG.SYS .. but FDAUTO > will still report "Done processing startup files C:\FDCONFIG.SYS and > C:\FDAUTO.BAT" (this is actually printed in WELCOME.BAT). So I've left > a comment in the updated FDAUTO that "cfgfile and autofile might be > deprecated in future". > :-) I personally never use the cfgfile or autofile variables or the cfg/auto aliases. But, using the AUTOFILE=%0 will solve the user file renaming. Changing there "set CFGFILE" to: REM FreeDOS can use CONFIG.SYS. But, it prefers FDCONFIG.SYS. set CFGFILE=%DOSDRV%\CONFIG.SYS if exist %DOSDRV%\FDCONFIG.SYS set CFGFILE=%DOSDRV%\FDCONFIG.SYS should be sufficient to handle renaming of that file as well. > > Jim > Jerome > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |
From: Jim H. <jh...@fr...> - 2024-03-02 00:33:16
|
And I just saw the typo in DOSLFN.CON ... should be DOSLFN.COM I don't have LFN loaded, so I didn't see this come up. :-P Jerome: If you accept this for the next test release, please fix my typo. :-) |
From: Jim H. <jh...@fr...> - 2024-03-02 00:20:10
|
Resending with FDAUTO.BAT as a file attachment (renamed FDAUTO.TXT) so it's easier to try out the config. Jim |
From: Jim H. <jh...@fr...> - 2024-03-02 00:16:28
|
Hi everyone The new T2403 release prompted me to finish updating the FDAUTO.BAT file. Quick background: This started because I was looking to prevent the CTMOUSE driver from loading .. but it was a bit hard to read the FDAUTO file. So I simplified it on my end. This should do everything the previous FDAUTO did - I just moved things around. Interestingly, I also freed up a tiny amount (160 bytes) of memory. Here's the MEM output from a fresh boot before I made changes: > Memory Type Total Used Free > ---------------- -------- -------- -------- > Conventional 639K 33K 606K > Upper 0K 0K 0K > Reserved 385K 385K 0K > Extended (XMS) 31,616K 433K 31,183K > ---------------- -------- -------- -------- > Total memory 32,640K 851K 31,789K > > Total under 1 MB 639K 33K 606K > > Total Expanded (EMS) 8,816K (9,027,584 bytes) > Free Expanded (EMS) 8,192K (8,388,608 bytes) > > Largest executable program size 605K (619,552 bytes) > FreeDOS is resident in the high memory area. And here's the MEM output from a fresh boot with the new FDAUTO file: > Memory Type Total Used Free > ---------------- -------- -------- -------- > Conventional 639K 33K 606K > Upper 0K 0K 0K > Reserved 385K 385K 0K > Extended (XMS) 31,616K 433K 31,183K > ---------------- -------- -------- -------- > Total memory 32,640K 851K 31,789K > > Total under 1 MB 639K 33K 606K > > Total Expanded (EMS) 8,816K (9,027,584 bytes) > Free Expanded (EMS) 8,192K (8,388,608 bytes) > > Largest executable program size 605K (619,712 bytes) > FreeDOS is resident in the high memory area. 160 bytes isn't much, but I thought it was interesting. :-) The original FDAUTO was 98 lines, my cleaned up FDAUTO file is 101 lines but I think it's easier to read. The general idea is to put "system" stuff at the top, and "user" stuff at the end. In summary, it sets a few env variables, then loads CPU-specific configs (for example: LFN and CDROM on 386+, ..) then loads the "supporting" BAT files if they are there. I moved the user's local settings (BLASTER, DIRCMD, aliases, ..) to the end of the file: > @ECHO OFF > REM - Updated AUTOEXEC file > > REM - set basic environment > > set DOSDRV=C: > set DOSDIR=%DOSDRV%\FREEDOS > > path %DOSDIR%\BIN > if not exist %DOSDIR%\LINKS\NUL goto NOLINKS > path %PATH%;%DOSDIR%\LINKS > :NOLINKS > > set NLSPATH=%DOSDIR%\NLS > set HELPPATH=%DOSDIR%\HELP > > set TEMP=%DOSDIR%\TEMP > set TMP=%TEMP% > > if "%CONFIG%"=="5" goto END > > set OS_NAME=FreeDOS > set OS_VERSION=T2403 > > REM - cfgfile and autofile might be deprecated in future > > set CFGFILE=%DOSDRV%\FDCONFIG.SYS > set AUTOFILE=%DOSDRV%\FDAUTO.BAT > alias cfg=edit %CFGFILE% > alias auto=edit %AUTOFILE% > > REM - detect CPU, load CPU-specific configs > > if not exist %DOSDIR%\BIN\VINFO.COM goto ENDCPU > %DOSDIR%\BIN\VINFO.COM /m > if errorlevel 3 goto CPU386 > if errorlevel 2 goto CPU286 > goto ENDCPU > > :CPU286 > > fdapm APMDOS > ctmouse > > goto ENDCPU > > :CPU386 > if "%CONFIG%"=="4" goto CPU286 > > lh fdapm APMDOS > lh ctmouse > REM lh share > > if not exist %DOSDIR%\BIN\DOSLFN.CON goto NOLFN > lh %DOSDIR%\BIN\DOSLFN.CON > REM - Add other stuff here once LFN is loaded.. > :NOLFN > > if not exist %DOSDIR%\BIN\CDROM.BAT goto NOCDROM > call %DOSDIR%\BIN\CDROM.BAT > REM - Add other stuff here once CDROM is loaded.. > :NOCDROM > > :ENDCPU > > REM - load other configs using external BAT files > > if not exist %DOSDIR%\BIN\FDNET.BAT goto NONET > call %DOSDIR%\BIN\FDNET.BAT > REM - Add other stuff here once FDNET is loaded.. > :NONET > > if not exist %DOSDIR%\BIN\FDASSIST.BAT goto NOASSIST > call %DOSDIR%\BIN\FDASSIST.BAT > :NOASSIST > > if not exist %DOSDIR%\BIN\WELCOME.BAT goto NOHELLO > call %DOSDIR%\BIN\WELCOME.BAT > :NOHELLO > > MEM /C /N > > REM - local settings > > set BLASTER=A220 I5 D1 H5 P330 > set DIRCMD=/O:GNE /Y > set COPYCMD=/-Y > > REM nlsfunc %DOSDIR%\BIN\COUNTRY.SYS > REM display CON=(EGA,858,2) > REM mode CON CP PREP=((858) %DOSDIR%\CPI\EGA.CPX) > REM keyb US,858,%DOSDIR%\BIN\KEYBOARD.SYS > REM chcp 858 > REM mkeyb UK > > alias reset=fdisk /reboot > alias reboot=fdapm warmboot > alias halt=fdapm poweroff > alias shutdown=fdapm poweroff > > :END Personally, I'm not a fan of cfgfile and autofile since the user could always rename FDCONFIG.SYS in favor of using CONFIG.SYS .. but FDAUTO will still report "Done processing startup files C:\FDCONFIG.SYS and C:\FDAUTO.BAT" (this is actually printed in WELCOME.BAT). So I've left a comment in the updated FDAUTO that "cfgfile and autofile might be deprecated in future". :-) Jim |
From: Lukáš K. <lu...@lu...> - 2024-03-01 16:37:24
|
Hello, I just encountered the very same issue with alt + keycode not working in case of QEMU. I used your program to generate these chars (well, at first I wrote very similar code by myself, and later I found you already resolved and published your code here :). Thanks for that! I have one more tip someone may find useful. I was exploring a way to use this from FED editor the similar way like ALT + keycode works. I noticed there is quite powerful option "Tools > Filter", so I can type e.g. "char 64" here to get "@", and then "@" is pasted directly into the text file I am working on. I did one more step and modified the configuration of FED in FED.CFG via changing following line (where X is a number): ToolsX=ASCII|%h%n%schar %p (This achieves the same functionality as the "Filter" option, but directly calls the "char" utility, requiring me to type only the ASCII decimal keycode.) Additionally, I assigned this ToolX to F12 keyboard shortcut, so I can type F12 and then the keycode in FED editor, which is (almost) as convenient as using ALT + keycode :) Best regards, Lukas > Someone had emailed me to ask how to get a list of extended ASCII > characters into a file on FreeDOS (the Alt key trick doesn't seem to > work under a virtual machine). So I wrote a program to help them to do > that. > > Because this is a simple program, I've released it into the public > domain. I've also posted it on Ibiblio, because I was unable to email > the zip file to this person). If you need such a program, you can find > it here: > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/user/char.zip > > > Usage is: > char [n ...] > > (If you don't give any options, you'll get a usage statement.) > > So if you want to print out the degree symbol (ASCII decimal 248) you > would type: > > char 248 > > (ASCII codes not in 0-255 are printed as '?' instead.) > > You can give multiple characters, and the program will echo them one > after the other. So if you wanted to type two degree symbols, you > would type: > > char 248 248 > > The program is written in C, and compiled using OpenWatcom: > > wcl -os -mt char.c > > > Jim |
From: <je...@sh...> - 2024-03-01 15:42:49
|
The FreeDOS Interim Test Build T2403 for March is now available for download at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ <https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/> Changes: * Primarily, the release was switched back to HTMLHELP from AMB based Help. The new version of help needs testing and checking of the English text. I don’t think the other languages have received any significant changes and are waiting on verification of the English text before being translated. 2024-02-23 07:30:44 fdhelper [unstable] (Shidel): Merge branch 'unstable' into 'unstable' 2024-02-23 07:02:54 append (shidel): updated to v5.0-0.7 (FCB bugfix) 2024-02-23 03:23:50 append (shidel): Merge branch 'master' of gitlab.com:FreeDOS/base/append 2024-02-23 03:23:35 append (shidel): update primary site information in metadata 2024-02-23 02:22:22 project_FDI-x86 [unstable] (shidel): Merge pull request #6 from boeckmann/unstable 2024-02-23 02:12:13 project_FDI [unstable] (shidel): Merge pull request #20 from boeckmann/unstable 2024-02-22 21:07:41 project_FDI [unstable] (Bernd Boeckmann): change help viewer to HTMLVIEW 2024-02-22 20:54:27 fdhelper [unstable] (Bernd Boeckmann): help.bat: prioritize HTMLHELP 2024-02-22 19:43:20 project_FDI-x86 [unstable] (Bernd Boeckmann): change help viewer to htmlhelp 2024-02-22 19:18:01 fdisk [unstable] (Bernd Boeckmann): update LSM 2024-02-22 19:15:15 fdisk [unstable] (Bernd Boeckmann): release 1.3.14 part2 2024-02-22 19:12:05 fdisk [unstable] (Bernd Boeckmann): release 1.3.14 2024-02-21 09:27:56 append (Shidel): Merge branch 'master' into 'master' 2024-02-21 09:27:55 append (tsupplis): Update INT21.ASM - Major Logic Fix for support of FCB I/O calls 2024-02-18 04:31:39 tree [unstable] (shidel): updated to v3.7.3 2024-02-17 14:02:53 debug (shidel): updated to v2.02 2024-02-17 09:20:06 fbc_help (shidel): added override to package structure verification 2024-02-17 09:09:57 fbc_help (shidel): added package config file 2024-02-17 08:17:14 blocek (shidel): updated to v1.75b 2024-02-17 07:43:14 jemm (shidel): updated to v5.84 2024-02-09 20:35:19 htmlhelp [unstable] (Bernd Boeckmann): update English help to 1.1.0 (preview) 2024-02-01 05:49:48 upx (shidel): updated to 4.2.2 2024-02-01 05:44:35 liquiwar (shidel): updated to 5.6.4 2024-02-01 05:38:55 testdisk (shidel): updated to 7.2 2024-02-01 05:33:34 fbc_help (shidel): updated to 1.10.1 2024-02-01 05:17:54 sleep (shidel): updated to 1.1 2024-02-01 05:17:06 fbc (shidel): updated to 1.10.1 Jerome |
From: Liam P. <lp...@gm...> - 2024-02-24 13:15:40
|
On Wed, 21 Feb 2024 at 11:36, Eric Auer via Freedos-devel <fre...@li...> wrote: > It seems the djgpp-compiled 32-bit version of the comcom shell > of dosemu2 will be abandoned, moving to a 64-bit only version. > > https://github.com/dosemu2/comcom32 Putting the GPL as the README is very lazy of them, and totally unhelpful. What is it, what does it do, how does it different from other DOS command interpreters? In a word, why should anyone care? Not a troll. I don't know, and I have dosemu2 and have therefore used it. -- Liam Proven ~ Profile: https://about.me/liamproven Email: lp...@ci... ~ gMail/gTalk/FB: lp...@gm... Twitter/LinkedIn: lproven ~ Skype: liamproven IoM: (+44) 7624 277612: UK: (+44) 7939-087884 Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 |
From: <je...@sh...> - 2024-02-23 12:32:46
|
Hi Jim, > On Feb 22, 2024, at 3:35 PM, Jim Hall via Freedos-devel <fre...@li...> wrote: > > Excellent news! I'll post an item on the website about it. > > I can't login to Ibiblio from where I'm at right now, so I can't > mirror it - maybe someone else with Ibiblio access can do that for me. > Otherwise I'll mirror this to Ibiblio over the weekend. > > > Jim Even though, I generally don’t do anything with mirrors. Since you don’t have access right now, I took care of it. I put a copy at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdisk/1.3.14/ <https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdisk/1.3.14/> :-) Jerome |
From: Jim H. <jh...@fr...> - 2024-02-22 20:42:02
|
Excellent news! I'll post an item on the website about it. I can't login to Ibiblio from where I'm at right now, so I can't mirror it - maybe someone else with Ibiblio access can do that for me. Otherwise I'll mirror this to Ibiblio over the weekend. Jim On Thu, Feb 22, 2024 at 12:25 PM Bernd Böckmann via Freedos-devel <fre...@li...> wrote: > > I imported FDISK 1.3.14 to the FreeDOS package repository. Changes from last imported version are: > > Fixes: > - CRITICAL: Fix a drive letter disagree between DOS and FDISK in cases > involving multiple disks and a mix of active and non-active > primary partitions. > - HIGH: Prevent querying LBA capabilities via INT13,41, if LBA access is disabled > by the user. This caused some broken BIOS to crash the system, > like BIOS version 0.9.4 of Book8088 and Xi8088. > > Changes: > - Do not check for extra cylinders by default. DR-DOS refuses to use > partitions exceeding the BIOS reported disk size, despite being valid. > - Update German translation. > > Bernd > > > > _______________________________________________ > Freedos-devel mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freedos-devel |