Re: [Freedos-devel] gcc-ia16 packaging

On Wed, 17 Oct 2018 22:13:51 +0200, Eric Auer wrote: > When you use LZMA, the only "easy" way to open it in DOS is to install > it :-! You can easily open it in DOS using 7z. Mateusz -- FreeDOS is present on the USENET, too! alt.os.free-dos ___

Re: [Freedos-devel] gcc-ia16 packaging

On Wed, 17 Oct 2018 22:24:02 +0200, Pär Moberg wrote: > On a "just a feeling" level I would like it to be uncompresseable with > 16-bit tools but that is like I said just a feeling, nothing big. The program (gcc) is not 16-bit, hence it has no value being on a 16-bit machine. Requiring a 32-bit

Re: [Freedos-devel] UNIX fortune for DOS

On Sat, 29 Sep 2018 17:18:20 -0500, Rugxulo wrote: > Tom, I am not aware of anybody else (Jim or Eric, for example) ever > specifying that this mailing list (freedos-devel) is only for > development of FreeDOS proper and not for development on or targeting > FreeDOS. While I don't necessarily

Re: [Freedos-devel] FreeDOS TUI Shell 0.2 has been Released (With some fixes)

On Mon, 24 Sep 2018 15:52:31 -0400, Steve Nickolas wrote: > On Mon, 24 Sep 2018, stecdose 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

Re: [Freedos-devel] FreeDos freeware in graphical field

On Sun, 23 Sep 2018 14:40:13 +, Mateusz Viste wrote: > But given your answer I assume it is simply not a 16-bit application. ...and indeed, trying to run it ends up with an immediate error message: Load error: no DPMI - Get csdpmi*b.zip Hence this is definitely not a 16-bit applicat

Re: [Freedos-devel] FreeDos freeware in graphical field

On Sun, 23 Sep 2018 12:05:19 +0200, Olivier de Lannoy (free) wrote: > 2) About memory capacity, testing for FreeDos was realized with this > setup: > LapTop, Intel(R) Core(TM) i5 CPU @ 2.30GHz with 8GB Memory I suggest 2GB > Memory at least (for BMP image size < 2Mo) but no problem for 16bits >

Re: [Freedos-devel] FreeDos freeware in graphical field

On Sun, 23 Sep 2018 10:30:24 +0200, Olivier de Lannoy (free) wrote: > Shapix is a freeware (free on charge). See http://www.shapix.org for > more information. It is unclear from the license if it allows redistribution. And if so, can it be in a modified (repackaged) form? Could you clarify?

Re: [Freedos-devel] Larger buffers in Watcom

On Wed, 19 Sep 2018 10:44:14 +0200, stecdose wrote: > HOW does a 16bit truncate limit to 16384bytes? > >      b1 b0  (byte 1, byte 0) >    b2 | |   (byte 2) >     | | | > decimal 81920 = hex 014000 decimal 65536 = hex   size of size_t = 2 >

Re: [Freedos-devel] Larger buffers in Watcom

