CompuServe Messages

Gee, I'd hoped you'd come up with a better answer than that… 🙂 If we make our own PRT: handler, and intercept all calls to it and move them across the network to another machine, presumably we'd need to have some way to access an unaltered PRT: handler on the destination machine, so it could pass through the Preferences drvier on that machine. If some programs use printer.device directly – and why not? – then we're still stuck. And you can't zap "serial.device" to "modem0.device" after the printer.device has been loaded, and you can't flush it unless nothing else is in the system. And is there a way to flush only only device from memory, without flushing every other zero-count device or library or font from the system at the same time?