Re: [Freedos-user] Coding in BASIC for Freedos?

[Mercury Thirteen via Freedos-user]

Well said. :)




Sent with Proton Mail secure email.

On Sunday, March 17th, 2024 at 8:57 PM, Ben Collver via Freedos-user 
 wrote:

> > Date: Sun, 17 Mar 2024 19:26:05 +0100
> > From: tom ehlert t...@drivesnapshot.de
> > To: "Discussion and general questions about FreeDOS."
> > freedos-user@lists.sourceforge.net
> > Subject: Re: [Freedos-user] Coding in BASIC for Freedos?
> > 
> > > On Sun, Mar 17, 2024 at 6:26 AM Liam Proven via Freedos-user
> > > freedos-user@lists.sourceforge.net wrote:
> > > [..]
> > > 
> > > > There are good reasons that DOS went away some 35 years ago. It has
> > > > its uses but not being able to flip to another window or another
> > > > screen to consult documentation, or try something out, or look it up
> > > > online, is a massive handicap.
> > 
> > +1
> 
> 
> This is an example of limited imagination. In this day and age it is
> common for people to use their phone to take a photo of an error message
> for troubleshooting. The idea that someone is stuck on a single
> dedicated computer in a vacuum without any other technology available
> is very retro indeed. It can be both, or something in between, or just
> for fun.
> 
> Even when DOS was still commercially produced, professional developers
> often preferred to do their development on another operating system.
> Many classic DOS games were developed using more powerful systems.
> This includes originals like Zork. They used DOS as their runtime.
> 
> But before they became professional developers, while they were still
> learning, they probably used all kinds of gross technologies, and
> wrote shoddy code, and probably had fun along the way.
> 
> > Nope. AFAICT it's a person wanting to learn programming; no mentioning of
> > FreeDOS.
> 
> 
> If it isn't FreeDOS related, then is it off-topic on this mailing list?
> 
> There's a lot of snobbery in the programming world. A famous expert
> declared that students who learned to program on BASIC were ruined
> forever. It's all too easy to debate a dead person, but i would
> respond "Whew! Now the pressure is off." Since i am ruined forever
> as a programmer, now i get to have fun. I don't have to take myself
> too seriously.
> 
> > I fail to see the advantage.
> 
> 
> Your failure of imagination is not helping this person.
> 
> If i were wanting to tinker with BASIC on DOS, I'd probably start
> with QBASIC.EXE because there has been so much written about it.
> Once i got the hang of that, then i'd graduate to something free.
> 
> Here are some links. I hope they help.
> 
> BASIC Techniques And Utilities Book:
> http://ethanwiner.com/fullmoon.html
> 
> 
> Programmed Lessons in QBasic
> https://chortle.ccsu.edu/QBasic/index.html
> 
> 
> QB Express Magazine & Tutorials
> http://www.petesqbsite.com/sections/express/express.shtml
> 
> 
> QBasic 1.1 Web-based, runs in a web browser
> https://archive.org/details/msdos_qbasic_megapack
> 
> 
> QBasic 1.1 Download
>  http://download.microsoft.com/download/
> win95upg/tool_s/1.0/W95/EN-US/olddos.exe>
> 
> 
> -Ben
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Coding in BASIC for Freedos?

[Mercury Thirteen via Freedos-user]

It does work indeed. :)

Sent with [Proton Mail](https://proton.me/) secure email.

On Saturday, March 16th, 2024 at 11:28 PM, Jeremy Leonard via Freedos-user 
 wrote:

> Back in my DOS days I used QuickBasic.
>
> https://winworldpc.com/product/quickbasic/45
>
> I liked the function style, no line numbers, compile to exe. I haven't tried 
> it on FreeDOS but I can't imagine it wouldn't work.
>
> On Fri, Mar 15, 2024 at 12:47 PM Thomas Cornelius Desi via Freedos-user 
>  wrote:
>
>> Hello,
>>
>> could someone from the list give me an advice, what programming language to 
>> learn,
>> if I would want to do some programming in FREEDOS?
>>
>> I am an absolute »Noobie« with programming, but stumbling about some source 
>> files,
>> especially BASIC, which I would work with.
>>
>> My aim is to do some alterations to existing source (sort-of-text editor).
>>
>> What would your advice be?
>>
>> Many thanks, best regards,
>> Thomas
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> --
>
> Jeremy Leonard
> jere...@elite4god.com
> Cell: (517) 285-8309___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] AUTO SHIFT keyboard on DOS??

[Mercury Thirteen via Freedos-user]

Regarding programmatic control of the keyboard LEDs, that was definitely 
possible. I have some od BASIC code I wrote in my early days which 
twiddle some bits in the byte at 0:0417 to accomplish it.




Sent with Proton Mail secure email.

On Thursday, February 8th, 2024 at 11:00 PM, Jerome Shidel via Freedos-user 
 wrote:

> Hi,
> 
> > To fake shifts, one can just modify the flags at 40:17 and 18.
> > It will not update the keyboard LEDs, but that is acceptable.
> > The BIOS itself uses 40:96 and 97 to track its own status.
> 
> 
> It has been a very long time. But, if I recall correctly, I’m fairly sure you 
> can programmatically change the LEDs as well. But, I don’t recall the 
> details. But, I might have code sitting around somewhere that has that 
> functionality.
> 
> However excluding CAPS LOCK LED, I don’t think I’ve had a keyboard with the 
> other LEDs for a very long time. No real way for me to test that at present.
> 
> > Of course the details can get a bit more complicated, as
> > you also have press and release events for shift keys etc.
> > and special E0 ... key combinations and so on. But if you
> > are happy with just the most mainstream keys acting in that
> > "long press means shift" style and only while no actual
> > ctrl, shift, alt or similar modifier keys are pressed, it
> > should be quite feasible to implement this.
> 
> 
> 
> Special and multiple key combinations was something I built into the keyboard 
> driver in the “Danger Engine.” That is the game and application framework I 
> made for some programs provided with FreeDOS.
> 
> The keyboard driver it has can track things like Left-Control+Right-Alt+A+P 
> or Up+Left+Tab. No real limit on total simultaneous keys in the driver. Plus, 
> it recognizes keys not normally supported under DOS. For instance, the Volume 
> keys and Browser buttons on my ancient Logitech Media Keyboard.
> 
> But, that driver is not very efficient. Being a prototype experiment, it is 
> cobbled together. Now that the issues involved were worked out, it needs to 
> be rewritten from scratch.
> 
> Even though the Danger Engine does some neat stuff, the same goes for the 
> entire thing. It definitely needs a rewrite.
> 
> :-)
> 
> Jerome
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Using HDMI monitor and USB keyboard/mouse on FreeDOS

[Mercury Thirteen via Freedos-user]

I do! Hopefully this isn't too off-topic for here, but as I'm not trying to get 
anyone to buy anything, and all the features of the keyboard are designed to 
work with zero software installed anyway - making it a great fit for DOS 
systems - I think (hope) it will be okay.

My blog has a series of posts spanning the past year or so of development work 
on it:
https://www.mercurycoding.com/blog.html?tag=Weapon%20Keyboard

Sent with [Proton Mail](https://proton.me/) secure email.

On Friday, February 2nd, 2024 at 5:16 AM, Thomas Cornelius Desi via 
Freedos-user  wrote:

> Hi Mercury Thirteen,
>
> do you have some more info on your build?
> I am interested in something like that, which would integrate a small 
> trackpad into the kbd.
>
> Thomas
>
>> On 01.02.2024, at 22:04, Mercury Thirteen via Freedos-user 
>>  wrote:
>>
>> Not strictly on-FreeDOS-topic, but speaking of devices which translate USB 
>> to PS/2, a recent project of mine has been designing a keyboard which, among 
>> many other features, can itself connect to a PS/2 port and also accept a USB 
>> device for input (e.g. a mouse, for example) whose data then gets forwarded 
>> to the PS/2 port as well. I originally added this feature to allow one to 
>> record both keyboard and mouse input and save it to a macro, but it could be 
>> used as a USB-to-PS/2 converter of sorts as well. The first prototype is 
>> functional (in fact, I'm typing this message on in now) and Revision B is 
>> waiting to be soldered up for further refinement. :)
>>
>> Sent with [Proton Mail](https://proton.me/) secure email.
>>
>> On Wednesday, January 31st, 2024 at 2:41 PM, Louis Santillan via 
>> Freedos-user  wrote:
>>
>>> You inspired me to build one myself. I’m awaiting a few parts now.
>>>
>>> On Tue, Jan 30, 2024 at 12:15 PM Bill Gee via Freedos-user 
>>>  wrote:
>>>
>>>> An update for the group -
>>>>
>>>> Today I built an adapter that translates USB keyboard and mouse to PS/2
>>>> signals.
>>>>
>>>> https://docs.pikvm.org/pico_hid_bridge/
>>>>
>>>> It works great! I can get into BIOS setup with it. CTL-ALT-DEL works.
>>>> I cannot see any problems with response time. Wolfenstein runs just fine.
>>>>
>>>> I had to buy one PS2 cable and the logic level converter. I already had
>>>> a Pico, one PS/2 cable and the micro-USB to USB-A adapter.
>>>>
>>>> Next to try is a different display adapter.
>>>>
>>>> ===
>>>> Bill Gee
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Using HDMI monitor and USB keyboard/mouse on FreeDOS

[Mercury Thirteen via Freedos-user]

Not strictly on-FreeDOS-topic, but speaking of devices which translate USB to 
PS/2, a recent project of mine has been designing a keyboard which, among many 
other features, can itself connect to a PS/2 port and also accept a USB device 
for input (e.g. a mouse, for example) whose data then gets forwarded to the 
PS/2 port as well. I originally added this feature to allow one to record both 
keyboard and mouse input and save it to a macro, but it could be used as a 
USB-to-PS/2 converter of sorts as well. The first prototype is functional (in 
fact, I'm typing this message on in now) and Revision B is waiting to be 
soldered up for further refinement. :)

Sent with [Proton Mail](https://proton.me/) secure email.

On Wednesday, January 31st, 2024 at 2:41 PM, Louis Santillan via Freedos-user 
 wrote:

> You inspired me to build one myself. I’m awaiting a few parts now.
>
> On Tue, Jan 30, 2024 at 12:15 PM Bill Gee via Freedos-user 
>  wrote:
>
>> An update for the group -
>>
>> Today I built an adapter that translates USB keyboard and mouse to PS/2
>> signals.
>>
>> https://docs.pikvm.org/pico_hid_bridge/
>>
>> It works great! I can get into BIOS setup with it. CTL-ALT-DEL works.
>> I cannot see any problems with response time. Wolfenstein runs just fine.
>>
>> I had to buy one PS2 cable and the logic level converter. I already had
>> a Pico, one PS/2 cable and the micro-USB to USB-A adapter.
>>
>> Next to try is a different display adapter.
>>
>> ===
>> Bill Gee___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] NVMe not found

[Mercury Thirteen via Freedos-user]

There's most likely a setting in your BIOS which will enable the computer to 
present this newfangled drive to your OS as a traditional IDE drive.




Sent with Proton Mail secure email.

On Sunday, November 12th, 2023 at 10:44 PM, Jody Spurrell via Freedos-user 
 wrote:


> I have a HP EliteDesk 800 G3 Mini with NVMe drive thats not detected,
> how to fix ?
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] HIMEMX zip file dates

[Mercury Thirteen via Freedos-user]

I typically do modify the times to reflect the version number. Of course that's 
not necessary by any means, but it's a habit I started doing as a quick and 
easy contingency to help me in the event of files becoming crossed, e.g. if I 
were to accidentally drop files into the wrong version folder or some such 
errantry.

Is the preferred behavior to not touch the times? If so, I can certainly 
refrain from doing so in future packages. :)




Sent with Proton Mail secure email.

--- Original Message ---
On Sunday, October 1st, 2023 at 7:04 PM, Jim Hall via Freedos-user 
 wrote:


> Eric wrote:
> 
> > You can also find updates for JEMM and HIMEMX on Japheth's GitHub "Baron 
> > von Riedesel", even his HIMEMSX to use more than 4 GB RAM :-)
> 
> 
> Mercury Thirteen wrote:
> [..]
> 
> > Looks like I fell behind on keeping up with all of Japheth's updates! The 
> > downloads section at MercuryCoding.com has been updated with new versions 
> > of HiMemX and JWasm as well. Thanks, Eric, for (indirectly) pointing this 
> > out to me! :)
> 
> 
> I didn't have the latest HIMEMX mirrored on Ibiblio, so I just grabbed
> the copies you have. I checked the file contents, and they have been
> touched since the original. For example, 3.38
> (https://github.com/Baron-von-Riedesel/HimemX/releases) was released
> Nov 21, 2022 and has file contents like this:
> 
> $ unzip -l HimemX338.zip
> Archive: HimemX338.zip
> Length Date Time Name
> - -- - 
> 6056 11-21-2022 13:01 HimemX.exe
> 6056 11-21-2022 13:01 HimemX2.exe
> 1954 04-16-2020 06:38 Readme.txt
> 4871 11-21-2022 13:01 History.txt
> 81855 11-21-2022 13:01 HimemX.asm
> 296 03-24-2020 01:56 Make.bat
> 529 03-24-2020 01:58 Makefile
> - ---
> 101617 7 files
> 
> 
> It looks like you modify the zip files when you mirror them. Your
> version looks like this:
> 
> $ unzip -l 3.38/himemx338.zip
> Archive: 3.38/himemx338.zip
> Length Date Time Name
> - -- - 
> 0 09-23-2023 03:38 APPINFO/
> 568 09-23-2023 03:38 APPINFO/HIMEMX.LSM
> 0 09-23-2023 03:38 BIN/
> 6056 09-23-2023 03:38 BIN/HIMEMX.EXE
> 2168 09-23-2023 03:38 BIN/UMBM.EXE
> 6056 09-23-2023 03:38 BIN/HIMEMX2.EXE
> 0 09-23-2023 03:38 DOC/
> 0 09-23-2023 03:38 DOC/HIMEMX/
> 1954 09-23-2023 03:38 DOC/HIMEMX/README.TXT
> 4871 09-23-2023 03:38 DOC/HIMEMX/HISTORY.TXT
> 0 09-23-2023 03:38 SOURCE/
> 0 09-23-2023 03:38 SOURCE/UMBM/
> 296 09-23-2023 03:38 SOURCE/UMBM/MAKE.BAT
> 12147 09-23-2023 03:38 SOURCE/UMBM/UMBM.ASM
> 0 09-23-2023 03:38 SOURCE/HIMEMX/
> 296 09-23-2023 03:38 SOURCE/HIMEMX/MAKE.BAT
> 81855 09-23-2023 03:38 SOURCE/HIMEMX/HIMEMX.ASM
> 529 09-23-2023 03:38 SOURCE/HIMEMX/MAKEFILE
> - ---
> 116796 18 files
> 
> 
> (You sent your message on 9/23, so that explains the dates.)
> 
> Are you folding the source code into the "exe" zip file to create a package?
> 
> 
> At least for the mirrored files on Ibiblio, I prefer to keep the files
> as provided by the developer (Jerome creates packages, but the Files
> Archive section is a straight mirror.) So I'll re-mirror the original
> releases from GitHub.
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] CD driver

[Mercury Thirteen via Freedos-user]

--- Original Message ---
On Tuesday, September 19th, 2023 at 3:37 PM, Eric Auer via Freedos-user 
freedos-user@lists.sourceforge.net wrote:

> ...
>
> You can also find updates for JEMM and HIMEMX on Japheth's GitHub "Baron von 
> Riedesel", even his HIMEMSX to use more than 4 GB RAM :-)
>
> ...

Looks like I fell behind on keeping up with all of Japheth's updates! The 
downloads section at MercuryCoding.com has been updated with new versions of 
HiMemX and JWasm as well. Thanks, Eric, for (indirectly) pointing this out to 
me! :)

>___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Can you recommend a good single-board-computer for legacy OSs?

[Mercury Thirteen via Freedos-user]

I wonder if it the products listed here would be a good resource to have 
somewhere on the FreeDOS wiki as a reference for others.

Thoughts, Jim, everyone?

Sent with [Proton Mail](https://proton.me/) secure email.

--- Original Message ---
On Friday, March 10th, 2023 at 2:28 PM, Lukas Satin  
wrote:

> Hello from Czechia, I run makerspace in the past and have 86Duino EduCake, a 
> smart breadboard including Vortex86. It can run DOS and Windows. Only 
> disadvantage is a lack of VGA output, so it can do only SSH.
>
> I second that Vortex86 choice.
>
> By the way Win XP and Win 7 won’t boot non ACPI bios, right? Or they wont 
> boot multicpu non ACPI bios. This issue happens with 6x Pentium Pro server 
> Unisys Aquanta or ALR Revolution 6x6. There is article to overcome this using 
> Whistler build that did not have ACPI hardcodes yet and apply XP SP3 on top 
> of it.
>
> Lukas RetroGamer (sberatele historickych pocitacu FB)
>
> On Fri 10. 3. 2023 at 15:32, Frantisek Rysanek  
> wrote:
>
>> On 10 Mar 2023 at 11:13, Mart Zirnask wrote:
>>
>>> Just for reference, I'll share some of my bookmarks.
>>> I'm just a shy hobbyist, not an engineer whatsoever, but I've been
>>> interested in fanless, small form factor DOS computing solutions for
>>> quite a while.
>>>
>> We are a similar blood type. Only I happen to have been working in
>> this toystore for 20 years :-)
>>
>>> EBOX-3100: Vortex86 400MHz, 1GB RAM, VGA, SeaBIOS, enclosure -- this
>>> one seems like the most "complete" solution:
>>> https://www.compactpc.com.tw/products/item/21
>>>
>> FYI, compactpc.com.tw is another sibling company of the DMP holding.
>> Therefore, similar to ICOP, "they also have their own CPU" = the
>> Vortex86.
>> AFAICT, CompactPC are more on the consumer/office side of the
>> business - in terms of temperature range, form factor and the general
>> feature set.
>>
>> The particular EBOX model that you've pointed to seems a bit of an
>> oddball to me. The Vortex86EX is junior to the Vortex86DX that I've
>> mentioned before. IIRC, the Vortex86EX is originally an "embedded"
>> CPU = intended for vehicle onboard computing, machine control and
>> whatnot. It shows in several respects:
>> - a relatively lower CPU clock
>> - some special peripherals: ADC, multichannel motor controller .
>> - an integrated 80C51 MCU core for general use
>>
>> https://www.vortex86.com/datas/upload/site/2019042310373055.jpg
>> https://www.vortex86.com/products/Vortex86EX
>>
>> Similarly to the DX, the EX does not have a VGA subsystem on chip
>> either - but, in contrast to the DX, the EX does not have a parallel
>> PCI - instead, it has a single external lane of PCI-e.
>> Therefore, this particular computer has a dedicated VGA chip - on
>> PCI-e, rather than the neat old Z9s on the PCI.
>> This dedicated VGA on PCI-e is possibly something "own" by DMP,
>> possibly related to the on-chip integrated VGA of the
>> Vortex86DX2/DX3. In the computer that you're referring to, its
>> nominal maximum resolution is 1024x768. Which doesn't seem like very
>> much.
>>
>> The SeaBIOS looks cool! This is the first piece of hardware that I
>> see from the DMP corp that has anything else than AMI.
>>
>> I can see that eBox PC's with Vortex86DX no longer exist.
>> No more XGI Z9s for the consumer segment. Interestingly, that chip
>> could only produce 1280x1024 maximum on the ICOP boards, despite 32
>> MB dedicated RAM.
>> But, eBox PC's with the Vortex86MX are still listed.
>> This one has on-chip integrated VGA, with a maximum resolution of
>> 1920x1200.
>> And, there's a DX3-based version that can do 1920x1080 (on-chip
>> integrated VGA).
>> Note that these VGA subsystems can only do basic 2D acceleration
>> (blitting and such), no 3D, no video playback accel.
>>
>>> Various DOS SBCs by JK Microsystems: 
>>> http://www.jkmicro.com/Products.html#dos
>>>
>> Interesting... I didn't know about this brand.
>> They have some pretty old legacy stuff, starting from a 386...
>>
>>> Various Vortex86 SBCs: 
>>> https://www.emacinc.com/products/pc_compatible_sbcs/486
>>>
>> The SBC models mentioned at that link are made by ICOP.
>>
>>> Categorized as "legacy" on the home page:
>>> SAT-DX4 - 133 MHz SBC with video and ethernet:
>>> https://www.winsystems.com/product/sat-dx4/
>>>
>> I didn't know this one either.
>> The particular board model looks like an ultra-classic (legacy)
>> 486DX4, but it smells to me of the pioneer days: a non-standard form
>> factor, two sockets for the DiskOnChip...
>> Doesn't appeal to me very much.
>> (I still remember the relief and exhileration, when the CompactFlash
>> arrived and the DiskOnChip landed in the scrap bin.)
>>
>> Frank
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net

