Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

Hi Volkert, which worries does Japheth have regarding accepting I/O trap patches? What are the pros and cons of supporting the QEMM API for I/O traps, compared to the MS EMM386 API? I think SB Live PCI soundcard drivers only support the MS API? How hard would MS API support for VSB be? > In

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

Hi Volkert, > Wasn't there a limitation in the MS API that didn't allow lower I/O ports > (under 100 or something?) to be trapped? Correct. But then, the QEMM QPI interface is 11 different far call functions, plus some more to get the QEMM install check and other expectations which apps may

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Soluti ons?

Hi Bret, > I've been working on adding an implementation of I/O port trapping to > JEMM using the EMM386/QEMM API (INT 2F.4A15). I have it basically working. Great news! > As far as the I/O port trapping, MS did a really crummy job of implementing > it. > Bob Smith of Qualitas found this

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Soluti ons?

Hi Tom, > details of course matter, as there is a huge difference between > mainboard DMA (afaik mostly used for floppies) and PCI DMA (used by > everybody else). Mainboard DMA also sounds good for ISA SoundBlaster, I guess? > for the former onboard DMA, I'm not sure there was ever some >

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

Hi Volkert, > Firstly, JEMM doesn't have a port trapping API that is compatible with > Microsoft's EMM386 memory manager. Yes, JEMM can offer similar > functionality using JEMM Loadable Modules (JLMs), but the programming model > of JLM is considerably different than the API in EMM386, or even

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for Fr eeDOS 1.3]

Hi Bret, > https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes I would say the FreeDOS tradition is to use 2 letter codes without explicitly specifying the intended codepage, because both setting LANG and loading the codepage are typically done in config and autoexec and it is easy to edit

[Freedos-devel] freecom beep crash question

Hi! I notice that FreeCOM 0.84pre2 hangs after beeping, probably because it uses some method for timing the beep which fails on certain hardware. Could somebody tell me whether newer FreeCOM versions fix this by using a foolproof timer, for example the 40:6c timer tick counter? Is there a

Re: [Freedos-devel] disk I/O performance

Hi Bret, >> any idea how reliable/wide distributed this is? > It seems to be fairly widely distributed. I just tested in a few > places. It's present in an old HP laptop (I think it's about 7 years > old now). It's also present in VMWare Player and QEMU, but not in > DOSBox-X. > I also

Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3?

Hi Jerome, > I never said performance was not important. Only, there are more > important things for the installer that come first. Among those > are things like stability, portability, flexibility and others. > Improving performance is near or at the bottom of the list. I would definitely not

Re: [Freedos-devel] disk I/O performance

Hi Tom, >> Jack has commented on the topic: > it would be cool to have his comment forwarded to this list, not only > a summarized version of it (as far as you understand and think is > important). Sure, here is the original comment, after checking back with Jack. Note that I had put that "64

Re: [Freedos-devel] disk I/O performance, was: What are the blocking bugs/issues for FreeDOS 1.3?

Hi Tom, thank you for the I/O trace! Indeed FreeDOS XCOPY also suffers from using a non-aligned buffer. For COPY, the person to tune the code would be Jeremy at the moment. About your COPY C:\kernel.sys C:\BLA test: Let me summarize the LBA trace: Sectors 466 to 469 are read one by one,

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

Hi Jerome, > If ... there are no partitions on the target hard drive, > it tells fdisk to automatically partition the drive... > If there is a command line option to perform automatic > partitioning using a single big partition, I am unaware of it. If FDISK defaults to making 1000 partitions

Re: [Freedos-devel] FreeCOM 0.85a release

Hi Jerome, > Out of curiosity, what would your perfect solution to multi-language support > entail? > Everyone live with English, compile your own or something else entirely? the current solution is quite nice if you ask me: You can create a command.com in the language of your choice by

Re: [Freedos-devel] FreeCOM 0.85a release

