Juste pour tous ceux qui nous bassinaient en disant que sous X, plus de problèmes d'extensions comme sous 9, enfin débarrasé de la plaie des plaies, etc, etc...
Eh bien, chers zamis, réjouissez-vous car grâce à Apple et à sa gestion pourrave des kernel extensions, nous avons de nouveau droit aux conflits d'extensions, mais qui sont cette fois ci beaucoup plus fun à résoudre...
Lu sur MacFixIt:
<BLOCKQUOTE><font size="1" face="Verdana, Geneva">quote:</font><HR>
PowerDelete and kernel panic Brent Rossow found that OS X 10.1.5 is not compatible with PowerDelete (the freeware that allows Shift-Delete to act as forward delete). He writes: "It will cause a kernel panic on startup. To recover: reboot into single-user mode (Command-Option-S), (2) enter 'fsck -yf' at the command prompt to fix any file system errors, (3) enter '/sbin/mount -uw /' to get out of read-only mode, (4) enter 'cd /Library/StartupItems/' to change to the StartupItems directory, (5) enter 'rmdir -r PowerDelete' to delete the directory containing the PowerDelete startup items, (6) enter 'reboot' to reboot the system. Everything should work after this."
DoubleCommand and kernel panic Bill Wing similarly found that OS X 10.1.5 is "incompatible with DoubleCommand, the extension that converts the Enter key to the right of the spacebar to a second Command key. I get a kernel panic when booting with DoubleCommand installed. Had to boot into single user mode and move the DoubleCommand folder out of the Startup Items folder." He notes that there is a more recent version of DoubleCommand available than the one he was using. He has not tested to see if it prevents the panic.
<HR></BLOCKQUOTE>
Comme c'est bien connu, sous OS X tout est plus simple, au lieu de devoir démarrer sans les extensions en appuyant sur la touche majuscule et de mettre à la poubelle les extensions problèmatiques, il ne suffit plus désormais que de booter en single user mode et de taper 12 commandes dans le terminal...
A quand un Conflict catcher pour OS X?
Eh bien, chers zamis, réjouissez-vous car grâce à Apple et à sa gestion pourrave des kernel extensions, nous avons de nouveau droit aux conflits d'extensions, mais qui sont cette fois ci beaucoup plus fun à résoudre...
Lu sur MacFixIt:
<BLOCKQUOTE><font size="1" face="Verdana, Geneva">quote:</font><HR>
PowerDelete and kernel panic Brent Rossow found that OS X 10.1.5 is not compatible with PowerDelete (the freeware that allows Shift-Delete to act as forward delete). He writes: "It will cause a kernel panic on startup. To recover: reboot into single-user mode (Command-Option-S), (2) enter 'fsck -yf' at the command prompt to fix any file system errors, (3) enter '/sbin/mount -uw /' to get out of read-only mode, (4) enter 'cd /Library/StartupItems/' to change to the StartupItems directory, (5) enter 'rmdir -r PowerDelete' to delete the directory containing the PowerDelete startup items, (6) enter 'reboot' to reboot the system. Everything should work after this."
DoubleCommand and kernel panic Bill Wing similarly found that OS X 10.1.5 is "incompatible with DoubleCommand, the extension that converts the Enter key to the right of the spacebar to a second Command key. I get a kernel panic when booting with DoubleCommand installed. Had to boot into single user mode and move the DoubleCommand folder out of the Startup Items folder." He notes that there is a more recent version of DoubleCommand available than the one he was using. He has not tested to see if it prevents the panic.
<HR></BLOCKQUOTE>
Comme c'est bien connu, sous OS X tout est plus simple, au lieu de devoir démarrer sans les extensions en appuyant sur la touche majuscule et de mettre à la poubelle les extensions problèmatiques, il ne suffit plus désormais que de booter en single user mode et de taper 12 commandes dans le terminal...
A quand un Conflict catcher pour OS X?