Hi,
On Fri, Dec 1, 2017 at 11:00 AM, Bart Oldeman via Freedos-devel
wrote:
>
> On 22 November 2017 at 09:57, Tom Ehlert wrote:
>> as a side note: if gcc has no far pointers, its usability as a 16 bit
>> compiler is serious limited.
>
>
Hi,
On Sat, Nov 18, 2017 at 12:53 PM, Ralf Quint wrote:
> On 11/18/2017 10:46 AM, David McMackins wrote:
>> But isn't bcc proprietary, thereby undermining the entire goal here?
>>
> Contrary to the believes of the FSF, the world is full of C compilers
In fairness, GCC is
Intel Planning To End Legacy BIOS Support By 2020
"
By 2020, they will be supporting no less than UEFI Class 3, which
means only UEFI support and no more legacy BIOS or CSM compatibility
support mode.
"
https://www.phoronix.com/scan.php?page=news_item=Intel-Legacy-BIOS-EOL-2020
Hi,
On Sun, Nov 19, 2017 at 8:17 AM, Andreas K. Foerster <a...@akfoerster.de> wrote:
> Am Sonntag, dem 19. Nov 2017 schrieb Rugxulo:
>
>> Intel Planning To End Legacy BIOS Support By 2020
>
> HORRORS THE SKY IS FALLING!!! THE END OF THE WORLD IS NEAR
>
&g
Hi,
On Sun, Oct 29, 2017 at 9:36 PM, Ralf Quint wrote:
> On 10/29/2017 3:04 PM, Jim Hall wrote:
>>
> IMHO, screw the FSF. Seriously. It has turned into one of those almost
> religious fanatics entities that pretend to be "more pious than the
> pope" (a translation of a
Hi,
On Fri, Oct 20, 2017 at 1:56 AM, Eric Auer wrote:
>
> think should be moved to "Base" in "FreeDOS 2.0"?
>
>> * chksum (6 kb)
>
> How about some of our md5 and sha... sum implementations?
IIRC, Blair's md5sum.exe is 30 kb (UPX'd) while C. Dye's chksum is roughly 6 kb.
Hi,
On Fri, Oct 20, 2017 at 6:48 AM, Joe Forster/STA wrote:
>
>> How about some of our md5 and sha... sum implementations?
>
> I'm working on pdsum, something that started as an expansion of pdSFV
> but I completely rewrote it since. It compiles with Borland C++ 3.1 to 37
>
Hi,
On Sat, Jun 23, 2018 at 8:09 PM, David McMackins wrote:
>
> Finally, I also wrote a program called the Multi-Disk Split Archive
> Installer (MDSAI) which is an installer program designed for deploying
> software too big for a single floppy disk. You put the installer on the
> first diskette,
Hi,
On Sun, Jun 24, 2018 at 7:10 AM, David McMackins wrote:
>
> When I try to UPX it, I get an assertion failure. Apparently UPX has
> trouble with FreePascal executables. I think this additionally confirms
> another compiler was used.
The 8 kb existing, TP-compiled .EXE? Or do you mean newer
Hi,
On Sun, Jun 24, 2018 at 4:41 AM, Mateusz Viste wrote:
> On Sat, 23 Jun 2018 21:09:17 -0500, David McMackins wrote:
>
>> I've noticed that PASSWORD is written for FreePascal, but the executable
>> in the distribution is only 8k in size. When I compile myself, it is
>> 60k. How is it being
Hi,
On Sat, Jun 23, 2018, 9:09 PM David McMackins wrote:
> I've noticed that PASSWORD is written for FreePascal, but the executable
> in the distribution is only 8k in size. When I compile myself, it is
> 60k. How is it being stripped to that small size?
>
Depends, I haven't looked closely,
Hi,
On Wed, May 2, 2018 at 7:07 AM, Eric Auer wrote:
>
>> JEMM386 is basically for 16 bit programs.
Hardware EMS (expanded) on 8086s was before XMS (extended, 286+).
But obviously some programs still utilized EMS for many years (e.g.
many Borland tools themselves would use
Hi,
On Tue, May 1, 2018 at 6:26 AM, Ercan Ersoy wrote:
>
> I work on Open Watcom. I would like disable DOS/4G dependency on Open Watcom
> (32 bit DOS mode) for compiled executable files.
wcc386 is the 32-bit compiler while wcl386 is the 32-bit compiler +
linker
Hi,
On Wed, Oct 18, 2017 at 8:49 PM, Bret Johnson wrote:
>
> > On 10/17/2017 8:44 AM, Jim Hall wrote:
> >> (1) What does "Base" mean in 2017 or 2018? I think there are some
> >> packages we might take out of "Base" and move into a "Compat" package
> >> group, such as:
> >>
>
Hi again,
On Wed, Oct 18, 2017 at 5:36 PM, Jim Hall wrote:
>> On 10/17/2017 8:44 AM, Jim Hall wrote:
>
>>> (2) Are there other packages we should install "Base" by default? I
>>> don't want to make this a free-for-all, but perhaps there are some
>>> utilities that should be
Hi,
On Wed, Oct 18, 2017 at 4:25 AM, Kenway, Owain wrote:
>
> From: Jim Hall
> Sent: 17 October 2017 16:44
>
>> I've lately wondered what should come after FreeDOS 1.2. I think it's
>> time to talk about "FreeDOS 2.0."
>
>> (4) Is there anything missing in
Hi,
On Wed, Oct 18, 2017 at 5:58 PM, Jim Hall wrote:
>
> I posted this topic to the FreeDOS Facebook group, as well. Sharing
> some comments from our Facebook friends, to add to the discussion:
> (edited for clarity/brevity)
>
> - a floppy maintainance kit
> [I think this
Hi,
On Thu, Oct 26, 2017 at 12:37 PM, Jim Hall wrote:
>> On Thu, 26 Oct 2017, David McMackins wrote:
>>
>>> I have been informed that gcc has a -m16 flag that actually outputs
>>> binaries that can run in 16-bit mode. Is there then anything stopping
>>> FreeDOS from being
Hi,
On Fri, Oct 27, 2017 at 10:44 AM, Andreas K. Foerster
wrote:
>
> You can also use [BCC/Dev86] on a GNU/Linux system as a cross compiler.
> Use the option -Md to produce DOS binaries.
> (Note: the version in FreeDOS is older and doesn't have the program
> unprotoize
Hi,
On Fri, Oct 27, 2017 at 7:31 AM, Tom Ehlert <t...@drivesnapshot.de> wrote:
>
>> On Fri, 27 Oct 2017, Rugxulo wrote:
>
>> All of the TurboC ports should be deprecated in lieu of OpenWatcom
>> (or, better yet, DJGPP).
> it's not a TurboC port. in 2001 TurboC w
Hi,
On Fri, Oct 27, 2017 at 2:04 PM, Andreas K. Foerster <a...@akfoerster.de> wrote:
> Am Freitag, dem 27. Okt 2017 schrieb Rugxulo:
>
>> I may finally make a "package" from this one of these days. Is that okay?
>
> https://akfoerster.de/dl/software/dos/fdo
Hi,
On Wed, Jan 17, 2018 at 11:11 PM, Antony Gordon wrote:
>
> AFAIK no one on this project is interested in building a C compiler from
> scratch for
> the purposes of developing FreeDOS.
Nobody's directly working on such, AFAIK, unless you count SmallerC
(which is not DOS
Hi,
On Wed, Feb 7, 2018 at 11:28 AM, Matej Horvat
wrote:
>
> Georg's port has a couple of rough edges. It wastes power when idle (no INT
> 28h calls)
__dpmi_yield() would probably be best under DJGPP:
http://www.delorie.com/djgpp/doc/libc/libc_279.html
> and for
Hi,
On Wed, Feb 7, 2018 at 11:28 AM, Matej Horvat
<matej.hor...@guest.arnes.si> wrote:
> On Wed, 07 Feb 2018 17:12:56 +0100, Rugxulo <rugx...@gmail.com> wrote:
>
>> BTW, what Allegro are you using? Stock 4.2.2? Raine dude's patched
>> version? Other?
>
> How d
Hi,
On Wed, Feb 7, 2018 at 12:54 AM, Mark Olesen wrote:
>
> I am working on a project forking FLTK to run on FreeDOS.
>
> It is a work in progress but is coming around nicely.
Looks good!
BTW, what Allegro are you using? Stock 4.2.2? Raine dude's patched
version? Other?
Hi,
On Sat, Feb 3, 2018 at 4:44 AM, Bart Oldeman wrote:
>
> as some of you know I spent some time fixing various bugs in FreeCOM.
>
> So for testing I uploaded a new prerelease on github:
> https://github.com/bartoldeman/freecom/releases/tag/com084pre3
>
> There are three
Hi,
On Sat, Aug 11, 2018 at 12:22 PM, Tom Ehlert wrote:
>
> as an anecdote: in 2001, the official compiler was MSC 6.0 and MASM.
> nobody cared either, and everybody used happily the (free) Turbo C 2.01
> and TCPP 1.0.
IIRC, Pat V. himself wanted the kernel to be able to build with
relatively
Hi,
On Wed, Aug 15, 2018, 7:51 PM Bart Oldeman wrote:
>
> thanks again everybody for the feedback. I now updated the prerelease to
> pre5 with a few changes and bug fixes,
>
Thanks for your efforts, of course, but ... it's still got some bugs. The
Watcom build runs faster (oddly), but my
Hi,
On Fri, Aug 24, 2018 at 6:48 AM David McMackins wrote:
>
> > in that case, you are showing acute symptoms of stallmanitis.
>
> You can use slurs all you want.
Some people here are apparently not as pro Free Software as the rest
of us. Though it's (almost) impossible to be a zealot with DOS,
Hi, Tom,
I know this was not a great bug report. In fact, I wasn't trying to be
too specific, just mentioning that some random and confusing stuff was
happening. I didn't have time to isolate it yet. It was just a warning
that things weren't quite perfect yet. (But I appreciate your work,
Bart.)
Hi again,
On Mon, Aug 20, 2018 at 12:25 PM Tom Ehlert wrote:
>
> more experiments.
>
> METADOS is a very advanced, very spaghetti BATCH project,
> which in the end connects you with TCP, downloads components
> (MEM.EXE below) from the internet and more interesting stuff.
> unfortunately, *very*
Hi, Walter,
On Sun, Aug 26, 2018 at 4:01 PM Walter Bright wrote:
>
> To answer some questions:
>
> 1. Any code (source or binary) distributed as part of the Digital Mars C/C++
> development system that is copyrighted by Walter Bright, Digital Mars, or
> Symantec, is Boost licensed.
Good to
Hi,
On Wed, Aug 22, 2018, 7:07 AM Tom Ehlert wrote:
>
> as a side note: I have no experience with UNZIP.EXE in DOS, but I think
> it's performance pathetically slow. is this normal?
>
Under VM? Yes, "unzip" is specifically known to be much slower than normal.
I'm not exactly sure why. Like I
Hi,
On Mon, Jul 23, 2018 at 1:15 PM, Bret Johnson wrote:
>
> Multiple issues. First, if you're going to do it in "pure C", you can't
depend on anything like MMX.
MMX is deprecated in lieu of "better" SSE2, though. Of course, that demands
P4/AMD64, but most people have those by now. (I hate to
Hi,
On Tue, Jul 17, 2018 at 6:21 AM, TK Chia wrote:
>
> I have uploaded updated packages at
> https://github.com/tkchia/build-ia16/releases/tag/20180616-update-20180708 .
Okay, I've downloaded this now but haven't tried it yet.
Please don't feel pressure from me about this, but
Hi,
On Mon, Jul 23, 2018 at 5:58 AM, Eric Auer wrote:
>
> Hi! I am not sure whether I understand your method, so
> maybe you can explain it in more detail. Is the alpha
> mask 1 byte per pixel, either 00 or ff per pixel? The
> multiplication is costly.
Since when is MUL costly? Or only because
Hi,
On Mon, Jul 23, 2018 at 5:27 AM, Eric Auer wrote:
>
> Hi, just a quick extra idea: You could read about
> the PCX file format for 8-bit colors and define one
> color to be "opaque".
>
> https://www.fileformat.info/format/pcx/egff.htm
This reminds me of Benjamin David Lunt's webpage, where I
Hi,
On Mon, Jul 23, 2018 at 11:54 AM, David McMackins wrote:
>
> I have two oppositions to this. First, I'd like to be able to do this in
> pure C. Second, this appears to be a byte-level operation, but the whole
> point of doing this is to work on multiple bytes simultaneously.
>
> I think I
Gruess Gott,
On Tue, Jul 24, 2018 at 6:28 AM, Tom Ehlert wrote:
> Argh….
C'mon, Tom, it's not that burdensome, is it?
>> Anyhow, you said you wanted to do your code in “Pure C”. From my
>> personal experience, a lot of the information on the web pertaining to
>> very low level graphics
Hi,
On Tue, Jul 24, 2018 at 10:05 AM, TK Chia wrote:
>
> I am not sure if it is feasible to include truly "full" sources inside the
> FreeDOS packages. The complete patched GCC source tree is quite large even
> when xz-compressed (about 58 MiB), even after excluding some of the bigger
>
Hi, sorry for delay in testing this a bit,
On Mon, Sep 3, 2018 at 7:45 PM Bart Oldeman wrote:
>
> thanks again everybody for the feedback. I now updated the prerelease to
> pre6 with mostly bug fixes and one build system change
>
> I hope this is finally stable enough for me to remove the pre6
Hi,
On Wed, Jul 11, 2018, 6:29 AM David McMackins wrote:
> I'm trying to link a program as a COM executable, but when I add the
> "format DOS COM" directive to the linker, it complains that libraries
> aren't available (such as clibs.lib). It works fine and produces an EXE
> if I leave out this
Entschuldigung!
On Tue, Sep 11, 2018 at 8:12 AM Tom Ehlert wrote:
>
> > The GNUC version seems to mostly work,
I didn't quite have the time or energy to test TC or Watcom builds
yet. In fact, due to external circumstances, some tests
regressed/broke even with original (2006, TC) FreeCOM, which
Hi,
On Tue, Feb 27, 2018 at 9:34 AM, Tom Ehlert wrote:
> Hallo Herr Jim Hall,
>
> am 27. Februar 2018 um 16:13 schrieben Sie:
>
>> On Tue, Feb 27, 2018 at 9:05 AM, Tom Ehlert wrote:
>>>
>>> > I did find where it's hanging in MetaDOS. (0.84-pre4,
Hi,
On Tue, Feb 27, 2018 at 9:06 AM, Tom Ehlert <t...@drivesnapshot.de> wrote:
>> On Mon, Feb 26, 2018 at 4:56 PM, Rugxulo <rugx...@gmail.com> wrote:
>>>
>>> On Thu, Feb 22, 2018 at 11:37 AM, Bart Oldeman <bartolde...@gmail.com>
>>> wrote:
Hi, Tom,
On Tue, Feb 27, 2018 at 9:05 AM, Tom Ehlert wrote:
>
>> I did find where it's hanging in MetaDOS. (0.84-pre4, TURBOC, Feb. 22)
>
> whatever this METADOS is.
> it would be cool if you posted a METADOS.VHD somewhere so people can
> easier reproduce these reports.
Hi,
On Fri, Apr 13, 2018 at 2:12 PM, Bart Oldeman <bartolde...@gmail.com> wrote:
>
> On 26 February 2018 at 18:21, Rugxulo <rugx...@gmail.com> wrote:
>> There's another valid .BAT (P5.BAT) that says "Syntax error" and
>> hangs. I haven't looked into exac
Hi,
On Sun, Apr 8, 2018 at 1:14 PM, thraex wrote:
>
> [I] couldn't find the Turkish translations in the tarball of
> freecom-com084pre4 (in the strings directory).
>
> Is this the right place to mention these issues?
"Probably", but since the maintainer is Bart, you may
Hi,
On Thu, Feb 22, 2018 at 11:37 AM, Bart Oldeman wrote:
>
> thanks everybody for the feedback. I now updated the prerelease to
> pre4 with just a few changes:
>
> https://github.com/bartoldeman/freecom/releases/tag/com084pre4
I did find where it's hanging in MetaDOS.
Hi,
On Mon, Feb 26, 2018 at 4:56 PM, Rugxulo <rugx...@gmail.com> wrote:
>
> On Thu, Feb 22, 2018 at 11:37 AM, Bart Oldeman <bartolde...@gmail.com> wrote:
>>
>> thanks everybody for the feedback. I now updated the prerelease to
>> pre4 with just a few changes:
Hi,
On Thu, Oct 11, 2018 at 7:02 AM Tom Ehlert wrote:
>
> on 12. September 2018 um 03:14 schrieben Sie:
>
> > On Tue, Sep 11, 2018 at 8:12 AM Tom Ehlert wrote:
> >>
> >> > The GNUC version seems to mostly work,
>
> > I didn't quite have the time or energy to test TC or Watcom builds
> > yet.
>
Hi,
On Fri, Oct 19, 2018 at 11:04 PM Rugxulo wrote:
>
> > *
> > restart machine.
> >TESTS NASMWAT
> > all 3 report 'bad command or file name "tar.exe", but proceed
> > in the end,
Hi,
N.B. All tests I'm re-running below are using old stock 2006 TC build
of FreeCOM. I'm just telling you the times and success for rough
comparison of what I'm seeing and what is normally expected (by me).
BTW, "tests /t oberon16" succeeds and only takes 29 secs.
On Fri, Oct 19, 2018 at 12:16
Hi,
On Fri, Oct 19, 2018 at 10:59 AM Tom Ehlert wrote:
>
> > Here's the DropBox link (again), in case it wasn't obvious:
>
> > * https://www.dropbox.com/s/6whjgmb9xhdgw29/metados-0.7.zip?dl=0
>
> how in god name would that be obvious?
I already mentioned it explicitly. In fact, you asked me
Hi again,
On Fri, Oct 19, 2018 at 10:22 PM Rugxulo wrote:
>
> On Fri, Oct 19, 2018 at 10:59 AM Tom Ehlert wrote:
> >
> > run
> >TESTS JED
> >
> > this should download a lot of stuff, build JED, and keep the machine busy
> > for 10 minutes.
>
Hi,
On Wed, Nov 7, 2018 at 11:02 AM Joe Forster/STA wrote:
>
> > doslfn ... not sure if it's free/libre, but it's widely used. Of
> > course, there are other alternatives, too, of varying quality (e.g.
> > StarLFN).
>
> There's no able alternative for DOSLFN.
> Honestly, I think we can't afford
Hi again, Jim,
Just for completeness
On Wed, Nov 7, 2018 at 9:01 AM Rugxulo wrote:
>
> Of course, there are many other Invaders clones
> (e.g. one ported from QBASIC to XPL0
* http://www.xpl0.org/INVADERS.ZIP
"
This game is freeware. That is, it's free to use and distribut
Hi,
On Mon, Nov 12, 2018, 7:05 PM Jim Hall
> WHAT I NEED FROM YOU:
>
> - If you disagree with the status of any of these, please comment in a
> reply
>
> Summary of the yellow and red items:
>
> * red (do not include)
>
> 1. Archivers/lha
>
Again, I'm pretty sure those sources came from Debian.
Hi again, Jim,
On Sun, Nov 4, 2018 at 7:10 PM Jim Hall wrote:
>
> And there are these programs that I think should not be included in
> FreeDOS 1.3, and I marked those in red. I know we've included some of
> these in previous releases, but I don't think the licenses are really
> that free or
Hi, Jim,
On Sat, Nov 3, 2018 at 6:50 PM Jim Hall wrote:
>
> I have been working to create a list of packages for FreeDOS 1.3.
>
> I mentioned back in June (as part of a discussion thread about "Removing
> non-free packages")
> that I would like FreeDOS 1.3 to be as "open source" as possible.
>
Hi, Jim,
On Sat, Nov 10, 2018 at 5:55 PM Jim Hall wrote:
>
> On Wed, Nov 7, 2018 at 9:03 AM Rugxulo wrote:
> > lincrawl ... (aka, Linley's Dungeon Crawl) is something I used to play
> [..]
> > relicensed to GPLv2+." I know that's not exactly the same as saying
&
Hi,
On Sun, Nov 11, 2018 at 4:19 PM Steve Nickolas wrote:
>
> On Sun, 11 Nov 2018, François Revol wrote:
>
> > Nice to see some retro people interested in legal issues :-)
>
> Which reminds me...
>
> The other day I was looking for assistance in cleanrooming some pieces of
> MS-DOS 2.11 and 3.x
Hi,
On Mon, Nov 12, 2018, 2:24 PM Steve Nickolas On Mon, 12 Nov 2018, Rugxulo wrote:
>
> > However, AFAIK, "OpenDOS" (kernel and shell only) is "sources
> > available, non-commercial only". So not exactly free/libre, but at
> > least it's not illegal.
e more... If
> anyone needs this on a system only having a few MB HDD and a 3,5"
> floppy, there are better ways to get this onto.
I made a one-floppy (.7z-compressed) DJGPP install years ago:
* https://sites.google.com/site/rugxulo/DJGPP203.7Z?attredirects=0
I started in 2009 and
ou grabbed it from FTP incorrectly, ASCII instead of
Binary mode??) Here's what I get from a quick re-download from
iBiblio:
c:\rugxulo>md5sum untardos.exe
0858daf85c4b3401724bdf56ae227122 untardos.exe
c:\rugxulo>crc32 untardos.exe
0x6503EA89 (22,439)
__
Hi,
On Tue, Oct 2, 2018 at 12:24 PM stecdose wrote:
>
> I have tested untardos.exe, it is great. No problems with recent
> linux-stock-tar-and-gzip files created with "tar cvfz file.tgz folder".
> This makes automating a build process easy.
> But running it the first time on real hardware
Hi,
On Fri, Sep 28, 2018, 2:53 PM Tom Ehlert wrote:
>
> > One thing about coding style (it does not affect you - just something
> > that I noticed when reading code):
> > You have put your main() at the end. I want to get an overview of what
> > happens. I start scrolling down, but still
Hi,
On Sat, Sep 29, 2018 at 6:22 PM Steve Nickolas wrote:
>
> For what it's worth, I actually agree with Tom here, not that I've
> actually given anything of real significance to the FreeDOS project (other
> than the single disk distro I did 15 years ago).
I almost also said "or Steve" because
Hi,
On Sat, Sep 29, 2018 at 5:10 PM Tom Ehlert wrote:
>
> Dear Nils,
>
> > If something is unclear, please respond :)
>
> this mailing list is about FreeDOS development.
>
> please stop spamming the list with your projects because you are
> bored. We are not.
Tom, I am not aware of anybody else
Hi,
On Wed, Sep 19, 2018 at 5:21 AM stecdose wrote:
>
> I don't know which is the best place for this message. As it is about
> development I stick to freedos-devel. Is it ok to also send to
> freedos-user, because in the end it will affect users when used. And
> maybe users have suggestions for
Hi,
On Wed, Sep 26, 2018, 1:20 AM stecdose wrote:
> What type of machine do you use for FreeDOS you have tested on?
>
I mostly tested my old 2011 Lenovo desktop. But I also today went and
tested my old 2010 Dell laptop (native, clean boot of FreeDOS via USB).
Shows the same problems.
> Maybe
Hi,
On Sat, Sep 22, 2018, 11:42 AM stecdose wrote:
>
> when I was experimenting with dev86/bcc, I have written a small pong game
>
> The source quite easy to unterstand I think and this very short project
> shows on how to use bcc from linux to produce .com files
>
There are at least two
Hi,
On Wed, Sep 26, 2018, 12:46 AM stecdose wrote:
> Can you tell me which OS/Hardware or VM you are using?
>
Well, I tested old DOSEMU and DOSBox before trying native FreeDOS
unsuccessfully. Of course, it could be due to obscure bugs, configs, or a
mix of other pieces.
>
Hi,
On Fri, Sep 14, 2018, 8:49 AM Seth Simon wrote:
>
> In MS-DOS 6.22, neither "if exist ::\nul echo exist" nor "if exist Q:\nul
> echo exist" (where Q is a drive that doesn't exist) will cause anything to
> be echoed.
I know this is a common DOS idiom, but keep in mind that I don't recall
Hi, Bart, (off-list)
I know this is a very minor issue, but I'm just trying to be helpful.
I know it's not much, so feel free to ignore completely, it won't hurt
my feelings.
On Mon, Sep 3, 2018 at 7:45 PM Bart Oldeman wrote:
>
> I now updated the prerelease to pre6
>
>
Oops! Forgot to change the recipient address. ;-)
On Sat, Sep 15, 2018 at 4:36 PM Rugxulo wrote:
>
> Hi, Bart, (off-list)
Well, it's still on-topic, I just didn't want to pollute the thread
with such a silly suggestion. It's not really a bug report nor
(barely) worth worrying
Hi again,
On Mon, Aug 27, 2018 at 8:27 PM Rugxulo wrote:
>
> what ever happened to the GDC front-end being contributed to GCC?
> (Well, even GNU gm2 [Modula-2] still isn't in trunk ... yet.
Just to (half) answer my own question:
* https://gcc.gnu.org/wiki/cauldron2018#gdc
* https://gc
Hi yet again,
On Tue, Sep 18, 2018 at 2:19 PM Rugxulo wrote:
>
> * https://gcc.gnu.org/wiki/cauldron2018#gdc
> * https://gcc.gnu.org/wiki/cauldron2018#modula-2
>
> Unfortunately, only the latter has slides (and two very brief video
> clips about debugging with GDB).
"T
l. So I've
used it quite a lot over the years (mostly in DOS!).
(... discussion continued below ...)
On Tue, Mar 26, 2019 at 7:31 PM Rugxulo wrote:
>
> Gruess Gott,
>
> On Tue, Mar 26, 2019 at 1:20 PM Tom Ehlert wrote:
> >
> > > Developers are very sloppy and include lots
Hi,
On Fri, Feb 22, 2019 at 5:44 PM Rugxulo wrote:
>
> I also did some minor fixes to my (unpublished, prerelease 0.7) MetaDOS.
> (If anybody cares, I could just upload it, but it's still not perfect,
> obviously.
> FYI, "Newwget" isn't publicly available anymore, so
Hi,
On Tue, Apr 2, 2019 at 4:51 AM Tom Ehlert wrote:
>
> > On Fri, Feb 22, 2019 at 5:44 PM Rugxulo wrote:
> >>
> >> I also did some minor fixes to my (unpublished, prerelease 0.7) MetaDOS.
>
> > Nobody said anything, so I didn't worry about it. But I
Hi,
On Tue, Apr 2, 2019 at 4:51 AM Tom Ehlert wrote:
>
> > I thought you might find this interesting
> not at all ; see below.
Really? You don't find it a bit curious?
> btw: MSC was the reference compiler for freedos, some time ago.
Are you sure you don't mean Borland C?
Anyways, if you
did. I also wanted to
make sure it was known so people wouldn't "accidentally" keep
preferring the old, buggy (but admittedly freeware) compiler.
*
https://groups.google.com/forum/#!searchin/comp.os.msdos.programmer/rugxulo$20db%7Csort:date/comp.os.msdos.programmer/erSPwBbzXdc/4nj-zQcaAgAJ
Gruess Gott,
On Tue, Mar 26, 2019 at 1:20 PM Tom Ehlert wrote:
>
> > Developers are very sloppy and include lots of things that they don't
> > need. They also split up things into too many files. Too many
> > dependencies. I'm just saying, it's overwhelming, even for them.
I'm aware that this
Hi,
On Mon, Feb 25, 2019, 8:18 AM TK Chia
> I have put out a new release of FreeDOS packages for the gcc-ia16
> toolchain, at
> https://github.com/tkchia/build-ia16/releases/tag/20190224 .
>
Are you sure you set the prefix correctly? It seems to not find crtbegin.o
(etc). But maybe I'm doing
Hi,
On Fri, Feb 22, 2019 at 7:03 AM Tom Ehlert wrote:
>
> > so in the end the issue is a stack overflow:
>
> after 5 months since this (16 year old) bug was found, there is still
> no official command.com for everybody else to test.
>
> there are also 3 located, and easy fixable bugs in the
Hi,
On Sat, Mar 9, 2019 at 6:49 AM Jerome Shidel wrote:
>
> > On Mar 8, 2019, at 9:40 AM, Eric Auer wrote:
> >
> > As DOS barely supports any overlay stuff, another question would be
> > which FreeDOS packages work directly from read-only media.
> > My guess is: MOST will!
>
> I agree that most
Hi again,
On Sat, Mar 9, 2019 at 9:15 AM Jerome Shidel wrote:
>
> > On Mar 9, 2019, at 8:19 AM, Eric Auer wrote:
>
> > And how big would the 3 largest packages in that ramdisk be? Which 3
> > packages?
>
> I don’t know off-hand. But, things like FPC & DJGPP are enormous.
> However, both of
Hi,
On Sat, Mar 16, 2019 at 11:10 AM TK Chia wrote:
>
> > Have you seen this before?
> >
> > * https://github.com/DarkWishMaster/TinyStdio
> > * http://www.sparetimelabs.com/tinyprintf/tinyprintf.php
>
> Anyway, what problems exactly did you come across in using the TinyStdio
> code?
I wasn't
Hi,
On Sun, Mar 10, 2019 at 8:26 AM TK Chia wrote:
>
> I have uploaded a new set of FreeDOS packages of the gcc-ia16 toolchain,
> at https://github.com/tkchia/build-ia16/releases/tag/20190310 .
Have you seen this before? (Honestly, I tried but failed to use it
correctly here. I'll have to try
Hi, Stas,
On Thu, Mar 14, 2019 at 5:56 PM Stas Sergeev wrote:
>
> As you probably know, once upon a time (like
> 20 years ago) there were the command.com sources
> from Centroid Corp under GPL. AFAIK they were
> removed from the freedos servers because of the
> licence uncertaincy.
I'm not
Hi, guys,
On Sun, Jan 27, 2019 at 6:35 PM Jim Hall wrote:
>
> Thanks for sharing! This is great stuff, so I've tweeted it from the FreeDOS
> twitter and just posted a news item about it on the website.
>
> On Fri, Jan 25, 2019 at 7:23 AM Eric Auer wrote:
>>
>> Hi DOS developers :-)
>>
>> As
Hi, just to discuss a bit off-topic (well, non-Python) programming
On Fri, Jan 25, 2019 at 9:09 AM Pär Moberg wrote:
>
> Is there a python 3 implementation for dos?
> I saw circuitpython and micropython and thought that they would be portable
> to dos since
> they run on quite limited
Hi,
On Fri, Jan 25, 2019 at 9:56 AM Bart Oldeman wrote:
>
> no, DOS support was bitrotted and then removed for Python 3.5
> (https://bugs.python.org/issue22591) in 2014. Newest full Python you
> can get is Python 2.4.2 at http://www.caddit.net/pythond/, but that's
> a long way before python 3.
>
Hi,
On Tue, Jan 29, 2019, 4:40 PM Matej Horvat On Tue, 29 Jan 2019 23:20:21 +0100, Rugxulo wrote:
>
> > There also was a guy, a few years ago, who was building ("Lightning")
> > Python for Win32 via OpenWatcom. I never tried it, but that would
> > probably
Hi again,
On Tue, Jan 29, 2019, 3:57 PM Pär Moberg I am looking for Python 3 since then I only need to learn python 3 to
> program on Raspberry Pi (with GPIO and GUI), My desktop (with GUI),
> CircuitPython (with GPIO) and DOS (with ?).
>
> So that is why I want Python 3/CircuitPython.
>
There
Saluton,
On Sun, Apr 14, 2019 at 7:16 AM Ivan Ivanov wrote:
>
> сб, 13 апр. 2019 г. в 08:46, Rugxulo :
> >
> > Perhaps you need to try a different floppy image? I could point you to
> > several
>
> Yes, if they could help to debug this issue.
Not directly
Hi, Ivan,
On Sat, Apr 6, 2019 at 12:44 PM Ivan Ivanov wrote:
>
> I built a coreboot BIOS image for QEMU and added to it the
> FD13FLOP.IMG (renamed to freedos.img) :
>
> Tried booting it but it gets stuck after
> "Done processing startup files FDCONFIG.SYS and FDAUTO.BAT"
> _ <--- blinking "_"
>
Hi,
On Thu, May 30, 2019 at 5:17 PM Steve Nickolas wrote:
>
> On Thu, 30 May 2019, Andreas Berger wrote:
>
> > This is slightly off topic, but can someone recommend a TCP and UDP library
> > for FreeDOS. I need it to Compile or Link to the 32-bit OpenWatcom C++
> > compiler.
> >
> > It doesn't
Hi,
On Sun, Jun 2, 2019 at 11:37 PM Mercury Thirteen via Freedos-devel
wrote:
>
> Darn. I was hoping that, in light of the early MS-DOS clone market, there was
> something maybe released by a third party
> to help users determine if their DOS was MS-DOSsy enough. A reach, I know,
> but... oh,
401 - 500 of 604 matches
Mail list logo