Knowledge (XXG)

Extension conflict

Source 📝

149:) made system calls. Generally, once an extension completed its task, it was supposed to pass on the (possibly modified) system call to the operating system's routine. If multiple extensions want to patch the same system call, they end up receiving the call in a chain, the first extension in line passing it on to the next, and so on in the order they are loaded, until the last extension passes to the operating system. If an extension does not hand the next extension in line what it is expecting, problems occur; ranging from unexpected behavior to full system crashes. This is triggered by several factors such as carelessly programmed and malicious extensions that change or disrupt the way part of the system software works. 22: 211:
All of this was mitigated by the ease with which extensions and the operating system itself could be swapped in and out: Instead of modifying configuration files as on other operating systems, extensions and other automatically run software simply had to reside in a particular subfolder of the System
203:
were third party utilities that automatically detected conflicts and problematic extensions and other software executing at boot, otherwise a time-consuming task that required users to turn off extensions in sets until they found the conflict, as well as allowing load order to be altered without
216:
for each System subfolder. In addition, the Mac was perfectly happy to have two (or more) System Folders present on a hard drive. Only the "blessed" System Folder would be loaded at startup. So, when a new version of the operating system was to be installed, or a new application, the user could
207:
The most common time for extension conflicts to start was the release of a new version of the operating system, followed closely by the installation of a complex new application that either conflicted with existing extensions, or installed extensions that conflicted with the existing set.
160:
and general instability. Some users happily loaded every extension they could find on their computer, with little or no impact. Others fastidiously avoided any non-essential extensions as a way of avoiding the problem. Many were judicious in the addition of extensions.
187:, which allowed users to disable specific extensions or groups of extensions at startup when troubleshooting the conflict by pressing the spacebar while the computer boots. This tool was also accessible by opening the Extensions CDEV in the 180:, damaged and outdated extensions were the most common cause of problems. Some users had to remember to turn off problematic extensions when running certain programs. 176:, required a large number of extensions. Many Macintosh users had hundreds of extensions running on their systems, all of varying age and quality. 39: 105: 86: 58: 381: 352: 337: 306: 43: 271: 246: 65: 224:, which uses a different extension mechanism. Software can still add new features to the Mac but instead of requiring a 72: 212:
Folder to be picked up. And load their order could be altered by renaming items in the Finder, based on descending
204:
renaming items. Extensions were only loaded at startup time, meaning that any attempted change required a reboot.
32: 241: 54: 403: 225: 266: 153: 130: 373: 217:
easily duplicate the system folder, perform the install, and then fall back if a problem resulted.
213: 188: 134: 79: 325:
Crossing Platforms A Macintosh/Windows Phrasebook: A Dictionary for Strangers in a Strange Land
377: 333: 329: 323: 302: 298: 292: 157: 365: 196: 173: 146: 138: 232:, which is a safer and more organized approach that cannot destabilize the entire machine. 251: 145:, thus receiving control instead of the operating system when applications (including the 122: 366: 126: 397: 200: 177: 172:
were installed as extensions. In addition, a number of applications, especially
142: 21: 229: 192: 165: 169: 261: 256: 228:, the new method has allowed Apple to push more and more extensions into 152:
In addition, extensions sometimes competed for system resources with
221: 164:
This problem increased during the mid-1990s as resource-hungry
15: 328:. Sebastopol, CA: O'Reilly & Associates, Inc. pp.  220:
Extension conflicts came to an end with the release of
46:. Unsourced material may be challenged and removed. 353:Now Startup Manager 7.0 Versus Conflict Catcher 3 156:, utilities and other extensions, leading to 8: 106:Learn how and when to remove this message 291:Stauffer, Todd; McElhearn, Kirk (2004). 183:Later versions of System 7 included the 283: 137:were bundles of code that extended the 372:. Sebastopol, CA: O'Reilly. pp.  141:'s capabilities by directly patching 7: 121:were sometimes a common nuisance on 44:adding citations to reliable sources 322:Engst, Adam; Pogue, David (1999). 14: 20: 31:needs additional citations for 297:. Almeda, CA: SYBEX. pp.  1: 272:Portable application creators 420: 242:Configuration management 125:computers running the 364:Pogue, David (2003). 247:Dependency management 168:technologies such as 267:Portable application 55:"Extension conflict" 40:improve this article 201:Now Startup Manager 119:Extension conflicts 294:Mastering Mac OS X 214:ASCIIbetical order 185:Extensions Manager 116: 115: 108: 90: 411: 388: 387: 371: 361: 355: 350: 344: 343: 319: 313: 312: 288: 226:kernel extension 197:Conflict Catcher 174:Microsoft Office 139:operating system 111: 104: 100: 97: 91: 89: 48: 24: 16: 419: 418: 414: 413: 412: 410: 409: 408: 394: 393: 392: 391: 384: 363: 362: 358: 351: 347: 340: 321: 320: 316: 309: 290: 289: 285: 280: 252:Dependency hell 238: 123:Apple Macintosh 112: 101: 95: 92: 49: 47: 37: 25: 12: 11: 5: 417: 415: 407: 406: 404:Classic Mac OS 396: 395: 390: 389: 382: 356: 345: 338: 314: 307: 282: 281: 279: 276: 275: 274: 269: 264: 259: 254: 249: 244: 237: 234: 189:Control Panels 127:classic Mac OS 114: 113: 96:September 2018 28: 26: 19: 13: 10: 9: 6: 4: 3: 2: 416: 405: 402: 401: 399: 385: 379: 375: 370: 369: 360: 357: 354: 349: 346: 341: 335: 331: 327: 326: 318: 315: 310: 304: 300: 296: 295: 287: 284: 277: 273: 270: 268: 265: 263: 260: 258: 255: 253: 250: 248: 245: 243: 240: 239: 235: 233: 231: 227: 223: 218: 215: 209: 205: 202: 198: 194: 191:found in the 190: 186: 181: 179: 175: 171: 167: 162: 159: 155: 150: 148: 144: 140: 136: 132: 129:, especially 128: 124: 120: 110: 107: 99: 88: 85: 81: 78: 74: 71: 67: 64: 60: 57: –  56: 52: 51:Find sources: 45: 41: 35: 34: 29:This article 27: 23: 18: 17: 367: 359: 348: 324: 317: 293: 286: 219: 210: 206: 184: 182: 163: 154:applications 151: 118: 117: 102: 93: 83: 76: 69: 62: 50: 38:Please help 33:verification 30: 383:0596004508 339:1565925394 308:0782142834 278:References 230:user space 193:Apple menu 166:multimedia 135:Extensions 66:newspapers 170:QuickTime 398:Category 368:Mac OS X 262:JAR hell 257:DLL hell 236:See also 222:Mac OS X 143:OS calls 131:System 7 158:crashes 80:scholar 380:  336:  305:  147:Finder 82:  75:  68:  61:  53:  178:Buggy 87:JSTOR 73:books 378:ISBN 334:ISBN 303:ISBN 199:and 59:news 330:307 299:776 42:by 400:: 376:. 332:. 301:. 195:. 133:. 386:. 374:7 342:. 311:. 109:) 103:( 98:) 94:( 84:· 77:· 70:· 63:· 36:.

Index


verification
improve this article
adding citations to reliable sources
"Extension conflict"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
Apple Macintosh
classic Mac OS
System 7
Extensions
operating system
OS calls
Finder
applications
crashes
multimedia
QuickTime
Microsoft Office
Buggy
Control Panels
Apple menu
Conflict Catcher
Now Startup Manager
ASCIIbetical order
Mac OS X

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.