I have restored from a ghost backup and have not had to reinstall the quella key. ----- Original Message ----- From: "Ricque" <ricque@xxxxxxxxxxxxx> To: <jfw@xxxxxxxxxxxxx> Sent: Thursday, January 13, 2005 3:58 PM Subject: Re: Implications of back up of hard drives with I L M & retaining use of older JAWS versions? > Since the authorization key may be lost during the imaging process, it would > probably be a good idea to move it back to the floppy before imaging. > Since the ILM key doesn't actually reside on the hard drive, the locking > code, and the authorization number should be retained in the image. > Ricque > ----- Original Message ----- > From: <ptusing@xxxxxxxxxxxxx> > To: <jfw@xxxxxxxxxxxxx> > Sent: Thursday, January 13, 2005 5:39 PM > Subject: Implications of back up of hard drives with I L M & retaining use > of older JAWS versions? > > > > HI, > > It would seem that a restored ghosted hard drive would be by > definition > > usually be left with a wiped out quella key. > > And since the I L M won't support earlier JAWS versions then minus the > > quella(killed during the restore), then backing up using ghost means one > > "might" be left with JAWS 6 and not with earlier JAWS versions? > > Any solution? > > The earlier message suggests that the I L M use alone fails to support > > what the quella did in terms of Access 32 (see original message) so > when > > ghost kills the quella, it's "bye bye" to older JAWS versionsafter the > > restore...? > > Also, can one remove the I l M key *totally* so one can start "over" and > > put the quella *back first * and then add the I L M key later to use > older > > JAWS versions after restoring using gthost? > > Other implications for backing up hard drives with his I L M key? > > > > > > > > > > ----- Original Message ----- > > > From: "Hal Pearson" <hspearson@xxxxxxxxxxxx> To: "JFW List" > > <jfw@xxxxxxxxxxxxx> > > > Sent: Thursday, January 13, 2005 1:23 PM > > > Subject: access32 and jfw ilm V 6, my findings > > > > > > > > > > Hi to Pat Tusing, and all on list, > > > > > > > > Last night I was able to get my Access32 working with the ilm version > of > > > jfw > > > > 6. Needless to say I was very excited, yes it can be done. I first > made > > a > > > > back up of the original jfw.ini file for Jaws 6, then copied the > > > > synthesizers section from an earlier version and pasted it in. Before > > > > installing new ilm version, I removed the V 6.0 quella version. I > chose > > to > > > > remove all settings, and that might be why I lost the ability to use > > > > Access32. I guess I wanted to do a fresh install and start with a > clean > > > > slate. So if you are using dectalk, and moving from quella to ilm, you > > may > > > > wish to keep your original settings, this includes default speech, > > frames, > > > > scripts, and dictionary changes. I'd advise this only if you aren't > > > > comfortable editing an ini file such as I did, lol! But I am still not > > > sure > > > > you can use Dectalk 32without a quella key installed. Right now I am > > > running > > > > jfw quella 4.51, 5.1, and ilm 6.0. I discovered, that I have a copy of > > > > dtsoft.jls located in my c:\program files\Freedom Scientific\JAWS\6.0 > > > > folder. The dtsoft.jls, is a necesssary file needed to run Dectalk, > it's > > a > > > > driver I think. Amazing what you can find on your system when you are > > > trying > > > > to get something to work for you. > > > > > > > > Hal > > > > > > > > > > > > [Synthesizers] > > > > Synth1Name=dtsoft > > > > Synth1LongName=DECtalk Access32 Software > > > > Synth1Driver=dtsoft > > > > Synth2Name=eloq > > > > Synth2LongName=Eloquence for JAWS > > > > Synth2Driver=eloq > > > > Synth3Name=SAPI 5X > > > > Synth3LongName=SAPI 5 > > > > Synth3Driver=sapi5x > > > > Synth4Name=NoSpeech > > > > Synth4LongName=No Speech > > > > Synth4Driver=nospeech > > > > > > > > -- > > > > To post a message to the list, send it to jfw@xxxxxxxxxxxxx > > > > To unsubscribe from this mailing list, send a message to > > > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. > > > > Archives located at: //www.freelists.org/archives/jfw > > > > > > > > If you have any concerns about the list, post received from the list, > or > > > the way the list is being run, do not post them to the list. Rather > > contact > > > the list owner at jfw-admins@xxxxxxxxxxxxxx > > > > > > -- > > > To post a message to the list, send it to jfw@xxxxxxxxxxxxx > > > To unsubscribe from this mailing list, send a message to > > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. > > > Archives located at: //www.freelists.org/archives/jfw > > > > > > If you have any concerns about the list, post received from the list, or > > the way the list is being run, do not post them to the list. Rather > contact > > the list owner at jfw-admins@xxxxxxxxxxxxxx > > > > -- > > To post a message to the list, send it to jfw@xxxxxxxxxxxxx > > To unsubscribe from this mailing list, send a message to > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. > > Archives located at: //www.freelists.org/archives/jfw > > > > If you have any concerns about the list, post received from the list, or > the way the list is being run, do not post them to the list. Rather contact > the list owner at jfw-admins@xxxxxxxxxxxxxx > > -- > To post a message to the list, send it to jfw@xxxxxxxxxxxxx > To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. > Archives located at: //www.freelists.org/archives/jfw > > If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx -- To post a message to the list, send it to jfw@xxxxxxxxxxxxx To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/jfw If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx