Re: [Freedos-devel] Package survey

Hi, I always thought it would be a good idea to model the FreeDOS install after the MS-DOS 6.x or IBM Personal Computer DOS 6.x (or 7.x) and include the actual core components of DOS. All the other stuff should be extra so a fresh FreeDOS install would look exactly like what MS-DOS 6.x looked

Re: [Freedos-devel] Application to check DOS API compatibility

Hi, There are some “unofficial” tests for genuine MS-DOS that can be used (within reason) to establish a “level” playing field for DOS. Microsoft used these methods as a part of the AARD code hidden in the Windows 3.1x startup program. Undocumented DOS discusses the AARD code somewhat in

[Freedos-devel] C/C++ Compilers

Hi, I’m still working on these compilers, Jim and I talked about another one that I’m playing with now, we’ll see what happens. Once I figure that part out, then I can work on the libraries… -T -- Check out the

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

il.com> wrote: > > Hi, > > On Wed, Jan 17, 2018 at 11:11 PM, Antony Gordon <cuzint...@gmail.com> wrote: >> >> AFAIK no one on this project is interested in building a C compiler from >> scratch for >> the purposes of developing FreeDOS. > > N

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi, AFAIK no one on this project is interested in building a C compiler from scratch for the purposes of developing FreeDOS. DJGPP can’t reliably generate code for all the DOS modes which rules it out, MSC and the Borland compilers. Pacific C is free but we only have access to the binary

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi, I’m going to address all the emails at once instead of replying to multiple emails so it will be pretty easy to follow (I think). Jerome, it initially looks like that because I haven’t had the time to devote to fully building this idea out. Also, due to the amount of things involved in

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi all and Happy New Year, I sent a screen shot, not knowing that there was a size limit on the emails, so I’m resending as a text only message. I have been working on a project for FreeDOS for well over year and I think it’s about ready for prime time. I thought it would be cool if there was

Re: [Freedos-devel] Booting other O/Ses from FreeDOS

Try Loadlin with no memory managers installed. > On Dec 29, 2016, at 11:49 PM, Ralf Quint wrote: > > On 12/29/2016 4:00 PM, Jose Antonio Senna wrote: >> So no, it's not reasonable to expect FreeDOS to work under a >>> running Win95. It may be possible in theory (if

[Freedos-devel] FDISK 1.3.1

Hi, FDISK 1.3.1 won’t run in the following VMs for me at least * VirtualBox 5.1.8-11374 * VMWare Fusion 7.0.0 I did get it to run under Parallels 11.0. This leaves me confused as to what is going on here. Brian is busy, I guess, so I haven’t talked with him in a while. If

Re: [Freedos-devel] 1.2-RC1 Fdisk still does not write a valid mbr

Hi, I think Brian got too busy, I still haven't figured out what causes 1.3.1 to break. I have reached out and even provided him with a copy of my VM as maybe I'm missing something. The CATS portion works now, but I haven't resolved my other error. Regards, T On Sat, Nov 5, 2016, 11:32 PM Paul

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Hi, Host OS should not matter. If the "gold standard" of MS-DOS works in that configuration with the disk images, there is definitely something that isn't right in this release. For those having a problem, what happens in FreeDOS 1.1. Tony On Sat, Oct 22, 2016, 12:10 PM Jerome E. Shidel Jr.

Re: [Freedos-devel] making himemx and jemmex more foolproof on old bios versions

Hi, I think at this point a comparison should be done with Microsoft's version on this machine to see if any differences can be detected. Also, I would run Microsoft's OS in the emulator to see On Wed, Jul 20, 2016, 3:34 PM Maarten Vermeulen wrote: > I looked at int 15h

Re: [Freedos-devel] Fwd: I'd like an absolute minimal version of FreeDOS.

Most of you missed the point on this. Here's the clearer version, based upon me reading (and re-reading several times). As a matter of fact, I'll use an example. Install any version of MS/PC-DOS prior to 6.0 on a computer. It boots up, tells you that you are running that particular version of

[Freedos-devel] FreeDOS Packaging

