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 Safeed

  • Rank
    InsanelyMac Protégé
  1. @gazzacbr: Hey, I used the old ethernet_pkg.zip to install my ethernet and it is working fine because the new driver would not work and it would not let me access the network setup page. Now the only problem is that when I use sleep my ethernet stops working. So, I tried to apply the sleep fix for the ethernet but it requires a file that I don't have or it was not included in the ethernet_pkg.zip file or anywhere else for that matter. The sleep fix for the ethernet requires a file called etherner_reload.sh and I need this file to fix the problem. Would you be a gent and upload a copy of your ethernet_reload.sh file please. If you don't have this file maybe Les Paulde can upload the file because if I remember correctly he also had issues with the new driver and he loaded this old driver and fixed it with the sleep fix when he was working out the ethernet load/reload issues. Please if anyone has this file upload it soon so I can fix this problem, thanks in advance. I also bought a Dell 1505 Wireless N Mini PCI-E Card with Broadcom number BCM94321MC off fleebay and in three weeks I will have it to see If I can get my wireless working. I know aimski did test the card and said that it was recognized but could not get it to connect, however, I decided that wireless N is too good to leave it unchecked. I will share the results with everyone here once done. I will try my best effort to install and test it in any way I can and I plan to make it work both on Vista and OS X sides since I have my dual boot Hackbook Pro working most of the way and it only requires a speedy wireless for me to be able to watch movies from Hulu.com uninterrupted wirelessly. Godspeed.
  2. @feeefic2: Okay here is what I did. Acer splits the 320 GB drive in these models into 4 partitions. The first one about 5 GB has system configuration software on it and the forth one seems to be empty and wasted and neither show up in Vista under my computer but under disk utility you can see them both. You should leave these two partitions alone. The second one is called Acer and it is about 144 GB and formatted NTFS that has Vista operating system on it and it is considered the main drive in Vista. You should leave this one alone as well. The third partition is called Data and it is almost 135 GB and also formatted NTFS. This is the partition you should be trying to install your OS X on. First, make sure the Data partition is empty and has no data on it. Next, in Vista control panel click System and Maintenance then find Administrative tools and click on the blue link under it that says: "Create and format hard disk partitions" and this will launch Disk Management in Vista. You should clearly see four partitions. Now, this is what you have to do and it was exactly what I did to prepare the partition for installation of OS X Leopard. You need to find the Data partition 3 about 135 GB in this Disk Management utility then right click on it and choose the option "Delete Volume" then accept by clicking OK on warning. You should see the banner for this volume that was blue now turned green and now it says "Free Space" on it. Now, you right click on this free space and select "Create Simple Volume" and system shows you the maximum available size with options to format this volume with NTFS. Choose the maximum size as it is and click the radio button to format this partition with NTFS, DO NOT choose the "Quick NTFS Format" as it will only erase the file allocation tables and not the drive itself that is not good in case there are encryption technology involved in data formatting/hiding in this partition when it was created by Acer that could interfere with your OS X installation. After a while, you'll have an NTFS partition about 135 GB formatted with NTFS file system but this is only a "Simple Volume" and is not good for your installation. Now, you need to exit this disk utility and click the Vista's start orb and type "cmd" to launch a command prompt screen as we need to use the DISKPART Utility to finalize the process. Once you have a command prompt window open, type DISKPART and start the utility. Now on DISKPART prompt type "select disk 0" without the quotations since these models come only with one physical drive which is drive 0. Now, the focus is on disk 0 and DISKPART says disk 0 is the selected disk drive. AT this point type "list partition" and you should see all four partitions however since we deleted the original Data partition and recreated it again, at this point it is ranked as the fourth partition. WARNING: You MUST be very CAREFUL not to delete your other partitions here. You need to find the "Simple Volume" that we created in Disk Utility and DELETE it again since you cannot convert it to a "Primary Partition" because DISKPART will not allow it. So, carefully verify that partition 4 is indeed the only partition that reads as a "Simple Volume" and if this is the case, then this is the partition we need to DELETE and then recreate again as a "Primary Partition". If, partition 4 is the "Simple Volume" then type "select partition 4" to trun the focus to this partition. DISKPART will announce that partition 4 is now the selected partition. Now, type "delete partition" and this command will prompt DISKPART to delete the selected partition 4. After, you accept the warning, the partition 4 is gone. Now type "create partition primary" and DISKPART will use the maximum available space to create this new primary partition 4 after you hit Enter to OK this process. For a comprehensive view of all DISKPART utility's options and how to use them please refer to this link: http://support.microsoft.com/kb/300415 You may also type ? at the DISKPART prompt to see the options or you may type a command after the word help such as "help create partition". After, you created the primary partition and formatted it using NTFS then you can turn it active by typing the command "active" however you cannot turn this partition active until you have installed your OS X on it. You can return to this utility after the installation of OS X and turn the partition active manually however you should know when an OS installation procedure takes place, the installation wizard always turns the partition active by default to be able to use it as the boot drive, in this case the OS X will be your boot-up OS. This is exactly how I prepared my partition before attempting installation of OS X so that OS X install process would not error out. Also, during the OS X installation procedure you must erase this same volume one more time using the "Mac OS X Extended Journaled" format to prepare the drive a final time for the OS X to install and work properly. I hope this will help you clear your issues. If not try researching the issue more and also try to be very specific about your hardware and your activities should you need additional help here. @Aristotele: Try running the utility Repair Permissions as explained in posting #106 It may help you since it cleared my issue with sound and I added the update for others to see. Good luck, having no sound is a big pain when it comes down to a computer specially a notebook.
  3. @gazzacbr: I figured out the problem with the sound and I have finally fixed the issue that does not require me to run the .wakeup script manually in order to activate the sound after machine bootup. I booted from the iDeneb ...v2 DVD and after clicking next I got to the installation screen. But, all I had to do was to click on the Utilities and then click Disk Utility and then on the left pane select my OSX volume then in right pane click Verify Disk Permissions. After this was complete, I had 2 issues. The first one was something about an invalid path for a file or a folder message and the second one was: Empty path in "com.apple.repair-permissions.pkg-group" receipt Unfortunately, I did not write down the first issue specifically but then I clicked Repair Disk Permissions and after it was done, only one issue was left, the one that is listed above verbatim from the screen. I tried to run the Repair Disk Permissions two more times to fix the above issue but it did not clear. So, I quit the Disk Utility and rebooted using my OSX volume this time to see if the sound problem was fixed without me running the .wakeup script and sure thing the sound was active and stayed on. I rebooted a couple more times and the sound is on after every single bootup, so it took care of it. Now, the above issue with Empty path is a known issue that Apple has put on their "You Can Ignore" list but some people were able to get rid of it by downloading the combo update for OS X Leopard. I am not worried about it and you should not be either since this Empty Path really reminds me of a well known issue with Windows XP/Vista about Empty Registry Keys. I had those in my previous XP installation and they never caused any problems, not even a slowdown on my OS like some people were mentioning. I do not wish to damage this installation by running a curious update from Apple. I will continue to troubleshoot my issues and once everything is running nice and smooth, I will do a complete mirror backup of all my partitions on my dual boot drive, at that point I can be more open to updating since I can always recover from my backup if all fails, I think this is how we should all proceed to be safe than sorry. I thought everyone should know this finding about the sound and the curious problem with Sleepwatcher but frankly it is not an issue with Sleepwatcher but with Apple OSX Disk Permissions. I hope this update about the sound can help some people here.
  4. @gazzacbr: Hey, I found out a way to run the .wakeup script at login for people like me that their sound does not get activated by Sleepwatcher program. If you put a copy of the .wakeup script somewhere on your OSX Dock and then right click on it's icon you get an option "Open at Login". I tested using this option to run the .wakeup script automatically and it works perfectly. The only annoying thing is that you have to manually close the Terminal screen that is left behind from the script execution. I know for sure that there is a way to run this script in the backgroud and in silent or non-verbose mode but since I have forgotten most scripting commands, I could not manage to get it to run silently and automatically at the same time. I was however able to run it in background using the command "bg .wakeup" and it worked and the script runs at startup or login but it is still in verbose mode which results in the Terminal logout screen to be left behind that you have to close manually. If you or any of the other guys can manage the proper command for running the .wakeup script silently and in the background this procedure definitely works. Maybe you, Les Paulde or DPyro can come up with the proper command for this. I have to also mention, this is in addition to the way Sleepwatcher runs the .wakeup script since you still need that to run the .wakeup script after you bring back your machine from sleep. Please see if you can remember how to run this script both in background and in silent mode as it will make the OS look perfect at bootup without having to see the extra screen that you have to close all the time. Also, do you know what is the update with the wireless, any luck yet?
  5. @feeefic2: Okay, I can see most of your problem from your reply. First of all, the booting from a USB stick is not the same as a fixed drive from an operating system point of view, this said I believe this to be half the problem. To fix this first, try to install a physical hard drive with a Windows OS such as XP or Vista on one partition and fully functional then create another partition (at least 20 Gig, mine is 135 Gig) for the Apple OS X and make sure this partition if also formatted with NTFS and free and clear of any data. This hard drive can be IDE or SATA or SATA2 (mine is SATA2 300) and that is really irrelevant at this point as I/O handling has nothing really to do with OS installation. Since at this level when you do not have an OS and you are trying to install an OS from a CD or DVD all I/O gets handled by a combination of the BIOS hardware and the kernel of the OS's Installation CD or DVD and in this case Apple OS X will handle the I/O if your BIOS could pass a hard drive IDE or SATA or SATA2 without a problem, ready to go and show to the OS X that it is a FIXED drive. Most kernels do not handle the removable drives such as a USB stick very well or go into a shock like OS X did here and that is your kernel state of panic. The second part that causes the kernel panic is the MFT on these removable USB sticks or generally most removable media since somehow they tend to look different than a fixed drive and that's how strange they are. Second, download the following tutorial written by Les Paulde here: InsanelyMac Forum > [How To] Install Mac OS X 10.5.6 on Acer Aspire 6920g Next, set your BIOS to boot from your DVD drive first and then find and download the following: iDeneb v1.4 (XxX_x86_10.5.6_Install_Disc_Universal_Final.v2) This is the installation DVD with the NTFS support package included in it. When you start your installation from this iDeneb v1.4 (XxX_x86_10.5.6_Install_Disc_Universal_Final.v2) version of the DVD according to the step by step tutorial, you will see when you need to add the NTFS support package to your installation and proceed. This is the package that I was mentioning to you. After, you add all the packages according to the tutorial follow the installation steps and make sure to erase your NTFS partition that you are trying to install OS X to and it is very important to select "Mac OS X Extended Journaled" from the format type drop down menu. I believe if you do all these you should be fine and you can proceed to install your OS X.
  6. @gazzacbr: I totally agree about the OSX being a pain in some ways and for a really formidable OS that is built on UNIX backbone for heaven's sake it should be a lot smarter as far as handling drivers and hardware. But I think the issue is that Apple does not want to make hacking their OS too easy in order to keep the hardware builders that can become their hard line competitors at bay to keep them out of Apple's business for good. After all, Apple sales more hardware (and expensive ones too) than software. They are not like Microsoft which is exclusively a software company that refuses to get involved in hardware business. Microsoft lets other companies make hardware to run their software, but most of the time they certainly make sure to convince those companies to make hardware that primarily would run their software smoothly and they don't care if that piece of hardware could not run any other software. That's how the monopoly runs in Microsoft's vains and it is deep rooted in the company. Anyhow, enough said. I was going to mention that you can make a copy of the .wakeup script and place it on the desktop near your drive icons and as soon as your desktop loads you can double click that icon in which it automatically opens Terminal and executes the script to activate your sound. However, at the end of the script's execution when Terminal window logs out, it remains open and you should close it manually. If I remember correctly from my unix programming days way back, you could also insert a couple of lines of command to .wakeup script in order to close the Terminal session after it runs the script almost like a .bat file in the old MS-DOS. I can't remember what or how but I'm sure it is certainly do-able. Some unix commands are very similar in behavior to DOS in the way they act. I believe the commands that can be added to .wakeup script are key stroke emulation type and can be embedded within the script itself in order to close it after execution almost like when a function or subroutine exits to main once it's done. After all, scripts are nothing but unorganized standalone subroutines that do not pass any parameters back to anything like a main process, they are instead a cheap way of getting what you immediately need at the moment like a sandwich except less tasty. However, I really think we should figure out how to run the damn thing and force it to make the sound activated at machine startup to make things run the way we want them not the way OSX wants to. I am going to try a few things and If I figure it out, I'll post my findings here. @feeefic2: I believe you got a kernel panic here and it is because of the FAT32 formatting. If you have no data on the partition format it using NTFS file system then include the - NTFS support package as it is stated at the beginning on page one of the OSX Install Tutorial here written by Les Paulde in order to enable full read/write access to NTFS drives and avoid a kernel panic. If you have any data on the partition which would be kinda odd since you're trying to install OSX at this time and the partition should be empty and later you will have to erase it using the OSX installation wizard during the install process. However, if that is the case you must backup your data first and then proceed to format the partition with NTFS file system. Then later during the install process you will erase the partition with OSX installation wizard by chooing the "MAC OS X Extended Journaled" and the wizard will format the partition a second time from NTFS to this format specifically in order to work with OSX. The included NTFS support package will also make it possible for you to access any other NTFS partitions or drives that you may have in your PC. Remember, only data files are usable while operating in cross-platform situation. Data files such as music files, picture files, documents and so on and NOT any programs, utilities or executable codes since programs, utilities and executable codes are OS specific but data is always sharable between different OS. I hope this helps.
  7. @ gazzacbr: Hey man thanks it worked, I have my sound working now. However, it does not work at bootup even though I have made all the adjustments recommended including the creation of the .wakeup script and making sure it is executable, changing to no password for my username and also installing a fresh copy of the Sleepwatcher and it's Startup Daemon. I checked the console and based on the log it seems that Sleepwatcher gets started and the session gets terminated but I am not sure if it executes the .wakeup script before getting terminated since I have no sound at bootup. But, If I run the .wakeup script either manually or telling the machine to sleep then wake it up in both cases the sound becomes activated immediately. Correct me If I'm wrong but I am not positive if the Sleepwatcher runs the .wakeup script at startup since it seems that this program is intended only to handle the sleep and wakeup events and it won't get triggered at bootup like we want it to. I believe the active process for Sleepwatcher gets started and then it goes into a waiting state for those two specific events, either sleep or wakeup. I don't know if the program considers the boot event a wakeup event or not. I tried to place the .wakeup script in the System/Startupitems folder and see if it would execute since now it is marked as "executable" but it did not run to activate the sound for me so I took it out. But I am almost positive that we can tell the Terminal to run the .wakeup script at bootup in silent non verbose mode without the use of Sleepwtcher for the boot event so that the sound becomes activated at machine startup. I worked with UNIX extensively some 20 years ago in a programming group of 9, however I suffer from the common symptom of "If you don't use it, you lose it." and also somewhat of information overload. I think if I start refreshing my memory it will come back to me very quickly. If you or anyone else have any suggestions that I could try, it would be great since now I have sound, Yeahhh;) Are you or anyone else having the same issue with the sound not going active due to non working of Sleepwatcher process. I believe "Les Paulde" had this problem if I read it correctly but did he or anyone get the sound to work right after bootup without executing the script manually because as I said I have not been able to do that. My machine boots up in a dead silence mode. Also, what is the purpose of Sleepwatcher Startup Daemon if it does not trigger to run a script, is it merely to get the Sleepwatcher Process started at bootup so that it awaits a sleep or wakeup event? If the Sleepwatcher Startup Daemon can execute the .wakeup event at bootup how can I set that up because I tried to find the program folder in Spotlight and I could not find it to play around and see if I could fix this issue. I have also ran the command to unhide the hidden system files but still could not find where Sleepwatcher or it's Startup Daemon has been installed in the system, of course I did not look a very long time, only a couple of minutes. I certainly appreciate the help from all members of this forum, after all good help is hard to come by these days since you get a lot of misinformation and bad advice but it seems to me that people here know what the heck they are talking about and for this I say more power to all you guys, namely Les Paulde, DPyro, gazzacbr and anyone that is actively contributing to help build a knowledgeable base. Thank you all and special thanks for the hard work in creating the tutorial Les Paulde, great work.
  8. Hi everyone, I'm new to this forum but I really like how everyone works together to nail down the issues. I used this tutorial and installed iDeneb v2 and I had all the issues but thanks to you all I was able to clear some of them. My sound is acting very strangely. I have installed the 889 driver and I have the icon in my top menubar and in the System Preferences I can access and adjust all the sliders and tabs, however I do not hear anything at all even with volume up and Internal Speakers chosen as Output Device, absolutely frustrating. So I believe here is a good one for you DPyro since you said you can check into it because this is really strange. I believe a while ago someone else was reporting this same issue but they said after three reboots their sound magically started working. But I was not that lucky and it does not want to work no matter however many reboots I do. Please give me some ideas to try and DPyro if you can find out what is happening that would be wonderful. I must also add that I tried the 888 driver and 888d and they even did not activate the device so there was no icon in the top bar. So, I had to go back to 889 driver that was at least partially there but without sound. ALso, I have a new problem that I do not know if anybody else has or not. I found out that my clock at the top bar works only while my Acer 6920 is on but if I shut down, it stops working and therefor when I boot up there is a significant time lost like many many hours and this is very annoying but I wondered if this has anything to do with my sound not being heard at all. Any help with these two issues would be greatly appreciated from you guys. I will keep an eye on this board for any ideas you guys can throw at these problems. ThanX.