Hi Jerome, of course you can say you prefer a command.com which can load translations on the fly. On the other hand, you know that the installer could do whatever it takes to put a command.com in the desired language on the fixed disk of the user :-) Actually my 3 floppy Brezel distro already

Re: [Freedos-devel] video FreeDOS running Windows 3.1

Hi Jeremy, does that mean the unstable kernel already supported Win 3.1 386enh? Cool to know :-) How about Windows for Workgroups in 386 mode, which is "non safe mode" there, so features are lost without it in WfW 3.11? Thanks for cherry-picking all the relevant patches! I guess the FDPP

Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3?

Hi Tom, to quote a 2018 FAT16 speed test example by Jack, copying a mix of files and directories of different sizes disk to disk: Plain FreeDOS 65s With LBACACHE 61s adds a small cache With UIDE 51s adds UDMA and larger cache With UHDD 47s all the above plus read-ahead With XHDD 43s all the

Re: [Freedos-devel] video FreeDOS running Windows 3.1

Hi Jeremy, others, > Kernel patches - http://server2.fdos.org/tests/kernel-win3-patch.diff > rest of sources (kernel, FreeCOM, format, fdisk, sys, share, edit) - > https://github.com/fdos I have been browsing those patches a bit. So I can share some insights about them, also implying many

Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3?

Hi everybody, I also agree that there should be a next release candidate first, not immediately a FreeDOS 1.3 release. Even when RC5 is perfect, nobody would stop us from simply bumping the version number for release. And when it is not perfect, things can be improved before the actual

Re: [Freedos-devel] video FreeDOS running Windows 3.1

Hello Jeremy, > Eric who's original research helped with the initial > implementation of the necessary patches a decade ago > (https://web.archive.org/web/20061001224249/http://www.coli.uni-saarland.de/~eric/stuff/soft/specials/win3.x-dosext-freedos-notes.txt) Wow that was from 2004 :-o The

Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3?

Hi! > reserved to condition for example yes, no, quit > 0.0:Y> 0.1:N > Space reserved to file diskcopy.c > (...) > 1.29:image file (Y/N)? > 1.30:disk (Y/N)? > 1.31:Copy another disk (Y/N)? Note that yes/no questions actually have kernel support. This

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi! I agree that it is not really useful to use ClamAV in DOS. By now, it has a list of millions of virus signatures of which basically all will be for Windows viruses anyway. You need more than 200 MB for a typical signature database for it and opening it takes ages before you can even scan

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

Hi Richard, as you are interested in having extremely large RAMDISKs: https://github.com/Baron-von-Riedesel/HimemSX might be interesting for you, because it can use RAM beyond the first 4 GB. Normal HIMEM versions can only use your first 4 GB, and between a few 100 MB and more than a

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

Hi Ralf, 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. Apparently the CPU detection in the installer would only recognize an 80186 even though

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

Hi! SHELLHIGH = \FREEDOS\BIN\COMMAND.COM ... devicehigh=srdxms.sys If you have not EMM386-style driver loaded, then you should not use ...HIGH style commands. Also, you write that autoexec uses C:\FREEDOS\BIN\srdisk E:8192 /s=256 (using % notation for C:\FREEDOS) So I expect this

[Freedos-devel] FAT32 ambiguity on BTTR

Hi! Some interesting detail from BTTR - makes me wonder whether FreeDOS kernel, FORMAT, DOSFSCK or some subset of the three are mistaken here. What does Microsoft say? Regards, Eric PS: You read that right. A DOS RAMDISK with > 32 GB size :-D

Re: [Freedos-devel] Thinking about FreeDOS 2.0

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 after the initial install using FDIMPLES, I wonder why bother with

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

Hi Jerome, to answer some specific parts of your mail: Yes, it is useful to have two different boot style CD images and not only the more compatible variant plus a boot floppy image. Because the latter would mean that people which could boot CD only in the less common style would need a floppy

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

Hi! Bumping this thread from Jim. I think if the majority of the games has palette issues, it could be VirtualBox or QEMU just not properly emulating VGA, VESA, VBE etc., possibly also depending on the color depth of the host operating system GUI. Which versions and settings were used? Which

Re: [Freedos-devel] Freedos EDIT

Hi Tom, I just noticed that the source to FreeDOS EDIT https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/edit.zip is incomplete as it assumes an existing DFLAT library which is not included, and at least non-trivil to locate on the internet. Looking at my

Re: [Freedos-devel] Update on website usability test

Hi Jim, hi everybody, sorry about being so late with the review. I hope the (rather critical, but of course not intended to be personal pouting & nagging) comments below still help. It may be my German bad understanding of fashion, but: A professional designer donated a new website design

Re: [Freedos-devel] How to work with FAT12 in FreeDOS 1.3

Thanks for quick reply. So too big, how big can I go and the CMD line (in FreeDOS) to achieve some sort of FAT12 drive (for my USB stick D:\ partition)? For FORMAT testing, I have FAT12, FAT16 and FAT32 drives in my DOSEMU2 installation. Those are created by manually changing the partition

Re: [Freedos-devel] The 386MAX source code has been released :)

Hi! Great to see that 386MAX became open source, thanks! :-) Also inspired by https://www.theregister.com/2022/06/30/software_freedom_conservancy_quits_github/ you could consider using for example gitLAB instead, if you like GIT in general, but have troubles with gitHUB in particular?

[Freedos-devel] Windows compatibility, was: FreeDOS Unstable - interim development builds

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 project_FD-NLS (shidel): added FreeDOS release README to NLS project 2022-06-19

Re: [Freedos-devel] Interim FreeDOS Build T2208

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 similar. Actual app changes seem to be those: - Sayswho (Senso) game now with

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

Hi Paul, While thinking about 64k limit for edit... I come to think about 16 bits and 32 bits programs... Why there is no two separate versions of FreeDOS, one for 16 bits CPUs (8086) and one for 32 bits CPU (386+)? That is not necessary - you mentioned a 32-bit version of some text

Re: [Freedos-devel] New version of text editor (and image viewer) Blocek

Hi! Hello, few days ago I released the version 1.7 of my text Editor Blocek. Great news, I was already waiting for an announcement here or on Jim's channels :-) + many improvements in the graphical user interface (GUI) ... + the scope of the Search or Search and Replace functions can

Re: [Freedos-devel] i have various topics to cover

hello! hello everyone, i have not been active because of school and mental best wishes! illness. i have something to say about defrag and chkdsk. they both require 386! i mean it makes no sense to me why necessary programs like these... in the case of chkdsk that clearly is a bug,

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

Hi! (I started looking into it to support loading lDebug in device-driver mode using DEVLOAD, which requires an allocation to the device that's larger than 64 KiB. I uploaded my experimental patch [1] ... However, I believe that DEVLOAD will not re-open the file handles held by existing

Re: [Freedos-devel] Interim FreeDOS Build T2208

Hi! I agree it would be good to have a changelog visible before downloading those 100s of megabytes :-) In particular, are there updates in the kernel? Should people test the improved Windows for Workgroups 3.11 compatibility that I vaguely remember not having been on time for the latest normal

Re: [Freedos-devel] When is FreeDOS slow and when fast

Hi! The computer: Pentium 4, SSD PATA disk, 512MB RAM The task: Compilation of the full Blocek source ("Build all") - 64603 lines of code using FreePascal 3.2.0 (GUI) Windows 98: 5,6s Everything happened on a FAT32 partition, I assume? FD, cwsdpmi, noUIDE, noLBAcache: 208,2s FD,

Re: [Freedos-devel] Open Watcom v2 DOS installer is abysmally slow in FreeDOS

