t 3 PCIe sound cards advertised as DOS/SB compatible
> and none have worked. Perhaps we need a list of working PCIe cards?
>
> I have a MB bookmarked on ebay, maybe I should take on a winter project
> and build my own machine?
>
>
> On Wed, Nov 11, 2015 at 2:55 AM, Mateusz Vist
On 14/11/2015 02:12, Geraldo Netto wrote:
> while (1) {
>Alain++;
> }
That will inevitably lead to an overflow. Probably wasn't the primary
intention.
Mateusz
--
___
Free
On 15/11/2015 14:30, Don Flowers wrote:
> I have been reinstalling FreeDOS and have my NIC card setup,
> I have a working connection (am writing this from my DILLODOS browser)
> but cannot get a download from FDNPKG. I can download to my HD and then
> install
> but FDNPKG is stalling.
Are you us
Hello group,
I write this message to share a little news about what I was doing in my
spare time these last two months: porting picoTCP to DOS.
picoTCP is a modern, dual-stack, open-source TCP/IP stack. It has been
created by the good people at Intelligent Systems (Altran), primarily as
a stac
Hi Tom,
On 20/11/2015 13:17, Tom Ehlert wrote:
> a) you forgot to publish the source for picotcpl.lib and
> picodosl.lib
No, I did not. The source archive contains everything that is necessary
to build picodosl.lib (have you tried? just type 'wmake').
picotcpl.lib, on the other hand, is the "sto
sk of fs
trashing).
http://fdnpkg.sourceforge.net
Mateusz Viste
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-i
racted correctly (v0.99.2
>> regress),
>> - [fix] closing file descriptors on install failure (no risk of fs
>> trashing).
>>
>> http://fdnpkg.sourceforge.net
>>
>> Mateusz Viste
>>
>>
>>
> --
, Nov 24, 2015 at 11:44 AM, Mateusz Viste <mailto:mate...@viste.fr>> wrote:
>
> On 24/11/2015 16:32, Dale E Sterner wrote:
> > Is there an Ibiblio link?
>
> As usual, yes :)
>
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distribution
inaries. I eventually extracted the
> "boot.img" and copied the new fdnpkg files to it and the extracted
> the "all_cd" files to a directory on my hard drive and adjusted the
> FDNPKG.CFG file. It works fine this way, but I never had a problem
> with the all_cd befor
On 25/11/2015 18:59, Karen Lewellen wrote:
> does anyone know of a boot management comparative to say grub, that
> runs in pure DOS?
> as in a tool that would let me, if I choose, load another edition of
> an operating system that has been installed on a different partition?
The boot manager i
extract. I have not yet tried
> this after creating the on-disk repo.
>
> I am now iin the midst of Thanksgiving prep, so I will try another
> clean install over the weekend.
>
> On Wed, Nov 25, 2015 at 12:23 PM, Mateusz Viste <mailto:mate...@viste.fr>> wro
picoSNTP is an SNTP client for DOS. It allows to easily synchronize the
computer's RTC clock using an external NTP server. picoTCP is based on
the picoTCP network stack.
Requirements:
- 8086
- 200K of free RAM
- a working packet driver
- a properly configured picoTCP environment
http://
Hi all,
With some luck, we could imagine having a v1.2 release somewhere next
year. But this won't happen without more people chipping in. There are
plenty of things that would need to be done, and that do NOT require any
development skills. If you wish to give some of your time, look at the
l
Hi Eric,
Nice to see you're still around fixing stuff :)
There is one little inconvenience I experienced with MODE, that I
reported earlier this year while working on my Svarog86 distribution.
It relates to MODE executing 'MODE MONO' without checking that it will
actually work (leading to scre
On 17/12/2015 20:05, Ralf Quint wrote:
> On what kind of system are you testing this?
I tested it on my "Toshiba T1100 Plus" portable computer. It's an
8088-based computer with an onboard CGA clone.
I can do further tests if necessary, if provided with specific
instructions what to test.
Mateu
I'm going with Louis on this one. When installing FreeDOS, I'd expect
the installer to overwrite my MBR with clean boot code, so I don't have
any troubles booting FreeDOS post install. That's what MS-DOS did, and
that's what I expect from any OS in fact.
Naturally, an appropriately big warning
Hi,
IIRC, FreeDOS 1.1 is broken by default when it comes to package
management. Hopefully v1.2 will work better.
As for now, you'd have to install packages via FDNPKG first, and only
then these packages will be detected and handled properly.
Example: FDNPKG INSTALL MEM
To answer your second qu
Looks neat! Any chance for having it released with clear authorship, and
some generic license? (say, 2-clause BSD for instance, to keep things small)
Does the tool check that it acts on a supported CPU before operating?
Performing such low-level actions on unsupported CPUs could have very
unexp
Hello list,
Short message to let you know I released a new 'bugfix' version of picoSNTP.
http://picosntp.sourceforge.net/
picoSNTP v0.9.1 fixes an obvious bug that I somehow missed the first
time (shame on me). Specifically, picoSNTP was synchronizing the
system's *time* fine, but not the *dat
I looked into my USB stuff, and I see I have:
1x 32M CompactFlash card
1x 128M USB pendrive
2x 512M SD card
1x 1G micro SD card inserted inside some USB "pendrive adapter"
Hence if I'd want to test anything, I wouldn't have any medium big enough.
Why not proposing the 2G image additionally to th
Hi,
I tested FDI, and - in general - it looks really awesome. I list below
all my remarks.
*** 1st Screen ***
"Please select you language." - this should be "youR language".
the language names that change when I pass on them are quite...
confusing. maybe it's just me, but I'd really prefer to
Hello all,
Some of you might recall a smallish 8086-tailored FreeDOS distribution I
did some time ago, called Svarog86. Today, I present Svarog386 - a much
more generic FreeDOS distribution, targeted to 386+ computers.
Why would I need to create my own distro, instead of relying on vanilla
Fre
On 17/05/2016 14:23, Tom Ehlert wrote:
> an operating system without CDROM and network drivers doesn't sound
> very useful to me, even if everything has the correct license. YMMV.
I think that the key is to perceive FreeDOS as a replacement to MSDOS,
nothing else (that is, "BASE"). The legalese o
Hello,
I'm glad to announce that DOSMid has been released in an updated version
today.
DOSMid v0.9 [21 May 2016]
- increased SYX delaying to 40ms (solves buffering troubles on MT-32
gears),
- fixes around how OPL percussion instruments are emulated,
- support for custom sound banks (IBK o
On 22/05/2016 21:10, Ralf Quint wrote:
> I think what the author mentions does apply in an even greater range to
> FreeDOS
>
> http://www.techrepublic.com/article/time-linux-fans-open-their-arms-to-closed-source/
I agree with the author, but I fail to see the point you are trying to
make regardin
Hi Don,
You might want to read the FreeDOS wiki article that describes the
package structure:
http://freedos.sourceforge.net/wiki/index.php/Package
Shortly answered, the "link" files are a recent feature of FDNPKG, that
makes it possible to make programs runnable within %PATH% without the
need
I might be missing the boat here, but what you describe vaguely look
like a problem I had in some distant past, when I misconfigured my HDD
in the BIOS.
Perhaps you could check whether your drive's geometry is 100% correct in
your BIOS?
Mateusz
On 19/07/2016 07:12, Dimitris Zilaskos wrote:
On 22/07/2016 10:34, Tom Ehlert wrote:
>> (Honestly, FreeCOM needs to be better optimized for size and then we
>> wouldn't have to worry at all. That is one of our weakest links.)
>
> seriously: command.com has ~3 K resident size. what are you
> complaining about?
This implies swapping capability,
On 24/08/2016 12:47, Ulrich Hansen wrote:
> I found that the intel DOS packet driver for the PRO/1000 network card
> isn’t in the CRYNWR package.
>
> As it is Open Source since 2007 I felt free to package it into an FDNPKG
> compatible zip-file.
>
> You can find it here:
> https://github.com/ulrich
As other said, you need to be sure to use a 8086 compilation of the
FreeDOS kernel. As an easy test you might want to try out Svarog86,
which is a FreeDOS distribution built specifically for 8086 compatibility:
http://svarog86.sourceforge.net/
Mateusz
On 28/10/2016 19:04, Simon Atkinson wrot
Hello all,
For those of you who followed my Svarog386 project: you might find it
interesting that the current version of Svarog386 comes with a multi-
lingual installer. This makes the installation process much more user-
friendly. The distribution also comes in an additional, alternative
"micro
On Fri, 30 Dec 2016 17:44:47 +0100, userbeitrag wrote:
> What I can do thou is plug the IDE HDD into another PC and pre-load
> FreeDOS there. Then, connecting the IDE HDD inside the 486-PC, FreeDOS
> should start.
That's correct, if done carefully. You have to make sure tough that both
computers
Sounds like the CHS data you noted down might not be "true" CHS (if we
can talk about "true" CHS at all on a flash device...), but rather LBA-
assisted or "Large-shifted" geometry. Have you forced the disk mode in
your ~2000 PC when doing the auto-detection? If not, it probably uses LBA
by defau
On Sun, 01 Jan 2017 22:44:38 +0100, E. Auer wrote:
> One-Time ONLY update of the 5-Mar-2015 drivers provided from SourceForge
> IBiblio.
Does this mean it's actually an update of the open-source branch (with
source code, GPL and all)? Too bad distribution is so restricted.
Mateusz
On Thu, 19 Jan 2017 17:40:03 -0500, Jerome Shidel wrote:
> Other than install and remove, I don’t think
> FDNPKG & FDINST do anything with them.
FDNPKG & FDINST only read the LSM files indeed, and they are designed to
handle both CR/LF and LF line endings ("a line ends with a single LF" +
"if it
Hi all,
I write this short announcement to present an alpha version of a new
software I have been creating these past weeks. EtherDFS is an
"installable filesystem" for DOS. It installs a network drive that is
seen like any "normal" drive to DOS and its application, with the
exception that the
On Thu, 02 Feb 2017 19:09:28 +0100, Tom Ehlert wrote:
> may I suggest to use UDP/IP instead of raw packets?
Hi Tom,
It's a more common suggestion than you might think :) That's why I
covered this already in the documentation:
https://sourceforge.net/p/etherdfs/code/HEAD/tree/etherdfs/trunk/etherd
I am pleased to announce that EtherDFS reached v0.6.
This updated version brings a few bugfixes and memory optimizations: resident
footprint is 7K now (was: 16K).
http://etherdfs.sourceforge.net
Mateusz
On Tue, 31 Jan 2017 09:19:05 +, Mateusz Viste wrote:
> Hi all,
>
> I write t
Hello group,
Today I released a new program I was working on these past weeks: DWOL.
DWOL is a tiny tool that computes and sends "wake-on-lan" packets. Wake-
On-LAN (WOL) is an Ethernet standard that allows a computer to be turned
on by a network message. DWOL is designed with two goals: being t
Hello,
I needed to verify the integrity of a few files after transferring them
to/from my 8086 PC the other day. The obvious method for such task is
computing a checksum of the file, like MD5, SHA1, etc... However, on an
8086 this may take ages (even on a fairly fast 386, computing the MD5 sum
BSUM (by Mateusz Viste) : 6.0s (100%)
CRC32 (by Joe Forster) : 8.5s (70%)
CRC32 (by Colin Plumb) : 26.7s (22%)
MD5 (by Colin Plumb): 52.9s (11%)
SHA1 (by Colin Plumb) : 85.7s (7%)
BSUM is the fastest, which is no surprise since the algorithm is
extremely simple (4 CPU instructions
On Mon, 10 Apr 2017 17:57:59 -0400, dmccunney wrote:
> I have to ask. How many folks *have* platforms now it *wouldn't* run
> on? I suspect the number is *very* small.
Surely, yes. Still, a 700% memory increase for a 10% performance boost
just doesn't feel right. I wrote bsum to cover an extreme
On Mon, 10 Apr 2017 17:07:30 -0500, Rugxulo wrote:
> Blair's (16-bit, FD) MD5SUM can do all of those hashes as well. Not sure
> if it'd be faster, though.
I believe that's the one I used. If I understand correctly, the original
author is Colin Plumb, and Blair took the maintenance of it at some p
On Tue, 11 Apr 2017 02:52:06 +, Mateusz Viste wrote:
> On Mon, 10 Apr 2017 17:07:30 -0500, Rugxulo wrote:
>> Converting hex nibble to ASCII shouldn't need a jump at all. On the
>> 8086 all jumps are very slow. Best to avoid them entirely if possible.
>> Here you can
frustrated, and just good enough to be reasonably sure that the
files I just copied from a diskette and then over network-through-
parallel-port didn't get corrupted in the process.
Mateusz
On Mon, 10 Apr 2017 09:48:41 -0700, Ralf Quint wrote:
> On 4/10/2017 6:36 AM, Mateusz Viste wrot
On Mon, 10 Apr 2017 23:30:35 -0500, Rugxulo wrote:
> Unless I'm mistaken, conditional jumps on 8086 don't go beyond -128 ..
> 127 (signed) byte range. Hence the billions of workarounds (TASM
> "jumps", MASM "option ljmp", etc).
I won't argue about what opcode is or is not available on 8086, since
On Tue, 11 Apr 2017 02:03:54 -0500, Rugxulo wrote:
> AFAIK, the longer one is 386+ only, hence not available with "cpu 8086".
The above code assembles with "cpu 8086" (NASM 2.12.02).
> Thus, if it still quietly assembles, that is a bug (but I thought that
> was long-ago fixed/avoided).
Perhaps a
On Mon, 10 Apr 2017 23:21:26 +0200, Eric Auer wrote:
> For checking if downloads worked without noise, I would already want
> something "stronger" than BSUM, such as
>
> https://en.wikipedia.org/wiki/Fletcher%27s_checksum
As already stated in this thread a few times, the BSD checksum is far
from
Hi Tom,
That's nice of you to provide the explanation. I didn't read it
completely (too lazy), nor understand it fully (too stupid), but the
other clueless guy might find it interesting that he was only half wrong.
At the end of the day, I will keep using "JZ SHORT" anyway, 'cause that
just wo
On Tue, 11 Apr 2017 22:24:56 -0500, Rugxulo wrote:
> My problem with always explicitly saying "short" is that it's both
> unnecessary and verbose.
Apparently not so "unnecessary" after all, if one really wants to use a
short jump, and not some other contraption.
> What disassembler are you using
On Wed, 12 Apr 2017 04:39:35 -0500, Rugxulo wrote:
> It worked fine (redirecting) for me yesterday! I can't imagine why it
> wouldn't work for you.
>
> Oh, before I forget, are you perhaps invoking NDISASM via some .BAT?
> Of course a .BAT doesn't really redirect (under FreeCOM) without kludge,
>
Hello group,
Not that long ago I announced here a new software I have created, named
EtherDFS. EtherDFS is an 'installable filesystem' TSR for DOS. It maps a
drive from a remote computer (typically Linux-based) to a local drive
letter, using raw ethernet frames to communicate.
Last weekend I r
On Mon, 10 Apr 2017 10:37:44 -0400, Dale E Sterner wrote:
> Would you or anyone else know if there is an 802.11 client for dos?
> Never heard of one but you guys know alot more than I ever will.
I don't think there is such thing as a "802.11 client" - it only depends
whether or not the given wifi
"something boots", before reinstalling a modern OS.
Mateusz
> On Wed, 19 Apr 2017 10:50:04 + (UTC) Mateusz Viste
> writes:
>> On Mon, 10 Apr 2017 10:37:44 -0400, Dale E Sterner wrote:
>> > Would you or anyone else know if there is an 802.11 client for
>
g to the *same* file at the same time from
two different clients is almost guaranteed to wreck things up.
Simultaneous reads, of course, are no trouble.
Mateusz
> On Wed, Apr 19, 2017 at 5:06 AM, Mateusz Viste
> wrote:
>
>> Hello group,
>>
>> Not that long ago I a
From: Mateusz Viste
On 24/08/2016 12:47, Ulrich Hansen wrote:
> I found that the intel DOS packet driver for the PRO/1000 network card
> isnAt in the CRYNWR package.
>
> As it is Open Source since 2007 I felt free to package it into an FDNPKG
> compatible zip-file.
>
>
From: Mateusz Viste
As other said, you need to be sure to use a 8086 compilation of the
FreeDOS kernel. As an easy test you might want to try out Svarog86,
which is a FreeDOS distribution built specifically for 8086 compatibility:
http://svarog86.sourceforge.net/
Mateusz
On 28/10/2016 19:04
From: Mateusz Viste
Hello all,
For those of you who followed my Svarog386 project: you might find it
interesting that the current version of Svarog386 comes with a multi-
lingual installer. This makes the installation process much more user-
friendly. The distribution also comes in an
From: Mateusz Viste
On Fri, 30 Dec 2016 17:44:47 +0100, userbeitrag wrote:
> What I can do thou is plug the IDE HDD into another PC and pre-load
> FreeDOS there. Then, connecting the IDE HDD inside the 486-PC, FreeDOS
> should start.
That's correct, if done carefully. You hav
From: Mateusz Viste
Hi all,
I write this short announcement to present an alpha version of a new
software I have been creating these past weeks. EtherDFS is an
"installable filesystem" for DOS. It installs a network drive that is
seen like any "normal" drive to DOS and its a
From: Mateusz Viste
On Thu, 02 Feb 2017 19:09:28 +0100, Tom Ehlert wrote:
> may I suggest to use UDP/IP instead of raw packets?
Hi Tom,
It's a more common suggestion than you might think :) That's why I
covered this already in the documentation:
https://sourceforge.net/p/ether
From: Mateusz Viste
I am pleased to announce that EtherDFS reached v0.6.
This updated version brings a few bugfixes and memory optimizations: resident
footprint is 7K now (was: 16K).
http://etherdfs.sourceforge.net
Mateusz
On Tue, 31 Jan 2017 09:19:05 +, Mateusz Viste wrote:
> Hi
From: Mateusz Viste
Hello group,
Today I released a new program I was working on these past weeks: DWOL.
DWOL is a tiny tool that computes and sends "wake-on-lan" packets. Wake-
On-LAN (WOL) is an Ethernet standard that allows a computer to be turned
on by a network message. DWOL i
From: Mateusz Viste
On Mon, 10 Apr 2017 00:56:17 -0500, Rugxulo wrote:
> It would be interesting to see some benchmark numbers for that (for
> various specific tools, 8086, 386, etc).
Just for the fun of it, I did some quick measures on my 386SX PC,
computing various checksums of a 2 Mi
From: Mateusz Viste
Hello,
I needed to verify the integrity of a few files after transferring them
to/from my 8086 PC the other day. The obvious method for such task is
computing a checksum of the file, like MD5, SHA1, etc... However, on an
8086 this may take ages (even on a fairly fast 386
From: Mateusz Viste
I have to clarify here that my intention was never to compete in any way
with the other algorithms out there. The BSD checksum is a well-known,
and pretty weak (16 bits) checksum. The goal behind bsum was only to
obtain a checksum tool that would run on my 8086 fast enough
From: Mateusz Viste
On Tue, 11 Apr 2017 02:52:06 +, Mateusz Viste wrote:
> On Mon, 10 Apr 2017 17:07:30 -0500, Rugxulo wrote:
>> Converting hex nibble to ASCII shouldn't need a jump at all. On the
>> 8086 all jumps are very slow. Best to avoid them entirely if possi
From: Mateusz Viste
On Mon, 10 Apr 2017 17:57:59 -0400, dmccunney wrote:
> I have to ask. How many folks *have* platforms now it *wouldn't* run
> on? I suspect the number is *very* small.
Surely, yes. Still, a 700% memory increase for a 10% performance boost
just doesn't fee
From: Mateusz Viste
On Mon, 10 Apr 2017 23:30:35 -0500, Rugxulo wrote:
> Unless I'm mistaken, conditional jumps on 8086 don't go beyond -128 ..
> 127 (signed) byte range. Hence the billions of workarounds (TASM
> "jumps", MASM "option ljmp", etc).
I won
From: Mateusz Viste
On Mon, 10 Apr 2017 17:07:30 -0500, Rugxulo wrote:
> Blair's (16-bit, FD) MD5SUM can do all of those hashes as well. Not sure
> if it'd be faster, though.
I believe that's the one I used. If I understand correctly, the original
author is Colin Plum
From: Mateusz Viste
On Mon, 10 Apr 2017 23:21:26 +0200, Eric Auer wrote:
> For checking if downloads worked without noise, I would already want
> something "stronger" than BSUM, such as
>
> https://en.wikipedia.org/wiki/Fletcher%27s_checksum
As already stated in this threa
From: Mateusz Viste
Hi Tom,
That's nice of you to provide the explanation. I didn't read it
completely (too lazy), nor understand it fully (too stupid), but the
other clueless guy might find it interesting that he was only half wrong.
At the end of the day, I will keep using "J
From: Mateusz Viste
On Tue, 11 Apr 2017 02:03:54 -0500, Rugxulo wrote:
> AFAIK, the longer one is 386+ only, hence not available with "cpu 8086".
The above code assembles with "cpu 8086" (NASM 2.12.02).
> Thus, if it still quietly assembles, that is a bug (but I t
From: Mateusz Viste
Hello group,
Not that long ago I announced here a new software I have created, named
EtherDFS. EtherDFS is an 'installable filesystem' TSR for DOS. It maps a
drive from a remote computer (typically Linux-based) to a local drive
letter, using raw ethernet
From: Mateusz Viste
On Wed, 12 Apr 2017 04:39:35 -0500, Rugxulo wrote:
> It worked fine (redirecting) for me yesterday! I can't imagine why it
> wouldn't work for you.
>
> Oh, before I forget, are you perhaps invoking NDISASM via some .BAT?
> Of course a .BAT doesn
From: Mateusz Viste
On Mon, 10 Apr 2017 10:37:44 -0400, Dale E Sterner wrote:
> Would you or anyone else know if there is an 802.11 client for dos?
> Never heard of one but you guys know alot more than I ever will.
I don't think there is such thing as a "802.11 client" - it
From: Mateusz Viste
On Wed, 19 Apr 2017 11:14:21 -0400, Dale E Sterner wrote:
> I see that someone on Ebay is selling an HP mini with a FREEDOS os
> installed. All the HP minis that I've seen have wifi & bluetooth built
> in. That would mean an 802.11 client to do it. The
From: Mateusz Viste
On Mon, 24 Apr 2017 21:11:25 -0400, Andy Stamp wrote:
> I set up a Linux VM with a FAT32 partition for the server and was
> playing with version 0.8.1 on my 486 and it was working great. Loaded
> Lotus 123 right off the network (and faster than I expected).
I'm
Hello,
Recently I released a new version of DOSMid (version 0.9.2), with
following changes:
DOSMid v0.9.2 [06 Jun 2017]
- fixed parsing of the /SBMIDI=xxx value (bug reported by James-F),
- sequential playlist playing (inspired by a patch from Graham Wiseman).
homepage: http://dosmid.source
On Fri, 03 Nov 2017 12:23:55 +0100, Eric Auer wrote:
>>> Quick news from /dev/null 's drivers: [etc. rant etc.]
>
> In short, you said "nag nag nag" ;-)
While it's obviously true that Rugxulo have some ranting issues, I don't
see any reason to promote proprietary software on the FreeDOS list
ei
On Sat, 04 Nov 2017 00:17:18 +, Dimitris Zilaskos wrote:
> Jack's drivers are required on a number of dos-era systems else FreeDOS
> will not even install/boot.
If it won't install nor boot, then how would you use any drivers in the
first place?
Any bug reports?
> Being unable to use FreeDOS
On Sat, 04 Nov 2017 20:09:48 +0100, userbeitrag wrote:
> I'm also thinking that FreeDOS should include a not-so-free and even a
> non-free section of software. The only limit should be restriction of
> redistribution.
I'm afraid this is contrary to the FreeDOS spirit. That being said, there
is at
On Sun, 05 Nov 2017 16:48:00 +0100, userbeitrag wrote:
> What I'm saying is that you might consider allowing additional software,
> either in the main distribution, or - which would be even better: to
> allow the addition of easy to set-up additional repositories
This has been possible for years a
tem.
> OT: Do you think your package manager could be installed on DR DOS as
> well?
http://fdnpkg.sourceforge.net says:
"It is written by Mateusz Viste primarily for the FreeDOS™ project, but
can be used with other DOS syst
On Mon, 06 Nov 2017 14:55:53 +0100, Tom Ehlert wrote:
> AND READ, competent programmers could have ported the kernel to GCC,
> with some time left to save the planet, and fight for peace on earth.
A competent programmer would NEVER fight for peace on earth. He would
rather write a function fightf
On Tue, 07 Nov 2017 23:28:08 -0800, Ralf Quint wrote:
> And yes, I would like to see this included in FreeDOS, as it is the only
> C compiler that both produces 16 bit code and can even run on a
> minimalistic FreeDOS system with only 256KB of RAM and two floppy discs.
Sounds nice! And if the lice
On Tue, 07 Nov 2017 14:58:30 -0500, Jerome Shidel wrote:
>> Shouldn't take much.
>
> Correct, but if your going to calculate stuff, should be accurate.
Also, whoever would take on doing this semi-pointless task, should
remember to take cluster size into account, since disk space occupied by
an
On Thu, 09 Nov 2017 19:10:31 -0600, Rugxulo wrote:
> You say it's as good as DJGPP (as far as maintenance), but that's not
> true at all.
I think it's pointless arguing over this matter. Desmet-C is, as far as I
checked, a reasonably looking C compiler that is able to produce working
executables
On Sun, 21 Jan 2018 15:12:26 -0500, Jerome Shidel wrote:
> I don’t readily have access to a gopher client.
FDNPKG INSTALL GOPHERUS
Mateusz
--
FreeDOS is present on the USENET, too! alt.os.free-dos
--
Check out the vibr
On Thu, 25 Jan 2018 00:57:02 +0100, Eric Auer wrote:
>> There are two DOS programs, MS Interlink and Laplink, that could
>> self-copy from one DOS PC to another through the serial port.
>
> As far as I remember, they do not work well with FreeDOS.
I don't know about MS Interlink, but LapLink work
On Tue, 20 Mar 2018 09:38:26 +, Jim Hall wrote:
> Yes, HP is one of the computer manufacturers that includes FreeDOS in
> their standard builds. If you go into their laptops and desktops, and
> search for FreeDOS, you'll get a list of devices that can be configured
> with FreeDOS as the default
On Mon, 14 May 2018 10:24:42 +0100, Tom via Freedos-user wrote:
> Hello, new to freeodos On a fresh install I tried "fdnpackage update"
> and a couple of packages wouldnt update as files already exiting.- see
> attached png How do I get further with these?
> Tom
Looks like your installation is br
On Fri, 29 Jun 2018 08:17:06 -0500, David McMackins wrote:
> DISKCOPY throws an error if I try to copy a 720k image to a 1.44M
> diskette. I couldn't find a flag that could do it. I tried setting the
> size to 720, but that threw a different error.
Have you tried formatting your floppy as a 720K m
On Sun, 08 Jul 2018 10:07:32 +, Bruce Sommerset wrote:
> I have some questions that perhaps more experienced users might be able
> to help me with. I am trying to get two computers to communicate with
> one another (Basically a small network) I have been skeptical about
> switching from MS-DOS
On Mon, 09 Jul 2018 21:08:35 -0500, David McMackins wrote:
> I have a 1998 Sony Vaio running FreeDOS. This model did not include an
> ethernet controller (or wlan), but it does have an old modem in it. I've
> been going through the networking guide referred to by Rugxulo, and I
> got down to runnin
On Tue, 10 Jul 2018 14:58:01 -0400, dmccunney wrote:
> Any chance of posting that somewhere that doesn't require a gopher
> client to access it?
You mean like http or whatever? Bleh. Where would be the fun then?
Gopher-disabled people are free to use one of the few web proxies out
there. FreeDOS
Hello,
Following a short discussion recently on one of the FreeDOS mailing
lists, I noticed that there is not much choice when it comes to 8086-
compatible, free (libre) calculators under DOS. I decided to fill this
gap, and created rcal.
http://rcal.sourceforge.net
Not sure it will be usef
On Tue, 07 Aug 2018 02:11:50 +, Bret Johnson wrote:
> There are several free DOS calculators listed here, including some that
> are TSR's: http://reimagery.com/fsfd/calc.htm
Can you point out exactly which of these are:
- 8086-compatible
- 'normal' applications (not TSR)
- floating point-aw
On Tue, 07 Aug 2018 06:45:33 -0500, David McMackins wrote:
> Why does your "copying policy" say MIT but the license in RCAL.TXT is
> GPL? Confusing.
No it's not, if you can read. Here's an excerpt of RCAL.TXT just for you:
rcal is published under the MIT license, as printed below.
(...)
rca
On Tue, 07 Aug 2018 07:57:12 -0500, David McMackins wrote:
> Based on the terms of the GPL, I think the package info file should say
> GPL since the package must still be distributed under the terms of the
> GPL (that's how copyleft works).
GPL itself doesn't mean much, since there are many varian
101 - 200 of 691 matches
Mail list logo
