This really is not a problem if you go to programs then JFW 6, there is a menu item that says explore jaws. You can move to personal folders in the usual way in windows, and that is where you would put any script files you want. Also, merge works well which will take care of some of this for you. You don't have to memorize a huge path name, just explore jaws. Rose Combs rosecombs@xxxxxxxxx -----Original Message----- From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Jeanie Vejil Sent: Thursday, July 07, 2005 9:19 PM To: jfw@xxxxxxxxxxxxx Subject: JFW 6.0 and the enu folder Hi all. I have a question concerning JFW 6.0 and where the enu folder is stored. I am using JFW 5.1 and haven't felt like installing 6.0 as I have heard that the enu folder isn't in the same place it has been located in for all versions of JFW until 6.0. I am running windows 98 SE if that makes any difference. If someone wants to write me privately with the information I'm asking for, please feel free to do so at proud2have-tsedog@xxxxxxxxxxxxxx Thanks in advance, and if there is anything else not in the same place it's always been in, please mention that too. Jeanie Vejil -- 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