Hi Willi, I downloaded open-watcom-2_0-c-dos.exe (an extracting .exe) at: https://github.com/open-watcom/open-watcom-v2/releases/tag/Current-build 140 MB size. This is a self-extracting ZIP file. You can try using our build of infozip UNZIP to extract it. Maybe the downloaded exe uses build

Re: [Freedos-devel] mode.com

Hi! MODE does indeed have verbose errorlevels in codepage handling: With FreeCOM, you can display them like this: C:\>mode con cp prepare=((437) c:\freedos\cpi\ega.cpx) MODE: No compatible FreeDOS DISPLAY driver loaded. Syntax example: ... DISPLAY CON=(VGA,437,1) C:\>echo %errorlevel% 101

Re: [Freedos-devel] FreeDOS package issues

Hi Jim, Well, you can tell a CD drive to play track X using my minimalist cdrom2ui, but I think that would be sort of an INdecent open source alternative because it is too minimal :-D On the other hand, a QuickBasic solution sounds like something needing FreeBASIC in QB mode, or something

Re: [Freedos-devel] IFS API

Hi! As we have various drivers which use the network redirector API, CD/DVD redirector API or both, including drivers which use those for different purposes, which advantage do we expect from using a special IFS API which is both "more on topic" and "less existing", as in only very specific DOS

Re: [Freedos-devel] Free FDISK interim builds

Hi Bernd, thank you for your work on FDISK! Version 1.3.5 (unreleased) -- - CRITICAL: Fix FDISK loading wrong head and sector values from MBR if operating in LBA mode. The previous incorrect behaviuor was hardcoding them to cylinder boundaries instead of

Re: [Freedos-devel] Slowdown-Units ratings and a CPU-bound depacker benchmark

Hi :-) To make this long thread a bit longer, I think that using port I/O in delay loops used to slow down too fast games by wasting time actually is a good idea (if you pick a safe port) BECAUSE the I/O is slow and not cached and not subject to too smart CPUs trying to optimize it away in

Re: [Freedos-devel] Extension proposal

Hi Jerome, if you are worried about collisions, use AMIS int 2d. Overhead is low and it is less crowded than MUX int 2f. RBIL was famous enough to make AMIS more widespread. FreeDOS is too niche to re-invent that wheel and declare int 2b to be a new trend. Why would your RESIDENT driver have

Re: [Freedos-devel] Extension proposal

Hi Jerome, there is no need to allocate a whole int 0x2b for just one driver. There are mechanisms which already invite drivers to share them :-) INT 2D - ALTERNATE MULTIPLEX INTERRUPT SPECIFICATION (AMIS) [v3.6] AH = multiplex number AL = function 00h installation

Re: [Freedos-devel] HTMLHELP progress report

Hi Bernd, thanks for all those fixes in HTMLHELP! How much faster are Unicode and HTML entity translation now? I would NOT remove the ZIP feature, because a typical help zip contains more than 100 files, with a median length of just 1 kB uncompressed. This would waste a lot of disk space

[Freedos-devel] useful HTMLHELP bug findings and proposals

Hi! Our GITLAB has recently received multiple useful tickets from Bernd Böckmann: https://gitlab.com/FreeDOS/base/htmlhelp/-/issues/3 Line 43 in CP857.H is wrong, messing up a certain character. https://gitlab.com/FreeDOS/base/htmlhelp/-/issues/4 Some Turkish CP857 characters are not

Re: [Freedos-devel] format /s

Hi Patrick, In principle, FORMAT /s simply formats your drive, which you can already do well with Linux tools, and then runs SYS to make it bootable. Alternatively, it can provide a boot sector built into FORMAT itself and fetch a copy of kernel & shell from e.g. the current drive, or the

Re: [Freedos-devel] trying to understand execrh.asm -- calls to EXECRH cause my 286 system to lock up