On Sun, 29 Jul 2018 11:17:08 +0800, TK Chia wrote: > I double-checked the compiler output (using `wdis test.o') for the > malloc( ) call under the huge model, and found that it actually clips > the size to a `size_t', and `size_t' is a 16-bit integer type even for > the huge model. I.e.

Re: [Freedos-devel] Larger buffers in Watcom

On Sat, 28 Jul 2018 11:49:42 -0500, David McMackins wrote: > Is there a way to allocate a buffer in OpenWatcom that is larger than > 64k? Sure. Either use XMS/EMS, or rely on the "huge model" kludge. > I'm currently trying to stay within the compact memory model, but > even if I compile for huge

Re: [Freedos-devel] Starting FreeDOS 1.3

On Wed, 25 Jul 2018 00:33:17 -0500, Rugxulo wrote: > Actually, you should be able to use LZMA compression in the main .ZIP > itself to squeeze some more space. I don't recall if any other packages > used that (yet). I think Mateusz was vaguely worried about wasting > dozens of MB of RAM just to

Re: [Freedos-devel] VGA frame rates and mouse

On Sun, 22 Jul 2018 19:48:20 -0500, David McMackins wrote: > By boolean mask, do you mean something like all 1s over the colors for > opaque and all 0s for transparent? The way I've got it now is just 1 bit > in the color byte represents opacity. It's either opaque or transparent, > and then the

Re: [Freedos-devel] Check if VGA is available

On Mon, 16 Jul 2018 05:51:09 -0500, David McMackins wrote: > I'm doing some graphics programming, and I want to support many > different graphics modes, but I need a way of checking to see if they > are available. Currently I'm working on VGA. How do I check if it's > available without just trying

Re: [Freedos-devel] Ideas

On Sat, 07 Jul 2018 12:51:46 -0500, David McMackins wrote: > Is FoxCalc not 16-bit? No, it's not. It's a protected mode application, ie. requires a 386 CPU. Mateusz -- FreeDOS is present on the USENET, too! alt.os.free-dos

Re: [Freedos-devel] PASSWORD modification to not print passwords in plain text into the log file

On Sun, 24 Jun 2018 10:00:59 -0500, David McMackins wrote: > I noticed the PASSWORD program puts password attempts in plain text into > its log file. This is dangerous if the user only barely miskeys their > password and another user reads the log file. > > I made a modification to only say which

Re: [Freedos-devel] FreeDOS PASSWORD executable size

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 stripped to that small size? I wrote it ages ago, and I guess

Re: [Freedos-devel] fltkal a DOS fork of FLTK using Allegro and DJGPP

On Wed, 07 Feb 2018 18:28:12 +0100, Matej Horvat wrote: > Georg's port has a couple of rough edges. It wastes power when idle (no > INT 28h calls) and for me it always crashed when opening file choice > dialogs (but not in NTVDM). Open Watcom support would be welcome as > well. On the other hand,

Re: [Freedos-devel] fltkal a DOS fork of FLTK using Allegro and DJGPP

On Tue, 06 Feb 2018 23:54:32 -0700, Mark Olesen wrote: > I am working on a project forking FLTK to run on FreeDOS. > > The github page is: > https://github.com/markjolesen/fltkal Georg did it a couple of years ago. https://sourceforge.net/projects/fltk-dos/ Will your port have some other

Re: [Freedos-devel] row4

On Wed, 01 Nov 2017 23:06:44 +0100, Andreas K. Foerster wrote: > Sorry if I sounded harsh, I didn't mean it that way. Don't worry :) > But I was happy that I found a solution that worked well for me, and > then you say it's bad. That's a bummer indeed. > And INT 28 doesn't solve the problem of

Re: [Freedos-devel] row4

On Mon, 30 Oct 2017 15:44:25 +0100, Andreas K. Foerster wrote: > "task scheduler"? "power manager"? There must be a misunderstanding > somewhere. I am talking only about the DOS version. A misunderstanding there is indeed - but I fear it's not where you think it is :) I planned to go into

Re: [Freedos-devel] row4 (was: Compiling with gcc)

On Fri, 27 Oct 2017 21:04:19 +0200, Andreas K. Foerster wrote: > The file in LINKS\ROW4T.BAT doesn't seem to work... It is not supposed to work unpacked as-is. The archive, even though it looks like a standard zip file, is in fact a FreeDOS package that needs to be installed using FDNPKG (or

Re: [Freedos-devel] What is FreeDOS 2.0?

On Fri, 20 Oct 2017 21:23:43 +0200, Tom Ehlert wrote: > I personally would expect more change then removing APPEND even if > APPEND has its roots in CP/M and MSDOS 1.0 I have to agree with Tom here. I really don't see the point of such move. We are talking about a legacy system that has no

Re: [Freedos-devel] Incompatibility issue due to FreeCom Dir command's output layout and Dosbox kernel limitations

Instead of filling out a binary country.sys by hand, you might want to use localcfg.exe - much more reliable. It will produce a country.sys file with all the parameters you wish. http://localcfg.sourceforge.net Of course, all this is pointless if your program won't listen to country

Re: [Freedos-devel] odd FreeDOS batch %1 %2 %3 behavior (differs from MS-DOS, too)

Hi Bret, Thank you for sharing your insight. It clearly looks like I will have to figure out an alternative approach to my batch files. Context: Such batch files are created by FDNPKG, my FreeDOS package manager, as "links" to some commonly used applications like zip, upx, nasm, etc, to avoid

