On Tue, 2 Oct 2018 11:55:25 -0400 dmccunney wrote:
>
>Wine is good enough for a lot of what folks do, but perfection isn't
>possible. Is there a list anywhere of what Odin is known to support?
Hmm, on my ArcaOS 5.0, version 0.8.9 is installed, and its doc says:
'there is a large database of working apoplications at the Netlabs repository'
That repository is at:
https://trac.netlabs.org/odin32
But I could not find an explicit list there.
BTW:
The latest version is 0.9.0, built in 2017 with some minor changes over 0.8.9
It is present in the builds, but the home-page does not seem to be updated.
With the abundance of virtualisation enviroments available these days,
there does not seem to be much incentive to work on stuff like this.
>How much fun was getting the VirtualBox environment set up?
Not too hard really, except for macOS, which is officially not supported
when running a Windows host, but it is doable ...
>Virtualization is not a magic bullet. There is overhead in getting
>something virtualized, and you need reasonably powerful hardware to
>run it. (I first encountered virtualization on IBM mainframes, which
>had VM/CMS, whose intent was to let you do stuff like run DOS/VSE in
>one partition while you ran a test instance of MVS in another so you
>could migrate from VSE to MVS in a controlled manner. IIRC, VM
>overhead was about 10% of total system resources.)
I remember VM, we used that as data-interchange vehicle when I was on the
development team for OS/2 version 1.0 extended edition in Uithoorn in the
Netherlands, with most of the team being in Austin Texas, this was 1989 :)
I even distributed my first incarnation of my disk tool there,
using what we would call a 'package manager' these days.
>OTOH, the DOSBox product is a VM for DOS emulation on other
>architectures. I have some DOS apps up under Android on a tablet
>using an Android port of DOSBox.
Indeed, and the DosBox as present in OS/2 is pretty good as well,
allthough I do not use it that much anymore ...
>The network connectivity is the glue. If you have it, many things
>become possible.
Yes, unfortunatily I have no network connectivity in my FreeDOS VM,
but I handle that by mounting a virtual-disk shared with other VM's.
But normally I only need it to test my bootable-CD, so I just boot
the ISO in a VM ...
>Thanks for the look at what you do. I was fascinated.
You're welcome!
Regards, JvW
PS:
The user-interface library 'TxWin' I use for my disk-tool is open-source.
It implements basic windowing functions in text-mode, much like OS/2 PM
or Windows, with a message-que etc, and supports buttons, entryfields,
list-controls, menus and dialogs (including a standard file-open etc)
It also has mouse support.
For the DOS target, it needs the OpenWatcom compiler to build anything,
so is probably not easy to use natively on FreeDOS. It also needs/uses
the DOS32A extender to create 32-bit dos-extended programs ...
The library can be downloaded from my 'Free Downloads' page:
https://www.dfsee.com/download/index.php
Or directly from:
https://www.dfsee.com/txwin/txwin5xx.zip
Apart from DOS as a target, you can build for OS/2, Windows, Linux and macOS.
Jan van Wijk, author of DFSee; http://www.dfsee.com/dfsee/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
