Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
Sign in to follow this  
ImTheOne

NetGear USB WiFi Adapter

6 posts in this topic

Recommended Posts

Ok so i finally got OSx86 Leopard running on my computer, but the only problem now that i didnt think of before was that Mac probably doesnt have a wireless driver for a NetGear WG111T USB 2.0 WiFi Adapter. So i googled it with no luck and was wondering if anyone knew if someone had hacked it to work on Mac or if that was even possible. This would be the only way i could get internet from the computer in my room. thanx

Share this post


Link to post
Share on other sites

Yeah it didnt work it always said program is not responding or something. I crashes my system though so i gotta reinstall it. Any other suggestions that could possibly work? thanx

Share this post


Link to post
Share on other sites

ok thanx i will try it i just dont know how it will work out with the wg111t which is what i have. leopard doesnt seem to be very stable for me, i was guessing it was like that because it was hacked. So i am probably going to try tiger i think i have already said that but i just dont really feel like downloading it. so this will be the 3rd time i reinstall it so hopefully this one wont crash it.

thanx for your help when i get home i will be sure to try it out.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • Up for https://sourceforge.net/p/cloverefiboot/wiki,
    • Has anyone had success/failure with using UPnP working with this Intel Network? I have a onboard Intel I219V2, that is working quite well, except I can't make UPnP work.  It works fine for other devices on my network, and my previous mac Mini.   In fact, I've not been able to get forwarded ports working even if I do them manually.   Any help or pointers towards where to look would be greatly appreciated.     (High Sierra, i7-8700K, ASUS ROG STRIX Z370-G)
    • Hi,  the resoldering complete socket would kill the board totally in couple month (as the guys from super-duper repair shop told me). It's all because of gygabite layered silicon grade. The layers are so thin, that they give 90% chance, that board would work correctly only a couple month until it would die. Even with IR equipment they have, gygabite silicon starting to get micro-bubbly 10-20 C before target desoldering temperature. So they not recommending to do it with this particular z97 lineup.   About pins - they are corrected with a microscope and skilled technician. As they broke right near the start, I won't be able to do it with looking glass I have). He did it quite good, visible that they were repaired, but esthetically looking super good.    As for build and Oz in it.  Current configuration is: Xeon e3 1245v3 CPU Z97hd3 Mobo Msi gtx 1050ti gaming X GF 1) Before pins problem, after I flash anything infused with Oz - it won't work with the graphics card installed. If I pull it out, flash, get bios setting right, boot and reset NVRAM (or clear CMOS, bios setting, NVRAM) than install graphics card - it freezes every boot.   2) If I press the CPU cooler a little bid, just give it a solid push - it kinda boots without a freeze, but not correctly. Bios go flickery.  3) After I pushed CPU couple times, I started to get random BSODS on windows, so I tested RAM. One dim would give me errors. I don't know, is this went after pushed a bid CPU cooler, or it was like that, but using totally different ram would give same freezes with OZ.  4) Tomorrow I would go again to this repair shop, they would try to perform another round of magic tricks. As this mobo work correctly (fully) with windows 10 - they not recommending it for full socket resolder. damaged pins were reserved. Maybe OZ uses them after all, but they were repaired. It's all looking magic, but there is no magic. If swapping not XEON CPU won't help it (but I saw builds with OZ and XEON), then I would search for another board or platform.       
    • You can try this one here 2.9.0 let me know if its better for you ?   VoodooHDA.kext.zip
    •   Boot option name retrieval 1) Locate the booter image as explained blow. 2) Locate ".contentDetails" in the parent folder 2.1) if unsuccessful, locate ".disk_label.contentDetails" in the parent folder 2.2) if unsuccessful, retrieve the volume's name   HFS Boot 1) Retrieve blessed file via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L41 1.1) if unsuccessful, retrieve blessed folder via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L45, append "\\boot.efi". NOTE: This is broken in the latest binary I checked. 1.2) if unsuccessful, use the following hard-coded paths: "\System\Library\CoreServices\boot.efi", "\EFI\APPLE\{ARCH}\BOOT.EFI", <StandardEfiPath>, "\\boot.efi" in this order 2) FV2 Recovery does not follow the usual practice because it is not shown by BootPicker anyway. Determine it via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleBless.h#L49, verify it does not match 1).   APFS Boot 1) Determine the APFS Volume Info (and hencefor detect whether it is APFS in the first place) via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L54 1.1) Determine the APFS Container Info via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L36 1.2) Verify the Volume Role via https://github.com/CupertinoNet/EfiPkg/blob/development/Include/Guid/AppleApfsInfo.h#L51 1.3) Retrieve blessed file analoguous to HFS 1). NOTE: This step and 1.3.1) are broken in the binary I checked, hencefor it does not happen, but is probably supposed to. 1.3.1) if unsuccessful, retrieve blessed folder and append the booter name the same way as in HFS 1.2) 1.4) (if unsuccessful,) locate all Volumes that are part of the same container, check whether the current Preboot partition has folders named by the just located Volumes' GUIDs and append the hard-coded paths from HFS 1.2) if existant 2) Recovery detection works the same way as 1.4), just for a Recovery instead of a Preboot volume


×