On Sat, Feb 22, 2025, 4:49 AM Paul Dufresne via Freedos-devel <
freedos-devel@lists.sourceforge.net> wrote:
> ---- Le ven., 21 févr. 2025 18:20:04 -0500 Kirn Gill II via Freedos-devel
> a écrit ----
>
>
>
>
> * > Due to various complaints of technical issues and bugs that all have
> the same common element of Broadcom virtualization technology ("VMware"),
> and with changes to the hypervisor that have rendered the virtualized
> environment somewhat hostile to the DOS ecosystem, I recommend we just
> flat-out state we do not support VMware or any other Broadcom
> virtualization platform. > > If it breaks under VMware, let the user
> keep the pieces.*
> To be honest, I kind of detected this same reaction by Jim (although he
> did not outspoke it, more by body language) at some point in last video
> meeting.
>
I think you misinterpreted my reaction.
I was aware of what was going on with VMware, that Broadcom bought out
VMware and were overcharging users. I probably said they were being stupid,
because my interpretation is Broadcom didn't really seem interested in
continuing VMware anyway.
I was also trying to recall (but couldn't remember) if we'd had any
previous issues with VMware. You might have noticed I mentally "checked
out" from the meeting around that time; I was googling and searching my
email history. I came "back" when someone asked me a question, and had to
ask their question again because I was just not paying attention the first
time.
In the end, I couldn't remember a specific example, but I had a vague
memory of a time when VMware broke some DOS compatibility and they didn't
really care.
I probably confused VMware with VirtualBox. They have a history of breaking
things in a release, which causes users to ask (either on the email lists,
or on the Facebook group) about "why doesn't FreeDOS work in VirtualBox?"
We spend a bunch of time helping them debug, but they just can't get out to
work. Then a few weeks later, VirtualBox makes a new "point" release that
fixes everything without anything from us. That is, FreeDOS didn't have a
problem, it was in VirtualBox.
But the bug about out of memory on VMWare, was not happening only in
> VMWare, I have seen it too on my real hardware, but not as easily as in
> VMWare.
> I had to have a specific video card in, and have logger driver installed
> to happen.
>
> And now that the cause of the bug was identified (some lines that was
> specific to GCC and TurboC but not WATCOM, so happens when FreeCom compiled
> with WATCOM but on some rare place like VMWare),
> this particular program should now be fixed.
>
> And the main reason that bring me to test on VMWare, was problems I was
> having with VirtualBox (that are not yet fixed on VirtualBox):
> -horrible static noise in the music or speach of some games.
> -bad colors in some games
>
> So now, I would be more encline to recommend Windows users to use VMWare
> than VirtualBox... as they cannot use QEmu (which is in command line).
>
>
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