Hi, Are source files going to still be packaged with the binary file in FreeDOS, or will the source code be a separate optional install? Granted, the whole core OS (what actually comprises DOS) isn't that big, roughly 4.32MB before the other stuff (3rd party editors, a wide assortment of GUI,

Re: [Freedos-devel] FDISK Update

il.com> wrote: > > I am a bit confused as to what is/should be the current version. > > Antony Gordon said he made modifications to v. 1.2.1 and 1.3 but I > don't know if the changes have been published and if so where. > > Then there is (same code, two different categor

[Freedos-devel] Japheth's HX SRC files

Hi, I dug into the wayback machine and grabbed what I could from Japheth's site. I'm working on dumping it into a Git repository so that it remains accessible. So far, HXSRC is up at https://github.com/cuzintone/HXSRC. I am working on JWASM and JWLINK as well and any additional code that I see

Re: [Freedos-devel] Japheth's HX SRC files

've added a few improvements and migrated issues as well. > It does have AppVeyor and Travis-CI connected, as like as Coverity. > Best regards, > Anton Kochkov. > > > On Mon, Feb 1, 2016 at 5:18 PM, Antony Gordon <cuzint...@gmail.com> wrote: > > Hi, > > > >

Re: [Freedos-devel] FDI and FreeDOS 1.2

Things would be so much simpler if FreeDOS emulated the Microsoft and IBM (and Caldera, Digital Research) counterparts and installed the base operating system. All these extra drivers for this, a compiler for that can just be on the CD and can be installed later. Jerome, if you could find a copy

Re: [Freedos-devel] FDI and FreeDOS 1.2

n Tue, Jan 26, 2016, 6:33 AM Mateusz Viste <mate...@viste.fr> wrote: > 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 >

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi, For Maarten and Mercury, look into DOS versions prior to 5.0, they included DEBUG and (GW-)BASIC. That would complete the DOS experience... well that and some sample BASIC programs like GORILLA.BAS and having LINK.EXE along with EXE2BIN. -T On Tue, Jan 26, 2016, 4:06 PM Jerome E. Shidel Jr.

Re: [Freedos-devel] Welcome to FreeDOS n.n

