Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About be-clear

  • Rank
  • Birthday 09/19/1950

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To be clear, I'm getting a one line BOOT0: ERROR message on a black screen. I've looked up this error and all YOUTUBE tutorials use Chimera or other type of software or go on to explain about 4K disk segments. These explanations are way above my understanding. Am I missing some preparatory step prior to attempting to simply boot from my USB drive?
  2. I'm a complete neubie. How do I 'switch' EFI? I'm using a DELL E6430 laptop, and I was able to setup an EFI boot but was unsure as to whether to use CLOVER or MAC BOOT. I chose the former but later on, upon failure, I tried 'Legacy ROM boot', and I no longer see the EFI option. I have set the BIOS to 'defaults' to no avail. Ah! This time I tried the latest 'Monterey' distro, thinking that perhaps something was wrong with the Big Sur distro. I'm able to browse the contents of the USB drive using TransMac and see all directories, which suggest the 'restore' from image did work ok. Was that a proper 'load' of the DMG on the USB? I formatted the USB 'for Mac' and then proceeded to right click on it and selected to 'restore' from the DMG file. Please advise whether I'm missing something. Thanks!
  3. Hi! I have tried several times, following instructions to the letter, to boot from my USB drive to install the latest Nirash Big Sur distro; but each time my laptop fails to detect it as a bootable device. I have tried UEFI, CMS, AHCI, Compatibility settings, disabled SecureBoot in my BIOS, to no avail. I can explore its contents in Mac and Windows and I see all directories, so it appears to be ok. However, if I insert it on my Mac and attempt to boot from the USB, macOS detects it but when chosen, the screen goes blank. This tells me something is defective. I have created the bootable USB from Windows, using MacTrans and PowerISO on Windows, but both fail to work. I would appreciate all and any help.
  4. be-clear


    You need to have an apple ID to be able to download Xcode, which includes Swift2 and other tools. You also need the ID in order to obtain a "developer" kind of ID that would allow you to download Xcode. I recommend you try UDEMY.com. They have iOS development courses for less than $20, and membership lasts for a year. So you have this time to try your best at becoming a developer. That's what I'm doing as we "chat" through this medium. Good luck!
  5. Hi! I'm a complete newbee, so I apologize if I got my perceptions wrong about what I've been reading for the past week or so, which, I MUST say, has rendered me more confused than illuminated. I understand that after a successful install of - in my case - of Yosemite using a Yosemite.zone USB install, I end up with a crippled laptop but basically working. I assume that I have no native DSDT nor SSDT files sitting in their respective directories - because I have looked for them and they are nowhere to be found - and I'm still unclear as to where my Hackintosh is booting from. Below I've attached a text file containing my TOSHIBA S855 Satellite laptop's specs. I have managed to find a very important kext file to activate my AMD Radeon 7600 graphics card. The installed/running vanilla VGA driver gives me only 1024 x 768 resolution and flashes constantly, making typing and/or reading very frustrating and difficult. Also, the window's control buttons and bar get obscured or completely disappear frequently, adding to the frustration. I have managed to EXTRACT A CLEAN DSDT.aml file from the same laptop, in a Windows 7 environment - I dual boot using Chimera - which I managed to clean up until it compiles ok. I've also attached the clean - .asl - text version of this, prior to compilation. I still have several devices that aren't recognized, such as bluetooth, card reader, wi-fi, sound, USB2.0 (3.0 works). I feel lucky that most devices other people have problems with, work in my case, such as sleep, battery, cpu, touchpad, DVD, etc. Now the questions are: 1 - Will this compiled DSDT.AML file still need further tweaking with additional patches (kext files)? I seem to believe that is the case from posts I've read from other users attempting similar results with their hardware. 2 - Assuming I have successfully compiled this patched dsdt.aml file, how do I go about placing it, and its counterpart SSDT.aml, where they are expected by the OS to boot? 3 - I followed the instructions attached to the Radeon kext, using the tools - attached to the downloaded zip file - to patch the (I assume) existing dsdt file, and watched the substitution of an existing AMD 7600 kext in some system folder. I took the chance to reboot after this, expecting the laptop to use the new kext, but nothing happened, luckily! I could easily have ruined my half-ass installation, being uncertain of what I was doing! 4 - I used DiskUtility to be able to locate the supposedly existing EFI (UEFI?) partition where one of these files reside, to no avail. Is such partition created using the mentioned USB install? 5 - If that is not the case, do I need such partition? 6 - If answer to 4 is YES, how do I create it without disturbing my existing setup? 7 - Does the Mac not check for installed hardware during installation of the OS, just like Windows does? 8 - I've seen some non-Mac supported devices' kext files - like AMD for graphics and sound in some system folders. Am I right to assume this is the good work of the people who customized the install tools? 9 - If answer to 7 is yes, then, why does the Mac not detect the non-supported hardware with the ADDED kext files I just mentioned? As you all can see, I'm completely baffled by all this, and would certainly appreciate any help some good samaritan may bring forth. Thanks! I look forward to receiving some replies. revised dsdt.adsl toshibas855specs.txt
  • Create New...