Re: [Freedos-devel] odd FreeDOS batch %1 %2 %3 behavior (differs from MS-DOS, too)

On Mon, 28 Nov 2016 17:58:14 -0600, Rugxulo wrote: > Maybe put double quotes " " around args when invoking the .BAT? This doesn't change anything regarding how the equal characters are processed. Worse even, the callee ends up being called with too many arguments each time, since each ""

Re: [Freedos-devel] odd FreeDOS batch %1 %2 %3 behavior (differs from MS-DOS, too)

Hi Tom, Thanks for your test - it shows that Microsoft is at least consistent with this behaviour, as odd as it is :) You got the same result as me on MS-DOS 6.0, ie "DOS processes the = character like a white space when found inside a %1, %2, %3 etc argument inside a batch file". FreeDOS

[Freedos-devel] odd FreeDOS batch %1 %2 %3 behavior (differs from MS-DOS, too)

Hi group, This message can be considered both as a minor bug report and a question. Here's an introduction to what I tested: I wrote a trivial program that I called getargs, it simply prints out the argv list: #include int main(int argc, char **argv) { int i; printf("got %d

Re: [Freedos-devel] fdnpkg: Repository download failed (ibiblio)

Can you please confirm whether basic WATT32 connectivity works for you? Typically, are you able to download anything using wget ? Mateusz On Mon, 07 Nov 2016 08:59:05 -0500, Paul Dufresne wrote: > After hours of network configuration, I have been able to have FreeDOS > fdnpkg giving something

Re: [Freedos-devel] keyb us does not work

s, Mateusz On Mon, 07 Nov 2016 08:45:40 -0500, Paul Dufresne wrote: > 2016-11-07 4:15 GMT-05:00 Mateusz Viste <mate...@nospam.viste.fr>: >> On Sun, 06 Nov 2016 00:14:25 -0400, Paul Dufresne wrote: >>> you might find it strange, but here in Quebec, we are totally lost &g

Re: [Freedos-devel] keyb us does not work

On Sun, 06 Nov 2016 11:17:27 -0500, Paul Dufresne wrote: > Maybe I should begin by trying to understand why there is keyb, and > mkeyb. :-) Here I found an excellent introduction to the subject: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/keyb/mkeyb/ xkeyb+mkeyb.txt Mateusz

Re: [Freedos-devel] keyb us does not work

On Sun, 06 Nov 2016 00:14:25 -0400, Paul Dufresne wrote: > you might find it strange, but here in Quebec, we are totally lost with > french keyboard. US is much more usable for us. Hi Paul, out of sheer curiosity - may I ask how do you actually write french without an azerty layout? Are people

Re: [Freedos-devel] How to rework some French translations and contribute a Turkish translation?

ored within the freedoslocal project as UTF-8. The only reason you'd want to convert them yourself is if you wish to test them on an actual FreeDOS system (highly recommended). Finally, please note that FreeDOS uses CP850 (aka 'Latin 1') for French localizations, not ISO-8859-1. cheers, M

Re: [Freedos-devel] How to rework some French translations and contribute a Turkish translation?

Hi, About translations of the installer - Jerome already provided an extensive explanation. About the rest of the system - I'd suggest taking a look here: http://freedoslocal.sourceforge.net/ We actually already have partial Turkish translations provided by Ercan Ersoy, you might want to

Re: [Freedos-devel] GUI shell

As most people that responded yet, I do not use GUI stuff on DOS, hence such application would be useless to me. GUI projects were probably interesting back in 1992, when people were *forced* to use DOS, and many wished some easy colourful interface. But today, the only people still using DOS

Re: [Freedos-devel] FDNPKG design issues

I'm not sure you noticed, but I already ported most of FDNPKG to 16bits a few months ago - it's called FDINST. No network though, nor repository support, nor LZMA. Mateusz On 27/01/2016 19:07, sparky4 wrote: > ok i was able to compile FDNPKG16 port... not for the difficult part > fixing

Re: [Freedos-devel] FDI and FreeDOS 1.2

On 26/01/2016 12:10, Antony Gordon wrote: > Things would be so much simpler if FreeDOS emulated the Microsoft and > IBM (and Caldera, Digital Research) counterparts and installed the base > operating system. I second that. But it would seem we are isolated in this opinion, since I see all the

Re: [Freedos-devel] Command.com DIR

It might be worth looking at possible "pending" patches - there are some waiting in line, but sadly never applied nor revised. The one example I immediately think of (because it's mine) is this one about CGA support: http://sourceforge.net/p/freedos/bugs/131/ Mateusz On 12/01/2016 19:36,

Re: [Freedos-devel] FDISK Update

Sounds awesome, thank you! Mateusz On 11/01/2016 17:59, Antony Gordon wrote: > Hi, > > I updated FDISK 1.2.1 and made some changes so that it would compile. I > also managed to get in contact with Brian and he's helping me resolve > the issues with the 1.3 code base that I'm having with

Re: [Freedos-devel] FreeDOS 1.2 beta

Hi Maarten, Thank you for your time. The packaging work is pretty straigh-forward - it's simply "look at what packages we have, and see if any newer versions are available and/or if any other interesting and useful software could be added". All packages are here:

Re: [Freedos-devel] A little message

I fear you are slightly too late - there are many places in the world where it's 2016 already - Most of Australia, some parts of Russia, New Zealand, and a few more. :) Mateusz On 31/12/2015 15:09, JAYDEN CHARBONNEAU wrote: > Yes,tonight is New Years Eve!Stay up late!Party!Watch the

Re: [Freedos-devel] FDI Language Translations

c 23, 2015, at 7:58 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> On 23/12/2015 13:38, Jerome E. Shidel Jr. wrote: >>>> Japanese - Nobody. >>>> Russian - Nobody. >>>> Chinese - Nobody. >>> >>> I thought there was a standard

Re: [Freedos-devel] FDI Language Translations

On 23/12/2015 13:38, Jerome E. Shidel Jr. wrote: >> Japanese - Nobody. >> Russian - Nobody. >> Chinese - Nobody. > > I thought there was a standard and completely acceptable practice > for representing these languages using the standard Western DOS > Latin based font that was put into place at the

Re: [Freedos-devel] FreeDOS 1.2 ALL packages

On 21/12/2015 00:02, Rugxulo wrote: >> util\fdnpkg > > Presumably latest here? (0.99.4 "<8 hours ago", according to SF.net page) Good catch! I did release (silently) FDNPKG to v0.99.4 yesterday. Since it contains nothing big from the user's point of view, I didn't feel that it justify

Re: [Freedos-devel] FreeDOS 1.2 BASE packages

On 20/12/2015 23:48, Rugxulo wrote: > ("BASE" does have both "uide" and "xmgr" but not "udvd2", so I'm not > sure why we don't just combine all that RDISK+UIDE+XMGR (etc.) into > one package) I think that was me who exploded this into different packages. The rationale was that when users look

Re: [Freedos-devel] FDINST

On 13/12/2015 16:21, Jerome E. Shidel Jr. wrote: > You need to update your online repo and all_cd.iso to contain the fixed > version of FDINST. Absolutely. But I need to publish a new formal release with latest FDNPKG/FDINST version first. Then I will update the all_cd with the new package,

Re: [Freedos-devel] FDINST

z/PKGTEST/latest >>> >>> Setup a virtual machine machine with a DOS CD-ROM and formatted Drive C: >>> >>> Mount the ALL_CD.ISO and boot the Floppy image the test will autorun. >>> >>> Since the tester sets up it’s own DOS target directory and stuff,

Re: [Freedos-devel] FDINST

erformanes. cheers, Mateusz On 10/12/2015 17:57, Jerome E. Shidel Jr. wrote: > >> On Dec 10, 2015, at 6:38 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> On 10/12/2015 10:46, Jerome E. Shidel Jr. wrote: >>> I don’t know why the A:\FDOS shows no files on your vm.

Re: [Freedos-devel] FDINST

wrote: > >> On Dec 7, 2015, at 12:47 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> Could you confirm please that these tests were performed using the >> latest version of both the all_cd.iso and fdinst? > > Still having issues with the latest versions. >

Re: [Freedos-devel] FDINST

will try to fix it as soon as I get the time, and will test then the FDINST part. cheers, Mateusz On 09/12/2015 23:17, Jerome E. Shidel Jr. wrote: > >> On Dec 7, 2015, at 12:47 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> Could you confirm please that these

Re: [Freedos-devel] FDINST

x is quite unstable when running FreeDOS - for example trying to execute djgpp immediately kills the VM). Mateusz On 06/12/2015 23:02, Jerome E. Shidel Jr. wrote: > >> On Dec 5, 2015, at 6:36 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> On 04/12/2015 18:5

