Started by andreas_g, May 27, 2010, 12:44:35 PM
Quote from: "eagle"I've noticed that too. I want to upgrade to Fusion 3.1, but not if it means that my NeXT VMs won't work...On a related note, do you know if it's possible to get audio input working in Fusion? I want to use Lip Service, which I thought had been removed from the Intel versions. I will be able to use Lip Service if I can get audio input working in VMware 2.x.
Quote from: "Uli"Has somebody already tried to contact the author of the audio driver?
Quote from: "Morgon"Quote from: "Uli"Has somebody already tried to contact the author of the audio driver?No one has contacted me yet.
QuoteIn the first place I wrote the driver for myself to get sound running with my Soundblaster16PCI. Just by luck that's just the chip VMware emulates so it works in there as well. [...] At the end maybe an idea. For my network driver VMwareFusion changed the emulated NIC with some update which can be undone by a setting in the configuration file. Maybe there is something similar happening with the sound driver now.
QuoteSorry again for not beeing able to help.
Quote from: "Uli"I have little time myself, and unfortunately know little about writing drivers, but your source code certainly provides a starting point. I will try to contact VMware and find out what exactly changed in Fusion 3.1, and maybe this will provide a path to go on ...Uli