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

> > Something targeting 16-bit Windows would be easier since the official API has > been frozen since 1992 Are you sure it would be easier? Especially reimplementing Win 3.1 enhanced mode would be very hard to implement, I think. To my knowledge, we do not have a working open source DOS task

Re: [Freedos-devel] FreeDOS on Pocket386

> Am 04.06.2024 um 00:24 schrieb Eric Auer via Freedos-devel > : > > 3. Or we could give SYS support for multi-sector FAT32 boot > sectors, which would be necessary for automatic switching > on FAT32. Only FAT16 is simple enough to handle both cases > within a single sector. Thinking again

Re: [Freedos-devel] problems with moving in a long history

> Am 04.06.2024 um 09:31 schrieb Wolf Bergenheim via Freedos-devel > : > > I did some more digging... Found a wikipedia article discussing it [1] but > maybe more interesting was a german text on 4dos tips[2] apparently Windows > 95 only put the rest of the command line in CMDLINE. The 4dos

Re: [Freedos-devel] FreeDOS on Pocket386

> Am 02.06.2024 um 23:55 schrieb Eric Auer via Freedos-devel > : > > Are you sure that this is not just what the PARTITION TABLE says? > Is there a way to ask FDISK whether it detects BIOS LBA support? Eric is right, I had a look at the relevant lines of the FDISK source. This is only an

Re: [Freedos-devel] FreeDOS on Pocket386

The LBA routine of the FAT16 loader seems to work for Jim. It is taking a more "conservative" approach compared to the one in the FAT32 loader, in that it reserves some space for the DAP in its data area instead of reserving it on the stack. I agree that including a choice in the installer

Re: [Freedos-devel] FreeDOS on Pocket386

> > 5. SYS C: /FORCE:CHS > > > And that boots without problem on the Pocket386! > > > Also: you asked about FDISK /XO output. It reports "W95B INT LBA > FAT32" in the upper left corner. This is running FDISK 1.3.15. > Well, this is good on the one hand, but bad on the other. It means that

Re: [Freedos-devel] problems with moving in a long history

> but then I realized that since it doesn't know about it, it doesn't actually > get the full line. It does only see the first 127 characters, > which is why you can get odd errors even though your line should be fine, > depending on where the break is... Nice analysis :) The behaviour of

Re: [Freedos-devel] FreeDOS on Pocket386

Hi Jim, > Am 02.06.2024 um 01:45 schrieb Jim Hall via Freedos-devel > : > > (I created a single partition on the 1.9G drive, formatted and > installed "plain DOS" to that, everything works fine) > How did you create the partition? Did you run FDISK or did you re-use an existing 1.9G

Re: [Freedos-devel] problems with moving in a long history

On 15.05.2024 16:01, Wilhelm Spiegl via Freedos-devel wrote: The main problem is, that if you type "arrow up" for "history" (repeating the previous command) and then "arrow left" (for moving the cursor into this long command) causes a break in the long option line at both versions. The cursor

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

Hi Wolf, welcome to the mailing list. Great to hear you started working again on DOG. Putting it on Github (or some other publicly accessible repo) sounds like a good idea :) Looking at https://gitlab.com/FreeDOS/util/dog, that seems to be version 0.83c. Is this the latest publicly available

[Freedos-devel] Free FDISK 1.3.15

Free FDISK 1.3.15 is released. https://github.com/FDOS/fdisk/releases/tag/v1.3.15 Fixes: • HIGH: Fix FDISK not modifying partition type via command /MODIFY and via UI if FDISK is started in extended options mode /XO. • HIGH: respect selected video page instead of hardcoding

Re: [Freedos-devel] zoo just needs packaging

On 28.05.2024 19:00, thraex via Freedos-devel wrote: There's also someone who has been updating zoo with bug fixes for UNIX-like platforms on , maybe cherry-picking some of them could make sense. Cherry-picking might not the best idea here. In my opinion

Re: [Freedos-devel] zoo just needs packaging

On 23.05.2024 20:20, Eric Auer via Freedos-devel wrote: So the ONLY thing missing seems to be putting everything into a ZIP (yeah, no .ZOO) file in the usual FreeDOS structure, as has happened with my RUNTIME recently thanks to some support, help and contributions from Vacek and Jerome :-) I

