Hi, to add my 2 cents...
Linux versions ask for your language (or even geolocate your IP :-))
and then default to your timezone (not needed for DOS if you assume
RTC is on local time) and keyboard layout for that language & place.
I think it would be very convenient if there could be a
Hi Tom, Jerome, everybody,
> however using any OS with the wrong keyboard driver is simply shit.
Trying to explain: Imagine your keyboard has AZERTY written on it. Then
DOS comes and simply assumes you have a "normal" QWERTY keyboard. Now
every time when you press the A button, DOS types Q for
Hi sparky4,
> this is most annoying i cannot do my usual file transfer with the
> freedos 1.2 unzip! gah!! why!?
The 16 bit unzip is probably quite limited in performance
and the range of files which it can unzip, but that is only
a guess... I do wonder how you installed FreeDOS 1.2 on a
To add my 2 cents regarding link files...
For stuff like DJGPP which has many tools, it is probably
a good idea to make a SEPARATE directory for installing DJGPP
and add that to the PATH :-) As NASM only includes a few files,
it can indeed be in the generic FreeDOS bin directory anyway.
Cheers,
Hi Phil,
> - The supplied optical drive driver doesn't seem to handle CD audio tracks
> well. Games such as Tomb Raider do not play any CD audio music. Replacing
> the supplied optical drive driver with resolves this issue for most games.
You wrote that VIDECDD worked. Did any free and open
Hi again,
>> I have tried many optical drive drivers under MS-DOS and VIDECDD.SYS is
>> what I found to work best with games. Other drivers have issues with
>> certain games that use CD Audio, even the OAKCDROM.SYS that comes with
>> Windows 98 for example.
Good to know :-) And good to know
Hi Phil,
>> Well Jerome is right that the "legacy friendly" distro works, but I
>> would still want to know which component of the default distro would
>> need a NEWER than Pentium CPU. After all, Pentium is quite new, too.
>>
>> I would expect that even the normal distro works when you skip
Hi Jim, glad to hear that FreeDOS is so often downloaded :-)
Regarding compatibility, I think about EMS / XMS drivers
and how crashes with their default config might make first
time users give up attempts to try "FreeDOS for fun" and
return to DOSBOX for gaming... I also think about how an
Hi Andreas,
> INT 28 doesn't solve the problem of heavy load for me.
> As I read it's just an IRET by default.
Well INT 28 is an interface for an extra layer of abstraction:
Int 28, int 2a, ah=84, or some other API only have effect when
a suitable driver or TSR such as POWER or FDAPM are
Hi Andreas,
>>> The new version makes use of the hlt instruction.
>>
>> Not good either. You should rather issue a proper 'idle' int and let the
>> task scheduler or power manager do its job.
>
> "task scheduler"? "power manager"? There must be a misunderstanding
> somewhere. I am talking
Hi David,
> I'm the one who started this mail chain. It started as a mere inquiry
> (on behalf of a friend, really) as to whether gcc would be a viable
> compiler. I got my answer: it's not.
when you interpret GCC as DJGPP, then DJGPP is
a pretty nice compiler for larger DOS programs:
It helps
Hi Javier, Steve and Ercan,
> JEMM386 is basically for 16 bit programs.
JEMM386 is for EMS and UMB memory. It is indeed
not a DOS extender. So in a way, you could say
that if your program uses protected mode with a
DOS extender, it will not depend on EMS anyway.
> As previously told switch to
Hi Rugxulo,
think should be moved to "Base" in "FreeDOS 2.0"?
...
> * chksum (6 kb)
How about some of our md5 and sha... sum implementations?
> * arclds (6 kb)
Is that like "file" but only for zip and other archives?
In that case my tiny 2 kB "filetype" tool seems better ;-)
>
Ercan!
> For developing this port, we should remove certain device drivers these
> are manage missing device on Arduino. These drivers are: Floppy disk
Look. The Arduino has EIGHT kilobytes of RAM. If you remove
FAT32 and a few other features, the KERNEL without ANY other
drivers still takes
Hi Matej,
> 1. When loading SRDXMS.SYS (with only SHELLHIGH=COMMANDW.COM and
> DEVICE=JEMMEX.EXE processed at that point), the driver loads, the kernel
> prints "Kernel: allocated 48 Diskbuffers = 25536 Bytes in HMA", then
> right after that I see "Not enough memory" ...
Are you sure that this
Hi! In reply to a thread on freedos-user,
here is some old and deep technical info.
Hi everybody ;-)
> I have Windows 3.11(not WFW) and can't find an
> option to turn off 32-bit disk acass in BIOS.
Not in BIOS, just the Windows 386+ driver for it.
On empowermentzone.com, I must have once
Hi!
> while he didn't specify a warning level, WCL doesn't even warn with
> -W=9 :-< (watcom 1.9)
Wow...
>> In such case the halloc() & hfree() pair does seem to be the only way.
And those are deliberately kept separate from normal
memory allocation calls because of the bad access
Hi Bart,
cool to hear about those FreeCOM updates!
Could you tell more about the comResFile
memory leak? Does it fix an old, elusive
bug which has been on the list repeatedly?
Thanks for the updates!
Eric
--
Check
Hi David,
> The EGA check does not come back positive on my VGA machine.
> Is this expected?
We suggested several: Do you mean the Pascal one suggested
by Mark, the PC Mag one suggested by Mateusz, or the ones
suggested by me? If all of them, then I would say NO, this
is not expected. If SOME
Hi David,
>> 1) new pixels = (old pixels & mask1) | (new pixels & mask2)
>>
>> Where mask1 and mask2 are the negated forms of each other.
That one only works for boolean masks, but it works on 386.
>> This even works for alpha masks:
>>
>> 2) new pixels = (old pixels "*" mask1) "+" (new
Hi, just a quick extra idea: You could read about
the PCX file format for 8-bit colors and define one
color to be "opaque". Then you can store your image
in PCX format in RAM and do run length coded BLOCKS
of either overwriting or not overwriting pixels on
screen, without needing per-pixel
Hi!
1) new pixels = (old pixels & mask1) | (new pixels & mask2)
Where mask1 and mask2 are the negated forms of each other.
>> That one only works for boolean masks, but it works on 386.
> By boolean mask, do you mean something like all 1s over the colors for
> opaque and all 0s
Hi! I am not sure whether I understand your method, so
maybe you can explain it in more detail. Is the alpha
mask 1 byte per pixel, either 00 or ff per pixel? The
multiplication is costly. You can also use bit test
and "set conditionally" (to 0 or 255) and "move
conditionally" byte sized 386
Hi David,
> I've discovered something weird (to me). I'm on a 1998 Sony Vaio with a
> Pentium 3 processor running FreeDOS 1.2. I have a test program which
> draws 64 full frames to the screen via VGA mode 13h. Each frame is a
> different color to force a full redraw. In addition, I draw a
Hi David,
so basically you want to find out how fast you can
update blocks of 64 000 pixels, starting at a VSYNC
and if possible taking at most very few VSYNC periods
until the update is done. Assuming ALL pixels change.
> No. In fact, my copying routine is extra slow, because since mode 13h
>
Hi David,
>> so basically you want to find out how fast you can
>> update blocks of 64 000 pixels
>
> I never said that...
What I mean is that you changed ALL pixels to make
sure to know what the frame rate in the WORST case
is, when ALL 320 x 200 pixels actually need updates.
>> You
Hi David,
> 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 to enter graphics mode?
I suggest limiting
Hi :-) Glad that we are inspiring you, Jerome ;-)
But I disagree about spending 35 for a book - you
can find plenty of information on the web, because
that topic was really popular in the early days of
the web. https://hornet.org/ for example gathered
gigabytes of software and information in
Hi Ercan,
> FreeQB:
> FreeQB is replacement for Microsoft QBASIC. FreeQB is
> QBASIC.EXE for FreeDOS and compatible QBASIC. It may
> run 8086 and low memory.
A GOOD BASIC is hard to write! I recommend to use the
existing FreeBASIC and support their efforts towards
a good IDE for it and
Hi Paul,
> Hi. About 30 years ago, someone made a comment
> on a group saying "until DOS is made 32-bit, DOS
> extenders are just a kludge".
Actually fd32 tries to be better than DOS + extender
by having a protected mode kernel, but it has been
a while since there was news from them and
.1 WDCTRL,386 driver insists on using - else it aborts with
"Invalid DOS version" (replaces handler by dummy, probably to find
out which int 13 drive is behind which drive letter!?).
Win3.1 DOSX calls int 2f.4a01, query free HMA space: BX = 0 = no
Hello TK Chia,
about your advanced compression for the 16 bit gcc zip:
> Yes, Info-Zip does not yet support LZMA compression...
> I made a deliberate choice to use LZMA compression...
Please be more specific about the amount of space saved.
It would be very convenient to be able to do
> You can easily open it in DOS using 7z.
Then I would suggest using the .7z file format in the
first place, which probably also saves more space and
makes it more recognizable how to open the file.
Of course one has to take care to stay within the DOS
7z support, assuming that DOS 7z is older
Hi Nils :-)
> when I was experimenting with dev86/bcc, I have written a small pong
> game that runs on bare metal PCs without DOS as well as on DOS, it uses
> only BIOS Interrupts.
>
> upxed it is only 1491 bytes, extracted 2528.
Quite nice for C, but check this 512 byte NASM version ;-)
Of
Hi Nils et al,
So where do I find those tools you mention? I see you added some
links in a second mail, but with which one should I start? ;-)
> http://www.flashdrive-repair.com/2017/10/chipgenius-v417-software-2017.html
>
Hi everybody,
I have a mysterious case of a bricked USB drive, maybe one
of the resident (DOS) USB experts can help me a bit here :-)
After using the flash drive / thumb drive / USB stick in
a Win10 PC with a loose USB contact, the stick stopped to
be recognized at some point. Checking in a
Hi, forwarding a feature request for FDISK from Fritz Mueller :-)
Could FDISK automatically trigger the /MBR action when you:
1. have the code area (offset 0 to 0x1BD) filled with identical
bytes (for example all 00)
2. update partitions
3. after the update, there is an active (boot)
Hi Louis,
> Do you mean something like the SHSU* Image/ISO to RAMDrive utils [0][1][2]
> when you said, " If we had a driver that could directly use CD/DVD media
> like a hard drive and cache changes to RAM, then things could be different
> and possibly even better"?
The problem is the CACHE
Hi Jerome, thanks for the insights :-)
So what is the combined size of all "programs which have settings
or high scores" which the user would like to be updated? Remember
that high scores in ramdisk are lost at reboot anyway and it is
possible that games just continue without error when they
Hi Jerome,
questions about the dynamic size semi-live CD, which are
the minimum amounts of memory for which package sets?
You say with 24 MB you get a system, then at some point
you get BASE, much later FULL or even EXTRA? So I would
like to know the RAM size thresholds for those :-)
[LiveCD1
Hi Jerome,
> LiveCD1 size is flexible...
Looking at your links (PS: typo "intalled") the current
list seems to be, in that order:
BASE, FDI, grep/head/du/sleep/tee/touch/which/less/trch/md5sum,
crc32, slowdown, doslfn, part, xfdisk, xdel, xkeyb, raread,
rawrite, edict, fdtui, fdnet, wget,
Thanks for the package list pointers! :-)
> All release specific settings are in that
> https://github.com/shidel/FDI/tree/master/SETTINGS
> Boot floppies are PKG_FDI.LST with files and directories
> in CLEANUP.LST removed.
> PKG_BASE is what is installed with BASE
Base: The classic mix of
Hi DOS developers :-)
As mentioned on BTTR, there is a really nice series of by
now four tutorials about low level DOS programming, with
multi core and long mode, by Michael Chourdakis :-) There
also is a proposed API which will help you to use multiple
CPU cores in your DOS projects.
The
Hi! Here is a quick overview of problems with various
free XMS drivers - maybe some of the maintainers can
throw in a patch to get improvements :-)
JEMMEX: Only uses 1st free int 15.e820 memory block.
Could use largest block, OR multiple blocks instead.
HIMEMX 3.34: Uses int 15.ea even where
Hi David,
the DOS way of supporting charsets with more than 256 different
characters ws called DBCS and used only in Asian / CJK countries:
https://en.wikipedia.org/wiki/DBCS
This is not exactly UTF-8. Normally, DOS users configure their
system to use one (or switch between a few) 256
Hi :-)
First of all: Congrats! 25 years of FreeDOS with Jim! :-)
After watching that youtube, I wonder what it would have
been like for him having taken that DOS job in Japan :-)
> FreeCOM bugs unfixed for straight 10 years.
Embarassing indeed...
> automatic network card detection
I
Hi Emir,
> https://sourceforge.net/p/freedos/bugs/185/
> Turkish CP 857 encoding is not applied in FreeDOS.
As far as I know, you can use MODE and DISPLAY to
load a CP857 font and you can use Turkish keyboard
layout in at least one of our keyboard drivers. All
source code comments are supposed
Hi Jerome,
> FDI itself can switch display font’s and for reasons I don’t
> feel like going in to at the moment, it does not use
> the codepage system. It uses transient bitmapped text mode
> fonts...
Does that mean FDI can only work in graphics mode? If it does
work in text mode, then why does
Hi Jerome,
as you want to minimize disk usage beyond the already space
efficient compressed CPI format "CPX", how about this idea:
Make a list of all codepages supported by the installer and
read all fonts for those. Because most fonts will be created
from common ancestors, only modifying a few
Hi Michal,
as you mention crosscompilation: DJGPP is a DOS version of GNU C,
but of course the big question is which programming languages you
speak and how much effort you want to put in the graphics. From a
low level perspective, switching to 320x200 MCGA mode (256 color,
default or custom
Hi!
> That will be my point too. Problem on developing for DOS is usually
> you are not allow to debug, unless in DOS. Exception is OpenWatcom,
> which will be my choice.
What do you mean by that? You can debug everything everywhere,
but if you have cross-compiled a DOS program using a
Hi kernel readers :-)
Looking at the development of dosemu2, I find that the
many changes there have moved away from freedos SO far
that backporting became hard, without me ever noticing.
There was the announcement of fdpp in 9/2018, one year
after development started, which morphs the kernel
Hi Tom,
>>> 2). 2017-Jun-9: "#189 Beep function freezes on recently intel platform
>>> (skylake/kabylake)"
>>> * https://sourceforge.net/p/freedos/bugs/189/
> Bart added this function as it seems to be missing from ia16_gcc
Okay so it is only fixed when you cross-compile from Linux?
>
Hi Jim, glad to hear from you about this :-)
> But mostly it's because I hadn't *removed* lesser-used communication
> channels from the website. So we have all these places linked from
> the "Forums" page, but some places are not very populated.
People already *on* the lesser-used channels are
Hi Jeremy and everybody,
I would only suggest any form of automated infrastructure,
central storage, distribution or conversion of translations
if you expect translations to happen frequently, which I do
not, or if you like tinkering with such infrastructures :-)
In the normal situation, I
Hi Rugxulo (and Jim!)
>> https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/ ...
> AFAIK, the maintainer is Jeremy Davis, ...
> https://github.com/PerditionC/fdkernel
I hope there is sufficient advertisement of the github link, Jim?
>>> Is kernel development officially dead? How about
Hi Rugxulo,
Thank you for your binary patch but...
> 1). 2016-May-6: "[Freedos-devel] Beep command can't stop sounding when
> run in Intel Skylelake platorm."
> * https://sourceforge.net/p/freedos/mailman/message/35068370/
>
> 2). 2017-Jun-9: "#189 Beep function freezes on recently intel
Hi!
In short, your FreeCOM beeps are infinitely long.
As you saym beep_l.c and beep_n.c implements them
as beep_low() and beep() as follows:
void beep_low(void)
{
sound(900);
delay(200); /* 400 */
nosound();
delay(100);
}
void beep(void)
{
sound(900);
delay(200); /* 400 */
Hi Thraex,
> Er, may I ask why you don't want to normalize into a single file format?
Simply because somebody has to create and maintain the infrastructure.
Jerome seems to be motivated to do that, at the moment...
- extract package specific translation files from packages
- convert to
Hi!
As experienced user of portable standard file formats, I would like
to say that CSV, with a clear definition of which style you should
use, is much better than "I just send you the ODS and you tweak it
in whatever way works for your conversion to translation data" ;-)
> I saw your new csv
> FAT implementions arent "just swappable" - they are more a adapter between
> the OS interface (FCBs/DOS 2.0 file descriptors in FreeDOS) and the
> blockdev driver.
Yes back in the times DOS was not much more than a BIOS
which helped apps to work with files, hence the D in DOS.
A good idea
Hi!
First, I have to say I am impressed by Jerome's 486 tinkering :-)
And I can confirm that Brix with PC Speaker sound works on my
actual modern hardware. I just rarely boot into raw FreeDOS :-)
> Instead of an official FreeDOS graphics card, perhaps a standard
> FreeDOS graphics API and/or
Hi Jim, a few short additional thoughts:
> But CAB files? No DOS system distributed files in CAB format
I remember DOS drivers for stuff like soundcards shipping
as part of some Windows installers. So it helps to be able
to dig into files meant for Windows, without needing any
Windows or Wine,
Hi Flamengo, welcome :-)
Can you give more details about the Wing game crash?
As we already have some EMACS and EMACS has a thing with
LISP, maybe we already have some LISP hidden in EMACS?
I vaguely remember some thread topics exist in DOS forums,
but somebody else would have to provide links
Hi Jerome,
> The more I think about it. The more I like a having a separate EXTRAS disc.
>
> Possibly even dropping the FULL/BASE choice and having just a BASE.
We did have a separate BASE ISO at some point in the past, but given
your earlier hint that FPC and DJGPP are 70 MB each, I think
Hi Jim, good to think about the package list :-)
If you ask me, the distro has grown large because a SMALL
number of packages are rather LARGE. Even then, when you
do not install all sources, it uses a lot less space: It
would be fine to keep the sources zipped until one wants
to work on a
Hi Jerome,
> not everything required by the installer quite fits on a 360k.
> (Although, I must admit, with a little more pruning and juggling
> by the installer and dropping the 386 kernel, It may just squeeze
> onto a 360)
Sounds like a great solution :-)
Found something interesting in my
Hi Thomas,
> I just had the thought of whether FreeDOS could be installed
> from a floppy image not written to an actual floppy disk.
Sure, we have been using memdisk before as the boot stage of
our ISO, but you can also mount ISO without burning an actual
CD or DVD in FreeDOS :-) It works
Hi Jerome,
> Current shipping kernels 2042, not modified nor recompiled.
Shipping from where?
> FreeDOS LiveCD 1.3-RC3 (Kernel386)
> FreeDOS 1.3-RC3 x86-Floppy Edition (Kernel86)
>
> Issue occurred on real hardware, but is easily reproducible
> using VirtualBox (latest 6.1)
>
> All other
>> The 8086 kernel can be compiled with FAT32.
The question is whether the floppy installer should use
an 8086 FAT32 kernel. Pro: It works with FAT32 partitions
which people may create even for 250 MB drives because
they believe smaller clusters would always be great. And
almost everybody has
Hi Jerome,
let me summarize: You can fdisk, format and use 100 GB FAT32 LBA
partitions using a certain (which?) version of a non-8086, e.g.
386 optimized kernel of FreeDOS. However, doing the same on some
(which?) kernel which is trying to support 8086, you fail to use
FORMAT on said, probably
Hi Jerome,
>> You are welcome to buy me a new harddisk so I can test your
>> 100 GB partitions of unspecified geometry,
> Wish I could. But, I’m on a budget.
I was just trying to emphasize that it is more work for
me to recreate your bug context than it would be for you
to provide more details
Hi experts :-)
http://wiki.freedos.org/wiki/index.php/Releases/1.3/Packages
lists udvd2 in context of "xmgr, rdisk and uide", but that
should be UHDD, not uide, nor udma. Also, looking at
http://mercurycoding.com/downloads.html#DOS
our Wiki does not yet mention UHDD, XMGR, RDISK or UIDE as
Hi Tom,
> most of the size increase (~3,5 K) is because a CLUSTER is no longer
> 16 bit, but 32 bit as required for FAT32, so the code can be used for
> both FAT16 and FAT32.
>
> some size increase (~1,5 K) comes from actual FAT32 specifics, that
> at least theoretically could be unloaded.
Hi!
>> You already mention the functionality on the floppy distro to
>> INSTALL the 386 kernel on 386, but it does not USE the same
>> kernel. Which is a big problem, because the user will still
>> be RUNNING the 8086 kernel from the floppy while they FDISK
>> and FORMAT while preparing to
(Reply to a mail in "New Old-Timer Reporting")
Hi!
Actually the 32 or 64 MB limit only affects EMS. If you
use XMS or a 32-bit protected mode DOS extender / DPMI,
you can easily use 2-4 GB of RAM, depending on how much
is reserved for 32-bit access to your graphics card etc.
Recently, Japheth
Hi!
> laptop is 15 years old, and even that has hardware that is 'too new'
You mean wireless?
> I think you're asking two implicit questions here: a) Should we abandon
> 16 bit hardware as nobody has any, which would mean FreeDOS goes 32bit.
No. Things which work well with 640k can AND
Danilo,
> First of all, if the idea of an 80x25 single file editor frightens you,
> you're either a wimp or too young to have done any programming when that
> was the norm. May I introduce you to Turbo Pascal 3.0? 80x25 text is the
> best there is.
Tom is neither, but you could argue that he
Hi!
Two thoughts inspired by the package survey:
Doszip EMM or DZEMM is a tiny SYS and a small DLL,
I suspect that it only works with Windows?
And while we have several MP3 related packages,
I miss an oggenc package in the survey ;-)
Cheers, Eric
Hi Aniket!
> Like shall I read Minix book etc. or something
> like that to get into OS dev?
Apps for FreeDOS are just apps, not operating system
development. If you want to develop for the KERNEL or
DRIVERS, you probably want to download a copy of RBIL,
Ralf Brown's Interrupt List. Online
Hi Jerome, thanks for your RBIL-HTML version :-)
https://fd.lod.bz/rbil/interrup/index.html
I have not remembered that it contains an Assembly / Machine
Language Opcode List :-) Of course less verbose than Sandpile,
but still interesting that RBIL has one at all:
Hi Danilo and merry holidays to everybody :-)
> So here's the question: Is there a process to pitch new packages
Just pitch them here. And if they are cool pitch them for our
ibiblio or other repositories of other people on the list :-)
>From there, distro inclusion would be a possible next
Hi Tom,
I think Zbigniew should state which version of the FreeDOS kernel
he is using, but because you have asked me so *cough* politely,
I hereby present some test results for a FreeDOS FAT32 enabled
Watcom C compiled Kernel 2038 (2009-05-16) in DOSEMU2...
1. switch to a diskimage-based
Hi people,
Zbigniew has found a problem with "open" which turns out to
be a buffer overflow in several FreeDOS kernel functions :-o
In short, when you open "textfile.txtgarbage", the garbage
is suspiciously silently ignored and "textfile.txt" opens.
Looking at the FreeDOS kernel source code,
Hi Danilo,
> It happens on both Virtualbox and my ancient Compaq NX-8220. And
> indeed, as hinted by several folks, it seems to be connected to fdapm.
I hope using the FDAPM ADV:REG setting instead of
the FDAPM APMDOS setting solves the speed issue?
See the readme ;-)
Regards, Eric
Hi Jerome!
> Mostly, you can easily see the size of each package without hopping out to my
> repo.
Cool idea, but that seems to include source code.
If FreeCOM itself would be 4.8 MB, you could not
even make a boot floppy with it ;-)
There are 64 packages with megabyte sizes, and
the
Hi Jerome,
I suggest to measure package sizes ONLY excluding the source
directories: The binary packages usually still include lots of
accessories and documentation, which are actually useful :-)
You could even do something evil such as making a copy of your
repository, doing a clever one-liner
Hoi Bart, nice to hear from you!
> Tom is right. The truncation is standard documented behaviour.
> It all goes via the internal implementation of TRUENAME
> ( http://www.delorie.com/djgpp/doc/rbinter/id/50/31.html )
> where the path is converted to its fully qualified version.
> quote:
Hi Charles, welcome to FreeDOS!
> Should I use Borland C or Turbo C++ or what. What version?
http://www.freedos.org/contribute/ recommends OpenWatcom C.
I suggest any current version, but preferably the DOS one.
You can use Borland / Turbo if you happen to have it or if
you want to compile
Hi Volkert,
> A few months ago, I opened a feature request to have support for GEMMIS
> added to JEMM386: https://github.com/Baron-von-Riedesel/Jemm/issues/5
>
> GEMMIS stands for *Global EMM Import Specification* and is a mechanism
> for handing over memory management control from EMM
Hi Paul,
> That's because on a AHCI only computer (without PATA or SATA IDE),
> you cannot access the sectors with INT 13h.
Yes you can. For harddisk/SSD. Unless you configure the
computer to disable BIOS completely and boot only UEFI
operating systems.
But in that case, you get plenty of
Hi!
> This is interrupt calls for using PCI devices.
Well you normally do not have to do anything special
to just USE them in DOS, but the interrupts help to
FIND and CONFIGURE them, in case they do not provide
compatibility to standard devices such as VGA :-)
You probably want to configure
By the way, if you want to know which PCI devices you
have, either real or virtual, you may want to try out
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/pcisleep.html
;-)
Regards, Eric
___
Freedos-devel
Hoi Volkert!
While you are creating that very promising VBE/AI AC97
driver, do you have a list of games which support that
interface or which support miles / ail / digipak / midipak
replaceable sound drivers or docs about the driver format?
Thank you :-)
>
Hi Paul,
> I now realize it is still an IDE driver, not an AHCI driver like I thought.
> Anyway, I wonder if the kernel itself would be needed to support AHCI mode
The DOS kernel has nothing to do at all with your drive controllers.
DOS either asks the BIOS to read or write sectors (for
Hi :-)
> Just a bit of FYI despite the project being nowhere near ready to go
> as of yet: there is a small group of us working on moving DOS into
> the 32-bit realm in the form of the [Night
> Kernel](https://groups.google.com/g/night-dos-kernel). As part of
> that journey, we eventually want
hi tom,
> there is simply no DOS application needing even 100 MB.
> making more than 4 GB available won't change this.
i beg to differ: jack's cache can be configured to cache
huge fractions of your partition (which may or may not be
good for performance) and that ramdisk modification by
japheth
Hi Mercury & everybody,
> I noticed a while back that Japheth updated his HiMemX driver, and
> I've finally gotten around to packaging it up for use in FreeDOS.
>
> Also, he's made a new driver which can do what that HiMemX does, and
> more... way more. HiMemSX can access memory above the 4
Hi Andreas,
how do you manage to receive gigabytes of data from a
few dozen peers with mere megahertz of CPU clock rate?
What are the chances to reduce server RAM footprint?
Regards, Eric
> I still use DOS to this day in an industrial setting...
> hundreds of remote machines with tens of
Hi!
> I don't receive gigabytes at once. I have multiple serial lines using a
> RS485 similar communications method (Master - Slave). The peers can be
> up to 1KM away. Each line can have up to 50 peers. Each peer is
> interrupted when it's 9-bit address is called and it starts
> communicating.
701 - 800 of 1009 matches
Mail list logo
