Hi,
> I'm looking at changing kDoSound() in ksound.c to a message model. Hmm, is there really any need to change the interface to the sound subsystem? kDoSound() just sends commands, after all, and it uses a fairly simple interface to do this. As far as I can tell, the current interface should work just fine for a message model; where's the problem? > I noticed > that some of the kernel sound commands return values that are then stored in > the accumulator. What uses these values afterwards? The virtual machine. > I don't suppose I can get > away with not implementing return values, can I? I'm afraid so- the interfaces to the game scripts are fixed. llap, Christoph
