This evening I found out what caused Voyager 3 pre-release 3 and 4 to insist
upon that I hadnt installed CManager.mcc even if such a file could be found in
MUI:Libs/mui and a CManager.library in LIBS:.
I had registered CManager on-line on www.vapor.com using my credit card and
the CManager.KEY file was e-mailed to my e-mail address. Something went wrong
with Thor when the e-mail was imported so I ended up with two files in the
decoded directory: CManager.KEY and CManager.KEY.0. Thor converts attached
files on import and saves them in the decoded directory.
The .KEY file was 30 bytes while the .KEY.0 file was 572 bytes. I had of
course copied the .KEY file to S:. It seems that either CManager.mcc and/or
CManager.library checks for the key file and if it doesn't check out something
goes wrong whihc Voyager displays as if the file isn't there at all.
Voyager should be a bit more investigative if a MUI class fails to load and
not just assume that it isn't there if something goes wrong during
instantiation.
The other persons who reported the same thing as I have, could you check if
either replacing and/or temporarily removing the CManager-key file from the
key file search path fixes your problems too?
/Mats-Olov Rustad
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