Hi Rich, -My BIOS supports both CHS and LBA. FreeDOS is using CHS due to the size of the CF card (~500MB). I will try forcing LBA. Actually that should depend on partition type, not on disk size ;-) -I log interrupt calls out to my serial debugger on my 286. In execrh(), I am not seeing

Re: [Freedos-devel] i have a tech question about 286 and XMS

Hi! is there any supported XMS driver for 286 that FreeDOS provides? himemx dose not support it and the fd286xms driver is old and not supported. maybe i could work on it. yes i have a 286 xD it's just frustrating that everything requires a 386 If I were you, I would just use FDXMS286 and

Re: [Freedos-devel] i have a tech question about 286 and XMS

Hi! FDXMS286.sys is the driver i am using it works with wolf3d code but not the dos game code. i made a work around but there might be a bug in that xms driver's code Please be more specific about what went wrong and which work around in which code snippet resolved the problem. I think a

Re: [Freedos-devel] Help Development with djgpp

Hi! I have no knowledge for protected mode. I think you need this for OpenWatcom C compiler. This is the only reason to use DJGPP compiler. Am I right? Else the initializing you show on the YouTube Videos is very simple for OpenWatcom. I think (check the youtube videos with examples by

[Freedos-devel] ACPI infos with ACPItool

Hi! A few months ago, Laaca has released AcpiTool 1.1c and 1.2b: http://www.laaca.borec.cz/soubory/acpitool.zip It shows ACPI info in DOS. The BTTR thread here https://www.bttr-software.de/forum/board_entry.php?id=20351=0=time=0 discusses the update to ACPItool 1.2b: Now I wonder whether

[Freedos-devel] VME broken on Ryzen CPU, autodetection useful?

Hi! I just got reminded that (2017 news) http://www.os2museum.com/wp/vme-broken-on-amd-ryzen/ VME is broken on AMD Ryzen of that time. That sounds like something which would be relevant for JEMM386, because it could automatically activate NOVME mode for affected CPU. Does anybody remember

Re: [Freedos-devel] FreeDOS code page Unicode compatibility

Hi! If you’re interested about the whole forint sign issue, read my Unicode proposal and its follow-up: https://www.unicode.org/L2/L2023/23060r-forint-sign.pdf https://www.unicode.org/L2/L2023/ ... -forint-sign-follow-up.pdf The way in which the follow-up quotes me misses out on quite a few

Re: [Freedos-devel] ANSI for DOS

Hi! There are other base components in FreeDOS, such as CuteMouse that do not support an 8086. That should be a almost compile time option. If neither .286 nor .386 are set early in the code, neither USE_286 nor USE_386 should trigger and you should get an 8086 compatible variant. However,

Re: [Freedos-devel] dosshell and task swapping, was: dir issues

Hi Rugxulo, [3] Windows 3.0 started to catch on. That meant HIMEM.SYS and XMS as standard; LIM-spec EMS started to fade. Apps like 1-2-3 r3 used DOS extenders routinely. Memory management really got important but everyone was buying 386SXs so you could sell them QEMM even if they didn't want

Re: [Freedos-devel] dir issues

Hi! VCPI was a superset of EMS, right? I don't think so, no. VCPI can be added to EMM386 to let it coexist with DOS extenders. VCPI itself does not provide EMS. EMS can exist in hardware on 8086, where DOS extenders cannot exist. EMS itself is not related to VCPI. The other

Re: [Freedos-devel] Problem booting FreeDOS on Book8088 PC-XT laptop

Hi Jim, http://www.bttr-software.de/forum/board_entry.php?id=21061 ... By now, the BTTR thread has figured out that the bug was in the Xi8088 BIOS, not in XT-IDE: When calling unsupported (bei neither XT-IDE nor the main BIOS) disk functions, the main BIOS trashed the int10 vector. A fixed

[Freedos-devel] comcom32 shell

Hi! It seems the djgpp-compiled 32-bit version of the comcom shell of dosemu2 will be abandoned, moving to a 64-bit only version. Maybe somebody wants to pick up comcom32 for use in plain DOS: https://github.com/dosemu2/comcom32 Note that this shell requires CWSDPMI exe in the same

Re: [Freedos-devel] comcom32 shell

Hi again! It seems the djgpp-compiled 32-bit version of the comcom shell of dosemu2 will be abandoned, moving to a 64-bit only version. Stas found out that comcom64 is compatible with 32-bit toolchains, so dosemu2 could keep an eye on that to keep comcom64 compatible with 32-bit builds for

Re: [Freedos-devel] NewDOS source code has been published!

Hi Willi, I will wait some days to see if there are other questions or proposals referring to NewDOS and then send André Olejko a list with everything at one time in german... He explicitly asked to NOT be bothered with such things. So I suggest that we just collect the questions and

Re: [Freedos-devel] special old DOS software looking for a place online

Hi everybody, thanks to help from two men, NEWTRACK is on track again! In other words: https://auersoft.eu/uni/newtrack-eyetracker/ and https://auersoft.eu/soft/ are working again and there even is a new mirror: https://m.lod.bz/auersoft.eu/soft/ etc. Thanks to Jerome and Tassilo for mirror

Re: [Freedos-devel] FDISK does not respect DLASortByDriveNo config of the kernel

Hi Bernd, I would assume the kernel parameter is neither meant to be queried at runtime nor is it used by a significant number of people at all. There is no external API, but you may pull it from RAM, possibly. Alternatively, you could extract settings from the kernel file of the boot drive or

[Freedos-devel] special old DOS software looking for a place online

Hi developers! As you may remember, I wrote a rather specialized eyetracking software called NEWTRACK *long* ago. It is open source, written in DJGPP GNU C and works with dual PCI VGA/VESA graphics. Given that I have no working web domain at the moment, would anybody be interested in mirroring

[Freedos-devel] initdisk question

Hi! Have a look at https://gitlab.com/FreeDOS/base/kernel/-/issues/4 which wonders whether there is a bug in CHS/LBA detection/forcing, risking to call the BIOS with invalid parameters or dividing by 0. Regards, Eric ___ Freedos-devel mailing

Re: [Freedos-devel] initdisk question

Hi again, Have a look at https://gitlab.com/FreeDOS/base/kernel/-/issues/4 which wonders whether there is a bug in CHS/LBA detection/forcing, risking to call the BIOS with invalid parameters or dividing by 0. We found out that the problem is something else: Kernels without FAT32 support

Re: [Freedos-devel] FreeDOS Interim Build T2402

Hi Jerome, For these: They are version updates. 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

Re: [Freedos-devel] FreeDOS Interim Build T2402

Hi Jerome, thanks for the updates! :-) The FreeDOS Interim Test Build T2402 for February is now available for download at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Changes

