Troubleshooting ViaVoice: a follow-up

Here's an overdue follow-up to our coverage of ViaVoice last month:

ViaVoice and upgraded G3s Regarding our report that ViaVoice does not work on older Macs updated to G3s, several readers took exception to this:

"Not true for my 7600/302 upgraded to a G3." [Jim O'Hearn]

"I had no problems at all installing and using ViaVoice 1.0 on my 1995-vintage PowerMac 7500 upgraded with a Newer Technology 250MHz MAXpowr G3 processor board and running under MacOS 8.5.1." [Andy Baird]

"ViaVoice works flawlessly on my Morotola Starmax 4000/160 upgraded to G3/240/512 with a Vimage board. (Similar to Mac 4400). I do not use virtual memory as suggested by IBM, just the 160MB built in RAM." [Bill Ling]

Update: Several readers (including Frank McCart and Tim Clabaugh) suggest that the problem may be limited to NuBus Macs with G3 upgrades. PCI Macs with G3 upgrades should work. See also this MacFixIt Forums thread.

However, Charlie Downs writes of one case where ViaVoice worked on a Mac not upgraded to a G3 at all: "A client purchased Via Voice then asked me to install it on his Performa 6500/300. I upped his RAM to 96MB and ran the installer. VM is on and set to 97MB. The client reports the software only occasionally misspells or misunderstands a word."

ViaVoice and virtual memory Regarding requirement that virtual memory be on for ViaVoice to work, Eli Block states that he "got around" this by running ViaVoice with virtual memory enabled and then turning virtual memory off, restarting, and running ViaVoice again. It then worked even with VM off.

ViaVoice and PaperPort conflict? Mike Friedman reports: "There is a known conflict between the PaperPort 5.02 menu extension and the ViaVoice menu extension. ViaVoice menu does not appear if PaperPort is enabled. IBM knows about this."

Resources

report

MacFixIt Forums thread

requirement

More from Late-Breakers