Re: [Freedos-devel] FDINST

On 04/12/2015 18:58, Mateusz Viste wrote: > I am in the process of fixing all the ibiblio packages that contain LFN. Done. I spent the day on repackaging the whole base of ibiblio packages so every single one is compliant to the 8+3 scheme. I also rebuilt a new all_cd.iso with all the upda

Re: [Freedos-devel] FDINST

. Mateusz On 02/12/2015 23:40, Jerome Shidel wrote: > >> On Dec 2, 2015, at 11:14 AM, "Jerome E. Shidel Jr." <jer...@shidel.net> >> wrote: >> >> >>> On Dec 2, 2015, at 3:28 AM, Mateusz Viste <mate...@viste.fr> wrote: >>> >>>

Re: [Freedos-devel] FDINST

On 02/12/2015 23:57, Rugxulo wrote: > Honestly, there's not much to do about it. If you see that a file uses > invalid chars or is longer than 8.3, just either ignore it or rename > it. I think that's what I will end up doing indeed. LFN in DOS always has been a hack anyway. Also, it's the

Re: [Freedos-devel] FDINST

On 02/12/2015 23:40, Jerome Shidel wrote: > It did not freeze or lockup. That's some success already :) This would confirm that the lockups and crashes were due to tinfl behaving badly on 16bit. That's good. > There were multiple issues and about 2500 errors (total). Containing -2,-3,-4 > and

Re: [Freedos-devel] FDINST

reasonable, I linked FDINST to it, so hopefully (?) FDINST should now support LFN files, and therefore it might solve all the -2 errors that were popping up when trying to unpack LFN files from packages. Mateusz On 01/12/2015 19:04, Mateusz Viste wrote: > Hi, > > Here is a new deve

Re: [Freedos-devel] FDINST

On 30/11/2015 20:48, Louis Santillan wrote: > I would post an issue to Richard Geldreich's miniz project site [0]. I did write to him yesterday already. > Rich also intended for tinfl to be > RFC compliant, so if there is an issue, he may want to address it. The problem has nothing to do with

Re: [Freedos-devel] FDINST

Hi, Here is a new devel version of the FDNPKG package (including FDINST, as usual). The big change is that I use zlib now, instead of tinfl. gopher://gopher.viste.fr/1/temp My limited tests show that it doesn't fail any more on neither the 'lzma' nor 'help' packages, which the previous

Re: [Freedos-devel] FDINST

Hello, Quick mail to say that although I had no time to work on the issue, I did a quick investigation and confirmed that the problem comes from the DEFLATE library I use (TINFL, from the Miniz suite). This library behaves differently when compiled under DJGPP (FDNPKG) and Watcom (FDINST). In

Re: [Freedos-devel] FDINST

before the end of next week) with some findings. cheers, Mateusz On 27/11/2015 20:10, Jerome E. Shidel Jr. wrote: > >> On Nov 27, 2015, at 3:58 AM, Mateusz Viste <mate...@viste.fr> wrote: >> >> On 27/11/2015 05:55, Jerome E. Shidel Jr. wrote: >>> Unfortunat

Re: [Freedos-devel] FDINST

On 27/11/2015 05:55, Jerome E. Shidel Jr. wrote: > Unfortunately, I don’t have access to any functional gopher clients. You can use a gopher proxy :) Here is a link: http://gopherproxy.meulie.net/gopher.viste.fr/1/temp Mateusz

Re: [Freedos-devel] FDINST bug?