[Freedos-devel] Problem booting FreeDOS on Book8088 PC-XT laptop

Hi! As you may have read, some company has created an eeepc sized PC-XT laptop called Book8088. It ships with MS DOS on a CF card. Bocke got an EDR-DOS kernel and SvarDOS apps to work on it, too, but FreeDOS kernels crash. SvarDOS is a FreeDOS based floppy distro - http://svardos.org/ which is

Re: [Freedos-devel] Problem booting FreeDOS on Book8088 PC-XT laptop

Hi Jim, I'm glad you're bringing this conversation back to freedos-devel .. because this is a good place to discuss FreeDOS things. In related news, the dosemu2 people also find the problem interesting. Their discussion mentions that FDPP, a port of the FreeDOS kernel,

Re: [Freedos-devel] NLS in Edlin

Hi! Willi Spiegl said in the meeting that there is no NLS in Edlin. I beg to differ! As with the HTMLHELP versus AMB issue, the problem, as far as I have understood Willi, is the lack of a process, possibly an automated pipeline, which will take updated translations and spread them to the

Re: [Freedos-devel] NLS in Edlin

I made recompiling Edlin easy for non-programmers, so that shouldn't be a problem. You don't have to know a lick of C to recompile it. One would still need the toolchain, so it would be great if there could be somebody who already has it (and does know C, just in case) who would volunteer as

