[Freedos-user] Writing articles about FreeDOS

[Jim Hall]

Thought you'd like to know: of all the articles published on
Opensource.com in January, my recap article about FreeDOS was the #3
most-read article.
https://opensource.com/article/22/1/try-freedos

So if you feel motivated to write for a tech website, and wonder if
they would be interested in a "FreeDOS" article, the answer is "Yes."

It's a great way to contribute to FreeDOS without writing code.

And now that we've released FreeDOS 1.3, this would be a great excuse
to write an article about FreeDOS.

Just a suggestion for those who like to write.


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

Re: [Freedos-user] Crynwr packet drivers

[Jim Hall]

>>> from Jim Hall:
>>>
>>>
>>> > I don't know why the sources later had an "AMD" statement put on them,
>>> > but you cannot claim "proprietary" or "copyright" on something that
>>> > was previously released under the GNU General Public License.
>>>
>>> > It appears that somewhere along the line, someone (at AMD?) had access
>>> > to the sources, probably in a larger source tree, and ran a batch job
>>> > or script to apply the "AMD" statement to a bunch of source files. And
>>> > that happened to catch these GPL and public domain source files. I
>>> > believe that was done in error. The original public domain and GPL
>>> > declarations trump the latter "AMD" statement.
>>>
>>>
>>> > Resolution:
>>>
>>>
>>> > (1) Let's re-accept the FDNET package into the next FreeDOS distribution.
>>>
>>> > (2) I'll make a note about this decision in the FreeDOS wiki at
>>> > http://wiki.freedos.org/wiki/index.php/Releases/1.3/Packages
>>> > (this currently has a red "do not include" note on it .. I'll update
>>> > to change it a green "include" message)
>>>
>>> > (3) To prevent future confusion, I'll create a new version of these
>>> > source files that *removes* the "AMD" statement, where a previous GPL
>>> > or public domain declaration was already made. (I think that's all of
>>> > the files in question.) I'll also create (or update, if it exists) a
>>> > README file to note the changes to the source files, and why.
>>>
>>>
>>> > I look forward to including networking support again in the next
>>> > distribution, which should be FreeDOS 1.3 RC5.
>>>
>>>
>>> > *If you agree or disagree, I'd appreciate your reply to this email.
>>> > Agreement can be simply "agree" or "+1". If you disagree, please
>>> > discuss. (But consensus from the last discussion favored including
>>> > FDNET, so if no one disagrees now, I'll assume no concerns on this.)


> On Thu, Oct 14, 2021 at 12:19 AM John Vella  wrote:
>>
>> Agree!

>> On Thu, 14 Oct 2021, 07:33 Thomas Mueller,  wrote:
>>>
>>> Agree
>>>
>>> Tom
>>>

On Thu, Oct 14, 2021 at 12:34 PM Louis Santillan  wrote:
>
> It would likely be prudent to get a confirmation statement from Russell 
> Nelson as well.
>

Hi everyone

I'm responding to this very old thread because I did reach out to
Russell and he recently got back to me. I wanted to share the outcome.
Yes, the AMD statements were an error. My conversation with Russell:

: Hi Russ
:
: It's been a while since we last connected. I hope things are great!
[..]
:
: Along the lines of DOS stuff, I had a question about the packet
: drivers on your site: http://crynwr.com/drivers/
[and you all know the details, see above]


Russell had a very short reply:

:: Yes, AMD applied in error. Who unpblishes software, anyway??


So there's the confirmation that AMD's statements were applied in error.


I'll add it to my to-do list to make an updated zip package of the
Crynwr packet drivers that removes the errant AMD statements, and
include a copy of my conversation with Russell as a separate Readme
file.


Jim


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

Re: [Freedos-user] Ontrack Disk Manager

[Jim Hall]

On Mon, Jan 24, 2022 at 2:40 AM Darik Horn  wrote:
>
> Regarding this old ticket:
>
> * https://sourceforge.net/p/freedos/bugs/211/
>
> FreeDOS 1.3 is compatible with Ontrack v9.57 and Ontrack v9.88.  I tested 
> these disk overlays on a 486 with AMIBIOS 2.02, which has the 504 MB 
> addressing limit.
>
> Kroll released their Ontrack software to the retro computing community at 
> zero-cost per:
>
> * https://www.philscomputerlab.com/ontrack-disk-manager.html


Thanks for sharing that link. I've added it temporarily to the Links
page under "Power Tools"
https://www.freedos.org/links/

I say "temporarily" because when I'm able to finish the new website
(after usability testing) I'll find a new place to link this on the
new site.


Jim


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

Re: [Freedos-user] Watcom compiler on FreeDOS 1.3 RC5

[Jim Hall]

> On Wed, Jan 26, 2022 at 2:33 AM Fabian Boucsein  
> wrote:
> >
> > After installing the Watcom from the IBIBLIO FreeDOS archive what
> > do i need to configure the compiler so that i can use it?

On Wed, Jan 26, 2022 at 12:34 PM Rugxulo  wrote:
>
> set WATCOM=%RAMDRIVE%:\watcom19
> set INCLUDE=%WATCOM%\H
> set EDPATH=%WATCOM%\EDDAT
> set WIPFC=%WATCOM%\WIPFC
> path %WATCOM%\BINW;%PATH%
> REM ... optional ...
> REM if "%DOS4G%"=="" set DOS4G=quiet
> REM ren dos4gw.exe *.ex
> REM copy /b cwstub.exe dos4gw.*
>
> This may also help:
> * http://www.freedos.org/books/get-started/june25-c-programming.html
>


The bit that Rugxulo is pointing to in that article is this:

> Before you can compile using OpenWatcom, you'll need to set up the
> DOS environment variables so OpenWatcom can find its support
> files. The OpenWatcom C compiler package includes a setup batch file
> that does this for you, as \DEVEL\OW\OWSETENV.BAT. Run this batch
> file to automatically set up your environment for OpenWatcom.


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

Re: [Freedos-user] 1.3 on VBox

[Jim Hall]

On Mon, Feb 21, 2022 at 3:09 PM Liam Proven  wrote:
>[..]
> And can anyone point me to any instructions for installing under
> DOSemu on a Linux box? I can't find anything, and the automatic
> FreeFOS 1.2 installer doesn't even work any more... :-(
>


I don't use DOSEMU anymore, but I do use QEMU. Here's my command line for that:


/usr/bin/qemu-system-x86_64 -name FreeDOS -machine
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu
host -m 16 -overcommit mem-lock=off -no-user-config -nodefaults -rtc
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
-msg timestamp=on -hda freedos.img -cdrom FD13LIVE.iso -device sb16
-device adlib -soundhw pcspk -vga cirrus -display sdl -usbdevice mouse



Note that this command line assumes you've already created your C:
disk image (qemu-img create freedos.img 500m) and that your FreeDOS
1.3 LiveCD is in the current directory.

This is slower to install on QEMU, but it's fine after that. And
unlike VirtualBox, QEMU emulates the PC speaker. (Disclaimer: I use
QEMU for some things, and VirtualBox for some other things. But I'm
generally moving more of my usage to VirtualBox.)


Jim


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

Re: [Freedos-user] How to upgrade 1.3 RC5 to 1.3

[Jim Hall]

> > On Feb 21, 2022, at 3:31 PM, Björn Morell  wrote:
> >
> > How do  I upgrade 1.3 RC5 to 1.3 on a 486 ( I can use bootcd ) ?

On Mon, Feb 21, 2022 at 4:09 PM Jerome Shidel  wrote:
>
> There is a CD Boot Floppy image included in the LiveCD and LegacyCD
> zip files alongside the appropriate ISO.
>
> You can run the normal Installer. However, you may wish to run it in
> advanced mode for greater control on what happens (setup adv).
[..]


As Jerome said, there's an "Advanced" feature in the installer to give
you more control over the install options, including options to not
reformat your hard disk.

Boot the LiveCD and run this command:

SETUP ADV


If you get an installer with a red banner at the top and red dialog
boxes, you're in Advanced mode.


Jim


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

Re: [Freedos-user] Re (2): Installing FreeDOS 1.3.

[Jerome Shidel]

> On Feb 21, 2022, at 1:25 PM, pe...@easthope.ca wrote:
> 
> Jerome,
> 
>> While it should get FreeDOS booting, I don=E2=80=99t think it will =
>> provide enough flexibility for what you want.
> 
> Afraid of that!   =8~/
> 
>> ... it is free 
>> just not open source. It has very strict =E2=80=9Ccan distribute if you =
>> change absolutely nothing=E2=80=9D license. 
> 
> No problem for me.
> 
>> ... dozens of options regarding the MBR/Partition tables. 
> 
> Setting the bootable flag on sdb1 might be a good first step.  Should 
> anything else in the partition table change?  Obviously partition 
> structure should not change.
> 
Possibly the boot code. 

> 
> Isn't at least one file missing from sdb1?  The kernel?  Command 
> interpreter?

They should be there. You boot the CD and double check the drive C: for 
KERNEL.SYS and COMMAND.COM . If there missing, then simply 
doing a SYS C: (May work from the RAM DISK or CD-ROM, otherwise from the drive 
A: emulated floppy) might get the system working.

> Thx!   ... P.

:-)

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