Hi, Why is there a welcome anyway? MS-DOS (and PC-DOS for that matter) just booted, loaded drivers and dropped you to a command prompt. Microsoft (or IBM) never welcomed you to anything. If you wanted a welcome, check out that nice 3-ring binder with the DOS reference pages (I go way back to

Re: [Freedos-devel] FDNPKG design issues

Hi, Zip is the default format right? What kind of zip library is being used? The program should assume that networking is configured and operational and should only have to establish connections in my opinion. Since I'm on baby ALERT (my wife is due soon) and I'm not working as much, I'll take a

Re: [Freedos-devel] FreeDOS Build Tools

ocess JSON. The resulting output is the same, but calling the two and how classes are setup to interface with these APIs are different. -T On Mon, Jan 11, 2016, 5:48 PM Rugxulo <rugx...@gmail.com> wrote: > Hi, > > On Mon, Jan 11, 2016 at 1:59 PM, Antony Gordon <cuzint...@gmail.com>

[Freedos-devel] FDISK Update

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 compiling it. Hopefully soon I will have something together and I can start on the rest of CAT

[Freedos-devel] FreeDOS Build Tools

Hi, Just thought I'd bring this back up as I am currently working on one of the core components to transition it from Borland to OpenWatcom. In looking at the code, I noticed that for internationalization, the CATS library is used. One version of the FDISK source code didn't have the source or

[Freedos-devel] FDISK Update

Hi, I haven’t quite figured out whats wrong with the 1.3 branch of FDISK, but I did manage to get 1.2.1 to compile. I had to do some minor code tweaks to fix some errors. I also fixed the makefile so it works better with Borland/Turbo C. As I use GitHub, I haven’t as of yet updated my

Re: [Freedos-devel] FDISK issue

4, 2016 at 9:54 AM, Antony Gordon <cuzint...@gmail.com> wrote: > > > > I’m attempting to recompile FDISK and apparently you need to assemble > bootnorm.asm > > and booteasy.asm and I’m getting this error when assembling booteasy.asm > > > > booteasy.as

[Freedos-devel] FDISK issue

Hi, I’m attempting to recompile FDISK and apparently you need to assemble bootnorm.asm and booteasy.asm and I’m getting this error when assembling booteasy.asm booteasy.asm:260: error: invalid parameter to [default] directive This is line 260 below. default db '?',' '+80h Any

Re: [Freedos-devel] fdisk translation

Hi, Since I still have the Borland Compilers in my VMs, I can take over FDISK if needed. I can try to re-work it to work with OW. Let me know a time frame for completion so if I take it, I don't drag the project out. -T On Wed, Dec 23, 2015 at 8:26 PM Paul Dufresne wrote:

Re: [Freedos-devel] FreeDOS 1.2 BASE packages

Hi, Given the changes in DOS since 2.X until now, Edlin and EXE2BIN should be optional. DOS 5 replaced Edlin with EDIT and EXE2BIN wasn't included with DOS after 3.3 or 4.01. Which memory manager offers the most compatibility? FDXMS or HIMEMX? -T On Sun, Dec 20, 2015, 4:53 PM Jerome E. Shidel

Re: [Freedos-devel] FreeDOS 1.2 ALL packages

Hi, An assembler and a Pascal compiler. Missing BASIC and C/C++. That would make the programming languages complete. You should probably mention sources for all packages in the "everything" install. Base should just reference that the sources are on the install media. IIRC, most Linux

Re: [Freedos-devel] FDI

Well, there is always the DOS 3.3/4.0 way of doing things - Using SELECT.COM and REPLACE.EXE I am willing to bet no one remembers updating DOS using REPLACE.EXE or installing DOS 4.0(1) using SELECT.COM -Tony On Thu, Dec 17, 2015 at 11:33 AM Jim Hall wrote: > I worry that

Re: [Freedos-devel] FreeDOS 1.2

Or ... FORMAT A: /F:720 On Tue, Nov 17, 2015 at 10:51 AM Antony Gordon <cuzint...@gmail.com> wrote: > CONFIG.SYS entry > DEVICE=[drive:][path]DRIVER.SYS /D:0 /F:2 > > may work > http://www.vfrazee.com/ms-dos/6.22/help/driver.sys.htm > > > On Tue, Nov 17, 2015 at

Re: [Freedos-devel] FreeDOS 1.2

CONFIG.SYS entry DEVICE=[drive:][path]DRIVER.SYS /D:0 /F:2 may work http://www.vfrazee.com/ms-dos/6.22/help/driver.sys.htm On Tue, Nov 17, 2015 at 10:48 AM Antony Gordon <cuzint...@gmail.com> wrote: > Those are 720K floppy disks. 9 sectors/track 80 tracks double sided = > 7

Re: [Freedos-devel] FreeDOS 1.2

Those are 720K floppy disks. 9 sectors/track 80 tracks double sided = 737,280 bytes On Tue, Nov 17, 2015 at 10:15 AM JAYDEN CHARBONNEAU < jcharbonnea...@cpsge.org> wrote: > The disks are the size of a standard floppy but they are also double > sided. They are made by the company NASHUA,and the

Re: [Freedos-devel] FDNPKG16 port!

Where is the code? You probably just need some #defines On Mon, Oct 12, 2015, 5:07 PM sparky4 wrote: > i got the wattcp 16 version and... > > it is borland C ... > > > crap!! > > so much problems!! > > please help! > > i need the makefiles to do their jobs! > > > > -- > View

Re: [Freedos-devel] FDI 1.2

Hi, Sometimes doing the "needful" exceeds the "requested". Jim has a vision of what he wants, basically a batch file based simplified install. You (Jerome) have created some very useful utilities for managing the screen and such. My thought was basically to incorporate your V8 tools as a part of

Re: [Freedos-devel] FDI 1.2

If the Int 21h handler is available, you can use INT 21 AX=3305. DL is returned with an integer indicating the boot drive (1=A:, etc.). This works for MS-DOS 4.0 and later. Given that FreeDOS aims for DOS 6+ compatibility so that functionality should be there. -T On Mon, Oct 5, 2015 at 3:05 AM

Re: [Freedos-devel] FDI 1.2

Hi, set /p is a Windows NT feature of CMD.EXE. It was not available in MS-DOS or Windows 9x. I even double checked on my Win98 VM and my Win ME VM before I wrote this. (Don’t ask why I have those. Just don’t). I get “Syntax Error” in both Windows 98 and Windows ME. It was nice of whomever

Re: [Freedos-devel] FDI 1.2

, 2015, at 6:26 PM, Antony Gordon <cuzint...@gmail.com > <mailto:cuzint...@gmail.com>> wrote: > >> Hey, >> >> Couldn't you use 4DOS as the command shell during the installation process? >> > Unfortunately, no. > > Some of the things that

Re: [Freedos-devel] FDI 1.2

Hey, Couldn't you use 4DOS as the command shell during the installation process? On Oct 2, 2015 1:18 PM, "Jerome E. Shidel Jr." wrote: > Well, best guess. I’m 70% done with the installer. > > Just need to port the backup creation code, the system files transfer > stuff and

Re: [Freedos-devel] FDI 1.2

For option 2, all you would need to do is execute a FreeDOS version function call. I don’t have the spec in front of me, however in the case of MS-DOS, and INT 21H/3306H and INT 21/30 returns the DOS version number. Int 21/30 can be altered by SETVER, but INT 21/3306 should return BL as the

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

Hi, So a cursory read of Wikipedia on this topic (ExFAT) and I stumbled across this Two experimental, unofficial solutions are available for DOS. The loadable USBEXFAT driver requires Panasonic's USB stack for DOS and only works with USB storage devices; the open-source EXFAT executable is an

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

> On Sep 27, 2015, at 9:45 PM, Louis Santillan <lpsan...@gmail.com> wrote: > > > > On Sunday, September 27, 2015, Antony Gordon <cuzint...@gmail.com > <mailto:cuzint...@gmail.com>> wrote: > Hi, > > Unfortunately, Linux doesn’t have a 16-bit C c

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

Hi, I don’t know too much about the innards of checking in and out code however, if you have the current version installed, you more than likely have the source to the current kernel. I would advise you to go the route of MSCDEX and use the network redirector interface. You may want to read

Re: [Freedos-devel] FDNPKG16 port!

Does the TCP stack work in 16-bit? If not, you'd probably have to build it to support loading packages from floppy disks or CDs. On Mon, Sep 21, 2015, 3:08 PM Bruno Félix Rezende Ribeiro wrote: > Hello, sparky4! > > Em Mon, 21 Sep 2015 08:07:17 -0700 (MST) > sparky4

Re: [Freedos-devel] FDI 1.2 Questions?

Hi, Unlike MS-DOS proper, FreeDOS comes with custom configuration files to optimize for different things, I have my personal opinion on this, but I digress. Given that the user may have modified the configuration files and there is no easy way to merge the changes of a vanilla FreeDOS config to a

Re: [Freedos-devel] FDI 1.2 Questions?

Hi, I think the best solution would probably be two setup programs. A quick setup like Jim wants and then a more advanced setup that provides all the advanced tools, disk image creation that more technical users would want. Simple version is the batch file, advanced version is C (or some other

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Eric, I just get ...? LOL I guess you're not liking me again. (Just kidding). On Fri, Sep 11, 2015 at 10:31 AM Eric Auer wrote: > > Hi Jayden (and Mateusz and Jim and...) :-) > > > Will we implement an "advanced" setup? [...] > > > The first would be the user friendly

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

HI, How many of you remember the DOS 6.22 install process? If possible, it should aim for that. It's simple and straight to the point. It worked across all platforms and got DOS up and running with minimal fuss. Once the setup is done, after a reboot, the FreeDOS package manager can run to add

Re: [Freedos-devel] FreeDOS 1.2 Installer

:46 PM, "Antony Gordon" <cuzint...@gmail.com> wrote: > If you just want to do the EULA thing, you can put a generic, this > contains free software based on several licenses, including GNU GPL, MIT, > and BSD. By continuing with this install, you accept all applicable

Re: [Freedos-devel] FreeDOS 1.2 Installer

If you just want to do the EULA thing, you can put a generic, this contains free software based on several licenses, including GNU GPL, MIT, and BSD. By continuing with this install, you accept all applicable licenses. To view them in detail, view C:\FREEDOS\DOC. On Sep 10, 2015 9:34 PM, "Jerome

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

Wow, This is the most activity I've seen on this list in a while, and it's a temper tantrum of sorts over whether someone has the right to close source or open source something they wrote. Talk about comedy. So how are those bugs looking on the bug list in FreeDOS? Yeah, I probably just got

Re: [Freedos-devel] FreeDOS 1.2 Installer Project.

Hi, I'm curious as to why a batch file and DOS 6 setup automatically initiated the format once the drive was selected. On Wed, Sep 9, 2015, 9:28 PM Jerome E. Shidel Jr. wrote: > > > On Sep 9, 2015, at 8:03 PM, Eric Auer wrote: > > > > > > Hi Jerome, > >

Re: [Freedos-devel] FreeDOS 1.2 package compilation

Perhaps it should take a cue from the MSDOS installer - prepare the drive and copy over there core OS. Then at the end of the core install, prompt for the additional stuff On Sun, Jun 21, 2015, 12:47 PM JAYDEN CHARBONNEAU jcharbonnea...@cpsge.org wrote: The installer.We should add a

Re: [Freedos-devel] FreeDOS 2.0

how cool that would be!). On Thu, May 28, 2015 at 10:30 PM, Mercury Thirteen mercury0x0...@gmail.com wrote: Correction... FreeDOS 1.2. Not 2.0. On Thu, May 28, 2015 at 4:40 PM, Antony Gordon cuzint...@gmail.com wrote: Hi, If I were building the FreeDOS distribution, the only thing

Re: [Freedos-devel] 32-bit FreeDOS

Hi snip Do ZM EXEs actually exist? Yes. Any 16-bit MS-DOS target compiler generates MZ executables. FreeDOS is full of them. I've also been curious as to what the format is for .TOS binaries (since GEMDOS has such a similar API to MS-DOS). Grab one and run it through a hex editor.

Re: [Freedos-devel] 32-bit FreeDOS

Hi, See my other email. In DOS, MZ=ZM, I guess Microsoft changed course at some point. They are typically called MZ executables. On Jun 8, 2015, at 8:55 PM, Steve Nickolas usots...@buric.co wrote: On Mon, 8 Jun 2015, Antony Gordon wrote: Hi snip Do ZM EXEs actually exist? Yes

Re: [Freedos-devel] 32-bit FreeDOS

.html) ZM used by some very early DOS linkers, and still supported as an alternate to the MZ signature by MS-DOS, PC DOS, PTS-DOS, and S/DOS -T On Jun 8, 2015, at 9:16 PM, Steve Nickolas usots...@buric.co wrote: On Mon, 8 Jun 2015, Antony Gordon wrote: Hi, See my other email