Re: [Freedos-devel] Cleaning up FDAUTO

Hi guys, thanks for cleaning up autoexec! REM - streamlined the network test (user adds their own stuff anyway). I hope they add it at a place where it actually gets to run :-) set PATH=%DOSDIR%\BIN if exist %DOSDIR%\LINKS\NUL set PATH=%path%;%DOSDIR%\LINKS A special test just for one

Re: [Freedos-devel] FreeDOS Phishing attack - warning!

Hi everybody, now I have also received one of those freedos phishing mails: test at multicenter.com.bo wrote "Re: [Freedos-devel] mode.com" from 193.201.8.100 saying: Please review and sign the enclosed document. This is essential for our current project (etc.) The link in the mail

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

Hi Bernd, Microsoft and IBM released the source code of MS-DOS 4.0 under MIT license [1]. To me, it looks fairly complete. Greetings, Bernd [1] https://github.com/microsoft/MS-DOS/tree/main/v4.0 As mentioned by DOSEMU2 people, this is a somewhat exotic, but interesting MS DOS 4.00, not

[Freedos-devel] FreeDOS Windows for Workgroups howto

Hi! Hidden in the "Tyrian 2000 in DOS with sound on PCIe only machines?" thread on BTTR which also contained the VSBHDA (soundblaster emulation for HDA machines, Japheth's variant) announcement, I found this link: https://github.com/pufengdu/RetroFuns/blob/main/WFWG/FDWFWG.md it explains how

[Freedos-devel] OT: Creating new threads

Hi Willi, My main problem is, that I can answer via mail, but I have absolutely forgotten how to create a new thread. ... Simply changing the "Subject" seems not to be the solution. The trick is to send a completely new mail to freedos-devel@lists.sourceforge.net - this will create a new

Re: [Freedos-devel] MBR boot failure + diagnosis on a PhoenixBIOS 4.0 Release 6.0 machine

Hi Bernd, /LOADMBR restores the whole sector. Does anyone think this is a major issue? In that case, I think loadmbr should never be used except when there was a previous corresponding savembr. Because using loadmbr in another way results in deleting the whole partition table and/or

Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

Hi! I have no life - I can devote the time and energy to it, just don't have the brainpower I'd like to think I have. I hope that will get better :-o Eric ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net

Re: [Freedos-devel] [Semi-OT] Thoughts: Actually doing stuff with MS-DOS 4.01

Hi! Well, what is wrong with http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/pkg-html/fdisk.html or alternatively http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/pkg-html/xfdisk.html or even

Re: [Freedos-devel] zoo

Hi! I ran one more test with zoo. It runs with FAT16 998 MB but not with FAT16 1025 MB. Did you use the original version for that test? Or the one already having the fix from the forum? The old zipper "zoo" has a built-in bug that prevents it to expand compressed files on FAT32 system.

[Freedos-devel] freedos runtime and terminal updates and alternatives

es/util/user/runtime/ there is a version from Eric Auer from 03sep2012 FDT2404 uses ver. 2.1 from Jim Hall, 2002 Is it an update? You should bring it up on the mailing list or ask Eric if it should be updated. terminal https://www.auersoft.eu/soft/ terminal-2007jun20 (3.3) FDT2404 us

[Freedos-devel] Ancient Windows compatibility notes

Hi! As Jim prefers such things to be on-list, here are some 2004 (and one 2006) bits from my archive regarding Windows compatibility, in context of the WfW 3.11 compatibility howto advertised on BTTR and here recently. Maybe some of you would like to have a look to see whether anything is still

Re: [Freedos-devel] Fwd: lspci (pciutils) for freedos

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

[Freedos-devel] List of app links and versions

Hi! Willi has made a list of links and version numbers of apps: https://www.bootablecd.de/FreeDOS-tools-hyperlinks.zip There are two new updates: doszip 2.66 (fixes a bug in search) ldebug 8 This can be useful to spot updates for our distro and for adding some extra details and links to

[Freedos-devel] country sys update missing?

Hi! Willi and Laaca noticed that the country sys settings for Germany have a flaw, but apparently Andrew, Jeremy and RR already updated https://github.com/FDOS/country/commits/master/country.asm so I guess this is a simple fix which can be implemented by updating the relevant FreeDOS package

Re: [Freedos-devel] zoo just needs packaging

Hi! To get the discussion a bit more productive again: https://www.bttr-software.de/forum/board_entry.php?id=21046=0=time=0 is the original thread and apparently RayeR has used Borland C to compile a fixed binary which Fritz has received and tested? So the ONLY thing missing seems to be

Re: [Freedos-devel] Back at it with DOG

Hi and welcome back, Wolf :-) I used to map a virtual drive to a folder on Linux - but like you found, I sometimes had problems with that (not all the time, just sometimes) so I stopped doing that. When I need to get access to my virtual drive, I use guestmount from the libguestfs package to

