Quick reply, I found the default open sourced e1000 installed driver
also not working for my e1000 device, subsequently downloaded/obtained
the real OEM drivers from third party sites. One of the OEM Dell
drivers, downloaded from Dell, had the included better ODI driver
versus the Intel OEM only h
> On Mon, Jun 23, 2025 at 02:15:48AM -0400, Jerome Shidel via
> Freedos-user wrote:
>Hi,
>
>After reading your reply, I think I may need to clarify what is meant
>by the repository ISO.
>
>The ISO files to which I am referring are created anytime there is an
>update to any package. They are the lat
> On Thu, May 22, 2025 at 05:19:10PM +, mg-forum via Freedos-user wrote:
>Hello,
>
>I have installed FreeDOS 1.4 to a 16 GB USB 2.0 stick. I booted it on AMD
>FX-4100 machine. It was working OK, but I was unable to make sound card work.
>Probably the Azalia sound card is too new hardware for
> On Thu, May 08, 2025 at 04:43:29PM -0400, Roger wrote:
>> On Wed, May 07, 2025 at 02:50:11PM -0400, Jerome Shidel via Freedos-user
>> wrote:
>>
>>
>>> On May 7, 2025, at 2:17 PM, Roger via Freedos-user
>>> wrote:
>>>
>>> F
> On Wed, May 07, 2025 at 02:50:11PM -0400, Jerome Shidel via Freedos-user
> wrote:
>
>
>> On May 7, 2025, at 2:17 PM, Roger via Freedos-user
>> wrote:
>>
>> Forgot mentioning, when booting FreeDOS-1.4 from USB flash media,
>> doesn't appear for
>Qemu with time being +4/+5 hours ahead, I was able to resolve using
>"-rtc base=localtime" options.
>
>However, FreeDOS-1.4 on bare metal, the bios is (again) in local time
>(Dell Optiplex 755), and FreeDOS continues reporting +4/+5 hours ahead.
>Weird.
>
>Roger
Need to follow-up here, just retes
> On Thu, May 08, 2025 at 09:43:32AM -0700, Ralf Quint via Freedos-user wrote:
>On 5/4/2025 2:12 PM, Roger via Freedos-user wrote:
>> Double checked, FreeDOS running on bare metal, the BIOS is in local
>> time.
>>
>> On Qemu virtualized FreeDOS clients, I've
Forgot mentioning, when booting FreeDOS-1.4 from USB flash media,
doesn't appear for having a method for detecting when booting from between
Qemu or a bare metal PC, as hardware configuration (eg. autoexec.bat) between
the two hardware schemes would likely be different.
Roger
__
> On Wed, May 07, 2025 at 10:17:10AM +0200, Alex via Freedos-user wrote:
>Hello, I wanted to ask if there's a way to install full FreeDOS OS on a
>USB stick, not the FullUSB live version, but the full operating system.
Works very well, using Qemu on Linux hosts and when booting from a bare
metal P
> On Tue, May 06, 2025 at 10:38:19AM +, John Thomas via Freedos-user wrote:
>I have gotten FreeDOS 1.4 up and running over Virtual Box over an Ubuntu linux
>host. Now I want to import a DOS executable into my FreeDOS1.4 Virtual Machine
>so I can execute it.
As others have mentioned, a few op
Double checked, FreeDOS running on bare metal, the BIOS is in local
time.
On Qemu virtualized FreeDOS clients, I've added "qemu -rtc
base=localtime", so time offset using qemu seems solved there.
I just need to augment the bare metal clients, why and how +4 hours?
Nothing seems to indicate the F
> On Sun, May 04, 2025 at 07:26:49PM +, John Thomas via Freedos-user
> wrote:
>I am trying to follow the instructions in "Using FreeDos" by Jim Hall,
>Chapter 1, “Installing FreeDOS”, "How to install FreeDOS on a Virtual
>Machine".
>
>Jim's manual is dated 2018. The gist of these instructions i
>> Roger via Freedos-user
>>
>> However, FreeDOS reports the time as UTC, +4 hours ahead of my local
>> time. (EDT local time here.)
>>
>> FreeDOS time seems hard-coded, and doesn't appear to be adjustable?
>>
>> Any way to script within FDAU
I believe most of my computers are using local time at the BIOS level.
However, FreeDOS reports the time as UTC, +4 hours ahead of my local
time. (EDT local time here.)
FreeDOS time seems hard-coded, and doesn't appear to be adjustable?
Any way to script within FDAUTO.BAT %TIME%-4 ???
Think I u
I have the following computer and network ethernet card:
DELL OPTIPLEX 755
Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)
Supposedly the 82566DM is supported by the Intel e1000 driver, however
only NDIS drivers, no apparent ODI. (eg. prodos-22.10.exe,
prodos-24.30.exe, ...)
Regar
Not sure if this email was sent out, regardless mutt says it was
post-poned:
FYI: "\n" are characters within C programming language, symbolizing the newline
character in C character and string literals.
Almost looks like a poorly coded program tried line interpreting the text file
once. Whethe
More consolus than answer, YouTube has demented advertising methods.
Not as if I were learning much watching cleaning videos.
Most videos are also poorly edited, wasting much viewing time. Or
again, maybe it was just the types of videos I was watching?
Youtube-dl, and more recently yt-dlp, pac
Within C programming, the "\n" represents the newline character within a
C character string literals. (Also used within Bash printf and Python
print scripts.)
Almost looks like a simplistic program tried line interpreting the text
file once. Whether from Unix to DOS, vice versa or just line
inte
Yup. This is exactly what I was thinking, except you're a good one or
two steps ahead having a better understanding of EFI/UEFI structure than
I.
I was thinking, booting into a stripped down or minimal Linux kernel,
and if required runit environment, then into qemu. With the NesUEFI
method likely
Wish Intel would create a BIOS emulation layer for booting DOS/FreeDOS
via EFI/UEFI. Ridiculous EFI/UEFI has no emulation layer for booting
older operating systems!
Also wishing for better comprehensible EFI/UEFI documenation. (Could be
just me getting older, but documentation seems lacking in s
> On Sun, Oct 20, 2024 at 02:19:51PM +0200, Eric Auer via Freedos-user wrote:
>
>Hi Michał,
>
>> Hi,
>>
>> > I'm still looking for an inexpensive X86 type SBC that can be used to
>> build a dos only machine.
>>
>> I have one word for you - weeCee.
>
>This is interesting, sort of a DIY designed d
> On Mon, Oct 14, 2024 at 11:24:41AM -0400, Felix Miata via Freedos-user wrote:
>> On Mon, Sep 30, 2024 Daniel Doran wrote:
>>> I got an Nvidia GeForce 2 MX AGP graphics card (256MB RAM), it’s in my
>>> Compaq Presario 6207EA PC. FreeDOS won’t boot with it installed, it just
>>> freezes. Howev
As with likely all of us with experience from DOS and the early
Windows years prior to ACPI IRQ sharing, very likely an IRQ conflict
with the effect of add-on hardware not working as intended. Although
your other two possible resolutions could possibly also cause similar,
however unlikely, but not
/www.amazon.es/dp/B0CMNWWCPG?ref=ppx_yo2ov_dt_b_fed_asin_title
>
>
> Gabriel González González
>
>
> El jue, 3 oct 2024 a las 6:03, Roger via Freedos-user
> () escribió:
>>
>> > On Wed, Oct 02, 2024 at 04:51:13PM +0100, Gabriel González via
>> > Freedos-
> On Wed, Oct 02, 2024 at 04:51:13PM +0100, Gabriel González via Freedos-user
> wrote:
...
>Really I'm studying how to develop a Kernel ( I'm reading a book about this
>, it is a guide to writing the Kernel code on C and at the same time theory
>and explanations ) . This Kernel is a "baby MSDOS"
I have an old Dell 8100 Inspiron (~2008) laptop with am nVidia
graphics card. As I recall, the laptop graphics card requires
enabling something called "quirks" option for the Linux nouveau (DRM)
graphics driver before being able to use the DRM/X/Xorg interface,
else the graphics card emits a blank
After manually removing and manually installing the previously stated package
name using fdnpkg tool, still was getting the error.
However, upon rebooting and then running fdnpkg checkupdates, now seeing zero
packages needing updating.
So somehow it magically fixed itself.
Looks like I'm good to
Although I've just successfully updated a clean install FD13 LiveCD
image (with all packages, no sources) using fdnpkg, only one of the many
packages failed. Oddly with the same error first mentioned on this
thread!
nethack, local version 3.4.3a updating to 3.6.7
again, only stdout or a prompt st
Just installed freedos using the typical recommended FD13-livecd media
image within qemu, and no problems with fdnpkg echoing "removing..." and
then "installing ..." updates.
Since I had no prior knowledge of fdnpkg stdout, I did not even notice
the missing "removing ..." stdout.
I do not think I
> On Sat, Aug 31, 2024 at 11:23:28PM -0400, Jerome Shidel via Freedos-user
> wrote:
>
>
>> On Aug 31, 2024, at 9:11 PM, Roger via Freedos-user
>> wrote:
>>
>> Using FreeDOS 13, first installed within Qemu (host Linux) using FreeDOS
>> Full USB image, a
Using FreeDOS 13, first installed within Qemu (host Linux) using FreeDOS
Full USB image, and getting the following error with fdnpkg:
c:\ fdnpkg update
"Error: Package contains a file that already exists locally:"
If I'm not mistaken, fdnpkg will not automatically upgrade already
installed pac
I tend to agree with avoiding wasting tons of time rebuilding code, code
already built and easily obtained. I found I could easily get lost (down a
rabbit hole) with building and maintaining build scripts, with lots of time
wasted just compiling code. After a decade, moved from using Gentoo
(sour
Could also check-out Gentoo Distribution's ebuild scripts for compiling
dosemu and other dos emulation applications.
Gentoo is a compile from source distribution, and most of the work for
manually compiling applications is already contained within each
application's ebuild (build) script.
Since we're mentioning publishers of exquisite books, books about
programming during the bare metal assembler programming era, a recent
popular book was published (about a decade ago) regarding learning
assembly language programming.
Programming from the Ground Up by Jonathan Bartlett
Publisher: O
Ebay.com is increasingly becoming a gamble. Many are using the online
service(s) for making easy money, rather than selling a
legitimate product. (eg. drug activity, other nefarious activities, ...)
Also, there's really no more Ebay.com customer phone support, likely with
Ebay.com simply relying
I think, you would be crazy not to ask for an interview from a
programmer (or "WABits") from this era!
> On Thu, Aug 01, 2024 at 01:11:16PM -0500, Jim Hall via Freedos-user wrote:
>On Thu, Aug 1, 2024 at 9:51 AM Liam Proven via Freedos-user
> wrote:
>>
>> From Canadian SF novelist Robert J Sawye
Cannot really tell who's exactly at fault. Closed source and proprietary
code.
We are not pushing blame around, just citing we don't have the problem.
On Wed, Jul 24, 2024 at 11:50 PM andrew fabbro via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
> On Wed, Jul 24, 2024 at 3:45 PM M
Me too, except since the downfall of Gates, about a decade ago or so, upon
the realization their statements of Linux being evil fell through, there
has been a steady influx of Windows developers into the world of open
source and Linux ever since.
Heard Southwest Airlines was the only airline worki
A hint, microsoft employees are mad, and they're trying to make a living!
On Thu, Jun 27, 2024 at 11:38 AM Jim Hall via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
> I just realized that someone started spamming our wiki yesterday. So I've
> taken that down until I can clean it out
"DOG is a DOS SHELL, or command interpreter. DOG works on most, if not all
flavors of DOG."
So, this is pun at DOS for being a dog? ;-) This is found on the Github
page.
Think you meant to state, "DOG is a DOS shell or command interpreter. DOG
shell works on most, if not all flavors of DOS."
Ad
I finished reading the "Why We Love FreeDOS" book a few nights ago. A
really good read, and led myself to a similar conclusion, DOS/FreeDOS is a
really good platform for learning and implementing initial experimental
engineering for experimental or working hardware due to simplicity and bare
metal
ent with [Proton Mail](https://proton.me/) secure email.
>
>On Saturday, June 1st, 2024 at 2:51 AM, Roger via Freedos-user
>freedos-user@lists.sourceforge.net wrote:
>
>> Would be really interesting to hear, how people continue actively using
>> DOS today, including their
Would be really interesting to hear, how people continue actively using
DOS today, including their hardware/software environment. Of course, not
including testing environments, as these can get really exquisite! And,
I already realize one of the environments DOS is still used, for
engineering and
>Microsoft is not willing to go to even the minimal effort of searching
>its own archives for the other versions to release them, but if someone
>else finds the code, it will permit the release under a permissive
> licence.
Excuse #1, there's no money being acquired for going over code for
releasi
>I have found that the best DosBox for this kind of thing is "DosBox-X".
>
>It supports applications better than the original DosBox.
Relooking over dosbox-x, yup, seems to have everything anybody might
need, including all of their wants such as networking. Focused on other
things that really mat
> On Fri, May 10, 2024 at 04:43:06PM +0100, Liam Proven via Freedos-user wrote:
>On Thu, 9 May 2024 at 22:20, Roger via Freedos-user
> wrote:
>
>> >They also have pre-compiled packages for Fedora and OpenSUSE.
>> >No manual compilation is needed for either of the
https://wiki.freedos.org/wiki/Main_Page
How do I install FreeDOS?
FreeDOS for everyone:
"We recommend using a PC emulator or virtual machine to install FreeDOS.
If you don't want to install, you can boot the LiveCD to try it out."
And
What do I need to run FreeDOS?
"If you are new to DOS, we reco
> On Thu, May 09, 2024 at 09:52:39PM +0200, Eric Auer via Freedos-user wrote:
>
>Hi!
>> Initially I tried Bochs, but found Bochs either cannot go full screen
>> using SDL2, or I just haven't found the magical incantation...
>
>A quick google says "try alt-enter" (to go full screen). In 2011, this
>
MY EXPERIENCE INSTALLING FREEDOS Took a week or so trying to install a
DOS enviroment along with an install of Word Perfect, quickly
reading/scanning through all available Internet documentation as of
2024/05 date.
Some key bits of information were from Jim Hall's FreeDOS book,
detailing an instal
49 matches
Mail list logo
