Jump to content
4 posts in this topic

Recommended Posts

Hi again,

 

I just installed Kalyway 10.5.2 (thought it would be the easiest way to get GUID) and none of the window/view settings are being remembered. A quick trip to the terminal reveals that .DS_Store files are somehow being surpressed (not just for network volumes, but the startup volume, too!). Does anyone know how to re-enable the creation of these files?

I fixed it. It's a bug in the Kalyway disc. I believe Kalyway's modded Finder has something to do with it (why was this modded anyway?). I was not getting any .DS_Store files until replacing it with the Vanilla Finder from my BrazilMac installation (I kept a backup, fortunately). With the Vanilla Finder, I started getting .DS_store files again, except for the "/" directory, and its immediate children. I then discovered that the permissions were wrong for "/"; it's supposed to Admin +rw, and not wheel. Repairing permissions in Disk Utility didn't work; it must be done manually.

 

Anyway, window/icon positions are now retained after rebooting!!!! Now go forth and spread your newfound wisdom...

 

Incidentally, I'm not 100% sure the problem was the Finder. I was messing with other stuff, too, but I'm pretty sure the Finder is part of it.

m8, would you know if this would effect the creation of Aliases, I am trying to make a media Center using front row (I really like the Leopard front row interface) and the only successful install I can get working on my Prescott based celeron system is Kalyway 10.5.2. I have a central server with my content on, but this is on my network and the only way I know for me to make this viewable in Front Row is to make an alias to the drive...but the Kalyway install will not let me make aliases.

 

If so, I would love if I could get that Vanilla finder and what commands you used to correct the permissions. I am a noob with this stuff

 

Thanks in advance.

I don't know if this affects aliases. If it won't let you make an alias, you could try doing it as root. You have two options: Option A is to use the Terminal and the "sudo ln -s " command; Option B is to enable root access, an log in as root. I think the latter is done via the Directory Utility -- Google ought to know.

×
×
  • Create New...