Re: [Freedos-devel] FreeDOS on Pocket386

Hi Jim, from an engineering point of view, I would say LBA avoids problems related to mismatching CHS geometries on different computers, so I still prefer the MANUAL method where users have to run SYS C: /FORCE:CHS before transplanting a disk from a computer with LBA support to one without

Re: [Freedos-devel] Four in a Row

Hi Jim, I downloaded it and looked it over. The sources are fine, no problem there. Then I played it on FreeDOS under QEMU. The on-screen help says 'N' for a new game, 'Q' to quit. Using 'N' to start a new game is fine. Playing the game works fine. But when I press 'Q' to quit, it hangs and

Re: [Freedos-devel] FreeDOS on Pocket386

Hi Bernd, Thinking again about the problem, wouldn't it be an option to always install the CHS loader if the partition to boot from is within the first 1024 cylinders? That would have mitigated the problem on the Book386. Earlier in this thread, I explicitly suggested to NOT use CHS unless

Re: [Freedos-devel] 16-bit Windows development

Hi Bernd, To my knowledge, we do not have a working open source DOS task switcher yet, capable of switching between "multiple DOS sessions", or is there one? There is TRIDOS, which was included in the old Blair distro of FreeDOS, but it is far from perfect. You could compare the situation

Re: [Freedos-devel] FreeDOS on Pocket386

Hi! It would be possible to add an additional screen to the installer (probably only advanced mode) to use the /FORCE:CHS option. That would be a good option to have, but I'd like to fix sys bootcode  so lba code works and maybe make a multi sector fat32 version that supports both chs &

Re: [Freedos-devel] FreeDOS on Pocket386

Hi! It would be possible to add an additional screen to the installer (probably only advanced mode) to use the /FORCE:CHS option. That would be a good option to have, but I'd like to fix sys bootcode so lba code works and maybe make a multi sector fat32 version that supports both chs &

Re: [Freedos-devel] FreeDOS on Pocket386

Hi Willi, checking tools like chkdsk which support FAT16 only than dosfsck (the only one that supports FAT 32, but even this one stops at 256 gb. The actual Linux dosfsck supports 2 tb, it is part of dosfstools). If you want to know which type of FAT your kernel supports and which type of

Re: [Freedos-devel] FreeDOS on Pocket386

Hi Jim, To Jim: Are you sure you ran FDISK /XO on the Pocket386 system? If FDISK says it detects LBA there but the LBA loader from FreeDOS doesn't work that'd be quite the bug. Definitely I'm seeing "W95B INT LBA FAT32" when running FDISK /xo on the Pocket386. I can't send photos to the

<    5   6   7   8   9   10   11   >