On 24/11/2015 18:38, Jerome E. Shidel Jr. wrote: > That fixed the problem with the attrib package. > But, now there is a new problem. :( > FDINST locks-up while extracting the help package. That's a bug specific to FDINST. FDNPKG works fine. In fact, the bug is present in the source code of both

Re: [Freedos-devel] FDINST bug?

On 23/11/2015 20:53, Jerome E. Shidel Jr. wrote: >> FDNPKG v0.99.3 fixes this issue. > > So, is it going to be fixed in FDINST? It is fixed, FDINST uses FDNPKG. Any fix inside FDNPKG's core applies also to FDINST, too. Sorry if that was unclear. > End result, any attempt to use attrib will

Re: [Freedos-devel] FDINST bug?

On 22/11/2015 20:39, Jerome E. Shidel Jr. wrote: > I’ve tried recompressing them multiple ways, but that either > causes FDINST to choke on all of the files. Or, just fail at the > same point. In fact, the problem is not about compression, but the lack of it. I introduced a 1-byte bug in v0.99.2

Re: [Freedos-devel] FreeDOS 1.2

Hi Geraldo, Looks nice! Let me know when it is confirmed that translations are okay, I will gladly add them. Or, if you wish, I can provide you svn access to the project so you can maintain these languages yourself. Side note: in any case, if/when you provide any files to the freedoslocal

[Freedos-devel] picoTCP: a modern, open-source TCP/IP stack for DOS

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

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 12:00, Jerome E. Shidel Jr. wrote: > Unzip seems to work fine for the packages on the FreeDOS 1.1 CD. (excluding > JEMMEX, which has some > attribute issues) > I’m not sure what you mean by “too many details” ? Are you able to uninstall cleanly a package that you simply unzip?

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 18:19, Jerome E. Shidel Jr. wrote: > I will probably add a pre-built floppy image to my download server > (http://up.lod.bz) > at some point. That would be awesome. > If FDI uses FDINST remove, how will it be able to tell if it failed to remove > a package because of an error or

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 17:23, Jerome E. Shidel Jr. wrote: > Converted FDI to use a single package for both binary and sources and > to use Mateusz’s all_cd.iso as the layout for packages and to use > FDINST instead of unzip. Sounds cool! So if I slap your boot floppy inside all_cd.iso's, we should end

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 13:34, Jerome E. Shidel Jr. wrote: > Just FYI, %DOSDIR% will be C:\FDOS in basic/normal mode. At some point, > whenI get around to writing vask in V8, advanced mode will allow setting a > different target for the install. Having a hardcoded location is fine, I guess... Although I,

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 12:52, Jerome E. Shidel Jr. wrote: > I may be wrong, but it appears that the original FreeDOS 1.1 packages > include “deployed” versions of the packages that include all the data to > do what your asking. That's not the case. Only LSM files are provided. The listing of actually

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 19:25, Jerome E. Shidel Jr. wrote: > It seems kind time consuming for the FDI to run through every installed > package with > "FDINST remove” prior to doing an install. What do you mean by "time consuming" ? FDINST REMOVE won't do anything if the package is not installed - it will

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

On 11/11/2015 20:09, Jerome E. Shidel Jr. wrote: >> What do you mean by "time consuming" ? FDINST REMOVE won't do anything >> if the package is not installed - it will execute only a check >> determining whether or not said package is already installed. This is >> something that needs to be done

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

ave support for packages -> do not touch %DOSDIR (maybe just backup a copy it into a zip or so), and instead do a remove/install loop on all BASE packages from the CD? Mateusz On 11/11/2015 20:36, Jerome E. Shidel Jr. wrote: > >> On Nov 11, 2015, at 2:18 PM, Mateusz Viste <mate.

Re: [Freedos-devel] FreeDOS 1.2

On 21/10/2015 14:31, Jerome E. Shidel Jr. wrote: > I did not know how the packages in 1.2 are going to be handled when it comes > to > source versus binary only. What I mean is are the source packages going to be > separate from the binaries, or like in previous versions its just a single > blob

Re: [Freedos-devel] extending chkdsk to fat32

Hi C.J, Reading your message I couldn't help but wonder about a few things. Exact questions below. On 20/10/2015 10:51, C.J. van Delft wrote: > I, for one, would also point out that there are many museums and > individuals with VERY old machines, who would need FreeDos if ever their > MS/IBM

Re: [Freedos-devel] FreeDOS 1.2

On 20/10/2015 20:29, Jerome E. Shidel Jr. wrote: > At present, I know very little about the FDNPKG. However, I thought it > was 32-bit+ only. The tool itself - yes. The package base is just that - a package base with software. Here are all the repos:

Re: [Freedos-devel] FreeDOS 1.2

I might have missed something along the way, but why not slapping the installer on the FDNPKG packages we already have and call it a day? Mateusz On 20/10/2015 16:44, Jerome Shidel wrote: > >> On Oct 20, 2015, at 9:47 AM, Mercury Thirteen >> wrote: >> >> Greetings!

Re: [Freedos-devel] FreeDOS 1.2

ersion of the > massive ZIP I assembled previously, no? > > Merc > > On 10/20/2015 3:26 PM, Mateusz Viste wrote: >> On 20/10/2015 20:29, Jerome E. Shidel Jr. wrote: >>> At present, I know very little about the FDNPKG. However, I thought it >>> was 32-bit+ only. >&

Re: [Freedos-devel] FreeDOS 1.2

that's another story). http://svarog86.sourceforge.net/ Mateusz > On 10/20/2015 3:32 PM, Jerome E. Shidel Jr. wrote: >>> On Oct 20, 2015, at 3:26 PM, Mateusz Viste <mate...@viste.fr> wrote: >>> >>> On 20/10/2015 20:29, Jerome E. Shidel Jr. wrote: >>

Re: [Freedos-devel] FreeDOS 1.2

On 20/10/2015 22:32, Eric Auer wrote: > Hi, at the risk of being controversial: Eric you mad man! You might need to run for your life soon :) > IF you can NOT boot from CD then you almost always want a floppy distro, > not some fancy shiny installer... Just my personal experience here ;-) > >

