Can't boot using key combos

Hi folks,
a few months ago, my wife's Macbook (model 5,2, Mid 2009) suffered a minor fall.
a few days after this little fall, a keyboard problem appeared: the left arrow key acts as if I almost always pressed. I activated the keyboard viewer and it's confirmed that.
I've tried to reinstall osX (10.6) and recovered backup from Time Machine. Maybe because of it (or not!), the problem decreased considerably, but reappeared days later. I've phisically removed the key, took a look and all looks normal.
So today, after she almost had a breakdown trying to write an email, I've decided to try to solve the problem again. Tried PRAM reset, Applejack, but it didn't work. Tried Verbose mode, but also didn't work. So I realized that none of the startup key combos are working. There's no Firmware Password activated. Tried using my old Apple Wireless Bluetooth Keyboard (first gen.), didn't work.
I searched and reasearched a lot and find no answer or even a clue. Then I realized something: apparently, the keyboard is not loading until the Apple logo/loading spinning appears. I noticied that by hitting the caps lock key wheen booting, and the light doesn't turn on until that grey screen.
So iIm asking for some help like:
Is there another way to enter Single-User mode or run Applejack?
Why the keyboard is not loading until the grey screen appears? How to solve this?
Any other suggestions or help would be great!
Thanks in advance,
baga