Re: [Freedos-devel] 32-bit FreeDOS

Hi snip I'd suggest using 0xC3 0x00 as a magic number for any non-8086 executable. Or, for preference, using a 4-byte magic number: 0xC3 0x00 0x00 followed by a byte giving the supported CPU architecture. Then the logic in the loader would be: 0xC3 0x00 0x00 suitable architecture -

Re: [Freedos-devel] 32-bit FreeDOS

Hi, On Jun 5, 2015, at 6:10 PM, Steve Nickolas usots...@buric.co wrote: A port of DOS to ARM would not be bound to any existing API and would not need to be compatible with any existing DOS implementations, while still being a port of DOS. That’s technically incorrect. The reason that

Re: [Freedos-devel] FreeDOS Developer Studio

Eric, That mainly is because Apple is Apple ;-) In DOS, you get very far with a standard C library, good old OpenWatcom or DJGPP, in the latter case even similar enough to the Linux GCC and G++ C and C++ infrastructure to ease porting of things to DOS. As DOS does not provide GUI,

Re: [Freedos-devel] 32-bit FreeDOS

Hey, On Jun 5, 2015, at 6:49 PM, Chelson Aitcheson chelson.aitche...@gmail.com wrote: Nothing is impossible if it was the case we would all still be using reel to reel and tape decks lol. Lots of ideas and spit balling here but hey why not write it up and if people wana contribute

Re: [Freedos-devel] FreeDOS Developer Studio

Hi. On Jun 3, 2015, at 3:55 PM, Rugxulo rugx...@gmail.com wrote: Hi, On Wed, Jun 3, 2015 at 1:12 PM, Eric Auer e.a...@jpberlin.de wrote: How about a FreeDOS Developer Studio? I don't want to be pessimistic or discourage anyone, but this sounds difficult. Not being pessimistic,

Re: [Freedos-devel] FreeDOS Developer Studio

Eric, Finally I’m not irking your nerves :) I wasn’t thinking of even using the Borland Museum tools. What I actually envisioned was much like what Apple does with Xcode, they provide an IDE, LLVM (and GCC) and Swift along with sample code, an SDK and documentation. Fortunately for FreeDOS,

Re: [Freedos-devel] FreeDOS Developer Studio

Why is that important? On Wed, Jun 3, 2015, 6:14 PM Steve Nickolas usots...@buric.co wrote: Keep in mind that OpenWatcom doesn't meet Debian or GNU's criteria to be open source. -uso. --

Re: [Freedos-devel] FreeDOS Developer Studio

. Most of the resources are out of print or hard to find in some cases. Templates for device drivers, templates for building FreeDOS compatible packages. On Wed, Jun 3, 2015, 5:40 PM Rugxulo rugx...@gmail.com wrote: Hi, On Jun 3, 2015 4:13 PM, Antony Gordon cuzint...@gmail.com wrote