Re: [Freedos-devel] prog lang. year for watcom compiler/programming book list?

Hello Richard, C in general and Open Watcom in particular are good choices for DOS programming. The other free options supporting more recent C versions are GCC as part of DJGPP targeting 32-bit DPMI, and, despite being somewhat experimental, IA16-GCC, a port of GCC for the DOS 16-bit real

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

> Am 01.05.2024 um 01:19 schrieb Ben Russell via Freedos-devel > : > > However, a proper fix for this should be something like this, executed before > one attempts to use INT 0x13: > > ;; Work around a bug in 1997 PhoenixBIOS 4.0 Release 6.0, > ;; where DL can be erroneously set to 0x00

Re: [Freedos-devel] Where is the source code?

> > If the written word is a barrier so high that the young people skip dealing > with FreeDOS, then how do you expect them to USE the OS to begin with, much > less WRITE code for it? (This thread is strictly and solely about developers, > not end users, in case you've forgotten.) I see it

Re: [Freedos-devel] Where is the source code?

> The moment FreeDOS starts pushing video lessons for developer tutorials is > essentially the day that FreeDOS has died. Well, that is a little bit of an exaggeration :) FreeDOS has died if people stop being interested in it, and with DosBox etc. as alternatives we are short of being at

Re: [Freedos-devel] Where is the source code?

> I like that idea. I think a good place to add these would be in the > "Technical information" section on that page, maybe as another row of > "info boxes" before (or after? not sure) the row that has RBIL, VGA > programming, and the Graphics Programming book. I would put it below Technical

Re: [Freedos-devel] Where is the source code?

> To make this more clear on the website, I've changed the info box > title from "Create new programs" to "For developers" - and changed the > action link in that info box from "Create programs" to "Developers". > I've also changed the "sitenav" link in the website footer from > "Create" to

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

Hello Steve, Some of the code's pretty braindead, too.  Especially what looks to have come from IBM.  I mean...house styles vary, but Algolization is still just hideous-looking.  But it goes beyond that - think some of the utilities are going to need major rewrites.  I'm thinking of writing

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

Hi Eric, > > 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 installing a new partition scheme > which will probably not fit to the size of

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

Hello Ben, thanks for reporting this. I opened a github issue at the FDISK repository containing the code for the MBR: https://github.com/FDOS/fdisk/issues/82 We may adapt BOOTNORM.ASM to work around the issue. https://github.com/FDOS/fdisk/blob/v1.3.14/source/fdisk/bootnorm.asm > P.S. If you

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

Sadly not. Only the binaries are released under MIT through the repository. > Does that mean we finally have a genuinely open sourced OMF linker? > > -hpa > ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net

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

> Am 26.04.2024 um 09:08 schrieb Steve Nickolas via Freedos-devel > : > > I got most of it compiled using the tools in the archive. Side effect of having these tools in the repo is that these are released under MIT license too, espectially: - MASM 5.1 - Microsoft LINK 3.65 - Microsoft C

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

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 ___ Freedos-devel mailing list

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

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 > Betreff: lspci (pciutils) for freedos > Datum: 9. März 2024 um 12:49:53 MEZ > An: Bernd

Re: [Freedos-devel] Website has moved to new hosting

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 ___ Freedos-devel mailing list

[Freedos-devel] FDISK 1.3.14

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

Re: [Freedos-devel] HTMLHELP

I am one step further. I installed dosfstools via zypper and ran the RBE install script again. It showed the following output: required lower permissions for creating DOS filessystems. '/usr/sbin/mkfs.msdos' -> '/home/rbe/bin/make-dosfs' required lower permissions for labeling DOS filessystems.

Re: [Freedos-devel] HTMLHELP

that this is part of RBE itself? Bernd On 11.02.2024 21:09, Jerome Shidel via Freedos-devel wrote: Hi Bernd, On Feb 11, 2024, at 2:11 PM, Bernd Böckmann via Freedos-devel wrote: Hi Jerome, thanks for the explanations! Am 10.02.2024 um 00:18 schrieb Jerome Shidel via Freedos-devel : Oh BTW

Re: [Freedos-devel] HTMLHELP