Re: [Freedos-user] How to upgrade 1.3 RC5 to 1.3

[Jerome Shidel]

> On Feb 21, 2022, at 3:31 PM, Björn Morell  wrote:
> 
> How do  I upgrade 1.3 RC5 to 1.3 on a 486 ( I can use bootcd ) ?

There is a CD Boot Floppy image included in the LiveCD and LegacyCD zip files 
alongside the appropriate ISO.

You can run the normal Installer. However, you may wish to run it in advanced 
mode for greater control on what happens (setup adv). Also, the Floppy Edition 
installer is an option as well. It can be run from a set of floppy diskettes. 
Or, even from the subdirectory (FDI-x86) on the CD-ROM. It is a completely 
different installer and is less CPU/disk intensive. It to has an advanced mode.

> 
> 
> 
> ___
> 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] 1.3 on VBox

[Liam Proven]

I installed the release version this evening, and I'm impressed. I'd
never thought I'd see a DOS VM find the (virtual) NIC and acquire an
IP address automatically! Wow!

And it still has a lot of RAM free too...

Very good work, all.

Is there any recommendation for a compatible SMB network client to put
on top of it?

And can anyone point me to any instructions for installing under
DOSemu on a Linux box? I can't find anything, and the automatic
FreeFOS 1.2 installer doesn't even work any more... :-(

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ 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] How to upgrade 1.3 RC5 to 1.3