Re: [Freedos-user] People often do not want responsibility and answer: It is unsupported

[Mercury Thirteen via Freedos-user]

I love your outside the boxthinking on this. Best of luck!

Sent with [Proton Mail](https://proton.me/) secure email.

--- Original Message ---
On Sunday, September 11th, 2022 at 6:11 AM, Lukas Satin  
wrote:

> Hi,
>
> Recently I started to maintain several opensource projects. And this subject 
> touches FreeDOS as well, so I'm asking what would be your argumentation for 
> that.
>
> I remember opensource 20 years ago, it was great and as a student I had time 
> to support or even develop my own projects. Companies did not release 
> opensource yet.
>
> Today companies = business only = profit. They learn to use opensource 
> because it is cheaper for them. Otherwise they would not use it. I think 
> their main reason is give a little bit of code, so someone can test it and 
> fix it for them, for free. That's it.
>
> Today's opensource developers, for example on Github, do it in their free 
> time and they need also paid job. Their paid job is in a company, like 
> something above, so they are heavily influenced by bad habits.
>
> This recently came to my attention when browsing several Github projects and 
> their history. So lets say you have opensource project for 10-15 years and it 
> provides some value, it provides a very broad operating systems support!
>
> Now the repository gets forked, because original mantainer does not have 
> time, or in some cases, it is even original mantainer, who breaks it.
>
> What is happening right now: They delete files, they delete project 
> configuration, they rewrite files.
>
> What they think they do: They think they are the best and they upgrade their 
> project for latest OS (Windows 10, soon 11 or 12 as well as Linux)
>
> What they really do: Lack knowledge of design patterns, lack knowledge of 
> using even development and git tools properly, lack understanding that 10 
> years old project provides bigger value than their latest Win10 only breaking 
> change.
>
> How would you argue with person like that? How would you try to explain to 
> them that there is a better way?
>
> You see it everyday from Microsoft. They remove downloads (Windows 8.1 WDK / 
> SDK is temporarily offline). Everytime you even ask a simple thing about 
> Windows XP on DOS on ANY gaming forum, the first dumb user automatically 
> replies: "It is not supported. Get away." - without even thinking as a human, 
> without even thinking anything - it is automatic response pre-programmed by 
> corporation marketing - they get it somewhere else, not from their head.
>
> Then, I look at the project, look at the code. And often it is very simple to 
> keep old OS support. You just change a few parameters or recompile some 
> library (as it was for the last 10 years anyway).
>
> Do you, as a FreeDOS have some opensource developer best practice guidelines? 
> How do you look at this issue?
>
> There will be always corporation pressure to upgrade to the latest, support 
> consumerism and increase ROI for stakeholders.
>
> But for opensource, developer needs to have a better mindset. Especially they 
> start maintain 10-15 years old projects - they have bigger responsibility 
> than just cut x86 architecture.
>
> I'm not saying they need to support and test old OS actively. But they should 
> not rewrite project source history like spaghetti. The least they could do is:
> 1) create new project file (prj) for new OS (my_project_w10.prj) and keeping 
> the original my_project.prj intact
> 2) create SDL1 branch and archive it (which can be used in FreeDOS), so 
> community can sometime backport some changes there. Instead they rewrite the 
> files, delete the files and you get mess
> 3) use more clever architecture or design pattern, like Adapter, to provide a 
> specific implementation for specific OS. Lets say they have OS X now and they 
> migrate to OS Y. Instead of rewriting half of git project, they would 
> encapsulate OS Y specific calls in a separate file and this file will be used 
> instead of original file for OS X based on project compilation settings or 
> based on runtime configuration
>
> What I currently fight with:
> 1) intolerant aggressive people, who should be smart (as a developers mostly 
> are)
> 2) automatic response: this is unsupported, this is deprecated => this is 
> like parrot, they have pre-programmed automatic response from aggressive 
> corporation marketing strategies
> 3) lack of understanding that 10-15 years old project is not only about his 
> personal needs, but it is about community of people, who use it for 10-15 
> years
> 4) lack of knowledge, no will or time to gain new knowledge => this results 
> in 1)
> 5) lack of education what is opensource, what is preserving history for long 
> time span projects and what is commercial oriented development
>
> So I forked several projects like that. Will fix them and record some Youtube 
> video. I think I will also record some Youtube video about the content of 
> this e-mail and provide some real life 

Re: [Freedos-user] Retire from sending monthly reminder message

[Mercury Thirteen via Freedos-user]

I vote no. Having a one-time email sent by default when folks join seems a good 
idea, but a monthly reminder? Overkill in my opinion.




Sent with Proton Mail secure email.

--- Original Message ---
On Monday, August 22nd, 2022 at 4:40 PM, Jim Hall  wrote:


> I'm actually wondering if we need the automatic monthly list reminders
> anymore. I was thinking about it today, and John started doing this
> for us when the FreeDOS email lists were on a different email service
> (the old fd-dev list, I think) and our web hosting was very different
> (HTML documents only, no automation). So John's automated reminders
> were an excellent solution, and I'm really glad he did that for us.
> 
> However, things are different now. For one, we have fewer people
> joining the list, so the same people are seeing the same list
> reminder, month after month. Maybe a monthly reminder is too frequent.
> But I think we're pretty unique these days in having a monthly
> reminder; I don't think other email lists or forums or discussion
> boards for other open source projects have a monthly reminder.
> 
> Also, our current FreeDOS email lists are hosted on Sourceforge now,
> and the Sourceforge list service lets the list administrator add a
> custom "welcome" message to anyone who joins the email list. I can
> copy the text of our list rules into that welcome message, so that
> anyone who joins the email lists will get a copy of the list rules.
> That seems a good thing to do, regardless.
> 
> I can also add the full text of the list rules to our "Forums" page on
> the website. We currently link to the list rules, but the rules can be
> made more obvious by including the full text right next to where you'd
> subscribe to the list. That seems an obvious place to put it. (I'm
> working on the website redesign anyway - albeit slowly - and I can
> make this part of the update.)
> 
> With these changes, do we need a monthly list reminder anymore?
> 
> 
> Jim
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] clipboard support utilities

[Mercury Thirteen via Freedos-user]

Thanks for this contribution!

And, for those of us not running any kind of Gopher client, I presume the link 
https://gemini.spam.works/x/tilde.pink/~bencollver/files/dos/util/clip/ will 
also work, yes?




Sent with Proton Mail secure email.

--- Original Message ---
On Sunday, July 3rd, 2022 at 5:36 PM, Ben Collver  
wrote:


> Hi,
>
> Back in 2019 i tinkered with a few real-mode clipboard utilities and i am 
> sharing them here in case someone might find them useful.
>
> gopher://tilde.pink/1/~bencollver/files/dos/util/clip/
>
> * winoldap.com is a TSR that provides the WinOldAp API for a system-wide 
> clipboard on FreeDOS. It is limited to 64K of data. It is based on code from 
> dosclip.arj and it has been modified to be assembled using nasm instead of 
> A86.
>
> Run: winoldap.com
>
> * mouseclip.exe is a TSR that provides a mouse-driven copy/paste feature on 
> the FreeDOS console. It has been modified to always use the WinOldAp 
> clipboard. It has also been modified to increase the maximum buffer size to 
> 32K.
>
> Run: mousclip.exe /B32767
>
> * clip.com reads up to 64K from stdin and copies it into the WinOldApp 
> clipboard.
>
> Run: clip.com 
> * paste.com reads up to 64K from the WinOldAp clipboard and copies it to 
> stdout.
>
> Run: paste.com >file.txt
>
>
> -Ben
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOS ASM Resources

[Mercury Thirteen via Freedos-user]

That's a great suggestion! Way back in the day, before I had internet, my local 
library was an excellent resource to begin learning. :)

Sent with [Proton Mail](https://proton.me/) secure email.

--- Original Message ---
On Saturday, July 2nd, 2022 at 7:01 PM, Daniel  wrote:

> If ya have a library, ya can try lookin there. Usin our library here I found 
> some good books to go through. Advanced MSDOS Programming, From BASIC to 
> 8086/8088 Assembly Language. There are other books I am waitin on. I also 
> have other books I collected over the years. I hope this is a good suggestion.
>
> On Sat, Jul 2, 2022 at 14:02  
> wrote:
>
>> Send Freedos-user mailing list submissions to
>> freedos-user@lists.sourceforge.net
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> or, via email, send a message with subject or body 'help' to
>> freedos-user-requ...@lists.sourceforge.net
>>
>> You can reach the person managing the list at
>> freedos-user-ow...@lists.sourceforge.net
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Freedos-user digest..."
>>
>> Today's Topics:
>>
>> 1. Re: DOS ASM resources (Ben Collver)
>> 2. Re: DOS ASM resources (Travis Siegel)
>> 3. Re: DOS ASM resources (Santiago Almenara)
>>
>> --
>>
>> Message: 1
>> Date: Sat, 2 Jul 2022 13:12:03 +
>> From: Ben Collver 
>> To: "freedos-user@lists.sourceforge.net"
>> 
>> Subject: Re: [Freedos-user] DOS ASM resources
>> Message-ID:
>> 
>>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> I made a mistake pasting a URL into my last post.
>>
>> OLD: http://ref.x86asm.net/coder32.htmlhttp://www.eji.com/a86/
>> NEW: http://ref.x86asm.net/coder32.html
>>
>> --
>>
>> Message: 2
>> Date: Sat, 2 Jul 2022 13:37:01 -0400
>> From: Travis Siegel 
>> To: "Discussion and general questions about FreeDOS."
>> , Bret Johnson 
>> Subject: Re: [Freedos-user] DOS ASM resources
>> Message-ID: 
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> Interestingly enough, I also bought a86/D86, and have found it to be the
>> best assembler/disassembler I've ever found for dos.? I ran across it
>> after (mostly) trying to use debug for things, so it was a welcome
>> relief.? I still use it when working on dos things, which admittedly
>> isn't very often these days, but at least it still works, and still does
>> what's needed.
>>
>> Of course, take this with a grain of salt, since I'm an intermediate asm
>> programmer (at best), and it takes me many hours to get anything
>> complicated untangled when looking at asm code, which is why I don't use
>> it much, but there's sometimes when nothing else can do the job as well,
>> so 
>>
>> Masm, Tasm, and others all have their own syntax which confuses me more
>> than helping.? I find debug and A86 fairly straightforward, which is why
>> I still like those methods when working with asm code.
>>
>> On 7/1/2022 11:58 AM, Bret Johnson wrote:
>>> Santiago:
>>>
>>> I agree pretty much with ECM. The best way to learn is to look at the code 
>>> someone else has written and try to understand it. Unfortunately, most ASM 
>>> coders aren't very good at comments/documentation, and you really need the 
>>> comments to help you figure things out. Looking at uncommented code doesn't 
>>> seem to help me very much -- I need to try and figure out how the coder was 
>>> thinking, not just the result of the thinking.
>>>
>>> I put LOTS of comments in my code -- I'm sure at least some people think 
>>> too many. Almost every line of the source has a comment, and each 
>>> "subroutine" has a comment header similar to what ECM has (but my "style" 
>>> is different than ECM's). The comment header includes details about what 
>>> the subroutine does, its inputs and outputs, and what it may change. The 
>>> header MAY also include the "context" of when and where the subroutine 
>>> should get used, and why the subroutine even exists at all (especially if 
>>> it is there to address some "special" situation). For example, most of my 
>>> programs are TSR's and in the most recent versions I'm working on the 
>>> programs can use different kinds of memory: conventional, upper, Expanded 
>>> (EMS), and/or Extended (XMS, which I access through a DOS Protected Mode 
>>> Services or DPMS server). I have comments to try and explain why I do 
>>> something that requires a special consideration for one of the different 
>>> types of memory. An example of this would be that you NEVER want a stack to 
>>> use Expanded memory, so sections of the code related to the stack need to 
>>> take that into account and should make some comment about it.
>>>
>>> When I first started (a LONG time ago), modern assemblers like NASM & FASM 
>>> didn't exist, and I didn't like MASM (though it was and still is kind of 
>>> "the standard" I 

Re: [Freedos-user] Limit text output to specific area

[Mercury Thirteen via Freedos-user]

Ah. Perhaps I'm remembering it incorrectly. It's been a long time since I used 
the BIOS-based windowing functions. :)






Sent with Proton Mail secure email.
--- Original Message ---
On Tuesday, June 14th, 2022 at 8:44 PM, Zbigniew  wrote:


> > The content will indeed wrap, just on a per-character basis instead of
> > per-word. It functions exactly how wrapping does when printing to the entire
> > screen.
>
>
> Which exactly BIOS/DOS interrupt/function you mean? Just made a short
> test using int 10h/06
> and it doesn't work that way.
> It makes a "window", but the function int 21h/09 prints the text at
> the former cursor position, not within a "window"
> --
> regards,
> Z.
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Limit text output to specific area

[Mercury Thirteen via Freedos-user]

The content will indeed wrap, just on a per-character basis instead of 
per-word. It functions exactly how wrapping does when printing to the entire 
screen.




Sent with Proton Mail secure email.
--- Original Message ---
On Tuesday, June 14th, 2022 at 7:53 PM, Zbigniew  wrote:


> > If you're speaking purely about limiting the cursor to the bounds of the
> > current window (which is what I believe you're referring to), yes I believe
> > it does do that much, if I remember correctly.
> >
> > However, if you're referring to some kind of "smart" word wrap ability, the
> > answer is no. The BIOS performs only basic dynamic text port sizing and does
> > not provide any sort of text wrapping or kerning features. It merely wraps
> > text to the boundaries of the window, just as it would when writing strings
> > to the full screen. Of course a programmer could always make their own... :)
>
>
> A little bit strange. You mean BIOS 10h will trap cursor, but if I
> do any output
> its screen-output functions won't do word-wrap within the bounds of the 
> window?
> --
> regards,
> Z.
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Limit text output to specific area

[Mercury Thirteen via Freedos-user]

If you're speaking purely about limiting the cursor to the bounds of the 
current window (which is what I believe you're referring to), yes I believe it 
does do that much, if I remember correctly.

However, if you're referring to some kind of "smart" word wrap ability, the 
answer is no. The BIOS performs only basic dynamic text port sizing and does 
not provide any sort of text wrapping or kerning features. It merely wraps text 
to the boundaries of the window, just as it would when writing strings to the 
full screen. Of course a programmer could always make their own... :)




Sent with Proton Mail secure email.
--- Original Message ---
On Tuesday, June 14th, 2022 at 6:18 PM, Zbigniew  wrote:


> Googling around gave no result. It seems it doesn't exist „ready for
> use”, so just to make sure:
> does DOS/BIOS offer any possibility to set active screen output
> „window” — I mean something like BIOS int 10h/06-07 — but trapping
> cursor inside?
> What I mean is using all the ordinary functions that do character
> output and having wrapping/scrolling on automatic (no counting
> characters necessary, not managing cursor position „manually” etc.)
> --
> regards,
> Z.
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] x86Box

[Mercury Thirteen via Freedos-user]

I realize this is a work in progress, but perhaps "The most popular emulators 
are listed here:" should instead say something like "FreeDOS images for some of 
the most popular emulators are listed here:" :)




Sent with ProtonMail secure email.
--- Original Message ---
On Tuesday, April 26th, 2022 at 1:06 PM, Jim Hall  wrote:


> On Tue, Apr 26, 2022 at 9:05 AM Daniel codehunte...@gmail.com wrote:
>
> > Has anyone looked into using x86Box as an alternative to vmware and 
> > virtualbox to run FreeDOS and other old operating systems?
>
>
>
> Hi Daniel
>
> If you mean 86Box, we already have a link to it on the FreeDOS website:
> https://www.freedos.org/links/
>
> In the redesigned website, the links to the different VM software will
> probably be on the "Downloads" page, so folks will see it, like on
> this mock-up:
> http://test.freedos.org/download/
>
>
>
> Jim
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] ECHO vs @ECHO

[Mercury Thirteen via Freedos-user]

Would it be feasible to throw together an "@ECHO.COM" application which would 
manually execute a normal "ECHO OFF" line if the DOS version is below 3.3 and 
simply terminate otherwise? The only caveat to this is that I''m not 100% 
certain that a command executed from within a .COM file from within a batch 
file like this would work back "upstream" and turn ECHOes off for the rest of 
the original batch file.


Sent with ProtonMail Secure Email.

--- Original Message ---

On Friday, February 25th, 2022 at 8:54 PM, Bret Johnson  
wrote:

