-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hi Debee, You're absolutely right; every distro does it differently <sigh>. I also looked around in the isolinux directory with partial success. You might also look at the syslinux.cfg or whatever it's called. I think there may be actually several cfg files in there to control the boot process. It would probably help to get a thurough understanding of syslinux system. I do not have such a knowledge either. But also one can look around in the /boot directory too but I believe most live CDs and other installers boot with syslinux or isolinux. What we really need is a wiki for speakup. We have one for Orca and it is filling out pretty well; it has a ways to go like any other public document but anyone with the brains and experience can update it with what they know. We should do similarly with speakup; those of us who use particular distros can write up how to use that distro to boot into speakup. Actually such fragments of the wiki or user supported documentation should be supplied to the maintainers of the respective distro. Slackware has such documentation and so far is still fairly current. I frankly don't recall if Debian has such a document in its collection. I haven't looked. Also, as you mentioned something about speakup.synth vs speakup_synth. It has officially changed to speakup.synth with the most recent changes to a totally modular speakup. So that style parameter would be effective for Slackware, Debian and any other distro where boot parms are supported. HTH. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAknKzwsACgkQWSjv55S0LfH7dgCg8TjSFnxmfqW3BVKy8jm9khZW fwwAoOjSXehyElASoPds9325xjLj3Q5o =lY8r -----END PGP SIGNATURE-----