[Björn Morell]

How do  I upgrade 1.3 RC5 to 1.3 on a 486 ( I can use bootcd ) ?



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

[Freedos-user] Re (2): Installing FreeDOS 1.3.

[peter]

Jerome,

> While it should get FreeDOS booting, I don=E2=80=99t think it will =
> provide enough flexibility for what you want.

Afraid of that!   =8~/

> ... it is free 
> just not open source. It has very strict =E2=80=9Ccan distribute if you =
> change absolutely nothing=E2=80=9D license. 

No problem for me.

> ... dozens of options regarding the MBR/Partition tables. 

Setting the bootable flag on sdb1 might be a good first step.  Should 
anything else in the partition table change?  Obviously partition 
structure should not change.

Isn't at least one file missing from sdb1?  The kernel?  Command 
interpreter?

Thx!   ... P.


-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W



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

Re: [Freedos-user] Installing FreeDOS 1.3.

[Jerome Shidel]

>> If that does not work or if you prefer, you can use FDISK and SYS to 
>> update the boot code.
> 
> Are instructions available?

Only as far as the individual programs help. 

> 
> The advanced installation process of FreeDOS might also provide a 
> resolution.

While it should get FreeDOS booting, I don’t think it will provide enough 
flexibility for what you want.

> 
> If all else fails I can repeat the FreeDOS installation with MBR 
> included. Then make Oberon the primary boot again.  Then reinstall 
> Boot Manager.  Then each of the systems should be bootable.  Fixing 
> FreeDOS directly is preferable.  =8~)

Well, if you want to just try and “fix” what is already installed. Head over to 
my server and grab the mirrored copy of MBRTOOL. The original site doesn’t 
exist anymore. However, it is free just not open source. It has very strict 
“can distribute if you change absolutely nothing” license. So, it isn’t 
provided with FreeDOS or on the official or my download repos. But, it is a 
great little utility with dozens of options regarding the MBR/Partition tables. 
There are two versions mirrored on my server. The last v1.x that is strictly 
command-line interface and the last 2.x which also has a text UI. Both work 
fine. However, 2.x version is much larger and not as suited for boot/recovery 
floppies.

https://fd.lod.bz/redist/disk/MBRtool/ 


> Thx!   ... P.
> 
> 
> -- 
> mobile: +1 778 951 5147
>  VoIP: +1 604 670 0140
>   48.7693 N 123.3053 W
> 
> 
> ___
> 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] Installing FreeDOS 1.3.

[peter]

From: Jerome Shidel  - 2022-02-21 00:14:37
> It installs to the First drive whose partition is compatible to DOS 
> and enumerated by the kernel as drive C:.
> 
> Unless, you run it in advanced mode. Then other hard disks could be 
> targeted for install.

Thanks Jerome.  Will try to remember for future.

> During installation on real hardware, you should have been prompted to 
> update your MBR. If you select no and there is not a compatible boot 
> loader in the MBR, the system won’t boot.

Yes, I declined the MBR update.  /dev/sdd2 has a working Oberon 
installation.  Also Boot Manager is installed and works.  
https://en.wikibooks.org/wiki/Oberon#System_Startup

Until a HDD failed a few years ago, FreeDOS and Oberon worked and 
either could be started by Boot Manager.  =8~)

> If you boot the Install media, you can try running MBRZAP (or ZAPMBR, 
> it’s been a while). It will run the portion of the installer that 
> updates the boot loader. (Or, at least it used to, I haven’t tested 
> it in a long time)

Writing in the MBR will spoil Boot Manager and make the system in sdd2 
unbootable; correct?  I'd rather just fix the kernel and command 
interpreter in sdd1.  A similar predicament was solved 5+ years ago.
Unfortunately I've forgotten details.  =8~(

> If that does not work or if you prefer, you can use FDISK and SYS to 
> update the boot code.

 Are instructions available?

The advanced installation process of FreeDOS might also provide a 
resolution.

If all else fails I can repeat the FreeDOS installation with MBR 
included. Then make Oberon the primary boot again.  Then reinstall 
Boot Manager.  Then each of the systems should be bootable.  Fixing 
FreeDOS directly is preferable.  =8~)

Thx!   ... P.


-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W


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