[Freedos-devel] FreeDOS Developer Studio

Hi, Since I’ve become the “bain of everyone’s existence” regarding the 32-bit extension to FreeDOS, I am going to attempt to offer an olive branch so I can stay on the list. How about a FreeDOS Developer Studio? It would combine all of the recommended build tools to build the operating from

Re: [Freedos-devel] FreeDOS 1.2 package compilation

for the OS. On Jun 3, 2015, at 12:42 AM, Antony Gordon cuzint...@gmail.com wrote: That was a HUGE zip file (once uncompressed). I’m just glad I use a sandbox for stuff like this, that zip file was like a box of chocolates… That being said…that much stuff comes on the FreeDOS full CD

Re: [Freedos-devel] 32-bit FreeDOS

Eric, It’s involved, but so was writing an MS-DOS clone almost 17 years ago that is able to run 98% of all DOS software natively factoring in the quirks and undocumented and partially documented structures that had to be clean room implemented to avoid infringement. You and I were around for

Re: [Freedos-devel] 32-bit FreeDOS

Eric, It’s simple. Every piece of computer hardware comes with a Windows driver. Depending on the age of the device, you may have the older Windows drivers, or the newer Windows Driver Model driver. The reality is that to the major manufacturers of hardware, DOS is dead. No one is using a

Re: [Freedos-devel] 32-bit FreeDOS

Eric, I only mentioned the Windows portion because it would tie in compatibility on the Microsoft side of things for classic software, not necessarily to re-invent Windows 3.x or Windows 9x. I'll try to elaborate more. If you strip the GUI from MS Windows, you have 3 important parts that run to

[Freedos-devel] Windows for Workgroups and FreeDOS

Hi, So for the pure fun of it, I decided to install Windows 3.11 on FreeDOS knowing full well how well it would work. (Cue laugh track) I don’t know how far anyone has gotten with this process but so far what I have found is that FreeDOS (unlike MS-DOS) in it’s default configuration ends up in

[Freedos-devel] 32-bit FreeDOS

I was re-reading some emails and I think I have an idea of how this would work. The goal is existing compatibility so that older DOS applications will run. Obviously, moving to 32-bit will eliminate most of the older processors, HOWEVER. by implementing a Windows 9x like model and build a

Re: [Freedos-devel] 32-bit FreeDOS

in alpha... On May 28, 2015, at 4:58 PM, Mercury Thirteen mercury0x0...@gmail.com wrote: Agreed, that was my exact line of thinking. However, the folks here seem to have come to the conclusion that FreeDOS will not evolve into the 32-bit realm. On Thu, May 28, 2015 at 4:47 PM, Antony Gordon