> This question is more about DOS in general than specifically about FreeDOS. 
> But, there are enough experienced and creative users around FreeDOS that 
> someone may be able to help me come up with a solution.
>
> I have a large set of DOS environments I use for testing. Basically, I have a 
> bunch of different versions of DOS that I can boot to (MS-DOS, PC-DOS, 
> FreeDOS, DR-DOS, from versions 3.0 to the latest of each). DOS versions 1 & 2 
> were so lackluster that I don't bother even testing with them. I have a copy 
> of the commercial program called System Commander which allows me to install 
> and boot all these different versions of DOS from a single partition on a 
> hard drive. I know there are other ways to accomplish the same feat, but I 
> bought a copy of System Commander a long time ago so that is what I use.
>
> I have all these DOS's installed on a Virtual hard drive so that I can run 
> them in different Virtual Machines with different types of CPUs (from the 
> lowly 8088 all the way up to modern CPUs). Again, this is a test environment 
> so that as I write programs I can verify they work whenever and wherever 
> they're supposed to.
>
> On the Virtual hard drive part of what System Commander does as you boot is 
> "restore" the hidden boot files (IO.SYS & MSDOS.SYS for MS-DOS, IBMBIO.COM & 
> IBMDOS.COM for PC- and DR-DOS, or KERNEL.SYS for FreeDOS), along with the 
> COMMAND.COM, CONFIG.SYS, and AUTOEXEC.BAT files so that the virtual machine 
> boots with the correct test environment.
>
> The problem is that the older versions of DOS don't work exactly like the 
> newer versions, particularly when it comes to batch files. For example, prior 
> to DOS version 3.3 you couldn't CALL one batch file from another, and also 
> prior to DOS version 3.3 you couldn't use the @ symbol at the beginning of a 
> line in a batch file to hide the output of the line (sort of similar to what 
> happens with the ECHO OFF you normally put at the beginning of batch files 
> but the @ symbol only works for a single line instead of the entire batch 
> file like ECHO OFF does).
>
> So, I have a relatively short AUTOEXEC.BAT file set up for each OS I boot, 
> which is unique to each OS. The main thing this small AUTOEXEC.BAT does is 
> set up some environment variables to identify the OS that booted which can be 
> used later in other batch files. At the end of the "simple" AUTOEXEC.BAT 
> file, I then jump to a "master" AUTOEXEC.BAT file that is common to all the 
> booted DOS's. Because each version of DOS is a little different, the "master" 
> AUTOEXEC.BAT file needs to do some "IF-THEN" scenarios based on which version 
> of DOS is running. I want the overall environment to be pretty much the same 
> (as much as I can, anyway) no matter which DOS is running. Having a "master" 
> AUTOEXEC.BAT file lets me make most of my changes in one common place instead 
> of needing to do the same thing a bunch of different times for each DOS 
> version.
>
> One problem I haven't figured out how to handle correctly is the ECHO OFF vs 
> @ECHO OFF issue. In older versions of MS- and PC-DOS (prior to version 3.3), 
> and all versions of DR-DOS, the "@ECHO OFF" command does not work at the 
> beginning of batch files. You need to use a simple "ECHO OFF" instead. If 
> they see an "@ECHO OFF" they display an "unknown command" error (it tries to 
> find an executable files called "@ECHO"). I'm trying to figure out a way for 
> all the "common" batch files (all batch files other than the small 
> AUTOEXEC.BAT file) to detect whether they can put the "@" at the beginning of 
> the line or not to keep the screen from getting unnecessarily cluttered and 
> confusing. I cannot figure out a way to do this. I'll go through some of the 
> things I've tried (to no avail -- the all put "unnecessary stuff on the 
> screen).
>
> I've tried creating an ECHO environment variable. With older versions of DOS:
>
> SET ECHO=ECHO OFF
>
> and with newer versions of DOS:
>
> SET ECHO=@ECHO OFF
>
> then at the beginning of all batch files I put a:
>
> %ECHO%
>
> That works with older versions of DOS but not newer versions. With newer 
> versions, it sees the "%" at the beginning of the line instead of the "@" and 
> looks for an executable file called "@ECHO" instead of seeing the "@" as the 
> "hide this line" character.
>
> Another option would be to create an actual @ECHO.BAT file and always put 

Re: [Freedos-user] Difficulty with serial communications

[Mercury Thirteen via Freedos-user]

Hi there,

Not sure if they'll have quite the information for which you're looking, but 
for all my low level programming needs I always turn to 
[OSDev](https://wiki.osdev.org/Expanded_Main_Page).

Hope this helps!

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

‐‐‐ Original Message ‐‐‐

On Thursday, February 3rd, 2022 at 8:46 AM, G.W. Haywood via Freedos-user 
freedos-user@lists.sourceforge.net wrote:

> Hi there,
>
> Sorry to rake up an old thread, it's what I could find in the archives.
>
> If Sourceforge provides a better search tool than what I've seen I'd
>
> be very pleased to know about it. I found this using a Google clone.
>
> On 2018-06-21 Ralf Quint wrote:
>
>> ... I am currently away from my FreeDOS programming stuff, I could
>>
>> send you some diagnostic tool either tomorrow or over the weekend ...
>
> My application is a very old suite of business software which I wrote
>
> about 30 years ago and is still in very active use. It's a multi-user
>
> sales/purchases/stock control/ etc. accounting system. It runs under
>
> FreeDOS, MS-DOS and Linux. It can use multiple serial port cards for
>
> the user terminals. The largest DOS installation I've done was eleven
>
> terminals (+console), although most only use one or two. Changes in
>
> legislation in the UK mean that here and there an extra I/O port will
>
> be wanted for what HMRC calls the 'digital link' between the business
>
> software and the desktop stuff which interfaces with HMRC's computers.
>
> The multi-port cards I've used in the past have been ISA. I did have
>
> to modify some of them to share interrupts, but that's always worked
>
> OK. Of course these won't fit in most recent computers. Multi-port
>
> PCI cards I've seen handle interrupt and I/O addressing differently
>
> from the way the ISA cards did it. I/O addresses are no problem, any
>
> address is configurable in the software, but despite claims to be able
>
> to use IRQ3 and IRQ4 in the sales literature none of the PCI cards
>
> that I've tried so far appears to be able to use either. My software
>
> expects that only those will be used for serial comms (if you think
>
> that means the software is silly, I'd blushingly have to agree).
>
> At some point I'd like to modify the software to handle more recent
>
> hardware but it's a long time since I did all that and I've almost
>
> forgotten how it all hangs together. If for example there's a TSR or
>
> something which can say route IRQ19 to IRQ3 I think that would do for
>
> the forseeable future, but I don't even know yet if that makes sense.
>
> If you (or anyone else) can point me to comprehensive and reliable
>
> documentation and/or tools useful for the investigation and routing of
>
> interrupts for PCI expansion cards under DOS I'd be most grateful.
>
> ---
>
> 73,
>
> Ged.
>
> Freedos-user mailing list
>
> Freedos-user@lists.sourceforge.net
>
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Interesting comment by Walter Bright

[Mercury Thirteen via Freedos-user]

Interesting he doesn't mention that Digital Mars is his own company.

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, January 29th, 2022 at 11:37 PM, Louis Santillan 
 wrote:

> He claims "The DMC++ compiler is far and away the best C++ compiler on DOS."
>
> https://news.ycombinator.com/item?id=30127615___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Cutemouse /O

[Mercury Thirteen via Freedos-user]

Most mice operate in a "staged" manner; that is, upon power-up even the most 
sophisticated mouse emulates a basic two button affair, until software jumps 
through a series of hoops to elevate its capabilities by sending a series of 
magic sequences of commands. The problem is that most applications only go as 
far as elevating the mouse to three button operation (if that - some perform no 
"elevation" at all, and leave you stuck with the most basic mouse mode) and 
never even attempt to activate wheel mode. Regardless of mode, however, the 
PS/2 interrupt (at least for PS/2 mice) fires the same way.

This is done because an interface to the enhanced features of advanced mice was 
never standardized, so manufacturers made do with existing commands, but simply 
gave special significance to certain sequences of them which would not normally 
occur in typical application usage. One such example is setting the mouse 
acceleration with a specific series of values instead of the usual procedure of 
directly setting the desired acceleration value directly and leaving it at that.

On Friday, January 21st, 2022 at 10:43 AM, Travis Siegel tsie...@softcon.com 
wrote:

> I believe the problem with the scroll wheel is that it doesn't generate
>
> an interrupt, so if the mouse driver doesn't specifically look for the
>
> scrool wheel, there's no way for the computer or operating system to
>
> know that it is being used. I had a similar problem under windows
>
> several years ago, and the solution was to turn off one of the settings
>
> in the dos prompt configuration. That also allowed right clicking within
>
> the dos prompt, (not just on the dos application, so you could select
>
> paste, copy and such), but actually have the right click be passed to
>
> the dos application. That particular configuration item has since
>
> stopped working as it used to. But, on the other hand, it's really not
>
> necessary anymore, since a right click does the proper thing now. I have
>
> no idea if there's an equivalent option for dos mouse drivers, but I do
>
> know if the driver doesn't support scroll wheels, then your mouse won't
>
> respond to the wheel, no matter how much you move it or click it.
>
> Perhaps there's a command line parameter to activate the scroll wheel on
>
> your particular driver. I've never used the cute mouse driver, so can't
>
> say if it does have such a parameter or not.
>
> On 1/21/2022 7:25 AM, Björn Morell wrote:
>
>> Hi,
>>
>> The progs I found which can use scroll wheel
>>
>> 4Dos; Help,Select and History
>>
>> Syschk
>>
>> MPXplay
>>
>> I have tried wheelk butit does not make any difference in any program
>>
>> I tried,
>>
>> I really would love for it to work in File Wizard.
>>
>> Have any of you found other programs or ways there scroll mouse works ?
>>
>> Bear
>>
>> Freedos-user mailing list
>>
>> Freedos-user@lists.sourceforge.net
>>
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> Freedos-user mailing list
>
> Freedos-user@lists.sourceforge.net
>
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Question about FreeDOS 3.0

[Mercury Thirteen via Freedos-user]

On Tuesday, November 30th, 2021 at 11:34 PM, dmccunney 
dennis.mccun...@gmail.com wrote:

> ...
>
> And this is not a machine you want to try to set up FreeDOS to run from the 
> bare metal on. Too much of the hardware is simply not supported by any form 
> of DOS. DOS stopped being sold and supported long before some of it existed, 
> and it uses UEFI, not a BIOS, so getting DOS to boot on it will be a real 
> challenge.
>
> ...

It would be interesting to find someone who purchased it and see exactly what 
software HP bundles with it.

[sarc]
I mean, come on, HP. You love to bundle software with everything! We can't even 
buy a printer from you without getting 1.7 GiB of extra crap on a disc. So what 
about FreeDOS? Hmm?
[/sarc]

But seriously, though, I wonder if the hardware in this specific laptop is 
actually supported under DOS, and perhaps HP supplies drivers for it just like 
they would supply drivers for Windows or whatever other OS they would sell 
alongside their hardware. Yeah, I know that's probably not the case. But that 
would be nice. That would be nice. :)___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Shared Folders not allowed in VirtualBox FreeDOS?

[Mercury Thirteen via Freedos-user]

Since I run a similar setup (Linux Mint with VirtualBox), I'll take this one. :)

The short answer is no.

The long(er) answer is that VirtualBox makes available a specific programming 
interface for the Shared Folders feature which provides both a 64-bit and 
32-bit entry point for the guest OS - something of which the 16-bit FreeDOS (or 
any other flavor of DOS, for that matter) cannot natively take advantage. 
Although a DOS extender could perhaps come to the rescue some day.

In my opinion, the easiest way to share files from host to guest is to use 
FTPSRV in the FreeDOS virtual machine and FileZilla in Linux to connect the 
two. This is the method I use, and I find it to be quite straightforward. In my 
experience the packet driver for the Intel PRO/1000 network adapter which is 
included with FreeDOS is buggy and causes transfers to time out occasionally, 
so if you go this route, I recommend using the PCnet-FAST III network adapter 
for your virtual machine along with the AMD PCnet DOS packet driver which is 
freely available on the internet.

If you ever find it necessary to exchange files between two DOS virtual 
machines, it gets even easier: simply make/download a blank floppy image and 
attach it to both machines at once. Saving files to the A drive in one machine 
will instantly show up on the A drive of the other, even when both are running 
simultaneously - just don't try writing to the floppy image from both machines 
at the same time. :)

Good luck!

On Wednesday, July 14th, 2021 at 9:03 AM, kaye n  wrote:

> Hello Friends
>
> My host is a linux OS. I think I have successfully installed FreeDOS in 
> VirtualBox.
>
> When the virtual FreeDOS is running, I want to be able to access my USB flash 
> drive as well as a Windows partition on the physical hard drive.
>
> I assume this is not possible?
>
> Thank you for your time.
> Kaye___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] A new UHDD release! :D

[Mercury Thirteen via Freedos-user]

Hey all!

I've packaged up the most recent version of UHDD, which you can find at 
MercuryCoding.com/downloads.html#DOS. The new version supports Read-Ahead and 
DMA/Caching Overlap for all cache sizes from 5 to 4093 MiB, which should help 
make all the work done by Jerome's FreeDOS installer happen faster than ever.

Enjoy! :)

Sent with [ProtonMail](https://protonmail.com/) Secure Email.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Easter Egg

[Mercury Thirteen via Freedos-user]

Nice!

I notice that, following the line which reads:
"FreeDOS Alpha 1 was released on September 16, 1994."

the next sentence reads:
"That is over 25 years or history."

which I believe should read:
"That is over 25 years of history."

Not being nitpick-y, just FYI. :)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, May 25, 2021 8:42 AM, Jerome Shidel  wrote:

> FreeDOS 1.3-RC4 LiveCD Easter Egg…
>
> https://youtu.be/SB17eypovvY___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Forwarding and commenting a FreeDOS 1.3rc3 critical review

[Mercury Thirteen via Freedos-user]

OH! I guess I should've read the entire email, eh? lol


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, May 15, 2021 3:22 PM, Robert Riebisch  
wrote:

> Hi Mercury,
>
> > > ...
> > > MSD?
> > > ...
> >
> > Microsoft System Diagnostics
> > A pretty handy little system evaluation tool Microsoft made back in the day.
> > https://en.wikipedia.org/wiki/Microsoft_Diagnostics
>
> Thanks, but I know MSD, as you can see in my posting you replied to now.
>
> ###
>
> 2.  Here's a screenshot of the main window:
> https://winuxinfocenter.de/wp-content/uploads/2018/09/msd1.png
>
>
> ###
>
> I wrote "MSD?" (with a question mark), because I wasn't sure, if Eric
> referred to MSD or SPEEDSYS with his "it" in "Which features does it
> have which COMPINFO is lacking?".
>
> Cheers,
> Robert
>
> ---
>
>   +++ BTTR Software +++
>  Home page: https://www.bttr-software.de/
>
>
> DOS ain't dead: https://www.bttr-software.de/forum/
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Forwarding and commenting a FreeDOS 1.3rc3 critical review

[Mercury Thirteen via Freedos-user]

‐‐‐ Original Message ‐‐‐
On Saturday, May 15, 2021 2:04 PM, Robert Riebisch  
wrote:

> ...
> MSD?
> ...

Microsoft System Diagnostics

A pretty handy little system evaluation tool Microsoft made back in the day.

https://en.wikipedia.org/wiki/Microsoft_Diagnostics


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Why do you use DOS

[Mercury Thirteen via Freedos-user]

I was fortunate enough for my early years to be in the DOS era (albeit near its 
end) and I still remember the tiny pang of sadness upon reading that Microsoft 
was phasing out the venerable platform.

