Hallo Herr Ralf Quint via Freedos-devel,
am Dienstag, 16. Juli 2024 um 20:35 schrieben Sie:
> On 7/14/2024 2:10 AM, tom ehlert via Freedos-devel wrote:
>>> And it is a basic fact that DOS (any DOS!) is a single-user, single tasking
>>> operating system. That excludes the
> And it is a basic fact that DOS (any DOS!) is a single-user, single tasking
> operating system. That excludes the use for any of those overly ambitious
> dreams of yours.
You seem to ignore that the multitasking Windows 3.11 did run on top of DOS.
Tom
Dear Liam Proven,
am Dienstag, 2. Juli 2024 um 14:07 schrieben Sie:
> On Tue, 2 Jul 2024 at 03:22, Richard Stoltenberg via Freedos-devel
> wrote:
Richard is obviously completely clueless and maybe had a joint/beer to much.
Just treat him like a troll and ignore him.
Don't feed the trolls.
> We could call it "Holes". Because a) it's tightly connected to "Windows"
IMO that's a pretty good name
> and b) there will be plenty of missing API for the foreseeable future.
for an unprobabable project.
> And Jim could announce this on June 29th :D
> What about the ArcaOS?
Are you missing the fact that it's neither free nor cheap.
Tom
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
> One more hint for your testing: Gnuchess requires NANSI to be loaded before
> playing, would it be possible to add this information anywhere?
in that case Gnuchess should check if ANSI/NANSI is loaded and say "ANSI.SYS is
needed for this program and exit" otherwise.
no need to document
Hallo Herr Bernd Böckmann via Freedos-devel,
am Freitag, 7. Juni 2024 um 13:46 schrieben Sie:
>> Am 04.06.2024 um 00:24 schrieb Eric Auer via Freedos-devel
>> :
>>
>> 3. Or we could give SYS support for multi-sector FAT32 boot
>> sectors, which would be necessary for automatic switching
>>
> but there are several different atexit calls activated. I hope you
> can register multiple atexits without causing problems?
Of couse.
> Will they
> be called in a sensible order when leaving the game?
in reverse order that they were called.
Tom
> 5. Boot the Pocket386 from the CF card
> It stops at "Loading FreeDOS" and just hangs there
these symptoms are remarkably similar to " Problem booting FreeDOS on Book8088
PC-XT laptop"
from earlier this year.
Tom
___
Freedos-devel mailing list
>> :http://master.dl.sourceforge.net/project/api-simple-completa/
> Warning! Malware detected. Download at your own risk.
> Just go away.
correction. on virustotal.com 32 major virusscanners found no issue with the
.zip.
I don't know what sourceforge is complaining about.
Tom
> :http://master.dl.sourceforge.net/project/api-simple-completa/
Warning! Malware detected. Download at your own risk.
Just go away.
Tom
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
>> 64 Ki * 16 KiB = 1024 MiB. (The actual maximum amount of clusters is of
>> course slightly less than 64 Ki, to be exacting.) So you're off-by-one,
>> a "2 GB" file system cannot possibly be fully utilised with FAT16 at a
>> 16 KiB per cluster size.
> Ah, OK. My apologies.
> Off-by-one
Hi Wilhelm ,
am Donnerstag, 23. Mai 2024 um 12:56 schrieben Sie:
> Hi Tom,
>
> Thank you for not having a choleric attack!
;)
> FDT24xx are monthly trial versions (if I remember right, you know it for two
> or three months now).
I know about "FreeDOS distributions", but I don't care
>> it seems that no knowledgable person finds zoo interesting enough to fix it.
>> and those who care about zoo have no clue.
>> I regret that I have to say this.
>>
>> Tom
> Was zoo even popular in its heyday?
I don't think so.
> I feel like when it comes to DOS, for the last 30 years it's
vel@lists.sourceforge.net
> Cc: "E. C. Masloch"
> Subject: Re: [Freedos-devel] zoo
> On at 2024-05-19 00:37 +0100, Liam Proven via Freedos-devel wrote:
>> On Fri, 17 May 2024 at 17:14, tom ehlert via Freedos-devel
>> wrote:
>>
>>>> Below 1GB F
>> I ran one more test with zoo. It runs with FAT16 998 MB but not with FAT16
>> 1025 MB.
> Below 1GB FAT16 uses 8kB clusters. From 1GB-2GB it uses 16kB ones.
> (Below ½GB it uses 4kB.)
That would require FAT17.
and indeed the problem (which was solved in january) is with clustersize
32KB
Hallo Herr Ralf Quint via Freedos-devel,
am Mittwoch, 8. Mai 2024 um 20:30 schrieben Sie:
> On 5/8/2024 1:22 AM, tom ehlert via Freedos-devel wrote:
>>> It's on the website, under the "developer" section.
>> in my version of firefox, there is no "developer&quo
> I hate to be the one to tell you, but "how Tom navigates a website" is
> not the same as "how many others navigate a website."
As a matter of fact, Tom navigates the web as any other people:
the way the websites make us use their website leaves usually little choice.
> Today, many more
>
Hallo Herr Jim Hall via Freedos-devel,
am Mittwoch, 8. Mai 2024 um 15:43 schrieben Sie:
> On Wed, May 8, 2024 at 3:23 AM tom ehlert via Freedos-devel
> wrote:
>>
>>
>> > On Tue, May 7, 2024, 8:46 PM Green Fog via Freedos-devel <
>> > freedos-devel@l
k, and you'll find a page with more information and links
> to the source code.
> I put this here because usability testing showed that people expected to
> find FreeDOS source code in a place where developers would find other info
&
Hallo Herr Steve Nickolas via Freedos-devel,
am Dienstag, 30. April 2024 um 17:07 schrieben Sie:
> On Tue, 30 Apr 2024, Bernd Böckmann via Freedos-devel wrote:
>> Sadly not. Only the binaries are released under MIT through the repository.
>>
>>> Does that mean we finally have a genuinely open
all GITHUB files have LF line endings.
as old MSDOS tools insist on CRLF line endings, you have to convert the files
first.
Tom
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
> Surprisingly, I have not received any communication whatsoever regarding
> libm.
possibility 1) libm orks exactly as laid out in the documentation.
poosibility 2) nobody cares about libm
btw: do you have a lot of communication about EDLIN?
Tom
> I wonder if they can be released (at least, binary-only) so people can
> use them on other things?
> Since it is listed in EMMS*.ZIP's makefile, reproducible builds can't
> be built without them.
so what?
Tom
___
Freedos-devel mailing list
Hello,
> In freedos/files/dos/emm386/emm/2.2/emms226.zip, its makefile shows it
> need to use sy2pack.exe or sy3pack.exe to pack just-compiled
> emm386.exe.
sy2pack/sy3pack used to be the only compressor that was able to compress
binaries
that act both as drivers (device=himem.exe) and
Hallo Herr Liam Proven via Freedos-devel,
am Mittwoch, 31. Januar 2024 um 18:23 schrieben Sie:
> This could be useful to several here, I think.
> https://and0uille.net/misc/debug90.html
thanks for the link.
SoftICE was indeed tremendously useful when debugging the FreeDOS kernel; I
think
> I am working on an academic project that requires understanding the MAD
> programming language so I can pick apart (and faithfully recreate) an old
> MAD program. That's the Michigan Algorithm Decoder, from 1959 and the early
> 1960s.
it would make this much more interesting if you would
>It is also possible to write TSRs and Device Drivers in higher-level languages
>but it is very cumbersome and you need to do a lot of "tricks" to get things
>to do what you want without wasting a lot of memory.
I wouldn't call it "tricks". It's "technics". Advanced programming is usually
not
Hallo Herr Jim Hall via Freedos-devel,
am Dienstag, 26. Dezember 2023 um 17:42 schrieben Sie:
> I actually never learned DOS assembly programming, but decided I'd
> like to start.
> What assembler do you recommend,
for noobies, they are all the same: take NASM.
"hello World" programmers don't
> Is there a FreeDOS walk thru of the source code that you would consider
> helpful to the uninitiated?
if you mean the *kernel* source, please say so.
> I want to start down the road to more bare
> metal coding and would love to be able to help with FreeDOS in the far
> future but I'm not
gt;
>>> Please be more specific about what went wrong and which
>>> work around in which code snippet resolved the problem.
>>> I think a workaround in FDXMS286 could be a good idea.
>>>
>>> Regards, Eric
>>>
>>>
>>>
; the original MS-DOS supported, including pre-386 hardware, or you can
> just as well bin the original premise. All in all I think your reply
> needlessly confrontational.
> Cheers, Hippo.
> On Wed, 1 Nov 2023 at 23:13, tom ehlert via Freedos-devel
> wrote:
>>
>>
> is there any supported XMS driver for 286 that FreeDOS provides? himemx
> dose not support it and the fd286xms driver is old and not supported.
why do you think that software for 30+ years old hardware needs to be
'supported'.
it's the same as last year, and 20 years before.
And will work
>> I work for embedded software on the board Vortex86DX 800MHz.
>> I need at least SVGA graphic (800X600).
> https://www.vortex86.com/products/Vortex86DX SoC has no built-in VGA,
https://icop-shop.com/product/vdx-6324rd/ has buildin VGA so there are at
least some boars available.
it might
Hallo Herr Ralf Quint via Freedos-devel,
am Donnerstag, 5. Oktober 2023 um 02:50 schrieben Sie:
> On 10/3/2023 11:30 AM, Michael Brutman via Freedos-devel wrote:
>> There is no point in punishing everybody by shipping tools that most >
>> people don't use. You can probably count all of the
3280/LICENSE
>> [3]: https://hg.pushbx.org/ecm/inicomp/file/41860de1db0e/heatshr.asm
>> [4]: >
>> https://hg.pushbx.org/ecm/ldebug/file/654bf2cbfffb/source/hshrink.asm#l208
>> [5]: > https://hg.pushbx.org/ecm/ldebug/file/654bf2cbfffb/source/mak.sh#l309
>>
>>
> Note that I have a different goal to most people. Most people
> want to run DOS-era software. I want to redefine the DOS era
> now that the "rush to market" is long over.
> Any thoughts?
Yes.
Good luck with that.
Tom
___
Freedos-devel mailing
Hi Ralf,
am Montag, 24. Juli 2023 um 20:06 schrieben Sie:
> On 7/23/2023 9:35 AM, tom ehlert via Freedos-devel wrote:
>>> ISTM that all the other graphical shells in FreeDOS are even less
>>> useful than GEM, and it would be no loss to remove them... but adding
&g
> ISTM that all the other graphical shells in FreeDOS are even less
> useful than GEM, and it would be no loss to remove them... but adding
> GEOS would be a win.
in what way is GEOS even related to FreeDOS which runs on PC's?
unless wikipedia has it completely wrong GEOS needs 6502 (commodore
> So in short, DOS is not great for real-time stuff,
+1
> but it certainly is not as bad as Windows :-p
Windows is actually quite good for realtime stuff (even hard realtime stuff) -
if you write your time critical stuff as a device driver.
there are a lot of provisions, directives, howto's
Hallo Herr Harald Arnesen,
am Freitag, 23. Juni 2023 um 21:29 schrieben Sie:
> Patrick McCavery [23/06/2023 18.13]:
>> If I could run format \s right from Linux, I could use all of my
>> existing toolchain and I would not have to run this command on a USB key
>> from within qemu.
>> > Could
Dear Vacek,
> If it wasn’t on the to-do list earlier, I'd kindly request a mapping of
> codepage 3845. Please map code point 0x9F, the Ft sign temporarily to
> U+FFFD and add a comment to the definition file along the comments of
> "addition of the forint sign into Unicode pending".
> This would
Hallo Herr Ralf Quint,
am Montag, 5. Juni 2023 um 23:06 schrieben Sie:
> On 6/5/2023 1:56 AM, jer...@shidel.net wrote:
>>
>> Hi All,
>>
>> /There are two separate issues when using: |IF EXIST ?:\NUL| /
>>
>> /I'm lazy and wrote up a info text file over at >
>>
> This could look something like this. The system boots as normal. A CONFIG
> option like ‘DOSMOVE=UMB’ could exist.
there exists already the DOS=UMB option, meaning "move as much as possible to
UMB".
IIRC when Bart implemented this he only moved DATA (buffers, LASTDRIVE=,
current
Hi Jerome,
if you make it a logger.exe (rather tehn .com), UPX should be able to compress
dual mode programs.
Tom
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Hi ecm,
> [1]:
> https://gitlab.com/DOSx86/logger/-/blob/aae3dfddcdacfea18950a96ce9449767c20b2d66/source/logger/common.inc#L267
this got me looking into this 'too slow' detection method.
and it is indeed slow. as in molasse. let me explain.
a) isn't
%%Comparing:
inc di
Hi,
> At present, the interface program for Logger just performs a slightly
> optimized brute force search for the Logger device driver. Although reliable,
> it is very slow compared to providing a simple interrupt call to test for
> installation.
given that this detection will be done once
Hi,
> Don’t know if the issue is in the Kernel (0.85a), HimemX (3.38), JEMM386
> (5.83) or My Head.
it's in the Kernel - or in your head.
to decide between these two alternatives it's always helpful to send your
actual sources - not
an english description of what you had intended to do.
and
Dear Bret,
> The article is found at
>> https://pushbx.org/ecm/dokuwiki/doku.php?id=blog:pushbx:2023:0321_cpu_performance_comparison
> I mostly agree with you and your article, but:
fine that you agree, but at most 50% of the article is even close to
'right'.
>>> Conclusion
>>>
>>>
> For
> instance, vecho (which displays many user messages, like “Welcome to
> FreeDOS”) don’t output text the same way as other programs and do not get
> captured at present.
I don't know how and why vecho displays text different. However it
could "display" the text twice: once in the
quot; or "sub-optimal" or something
> like that, but the results are very real and are simply what they
> are. Also, as already stated, the purpose of SLOWDOWN is not to be
> a benchmark but you can indirectly use it as a benchmark.
> ___
> Freed
Hallo Herr Bret Johnson,
am Donnerstag, 23. März 2023 um 20:31 schrieben Sie:
>>> Even though a 350 MHz K6-2 is WAY faster than my 3.3 GHz i5? And
>>> again, I know it doesn't make any sense, but it's still true.
>>>
>>> As far as I can tell, the Emperor has no Clothes.
>>
>> I'm confused by
Hi,
am Dienstag, 21. März 2023 um 23:26 schrieben Sie:
> Hello!
The article is found at
> https://pushbx.org/ecm/dokuwiki/doku.php?id=blog:pushbx:2023:0321_cpu_performance_comparison
I mostly agree with you and your article, but:
>Conclusion
>CPU-bound benchmarks are much faster on a modern
Hallo Herr Rugxulo,
am Montag, 20. März 2023 um 23:20 schrieben Sie:
> Hi again,
> On Mon, Mar 20, 2023 at 5:06 PM Bret Johnson wrote:
>>
>> This is something much more serious than a "tradeoff" or a
>> "regression". My new i5 CPU appears to be spending _at least_ 99%
>> of its resources NOT
Hallo Herr Bret Johnson,
am Donnerstag, 9. März 2023 um 23:27 schrieben Sie:
> The computer I'm currently using is a few years old, old enough
> that I can boot DOS on the actual hardware. The CPU is an Intel i5-4590
> running at 3.30 GHz.
> I have a DOS program I wrote a long time ago,
> IDLEHALT=1 works for my machines and reduces the CPU load under
> VirtualBox to nearly zero at the command prompt.
:-)))
FDAPM whatever
should be REMified.
OTOH this seems to be a problem between FDAPM,
VirtualBOX and Watcom Installer. Whoever wants to develop ON FreeDOS
...
>> Am
Hallo Herr Bernd Boeckmann via Freedos-devel,
am Freitag, 17. März 2023 um 12:52 schrieben Sie:
>> Any thoughts?
> I have some additional data:
> 1) Pentium MMX 166, T2303 default installation:
> Installation time Open Watcom 1.9, FDAPM activated: 7:09 minutes.
> After FDAPM OFF: 4:30
Hi,
> while hacking on FDISK and having some thoughts about different
> sector sizes I stumbled upon the problem that the extended INT13
> function 48 may return a sector size != 512 while the INT13,0X
> functions always seem to operate on „virtual“ 512 sector sizes.
all INT13 functions operate
Dear Bret ,
am Donnerstag, 9. März 2023 um 23:27 schrieben Sie:
>>> My terminology is compliant with that definition.
>>
>> *Sigh*
>>
>> I am aware of that. The general term "re-entrancy" is not synonymous
>> with the specific term "reentrant kernel".
> So re-entrancy is not synonymous with
>> A Virtual Machine for the rest of us is something like VMWare, Qemu,
>> VirtualBox, etc. - something that simulates a real machine. You
>> load a real operating system in it and the operating system
>> generally doesn't know or care that it's actually in a simulation.
> So "the rest of us"
> That depends.
whatever 'depends'.
> Besides poorly optimized system caches, is the
> installer doing things that blow the cache and increase the miss rate?
whatever the installer is doing: unless you find a valid 'this is
doing something in a stupid way' point this installer is as much a
> Over a month ago, I opened an issue on the FreeDOS project on
> GitLab about the Open Watcom v2 installer being extremely slow in
> FreeDOS. It takes an hour or more on FreeDOS, while the same
> installation completes on MS-DOS 7.1 within just a few minutes.
either you report your config.sys
> The SDA of MS seems fairly well documented in RBIL, but I'd be
> pretty surprised if all DOS clones (particularly Virtual Machines
> like DOSBox) are compliant so it may not be a good idea to pursue.
> I suspect FreeDOS would be pretty close to compliant, but I'm not even sure
> about that.
Hallo Herr Bret Johnson,
am Montag, 6. März 2023 um 19:43 schrieben Sie:
>>> 386MAX supports the Global EMM Import Specification (GEMMIS), which
>>> allows Windows 3.x to start in 386 Enhanced mode, even when the EMM
>>> manager is loaded. (The documentation in the 386MAX source code
>>> seems
Hallo Herr tom ehlert,
am Montag, 6. März 2023 um 10:14 schrieben Sie:
> Hallo Herr jer...@shidel.net,
>> Any volunteers?
> to start first: what would be the point to have 386MAX in freedos
> distribution (after 20 years without it)?
> I know that it was somewhat important
Hallo Herr jer...@shidel.net,
am Sonntag, 5. März 2023 um 22:43 schrieben Sie:
> Hi all,
> I spent a few minutes looking at 386MAX.
> Unfortunately, it is going to take at least a some work by someone
> (not me) before it could even be considered for inclusion.
> First, it cannot even be
Hallo Herr Bret Johnson,
am Freitag, 3. März 2023 um 23:40 schrieben Sie:
>>> But I was still wondering if anybody has seen it done before since
>>> I don't think I've ever seen an actual implementation.
>>
>> neither did I.
> Probably not worth pursuing. But even just the idea of a
>
Hi,
> I'm wondering if anybody has any experience, or has seen any source
> code, related to manipulating the DOS Swappable Data Area (SDA) to
> make DOS re-entrant. I working on at least one TSR program right
> now where I think something like that might be useful but I've never seen it
> done
>>> The reason why partition boundaries are aligned on cylinder boundaries
>>> is that a lot of other OSes also rely on that.
>> any example of this? I don't any (not completely braindead) operating
>> system would rely on that; it's just the way that FDISK and friends
>> place partitions on the
Hallo Herr Ralf Quint,
am Mittwoch, 1. März 2023 um 18:08 schrieben Sie:
> On 3/1/2023 8:22 AM, Bernd Boeckmann via Freedos-devel wrote:
>> Hello,
>>
>> I am now reaching a state where I think that FDISK not any longer breaks the
>> partition layouts created by itself.
>>
>> However, there is
Hallo Herr Rugxulo,
am Mittwoch, 1. März 2023 um 10:22 schrieben Sie:
Hi again,
> It's entirely possible that Richard dislikes DOS that much.
I also dislike Richard. we can leave it at that.
Tom
___
Freedos-devel mailing list
Hey!
> As a matter of curiosity, given that we were unable to find a
> precise answer to why Microsoft dropped IFS after MS-DOS 5.0
to start with, your question is pretty much nonsense. IFS or the
"networking redirector" was definitively there in MSDOS 6.2 and most
likely in 7 (aka Win95).
it
Hallo Herr Bernd Boeckmann via Freedos-devel,
am Montag, 27. Februar 2023 um 13:07 schrieben Sie:
>> Am 27.02.2023 um 07:26 schrieb Deposite Pirate :
>>
>> I'm not sure if this fdisk can already do that, but additionally it
>> would also be very useful if it could align partitions to 4k rather
Hallo Herr Ralf Quint,
am Dienstag, 21. Februar 2023 um 01:17 schrieben Sie:
>
> Don't recall when MSCDEX first showed up, but I think it was
> after the networking redirector stuff (for both Novell and LanManager)
> in MS-DOS 3.0.
early version of Novell hooked a couple of
Hallo Herr Ralf Quint,
am Montag, 20. Februar 2023 um 18:18 schrieben Sie:
> On 2/19/2023 5:38 PM, Aitor Santamaría wrote:
>> Hello,
>>
>> Does anyone know if the IFS (Installable File System) API is
>> documented anywhere?
> There is no such thing for DOS. For DOS, things like this, for
> And to be clear: I don't plan to delete these from the FreeDOS Files
> Archive at Ibiblio. My proposal is just to not include them in the
> next FreeDOS distribution.
+1
> If people want to keep using, say, SEAL -
> they can download it and install it themselves.
as of many other packages.
> The main difference between using VBADOS and EtherDFS would come
> down to the DOS machine. If running DOS inside VirtualBox, VBADOS
> would most likely be the easiest to setup and use. However, using
> EtherDFS works under other Virtual Machines and with real hardware.
EtherDFS should work
https://forums.virtualbox.org/viewtopic.php?f=4=105823
I haven't tested this, but there seems to exist "VBSF.EXE -- a client
for Shared Folders. This allows shared folders to be mounted as drives
inside MS-DOS (and Windows 3.x) directly, without any network stack."
which is more or less
>>> whatever EMM386 and friends was and is, it is definitively not what
>>> people think when they hear 'DOS VM'. you are abusing words to make a
>>> point. not good.
>> I don't really care. I am talking about how existing DOS 386 memory
>> managers have worked for 35+ years now.
>> The 80386
> I know. I am a professional in this field and have been since 1988.
> Please do me the courtesy of imagining that I know what I am talking
> about.
according to https://cz.linkedin.com/in/liamproven
FOSS and cloud reporter · Freelance writer and English teacher · Technical
writer/editor ·
>> 3. Develop embedded systems.
> Not sure that's important in 2023. Any citations?
http://wiki.freedos.org/wiki/index.php/Main_Page
>> whatever EMM386 and friends was and is, it is definitively not what
>> people think when they hear 'DOS VM'. you are abusing words to make a
>> point. not
Hallo Herr Ben Collver,
am Freitag, 27. Januar 2023 um 18:23 schrieben Sie:
> On Fri, 27 Jan 2023 at 16:42, tom ehlert wrote:
>> any reason you don't download VirtualBox for your platform, select
>>
>> proper devices (there is even a Soundblaster16 e
Hi,
most people around here already have a working machine, most likely
Windows or Linux.
any reason you don't download VirtualBox for your platform, select
proper devices (there is even a Soundblaster16 emulated), install DOS
on it and go.
VirtualBox isn't perfect, but probably much better
Hallo Herr Liam Proven,
> I suppose my first suggestion would be: sod Windows.
> A suggestion of a justification:
> If people want a FOSS DOS then they must use a FOSS GUI, and if they
> want a proprietary GUI then they must accept that also means a
> proprietary DOS underneath.
this argument
> --
> Diese Nachricht wurde von meinem Android Mobiltelefon mit mail.comMail
> gesendet.
> Am 22.01.23, 17:56 schrieb tom ehlert :Hi,
>> the proposal was from me. Maybe some of you know that I work on the text for
>> a new help version.
>> To do so, I use diff
Hi,
> the proposal was from me. Maybe some of you know that I work on the text for
> a new help version.
> To do so, I use different sources, depending on what I can get.
> Sometimes documentation is very good, sometimes there is none,
> sometimes even command/? gives no information and I have
Hallo Herr Knedlik,
am Sonntag, 15. Januar 2023 um 15:17 schrieben Sie:
> Okay, I’m still even a few days after very confused. I came into
> DOS with my only programming knowledge being on modern 64-bit
> systems and I didn’t even go lower-level than C++.
> I have no idea where to start - I
> Okay, I’m still even a few days after very confused. I came into
> DOS with my only programming knowledge being on modern 64-bit
> systems and I didn’t even go lower-level than C++.
> I have no idea where to start - I would love to learn how to do all
> the cool stuff like graphics and then
__
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
Mit freundlichen Grüßen / with kind regards
Tom Ehlert
+49-15151898538
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
> I’m currently trying to make a function in a separate assembly
> file, but I’m having problems linking it with a C program.
it always helps to take the time to describe the problem you are
facing, like
what compiler, assembler, linker
WHAT KIND OF PROBLEMS
Tom
> You really don't want a 160 kb editor on a floppy (unless you copy it
> to a RAM disk).
copying it to a RAM disk will require 1 or 2 seconds every time you
boot this floppy.
starting this from floppy requires 1 or 2 seconds every time you use
the editor - usually less often then you use to
> In general, I find that toggling options are a bad idea. Things
> just get too confusing, especially if you have multiple "sources"
> for the options (like combinations of internal/compile-time default
> settings, environment variables, options entered through a batch
> file, options entered
Hallo Herr Jerome Shidel,
am Mittwoch, 9. November 2022 um 16:26 schrieben Sie:
> Not all options perform toggling. For example:
> dir /p - pauses per page
> dir /p /p - pauses per page
> I don’t think the toggling is very important. But, it does deviant from
> MS-DOS.
> I
to make myself a better mailing list citizen, I created a new topic
for this different issue ;)
I have INITDISK.C that will detect and
mount GPT partitions if available.
FAT partitions on GPT disks are fully 'normal' drives.
to be discussed, and I have no strong opinion here:
shall FreeDOS
Hi all,
it seems this case is not as dramatic as it seemed first (to me).
to repeat my earlier steps, I downloaded and installed
kernel-master.zip and country.zip; edited config.bat to
COMPILER=OWWIN, compiled and the resulting kernel.sys booted as it
should.
BUT: when I edited config.c, and
> Does it make a difference on your computer if the kernel is
> compiled for 386+ vs 86+ ? Was this on real computer or virtual?
it was a VirtualBox machine.
I only changed in build.bat from build.b the compiler setting, using
OCWIN, so it probably was 8086
of course I have a very specific
> correcting for this, the the boooting kernel goes as far as
> I'm looking into this, seems to be some sort of memory corruption.
> On my test VirtualBox vm it works fine, on my laptop I get a halt
> but much later than you, where FreeCom is loading. The gcc compiled
> kernel works in all my
> One of the main things that started me down this rabbit trail was
> the need to know which Ethernet card is being virtualized in a
> particular VM so I can load the correct packet driver.
> I have a
> single ETHERNET.BAT file I run to install the packet driver, and
> since detecting which
> One of the main things that started me down this rabbit trail was
> the need to know which Ethernet card is being virtualized in a
> particular VM so I can load the correct packet driver.
ca. 30 years ago PCI enumerating has been invented.
> I have a
> single ETHERNET.BAT file I run to
Sorry,
I posted this under the wrong topic.
so:
when downloading https://github.com/FDOS/kernel via
[code] downnload ZIP
the downloaded kernel-master\country directory is empty, and the
project does not build.
correcting for this, the the boooting kernel goes as far as
FreeDOS boot FAT
1 - 100 of 546 matches
Mail list logo
