On Wed, 11 May 2022 21:41:40 -0400
Jerome Shidel wrote:
> Possibly. Keyboards and Codepages are vary different things. To which
> program are you referring? The program “could” have hard-coded
> keystrokes (always need Y/N…), maybe a setting in its NLS or use an
> environment variable.
>
> :-)
Hi,
> On May 11, 2022, at 11:44 AM, Daniel D. wrote:
>
> Hi, again!
>
> Thank you very much for the swift reply!
>
You welcome.
> [..]
> Thanks, I didn't know about this software.
No problem. It’s still very new and only works on the Package Description Lists
at present. Support for
Hi, again!
Thank you very much for the swift reply!
On Wed, 11 May 2022 08:06:05 -0400
Jerome Shidel wrote:
> First, you need to configure the system for the proper codepage.
> Probably adding/replacing the portion regarding the displayed
> language settings in FDAUTO.BAT with these will do
Hi,
> On May 11, 2022, at 3:56 AM, Daniel D. wrote:
>
> Hi!
>
> I hope this is the correct mailing list to contact.
>
> Recently, I've done some Norwegian translations of the language files
> of FreeDOS, which have been merged into this repository
> https://github.com/shidel/fd-nls (is this
Hi!
I hope this is the correct mailing list to contact.
Recently, I've done some Norwegian translations of the language files
of FreeDOS, which have been merged into this repository
https://github.com/shidel/fd-nls (is this an "official" repo?).
Now that I've added a few translations, I
Hi! Bumping this thread from Jim. I think if the majority of
the games has palette issues, it could be VirtualBox or QEMU
just not properly emulating VGA, VESA, VBE etc., possibly also
depending on the color depth of the host operating system GUI.
Which versions and settings were used? Which
Hi all,
I got in touch with Jim Hall about a month ago, and when he learned that I
still run FreeDOS on vintage hardware, he asked me to test the games that ship
with FreeDOS there. Many of them seem to have issues when run in virtual
machines, and not all FreeDOS developers still maintain PCs
On 12/24/2021 7:49 AM, TK Chia wrote:
Hello Daniel, hello Jim,
Thanks for the tests!
Both games use a combination of kbhit + getch (with the arrow keys
taking an extra getch, if the first one yields either 0 or 224).
[...]
Right now I'm writing a new real mode game (actually, a demake of
Hello Daniel, hello Jim,
Thanks for the tests!
Both games use a combination of kbhit + getch (with the arrow keys
taking an extra getch, if the first one yields either 0 or 224).
[...]
Right now I'm writing a new real mode game (actually, a demake of my
WIP protected mode game,
Hello - I'm the author of both Dungeons of Noudar and The Mistral Report.
Thanks for the tests!
Both games use a combination of kbhit + getch (with the arrow keys
taking an extra getch, if the first one yields either 0 or 224).
While I should certainly write my own keyboard handler, that was very
An interesting (and series of very very long) "hot takes" of FD 1.3RC4 from
the "Temporarily Offline Retro Tech" youtube channel.
FreeDOS Install and Bundled Apps - Part 1
https://youtu.be/j6s50qGZzO4
FDOS! What's in the FDOS folder? - FreeDOS Part 2
https://youtu.be/v-_RqLP_Bgs
More FDOS! = The
On Wed, Dec 22, 2021 at 12:45 PM Bret Johnson wrote:
> I realize that VMs are all the rage these days for DOS, but I would
> also like to see how things work on real hardware. I rarely play
> games myself any more, but games are usually a pretty good test of
> compatibility.
[..]
Yes, that's
I realize that VMs are all the rage these days for DOS, but I would also like
to see how things work on real hardware. I rarely play games myself any more,
but games are usually a pretty good test of compatibility.
The problem is that with real hardware there is WAY more variation than there
Sure, I can start a page on the wiki.
On Wed, Dec 22, 2021, 5:00 AM Jerome Shidel wrote:
> Hi, Jim
>
> Because, there are also VM’s like VMware, DOSBox, DOSBOX-X, Bochs, etc.
>
> It might be good for you to start a compatibility spead-sheet.
>
> Jerome
>
>
>
>
Hi, Jim
Because, there are also VM’s like VMware, DOSBox, DOSBOX-X, Bochs, etc.
It might be good for you to start a compatibility spead-sheet.
Jerome
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
Jim Hall [22/12/2021 02.02]:
I am testing on both VirtualBox ("VB") and QEMU. (I don't seem to have
sound set up properly on VirtualBox, but it works fine on QEMU. If
someone else uses VirtualBox and has sound working, please share your
config info.)
What are the options you use when starting
I'm starting to go through all of FreeDOS 1.3 RC5 and testing
everything. I'm starting with Games, so I wanted to start a thread
dedicated to Games discussion.
I am testing on both VirtualBox ("VB") and QEMU. (I don't seem to have
sound set up properly on VirtualBox, but it works fine on QEMU. If
Just testing my new email address,to make sure it is on the DEVEL list
again.
-Jayden
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just
Hi Mike,
Ulrich Hansen just reported a bug in my FTP server and I have verified
it. The technique that I use to detect if a drive is valid behaves
differently under FreeDOS than under PC DOS or DOSBox.
Can anybody point me to documentation or code for DOS INT 21,32h ? The
function is
On 10/3/2011 6:42 AM, Eric Auer wrote:
No, it actually behaves as expected if you see this in DOSEMU: Only
FAT drives have a DPB, but network / redirector / CD / DVD drives
do not, so as RBIL already says: FFh invalid or network drive ;-)
I missed the network drive part, which makes the code
Hi Mike, here is the code of int 21 function 32 of FreeDOS:
/* Get DPB */
case 0x32:
/* r-DL is NOT changed by MS 6.22 */
/* INT21/32 is documented to reread the DPB */
{
int drv = (lr.DL == 0 || lr.AH
Eric - thanks for sending the code. I can't see the immediate problem
so I have to write some testcases.
I'm using VirtualBox to host/run FreeDOS 1.0. As far as FreeDOS is
concerned, there is a Drive C and it is a physical IDE drive. (It is
actually a virtual drive emulated by
Hi Jim,
while I agree that more and more software is creeping into
the distro if we add all interesting things, this list
is still somewhat comparable to full 1.0. Yet already 1.0
had exactly the creep problem that you describe. So first
we should indeed get a more basic 1.1 ready before we can
Hi again Rugxulo,
So VMware needs PCNET? VirtualBox needs AMDPD? QEMU needs NE2000?
Anybody know BOCHS? (Yes, I'm assuming more re: emulation than real
hardware here, isn't that reasonable?)
Bochs emulates a bad(?) NE2000 and a nonstandard PCI Pseudo NIC
for which an Etherboot driver exists
Most attractive to average users (rough guess):
Mpxplay
Bret's USB
CuteMouse
mTCP + common packet drivers
Arachne
WGET
Mined
GNU Emacs
Perl
Python
OpenGem
OpenWatcom + NASM
FreeDoom + Eternity Engine
HXRT + HXGUI
p7zip
DJGPP (GCC + GPP + Watt-32)
UIDE + XMGR + RDISK + SHCDX33E
Hi,
On 7/17/11, Jim Hall jh...@freedos.org wrote:
Most attractive to average users (rough guess):
While I'm glad to see enthusiasm for what the next FreeDOS distro
should include, and you've got a lot of interesting stuff above, I'll
point out that this is a classic example of scope creep.
Op 17-7-2011 23:23, Rugxulo schreef:
This was merely an exercise at naming popular, i.e. heavily-desired,
apps that most common users might probably want. It is not intended to
reflect my own goofy needs.
And besides, most of these already were in FD 1.0, so nyah. ;-)
For a full CD it's
Hi,
On 7/17/11, Bernd Blaauw bbla...@home.nl wrote:
Op 17-7-2011 23:23, Rugxulo schreef:
This was merely an exercise at naming popular, i.e. heavily-desired,
apps that most common users might probably want. It is not intended to
reflect my own goofy needs.
And besides, most of these already
On 7/15/2011 11:33 AM, Bernd Blaauw wrote:
Op 15-7-2011 5:08, Michael B. Brutman schreef:
- How do I use the new installer that Jim has been working on?
It's in the new ISO that I plan to upload by Sunday evening. Still need
to work out some things to make it a smoother experience. The initial
Op 16-7-2011 16:30, Michael B. Brutman schreef:
Good - I await the next revision. I'm trying to do my part here by
testing it ..
great, thanks.
On all of my machines (DOS, Windows and Unix) I try to keep the optional
packages separate from the core OS functions. So DOS will live in /DOS
Hi,
On 7/16/11, Bernd Blaauw bbla...@home.nl wrote:
Op 16-7-2011 16:30, Michael B. Brutman schreef:
Does this mean that they will be put on the CD later, or that the user
has to find a different way to get them on the machine? I think that
every packet driver known to man probably fits
Hi Mike,
- Are all of the binaries always put into the one bin dir? I expected
Yes, like with Linux. Also remember that DOS often has
small environment variable space, so we keep PATH short
and have no opt or usr local ;-) However, FreeDOS
1.0 did have a few packages using further
Some general questions and comments from a newbie:
- How do I use the new installer that Jim has been working on?
The new Install isn't in the first 1.1 test release. Look for it in the next
test distro, if Bernd decides it is okay for testing.
Op 15-7-2011 5:08, Michael B. Brutman schreef:
- How do I use the new installer that Jim has been working on?
It's in the new ISO that I plan to upload by Sunday evening. Still need
to work out some things to make it a smoother experience. The initial
menu showing which CD drives were found
On Fri, 15 Jul 2011, Bernd Blaauw wrote:
See above, minimising things. WATTCP programs are usually compiled as
DJGPP programs, having kind of huge disk footprint compared to your
drivers for example.
The Watt32 libs are pretty big. The regular WatTCP is a lot smaller and
16-bit Internet
I just took my first pass at installing 1.1 using the ISO image that
Bernd Blaauw provided a few days ago. I got it done, but it was not
without a few problems. I'll assume those are user errors until I can
prove otherwise.
Some general questions and comments from a newbie:
- How do I use
Hi all,
good news:
today I had gpf problems with a 160Gbytes SATA disk... I updated DOSFSCK
to the latest version 2.11c and it worked like a charm :)
Thanks to whoever maintains that (I gess it would be Erik)...
Alain
Hi,
I could only test the base disc. Drive C: is a FAT32 drive (FreeDOS and
WinXP pre-installed).
(*) You can choose between 6 items, but only 2 are visible in the
FreeDOS install / FreeDOS safe mode menu.
(*)There is no info that you have to tpye ESC to exit PG
(*)After install program I
I collect my experiences of installing FreeDOS 1.0 base iso without
source on a hard disc with 2 FAT32 (primary and logical) partitions:
(1a)When INSTALL program exits:
(*) the pc hangs or
(*) an error messag is displayed again and again and agin (a problem
with FOR command)
(1b)When I change
39 matches
Mail list logo
