If the decision is still in favor of having a LIB and INCLUDE directory,
there will have to be subdirectories under theses for each of the compiler
tools, provided the installation can be 'customized'.
This customization, akin to what Ubuntu does, is basically take the package
and customize it
I was thinking Perl (or awk) for the line processing to remove lines because
you may install a lot of apps in between the one you want to delete.
-T
- Original Message -
From: "Eric Auer" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, January 09, 2008 10:36 AM
Subject: Re: [Freedos-devel] Ins
mode is going to eat CPU time
just on the context switch, and if you're polling for position, that's a lot
of switching going on to update a cursor. I think it definitely makes more
sense to roll your own protected mode version of the driver to minimize the
context switch
And just what is wrong with development in C? It could be worse, they could
have used B...
-T
- Original Message -
From: "Oleg O. Chukaev" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 11, 2007 12:42 PM
Subject: Re: [Freedos-devel] File manager
> Robert Riebisch wr
I still think it would still be easier to build a calculator API and just
implement what you need into Blocek. Simple calculations would be of course
easy to do, but imagine having to do complex functions, with nested levels
would require recursive calls on an interrupt...
The original intent o
Since the source is freely available (given its license) why not just add the
parts you need to a library (obviously minus startup and resident code) and use
the equivalent of DOS DLL files (the wonderful world of overlays) or just link
it in.
Then you can add the portions of this program are
I was bored so I tried FreeDOS 1.0 and WfW 3.11.
Setup installed fine (in VirtualPC 2K4) totally trashed in VMWare...
Reboot, attempt to load WfW, get an error message that WfW can't run because
some protected mode application is running that I need to kill. Hmmm, so I look
in the Windows direc
So drivers that already exist for sound cards (I recall DOS drivers for some
C-Media cards) they won't load under FreeDOS? IF that is the case, then
there is some fixes that need to be made to the device driver code and
possibly the MCB (memory control block) chain.
-T
- Original Message --
There can be as many compilers as there needs to be, but I think the whole
point is to make the distribution less confusing, let's pick a particular
tool and the distribution includes that, but you can download the other tool
from the website.
- Original Message -
From: "Aitor Santamar
I was on the web site recently and saw that there is a FreeDOS 1.02 out (or
forthcoming). Are there plans to produce a slipstream update, some type of
installer that checks the existing FreeDOS installation and verifies kernel
2136 (or 37) and a few other sanities, then proceeds to drop in the u
Oops, I forgot...you may want to walk the SFT or the JFT
The assumption here is that you know how to find and "walk" them
-T
- Original Message -
From: "Blair Campbell" <[EMAIL PROTECTED]>
To: "FreeDOS Devel"
Sent: Sunday, November 05, 2006 11:42 PM
Subject: [Freedos-devel] Int 21/A
I would suppose that by walking SysVars, (well DOS actually has this
information) by looking at offset 20h in the System File Table, you can get
the filename in FCB format, for 8.3 filenames prior to DOS 7.x (LFN)...Int
21h/60h can get the canonicalized filename
I think that would be the best b
Well, to be like our more refined OS counterpart (MacOS), there was
typically a 3-6 month update cycle (the longest I remember was 9
months)...hence the 7.5, 7.5.1, 7.5.2, 7.5.3, etc
Or, we could go the Microsoft route...issue a big patch file that updates
and fixes based using a patch prog
I figure the best place would be whereever Blair would check (or where he
would like it to be).
We can borrow a lot of interesting things from Microsoft and other OSes in
certain situations.
For example, we can borrow from Microsoft the idea of an Emergency Boot Disk
(EBD). This disk could be
- Original Message -
From: "Lyrical Nanoha" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 04, 2006 1:44 AM
Subject: Re: [Freedos-devel] FreeDOS Boot CD Question
> On Wed, 4 Oct 2006, Tony wrote:
>
>> Would boot floppy emulation (used on Windows 95/98) be eas
ge read-only and does not
> copy it into memory like ISOLinux does. For the boot process to work,
> however, the boot image needs to be read-write. So ISOLinux is really
> the best choice. Plus, I don't use Windows, so Nero is a problem for
> the distro maintainer.
>
> On 10
r 03, 2006 11:46 PM
Subject: Re: [Freedos-devel] FreeDOS Boot CD Question
> On Tue, 3 Oct 2006, Tony wrote:
>
>> Hi all,
>>
>> Now I know most of us have a Windows machine with a legitimate copy of
>> Nero or maybe even a freeware ISO making utility so I was wonderi
DevelopersMicrosoft has released Virtual PC
2004 free...If you have a qualifying machine...i.e., must run a legit copy of
Win 2K/XP, you can download and install VPC 2K4, install FreeDOS using the
iso and begin testing and development. If you make copies of your DOS boot disks
(from MS,
Hi all,
Now I know most of us have a Windows machine with a
legitimate copy of Nero or maybe even a freeware ISO making utility so I was
wondering...
Why hasn't anyone made a boot CD that boots using
FreeDOS instead of ISOLINUX?
Don't get me wrong, I like ISOLINUX just fine, but
in ret
I would think that only the utilities that need to use protected mode, a DOS
extender, or VCPI would be written using DJGPP or in 32-bit code...at the
moment, I can't really think of a utility that would...perhaps maybe a task
switcher written with a DOS extender that utilizes VCPI to multitask
20 matches
Mail list logo
