[Freedos-devel] FreeDOS virtual get-together on Sunday!

2023-04-12 Thread Jim Hall
I wanted to remind everyone that our next FreeDOS virtual get-together is coming up soon - Sunday, April 16 at 11am US/Central. Use your favorite timezone converter to find your local time. As always, we'll do the meeting via Bluejeans. I'll share the meeting URL here shortly before the meeting.

Re: [Freedos-devel] Slowdown-Units ratings and a CPU-bound depacker be nchmark

2023-04-12 Thread Bret Johnson
> However, the topic of port I/O and MMIO reminds me of some activity > by RayeR and others regarding low-level configuration to speed up > access to PCI / PCIe graphics in DOS. I think the issue was that no > fast defaults were applied by the BIOS, slowing down VESA LFB a lot. Video is kind of a

Re: [Freedos-devel] FreePascal bug [off-list]

2023-04-12 Thread Ralf Quint
On 4/12/2023 5:08 PM, Jim Hall wrote: A user emailed me (late last year) with a bug/issue report on FreePascal in FreeDOS 1.3. I was going to (finally) reply to say they really should ask the FreePascal people about this, but I realized I couldn't really make out what they were saying. This is

[Freedos-devel] FreePascal bug [off-list]

2023-04-12 Thread Jim Hall
A user emailed me (late last year) with a bug/issue report on FreePascal in FreeDOS 1.3. I was going to (finally) reply to say they really should ask the FreePascal people about this, but I realized I couldn't really make out what they were saying. This is the part of their email that relates to

Re: [Freedos-devel] Slowdown-Units ratings and a CPU-bound depacker benchmark

2023-04-12 Thread Eric Auer
Hi :-) To make this long thread a bit longer, I think that using port I/O in delay loops used to slow down too fast games by wasting time actually is a good idea (if you pick a safe port) BECAUSE the I/O is slow and not cached and not subject to too smart CPUs trying to optimize it away in

Re: [Freedos-devel] I wish I had a boot.log file

2023-04-12 Thread jerome
Hi All, Fixed a minor issue in Logger, that would cause the interface program to not find the device driver when it was loaded low. At present, the interface program just does a brute force memory scan to find the driver. There are safeguards in place to prevent false positives and some