My first computer was an IBM PC/XT with DOS 3.something, which was a 
hand-me-down from my uncle after the university at which he works decided to 
dispose of it. Years later, I graduated to another hand-me-down; a Packard Bell 
486 machine with a mind-blowing 4 megs of RAM running DOS 6.22 and Windows 
3.11, obtained from a friend at church. Both machines were a fascinating 
learning experience, teaching me the ins and outs of "The DOS Way" and they 
were my first exposure to programming, first in QBASIC, then Microsoft's Visual 
BASIC for DOS, then eventually Bob Zale's Power BASIC. I've since moved on to 
Assembly, C, and JavaScript for the occasional day-job coding I need to perform 
- [Dijkstra's quote be darned 
(lol)](https://programmingisterrible.com/post/40132515169/dijkstra-basic) - but 
BASIC is still a faithful favorite. Some of my work has involved the machine 
tool industry, which has many CNC operators still using DOS-based PLC controls 
to this day. When an aging PC gives up the ghost on a vertical turret lathe 
valued in the hundreds of thousands of dollars, the ability to quickly set up a 
new replacement system complete with FreeDOS and a small collection of utility 
programs to get the client up and running is invaluable. Additionally, I still 
occasionally use DOS personally because, despite all the "advances" coming out 
of Redmond, I find Windows offerings way too bloaty and chock full of 
training-wheels design - both of which I detest. Even Linux, as enlightened as 
it is, pales in comparison to the speed, efficiency, small size, and sheer 
customizibility of FreeDOS.

In short, (Free)DOS is everything an OS should be. It puts power in the user's 
hands to control their machine however they wish. It remembers that the owner 
of the computer is the user - not the OS.

Kudos to Jim et al. for their work on this great platform!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, April 14, 2021 11:59 AM, Johnpaul Humphrey jpth1...@gmail.com 
wrote:

> In light of the "DOS was dead" discussion, I wanted to ask a question.
> I was born after support was dropped for MS-DOS, so I can't claim
> nostalgia as my reason for use. Recently I installed FreeDOS on my
> modern HP-Pavilion laptop, alongside BSD, Linux, and plan9. I did this
> because I like DOS's speed and assembly programming.
> It worked fine after I fixed the beep bug with your help.
> So my question is, why do YOU use FreeDOS?
> Is it primarily nostalgia? Legacy program support? Speed?
> Note that I don't consider running legacy software a bad reason. I was
> shocked by how much good software has been "thrown away" because of
> its age. On Linux all my favorite software (vi, siag office, twm,
> motif ) was written before I was born. However, that is not my
> primary reason for using FreeDOS. my primary reason is because it is
> like the motorcycle of operating systems. It is lightweight, has no
> red tape to cut through to do things, and is monotasking. (Monotasking
> is also why I don't use it as much as I would like to, but why I use
> it at all.)
> I figured that if I had a different reason than what everybody
> assumes, that some of you might as well. Everyone seems to assume that
> DOS is used by people who are unable to cope with progress and have to
> run their ancient version of word perfect. If that is your reason, it
> is not a bad reason. I was thinking of eventually writing a 64-bit dos
> work [sort of] alike eventually, but it would not be able to support
> legacy programs due to segment offset addressing and a million other
> things.
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Why do you use DOS

[Mercury Thirteen via Freedos-user]

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, April 14, 2021 6:09 PM, Liam Proven lpro...@gmail.com wrote:

> On Wed, 14 Apr 2021 at 18:00, Johnpaul Humphrey jpth1...@gmail.com wrote:
>
>> So my question is, why do YOU use FreeDOS?
>
> OK. Disclaimer first: I do have FreeDOS here and there but I
> personally prefer running PC DOS 7.1 or DR-DOS. The small differences
> in FreeDOS irritate me, and I am more familiar with these versions. I
> worked in tech support on DOS in the 1980s and 1990s and know those
> versions best.
> That aside: why do I still run DOS?
> Well, I built up a lot of skills in DOS in my early career –

"But what I do have are a very particular set of skills, skills I have acquired 
over a very long career..."
Liam, are you sure your last name isn't Neeson? lol
But seriously though, you capture many of the same reasons I myself still use 
DOS. I may not use it often, but when I do, the immense power and control it 
gives me to perform the task at hand is unparalleled. Cheers to (Free)DOS! :D

> I won jobs on the basis of my DOS troubleshooting and optimisation skills. I
> was an expert in DOS manual memory management and could usually get
> circa 620 kB free conventional memory even on a heavily-loaded machine
> with multimedia, an optical drive and a network stack.
> These skills are completely obsolete and redundant these days.
> So, installing DOS, especially on real hardware, is a fun chance to
> exercise old skills that I do not get to use any more.
> There are a huge number of DOS applications out there as abandonware
> these days, albeit only quasi-legal. It's the work of minutes to
> assemble a top-flight selection of office apps worth thousands of
> £/$/€ 30 years ago. I know how to use many of these apps very quickly
> and efficiently.
> DOS takes little maintenance, especially compared with 21st century Windows.
> It's very fast, it does a lot of what I need, and also it's blissfully
> free of distractions once you've got it working. You can't just
> Alt-Tab to another window and then waste hours idly surfing the Web.
> You can't meaningfully use the Web at all. That helps me to get more
> done.
> It's also handy for re-flashing BIOSes and things like that. :-)
> ---
>
> Liam Proven – Profile: https://about.me/liamproven
> Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com
> Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
> UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Recovery of a file on a non booting Windows computer

[Mercury Thirteen via Freedos-user]

+1 on the Linux Mint recommendation. Out of all the Linuxi I've personally 
tried, I've found Mint to be quite user friendly and I would say it's a great 
place to start for those more familiar with a Windows-like interface.


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, April 14, 2021 12:43 PM, Ralf Quint  wrote:

> On 4/14/2021 5:19 AM, Stephanos wrote:
>
> > Dear All
> > I want to boot to freeDOS using a CD ROM.  Then I want to insert a
> > memory stick into the computer and copy a file from the Windows HDD onto
> > the memory stick.  Is this possible and if so which version of freeDOS
> > do I use?
>
> If you are talking about any Windows newer than Windows ME, simply
> forget about this route.
>
> Use a Linux Live CD (I personally would recommend Linux Mint 20.1 Mate)
> and use that one instead...
>
> Ralf
>
>
> --
>
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FSF

[Mercury Thirteen via Freedos-user]

Exactly! :D


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, March 31, 2021 7:13 PM, Bryan Kilgallin  
wrote:

> Thanks, Rugxulo:
>
> > Just
> > because someone doesn't agree with him, even if he speaks
> > egregious words, doesn't mean he should be destroyed.
>
> "I Disapprove of What You Say, But I Will Defend to the Death Your Right
> to Say It"
> Evelyn Beatrice Hall
>
> ---
>
> members.iinet.net.au/~kilgallin/
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FSF

[Mercury Thirteen via Freedos-user]

+1


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, March 31, 2021 7:08 PM, Rugxulo  wrote:

> Hi,
>
> On Wed, Mar 31, 2021 at 12:04 AM dmccunney dennis.mccun...@gmail.com wrote:
>
> > Meanwhile, I'm beyond caring about Stallman or the state of the FSF.
> > Both deserve whatever happens to them.
>
> It might be more honest (only guessing here) to admit that "He
> stresses me out, I can't deal with him, I don't understand him, and I
> have no need to interact with him." But the way you describe it here
> (although I admit you have some indirect?? experience) sounds not only
> indifferent but rather like a grudge or vendetta.
>
> I don't believe in the death penalty. And we certainly don't burn down
> prisons with everyone inside them just because we don't like the
> crimes that were committed by them. That would be inhumane and unjust.
>
> Richard Stallman has not been convicted by a court. He is not in
> prison. Let's not burn his house down over pathetic words. It's very
> easy to take things the wrong way unintentionally. We shouldn't all
> have to walk on eggshells and be "literally" perfect just because
> angry people always want to punish somebody, anybody, who gets in
> their way.
>
> He's not perfect. He doesn't have to be. If we can't deal with him
> rationally and justly, that's our problem, not his. (But judging
> people we've never met without any direct evidence other than
> fragments of sentences online over several decades isn't actually
> enough to convict anyone. It's not true justice.)
>
> I don't mean you specifically (obviously?). You're allowed to vent and
> have emotions. You can make your own decisions. You don't need my
> help. But overall it's not fair to hate someone based upon so little
> information.
>
> Let's not overreact. Let's forget it entirely. It's truly not our
> domain to judge him.
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FSF

[Mercury Thirteen via Freedos-user]

+1

Despite not being a Stallmanite myself, I seriously couldn't agree more. 
Besides, it's not like he just got hired to the board of an organization 
fighting human trafficking... it's software. Completely unrelated. One's 
opinion on any given topic has little to nothing to do with how well they can 
perform their job in a completely unrelated field.

And once this drama starts, where does it end? Shall we have a survey of all 
FreeDOS users to determine which ones hold unpopular opinions and disassociate 
from them en masse? And who decides what opinions are unpopular? The 
ludicrosity of this logic becomes quickly apparent.

Lots of Stallman's views are vastly misaligned with my own, however we may 
disagree with others on matters of principle (or even because they're simply an 
unpleasant sort of fellow) and yet be mature enough to see the importance of 
upholding their right to hold that very idea which we may consider outlandish 
and offensive.

Opinion outrage such as this is very tiring these days, not to mention has 
little to do with FreeDOS itself as a whole.



Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 29, 2021 6:24 PM, Rugxulo  wrote:

> Hi,
>
> On Mon, Mar 29, 2021 at 2:40 PM tom ehlert t...@drivesnapshot.de wrote:
>
> > https://arstechnica.com/gadgets/2021/03/red-hat-withdraws-from-the-stallman-led-free-software-foundation/
> > maybe it's time to show the FSF the middle finger, too?
> > Tom
>
> Why do you bring this drama here?? How does quasi-political outrage
> affect FreeDOS? There is little to link FreeDOS to FSF other than the
> GPL, but (as you know) the GPLv2 is very, very popular overall in the
> software world.
>
> Honestly, he's been known as "very eccentric" for many years. I don't
> think anybody is surprised. He has opinions and voices them (whether
> unpopular or not). You know what they say about opinions, right?
> Everyone has one.
>
> Let's not crucify anyone, and let's not cancel any technical plans
> because of irrational anger.
>
> You don't have to like or support him, but keep in mind that it's very
> inconvenient having to walk on eggshells just because various other
> people can't get along for trivial reasons. (Yes, hypothetical
> opinions are trivial. If someone can't handle their own emotions upon
> every outrageous statement, nobody else wants to deal with that. It's
> reasons like this that I don't use Twitter.)
>
> Please don't fan the flames here. It's not important. If you want to
> start a crusade, you're going to lose.
>
> (Jim, I'm not condoning his opinions, but it's tiring always reading
> about drama like this.)
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] [OT] BIOS weirdness with SATA/IDE adapter

[Mercury Thirteen via Freedos-user]

On Thursday, March 11, 2021 12:49 AM, Nils Stavlid  wrote:

> Dear all,,, personally I like it whenever topics spiral out on a side track 
> like in this case.
> ...

As do I! It's refreshing to see all the diversity of thought in everyday 
FreeDOS users. Cool stuff! :)___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] [OT] BIOS weirdness with SATA/IDE adapter

[Mercury Thirteen via Freedos-user]

Agreed. I guess we can thank Tom for that! lol


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, March 10, 2021 5:23 PM, Random Liegh via Freedos-user 
 wrote:

> Is this a conversation that really needed to happen on a public,
> technical list?
>
> No, it is not. It could and should have been moved to private emails.
>
> I'd like to request that it continue there so the rest of us aren't
> forced to have our inboxes filled with unwanted nonsense.
>
> Thanks!
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] BIOS weirdness with SATA/IDE adapter

[Mercury Thirteen via Freedos-user]

I'll step in for a brief moment to answer this in my own way prior to Felix 
doing so. Sorry, Felix. :)

As to why you must be "annoyed" by anyone else's choice of email signature, I 
would point out the Christo-American concept of free speech. Felix has complete 
freedom to say whatever he wants whether in person or via email signature, just 
as you have complete freedom whether or not to be annoyed by it. It's basically 
the same concept everyone else here applies when reading one of your overly 
dramatic responses; we understand you have freedom to say anything you want, 
and we choose to not let ourselves be bothered with taking it seriously.

And as for the heart of the "nonsense" itself - if you are in fact genuinely 
interested in the subject and not in simply firing off one more snippy email - 
I would start with the works of Dr. Stephen Meyer, Eric Metaxas, Dr. James 
Tour, and John Lennox, Professor emeritus of Mathematics at Oxford University. 
A brief catalog of some of their relevant videos, which may be easier to digest 
than the sum of their published works:

https://www.youtube.com/watch?v=y02a28FrMKs
https://www.youtube.com/watch?v=8FKmIDApbe0
https://www.youtube.com/watch?v=zU7Lww-sBPg
https://www.youtube.com/watch?v=x5tUDJ23Kms
https://www.youtube.com/watch?v=wBio3y0Rrbc

Granted, these fellows aim more generally towards the scientific community as 
opposed to schools, but the same conceptual parallels remain.

*donning my best announcer's voice*
And now, back to you, Felix!
:)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, March 10, 2021 4:15 PM, tom ehlert t...@drivesnapshot.de wrote:

> "Evolution as taught in public schools, like religion,
> is based on faith, not on science."
> either give us a pointer why you think you must annoy us with that,
> or please stop with that (mostly religious) nonsense.
> Tom
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Updates to the FreeDOS website?

[Mercury Thirteen via Freedos-user]

It looks great! My only suggestion would be to add top padding to the "Download 
FreeDOS" and "What’s New" sections so that the title of one does not appear 
immediately beneath the previous for better visual separation.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, February 21, 2021 8:08 PM, Jim Hall  wrote:

> Hi everyone! I mentioned in another email that I'm working on a few changes 
> to the FreeDOS website. The goals in this update are to make things easier to 
> find, to improve accessibility, and to make it easier to share news items to 
> social media.
>
> I've updated the test site based on your feedback from last time, and I'd 
> like to know what you think of the new version.
>
> http://test.freedos.org/
>
> However, not everything is working yet! Specifically, most "sub-pages" (links 
> to other pages on this site) will put you on a plain text page with a 
> description of what the page will be about. So if you get a "plain text 
> page," it's just not updated yet.
>
> Also: the green bar at the top of the page is not part of the website 
> redesign. That's just meant as an alert that you are on a test site. That 
> green bar will go away in the final update.
>
> Would you like to test the new website? There's a link in the green bar where 
> you can answer some questions to provide directed feedback. You can email me 
> your reply.
>
> (If it looks like this design works well, then my next step will be to apply 
> the new design to the rest of the test website, and see how the "sub-pages" 
> work with the new design.)
>
> Thanks!
>
> Jim___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Updates to the FreeDOS website?

[Mercury Thirteen via Freedos-user]

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, February 7, 2021 6:49 AM, Jim Hall  wrote:

> ...
> Do you need a tool tip for the social media icons? Each icon is the logo of a 
> different social media platform: Twitter, Facebook, YouTube. If you have an 
> account on one of these, the logo should attract you to that. If you don't 
> have an account on them, then you probably wouldn't click on it anyway. Or so 
> I assumed.
> ...

I'd say that's a safe assumption to make.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FYI: I'm speaking at FOSDEM'21 this weekend

[Mercury Thirteen via Freedos-user]

Yep, totally clueless over here lmao

Anyway, if anyone here is interested in the actual state of the project as 
opposed to accepting the claims of those quick to discountenance and slow to 
personally contribute, you're welcome to jump on over to [our 
forum](https://groups.google.com/g/night-dos-kernel). Feel free to join and 
help out the effort! :)

BTW, Jim! Thank you for highlighting our project in your video presentation! :D

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Friday, February 5, 2021 7:28 AM, tom ehlert t...@drivesnapshot.de wrote:

>> I want to get "1.3" finally wrapped up, and I'd like to have a
>> "2.0" someday. The NightDOS folks are working
>
> english is not my first language so i could missread this.
> but doesn't 'folks are working' suggest a plurality of human being,
> opposed to the reality of a single guy who ever contributed, but is
> currently busy with other stuff
>
>> on their updated kernel - if they can get it working
>
> currently, after 5+ years of development they have functionality of a
> FreeDOS 512 byte bootsector: read a file from FAT16 into memory.
> that's it.
>
>> and still runs all 16-bit DOS applications,
>
> or run ANY application.
>
>> then we could include that as an alternative kernel
>> for people who (a) have a more modern system, and (b) opt-in to use it.**
>
>> ** But, NightDOS is a long way from being able to do that. The
>> goals of NightDOS are pretty lofty,
>
> and he has not the faintest idea how to get there.
> Tom
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Updates to the FreeDOS website?

[Mercury Thirteen via Freedos-user]

Looks good! IMO, however, the text would look better below the video/image 
thumbnails.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Friday, February 5, 2021 3:55 PM, Jim Hall  wrote:

> Do the social media icons on this test page look better? (This also centers 
> the screenshots and "learn more" buttons.)
>
> http://test.freedos.org/test.html
>
> On Fri, Feb 5, 2021 at 2:29 PM Jim Hall  wrote:
>
>> Thanks, this feedback is very helpful!
>>
>> I hadn't finished styling the page. The next iteration will provide a 
>> narrower reading area (like the current www.freedos.org) which should help 
>> the "text spans from edge to edge of the screen" issue. Also will add 
>> spacing around the top "menu" items, and centering the screenshots and 
>> "Learn more" or "More videos" buttons.
>>
>> By "I like the icons at the footer in the current site" I think you mean the 
>> colors in the icons are easier to distinguish than plain gray icons in the 
>> updated design. I was curious what folks would think about that. I can put 
>> colors on those again. :-)
>>
>> Your other feedback on the scenarios/questions is also helpful, thanks!
>>
>> Jim
>>
>> On Fri, Feb 5, 2021 at 1:20 AM Robert Spiteri  wrote:
>>
>>> Hi,
>>>
>>> First of all thanks for all your work on FreeDOS.
>>>
>>> Allow me to give you my opinion regarding aesthetics since I develop 
>>> websites myself:
>>>
>>> - Text spans from edge to edge of the screen - It is quite tiring to read 
>>> especially on a wide screen. Consider limiting the content to a maximum 
>>> width of 1100px centered.
>>> - I would put What's New as the first section - Myself I would be 
>>> interested in knowing about any updates as soon as I visit the site
>>> - The top menu items are too crammed - consider adding some spacing between 
>>> them
>>> - Welcome to FreeDOS section - Consider centering the youtube videos and 
>>> the More Videos button
>>>
>>> Other than that I like the colours etc. Here are my replies to your 
>>> questions:
>>>
> 1. What is your immediate impression? Does it look easier to find 
> information? Is it more welcoming?
>>> Yes it is more welcoming but honestly I like the icons at the footer in the 
>>> current site.
>>> [..]___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] install freedos on eeepc 1201NL

[Mercury Thirteen via Freedos-user]

I would assume it has more to do with the mode of the disk controller. Check 
your BIOS (if it even gives you the option) to make sure it's set to the most 
PATA-compatible mode available instead of AHCI or something like that.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Friday, December 11, 2020 12:55 PM, Joao Silva  wrote:

> Hi!
>
> Trying to install Freedos 1.3 rc fullusb on a eeepc 1201NL but got a problem, 
> can't find hdd with windows 10 installed.
>
> Could be because of the ntfs fat?
>
> Thanks___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] AMB, Ancient Machine Book format and FreeDOS Help

[Mercury Thirteen via Freedos-user]

I have a feeling someone left the group up on a mobile device while in a 
pocket... lol

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, December 7, 2020 12:52 PM, Jim Hall  wrote:

> This person has been banned for spamming the group.
>
> On Mon, Dec 7, 2020 at 11:36 AM Kai Ketelhut  wrote:
>
>> Ml
>>
>> --
>> Lic. Kai Olaf K e t e l h u t sic
>>
>> Sent from my Android phone with GMX Mail. Please excuse my brevity.
>> On 07/12/2020, 18:34 Kai Ketelhut  wrote:
>>
>>> Stanca
>>>
>>> --
>>> Lic. Kai Olaf K e t e l h u t sic
>>>
>>> Sent from my Android phone with GMX Mail. Please excuse my brevity.
>>> On 07/12/2020, 18:33 Kai Ketelhut  wrote:
>>>
 [Freedos-user]
 [/Freedos-user]

 --
 Lic. Kai Olaf K e t e l h u t sic

 Sent from my Android phone with GMX Mail. Please excuse my brevity.
 On 07/12/2020, 18:30 Kai Ketelhut  wrote:

> ;
>
> --
> Lic. Kai Olaf K e t e l h u t sic
>
> Sent from my Android phone with GMX Mail. Please excuse my brevity.
> On 07/12/2020, 18:18 Eric Auer  wrote:
>
>> Kai,
>>
>>> ML
>>
>> That does not make any sense.
>>
>>> Lic. Kai Olaf K e t e l h u t sic
>>>
>>> Sent from my Android phone with GMX Mail. Please excuse my brevity.
>>
>> This is not brevity, this is plain spam. Even if this mailinglist
>> was a chat room, all messages so far have been unintelligible:
>>
>>> 00=
>>>
>>> Sound
>>
>>> 00=
>>
>>> .
>>
>>> ty_ty
>>>
>>> by ty::ty with EE2 google glass for ml by windows 7 by 5 14 floppy by 
>>> MIL-STD-810 in apendix of dos 1.0
>>
>> None of those emails has made any sense yet.
>>
>> Please move your fingers far enough to form actual words
>> and sentences and mail THOSE if you want to say something.
>>
>> Eric
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> ___ Freedos-user mailing 
> listfreedos-u...@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/freedos-user

 ___ Freedos-user mailing 
 listfreedos-u...@lists.sourceforge.net 
 https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>> ___ Freedos-user mailing 
>>> listfreedos-u...@lists.sourceforge.net 
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Make sure your opinion is heard

[Mercury Thirteen via Freedos-user]

I was thinking something along these lines. There could be a "Classic" install 
option which installs only the same components offered by MS-DOS, and a 
"Modern" option which has the same content, but with significant components 
swapped out for their more modern alternatives - e.g. a newer text editor 
instead of a basic EDIT clone, etc. On a subsequent screen, there could be an 
option for installing additional packages as part of the process, which would 
house the myriad of other components available.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, December 5, 2020 12:51 AM, TK Chia u1049321...@caramail.com wrote:

> Hello Jerome,
>
>> Some random additional thoughts,
>> I guess some times there was a little confusion with the 1.2 release over a 
>> FULL install.
>
> Maybe a good way would be to call a "FULL minus EXTRA" install by a less
> confusing name? E.g. perhaps call it a "RICH" install or something
> along those lines.
> Thank you!
> ---
>
> https://github.com/tkchia
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Old BIOS issue

[Mercury Thirteen via Freedos-user]

There's Y2KPatch which did the job on the dozen-or-so computers I had access to 
at the time. Be warned, however, that I make absolutely no guarantees as to how 
it will work on your system... I was a very young coder circa 1999, and I 
haven't revised it since.

You can find it here in the QBASIC Library:
http://mercurycoding.com/downloads.html

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, October 17, 2020 12:33 PM, ZB zbigniew2...@gmail.com wrote:

> Does there exist any DIY to fix "millennium bug" in old BIOS (no update
> available, unfortunately)? I mean "real fix, not workaround" - finding the
> proper cells in BIOS, modifying contents accordingly, burning... done
> ---
>
> regards,
> Zbigniew
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Run Linux & Linux binaries on DOS

