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
FDRC is nice and comfortable. But you could go further. Now is the TSR module
called by hotkey.
What about making a alternate interface through some interrupt?
Now FDRC serves to users but if you would make some API let's say on 2Fh DOS
multiplex it could serve to programmers also.
I would like
I would like to ask: which file manager is preffered for FreeDOS distributions?
I think it is very important thing - nobody will use DOS without any NC clone.
And it is stupid to not have such thing on the distribution CD/diskette.
Maybe Necromancer's DOS Navigator? It is GNU but it doesn't
Hi,
I have 2 favourite file managers:
NDN - file managers with most features
FW - file wizard, also very good and much faster than NDN.
I would prefer FW in FreeDOS (and it is also open source!). I uploaded
source and binary to
On Sat, 7 Apr 2007, Ladislav Lacina wrote:
I would like to ask: which file manager is preffered for FreeDOS
distributions? I think it is very important thing - nobody will use DOS
without any NC clone. And it is stupid to not have such thing on the
distribution CD/diskette. Maybe
On Sat, 7 Apr 2007 13:38:57 +0200, you wrote:
This all is needed because Blo?ek works in VESA graphics mode so the dialog
window of FDRC can't be displayed.
I wonder nowadays display card still have support of VESA or not.
UNIVBE refuse to work long ago, and other free VESA drivers stopped
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
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
