Nightshade Legacy

Mac Lion OS and Nightshade

Asked by Joe Blow

I made the mistake of upgrading to Mac's Lion OS (I have been a Windows user for a long time, and admit to not understanding Mac very well). Nightshade originally installed scripts and everything into the /OPT/ folder - under Lion, while I can unhide that folder, some of the applications I use to develop scripts can no longer access that folder in spite of issuing the global unhide command. I tried reinstalling Nightshade, but find no way of changing where it installs scripts, etc. What's worse, after an install, I can no longer find the app file, so essentially I am dead in the water. Probably not Nightshade's fault. But after this experience, Windows machines are looking pretty good LOL.

Anyway, if anyone with some Mac expertise can help me, it would be much appreciated.

Oh yes - and to add to my aggravation, I could not log into this forum with my old name and password (obviously forgot it). So had to come bad as Joe Blow.

John Zimmerman

Question information

Language:
English Edit question
Status:
Solved
For:
Nightshade Legacy Edit question
Assignee:
No assignee Edit question
Solved by:
Joe Blow
Solved:
Last query:
Last reply:
Revision history for this message
Joe Blow (johnkzimm) said : 		#1

Well, I got it to working again. For some reason Nightshade does not install into the Apps folder under Lion - instead, the executable ends up in the /OPT/LOCAL/BIN/ folder which means, unless you unhide it, you won't be able to see it to run it. I moved the executable into the apps folder and it works fine. But I gotta say, this is the most anti-user mess I have ever experienced.

Ok, enough ranting. Back to writing scripts LOL.

John

Revision history for this message
Joe Blow (johnkzimm) said : 		#2

Well, I got it to working again. For some reason Nightshade does not install into the Apps folder under Lion - instead, the executable ends up in the /OPT/LOCAL/BIN/ folder which means, unless you unhide it, you won't be able to see it to run it. I moved the executable into the apps folder and it works fine. But I gotta say, this is the most anti-user mess I have ever experienced.

Ok, enough ranting. Back to writing scripts LOL.

John