[Mercury Thirteen via Freedos-user]

I've never used DSL, but I have used BusyBox back in my Android dev days. So:

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, September 29, 2020 12:33 PM, Jason Pittman 
 wrote:

> I know nothing about BusyBox, so I'm going to ask a dumb question. Does DSL 
> allow you to, say, install apt (or another package manager), gcc, make, etc., 
> or does it only allow you to run the common linux commands shown on the 
> BusyBox website?
>
> (And on a side note, has anyone actually gotten it to work? I'd already know 
> the answer to my question above if I could get it to do something other than 
> crash the VM when I run "dsl.com")
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, September 23, 2020 11:33 AM, Jim Hall  wrote:
>
>> After poking around the GitHub project, this is actually a very clever 
>> thing. Looks like he's using VM86 mode (requires '386 or later CPU) to 
>> instantiate a dedicated Linux kernel with BusyBox to run the Linux commands. 
>> This is not bringing up a full Linux installation in a VM - this is only the 
>> kernel + BusyBox. So that keeps it small.
>>
>> Now, what would you *do* with this? Why would you need DSL under FreeDOS? 
>> I'm not sure. But it's a neat idea that is well done. Good job!
>>
>> On Wed, Sep 23, 2020 at 10:41 AM Louis Santillan  wrote:
>>
>>> The author freely admits running DOS & Linux side-by-side this way is
>>> a fragile coordination [0]. I doubt that redirection would work as
>>> one might desire. The recently updated ascii demo [1] shows calling
>>> various DOS and Linux commands, and, shows creating a text file with
>>> `dsl vi hello.txt` and then later opening that same file with `edit
>>> hello.txt`. Interestingly, the file appears written to the filesystem
>>> as `HELLO.TXT`, as MS-DOS 6.22 is case insensitive (w/o a LFN driver).
>>> I wonder what would happen if an LFN driver was added to the mix.
>>>
>>> [0] https://news.ycombinator.com/item?id=24556801
>>> [1] 
>>> https://camo.githubusercontent.com/deb8f6b6cc59686ba91a3758daeb047fccdf05dd/68747470733a2f2f636861726c69652e73752f7265636f7264696e672d61633565396166353936613931382e676966
>>>
>>> On Wed, Sep 23, 2020 at 4:39 AM Eric Auer  wrote:


 Hi everybody,

 I would predict doslinux to be a variant of a Linux loader,
 so my questions here are: Can Linux safely write to the DOS
 partition while running? What are the limitations to return
 to DOS after using Linux? Is it possible to switch between
 DOS and Linux without having to reboot Linux each time? Are
 direct interactions possible, e.g. run single apps and pipe
 their output from Linux to DOS or from DOS to Linux?

 As Jim writes about modifications to make doslinux work with
 FreeDOS, it can probably do more than just load Linux, but I
 would be happy to read more about the details here on the list.

 Thanks :-) Eric



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Run Linux & Linux binaries on DOS

[Mercury Thirteen via Freedos-user]

"Does DSL allow you to, say, install apt (or another package manager), gcc, 
make, etc.,"

No.

"or does it only allow you to run the common linux commands shown on the 
BusyBox website?"

Yes.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, September 29, 2020 12:33 PM, Jason Pittman 
 wrote:

> I know nothing about BusyBox, so I'm going to ask a dumb question. Does DSL 
> allow you to, say, install apt (or another package manager), gcc, make, etc., 
> or does it only allow you to run the common linux commands shown on the 
> BusyBox website?
>
> (And on a side note, has anyone actually gotten it to work? I'd already know 
> the answer to my question above if I could get it to do something other than 
> crash the VM when I run "dsl.com")
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, September 23, 2020 11:33 AM, Jim Hall  wrote:
>
>> After poking around the GitHub project, this is actually a very clever 
>> thing. Looks like he's using VM86 mode (requires '386 or later CPU) to 
>> instantiate a dedicated Linux kernel with BusyBox to run the Linux commands. 
>> This is not bringing up a full Linux installation in a VM - this is only the 
>> kernel + BusyBox. So that keeps it small.
>>
>> Now, what would you *do* with this? Why would you need DSL under FreeDOS? 
>> I'm not sure. But it's a neat idea that is well done. Good job!
>>
>> On Wed, Sep 23, 2020 at 10:41 AM Louis Santillan  wrote:
>>
>>> The author freely admits running DOS & Linux side-by-side this way is
>>> a fragile coordination [0]. I doubt that redirection would work as
>>> one might desire. The recently updated ascii demo [1] shows calling
>>> various DOS and Linux commands, and, shows creating a text file with
>>> `dsl vi hello.txt` and then later opening that same file with `edit
>>> hello.txt`. Interestingly, the file appears written to the filesystem
>>> as `HELLO.TXT`, as MS-DOS 6.22 is case insensitive (w/o a LFN driver).
>>> I wonder what would happen if an LFN driver was added to the mix.
>>>
>>> [0] https://news.ycombinator.com/item?id=24556801
>>> [1] 
>>> https://camo.githubusercontent.com/deb8f6b6cc59686ba91a3758daeb047fccdf05dd/68747470733a2f2f636861726c69652e73752f7265636f7264696e672d61633565396166353936613931382e676966
>>>
>>> On Wed, Sep 23, 2020 at 4:39 AM Eric Auer  wrote:


 Hi everybody,

 I would predict doslinux to be a variant of a Linux loader,
 so my questions here are: Can Linux safely write to the DOS
 partition while running? What are the limitations to return
 to DOS after using Linux? Is it possible to switch between
 DOS and Linux without having to reboot Linux each time? Are
 direct interactions possible, e.g. run single apps and pipe
 their output from Linux to DOS or from DOS to Linux?

 As Jim writes about modifications to make doslinux work with
 FreeDOS, it can probably do more than just load Linux, but I
 would be happy to read more about the details here on the list.

 Thanks :-) Eric



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Lightning talk at State of the Source summit

[Mercury Thirteen via Freedos-user]

I signed in then ended up having to run out on a surprise errand, so sadly I 
already missed your segment. Maybe next time... :)

Thanks for the heads-up though!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, September 9, 2020 3:32 PM, Jim Hall  wrote:

> Hi everyone!
>
> If you're online as I send this, you might like to know I'm doing a Lightning 
> Talk at the OSI's State of the Source summit - in just a few minutes. It's 
> free to join!
>
>> LIGHTNING TALKS
>> Jomar Silva, Javier Perez, Christina Hupy, Stephen Jacobs, Alyssa Wright, 
>> Robert Jacobi, Jim Hall, Deb Goodkin, Brian Douglas
>> Red Hat Room - https://osi.gl.blindsidenetworks.com/ope-avy-2t4
>> Access Code: 299867
>
> If you’re free, hop on in!___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] A few suggestions to improve debug

[Mercury Thirteen via Freedos-user]

4. Ctrl + Arrow should skip a word at a time, as in most modern text editors.


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, August 31, 2020 1:44 PM, ZB  wrote:

> 1.  I believe it would be handy if it could immediately after its start
> perform 'r' (show registers' contents). Usually we're going to have
> a look at that first when using "debug". Even if we aren't - having
> these two lines on the screen immediately after start won't do any harm.
>
> 2.  It could keep "history" for last, say. twenty-thirty command-line entries
> (available as usual with Up/Down keys).
>
> 3.  Its command line should recognize "movement keys" just like command.com
> does, I mean Home/End should move cursor to beginning and end current
> entry, Left/Right also for movement (presently Right does just "latest
> entry" while Left is redundant "Backspace" copy) and Del should "eat"
> characters "right from the cursor" (the usual "Del way").
>
> Just basic stuff. Actually I believe that EVERY utility that offers 
> command
> line entry should act like I described in points 2 and 3. Why not use 
> these
> keys we have present on every PC keyboard - for easier and faster editing?
> --
> regards,
> Zbigniew
>
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Open source thoughts about my DOS stuff

[Mercury Thirteen via Freedos-user]

On Thursday, August 27, 2020 4:56 AM, Eric Auer e.a...@jpberlin.de wrote:

> ...
> Mercury, I thought bitbucket was a relatively unstructured place to "just 
> upload files"?
> ...

According to 
[this](https://bitbucket.org/product/guides/getting-started/overview), it seems 
pretty GitHub-by. :)___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Open source thoughts about my DOS stuff

[Mercury Thirteen via Freedos-user]

BitBucket is another option. I haven't used it personally but I believe Maarten 
has, so he is better suited to answer any questions which may arise about how 
it differs from GitHub.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, August 27, 2020 12:03 AM, Jim Hall  wrote:

> I don't know of any source code client like git or svn for DOS or FreeDOS. 
> But I haven't looked recently.
>
> My recommendation is to put it on GitHub. I used to have a GitHub, but I 
> never used it, so I deleted my account. But now that I have new project stuff 
> that I want to keep working on and collaborate on, I'm planning to create a 
> new GitHub account and put my stuff there.
>
> I like the ability to organize your stuff a little easier on GitHub, compared 
> to Sourceforge. I like the svn repo on Sourceforge and I have stuff hosted 
> there, but I'm thinking my newer, bigger stuff will probably go on GitHub.
>
> To migrate, I recommend doing it a bit at a time. Take an afternoon and just 
> focus on one project. Migrate the code, commit, label, verify - then migrate 
> the next version, repeat. Then spend a different day/afternoon to focus on 
> another project, until you're done.
>
> Jim
>
> On Wed, Aug 26, 2020, 2:22 PM Eric Auer  wrote:
>
>> Hi everybody!
>>
>> I had a thought about my more or LESS working website
>> which has all those ZIPs of freedos and other packages:
>>
>> It would probably be more modern and not require any
>> website on my own to put all that on one of those modern
>> portals where people can browse sources and fetch and
>> submit changes, right?
>>
>> How compatible are such websites with DOS binaries? Do
>> they have the possibility to do automated compiles for
>> users of source versions selected by the users etc.? I
>> do not intend to port anything to a new compiler, just
>> asking :-)
>>
>> Which website of that type do you people recommend?
>>
>> And would anybody feel like grabbing my zips, throwing
>> all the contens on such a site and then give me a sign
>> so I can open some type of virtual inbox in case people
>> have feedback about any of the packages now provided
>> as dusty static zips?
>>
>> If you think this is a sign of me being very lazy: That
>> might be true. But on the other hand, it is also an offer
>> to provide support in a more modern way as soon as some
>> "time donor" has put the files on the platform for me :-)
>>
>> See https://auersoft.eu/soft/ for the pile of zips here.
>> They are not that many PACKAGES, but often many VERSIONS.
>>
>> https://auersoft.eu/soft/ those obviously are not BY me
>> at all, but many zips are versions that I HAVE patched.
>>
>> https://auersoft.eu/soft/specials/ those tend to be by
>> me, but too off-topic to be close to the distro. Still:
>>
>> Fdshield, moresys, runtime, metakern and some smaller
>> tools for use with installer scripts may have crossed
>> your paths already :-)
>>
>> https://auersoft.eu/soft/specials/ features a single 2.88
>> MB floppy image version of an old DOS distro by Rugxulo,
>> pcisleep (which also does LSPCI stuff), a pre-compiled
>> German freecom command.com, getargs for MEMDISK and some
>> other obscure things. Even some old ctmouse test area.
>>
>> As you see, everything there is at least 10 years old.
>> Yet I think there are quite a few useful packages :-)
>>
>> Let me know that you think... Thank you!
>>
>> Regards, Eric
>>
>> PS: Maybe I should have used freedos-devel, but I think
>> there are more people on -user and you do not need to be
>> a devel to feel like helping by uploading or commenting.
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Happy Camper

[Mercury Thirteen via Freedos-user]

Nice work. Go, man, go!


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, August 11, 2020 4:56 PM, Jerome Shidel  wrote:

> Hi All,
>
> Today was a pretty fun day…
>
> After a few hours in CAD, some time 3D-printing, soldering, making a label 
> and what not... Today, I manufactured a brand new battery for my 486 
> notebook. Works like a champ. Hopefully, it remedies a couple minor issues. I 
> think the completely dead battery OEM battery was causing those.
>
> Oh, also threw together a internal audio amplifier in the docking station. 
> This allows me to use the Sound Blaster AWE64 Gold sound card without 
> external speakers and just to run a audio patch cable from the card back to 
> the docking station's speaker input jacks. The card has no on-board amplifier 
> and cannot drive speakers directly. TDK DVD Writer works (at least as a 
> CD-ROM) and can even play music CDs. Although, I must say that none of the 
> FreeDOS CD/DVD drivers work with this drive. I was able to find drivers for 
> the 10/100MB NIC. So, all the hardware is working.
>
> !!! ETHERDFS works great for moving stuff to and from the Notebook. Thanks 
> Mateusz. !!! :-)
> (FYI, works in PC-DOS too. Haven’t tried it in MS-DOS or DR-DOS… Yet.)
>
> Getting the DVD drive working was the hardest part. Too make a long story 
> shorter… The main problem was getting the VLB Super I/O board to talk to it. 
> Decades ago, I just used the CD controller on a Sound Blaster Card instead of 
> the I/O board. I no longer have that card and needed to use the I/O board. 
> Well, it is configured through jumpers (about 16 of them). I no longer have 
> the manual and hours searching the internet found nothing. So, through trial 
> and error got it good enough.
>
> They really don’t make ’um like they used too. This docking station is 
> something else. I forgot how it turned this notebook into a more than capable 
> desktop. It’s got 2 ISA and 2 VLB expansion slots. I’ve got that DVD drive in 
> there. But, it also has room, mounts and power for 2 more full sized hard 
> drives. But, I gave up on getting either the 40GB or 60GB IDE drives I have 
> to work in it.
>
> For those who are interested, as it sits right now, this is how the 
> notebook+docking station is configured…
>
> (I’m so glad I had imaged all my old software and driver diskettes)
>
> ACom Vesa-4000 Notebook (no longer in business)
> 486DX2-66Mhz w/12mb RAM, 524mb Seagate Hard Drive
> 9.5” Active Matrix LCD Display
> 2-button Trackball (non-functional, COM2, maybe dead)
> Logitech ClearCase Mouse (COM1)
> Sound Blaster AWE64 Gold w/12mb RAM
> WinBond DC-280E VLB Super I/O Board
> 3COM 509B 10/100 NIC
> Internal 3W+3W stereo amplifier & 2” speakers.
> TDK DVD-RW Drive.
> 3.5” Floppy Drive
>
> 2 x Type 2 PCMCIA Slots (aka: 1 x Type 3 PCMCIA)
> 2 x VGA (one at a time, up to 1024x768)
> 3 x COM (1,3,4) (another on notebook, but inaccessible when docked)
> 2 x LPT (another on notebook, but inaccessible when docked)
> 2 x GAME
> 1 x SCSI
> 1 x PS/2 (another on notebook, but inaccessible when docked)
>
> PCMCIA Type 2:
> DSI Scout 28,800bps Fax/Modem (Working)
> EXP 14,400bps Fax/Modem (unknown state)
> Maxtor MobileMax 4MB Flash Memory Card (not working, possible config issue or 
> dead)
>
> OS:
> MS-DOS 6.22 (Works)
> PC-DOS 7.1 (Works better)
> FreeDOS 1.3-RC3 (Works best, except with Windows 3.11)
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Save the date : FreeDOS virtual get-together

[Mercury Thirteen via Freedos-user]

Sounds good. Looking forward to it! :D

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Friday, August 7, 2020 3:46 PM, Jim Hall  wrote:

> Hi everyone!
>
> I really enjoyed the last FreeDOS virtual get-together on June 29. I finally 
> got to meet many of you - we've exchanged emails and worked online together 
> all these years, and that was the first time I got to meet you.
>
> Let's do another get-together! Save the date for Sunday, August 16 11am-noon 
> (UTC-5, US/Central). [You can use your favorite time zone converter to find 
> the time where you are.]
>
> Our June 29 meeting was a social gathering, so we let conversation cross many 
> topics. I'd like this next meeting to be focused on FreeDOS. This is a great 
> time to compare notes on any projects or programs you're working on.
>
> Watch the website on August 16 at 11am (UTC-5) for a link to the video 
> meeting on BlueJeans. The meeting can support up to 75 people, but only 16 or 
> 17 people joined last time.
>
> Jim___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Benchmark volunteers wanted

[Mercury Thirteen via Freedos-user]

That's something I could do... as long as nobody minds the delay incurred by my 
packed schedule lol

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, July 12, 2020 4:12 PM, Eric Auer e.a...@jpberlin.de wrote:

> Hi DOS users :-)
> As FreeDOS has the reputation of having slow disk I/O,
> I would like to get that quantified a bit... So if you
> have not only FreeDOS but also other DOS brands on your
> computers and can run the same tests on different DOS
> versions on the same hardware, I would like to get in
> touch with you :-)
> Thank you! Eric
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOS Software Catalog? Open sourcing DOS Apps?

[Mercury Thirteen via Freedos-user]

I think Chelson Aitcheson was working on something like this called DOSLife... 
but perhaps I misremember what the project was all about.

Chelson, if you see this, feel free to jump in and enlighten me! :)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, June 20, 2020 4:38 PM, Robert Riebisch r...@bttr-software.de wrote:

> Hi Martin,
>
>> I had been contacting OS/2 developers that no longer support their software
>> and asked them to open source their software. Sometime I have luck,
>> sometimes not, but I have been consolidating the source code on Github for
>> some years now.
>> https://github.com/os2world
>
> I did similar for some DOS software, but didn't create a collection.
> I think, it must have been around 10 to 20 titles, mostly small tools, IIRC.
>
>> - I was wondering if in the DOS or FreeDOS community had been any similar
>> effort.
>
> I don't know about anything coordinated.
>
>> - I also want to know if there some sites or a general community site like
>> a wiki with a catalog of open source, close source, new, old DOS software.
>
> None that I know of.
>
>> I know there are several sites of DOS games, but it seem there are no much
>> sites that their goal is to have the DOS applications catalog.
>
> Expect it to be a tremendously comprehensive task for years.
>
>> For example I have one created for but OS/2 on a MediaWiki
>> (https://www.os2world.com/wiki/index.php/Category:Software)
>
> Looks impressive.
> I already thought about something like that several month ago, but still
> didn't start, because I still didn't define the scope:
>
> - I wanted to start with the shareware archives, e.g., SimTel.Net.
> - I had the idea of creating it in German language only, because that's
> my native language.
> So far, I just setup an empty PmWiki installation. (In contrast to
> MediaWiki, PmWiki needs no database. It stores anything in text files.)
>
>> My interest is OS/2 but I want to know if there are some similar efforts on
>> the DOS community to see if we can join some efforts.
>
> Would be nice, but as of today nobody else seems to care.
> But maybe I'll start it anyway.
> Cheers,
> Robert
> ---
>
> +++ BTTR Software +++
>  Home page: https://www.bttr-software.de/
>
> DOS ain't dead: https://www.bttr-software.de/forum/
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] C: location

[Mercury Thirteen via Freedos-user]

