Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About zoro2

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
  1. I have an odd sleep problem. I don't know if this would help to know or not? If I leave myself logged in it goes to sleep and AFAIK it wakes up even much later just fine. But, If I log out and it goes to sleep, it gets to a place, not immediately but after some time, where it wont wake up at all. I have to reboot. The only KEXT I use that I think is related to sleep is: NullCPUPowerManagement.kext.
  2. Netflix DRM 8152 ***Snow Leopard***

    I would like to see this tread revisited. I am having the same error with Netflicks Feb 2010. THe woman on the phone would not give me a tech person. The question she asked made me suspicious. She asked, are you running this on an apple machine with a real engraved Mac logo on the front of the computer? I had said yes as I do have an APPle logo stuck to my case. But I knew she was really asking if my Mac was real of not. I think they are on to us. I have tried all I have seen in this thread and all I have read. IT is giving the DRM error and will not play no mater what I do. Arrgh.
  3. Sorry I can't remember what steps I took exactly, but last spring I did my first hackintosh build from scratch. I did the same thing, software raid on two 500 drives. I forget the thread but there was one that may have talked about the why of your problem. Unless I am totally misreading you, there has to be a small partition the system can boot to, then hand off to a raid disk in the raid array. I ended up with an inelegant solution but a working one. I created to small drives (was recommended to put the same on each of the two raid drives although one is pretty useless) My raid boots fine but it boots to the small startup drive and finishes booting on the Raid drive. SO it actually appears to boot raid. If it had no other drive to look for pre-raid, it could not boot into raid. Is your drive which cannot be disconnected part of your raid set up without realizing it? It has to go somewhere before raid boot.
  4. Hey all, thanks for all the past help in resurrecting my drives. Been error free for the most part for .. a month? Regarding the discussions on DSDT, I have the DSDT SE app, don't know if there is a better one but this seems a good choice. I have seen some discussions about this but not an actual tutorial. Is there a link for this? My sound has been working well. My first installation had some problems and I had to reinstall a few times to get it all working. Now I am getting back into some pro audio stuff and now I am noticing that the sound may not be set up as well as I thought. Using a Focusrite Saffire DSP, a Sure Mic, and Logic Express I have been recording some audio books. The problem is that, during playback (Mic disconnected) I have my KRK monitors outputting sound via the Focusrite driver for out as well as input. But they also have the system alerts set at very high volume. I can adjust the sound for the tracks via the Focusrite Saffire control panel. But I am no longer able to touch the sound level for system. There appears to be no settings to adjust the system volume when used with these drivers. I thought I was going to blow my speakers the other day, or my hears. I was listening to what I recorded and an alarm I had set went off with just a click - sounded like a gunshot. I have looked in the obvious place, the system/sound panel. There is a setting for system sounds that is separate from input driver selection and output driver selection. It very clearly says "Sound Effects" and allows a choice of all the same sources as the IN and the Out. So in theory I should be able to choose Focusrite driver for audio in, Focusrite driver for line out and line out (the normal speaker output) for system alerts. But it is not working this way. The system alert and system sounds work through the same as the external, whatever that is set to. Just now I have set the output to non Focusrite as I don't have a recording session scheduled at the moment. Back to DSDT. Assuming this will tell me all I Need to know once I follow a tutorial and find errors pertaining to my sound board, is this rather large file something that I could take and paste into a word processor , edit, and return as save (and use)? What I really want to know is whether it would work to use Panorama, my favorite database app to make something for creating a macro to crunch the data in a very large file rapidly. Pan is Ram based and it imports a 10k text file faster than you can get your finger off the mouse button. It crunches data and exports it just as fast. But again, I need to read more about what has to be done, what sort of errors I should be looking for, etc. Thanks.
  5. Progress. I am almost back on track now. Getting a KP after successfully booting and while checking with Apple for updates. Didn't do this before but, oh well. Downloading the 10.6.2 combo update from APple now via the working 10.5 drive. Hoping the KP will go away once I am all updated. But that has to be done regardless so, one thing at a time. Curiously, on the Apple site, one line about the 10.6.2 combo updater stands out. It said (emphasis mine): WHat a surprise.
  6. SHould be the blue ones. I will have to check, been a while. ADDED: Yep, blue. I can't remember the reason anymore but blue is more reliable or some such. OK... Started out on a IIsi, then 7600, 9600. Enjoyed tweaking the XLR8 chip I bought and kept wanting more. I guess watching my friends and their PCs I just have to confess to a bad case of BIOS envy. I love being able to tweak a system so much. And, I Love the MDD G4 case, practically industrial art IMHO. But it was never really upgradable. SO I began resenting Apples occasional "back water Mac" releases that you just could not do much with, like the MDD G4. Of course my new system is geekbenched at (almost) a full 10X speed of my old G4, and that feels good too. Well, I guess I am a magnate for these things of late. I am thinking that, as this bootable drive is relatively fresh, and the RAID is still working I May just grab any new files off the disk, and do the scorched earth thing. Erase the SNL disk, start over. If I do that, I am pretty confident now that I know which installer packages work. I would not choose any migrated files. What I find to be confusing is how when I do a plain Jane install of the system, no migrated accounts, the machine puts my current user name on the new account. Then when I used migration assistant, now only CCC, to move over my files, I Was moving over similar named accounts. I am still a little unsure about which folders to migrate over (using CCC from now on) when I get to that step? I am thinking just move the documents and the apps folders. It would be nice if they stayed registered, but I have wasted a very large chunk of my time (as well as gotten time on this list where I am sure others are waiting for time as well) To answer the question, I have three accounts on this disk at the moment, one for a guest, one for me from my old RAID migrated account, and one for me with a slight alteration in my name for the account I created when I last installed SNL. Unless I hear differently, I will go that route, clean house tonight and start fresh in the morning. Thanks all very much. ON top of that one way I tried to fix the sound problem was to reinstall SNL over a working SNL bootable system. But, the fresh loaded SNL was 10.6 where the system I was replacing is 10.6.2. Sound did recover. And sound sounds much better, stronger, clearer, than it did in 10.5. Not sure why but it's noticeably better.
  7. It does. I will allow you to review what I just posted. IF no comment or suggested changes, I will do the second part, boot and try to name Admin access for this user. Much thanks
  8. I know, right? Hard to get back to productivity till it's all back. My girlfreinds getting suspicious too, seems I am spending more time trying to fix this problem than pay attention to her. Actually, aside from raw beginnings last spring, once this machine got running it has been pretty sweet. Looking forward to normal - whatever that is.
  9. Isn't there a way to repair permissions? I tried doing that with DU from the Leopard drive. It said it repaired permission but only took a half a second, so I doubt it. How do I repair permissions while booted in single user mode? This time I got similar results, but slightly different. THe "/sbin/mount -uw /" wasn't used with the final slash mark, it made a difference. While it allowed me to change the root password, allegedly ... it gave me the following error: unable to change the password for the record root eDSRecordNotFound WHat did you mean that you got different permissions? IS there a standard install set up that if you have it, I should have it just the same? If so, and there is no way to repair permissions, what are my options? Ongoing thanks for your time.
  10. Boot method to single user: Chameleon screen, select boot drive. THen hit down arrow. Pop up menu on screen for booting ignoring caches (tried that but not different), booting single user, etc. Booted single user again. Trying :/ root# passwd root Note that at this point it is showing just as I have typed. IT is not showing my username and root, just ":/root" Result: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache dyld: shared cached file was build against a different libSystem.dylib, ignoring cache Launch_mesg(): socket is not connected Passwd: unable to open directory node with name /local/default. Node wasn't found. :/root# Any hope?
  11. Not yet. I printed your last post and booted in single user. Result: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache dyld: shared cached file was build against a different libSystem.dylib, ignoring cache /sbin/fsck -fy /sbin/mount -uw / #root: (TYPING:) /sbin/fsck -fy -sh: /sbin/fsck: no such file or directory #root: (TYPING:) /sbin/mount -uw / root_device on / (hfs. local. read-only, journaled) devfs on / dev(devfs. local. nobrowse #root: Unless I have misunderstood and when it prompts "#root:" is where I only need put in a password, it did not work. Why is the following line appearing so aften? I have never seen it before and it would seem to be a part of this problem? Ongoing thanks. I have a 1 gig Fantom Green Drive, external. It runs eSata or USB and it does not click.
  12. No, it always says on this drive that; "... is not in the sudoers file. This incident will be reported." I think we are stuck. Maybe running the DD script a couple times from the other drive, trying the various rebuild cache options? It sound like the caches are messed up. Please be aware, this machine is still running the installed SNL 10.6. I have not run the updater to 10.6.2 because I have no access privileges to change anything. I don't know if that helps but, FWIW. THanks.
  13. No, it is still not working. Staying only on teh SNL machine from now on. THe problem is the terminal starts with the error: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache I get the idea that this line should not be popping up (thrice) on the terminal just by opening the terminal. I have tried sudo update_dyld_shared_cache -force but it apparently makes no difference. afaik the only way I have proven that there is no password at root level is from the other machine. When I try SU and every password I wrote down Termainl responds "Sorry, try again". When I try "passwd root" (and try a new password) I get dyld: shared cached file was build against a different libSystem.dylib, ignoring cache and then "authentication token failure"
  14. You are correct in what you say, however it is not taking. Yes, it was at bash-3.2#. But I used the passwd root as suggested and put in a root password. I wrote it down and it seemed to have taken. But as I have not been able to gain access with any method discussed, I tried two other times to change the password just to get one to stick. Each time I am writing them down. Just now I tried (logged into SNL) in the Terminal. $ passwd root This gave me the following. It looked like it accepted my password, the I put in the new password, then put in the new password a second time to confirm it. Then it gave me a complaint about a shared cache file and said I have an authentication token failure. $ passwd root dyld: shared cached file was build against a different libSystem.dylib, ignoring cache Changing password for root. Old Password: New Password: Retype New Password: passwd: authentication token failure What is that? And, no I Can't click on the lock and type root for the user and blank password field, or any of the root passwords I thought I had entered preciously. Yes, there is still no admin account on this boot, but there are three bootable accounts. Root appears to have accepted the password, but has a token failure. Worse, it complains that I am not in the sudoers contents. Which seems crazy as it is my computer and of course I would be in the sudoers contents... Thoughts? THanks. ADDED: I just booted back to my Leopard RAID drive. sudi -s and my login pass gives the empty bash-3.2# reference. It seems that in OSX if I Have root access in one account, I would have it in every account. But it seems not to be so? I just reverified that nothing I try with the boot disk with no admin accounts will allow me in to the admin or the root level. Yes, as you said this is at bash-3.2# from sudo -s on this raid drive, but none of your suggestions will take when booted back to the no admin drive. I even tried the sudo update_dyld_shared_cache -force but that did no good that Ic could see. Sigh, thanks for all your time. I am tired. Maybe some sleep will make this more clear to me.
  15. OK, I guess I have not understood this so it isn't that obvious. I have read about Admin and root being similar but not the same. Thus far I have not looked at root. What you are saying is that on this working RAID system, I can input sudo - s (current admin password) then after bash-3.2# I can put in passwd root. Sorry, this is really a new concept, following the Apple Developers Page: Mac OS X v10.5 From the Finder's Go menu, choose Utilities. Open Directory Utility. Click the lock in the Directory Utility window. Enter an administrator account name and password, then click OK. Choose Enable Root User from the Edit menu. Enter the root password you wish to use in both the Password and Verify fields, then click OK. Did this just now. I have a root user ID then. I will now try the reboot and see what happens. ADDED: OK, back now. No luck on the other drive. Yes I Now have a root password, although not a root ID. I assume the root ID is "root"? I now have "Other" added to this value for log in privileges. It accepts the Root password I put in last. But the target disk does exactly the same as before. I cannot get in with the new root values. --------------- Gatherd data from target external boot drive: sudo -s dyld: shared cached file was build against a different libSystem.dylib, ignoring cache Password: Sorry, try again. Password: zoro2 is not in the sudoers file. This incident will be reported. zoro2-Mac-Pro:~ zoro2 $ --------------- Weird, reported to whom? Definitely open to suggestions here. ADDED: There is a thread, here and here (this has some outdated info as Netinfo Manager appears to be no longer a part of 10.5 and above. THis is referenced here) on how to edit a suduers file using visudo. I am not going to mess things up without further feedback, but would this be a good direction? - Thanks ADDED: I am not at all clear about all of this. I enterd the root password as you sugested, but I don't seem to need it. Am I reading the following sudoers contents correctly, that; # Same thing without a password # %wheel ALL=(ALL) NOPASSWD: ALL Means a password actually does not matter? Not good if true. Here is the contents of suduers; Mac-Pro:~ zoro2$ sudo cat /etc/sudoers Password: # sudoers file. # # This file MUST be edited with the 'visudo' command as root. # # See the sudoers man page for the details on how to write a sudoers file. # # Host alias specification # User alias specification # Cmnd alias specification # Defaults specification Defaults env_reset Defaults env_keep += "BLOCKSIZE" Defaults env_keep += "COLORFGBG COLORTERM" Defaults env_keep += "__CF_USER_TEXT_ENCODING" Defaults env_keep += "CHARSET LANG LANGUAGE LC_ALL LC_COLLATE LC_CTYPE" Defaults env_keep += "LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIME" Defaults env_keep += "LINES COLUMNS" Defaults env_keep += "LSCOLORS" Defaults env_keep += "SSH_AUTH_SOCK" Defaults env_keep += "TZ" Defaults env_keep += "DISPLAY XAUTHORIZATION XAUTHORITY" Defaults env_keep += "EDITOR VISUAL" # Runas alias specification # User privilege specification root ALL=(ALL) ALL %admin ALL=(ALL) ALL # Uncomment to allow people in group wheel to run all commands # %wheel ALL=(ALL) ALL # Same thing without a password # %wheel ALL=(ALL) NOPASSWD: ALL # Samples # %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom # %users localhost=/sbin/shutdown -h now