BTW, this isn't directly related to this guy (and haven't heard any
feedback from him lately), but I'll continue in this thread here
anyways since the topic is still valid.

Seems there is a bug in VirtualBox (4.1.8, at least, doubtful fixed in
4.1.10) that causes implicit file renaming to fail in FreeDOS. So
things like UPX and "sed -i" don't work correctly, it keeps the
garbled temporary name instead and doesn't work. It's not the fault of
the shell (4DOS, FreeCOM), and it's not DOSLFN. I even upgraded the
kernel to 2041 (from 2040), skeptically, but that didn't fix it

It turns out that the bug isn't there when VT-X is enabled, only when
it's off (blech!). So I saw it on my laptop but not desktop. Very
annoying, it's almost unusable with such a bug (and was already kinda
painfully slow without VT-X).

I have no idea how to even describe such a bug for their bugtracker,
much less have any hope that they actually care or could fix it. Just
mentioning it here in case someone cares. (Perhaps now would be a good
time for me to test some other VMs.)

On Fri, Mar 2, 2012 at 2:59 PM, nweissma <nweis...@verizon.net> wrote:
> I am using solaris 11 11/11 (64-bit; latest) as the VirtualBox host; VB
> version is 4.1.8 (the latest) https://www.virtualbox.org/wiki/Downloads;
>  and I am using fd11src.iso (although I am in possession of fdfullcd [152
> MB]and fdfullws [241MB])
> I mention that the hardware = AMD Athlon II x2 250 .. I will mine sysbo data
> if you request it
> From: Rugxulo
> Sent: Friday, March 02, 2012 12:47 AM
> To: freedos-user@lists.sourceforge.net
> Subject: Re: [Freedos-user] FreeDOS Install on VirtualBox
> BTW, what host OS and which version of VirtualBox are you using? And I
> assume you're using fd11src.iso?

This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
Freedos-user mailing list

Reply via email to