To make sure I'm on the same page with you, you have two video cards in your 
Mac - the stock Radeon HD 5770 that this model ships with, and the the RX580 
you added in, yes? And upon boot, the Mac only shows the boot select screen on 
the built-in card and not the RX580, and you concluded it was doing this 
because of a firmware issue on the RX580?

Assuming all that is correct, then I assume normally when the Mac Pro boots 
(can't say for sure since I don't have one, let alone one with two video cards 
lol) the boot screen appears on the main card because that's what the Mac's EFI 
BIOS is configured to do, and if that's the case there are two possible 
scenarios:

1) The EFI is set to only display on that specific model (or possibly even 
serial! You know how Apple is with their hardware lol) of video card, and won't 
display it on any other (so you're out of luck)

2) The EFI only displays these options on what it sees as the "first" video 
card, in which case removing the factory one altogether (or swapping their 
order) might do the trick.

I would assume scenario 2 is most likely the case, so I would try removing the 
factory card altogether and see what happens. If there's any EFI interface you 
can access, you could try looking for an option for this as well. Maybe it's as 
simple as changing a setting.

Regardless, I don't think VMWare will allow enough direct access to the 
firmware on any device in the Mac for that method to work. You'll have to boot 
from CD to update firmware if it does turn out to be necessary to do so.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, April 2, 2020 1:30 PM, RJ Givens drummerguyservi...@gmail.com 
wrote:

>> On Apr 2, 2020, at 10:16 AM, Eric Auer e.a...@jpberlin.de wrote:
>> Hi! Some ideas regarding the possibility to use native
>> Mac tools for your RX580 graphics card BIOS update task:
>> http://blog.greggant.com/posts/2018/05/07/definitive-mac-pro-upgrade-guide.html#efi-flashable
>> https://www.reddit.com/r/macpro/comments/al3kk2/flash_rx_580_to_show_boot_screen/
>> Apparently ATI / AMD is not very helpful, but
>> maybe you get some ideas from those forums :-)
>
> I’ll check those out.
>
>>> There is no boot screen with the rx580, which is why
>>> I need to flash the firmware on it.
>>
>> Why do you need a boot screen? That sounds like
>> some very low priority moment to have graphics?
>
> I need the boot screen to be able to boot from the Freedos Disk, otherwise 
> the computer will boot directly into the startup disk.
>
>>> I got freedos to boot from the disk, and got ATIFlash
>>> running, but it’s only seeing the original card.
>>
>> Does that mean you booted FreeDOS on the raw
>> hardware of the Mac? How have you managed to
>> do that? And what does original card mean, do
>> you have TWO graphics cards? Why not remove
>> the non-ATI while you do that BIOS update??
>> And actually why is having a boot screen on
>> the non-ATI card not sufficient for you? ;-)
>
> I booted to Freedos via an CD. Have to access the bootable cd via the boot 
> screen by holding down the option key on start up. If you don’t hold down the 
> option key, it just boots into which ever OS is set as your startup disk.
> Yes , I have 2 graphics cards, the stock ATI card that came with the Mac Pro, 
> and rx580. The goal
> Is to remove the stock ATI card, but I need the boot screen to access the 
> bootable cd. I haven’t found a way to execute the bootable cd from within 
> MacOS or Windows.
> They are both ATI card. I swap between Mac OS and windows often and having 
> the boot screen is the easiest way to do so. The RX580 stock does not have 
> the boot screen EFI, which is why I am trying to flash it to do so.
>
>> In case you prefer another language then English
>> and this is why your mails often feature extremely
>> short descriptions of the situation: Please write
>> in your native language, by exception. There are
>> people speaking various languages on this list so
>> you may be understood better than in English :-)
>> Thank you! Regards, Eric
>
> I think I’ve been pretty clear about what’s going on. Thanks for assuming 
> English is my second language.
>
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] C: location

[Mercury Thirteen via Freedos-user]

Basically that's because Mac OS contains a hardware abstraction layer which 
separates the updater you're trying to run (and VMWare itself, for that matter) 
from the actual hardware you're running. It would be best to add the files 
you're tying to use to a bootable FreeDOS CD, then boot from that to flash the 
firmware. In that manner the main OS will not be standing gatekeeper and 
blocking your path.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, April 1, 2020 2:25 AM, RJ Givens drummerguyservi...@gmail.com 
wrote:

> I figured that part out. Now my issue is ATIFLASH says there is no card 
> detected.
> Any insight on that?
>
>> On Mar 31, 2020, at 11:23 PM, Felix G. constantlyvaria...@gmail.com wrote:
>> Hi!
>> The C: drive does not map directly to a folder on your host machine.
>> What I would suggest, because it worked great for me, is that you
>> create an ISO image containing your files then mount that to your VM
>> as a CD ROM.
>> Note that files you copy off of CD ROM in the DOS context will have
>> the read-only attribute set, which may need to be removed with attrib
>> for some applications.
>> Hope this helps.
>> Best,
>> Felix
>>
>>> Am Mi., 1. Apr. 2020 um 00:25 Uhr schrieb RJ Givens
>>> drummerguyservi...@gmail.com:
>>> I’ve just installed Freedos 1.2 in VMWare on OSX. Does anyone know where I 
>>> might be able to find the c: drive location?
>>> I need to flash a bios on my video card and need to drop some files in the 
>>> FreeDos C:
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] UIDE versus UHDD in freedos 1.2 - and 1.3

[Mercury Thirteen via Freedos-user]

On Saturday, March 28, 2020 6:34 AM, Eric Auer e.a...@jpberlin.de wrote:

> Hi Mercury, some short answers :-)
> I think dates as version numbers are fine when there is no explicit version 
> numbering. I would use the date of the most recent file, leave the decision 
> to you whether that means the version is this week since YOU yourself have 
> made per-driver excerpts of the readmes. Otherwise, use the newest timestamp 
> of the original files, even in situations where only documentation updates 
> took place.

Personally, I would like to assign a new version date to my packages since I've 
made some significant changes... however, I think that also would cause 
unnecessary confusion to existing users of these programs. E.g. "Sweet, a new 
version! Oh, wait... this is the same binary I already had. :(( " So I guess 
I'll leave the versions as-is.

> Regarding sources, please always use source\NAME\FILE.EXT naming. It is no 
> problem to have separate copies of CC in source\uide\cc.asm and 
> source\uhdd\cc.asm when installed. There is an official howto for the 
> directory tree etc. in ZIP files for install friendly packages, somewhere 
> online.

Yep, I think the place to which you're referring is 
[here](http://wiki.freedos.org/wiki/index.php/Package), a page I already knew 
about. Had I just read a little further, I would have seen the answer to this 
problem! lol

> Having two himemx variants to compare sounds like Japheth hopes to get MANY 
> TESTERS so a new update can consolidate into one version again? Or maybe a 
> command line option to pick one of the two styles now represented by two exes?

I think it's to give users a choice, depending on their needs. He mentions they 
both employ a different strategy of allocating blocks - perhaps one is 
First-Fit and another is Best-Fit - and each strategy would work better for 
different users. So he gave them a choice. But Idk, that's just my take on it. 
:)

> I suggest that you give Jerome a signal when you think the packages on your 
> website have been updated to fix all items mentioned by him and fully fdinst 
> / fdnpkg compatible :-)

Will do. Hopefully by the end of the day!

> Thank you for your help! Regards, Eric

No problem. Glad to help!___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] UIDE versus UHDD in freedos 1.2 - and 1.3

[Mercury Thirteen via Freedos-user]

Hi Jerome, Eric!

On Friday, March 27, 2020 1:16 PM, Jerome Shidel jer...@shidel.net wrote:

> Hi Eric,
> I took a quick look.
> There is some minor confusion and package issues and they cannot be replace 
> the current packages “AS-IS”.
> At a glance…
> Are they all newer than the ones already in the repo?

Since the author did not assign explicit version numbers, I had been generating 
version numbers based on the date of the most recent modification in the change 
log section of the readme file. However, since some changes were to the 
documentation only and did not affect the code, this resulted in a newer 
version number than the existing package despite the included binary being 
identical. I had listed the "makeshift" versions on my site, but not to the 
individual LSM files in hopes I could dig up some "real" final version numbers 
somewhere. These issues have all been fixed in the versions I uploaded today - 
all versions listed are pulled directly from the binaries themselves, the LSM 
files have been modified accordingly, and I also updated the descriptions of 
the packages to further indicate the differences between my packages and any 
existing ones on the ibiblio list.

> For example…, RDISK shows no version in package, web page says 2011-04-25. 
> Repo version is 2015-03-05.

Can one of you point me to the existing RDisk package (and XMgr too, if one 
exists)? I only found SRDisk on the ibiblio list.

> HIMEMX contains two EXE versions? Why?

According to the readme: "Currently there are 2 versions of HimemX supplied, 
HimemX and HimemX2. HimemX2 uses a different strategy when it comes to extended 
memory block allocations."

> Where is the License file that was in previous versions?

Japheth no longer includes it, instead he added a License section to the readme 
file.

> All packages extract sources to the SOURCE path. This is a problem if the 
> user selects install sources. For example, both UHDD and UIDE contain a 
> SOURCE\CC.ASM file. This will collide and cause package installation to fail 
> with FDNPKG and FDINST.

I see that could be problematic, even if they are the same file. I could 
separate CC into its own package, perhaps. Any thoughts from you guys on 
whether or not that's an appropriate way to handle this issue?

> Some other docs seem to be missing. Like UIDE\UIDE.TXT. (may no longer be 
> needed, IDK)

This file was not included in the driver pack from which I split off the 
individual packages, but the existing readme has its own collection of 
technical notes. From that I conclude it no longer applies to the current 
version.

> Unfortunately, I don’t have the spare time to dedicate to carefully go over, 
> verify and adjust them at present.

No problem, I understand how time-consuming this can be!___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] WinWorldPC disk images...

[Mercury Thirteen via Freedos-user]

Do you know if they are literally one single disk image simply split into 
pieces? If so, there are file joining programs to perform this function.

Come to think of it, most un-archivers can reassemble the split files into one, 
but it depends on how the file was split in the first place.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, March 26, 2020 11:12 AM,  wrote:

> I'm on a CentOS 7 system. I downloaded a rar archive of Wordperfect 6.0 dos 
> that is an archive of floppy images. I do not at this time have real floppy
> support... but I do have zip disks. Is there a way I can mount these images 
> and create one larger image?___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Shared Folders on FreeDOS 1.3 rc2 VirtualBox in the Lubuntu ... problems

[Mercury Thirteen via Freedos-user]

Hi Everaldo!

Since Oracle did not include a DOS driver in the Guest Additions image, the 
Shared Folders feature of VirtualBox does not work on FreeDOS - or even on 
MS-DOS, for that matter. I looked into creating such a driver once, but 
browsing the documentation and source code of VirtualBox itself, is became 
apparent that the callback functions they make available to the host OS are 
using 32/64 bit code and therefore are not easily implemented in a 16-bit SO 
such as DOS without getting into all manner of CPU mode switching ugliness.

If only the case were different! I'd love to be able to exchange files between 
my FreeDOS virtual machine and my host OS without using FTP. :)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, March 25, 2020 2:50 PM, Everaldo Bernardo Cunha 
arcanjo...@gmail.com wrote:

> Hello, friends!
> I don't get to configure "Shared Folders" after to have installed the
> FreeDOS 1.3 rc2 on VirtualBox from Lubuntu 16.04. I did the step by
> step, but when I installed the package "Guest Additions for VirtualBox",
> unconfigured the network and I don't have more access to the Internet
> for the FreeDOS ... So, how will I proceed? Is There some tutorial
> Is there some explanation you know? I'll await your answers.
> Everaldo
> P.S.: after unconfigured the network, I have to install FreeDOS again,
> because I tried to do it work, but I don't got ...
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS wishlist and feature requests

[Mercury Thirteen via Freedos-user]

I think I see what happened here.

Back when Eric originally posted that here was a new version, I built it and 
posted it here. Today, I assumed (mistakenly) the author had made no changes in 
the mean time, so I downloaded his current source and packaged it with the 
binary I built a week (or whatever) ago. Oops.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 23, 2020 5:06 PM, Mateusz Viste mate...@viste.fr wrote:

> On 23/03/2020 21:47, Mercury Thirteen via Freedos-user wrote:
>
>> I noticed that, but the driver itself reports it is 3.34.
>
> In the source code I have seen "3.35", though:
> VERSIONSTR equ <'3.35'>
> DRIVER_VER equ 300h+35
>
>> have two 3.34 versions: one from 2015 and one from 2020. The new 2020
>> version should have been bumped to 3.35, but it was kept at 3.34 for
>> some reason.
>
> Probably because Japheth did not work on the 2015 version, but forked
> off an older version, meaning his version is not an incremental update
> of the 2015 3.34... So there are effectively two different branches now.
> Mateusz
>
>> ‐‐‐ Original Message ‐‐‐
>> On Monday, March 23, 2020 4:40 PM, Mateusz Viste mate...@viste.fr
>> mailto:mate...@viste.fr wrote:
>>
>> On 23/03/2020 21:30, Mercury Thirteen via Freedos-user wrote:
>>
>> Also, the packaged version of HIMEMX is done and can be found here
>> http://mercurycoding.com/downloads/DOS/HIMEMX.zip. Hopefully I
>> didn't
>> miss anything!
>>
>> There is a version mismatch between the lsm (3.34) and the actual driver
>> (3.35).
>> Mateusz
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> <mailto:Freedos-user@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS wishlist and feature requests

[Mercury Thirteen via Freedos-user]

I noticed that, but the driver itself reports it is 3.34. Basically we have two 
3.34 versions: one from 2015 and one from 2020. The new 2020 version should 
have been bumped to 3.35, but it was kept at 3.34 for some reason. Yay, 
clarity! lol

It seems the 3.35 version mentioned in readme.txt hasn't been released yet.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 23, 2020 4:40 PM, Mateusz Viste mate...@viste.fr wrote:

> On 23/03/2020 21:30, Mercury Thirteen via Freedos-user wrote:
>
>> Also, the packaged version of HIMEMX is done and can be found here
>> http://mercurycoding.com/downloads/DOS/HIMEMX.zip. Hopefully I didn't
>> miss anything!
>
> There is a version mismatch between the lsm (3.34) and the actual driver
> (3.35).
> Mateusz
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS wishlist and feature requests

[Mercury Thirteen via Freedos-user]

Thank you! This explains why my searching got me nowhere lol

Also, the packaged version of HIMEMX is done and can be found 
[here](http://mercurycoding.com/downloads/DOS/HIMEMX.zip). Hopefully I didn't 
miss anything!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 23, 2020 4:21 PM, Eric Auer e.a...@jpberlin.de wrote:

> Hi Mercury,
>
>> Where would one find the most recent UHDD sources?
>
> They can be found in
>
>> ftp://ftp.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/cdrom/uide/drivers-2019-03-31.zip
>
> which alas is a VERY generic name to google for...
> The zip contains:
> readme.txt, uhdd.asm and uhdd sys 2019-04-02
> cc, rdisk, rdiskon, udvd2, uide,
> xmgr all asm & sys 2015-03-05.
> As far as I remember, a 2017-10-30 update of xmgr
> should be available - somewhere else on ibiblio.
> Also, separate uide and udvd2 packages should be
> in the FreeDOS 1.3 repositories already, but have
> a look whether they are up to date.
> udvd2 is a driver for SATA and ATAPI CD/DVD drives
> uhdd is a disk cache and UDMA driver
> uide combines basic features of udvd2 and uhdd for
> those who want to create very small boot disks.
> rdisk is a FAT16 ramdisk (2 MB to 2 GB size)
> xmgr is a himem style memory manager
> Unlike most CD/DVD drivers which need special CD
> caches such as cdrcache, udvd2 can automatically
> use the cache provided by uhdd if both are used.
> Note that the readme describes ALL drivers, so you
> could put copies in each package. Having separate
> packages helps users to find and install individual
> components, whereas the "drivers.zip" is something
> only insiders would suspect to contain all this ;-)
> Regards, Eric
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS wishlist and feature requests

[Mercury Thirteen via Freedos-user]

Where would one find the most recent UHDD sources?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 23, 2020 2:33 PM, Eric Auer e.a...@jpberlin.de wrote:

> Hi Mercury,
>
>> "Creating packages for FreeDOS software that are not packaged yet."
>> ... any "top requests" as it were?
>
> If you ask me: UHDD (only UIDE and UDVD2 listed yet?) and the
> new HIMEMX version by Japheth, as discussed here recently :-)
> HIMEMX should get some tests in particular by users of either
> ancient or very modern computers and that would get easier if
> a package would be available :-) Background: Japheth has added
> his own advanced parsing for int 15.e820 results (different
> from the old Pemberton fork) and uses a special sequence of
> "mov cr0,eax; jz $ + 2", maybe for CPU compatibility reasons.
> Japheth drops int 15.8a calls: Very few old computers worked
> better with those calls, but the Pemberton fork failed to do
> sufficient checks whether the call actually is supported, so
> that forked version was worse for various modern computers.
> Thank you :-) Eric
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS wishlist and feature requests

[Mercury Thirteen via Freedos-user]

Cool, thanks for the info!

Not that I'm promising anything given my schedule, but maybe I'll be able to 
throw something together in my limited spare time. Shouldn't be too hard to get 
the others together since I already built HIMEMX from Japheth's new sources.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 23, 2020 2:33 PM, Eric Auer e.a...@jpberlin.de wrote:

> Hi Mercury,
>
>> "Creating packages for FreeDOS software that are not packaged yet."
>> ... any "top requests" as it were?
>
> If you ask me: UHDD (only UIDE and UDVD2 listed yet?) and the
> new HIMEMX version by Japheth, as discussed here recently :-)
> HIMEMX should get some tests in particular by users of either
> ancient or very modern computers and that would get easier if
> a package would be available :-) Background: Japheth has added
> his own advanced parsing for int 15.e820 results (different
> from the old Pemberton fork) and uses a special sequence of
> "mov cr0,eax; jz $ + 2", maybe for CPU compatibility reasons.
> Japheth drops int 15.8a calls: Very few old computers worked
> better with those calls, but the Pemberton fork failed to do
> sufficient checks whether the call actually is supported, so
> that forked version was worse for various modern computers.
> Thank you :-) Eric
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS wishlist and feature requests

[Mercury Thirteen via Freedos-user]

Point #2 on the wishlist states:

"Creating packages for FreeDOS software that are not packaged yet."

Do we have a list of this software, partial or otherwise? Or any "top requests" 
as it were?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Monday, March 23, 2020 9:31 AM, Eric Auer e.a...@jpberlin.de wrote:

> Hi everybody, it seems that
> https://sourceforge.net/p/freedos/feature-requests/
> has not been updated for a while: A few wishes seem
> to no longer apply or would be easy to cover with
> current distros.
> On the other hand, the wishlist still is a classic ;-)
>
>> http://wiki.freedos.org/wiki/index.php/(Free)DOS_development_wishlist
>
> Regards, Eric
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Introducing myself, and inquiring about using FreeD OS as a blind user

[Mercury Thirteen via Freedos-user]

I may as well jump on the bandwagon here... :D

I find VirtualBox quite easy to set up; most things just work out-of-the box, 
whatever the OS you install upon it, and its simple GUI allows even things 
which do need a bit of configuration to be handled in a fairly straightforward 
manner.

