Charley Cox, 

Thanks for your quick response to my request concerning LOGPATH.LSP.  
Yes, I was referring to the redefinition request concerning PARSE-NAMESTRING. 
Is there any way this problem can be fixed and the redefinition dialog avoided?  
Having to redefine the function each time the file is loaded is very painful. 

Secondly, I was referring to another problem that does not occur when loading 
LOGPATH.LSP, but when evaluating one of the examples given in the file.  The example 
I'm referring to is: 


  (setf (lp:logical-pathname-translations "prog")
        '(("CODE;*.*.*"    "/lib/prog/")))
  <cl> (lp:translate-logical-pathname "prog:code;documentation.lisp" :namestring)
  "/lib/prog/documentation.lisp"


Here is what happens when the evaluating the above two forms in ACL4W (I've included 
everything from the system is started up): 

  Welcome to Allegro CL for Windows 
  Version: 3.0 Release: 25-Oct-95 11:54
  Copyright (C) 1992-1995, Franz Inc., Berkeley, CA, USA.
  All rights reserved.
  Loaded Franz Inc. Patches: None.

  > 
  ;; Loading from #P"c:\\allegro\\logpath.lsp"
  ;; Load Successful
  ;; 120 forms read from #P"c:\\allegro\\logpath.lsp"
  ;; Result of last form read was ("a" "b" "c" ...)
  T

  > (setf (lp:logical-pathname-translations "prog")
        '(("CODE;*.*.*"    "/lib/prog/")))
  (("CODE;*.*.*" "/lib/prog/"))
  > (lp:translate-logical-pathname "prog:code;documentation.lisp" :namestring)
  "/lib/prog/.LSP"
  > 

So the bug is that "/lib/prog/.LSP" is returned rather than "/lib/prog/documentation.lisp". 
I'd be very happy if this problem is fixed.  

I've currently traced down the problem to the function translate-logical-pathname-aux.  
Exactly what happens (inncorrectly) in there I'm not sure about.  It could also be a 
translation table or something that is accessed by translate-logical-pathname-aux that 
has been set up inorrectly. 


Thanks for any help on this!

Ole J. Mengshoel.