Re: [Freedos-devel] FreeDOS 2.0

Hi, If I were building the FreeDOS distribution, the only thing that would be included as a part of the official FreeDOS install would be the components that make up the OS depending on the MS/PC DOS version distribution we wanted to emulate. I would also supply these files as one complete

Re: [Freedos-devel] FreeDOS (ODIN) and 8086 compatibility

MORE and SORT typically work on files and console input. When piping a temporary file is created. IIRC that is done even in UNIX from which the file handle idea and pipes originated from. I do believe MODE MONO was specifically for working with Hercules and monochrome video cards, whereas working

Re: [Freedos-devel] FreeDOS (ODIN) and 8086 compatibility

That is pretty old. Is that something that is still needed or wanted? On May 24, 2015, at 5:29 AM, Mateusz Viste mate...@viste.fr wrote: Hi all, Not sure that anybody cares about this, but just in case - I recently tested the 1-diskette FreeDOS distribution ODIN on an 8086 PC, and

Re: [Freedos-devel] Hello!

I think the original goal of FreeDOS has been met, based upon what I remember from back in 2000 or so when I came across the project. I have seen many posts back and forth about adding support for this and that because Windows sucks and so forth and so on. With that being said, here's what I see.

Re: [Freedos-devel] System Configuration Editor

://code.google.com/p/nanosyntax/source/browse/trunk/syntax-nanorc/js.nanorc On Wed, Apr 15, 2015 at 10:15 AM, Antony Gordon cuzint...@gmail.com wrote: In it's present version, it checks the system path and the boot drive and loads the following files: AUTOEXEC.BAT CONFIG.SYS FDCONFIG.SYS

Re: [Freedos-devel] System Configuration Editor

, but On Mon, Apr 13, 2015 at 10:41 AM, Antony Gordon cuzint...@gmail.com wrote: Jayden, I don't know if you have used Windows (I'm sure you have), but my program is essentially a DOS version of the System Configuration Editor that came with Windows 3.x. It's been many years since

Re: [Freedos-devel] System Configuration Editor

a month/month and a half now. -Jayden On Sat, Apr 11, 2015 at 11:55 AM, Antony Gordon cuzint...@gmail.com wrote: I've dug up an old program that I used when I was a PC tech to edit configuration files (AUTOEXEC.BAT, CONFIG.SYS, and the assortment of Windows 3.x config files). It's

[Freedos-devel] System Configuration Editor

I've dug up an old program that I used when I was a PC tech to edit configuration files (AUTOEXEC.BAT, CONFIG.SYS, and the assortment of Windows 3.x config files). It's written in (Turbo) Pascal. Jim suggested I add syntax highlighting and features from MEM to it. I need some pointers on the

[Freedos-devel] New version of FreeDOS and backwards compatibility (RE: FreeDOS 1.2 and 2.0 roadmap discussion)

I was reading all the posts regarding the FreeDOS 2.0 roadmap and a possible move to a 32-bit kernel. So for the TL;DR crowd, I think the FreeDOS roadmap should include every possiblity. Continue reading below if interested. Now while my involvement has been pretty non-existent for nearly 5

[Freedos-devel] (no subject)

http://membres.multimania.fr/eaoyjpa/ _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.

Re: [RDA-L] Announcement of RDA publication date

Hi Diane, Is there a mechanism for typo correction? I was just casually looking through the list and found RDA Form of Musical Notation Tomic sol-fa 'Tomic' should read 'Tonic' Best wishes, Antony -- Antony Gordon Senior cataloguer/System administrator British Library Sound Archive 96

[Freedos-devel] FreeDOS Installer

Who is currently working on this project? I have a couple of ideas I'd like to bounce off them. -Tony _ Rediscover Hotmail®: Get quick friend updates right in your inbox.

Re: [Freedos-devel] Rebooting without restarting the PC

You may have to take a page from the Win98 boot floppy, if possible. If you've ever watched it load, it cycles through several drivers trying to find the CD-ROM...especially in the SCSI territory. Date: Mon, 26 Mar 2007 12:35:38 +1000 From: adam-nos...@servfire.net To:

