Re: [Freedos-devel] mode.com

2023-03-19 Thread Ralf Quint
On 3/18/2023 7:49 AM, wilhelm.spi...@mnet-online.de wrote: Hi all, sometimes trying to write FD help makes me crazy. Mode is a typical example. At https://gitlab.com/FreeDOS/base/mode/-/blob/master/DOC/MODE/MODE.TXT there is a big explanation what the original mode.com from 1995 can do

[Freedos-devel] Ré : How to setup a compiler for FreePascal on Fedora Linux to FreeDOS 16 bit

2023-03-19 Thread Paul Dufresne via Freedos-devel
I said: > And now I am realizing that 80186 is kind of too advanced for FreeDos that > prefer 8086... but I think the older > FreePascal can do is 80186. They have done: [paul@fedora mypas]$ ls /usr/lib64/fpc/3.2.2/units/msdos/ 80186-compact 80186-medium 80286-compact 80286-medium

[Freedos-devel] How to setup a compiler for FreePascal on Fedora Linux to FreeDOS 16 bit

2023-03-19 Thread Paul Dufresne via Freedos-devel
I am thinking about using FreePascal to write programs for DOS. Writing an "hello world" program in FreePascal for 32 bit DOS (Go32) is easy, because the fpc package can be installed with fdimples from the Live installer. But there is no 16 bit FreePascal directly for DOS. So one have to used

[Freedos-devel] Bug or Not

2023-03-19 Thread Prime Seal
Mr J Hall here is the links to the video of FreeDOS after configuration. The errors after configuring fdauto.bat file YouTube: https://www.youtube.com/watch?v=h5_fXGL36yo Kind regards Seal Prime ___ Freedos-devel mailing list

Re: [Freedos-devel] I wish I had a boot.log file

2023-03-19 Thread Rugxulo
So you want a TEE utility? Or just to single step through it all (F8)? Try pressing the Pause key. (Yes, I know that's timing sensitive, sorry.) On Sun, Mar 19, 2023 at 10:30 AM Paul Dufresne via Freedos-devel wrote: > > So many messages on boot I cannot scroll back. > If only the boot process

Re: [Freedos-devel] I wish I had a boot.log file

2023-03-19 Thread Mercury Thirteen via Freedos-devel
It would be nice if FreeDOS had something like *nix's DMESG. Sent with [Proton Mail](https://proton.me/) secure email. --- Original Message --- On Sunday, March 19th, 2023 at 11:29 AM, Paul Dufresne via Freedos-devel wrote: > So many messages on boot I cannot scroll back. > If only

Re: [Freedos-devel] 386MAX

2023-03-19 Thread Rodrigo Morette
Hey all, I have been playing around with these sources, a minimal "working" build is possible with 386MAX.SYS and 386MAX.VXD. But there is a problem who inviabilizes an OSS build: 386MAX.VXD statically link 3 proprietary objects who seems to be from a development kit made by Microsoft:

Re: [Freedos-devel] Reminder: FreeDOS virtual get-together tomorrow (Sunday)

2023-03-19 Thread Jim Hall
Hi everyone! Here's the URL for the FreeDOS virtual get-together, starting in ten minutes: https://bluejeans.com/683879830/9370 See you there! On Sat, Mar 18, 2023 at 6:35 PM Jim Hall wrote: > > Hi everyone! I wanted to remind you that our next FreeDOS virtual > get-together is tomorrow

[Freedos-devel] I wish I had a boot.log file

2023-03-19 Thread Paul Dufresne via Freedos-devel
So many messages on boot I cannot scroll back. If only the boot process would also copy everything in a boot.log file!___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

[Freedos-devel] if exist %TEMP%\fdlive.dat goto CompletelyLoaded [not done]

2023-03-19 Thread Paul Dufresne via Freedos-devel
Testing FDT2303Live.iso in QEMU. Seems I always get: Cute mouse loaded then I think the line mentioned in title does not find fdlive.dat... So I always get the message: FDLIVE_ERROR: Unable to load all packages (probably need more ram) ... had given 2Gb of ram to -m 2048M of Qemu part of

Re: [Freedos-devel] watcom, was Re: Booting and FDAPM

2023-03-19 Thread Bernd Boeckmann via Freedos-devel
Hi Jerome, > At present, the RBE is not setup to include 2 branches from the same GitLab > project. > > It would require a separate GitLab project (with a different name, like > watcomv2). I think having two different watcom C packages could cause user > confusion on which one to install. It