Hi Matthew,
> ... storage, which I set to 40 GB. The installation took a long
> time---several hours, although I didn't measure it carefully.
> Post-installation, it seemed to run slowly, e.g., a directory listing of
> the FreeDOS "bin" directory took a minute or so to display anything. ...
Tha
Greetings, friends!
The release candidate announcement encouraged people to try FreeDOS out
and report any problems, so here I am to say that I successfully booted
and installed 1.2-RC1 in a generation-1 Hyper-V 2012 R2 virtual machine
using the ISO image. I pretty much took the defaults for ever
Hello Louis,
> Any idea how VirtualBox was configured for the user reporting the
> issue? NAT, Internal Network, Bridged, Host-only? This could answer
> the firewall question.
This was discovered to be an issue after the last VirtualBox update by Me
during final testing just before the final
Any idea how VirtualBox was configured for the user reporting the
issue? NAT, Internal Network, Bridged, Host-only? This could answer
the firewall question.
On Wed, Nov 2, 2016 at 4:35 AM, Jerome E. Shidel Jr. wrote:
> Hello All,
>
> The latest release of VirtualBox seems to have broken network
Hello All,
The latest release of VirtualBox seems to have broken networking support on
that “hardware.” Under the previous version of VirtualBox, installing the FDNET
package (included with RC1) would provide an automatic fully working networking
support. Programs like FDNPKG, PING, WGET and su