Re: [Freedos-devel] Projects in need of a maintainer?

Probably the best idea would be to have multiple script engines. Existing DOS apps use .BAT kinda like PowerShell in W2K. It would even be possible to use BASIC (or any other programming language). Default to .BAT, but the script engine could be swapped out...remember overlays? -Original

Re: [Freedos-devel] Projects in need of a maintainer?

I didn't think JP Software had 'abandoned' 4DOS... Date: Fri, 3 Apr 2009 18:01:13 +0200 From: michael_reichenb...@freenet.de To: freedos-devel@lists.sourceforge.net Subject: Re: [Freedos-devel] Projects in need of a maintainer? Well, there is a list more or less up to date.

Re: Please i need your help

Thanks. I spotted that and have emailed Marjorie to let her know that her mail list has been compromised. Best wishes, Antony Gordon On 19/3/09 10:08, Makx Dekkers m...@makxdekkers.com wrote: Please be aware this is a scam, identical to one that was posted here: http://419.bittenus.com/7/9

Re: [Freedos-devel] compressed FAT filesystems

I've read all the posts, now lets look at what DriveSpace/DoubleSpace actually did... You take a hard drive of x capacity, analyze the free space, a 'CVF' (Compressed Volume File) with variable cluster size, move the files on the disk into the newly created CVF file, compressing them in the

Re: [Freedos-devel] compressed FAT filesystems

, assume that anything that is on it is compressed. Then add a compressor like LZO to compress/decompress everything going in and out. That way the file system does not even need to be changed. Imre - Oorspronkelijk bericht - Van: Antony Gordon [mailto:[EMAIL PROTECTED

Re: [Freedos-devel] compressed FAT filesystems

I would think that the information contained in the MS-DOS 6 Programmers reference is free of any restrictions related to that lawsuit. An initial clean room design would allow us to imitate the core functionality of DoubleSpace. This would allow us to read the compressed volume files, if for

Preferred title ???

I like the German expressions which prompts me to wonder if 'Devised title' or 'Constructed title' would capture in English the essence of Ansetzungsform ... and also convey what these titles really are. Antony Gordon British Library Sound Archive On 5/2/08 09:12, Bernhard Eversberg [EMAIL

Re: [Freedos-devel] FreeDOS directory standard (1.1?)

variable. -T Date: Wed, 9 Jan 2008 06:37:59 +0300 From: [EMAIL PROTECTED] To: freedos-devel@lists.sourceforge.net Subject: Re: [Freedos-devel] FreeDOS directory standard (1.1?) Hi! 8-Янв-2008 00:05 [EMAIL PROTECTED] (Antony Gordon) wrote to freedos-devel@lists.sourceforge.net: AG

[Freedos-devel] Installed Application Database Hypothesis

Hypothesis: Implementing an Installed Application Database along with an associated install API would make installing applications easier (perhaps somewhat akin to Windows). What I've learned: Each application comes packaged in a ZIP file that contains a text file with a list of

Re: [Freedos-devel] FreeDOS directory standard (1.1?)

In FreeDOS 1.1 (or whatever) once the directories are finalized, a system variable can be declared in the OS (at the master environment level) like in Windows NT/2000/XP called SYSTEMROOT. On my Windows machine it's C:\WINDOWS. For FreeDOS it can be C:\FDOS. Then the other directories (with the

Re: RDA to FRBR mapping

with different expressions of the same or other works. Antony -- Antony Gordon Senior cataloguer/System administrator British Library Sound Archive 96 Euston Road London NW1 2DB UK tel: +44 20 7412 7412 fax: +44 20 7412 7441 email: [EMAIL PROTECTED

Re: [RDA] Re: FRBR and prime entry: What about relation ships

I'm definitely with Bernhard here. If we don't at least aspire to perfection -- which encompasses practicality and utility -- how can we hope to get anywhere close. -- Antony Gordon Senior cataloguer/System administrator British Library Sound Archive 22 Micawber Street London N1 7TB UK tel

  1   2   >