Hi Jerome, thanks for the explanations! > Am 10.02.2024 um 00:18 schrieb Jerome Shidel via Freedos-devel > : > > Oh BTW... If your interested in seeing the RBE in action, or making builds > locally, it’s very easy to install and create builds. You can read the > instructions for installation

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

On 09.02.2024 22:30, Ralf Quint via Freedos-devel wrote: It always complains it can't find it and wants it to be put in the "roms" folder Under Windows I had success by creating a "roms" directory in the directory of 86box.exe, and then copying the rom images provided by [1] into that

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

On 09.02.2024 21:17, Ralf Quint via Freedos-devel wrote: is one reason why I used to write my own asm routines for BIOS calls In this case it may be of interest how intr is actually implemented internally [1] :-). Yes, intr() is not the most efficient, but the most "portable" compiler-wise,

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

Hi Ralf, On 09.02.2024 20:02, Ralf Quint via Freedos-devel wrote: I can't see any reason as to why a data segment on a BIOS call should be set to any random value. For example, take this code (copied from FDISK source): static void Reset_Drive( int drive ) {    union REGPACK r;    memset( ,

[Freedos-devel] HTMLHELP

Hello, I uploaded Willis recent changes containing the HTML help 1.1.0 (English) to the unstable Gitlab repo [1]. The other languages are still shipped in version 1.0.8. This also contains version 5.3.6 of the HTMLHELP.EXE with several bugs fixed. Crashes and display corruptions should

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

On 05.02.2024 23:14, Ralf Quint via Freedos-devel wrote: Sorry, was just confused as to why all the sudden this was brought up. No one was harmed :-) I wanted to explain why I set DS to zero and probably went a bit off-topic by referring why the Watcom manual recommends it. The longer I

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

On 05.02.2024 23:01, Ralf Quint via Freedos-devel wrote: Sorry, but if this is indeed an 8088/8086 (or even a V20) CPU, there is no protected mode I did not claim that!?! This is about invoking interrupts from a high level language, following the recommendations of the compiler vendor,

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

On 05.02.2024 19:56, Bret Johnson wrote: That doesn't quite make sense, since 0 is just as much of a "garbage" segment as any other random selector It does! Because if you have a REGPACK as automatic object (on the stack), this likely contains random values for DS and ES. I am not that

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

The versions 0.9.4 - 0.9.8 of 8088_bios [1] seem to be affected by a bug I described in an GitHub issue [2]. It causes DS:0041 to be overwritten by the BIOS. Problem is, that DS points to whatever it is set when entering the BIOS and not to the BIOS data area. The bug is that the BIOS fails to

Re: [Freedos-devel] Bug: SET /E

Yes, that SET /E is a tricky beast. I am currently struggling to implement this for EDR command.com for the EDR-DOS fork at https://github.com/SvarDOS/edrdos. At first this seems to be easy to implement. But as always, the tasks that seem to be easy… I also had some thoughts of how to process

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

Hi Eric, > 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. I would only read kernel RAM directly if the kernel tells me the address, for

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

Hi, while hunting a FDISK  bug reported to me on Github regarding the order of the drive letters FDISK assigns, I noted that the FreeDOS Kernel actually supports different drive sorting algorithms via its DLASortByDriveNo config setting. While it is unrelated to the bug, this may impose a

Re: [Freedos-devel] FreePascal near to far pointer conversion

or the TP mode, and doing @Procedure or without the @. You can read the full details here, maybe someone has a hint: Far pointer versus Pointer in 16-bit DOS (freepascal.org) <https://forum.lazarus.freepascal.org/index.php/topic,60973.msg457397.html#msg457397> Thanks in advance, Aitor

Re: [Freedos-devel] FYI: Website update happening this week

Well done, one suggestion I oversaw the first time I looked at the new site: On https://freedos.org/about/devel/ I would change the order of the compilers, otherwise people could get the impression that DDS Micro-C, DeSmet C and the Digital Mars compilers are the ones which are commonly

Re: [Freedos-devel] Streamlining the next FreeDOS Test distribution

I'd like to add that it would be good to have the current kernel build included as the kernel of the interim builds, so that it can be tested. Perhaps the current kernel can be automatically fetched from the github actions page [1] or some other place while building the test images? Bernd

