| ||||||||
General Mac OS X Discussion General Apple and Mac OS X Discussion
|
| | LinkBack | Thread Tools | Display Modes |
(#21)
|
| Junior Member Posts: 25 Join Date: Feb 2010 Location: Perth, Australia | Quote:
./Applications/Safari.app ./Library/Widgets/Web Clip.wdgt ./System/Library/Frameworks/JavaScriptCore.framework ./System/Library/Frameworks/PubSub.framework ./System/Library/Frameworks/WebKit.framework ./System/Library/LaunchAgents/com.apple.PubSub.Agent.plist ./System/Library/LaunchAgents/com.apple.WebKit.PluginAgent.plist ./System/Library/PrivateFrameworks/JavaScriptGlue.framework ./System/Library/PrivateFrameworks/Safari.framework ./System/Library/PrivateFrameworks/SyndicationUI.framework ./usr/bin/pubsub ./usr/share/man/man1/pubsub.1 So, other than updating the Safari application, it is updating the Web Clip DashBoard widget. It is also updating a bunch of Frameworks and PrivateFrameworks to do with WebKit, JavaScript and PubSub (which appears to be related to RSS/Atom feeds). It is also updating a couple of LaunchAgents, related to PubSub and WebKit. Finally it updates a command line utility (in /usr/bin) and its associated man page, which is used to manage RSS/Atom feeds. Despite the fact it is updating a bunch of Frameworks, there is nothing there which is touching the kernel, drivers or kexts. From my limited understanding of NBI, there is nothing that has been changed that NBI would be able to "fix". The fact that Frameworks and LaunchAgents have been changed could cause issues during a boot but I don't see how this is related to anything that NBI could fix. Does anyone have a better understanding of exactly what NBI can (and can't) fix? MacBook (13" Aluminium) | 2.4GHz Core 2 Duo | OS X 10.6.3 | 2GB RAM | 250 GB HDD Mac Mini Server | 2.53GHz Core 2 Duo | OS X 10.6.3 Server | 4GB RAM | 6TB HDD PowerBook G4 12" | 1.5GHz PPC G4 | OS X 10.4.11 | 512MB RAM | 160GB HDD | |
| | |
(#22)
|
(#23)
|
(#24)
|
(#25)
|
| Senior Member Posts: 122 Join Date: Aug 2009 | One of the USBs should be the install "DVD", so, boot into that, but, don't install. That USB or the other one should have the DellEFI program on it. Run DellEFI from the appropriate USB. BIOS A05 | USB Legacy: ON | USB Wake: OFF | Bluetooth: OFF | NBI .8.4 RC1.1 (20100616212351) Sleep: Working | Speakers: Working | Headphone Jack: Working |
| | |
(#26)
|
(#27)
|
| Junior Member Posts: 7 Join Date: Feb 2010 | Quote:
It may very well share some libraries, but it will not be modifying any kexts, the kernel, DSDTs, boot loader or smbios/boot.plist files. If it's not touching any of those, NBI won't make a difference whatsoever. To claim a problem that NBI fixed means he'll have to DESCRIBE the problem that NBI fixed, and why. Such categorical statements really mislead others into believing there are problems when there are none. NBI is not snake oil, it simply automates a process most people aren't willing to do by themselves. In fact, NBI isn't even necessary to run OS X on the 10v if you've a solid understanding of operating system fundamentals. | |
| | |
(#28)
|
| Junior Member Posts: 21 Join Date: Nov 2008 | Quote:
I'm feeling like a rookie. I'm able to boot into the installation routine but how can I get access to the DellEFI files on the stick? | |
| | |
(#29)
|
(#30)
|
![]() |
| Thread Tools | |
| Display Modes | |
| |
Copyright © 2008-2011 MyDellMini.com.










Linear Mode