Also - although it does not allow native disk access as you described VMWare 
does - its uncompressed .VDI files can be mounted (under Linux, at least) and 
accessed directly from the desktop without any intervention from VirtualBox 
itself or the VM to which it is attached. Or, if one runs Windows instead, 
there is [Arsenal Image 
Mounter](https://github.com/ArsenalRecon/Arsenal-Image-Mounter) which provides 
similar functionality.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 5:20 PM, Bret Johnson  wrote:

> Karen:
>
> Inside a Virtual Machine, ALL hardware is virtualized  to some degree or 
> other -- you never get direct access to the real hardware (whether it's 
> keyboard or mouse or video screen or hard drive or serial port or even the 
> clock).  Exactly what gets virtualized through to the VM and exactly how it 
> gets passed through depends on the VM.  Different VM's do some things better 
> than others.
>
> I've played around a little bit with different VM's (VMWare, Bochs, DOSBox, 
> QEMU, VirtualPC, PCEm, and others).  None of them are very easy to set up. 
> and they all have their limitations and quirks.  At least for my purposes, I 
> still find VMWare to be better than the others even though I still consider 
> it really pretty bad and don't do anything serious with it.  And again, the 
> main problem I have with VMWare is that it does not pass the keyboard though 
> to the VM like it should and the keyboard is VERY critical in DOS (far more 
> critical than the mouse).___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] fresh compile for himemx anybody?

[Mercury Thirteen via Freedos-user]

Here you go...

http://mercurycoding.com/downloads/HiMemX

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, March 12, 2020 1:09 PM, Eric Auer e.a...@jpberlin.de wrote:

> Hi all,
>
>> https://www.bttr-software.de/forum/board_entry.php?id=16187
>
> tells that not only Japheth's JEMM got updated recently, but also
> HIMEMX source codes received an update for improved int 15.e820
> "multiple memory block" support. Unlike the old Pemberton patch
> the update by Japheth does not call int 15.8a in risky ways, so
> I would love to see a binary from Japheth's HIMEMX 3.34 sources.
> Maybe somebody with the right compiler could provide one :-)
> Thank you! Regards, Eric
> PS: Actually Japheth's HIMEMX does not call int 15.8a at all, so
> very few users with really old BIOS might still use Pemberton's.
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos 1.3 and Windows 9x...

[Mercury Thirteen via Freedos-user]

The easiest way to support Windows 9x software would involve evolving FreeDOS 
into the 32-bit era, most likely via a kernel upgrade.

Hmm, I seem to remember there being some little project aiming to do that... lol

But yes, I agree it would be nice to have the option to run some older GUI 
programs under our favorite OS.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, January 5, 2020 8:27 PM,  wrote:

> MS DOS 6.x was not the end of MS-DOS. Windows 9x releases added a strange 
> protected mode, but unlike NT, these versions of Windows still ran on top of 
> MS-DOS.
>
> There is no support for DOS based Windows any longer and the ReactOS project 
> essentially abandoned it. However, there are embedded systems that depend on 
> Windows 9x. It would be great if Windows 9x era software could be supported 
> by something open and more stable. Why not replace the graphical system with 
> FLTK and the WIN32API with a special library or something similar?
>
> Where Windows 9x comes to mind is on systems that use specialty ISA hardware 
> which never got ported to NT. One system in particular used two servers, 
> Windows 9x on one and MS DOS 6.22 on the other. Given time, I would love to 
> substitute Freedos and see what happens. PPM bought out the Tyco system, but 
> the new system is designed around different hardware with different problems 
> and isn't necessarily better. I don't buy the notion that NT is better than 
> DOS based Windows.
> A port of Q-Soft to a combination of FLTK and Freedos is very interesting to 
> me. Theoretically, one can reverse engineer to drive the shared memory card 
> in Freedos.
> Q-Soft is a Windows 32 program, but that could be abstracted out and a 
> different system could be developed that runs in protected mode on top of 
> Freedos.
>
> I think Q-Soft has a vxd internal to it, which is crazy IMHO. There should be 
> a driver in device manager for the ISA shared memory card. The idea of a 
> graphical hardware tree is something that would be nice to have in an open 
> source gui that runs on top of Freedos.
>
> Even an unofficial service pack for 98se that lets you use more memory and 
> modern hardware would be welcome.
>
> Just some thoughts is all.
>
> -- Michael C. Robinson___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Updated FreeDOS website

[Mercury Thirteen via Freedos-user]

Nice work!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, January 5, 2020 7:21 PM, Jim Hall jh...@freedos.org wrote:

> Hi everyone!
> I've been working on an updated FreeDOS website for a while now. And
> today, I've uploaded the new website to https://www.freedos.org/ (same
> as http://www.freedos.org/)
> The website had become difficult for new users to find the information
> they needed. Interest in FreeDOS seems to have picked up a bit lately,
> and I get a fair bit of emails from people who haven't used DOS
> before, but want to try out FreeDOS. They are trying to find this or
> that, and the old website just made it difficult to get to the
> information they needed.
> The new website should be easier to read, easier to navigate, and
> easier to find the information you need right away. It should also
> have better support for mobile web browsers (we get a lot of website
> visitors on phones).
> The big changes you might notice right away:
>
> - Every page that has a specific call to action ("Download this" or
> "Join the email list") now puts that link in an obvious blue "button"
> - The top nav is now reserved for things new users typically want to
> do: read the wiki, join the email lists or forums, report a bug, etc.
> - The download page now breaks up the different download options, so
> it's more clear what you need to download depending on your PC.
> If you find any broken links or dead pages, please email me so I can
> fix it. Thanks!
> Jim
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] anyone here code software?

[Mercury Thirteen via Freedos-user]

As we have been known to say on the Night kernel forum...

"Why? Because FreeDOS. That's why!"

:)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, November 28, 2019 8:27 PM, Karen Lewellen klewel...@shellworld.net 
wrote:

> One of the members over at Dos Ain't dead has a fine tag in their
> signature.
> Dos: the question is not why, but why not.
> On Thu, 28 Nov 2019, Ralf Quint wrote:
>
>> On 11/28/2019 1:45 PM, Karen Lewellen wrote:
>>
>>> I have a professional question, so seek an expert who  codes or develops
>>> software for DOS.  This is not a list topic, so would appreciate
>>> permission to contact whomever writes me off list.
>>
>> I do this on occasion still, after having done this for +15 years when DOS
>> was still THE OS around...\
>> Ralf
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Quick FreeDOS 1.3 Live CD Poll

[Mercury Thirteen via Freedos-user]

No. No, no, no. Just... no.

By the way, I vote 'no' :)

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, November 14, 2019 10:27 AM, Jerome Shidel jer...@shidel.net wrote:

> Hi,
> I’m just looking to do quick poll on you thoughts and opinion.
> When FreeDOS 1.3 is booted as a Live environment from the CD-ROM, should it 
> be permitted access to any internal hard drive(s)?
> Allowing access, can permit reading and writing files and/or installation to 
> the HDD.
> (This will allow installation. partitioning and other operations without a 
> need to reboot out of the Live Environment)
> Preventing access, will prevent any accidental changes to the HDD and provide 
> a very safe playground.
> (This will require rebooting the computer and selecting a different boot 
> option to install.)
> Yes. Prevent access to internal hard drive.
> No. Allow access to internal hard drive.
> :-)
> Thanks, Jerome
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Source code to Windows 9x and ME...

[Mercury Thirteen via Freedos-user]

On Thursday, September 26, 2019 12:07 PM, Jon Brase  wrote:

> ...
> But as someone said upthread, finding someone properly placed to advocate for 
> such a thing internally would likely be very helpful in such an effort.

Perhaps Theodore Ts'o or Ky Srinivasan? According to 
[this](https://www.theregister.co.uk/2019/08/28/microsoft_exfat_spec_linux_kernel),
 they played a part in getting exFAT open sourced.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] can FreeDOS do anything to make up for Virtualbox and VMWare's lack of decent support for DOS sound?

[Mercury Thirteen via Freedos-user]

For those times when VirtualBox doesn't cut it, I use AQEMU, a GUI-based 
frontend for QEMU.

QEMU itself supports SO many options that using it from a command line can be a 
little daunting; AQEMU's GUI approach makes creating/configuring VMs much more 
straightforward IMO.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, September 19, 2019 8:39 AM,  wrote:

> Asking the question a different way.
>
> Is there another virtual app (alternatives to Virtualbox or VMWare) that does 
> a much better job supporting DOS hardware which I can install FreeDOS onto?
>
> That's probably the ultimate solution for those of us not installing FreeDOS 
> on actual hardware, which is a constantly growing base and if not the 
> majority yet, will be soon.
>
> The solutions like DOSBox and 86Box are self-contained virtual hardware/OS 
> solutions but was hoping for an improvement over Virtualbox or VMWare I can 
> install FreeDOS onto.
>
> Steve
>
> On 2019-09-18 20:22, geneb wrote:
>
>> On Wed, 18 Sep 2019, Jim Hall wrote:
>>
>>> On Wed, Sep 18, 2019 at 8:07 AM geneb  wrote:
>>>
 I've found that 86Box is probably the best PC emulator out there.  It's
 basically a PC emulated at the hardware level for a number of different
 motherboard chipsets.  It actually uses original BIOS ROMs and even video
 BIOS ROMs.  You can find it here: https://github.com/86Box/86Box  It's a
 fork of PCem and works wonderfully.  It will emulate pretty much any CPU
 between the 8088 and Pentium MMX.
>>>
>>> Thanks for the link to 86Box. I've added it to our Links page:
>>> https://www.freedos.org/links/
>>
>> You're welcome!
>>
>> g.
>>
>> --
>> Proud owner of F-15C 80-0007
>> http://www.f15sim.com - The only one of its kind.
>> http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
>> Some people collect things for a hobby.  Geeks collect hobbies.
>>
>> ScarletDME - The red hot Data Management Environment
>> A Multi-Value database for the masses, not the classes.
>> http://scarlet.deltasoft.com - Get it _today_!
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] using SoundBlaster 16 DOS sound drivers under Virtualbox

[Mercury Thirteen via Freedos-user]

Even with a driver installed, VirtualBox only emulates DMA-based sound and not 
the I/O port based sound used in some games/programs.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, August 18, 2019 6:09 PM,  wrote:

> Hello,
>
> Virtualbox supports SoundBlaster 16 BUT there is no sound on the game 
> PakuPaku when played.
>
> I didn't really expect sound because even though Virtualbox merely mimics the 
> SB16 hardware, no drivers are installed.
>
> The BLASTER environment variables are there in the FDAUTO.BAT file, but I 
> notice no drivers load in FDCONFIG.SYS so I'm guessing that's because of 
> licensing.
>
> There's a lot of 'junk' secondhand or worse SB16 driver installers out there 
> you can find on various websites, but I'm super picky about where I get my 
> files from.
>
> If I grab SoundBlaster 16 DOS drivers from here (I like getting stuff from 
> the official source as much as possible)...
>
> https://web.archive.org/web/19980213040248/http://www1.creaf.com:80/wwwnew/tech/ftp/ftpinx.html
>
> ...and here...
>
> https://support.creative.com/Products/ProductDetails.aspx?catID=1=207=1842=Sound%20Blaster%2016=Others=
>
> ...and install them, can they be expected to produce sound?
>
> Thanks,
>
> Steve Sybesma___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] How to set up fdconfig.sys and autoexec files for a driver?

[Mercury Thirteen via Freedos-user]

Perhaps [this](https://www.youtube.com/watch?v=e14dFZWi2eI) would be of 
assistance.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, July 18, 2019 7:58 PM, HTV04 .  wrote:

> I searched on Vogons, but I couldn’t find anything on what my problem is, 
> even when searching about my BIOS. I really don’t know what to do here.
>
> On Thu, Jul 18, 2019 at 10:16 AM ZB  wrote:
>
>> On Thu, Jul 18, 2019 at 10:06:14AM -0400, HTV04 . wrote:
>>
>>> I checked pcisleep on my computer and I saw that the ESS SOLO-1 was on port
>>> 10. How do I ???kick??? the SOLO-1 to a different port? I have a most likely
>>> outdated Phoenix BIOS, and I saw nothing about PCI configuration, only I/O
>>> configuration.
>>
>> I believe the best tip can be given by someone who has ESS SOLO-1. When you
>> google for "ESS SOLO-1" you'll see several links - I recommend the ones from
>> "vogons.org". This is gamers' site, and there are guys who already fought
>> such ESS SOLO-1 cards - so probably they have solution ready for application
>> --
>> regards,
>> Zbigniew
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> --
> Sincerely,
> HTV04___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] How to set up fdconfig.sys and autoexec files for a driver?

[Mercury Thirteen via Freedos-user]

IIRC, ESS provided some kind of utility which probed the system to detect the 
configuration of the card and report its findings. Was any such thing included 
in the driver package you downloaded?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, July 17, 2019 10:43 AM, HTV04 .  wrote:

> Just thought I’d make a new thread since the old on was getting long and 
> off-topic anyway.
>
> I’m trying to install an ESS SOLO-1 driver I found here:
> https://www.philscomputerlab.com/ess-es1938s-solo-1.html
>
> I copied the files onto my old computer and put them in the correct places, 
> but I don’t know how to configure fdconfig.sys and autoexec.bat to run the 
> driver.
>
> I know I have to enter this code into fdconfig.sys (config.sys):
> DEVICEHIGH=C:\SOLO1\ESSOLO.SYS
>
> And this code into autoexec.bat:
> LH C:\SOLO1\ESSOLO.COM
> SET BLASTER=A220 D1 I5 T4
> C:\SOLO1\ESSVOL.EXE /v:10 /l:0 /w:10 /m:0 /c:10 /s:10 /a:0 /p:0
>
> Problem is, fdconfig.sys and autoexec.bat seem really complicated, mainly due 
> to the startup menu FreeDOS has. I saw in the autoexec.bat file that certain 
> code loads when the startup option is 2, yet I saw nothing loaded for 1, even 
> though that it supposed to be the most powerful option (I think). This is 
> really confusing. I want to make sure the drivers only load with the options 
> that support it (for example, options 3 and 4 shouldn’t load the drivers 
> because those are safe modes). How do I do this?
> --
> Sincerely,
> HTV04___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Need help reformatting disk for clean install of FreeDOS

[Mercury Thirteen via Freedos-user]

IIRC, you just use FORMAT without the /Q switch.

Sent from ProtonMail mobile

 Original Message 
On Jul 13, 2019, 7:29 PM, HTV04 . wrote:

> Too late for that, haha.
>
> How do I force a full format like the installer would do, though?
>
> On Sat, Jul 13, 2019 at 7:27 PM Dale E Sterner  wrote:
>
>> One thought, you could replace your c: drive with
>> a cf chip from Komputerbay on Amazon. Just
>> pull out the old hard drive and replace it with an
>> IDE adapter and cf chip. You can save your old
>> c: drive so can get back your old system by
>> just plugging it back in, if you ever want 98 back.
>>
>> cheers
>> DS
>>
>> On Sat, 13 Jul 2019 07:19:59 -0400 "HTV04 ." 
>> writes:
>>> I would like to do a clean install of FreeDOS though, and makes sure
>>> the C:
>>> partition is completely wiped by doing a full format on it and
>>> reinstalling
>>> FreeDOS.
>>>
>>> On Sat, Jul 13, 2019 at 7:17 AM Eric Auer 
>>> wrote:
>>>
>>> >
>>> > Hi!
>>> >
>>> > Actually if YOU have no problem with Windows 98 files
>>> > still being on your FreeDOS C: drive, then there is no
>>> > need to format, partition or delete anything. Of course
>>> > you are free to use the normal DOS commands to delete
>>> > those files which you no longer need. You could even
>>> > install a boot manager and make Win98 and DOS available
>>> > as boot time choices, with some additional tricks.
>>> >
>>> > I think Mercury assumed that you had problems booting
>>> > DOS after installing and that you wanted to completely
>>> > get rid of all other operating systems and data on the
>>> > disk, so he gave you the steps for that.
>>> >
>>> > Regards, Eric
>>> >
>>> > > Thanks for advice! I don’t want to mess with my current
>>> partitions
>>> > though.
>>> > > Is there a way I can just format the existing C: partition (with
>>> the
>>> > format
>>> > > command)?
>>> > >
>>> > > And should I do this from the CD-ROM? If so, how?
>>> >
>>> >
>>> > ___
>>> > Freedos-user mailing list
>>> > Freedos-user@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>>> >
>>> --
>>> Sincerely,
>>> HTV04
>>
>> **
>> From Dale Sterner - MS organic chemistry
>> http://pubs.acs.org/doi/abs/10.1021/jo00975a052
>> ***
>>
>> 
>> Drink This Before Bed, Watch Your Body Fat Melt Like Crazy
>> Diet Insider
>> http://thirdpartyoffers.juno.com/TGL3141/5d2a688a67958688a42b2st03duc
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> --
>
> Sincerely,
> HTV04___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Need help reformatting disk for clean install of FreeDOS

[Mercury Thirteen via Freedos-user]

On Saturday, July 13, 2019 7:16 AM, Eric Auer e.a...@jpberlin.de wrote:

> ...
> I think Mercury assumed that you had problems booting
> DOS after installing and that you wanted to completely
> get rid of all other operating systems and data on the
> disk, so he gave you the steps for that.
> ...

Yep, that was exactly my thought process. :)

So to more accurately target what you want to do, I would not delete all 
partitions, but only the one holding drive C. All the other steps should still 
work.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Need help reformatting disk for clean install of FreeDOS

[Mercury Thirteen via Freedos-user]

I would:

1. Run FDISK and delete all partitions
2. Create a single Primary DOS partition and mark it active
3. Exit FDISK and reboot
4. Run FDISK /mbr to fix the boot record
5. Use SYS c: to transfer system files to the hard drive

Then you should be good to go!

Sent from ProtonMail mobile

 Original Message 
On Jul 13, 2019, 2:49 AM, HTV04 . wrote:

> Hi, I’m new to FreeDOS. I wanted to revive my old computer (a Compaq 
> Prosignia 150) that originally had Windows 98, so I set up a CD-ROM with the 
> FreeDOS installer.
>
> When I booted from the CD-ROM, everything seemed to be going smoothly. I had 
> to use the “raw” workaround, though, otherwise I would be given several 
> “Invalid Opcode” errors. This doesn’t have much to do with the problem I’m 
> having though, or at least I don’t think so.
>
> Problems arose when I got a message saying that a previous OS was detected 
> (which was Windows 98), and that I could either continue installing or make a 
> backup. I searched this up online, and found absolutely no documentation on 
> this. I came to the conclusion that it would just format my C: drive and 
> continued. After I started the install however, it just installed all the 
> files alongside my old ones, so the installer completely skipped the part 
> where it would format the drive.
>
> So now I have FreeDOS 1.2 installed, but my Windows 98 files still exist. Is 
> there anyway to replicate the formatting process from the CD-ROM (and can I 
> run the command from the CD-ROM)? If it involves using the format command, 
> can you tell me the exact command the installer uses? I kind of have OCDs for 
> that sort of thing, sorry. I’m looking to do a full format.
>
> I would recommend a change for this in FreeDOS 1.3, to allow clean installs 
> of FreeDOS in place of the operating system currently installed.
>
> Thanks in advance, and I can’t wait to try out FreeDOS on my old computer!
> --
>
> Sincerely,
> HTV04___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Installing with QEMU