Re: [Freedos-devel] FDNPKG16 port!

On 06/10/2015 17:49, sparky4 wrote: > Yeah thats what i am doing and apparently there is no ungz function in watcom > C Of course there isn't, since that's a function I wrote myself. It's a core part of fdnpkg. see libgz.c. Mateusz

Re: [Freedos-devel] exfat support from android linux for freedos sdxc support and more?

I don't want to sound harsh, but "drawing specs" is easy, anybody can do that. Do some code that actually works, then we're talking. Mateusz On 25/09/2015 03:44, Mercury Thirteen wrote: > I don't see where we need multitasking for NAS use. A program could be > made to both handle incoming

Re: [Freedos-devel] fdpkg is being maintained?

On 17/09/2015 17:29, sparky4 wrote: > Is fdpkg being maintained? It's pretty much dead. Blair has dropped it 10 years ago, and the last person to have touched it is you, somewhere 2 years ago (but I don't think it resulted in any public release). Mateusz

Re: [Freedos-devel] FDI 1.2 Questions?

As far as I'm concerned, I agree with Jim on that one. Creating a super-power installer is pointless - it will take months to release (if it happens at all), while what I personally need is just an intro screen that warns me about all my disk going to be flushed, some 'OK' button so I give it

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

For instance, "BASE" contains 4 different XMS managers. Why would I want to keep them all on my disk, if I only need the one that works for me? Mateusz On 11/09/2015 18:40, Jerome E. Shidel Jr. wrote: > >> On Sep 11, 2015, at 10:51 AM, Mateusz Viste <mate...@viste.fr&g

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

On 11/09/2015 16:39, Jim Hall wrote: > (...) then use FDNPKG or > UNZIP afterwards to install the other packages that you want. To avoid confusion, I will add that using UNZIP is not a one-to-one alternative to FDNPKG. I strongly discourage using UNZIP to install packages - such packages won't

Re: [Freedos-devel] mTCP/IP stack by M Brutman is now closed source

On 10/09/2015 19:23, Paul Dufresne wrote: > Well, I don't know how hard it would be to port picoTCO (GPL v.2) to DOS: There is also lwip that looks very solid - highly active, BSD license, stable IPv6 support, designed to be lightweight and portable. And there's already a DOS port of it! made

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Hi, No solutions here, only some ranting :) - the tricky part might be to make it possible to install FreeDOS on a system where there is already something (ie. multiboot), and make it actually bootable, without breaking the other stuff. Personally I wouldn't object if FreeDOS would just