Quote
The BIOS is set to resume using any keyboard key.
That means that "Specific Ley PowerOn" is no activated, or what? The BIOS Section "Wake Up Event Setup" contains the following options:
- Resume From S3 By USB Device
- Resume From S3 By PS/2 Keyboard
- Specific Key PowerOn
- Resume From S3 By PS/2 Mouse
- Resume By PCI Device (PME#)
- Resume By PCI-E Device
- Resume By RTC Alarm
Which one did you enable/disable?

Similar Messages

Resized partition, now can only boot using option key

I made my boot camp partition larger and my os x partition smaller using a 3rd party program. I can still boot into windows, but only using the option key. When I look at my startup disks in OS X, only my OSX partition shows up. Is there any way to make snow leopard recognize this resized partition? Thanks!

Hi,
I am not familiar with that program but since it is a Windows program I doubt that it has installed anything in OSX.
Most likely that program wasn't even "aware" that it was used on a Mac running WIndows.
And it also might be that that is the reason for your problem.
To run Windows with BootCamp on a Mac OSX has to establish/use a form of hybrid GPT/MBR partitioning.
GPT for OSX and MBR for Windows.
That also means that using any kind pof partitioning tool (resizing etc.) would have to be done best in OSX since only OSX "knows" that there is a Windows partition and can handle the hybrid partitioning accordingly.
First thing I would propose (if not already there) is a backup / clone of your OSX onto an external HD.
Secondly boot your Mac from the OSX DVD and use Disk Utility from it to verify/repair your OSX.
Regards
Stefan

Can't boot using EFISTUB

Hello,
I am trying to install arch on my recent laptop (lenovo thinkpad) in UEFI. I already made an aproximatively successful install of arch few weeks ago using grub, and I believe it should work, but I just prefer refind wich seems clearer to me (I mean I feel like I know what part of the computer Im changing, while grub-install is just too magic for me, especially when I end up still having a part of the grub on a completly formated hard disk... anyway).
When I try to boot arch from rEFInd, the system hangs on "using load options *load options i chosed*". It seems to freeze and all I can do is press power button to reboot laptop.
I checked files in my efi partition and i'm sure everything is fine. I have a refind_linux.conf file in my arch folder, created with what I found in the beginner's guide
"Boot to 5" "root=/dev/sda5 ro rootfstype=ext4 systemd.unit=graphical.target"
"Boot to console" "root=/dev/sda5 ro rootfstype=ext4 systemd.unit=multi-user.target"
I also tryed to use label or partuuid in it (root=PARTUUID=XXXXXX) and it didnt solve the problem.
I created a custom entry with the refind.conf file (in EFI/refind/ folder), adding something like :
menuentry "Arch" {
icon \EFI\BOOT\icons\os_arch.icns
loader \EFI\arch\vmlinuz-arch.efi
initrd \EFI\arch\initramfs-arch.img
options "ro root=/dev/sda3"
One interesting thing I noticed when doing this is that when I made mistake with paths for kernel or ram, refind would tell me so and wouldnt crash. The hang really happens upon loading those files.
I tryed to boot arch from the efi shell that I could access from the usb drive I used for installation, and had the same crash problem in the console.
That made me think that something was really wrong with my vmlinuz-linux file or my initramfs, I tryed reinstalling both with mkinitcpio and pacman -S linux, still got stuck. Of course after the updates I would recopy them in /EFI/arch/ folder with the correct names according to the wiki.
I was able to partly boot to arch from refind by replacing my vmlinuz with the one that was given with the arch iso (downloaded from torrent on the official site), but everything wasn't still right and I found that solution messy anyway and didnt want to search too much on that path.
So that's it, i hope it is clear, my english is far from perfect and I apologyze for that. And hi everyone by the way, i'm new to arch, still not sure if i'm going to use that distribution. I'm usually not the linux type but I have to say i'm much more excited about this one than the others I used (ubuntu and stuff like that). At least, when i encounter a problem (and for some reason, I alwails encounter loads of problems on linux), I learn stuff.
Thanks

Hika wrote:
srs5694 wrote:Second, for the auto-detection code (with refind_linux.conf), rEFInd matches the first initrd file it finds to your kernel. Arch, though, provides two initrd files for your default kernel, so rEFInd might be launching either of those initrd files. If you want to use auto-detection, it's best to include separate options lines, each of which references a specific initrd file. With the last couple versions of rEFInd, those references will override the auto-detection. I doubt if this is really your problem, but it could be at least part of it, and it's something you should keep in mind in the future in any event.
I am not sure I understand this one. You mean I should add an "initrd=\EFI\arch\initramfs-arch.img" to each of my options ?
Yes -- but see below. Also, you'd probably want to create at least one entry that references the fallback initrd rather than the default one.
I thought about doing so but I read somewhere someone saying that that kind of feature (specifying initrd for auto-detection entries) wasn't implemented yet. I will do this in the future anyway.
It's a very recent feature. I'm not sure if it's implemented in the version of rEFInd you'd get via pacman, but it's definitely present in the latest version of rEFInd available from its own downloads page.
By the way, how do I access the options I added in refind_linux ? I couldnt find it, I tryed to press inser or + as I read somewhere, got redirected to an empty menu. I first thought I made a mistake with the refind_linux file, but the options I add in it are taken in account for default loading (as I said i can see the loading options just before the crash so i could check).
After you highlight your main Arch option, pressing Insert, F2, or + should bring up a menu of the sub-options specified in refind_linux.conf or in the manual boot stanza you created. Highlight one of these and press Insert, F2, or + again and you should see the options editor screen with the current options. If you see the editor but the options it shows are blank, or show only the initrd= option, then that suggests that you've not placed refind_linux.conf correctly; the file should be in the same directory as the kernels to which it applies. If you don't get an editor at all, then that suggests you're using an old version of rEFInd; the options editor was added with version 0.4.7.
srs5694 wrote:Third, what kernel version are you using? Early versions of the EFI stub loader didn't display error messages when they couldn't find their initrd files. Newer versions do. (I don't recall where the cutoff was, though -- probably with 3.5.0 or perhaps 3.6.0.) Thus, if you're using an old version, it could be that the kernel can't find the referenced initrd file for some reason, and so is silently hanging. If you're using a more recent kernel, this is less likely, since the kernel should display an error message to the effect that it couldn't load the initrd file.
As I said I tryed to reinstall the kernel , so I guess I must have the last version. I just typed pacma -Q, I got the package linux 3.6.10-1 installed.
OK, so if you try to launch that and the system hangs without displaying an error message, that suggests that the problem isn't simply that the kernel can't find its initrd file.
Beyond that, I'm not sure. Maybe you've encountered an obscure bug in the EFI stub loader, or perhaps your kernel is incompatible with your hardware in some basic way. A kernel version upgrade might fix it, or you could try installing ELILO and use that -- ELILO will at least bypass the EFI stub loader, in case it's the cause of your problem. (GRUB 2 might also work, but ELILO is much easier to configure manually.)
Well, grub 2 used to work with a previous install I made of arch. The only changed I made since that time is a bios update, could it cause that kind of problem ?
Perhaps. UEFI firmware is still immature. It's also big -- the core of EFI is about the same size as the core of the Linux kernel (without its drivers), and it's not nearly as well tested. That's a breeding ground for bugs, and I've seen some weird ones.
That said, you've switched from GRUB 2 to the EFI stub loader at the same time you upgraded your firmware. Thus, it's impossible to say which change has caused the problem. My hunch is it's the switch from GRUB 2 to to the EFI stub loader, but it could be that the latter is failing because of a problem with your firmware (new or old version might not matter).
I might also try a proper reinstall of rfind using the guide that is on the offical refind site instead of the arch one.
If I am right, a proper uninstall of refind would be to remove the package using pacman, revert all the modifications I made in the EFI partition, and remove the boot entry in bios using efibootmgr. (that's partly a question)
Yes, that would uninstall rEFInd. The latest version (0.6.1) has an install.sh script that should do the job right in most cases, although you might need to use a parameter or two on some systems. If you're using an emergency boot disc, in particular, note the new --root option, which you use to point to the root of your regular installation. (You should mount your /boot and/or ESP at appropriate places within that tree, too.) Also, be aware that rEFInd's defaults are built with Fedora, Ubuntu, SUSE, and similar distributions in mind. Arch's naming and handling of kernels is unusual, which is why you might need to explicitly specify your initrd in refind_linux.conf or create manual boot stanzas in refind.conf for Arch but not for most other distributions.

G510 can't simultaneously use keys and touchpad

Whenever I use the ke'yboard, the mouse freezes. This may not seem like much of a problem, but that means whenever I play a game that uses the mouse to move the screen, I can't move at the same time. I've looked through the settings and tried different changes, but nothing seems to work.. Help?

hi Laura_G,
Have you tried checking the touchpad hardware setting?
This feature is like a palmcheck feature. Where it like mutes the touchpad when a keyboard input is detected to prevent accidental touchpad movements or clicks.
Try checking Palm check
http://forums.lenovo.com/t5/IdeaPad-Y-U-V-Z-and-P-series/Z500-Touch-Elan-TouchPad-Can-t-Disable-Palm...
Hope this helps
Cheers!
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Appleworks 6.2.7 will not open and can't boot from Systemworks CD

Received message "need to restart your computer". Now Appleworks 6.2.7 will not open and I can't boot using SystemWorks CD -- keep getting the above "need to restart your computer" message when trying to start with SW CD. I've gone through the troubleshooting steps i.e. safe boot, throw away the prefs file, and have just reinstalled Appleworks from my software restore CD. When I try to open AW I now get message "Appleworks has unexpectedly quit". What do I do now? Suggestions and advice would be appreciated.
Lorne

Unless you absolutely have to open files created in ClarisWorks 4 or earlier or drag & drop in tables, I recommend the first thing you do is update to AppleWorks 6.2.9. AppleWorks 6.2.7 update came out around January 2003 & was the worst update ever. Fortunately, the 6.2.9 updater came out in January 2004 & fixed the issues 6.2.7 was supposed to fix and the ones it caused. You can find the links to the updater on this page where you can choose the appropriate updater for your AppleWorks 6 installation.
Then after updating, delete the AppleWorks preferences as in my user tip Barbara gave the link to.
Peggy

Cannot get MacPro to allow me to boot to an alternative boot disk. Can choose in control panel but will not use the disk to boot. Also won't boot using disk selected using option key

My primary boot disk is encrypted as is a secondary boot disk (backup) but I cannot boot using any other disk. System 10.8.5, MacPro 4.1.
All disks mount using primary boot disk. All disks check out as OK and I have repaired permissions.
When I choose in the control panel the Mac boots but will always use my original boot disk.
When I select the disk using the option key at startup, the boot process stalls with a grey screen and a spinning cursor.
Thanks,
Dave

Still trying to figure this out. I erased the drive, did a format using disk util and then re-installed the system but I still cannot get the disk used as a startup drive. I also tried an external firewire drive and it won't allow me to boot from it either.
I can choose it starting up with the option key but it just gives me a blue screen and the spinning cursor.
If I select it in the startup pref pane it boots into my other startup drive only.
DaveLon

I use an Apple bluetooth keyboard with my iPad. In messages I can't find a way to "send" a message without tapping on Send on the iPad's screen. I've tried every key and key combo that I can think of. Am I missing something?

I use an Apple bluetooth keyboard with my iPad. In messages I can't find a way to "send" a message without tapping on Send on the iPad's screen. I've tried every key and key combo that I can think of. Am I missing something?

I already have multiple devices and by far I like my iPad the most over laptops and the iPad. That including checking out my friends MacBook Air.
The difference for me is the touch interface on the screen itself for things that do not require a lot of typing. For me, the iPad is more "magical" than anything else I've used.
Again, I do appreciate your answers but you don't know my situation. Not everything is as it is perceived without knowing me and what I have to go through.

Key combos to get it to boot up

Having trouble booting up my old G5. If I'm lucky, I can hold down the 'C' while pushing the power button and it may or may not boot after several tries. Using tiger 10.5 (?) Can't remember the exact version because it isn't booting up anymore. Last time it did there was no keyboard/mouse recognition. Is there any key combo to try other than the 'C'?

Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
/sbin/fsck -fy
Repeat until it shows no errors fixed.
(Space between fsck AND -fy important).
Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
http://docs.info.apple.com/article.html?artnum=106214
We might get clues with verbose mode...
http://support.apple.com/kb/HT1492

Can "Refit" Be Used for USB Boot From External Optical Drive?

Since the new Mac Mini 2011 has no optical drive, how would one make a generic USB 2.0 optical drive act as a boot device? I have heard that a utility called "Refit" can alter the boot loading order and device choices in Macs. I suppose it is also possible that the new Mini may already be set up to boot first from USB. I would appreciate any comments. It would be nice to have some kind of optical drive boot option for Windows installation and other possible utilities that need to boot before the OS in order to work. Maybe I will have to take my external optical drive to an Apple store to find out. Hope not. I also suspect that a USB keyboard will be mandatory for "Refit" and the boot drive to be used before Mac OS X is loaded.

No utility should be needed.
You can hold the Option key down during the boot process to select which drive you wish to use as a boot device.
Also pressing and holding C boots to the optical drive.
There is reportedly a pretty broad number of USB optical drives that people have been able to use as a boot device, as inexpensively as $30. I don't know that there is a specific list though. I would research whichever model you wish to buy with a quick google search or searching that model here in the forum.
Or maybe somebody will have a recommendation which one they have.

How can I boot and run my Mac Mini on my 12" PwrBk display using firewire?

How can I boot and run my Mac Mini on my 12" PwrBk display using firewire?

bwhit:
Welcome to Apple Discussions.
No reason why you should not be able to do it using Firewire Target Disk Mode. Here's what you do:
1. With both computers shut down connect both via firewire.
2. Startup the Mini and hold down "T" key immediately after chime.
3. Startup the PB and immediately after chime hold down Option key.
4. Select second HDD icon on the screen and click on the right pointing arrow.
5. Computer will boot from Mini's HDD.
Be sure to shut down PB completely before shutting down Mini.
Please do post back with an update or with further questions or comments.
Cheers
cornelius

Black Bar on Screen with Text (accidental key combo, can't get rid of it)

In a mad typing dash 2 days ago, I accidentally hit a key combo that placed a black bar in the middle of my screen with the words "Gmail - friday - my email address" (I was in Gmail composing a message at the time). It's visible at all times, using all apps, and on my desktop. I've tried rebooting, quitting all apps, checking my system prefs, looking for answers online, all to no avail. I can't click on it, highlight it or drag it to the trash and I'm at a loss...any suggestions? Many thanks!

Were you able to fix this? I have it too..

HT201612 I was trying to install windows using boot amp but now I can't boot my MaOckbook pro again

I was trying to install windows using boot amp but now I can't boot my MacBook pro again

Go to the Windows Control Panel and select Boot Camp applet. In that applet there is a Boot Drive option. Select Mac OS X.
Or restart the system and hold down the Option key for a few second. A Boot Menu screen will come up. Select Macintosh HD.
Once in OS X go to the Sys Prefences, Startup Disk and select Macintosh HD Mt Lion 10.8.2 and click Restart then Restart again. the system will now restart in Mac OS X.
To boot back to Windows do the same, Startup Disk, and select Windows then Restart and Restart again.

[SOLVED]Can't boot Arch after installation-grub use wrong uuid in bios

Hello I would like to ask for Your help and say hello. I'm new here.
I have one big problem with Arch. Can't boot it after base installation. The same problem with Arch, that was mentioned in this topic:
https://bbs.archlinux.org/viewtopic.php … 7#p1294597
I have the same problem and the same error:
No such Device: ad4103fa-d940-47ca-8506-301d8071d467.
Loading Linux core repo kernel ...
error: no such partition.
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue..._
I'm new here, and with Arch, could you explain me how to fix it? I tried the solution given in the link above, several times but with each time i have errors and warnings from the post 1 in mentioned topic. I installed my Arch from usb thumb drive. Maybe this is something to do with it? Also, my hard drive that Arch is installed on is being connected to a "raid card" named Adaptec, but during installation my disk is being found so i think that drivers is present and works ok, so it is not related to this, also there is no raid present, i use it only as a mean to connect to motherboard because there is not enough sata port, and because:
https://bugs.archlinux.org/task/35626
he wrote that this error is also on virtualbox, so it is not my fault and Adaptec related issue.
I haven't tried this yet:
Sotanaht,
I had the exact same problem as you, but I was able to fix it by replacing the bad grub.cfg file with the grub.conf file found in the same directory. If you try this do not forget to back up your original file (just in-case smile)
because i don't know much about it, don't want to destroy data on my hard disks or to destroy my other distros (i use Ubuntu with derrativates such as Mint, Kubntu, Lubuntu, Xubuntu, and Slackware 13.37 and 14.00).
If you could explain it in details i would be really happy.
I could post something about my setup, please write what. My computer is:
-AMD X4 PII 955 runinng at 3.2GHz
-4GB DDR2 runinng at base clock (800 if i remember correctly)
-about 7 hard drive disk connected to a sata ports, one adaptec drive that i mentioned above and one dvd-rom
-nvidia GTX260
-850W PSU Chieftec
Last edited by firekage (2013-07-02 08:11:29)

Yes, of course. I did it several times with
grub-mkconfig -o /boot/grub/grub.cfg
and the result is always the same - Error posted above.
Here is my grub.cfg file:
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-ad4103fa-d940-47ca-8506-301d8071d467' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
It is wrong, the root partition is different than in this, we can see that this grub leads to wrong root partition, i posted my root partition at the bottom from /etc/fstab. I don't know how to fix it - i'm not familiar with the dos names (hd 0,5 and so on).
Here is my /etc/fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb2
UUID=59603166-5d8a-4aaf-81f7-5a822fd630e5 / ext4 rw,relatime,data=ordered 0 1
# /dev/sdb1
UUID=20028674-d7e8-4bf4-8551-64f133641962 none swap defaults 0 0
(END)
Last edited by firekage (2013-07-01 06:26:59)

Various results of using CMD-I key combo for get info

I just updated to Snow Leopard from Leopard and I'm pretty baffled by some new behavior.
I'm used to using the key combo CMD-I to pull up the get info dialog so I can change the default app to open the files with.
Every once in a while, when I select a bunch of files and do CMD-I key combo, it opens up many many individual windows. I can't figure out when or why it does this and how to get the get info window so I can change them all to open with Quicktime.
Other times, it does what I expect. It opens up one get info window for all the items so I can change the open with app.
Can anyone explain what's going on and how to get the usual CMD-I back? Thanks,

Thanks Malcolm.
CMD-Opt-I key combo helps when CMD-I fails, but, I still don't understand what the problem is with CMD-I being inconsistent.
I just did an experiment with some files that I have in iTunes because these are the ones I often need to Get Info to change them to open with Quicktime player.
Example.
Folder 1 has 19 files. CMD-A followed by CMD-I opens up one dialog box "Multiple Item Info". I can change the open with default.
Folder 2 has 4 files. CMD-A followed by CMD-I spawns 4 windows with each files name followed by info, e.g. "Filename1.mp3 Info"
This doesn't make sense.

Hello, can someone help me: my eMac G4 700 MHz. I can not boot it. If he starts appears on the screen, only a small "folder with a question mark." The Mac was not used 1 year. Question 1: Problem = hard drive? Question 2: Problem = PRAM battery? the What

Hello, can someone help me: my eMac G4 700 MHz. I can not boot it. If he starts appears on the screen, only a small "folder with a question mark." The Mac was not used 1 year.
Question 1: Problem = hard drive?
Question 2: Problem = PRAM battery?
the
What can I do to boot?

Restart with the Option key held down.
If the internal drive shows up, it's the PRAM battery.
If it doesn't, insert a compatible Mac OS 9 or X install disk, click the button with the circular arrow, and either repair the internal drive or install a new OS on it. If it doesn't show up in Disk First Aid(9) or the Disk Utility(X), it's either not plugged in or needs to be replaced.
(97530)

Can't boot using key combos

Similar Messages

Maybe you are looking for