[Mercury Thirteen via Freedos-user]

On Saturday, June 15, 2019 12:57 PM, Jim Hall  wrote:

> ...
> Then you boot FreeDOS in QEMU. Note that QEMU takes a ton of command line 
> arguments to define each part of the virtual machine. Here's my command line:
>
> qemu-system-i386 -m 32 -k en-us -rtc base=localtime -soundhw sb16,adlib,pcspk 
> -device cirrus-vga -display gtk -hda freedos.img -cdrom FD12CD.iso -drive 
> file=fat:rw:/home/jhall/dos -boot order=c
> ...

And for those of us who would rather forgo full command lines like that (me) 
there's [AQEMU](https://sourceforge.net/projects/aqemu). :)___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Packet Driver Help

[Mercury Thirteen via Freedos-user]

My first thing would be to try booting without JEMM. There's another (better, 
IMO) Extended Memory driver which doesn't tend to lead to exceptions like JEMM 
does.

Best o' luck to ye!

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Thursday, May 9, 2019 5:52 PM, Martin Collins 
 wrote:

> Hi,
>
> Sorry to email but need a little help please, if someone would be so kind?
>
> I just acquired a £30 Ebay bargain, a good condition Lenovo Thinkpad X100E. 
> Nice little laptop (runs a little hot in Linux) which I've dual booted with 
> FreeDOS 1.2 & Peppermint Linux. I have been trying to get a packet driver 
> working to enable my Ethernet without much success.
>
> NICSCAN.EXE (http://www.georgpotthast.de/sioux/pktdrv/nicscan.zip) & 
> Peppermint report the card as follows:
>
> PCI vendor 10EC, Realtek Semiconductor Co., Ltd.
> PCI vendor 8168, RTL8111/8168B PCI Express Gigabit Ethernet Controller
>
> I tried several packet drivers without success and eventually I appeared to 
> find exactly what I needed when DuckDuckGo led me to this packet driver for 
> DOS: https://support.lenovo.com/lu/en/downloads/ds003425
>
> Which is a DOS Realtek driver for the following Thinkpad models: ThinkPad 
> Edge 13, Edge E30, Edge 14, Edge E40, Edge 15, Edge E50, L412, L512 and X100e
>
> The zip file does not provide an actual packet driver but provides several 
> files to make one. In short if I want the final driver to be called X100E.COM 
> then I run the following commands: RTPATCH.EXE RTEND.DOS RTEND2.TXT 
> X100E.COM. I copy X100E.COM into C:\FDOS\NETWORK and edit 
> C:\FDOS\BIN\FDNET.BAT and add the following couple of blocks of text.
>
> berndpci 10ec8168
> if errorlevel 1 goto x100e
>
> REM ... Downloaded from https://support.lenovo.com/lu/en/downloads/ds003425 
> ...
> :x100e
> X100E.COM
> goto finish
>
> Unfortunately on a reboot I get the following error(s) when X100E.COM is 
> executed.
>
> JemmEx: exception 06 occured at CS:EIP-0386-, ERRC= 
> SS:ESP=0386:0001 EBP=091E EFL=00033202 CR0=8011 CR2= 
> EAX= EBX= ECX=00FF EDX=20490376 ESI= EDI= 
> DS=0376 ES=0376 FS= GS= [CS:IP]=FF FF FF FF 40 C0 B4 8D
>
> So I'm not sure where I can go from here and just wondered if anybody has any 
> ideas or pointers they could give me please? BTW I am also getting Extended 
> Memory errors when running my favourite word processor - Protext.
>
> Thanks everybody!
>
> Best regards,
>
> Martin___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Choosing an interrupt number

[Mercury Thirteen via Freedos-user]

I wrote a program years ago which probes the 16-bit interrupt dispatch table 
under DOS and saves the addresses of all 256 handlers to a file you specify. If 
you like, I can dig up the old VB source. Let me know.


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On August 4, 2018 11:40 AM, David McMackins  wrote:

> I'm wanting to set up a packet driver, but it asks for which packet int
> number to use. From the packet driver specification, I see this is
> supposed to be between 0x60 and 0x80, but how can I tell if any of these
> are already taken?
>
> Happy Hacking,
>
> David E. McMackins II
> Supporting Member, Electronic Frontier Foundation (#2296972)
> Associate Member, Free Software Foundation (#12889)
>
> www.mcmackins.org www.delwink.com
> www.eff.org www.gnu.org www.fsf.org
>
> --
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] virtualbox int 15 memdisk failure - was: Unable to install FreeDOS 1.2 on VirtualBox

[Mercury Thirteen via Freedos-user]

Both "int" and "raw" launch properly, but "bigint" gives the same ol' "Invalid 
Opcode" loop.

VirtualBox doesn't have an explicit setting for AHCI versus IDE, but you can 
get the same effect through what type of storage controller you add to your 
virtual machine; if you want it handled as AHCI, you add a SATA controller, and 
if you want IDE, you add an IDE controller. The VirtualBox BIOS has no "Setup" 
interface of which I'm aware. Boy, I wish it did!


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On July 31, 2018 4:42 AM, Eric Auer  wrote:

> Hi!
>
> > To further isolate the Invalid Opcode issue, I extracted the floppy
> > image (FDBOOT.IMG from the ISOLINUX folder) from the ISO and booted
> > it as a floppy disk in VirtualBox which launched the installer
> > flawlessly.
>
> Thanks for the testing! So apparently NOINVLPG would not have helped.
> How about the memdisk "int" instead of "bigint" or "raw" options?
>
> Does VirtualBox have options to select AHCI versus IDE or to change
> the int 15 memory access styles?
>
> Cheers, Eric
>
>
> ---
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] virtualbox int 15 memdisk failure - was: Unable to install FreeDOS 1.2 on VirtualBox

[Mercury Thirteen via Freedos-user]

So, being a VirtualBox "owner", I did some testing. :)

First, I tested three methods of installing FreeDOS 1.2: FD12CD.iso, 
FD12LGCY.iso, and FLOPPY.IMG from FD12FLOPPY.ZIP. The infinite Invalid Opcode 
loop only occurs for me when booting FD12CD.iso. Oddly enough, booting 
FD12LGCY.iso on VirtualBox gives the message, "Unfortunately, this method of 
installation is not supported on this platform. Please try a different 
installation method.", although you can proceed to run the setup program from 
the prompt and it launches normally. I didn't run the setup through to 
completion since I have stuff on my virtual HD that I don't want to lose, but I 
can test that further with a blank one if it would help. The floppy image from 
the ZIP boots without issue.

To further isolate the Invalid Opcode issue, I extracted the floppy image 
(FDBOOT.IMG from the ISOLINUX folder) from the ISO and booted it as a floppy 
disk in VirtualBox which launched the installer flawlessly. The only difference 
was taking ISOLinux out of the mix, so it seems to me that VirtualBox is doing 
exactly what it should, it's just ISOLinux that isn't happy.

Hope that helps!


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On July 29, 2018 6:56 PM, Eric Auer  wrote:

> Hi Jim, others,
>
> > Mercury Thirteen means this:
>
> > https://sourceforge.net/p/freedos/bugs/212/#1b4c
>
> > I'm not sure why VirtualBox has this problem. I don't recall that we
> > saw this when wen tested the FreeDOS 1.2 distribution, did we? Or
> > did VirtualBox have some regression? I use a different VM, so I don't
> > know.
>
> For those without HTTPS SF compatible DOS browsers or extra time...
>
> Andrew Pennebaker wrote 2018-05-05 about freedos12:
>
> > I am trying to install FreeDOS in a virtual machine using VirtualBox,
> > but a few seconds after I press Enter to begin the installation
> > process, I get an infinite scrolling list of "Invalid Opcode"
> > errors.
>
> > I'm using FreeDOS 1.2, in VirtualBox 5.2.10, in macOS 10.13 High
> > Sierra.
>
> Jim originally suggested to use the /NOINVLPG option for JEMM386 based
> on http://wiki.freedos.org/wiki/index.php/VirtualBox and disabling AHCI
> mode and selecting legacy IDE mode in BIOS setup, but later he wrote:
>
> > An alternative solution I've seen mentioned elsewhere is adding the
> > raw parameter to memdisk in the boot menu.
>
> > When you boot the FreeDOS install CDROM, when you get the get the
> > first "Welcome to FreeDOS 1.2" boot menu, press Tab when you're on
> > "Install to harddisk" and add 'raw' (without quotes) to the kernel
> > command line, then press Enter to boot.
>
> > From this: KERNEL /boot/syslinux/memdisk
>
> > To this: KERNEL /boot/syslinux/memdisk raw
>
> According tohttps://www.syslinux.org/wiki/index.php?title=MEMDISK
>
> that magic "raw" parameter is about memory access and sizing:
>
> https://www.syslinux.org/wiki/index.php?title=MEMDISK#Memory_access_method
>
> > Memory access method
>
> > MEMDISK normally uses the BIOS "INT 15h mover" API to access high
> > memory. This is well-behaved with extended memory managers which load
> > later. Unfortunately, it appears that the "DOS boot disk" from WinME/XP
> > deliberately crash the system when this API is invoked. The following
> > command-line options tell MEMDISK to enter protected mode directly,
> > whenever possible:
>
> > raw Use raw access to protected mode memory.
>
> > bigraw Use raw access to protected mode memory, and leave the
> > CPU in "big real" mode afterwards.
>
> > int Use plain INT 15h access to protected memory. This assumes
> > that anything which hooks INT 15h knows what it is doing.
>
> > safeint Use INT 15h access to protected memory, but invoke
> > INT 15h the way it was before MEMDISK was loaded.
> > This is the default since version 3.73.
>
> So apparently VirtualBox has a problem in the int 15 memory copy API!?
>
> If that is the case, then I would expect HIMEM to have problems as
> well, while EMM386 should have fewer problems as it uses protected
> mode directly in more cases? Or is this just about some special case
> of reentrancy? Related to how both MEMDISK and LBACACHE try to use
> memory beyond 1 MB, one for the disk image, the other for XMS cache?
> In the latter case, LBACACHE should be told to not cache a MEMDISK.
>
> The best solution would probably be to improve the VirtualBox BIOS??
>
> Another idea would be to try the MEMDISK "int" option which respects
> int 15 hooks, because HIMEM probably has to hook int 15 as well and
> the "safeint" default of avoiding new hooks might be exactly wrong?
>
> It would be cool if some VirtualBox owners could do some testing :-)
>
> Thanks! Regards, Eric
>
> PS: Do we know whether NOINVLPG actually helped in THIS situation?
>
>
> 

Re: [Freedos-user] Unable to install FreeDOS 1.2 on VirtualBox

[Mercury Thirteen via Freedos-user]

No problem!

Sent from ProtonMail mobile

 Original Message 
On Jul 29, 2018, 3:34 PM, FabulousKana wrote:

> It worked. Thank you very much.
>
> On 7/29/2018 9:05 PM, Mercury Thirteen via Freedos-user wrote:
>
>> I get this every time I install 1.2 on VirtualBox. Try hitting Tab then add 
>> " raw" after the command shown.
>>
>> Sent from ProtonMail mobile
>>
>>  Original Message 
>> On Jul 29, 2018, 2:07 PM, FabulousKana < fabulousk...@disroot.org> wrote:
>>
>>> Hello,
>>>
>>> I need some help. I am using VirtualBox 5.2.16 on Windows 10. I spotted
>>> that my virtual machine with FreeDOS had some weird corruptions so I
>>> decided to reinstall it.
>>>
>>> After booting the CD (FD12CD.iso), selecting the option "Install to
>>> harddisk" and waiting a little while it starts showing error messages
>>> with "Invalid Opcode". When I skip config.sys/autorun.bat on startup and
>>> run "setup.bat" manually it shows the language selection properly, but
>>> ends up with error "Unable to locate the installation packages. A reboot
>>> may help." If I run autorun.bat instead it shows the error messages
>>> "LBACACHE: XMS error.43ff Not enough free XMS memory." and "Can not set
>>> environment variable '_B'. Environment full?". Everything worked just
>>> fine before updating the VirtualBox. The checksums are appear to be
>>> correct so I don't think that installation iso is broken. Anyone has any
>>> ideas what it could be?
>>>
>>> Thanks in advance.
>>>
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org!
>> http://sdm.link/slashdot
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>>
>> https://lists.sourceforge.net/lists/listinfo/freedos-user--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Unable to install FreeDOS 1.2 on VirtualBox

[Mercury Thirteen via Freedos-user]

VirtualBox does support Fast A20, if that helps.

I know because I use that technique in the Night kernel :)

Sent from ProtonMail mobile

 Original Message 
On Jul 29, 2018, 3:03 PM, Eric Auer wrote:

> Hi!
>
> 256 MB should be plenty, but I do not know
> what the default configuration is. HIMEMX is
> supposed to be okay, but you can try other
> provided boot options with other drivers.
>
> Also note that it might matter which style
> of A20 gate your virtual machine offers,
> as misunderstandings about that can cause
> confusing for HIMEM and EMM386 drivers.
>
> Such problems can then show up as trouble
> when using XMS, HMA or UMB. FreeDOS uses
> all of those relatively early during boot
> when they are enabled, but of course you
> can change the configuration in many ways
> such as not putting DOS=HIGH,UMB lines.
>
> Regards, Eric
>
>> Virtual machine has 256 MB of RAM. I tried giving it 512 MB...> ... it 
>> appears to be using A:\FDSetup\BIN\HIMEMX.EXE as
>> DEVICE in FDCONFIG.SYS. ...
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Unable to install FreeDOS 1.2 on VirtualBox

[Mercury Thirteen via Freedos-user]

I get this every time I install 1.2 on VirtualBox. Try hitting Tab then add " 
raw" after the command shown.

Sent from ProtonMail mobile

 Original Message 
On Jul 29, 2018, 2:07 PM, FabulousKana wrote:

> Hello,
>
> I need some help. I am using VirtualBox 5.2.16 on Windows 10. I spotted
> that my virtual machine with FreeDOS had some weird corruptions so I
> decided to reinstall it.
>
> After booting the CD (FD12CD.iso), selecting the option "Install to
> harddisk" and waiting a little while it starts showing error messages
> with "Invalid Opcode". When I skip config.sys/autorun.bat on startup and
> run "setup.bat" manually it shows the language selection properly, but
> ends up with error "Unable to locate the installation packages. A reboot
> may help." If I run autorun.bat instead it shows the error messages
> "LBACACHE: XMS error.43ff Not enough free XMS memory." and "Can not set
> environment variable '_B'. Environment full?". Everything worked just
> fine before updating the VirtualBox. The checksums are appear to be
> correct so I don't think that installation iso is broken. Anyone has any
> ideas what it could be?
>
> Thanks in advance.
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Networking without ethernet?

[Mercury Thirteen via Freedos-user]

Afaik, TCP/IP interfaces to a packet driver, which then works directly with the 
NIC. It shouldn't matter over which medium you're ultimately communicating, as 
long as it presents the packet interface which TCP/IP expects.

Sent from ProtonMail mobile

 Original Message 
On Jul 10, 2018, 1:23 PM, David McMackins wrote:

> Even if I did, that doesn't answer my question. Even if I get connected
> to dial-up, will TCP/IP applications still work, or will they complain
> about drivers since they are trying to access a NIC?
>
> Happy Hacking,
>
> David E. McMackins II
> Supporting Member, Electronic Frontier Foundation (#2296972)
> Associate Member, Free Software Foundation (#12889)
>
> [www.mcmackins.org](www.mcmackins.org [www.delwink.com]( href=)">www.delwink.com
> [www.eff.org](www.eff.org [www.gnu.org](www.gnu.org 
> [www.fsf.org](www.fsf.org
>
> On 2018-07-10 12:17, Louis Santillan wrote:
>> Have you tried setting up a Linux box as a dial-up server? [0]
>>
>> [0] [https://www.howtoforge.com/linux_dialin_server](> href=)">https://www.howtoforge.com/linux_dialin_server [8]
>>
>> On Mon, Jul 9, 2018 at 9:10 PM David McMackins 
>> wrote:
>>
>>> I have a 1998 Sony Vaio running FreeDOS. This model did not include
>>> an
>>> ethernet controller (or wlan), but it does have an old modem in it.
>>> I've
>>> been going through the networking guide referred to by Rugxulo, and
>>> I
>>> got down to running NICSCAN.EXE only to realize *oops!* this
>>> computer
>>> doesn't even have an ethernet card.
>>>
>>> Supposing I could find a working phone line and dial-up service to
>>> connect the modem to, is there hope of using TCP/IP applications
>>> like
>>> wget over it using the software available to me?
>>>
>>> Happy Hacking,
>>>
>>> David E. McMackins II
>>> Supporting Member, Electronic Frontier Foundation (#2296972)
>>> Associate Member, Free Software Foundation (#12889)
>>>
>>> [www.mcmackins.org](www.mcmackins.org [1] [www.delwink.com](>> href=)">www.delwink.com [2]
>>> [www.eff.org](www.eff.org [3] [www.gnu.org](>> href=)">www.gnu.org [4] [www.fsf.org](www.fsf.org [5]
>>>
>>>
>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! [http://sdm.link/slashdot](>> href=)">http://sdm.link/slashdot;>[http://sdm.link/slashdot](>> href=)">http://sdm.link/slashdot;>http://sdm.link/slashdot;>http://sdm.link/slashdot;>[http://sdm.link/slashdot](>>  href=)">http://sdm.link/slashdot [6]
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> [https://lists.sourceforge.net/lists/listinfo/freedos-user](>> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](>>  
>>> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](>>  href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user [7]
>>
>>
>> Links:
>> --
>> [1] http://[www.mcmackins.org](www.mcmackins.org
>> [2] http://[www.delwink.com](www.delwink.com
>> [3] http://[www.eff.org](www.eff.org
>> [4] http://[www.gnu.org](www.gnu.org
>> [5] http://[www.fsf.org](www.fsf.org
>> [6] [http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>[http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>http://sdm.link/slashdot;>http://sdm.link/slashdot;>[http://sdm.link/slashdot](>  href=)">http://sdm.link/slashdot
>> [7] [https://lists.sourceforge.net/lists/listinfo/freedos-user](> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](>  
>> href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>https://lists.sourceforge.net/lists/listinfo/freedos-user;>[https://lists.sourceforge.net/lists/listinfo/freedos-user](>  href=)">https://lists.sourceforge.net/lists/listinfo/freedos-user
>> [8] [https://www.howtoforge.com/linux_dialin_server](> href=)">https://www.howtoforge.com/linux_dialin_server
>>
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! [http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>[http://sdm.link/slashdot](> href=)">http://sdm.link/slashdot;>http://sdm.link/slashdot;>http://sdm.link/slashdot;>[http://sdm.link/slashdot](>  href=)">http://sdm.link/slashdot
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> [https://lists.sourceforge.net/lists/listinfo/freedos-user](>