Re: [Freedos-devel] FreeDOS 1.2 Installer

e many of us) I would say go for it. > > On 9/7/2015 12:56 PM, Mateusz Viste wrote: >> I'm not 100% sure anymore, but I vaguely recall "Mercury Thirteen" >> saying he's working on v1.2 (there was also an announcement on the FD >> website at some point about that).

Re: [Freedos-devel] FreeDOS 1.2 Installer

from what > was expected. > > On 9/8/2015 2:31 AM, Mateusz Viste wrote: >> I took a quick pick at your big ZIP file. Sadly, there are no FreeDOS >> packages in there - only plenty of LFN files in subdirectories that are >> not compliant with FreeDOS package structu

Re: [Freedos-devel] FreeDOS 1.2 Installer

Since Jim doesn't seem to have > much free time (like many of us) I would say go for it. > > On 9/7/2015 12:56 PM, Mateusz Viste wrote: >> I'm not 100% sure anymore, but I vaguely recall "Mercury Thirteen" >> saying he's working on v1.2 (there was also an announcement

Re: [Freedos-devel] FreeDOS 1.2 Installer

I'm not 100% sure anymore, but I vaguely recall "Mercury Thirteen" saying he's working on v1.2 (there was also an announcement on the FD website at some point about that). Mateusz On 07/09/2015 13:51, Jerome E. Shidel Jr. wrote: > Who is making the Batch file based installer for FreeDOS 1.2?

Re: [Freedos-devel] FreeDOS 1.2 Installer

er and information about my V8PT utilities, I don’t see that anyone >> was creating an installer. >> >> >>> On Sep 7, 2015, at 12:56 PM, Mateusz Viste <mate...@viste.fr> wrote: >>> >>> I'm not 100% sure anymore, but I vaguely recall "Me

[Freedos-devel] HIMEMX - new home

Hi all, It has been a few years now that HIMEMX was abandoned. There were a few very valuable community patches floating around though, sadly never really applied to any "official" release. In an attempt to make things a little less messy, I created a sourceforge project for HIMEMX, here:

Re: [Freedos-devel] V8Power Tools

Might be a dumb question - but why creating so many micro tools? Would it be possible to have all of them inside one binary, with behavior adapted with a switch? (a la busybox - like "V8POWER VCURSOR HIDE") ? It would certainly make the toolbox much more space-efficient on big (fat) clusters

Re: [Freedos-devel] Offering software to the FreeDOS official distribution: Terminal Matrix 8086, DeciMatrix 8086 and QDot 8086

Hi Bruno, I honestly haven't looked at Terminal Matrix (yet), mostly because I was highly confused about what to expect after reading the description on your website. If it genuinly does something at least semi-useful, or semi-fun, and it's libre software, then I believe we should add it to

Re: [Freedos-devel] Offering software to the FreeDOS official distribution: Terminal Matrix 8086, DeciMatrix 8086 and QDot 8086

, Mateusz Viste wrote: Hi Bruno, I honestly haven't looked at Terminal Matrix (yet), mostly because I was highly confused about what to expect after reading the description on your website. If it genuinly does something at least semi-useful, or semi-fun, and it's libre software, then I believe we

Re: [Freedos-devel] Kernel.sys and fdos (dir)

I totally agree with Eric here - using DOS means we have absolute power over the computer. This comes with some responsibility that the user must know what he's doing. Even on Win9x it was possible to delete some system files that would render the OS unbootable. Mateusz On 28/06/2015 22:41,

Re: [Freedos-devel] FreeCOM high CPU consumption

On 23/06/2015 15:41, JAYDEN CHARBONNEAU wrote: I have a memory problem.I booted FreeDOS into my flashdrive,which is 8 gigabytes.But when I ran MEM,it reported that I have under 1 megabyte of free memory.If I run Visual Basic 1.0,it reports that I am out of memory.Any help for this?I have

[Freedos-devel] FreeCOM high CPU consumption

Hi there, I noticed that FreeCOM is using much CPU on my PII machine according to FDAPM. When FreeCOM runs in an empty shell, FDAPM (APMDOS) reports about ~50% of CPU idleness, while if I run a power-efficient application that call INT28 from time to time (besides doing its real job), FDAPM

  1   2   >