Aaron,
No, the point is the remedy for the Acorn problem (adding the "second" printer in CUPS and deactivating the out of the box /dev/null one (referring to the detailed instructions from your colleague Roy) allowed me to get some (possibly raw) printer activity from VRPC but, I assert, later was discovered to have disabled the MAC side. This is perhaps unsurprising insofar as the out of the box CUPS entity, though still present, is inactive in favour of the one added by the specialist instructions. If the Mac side is left disabled as I assert, the CUPS adjustment has to be reversed.
I am asserting that whilst Roy's remedy moves the problem forward (printer comes in to life from VRPC side) as an unwanted by-product it 'breaks' the Mac side. Has he been able to subsequently use the Mac side with the original (I term it /dev/null) driver deactivated and VRPrinter (as he named it in the article) active from CUPS?
sample from his text for context:
This article covers printing problems with VirtualAcorn running under Mac OS X. This article assumes that you have correctly configured a RISC OS printer driver for your printer and that RISC OS generates the print job without any errors. If further assumes that the print job arrives in the Mac OS X print queue, but then vanishes without being printed. [Chris: my experience exactly]
<cut>
<cut>
The next screen asks for the make and offers a drop list. Select the very top one which is 'Raw'.. Do not select the actual printer.. The next screen asks for Model, but should already have 'Raw Queue (en)' inserted. Don't change this and just accept it (by selecting it) and continue.
The Admin screen should show that this printer has successfully been added. If you now select the printer tab, you should find this new printer in the list, with the Device URI:
usb://... you filled in. Now Click 'Set As Default'.
<end of quote>
I think my Acorn printer driver is probably OK.