Re: [Freedos-devel] FreePascal near to far pointer conversion

On 12.11.2023 02:44, Rugxulo via Freedos-devel wrote: FarAddr internal function Thanks, that brings me further :-) I also changed my coding style from a more C oriented style to a more Pascal like. Unlike in C, one does not have to pass around (explicit) pointers that often. For example

Re: [Freedos-devel] FreePascal near to far pointer conversion

> > I believe int64 was originally from Delphi. (Isn't there also "long > long" support in OpenWatcom via "-za99“?) Hello Rugxulo, Yes, Watcom C supports 64-bit integer arithmetic, in contrast to Turbo C 3.1, which to my knowledge does not, but silently interprets „long long x“ as „long x“,

Re: [Freedos-devel] FreePascal near to far pointer conversion

> ancient versions of TP, like 3.0 on winworldpc, and I actually quite > like to go down memory lane once in a while, although I have ported > most of my projects to Watcom C by now. > > cheers, Hippo > > On Thu, 9 Nov 2023 at 23:44, Bernd Böckmann via Freedos-devel >

Re: [Freedos-devel] FreePascal near to far pointer conversion

Btw, when compiling in large memory model via fpc -Wmlarge the pointer errors when compiling keyb are gone. There are some 20 remaining compile errors. Perhaps these can be solved. Bernd On 09.11.2023 23:38, Bernd Böckmann via Freedos-devel wrote: Hello Aitor, > Could you please p

Re: [Freedos-devel] FreePascal near to far pointer conversion

Hello Aitor, > Could you please post the exact message you got from the compiler? For something like this "FarPointer(@Buffer)" I get the following error message: "Error: Illegal type conversion: "Pointer" to "FarPointer"" My opinion is that this should be supported by the compiler, because

Re: [Freedos-devel] FreePascal near to far pointer conversion

. Greetings, Bernd On 08.11.2023 20:57, Ralf Quint via Freedos-devel wrote: On 11/8/2023 11:40 AM, Bernd Böckmann via Freedos-devel wrote: Hi all, has anyone recently played around with the FreePascal 8086 cross compiler to generate DOS executables? I try to convert a near pointer to a far pointer

[Freedos-devel] FreePascal near to far pointer conversion

Hi all, has anyone recently played around with the FreePascal 8086 cross compiler to generate DOS executables? I try to convert a near pointer to a far pointer while working under the small memory model, but that is not as trivial as it should be, because I have not found a language /

Re: [Freedos-devel] FreeDOS Interim Build T2310 - no free space on CD

Hi, > Honestly, I'd prefer a 3-tier split, actually. The Base CD should be > somewhere around 300MB max. Is it really a good idea for a medium, which supports ~700 MB of data, to restrict that to 300 MB? Considering one has to „burn“ the media, I favour burning one disk instead of two or

Re: [Freedos-devel] Ré : T2308 invalid partition signature after format

I suspect the invalid partition signature is coming from SeaBIOS (QEMU BIOS). [Maybe the MBR itself?] It is the MBR code FDISK installs, which outputs the message. But my guess we could partition and format without rebooting if QEMU is detected. Don't know which hardware need a reboot after

Re: [Freedos-devel] Ré : T2308 invalid partition signature after format

Great to hear it is working now. > > So I was confused in thinking I had formated hard disk... I had it only > partitioned. (message was correct, just me bad interpreting it). Perhaps we should change the message in the installer to make this more clear? This problem seems to occur more often

Re: [Freedos-devel] T2308 invalid partition signature after format

Hi Paul, > While trying FDOS Live T2308.iso on QEMU under Fedora 38, I get a D: prompt, > I do setup, format the drive, reboot, but then I get: > partition signature != 55AA That message comes from the FreeDOS installed MBR boot code. So the first stage of the boot process - BIOS loads and

Re: [Freedos-devel] Interim Build Delayed

. Thanks for the hint! Bernd [1] http://amb.osdn.io/phpamb.php?fname=archiwum/format-20201216.amb [2] https://datatracker.ietf.org/doc/html/rfc1951 On 01.09.2023 20:00, C. Masloch via Freedos-devel wrote: On at 2023-09-01 19:03 +0200, Bernd Böckmann via Freedos-devel wrote: Well, I think it's me

Re: [Freedos-devel] Interim Build Delayed

Well, I think it's me to blame ;-) I will try to build some compression mechanism into AMB, so that the help files get smaller. The main FreeDOS help file would also benefit from that, I think. Bernd On 01.09.2023 16:49, Jerome Shidel via Freedos-devel wrote: Hi All, The FreeDOS Monthly

Re: [Freedos-devel] Updating/moving the wiki

On 27.08.2023 00:11, Jerome Shidel via Freedos-devel wrote: Unless everything is running on the same CMS, issues (like dead links) will crop up. But for the most part, perma-links and standardizing page names would take care of most of that. I was thinking about the wiki being recognized as

Re: [Freedos-devel] Updating/moving the wiki

On 26.08.2023 17:48, Jerome Shidel via Freedos-devel wrote: Would require manually glueing an index together of the projects with Wikis under a main “landing page” which could be a project like issue-reporting. Then point wiki.Freedos.org to that page. I would not recommend that. First, the

Re: [Freedos-devel] Virtual get-together?

> Am 30.07.2023 um 20:15 schrieb Jim Hall via Freedos-devel > : > > Let's try again next month. Is this today or another Sunday? Greetings, Bernd ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net

Re: [Freedos-devel] set device info

Hi Paul, I can reproduce this on T2307. It is running fine on a test image with self-build kernel (Git master, IA16-GCC) and alternative command shell (SvarCOM). The problem also does not occur under T2307 with SvarCOM as a shell. But I am not yet sure if it is the kernel or FreeCOM to blame.

[Freedos-devel] Free FDISK 1.3.8 released

Today I released FDISK 1.3.8 into the wild: https://github.com/FDOS/fdisk/tree/v1.3.8 The FDISK user interface is now translatable. Version 1.3.8 ships with translations for German, French and Turkish. Translation into Polish is in the works, and I also would like to have it available in

Re: [Freedos-devel] Second call for htmlhelp

Hi, a while ago I thought it would be useful, if programs can provide their own AMB (HTML) help files findable by the „help“ command. If I understand correctly, the help command as of now only works for commands contained in the global .AMB help file. The algorithm for „help appx" would be

Re: [Freedos-devel] Second call for htmlhelp

One additional note: We also have AMB. Willi, are the AMB files created manually or converted from the HTML files? In case the source is the same, we have to stick to the lowest common denominator. AMB spec for example states that line wrapping is an optional feature. Not sure if the current

Re: [Freedos-devel] Happy 29th anniversary to FreeDOS!

Jim, do you still have the original announcement? Would be an interesting read I guess. > Am 29.06.2023 um 19:44 schrieb Jim Hall via Freedos-devel > : > > In 1994, several of us got together around a pretty neat idea. > > We liked DOS, but Microsoft was clearly moving completely to Windows.

[Freedos-devel] FDISK 1.3.7 and HTMLHELP 5.3.6

Hi, I released FDISK 1.3.7. Apart from the re-introduced /AMBR command line argument, there are no significant changes. The /AMBR argument is used by some external tools, specifically the SvarDOS installer. https://gitlab.com/FreeDOS/base/fdisk/-/tree/1.3.7/ I also pushed HTMLHELP 5.3.6 to

Re: [Freedos-devel] HTMLHELP progress report

Hi Eric, > How much faster are Unicode and HTML entity translation now? The speed up of the table lookup is about factor 3. However, there are still some bottlenecks in the tag / entity substitution code (not the UTF to codepage translation). The code makes heavy use of memmove and realloc,

[Freedos-devel] HTMLHELP progress report

Hi, the last week I worked on HTMLHELP fixing various bugs, and initial tests by Fritz Müller and me give hope that the crashes and display corruptions are gone. The changes made so far, which will make it into the next FreeDOS interim build, are: ! Fix a heap corruption bug leading to

Re: [Freedos-devel] useful HTMLHELP bug findings and proposals

The most critical bugs are fixed by me as of now. I will continue working on it to have a new release for next FreeDOS interim release. Greetings, Bernd > Am 16.06.2023 um 19:41 schrieb Eric Auer : > > > Hi! > > Our GITLAB has recently received multiple useful tickets from Bernd Böckmann: >