White triangle warning on boot load - sony neo v

Hi All,
Can someone please help me in resolving the below one
white triangle warning on boot load - sony neo v. Phone seems to be not working
Regards
Lokeshkumar

http://www.sonymobile.com/gb/tools/update-service/
http://www-support-downloads.sonymobile.com/Software%20Downloads/Update_Service_Setup-2.11.12.5.exe
Alternatives on How to backup Xperias
http://talk.sonymobile.com/thread/36355
Don't forget to mark the Correct Answers & Helpful Answers
"I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)

Similar Messages

  • Error installing grub boot loader

    I am currently following the beginner guide for installing arch, and once I get to the place where I need to install a boot loader and use the command pacman -S grub-bios, I get a seemingly never ending output of "sh: /usr/bin/wget: no such file or directory" then it will change to "warning: failed to retrieve some files from core"(more like all files lol) etc as it goes through the repos. I've followed the guide to a tee, with the exception of the example partitioning on there. Anyone have any ideas on what could be going wrong?

    It seems like wget is missing on the install partition. This is after you have done arch-chroot right?
    I would try to do a
    # pacman -Syy wget
    to update the archive and install wget
    and then try grub-bios again
    edit:
    If you are still on the install media the command you want to use is
    # pacstrap /mnt grub-bios
    Last edited by drobole (2012-12-16 11:47:49)

  • Mac hangs at white screen with spinning with loading wheel while shutting down.

    I've had a problem with my computer recently that really bugs me, because I been needing to install os x updates, but when i try to shut my computer down, it hangs at a white screen with the grey loading wheel forever until I forcibly shut it down. This has been bugging me a lot, and when I try other peoples' solutions, (e.g. resetting NVRAM, uninstalling apps), I can't figure out what apps to uninstall, and resetting the NVRAM is no luck. I have a console log of the shutdown here:
    3/14/2014 8:12:04.325 AM WindowServer[133]: CGXGetConnectionProperty: Invalid connection 37731
    3/14/2014 8:12:04.327 AM WindowServer[133]: CGXGetConnectionProperty: Invalid connection 37731
    3/14/2014 8:12:04.327 AM WindowServer[133]: CGXGetConnectionProperty: Invalid connection 37731
    3/14/2014 8:12:04.327 AM WindowServer[133]: CGXGetConnectionProperty: Invalid connection 37731
    3/14/2014 8:12:04.328 AM WindowServer[133]: CGXGetConnectionProperty: Invalid connection 37731
    3/14/2014 8:12:04.347 AM com.apple.launchd.peruser.501[210]: (com.apple.EscrowSecurityAlert[483]) Exited: Killed: 9
    3/14/2014 8:12:04.354 AM WindowServer[133]: _CGXGetWindowOrderingGroup: Operation on a window 0x15 requiring rights 0x5 by caller Dashboard
    3/14/2014 8:12:04.354 AM WindowServer[133]: _CGXGetWindowOrderingGroup: Operation on a window 0x14 requiring rights 0x5 by caller Dashboard
    3/14/2014 8:12:04.354 AM WindowServer[133]: _CGXGetWindowOrderingGroup: Operation on a window 0x13 requiring rights 0x5 by caller Dashboard
    3/14/2014 8:12:04.354 AM WindowServer[133]: _CGXGetWindowOrderingGroup: Operation on a window 0x11 requiring rights 0x5 by caller Dashboard
    3/14/2014 8:12:04.354 AM WindowServer[133]: _CGXGetWindowOrderingGroup: Operation on a window 0x10 requiring rights 0x5 by caller Dashboard
    3/14/2014 8:12:04.355 AM WindowServer[133]: _CGXGetWindowOrderingGroup: Operation on a window 0x71 requiring rights 0x5 by caller Dashboard
    3/14/2014 8:12:04.355 AM com.apple.launchd[1]: (com.apple.ShareKitHelper[299]) Exited: Killed: 9
    3/14/2014 8:12:04.355 AM WindowServer[133]: CGXOrderWindowList: Operation on a window 0x15 requiring rights kCGSWindowRightPresenter by caller Dashboard
    3/14/2014 8:12:04.355 AM DashboardClient[496]: CGSOrderWindowList
    3/14/2014 8:12:04.364 AM com.apple.launchd[1]: (com.apple.internetaccounts[279]) Exited: Killed: 9
    3/14/2014 8:12:04.364 AM com.apple.launchd.peruser.501[210]: (com.intego.commonservices.integomenu[263]) Exited: Killed: 9
    3/14/2014 8:12:04.387 AM com.apple.launchd.peruser.501[210]: (com.apple.iTunesHelper.17984[270]) Exited with code: 1
    3/14/2014 8:12:04.387 AM com.apple.launchd.peruser.501[210]: (com.apple.ImageCaptureExtension2.10416[354]) Exited: Killed: 9
    3/14/2014 8:12:04.387 AM com.apple.launchd.peruser.501[210]: (com.apple.gamed[275]) Exited: Killed: 9
    3/14/2014 8:12:04.390 AM com.apple.launchd.peruser.501[210]: ([0x0-0x37037].com.apple.AppleSpell[391]) Exited: Killed: 9
    3/14/2014 8:12:04.428 AM _cvmsroot[534]: audit warning: allsoft
    3/14/2014 8:12:04.428 AM _cvmsroot[535]: audit warning: soft /var/audit
    3/14/2014 8:12:04.453 AM _cvmsroot[537]: audit warning: closefile /var/audit/20140314120742.20140314121204
    3/14/2014 8:12:04.481 AM sessionlogoutd[538]: sessionlogoutd Launched
    3/14/2014 8:12:04.497 AM loginwindow[92]: ERROR | -[Application setAppContext:] | Unable to get PID for context [0,53261]
    3/14/2014 8:12:04.505 AM sessionlogoutd[538]: DEAD_PROCESS: 92 console
    3/14/2014 8:12:04.541 AM gamed[530]: CKSoftwareMap: Registering with Daemon
    3/14/2014 8:12:04.562 AM loginwindow[92]: ERROR | processNotificationManagerLSNotificationCallBack | LWCASProcessNotificationManager UNEXPECTED NOTIFICATION of type: kLSNotifyApplicationBirth
    3/14/2014 8:12:04.593 AM airportd[113]: _doAutoJoin: Already associated to “ThompsonFamily1”. Bailing on auto-join.
    3/14/2014 8:12:04.599 AM com.apple.kextd[12]: Can't create kext cache under / - owner not root.
    3/14/2014 8:12:04.602 AM com.apple.kextd[12]: Rescanning kernel extensions.
    3/14/2014 8:12:04.000 AM kernel[0]: Kext loading now disabled.
    3/14/2014 8:12:04.000 AM kernel[0]: Kext unloading now disabled.
    3/14/2014 8:12:04.000 AM kernel[0]: Kext autounloading now disabled.
    3/14/2014 8:12:04.000 AM kernel[0]: Kernel requests now disabled.
    3/14/2014 8:12:04.602 AM com.apple.kextd[12]: Can't create kext cache under / - owner not root.
    3/14/2014 8:12:04.602 AM shutdown[539]: halt by _cvmsroot:
    3/14/2014 8:12:04.602 AM shutdown[539]: SHUTDOWN_TIME: 1394799124 602127
    3/14/2014 8:12:04.632 AM Dock[221]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted
    3/14/2014 8:12:04.632 AM Dock[221]: XPC error messaging com.apple.IconServicesAgent: Connection invalid
    Any help would be appreciated,
    Thanks.

    Select the icon of the startup volume ("Macintosh HD," unless you gave it a different name) in a Finder window and open the Info window. In the Sharing & Permissions section, what is shown under Name and Privilege?

  • Re-locking boot loader

    I unlocked my Xperia Mini ST15i's boot loader, but never got around to flashing any kernel or ROM. I'm having a rebooting issue with the phone now, and want to try repairing it from a PC. Is there a specific procedure for re-locking the boot loader on an ST15i? (Also: after charging the battery fully, then rebooting, sometimes the battery appears half-empty, or even completely empty. Could this indicate the battery needs replacing?)

    My ST15i with 4.0.4 installed is rebooting automatically. Sometimes during boot (SONY or XPERIA logos), sometimes just after booting. Bluetooth is off. SIM and SD cards are removed. I have repaired the phone to 4.0.4 using both Bridge for Mac and PC Companion on Windows. The phone will boot successfully only when connected to power or computer via USB. If the USB cable is disconnected after booting, the phone instantly crashes. The battery charge indicator is all over the place. After charging to 100%, the next time the phone is connected the charge icon will only show half full, or after booting in Safe Mode it'll show something like 28%. I tested the phone using a brand-new battery at a phone shop and it still wouldn't boot successfully Any suggestions?

  • Problems unlocking the boot loader of xperia z3

    Hello,
    i'm trying to unlock the boot loader of my xperia z3, i'm following the instructions on sony's site but i'm stuck: i connect the phone to the pc in fastboot mode (blue light on), then i open the command prompt window in the platform-tools folder of android sdk, but when i type fastboot devices nothing happens. If i try to enter my unlock code i get "waiting for device" forever. 
    Any help?

    I recommend that you check that you have installed the fastboot driver. You can download it from here: http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
    And as uliwooly says, make sure that you have read the information on http://developer.sonymobile.com/unlockbootloader/ and that you are aware of the risks.
     - Official Sony Xperia Support Staff
    If you're new to our forums make sure that you have read our Discussion guidelines.
    If you want to get in touch with the local support team for your country please visit our contact page.

  • Latitude E5440 - Truecrypt Boot Loader Problems

    I've been using Truecrypt for many years on Latitude D  and E Series laptops and never had a problem until we upgraded to E5440's.  Now I continually get Truecrypt boot loader errors.
    I've tried versions 7.1 and 7.1a and FDE as well as just encrypting the System Partition.  What happens is that when the computer is started up, I get a black screen with a white blinking cursor.
    The temporary fix is easy.  I boot off the Truecrypt Rescue disk and Repair the Truecrypt Boot Loader.  This works for several days and then it happens again.
    I am lost as to a solution, but I believe it might involve one of the following:
    1. Hybrid Hard Drives.  These E5440's have a Samsung 500GB hybrid drive in them.  I am wondering if some file or component of Truecrypt is being put on the Flash drive component of the HD and it becomes unavailable at boot up.
    2. Closing the lid of the laptop instead of shutting it down for transport. 
    If you've had similar problems or have any insight into this issue, I would love to get your feedback.
    Thanks, Greg
    Also, these laptops run W7 Pro.

    I've been using Truecrypt for many years on Latitude D  and E Series laptops and never had a problem until we upgraded to E5440's.  Now I continually get Truecrypt boot loader errors.
    I've tried versions 7.1 and 7.1a and FDE as well as just encrypting the System Partition.  What happens is that when the computer is started up, I get a black screen with a white blinking cursor.
    The temporary fix is easy.  I boot off the Truecrypt Rescue disk and Repair the Truecrypt Boot Loader.  This works for several days and then it happens again.
    I am lost as to a solution, but I believe it might involve one of the following:
    1. Hybrid Hard Drives.  These E5440's have a Samsung 500GB hybrid drive in them.  I am wondering if some file or component of Truecrypt is being put on the Flash drive component of the HD and it becomes unavailable at boot up.
    2. Closing the lid of the laptop instead of shutting it down for transport. 
    If you've had similar problems or have any insight into this issue, I would love to get your feedback.
    Thanks, Greg
    Also, these laptops run W7 Pro.

  • [SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.

    Hello,
    The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
    efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
    Information
    efibootmgr 0.6.0-1
    refind-efi 0.6.8-1
    Linux 3.8.4-1-ARCH
    sudo efibootmgr
    BootCurrent: 000A
    Timeout: 0 seconds
    BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
    Boot0000 Setup
    Boot0001 Boot Menu
    Boot0002 Diagnostic Splash Screen
    Boot0003 Startup Interrupt Menu
    Boot0004 ME Configuration Menu
    Boot0005 Rescue and Recovery
    Boot0006* USB CD
    Boot0007* USB FDD
    Boot0008* ATAPI CD0
    Boot0009* ATA HDD2
    Boot000A* ATA HDD0
    Boot000B* ATA HDD1
    Boot000C* USB HDD
    Boot000D* PCI LAN
    Boot000E* ATAPI CD1
    Boot000F* ATAPI CD2
    Boot0010 Other CD
    Boot0011* ATA HDD3
    Boot0012* ATA HDD4
    Boot0013 Other HDD
    Boot0014* IDER BOOT CDROM
    Boot0015* IDER BOOT Floppy
    Boot0016* ATA HDD
    Boot0017* ATAPI CD:
    Boot0018* PCI LAN
    ls -R /boot
    /boot:
    EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
    /boot/EFI:
    boot refind tools
    /boot/EFI/boot:
    bootx64.efi icons refind.conf
    /boot/EFI/boot/icons:
    *** Icons
    /boot/EFI/refind:
    icons refind.conf refind_x64.efi
    /boot/EFI/refind/icons:
    *** icons
    /boot/EFI/tools:
    drivers shells
    /boot/EFI/tools/drivers:
    ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
    /boot/EFI/tools/shells:
    Shell.efi Shell_Full.efi
    cat /boot/refind_linux.conf
    "Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
    "Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
    # refind.conf
    # Configuration file for the rEFInd boot menu
    # Timeout in seconds for the main menu screen. Setting the timeout to 0
    # disables automatic booting (i.e., no timeout).
    timeout 5
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner (built-in or loaded via "banner")
    # label - boot option text label in the menu
    # singleuser - remove the submenu options to boot Mac OS X in single-user
    # or verbose modes; affects ONLY MacOS X
    # safemode - remove the submenu option to boot Mac OS X in "safe mode"
    # hwtest - the submenu option to run Apple's hardware test
    # arrows - scroll arrows on the OS selection tag line
    # hints - brief command summary in the menu
    # editor - the options editor (+, F2, or Insert on boot options menu)
    # all - all of the above
    # Default is none of these (all elements active)
    #hideui singleuser
    #hideui all
    # Set the name of a subdirectory in which icons are stored. Icons must
    # have the same names they have in the standard directory. The directory
    # name is specified relative to the main rEFInd binary's directory. If
    # an icon can't be found in the specified directory, an attempt is made
    # to load it from the default directory; thus, you can replace just some
    # icons in your own directory and rely on the default for others.
    # Default is "icons".
    #icons_dir myicons
    # Use a custom title banner instead of the rEFInd icon and name. The file
    # path is relative to the directory where refind.efi is located. The color
    # in the top left corner of the image is used as the background color
    # for the menu screens. Currently uncompressed BMP images with color
    # depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
    #banner hostname.bmp
    #banner mybanner.png
    # Custom images for the selection background. There is a big one (144 x 144)
    # for the OS icons, and a small one (64 x 64) for the function icons in the
    # second row. If only a small image is given, that one is also used for
    # the big icons by stretching it in the middle. If only a big one is given,
    # the built-in default will be used for the small icons.
    # Like the banner option above, these options take a filename of an
    # uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
    # or a PNG image. The PNG format is required if you need transparency
    # support (to let you "see through" to a full-screen banner).
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    # Set the font to be used for all textual displays in graphics mode.
    # The font must be a PNG file with alpha channel transparency. It must
    # contain ASCII characters 32-126 (space through tilde), inclusive, plus
    # a glyph to be displayed in place of characters outside of this range,
    # for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
    # may be of any size, although large fonts can produce display
    # irregularities.
    # The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
    #font myfont.png
    # Use text mode only. When enabled, this option forces rEFInd into text mode.
    # Passing this option a "0" value causes graphics mode to be used. Pasing
    # it no value or any non-0 value causes text mode to be used.
    # Default is to use graphics mode.
    #textonly
    textonly
    # Set the EFI text mode to be used for textual displays. This option
    # takes a single digit that refers to a mode number. Mode 0 is normally
    # 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
    # modes. Mode 1024 is a special code that tells rEFInd to not set the
    # text mode; it uses whatever was in use when the program was launched.
    # If you specify an invalid mode, rEFInd pauses during boot to inform
    # you of valid modes.
    # CAUTION: On VirtualBox, and perhaps on some real computers, specifying
    # a text mode and uncommenting the "textonly" option while NOT specifying
    # a resolution can result in an unusable display in the booted OS.
    # Default is 1024 (no change)
    #textmode 2
    textmode 1024
    # Set the screen's video resolution. Pass this option either:
    # * two values, corresponding to the X and Y resolutions
    # * one value, corresponding to a GOP (UEFI) video mode
    # Note that not all resolutions are supported. On UEFI systems, passing
    # an incorrect value results in a message being shown on the screen to
    # that effect, along with a list of supported modes. On EFI 1.x systems
    # (e.g., Macintoshes), setting an incorrect mode silently fails. On both
    # types of systems, setting an incorrect resolution results in the default
    # resolution being used. A resolution of 1024x768 usually works, but higher
    # values often don't.
    # Default is "0 0" (use the system default resolution, usually 800x600).
    #resolution 1024 768
    #resolution 3
    resolution 1024 768
    # Launch specified OSes in graphics mode. By default, rEFInd switches
    # to text mode and displays basic pre-launch information when launching
    # all OSes except OS X. Using graphics mode can produce a more seamless
    # transition, but displays no information, which can make matters
    # difficult if you must debug a problem. Also, on at least one known
    # computer, using graphics mode prevents a crash when using the Linux
    # kernel's EFI stub loader. You can specify an empty list to boot all
    # OSes in text mode.
    # Valid options:
    # osx - Mac OS X
    # linux - A Linux kernel with EFI stub loader
    # elilo - The ELILO boot loader
    # grub - The GRUB (Legacy or 2) boot loader
    # windows - Microsoft Windows
    # Default value: osx
    #use_graphics_for osx,linux
    # Which non-bootloader tools to show on the tools line, and in what
    # order to display them:
    # shell - the EFI shell (requires external program; see rEFInd
    # documentation for details)
    # gptsync - the (dangerous) gptsync.efi utility (requires external
    # program; see rEFInd documentation for details)
    # apple_recovery - boots the Apple Recovery HD partition, if present
    # mok_tool - makes available the Machine Owner Key (MOK) maintenance
    # tool, MokManager.efi, used on Secure Boot systems
    # about - an "about this program" option
    # exit - a tag to exit from rEFInd
    # shutdown - shuts down the computer (a bug causes this to reboot
    # EFI systems)
    # reboot - a tag to reboot the computer
    # Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
    #showtools shell, mok_tool, about, reboot, exit
    showtools shell, mok_tool, about, reboot, exit
    # Directories in which to search for EFI drivers. These drivers can
    # provide filesystem support, give access to hard disks on plug-in
    # controllers, etc. In most cases none are needed, but if you add
    # EFI drivers and you want rEFInd to automatically load them, you
    # should specify one or more paths here. rEFInd always scans the
    # "drivers" and "drivers_{arch}" subdirectories of its own installation
    # directory (where "{arch}" is your architecture code); this option
    # specifies ADDITIONAL directories to scan.
    # Default is to scan no additional directories for EFI drivers
    #scan_driver_dirs EFI/tools/drivers,drivers
    scan_driver_dirs /boot/EFI/tools/drivers,drivers
    # Which types of boot loaders to search, and in what order to display them:
    # internal - internal EFI disk-based boot loaders
    # external - external EFI disk-based boot loaders
    # optical - EFI optical discs (CD, DVD, etc.)
    # hdbios - BIOS disk-based boot loaders
    # biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
    # cd - BIOS optical-disc boot loaders
    # manual - use stanzas later in this configuration file
    # Note that the legacy BIOS options require firmware support, which is
    # not present on all computers.
    # On UEFI PCs, default is internal,external,optical,manual
    # On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
    #scanfor internal,external,optical,manual
    scanfor internal,external,optical,manual
    # Delay for the specified number of seconds before scanning disks.
    # This can help some users who find that some of their disks
    # (usually external or optical discs) aren't detected initially,
    # but are detected after pressing Esc.
    # The default is 0.
    #scan_delay 5
    # When scanning volumes for EFI boot loaders, rEFInd always looks for
    # Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
    # and scans the root directory and every subdirectory of the /EFI directory
    # for additional boot loaders, but it doesn't recurse into these directories.
    # The also_scan_dirs token adds more directories to the scan list.
    # Directories are specified relative to the volume's root directory. This
    # option applies to ALL the volumes that rEFInd scans UNLESS you include
    # a volume name and colon before the directory name, as in "myvol:/somedir"
    # to scan the somedir directory only on the filesystem named myvol. If a
    # specified directory doesn't exist, it's ignored (no error condition
    # results). The default is to scan the "boot" directory in addition to
    # various hard-coded directories.
    #also_scan_dirs boot,ESP2:EFI/linux/kernels
    # Partitions to omit from scans. You must specify a volume by its
    # label, which you can obtain in an EFI shell by typing "vol", from
    # Linux by typing "blkid /dev/{devicename}", or by examining the
    # disk's label in various OSes' file browsers.
    # The default is "Recovery HD".
    #dont_scan_volumes "Recovery HD"
    # Directories that should NOT be scanned for boot loaders. By default,
    # rEFInd doesn't scan its own directory or the EFI/tools directory.
    # You can "blacklist" additional directories with this option, which
    # takes a list of directory names as options. You might do this to
    # keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
    # another boot loader or to exclude a directory that holds drivers
    # or non-bootloader utilities provided by a hardware manufacturer. If
    # a directory is listed both here and in also_scan_dirs, dont_scan_dirs
    # takes precedence. Note that this blacklist applies to ALL the
    # filesystems that rEFInd scans, not just the ESP, unless you precede
    # the directory name by a filesystem name, as in "myvol:EFI/somedir"
    # to exclude EFI/somedir from the scan on the myvol volume but not on
    # other volumes.
    #dont_scan_dirs ESP:/EFI/boot,EFI/Dell
    # Files that should NOT be included as EFI boot loaders (on the
    # first line of the display). If you're using a boot loader that
    # relies on support programs or drivers that are installed alongside
    # the main binary or if you want to "blacklist" certain loaders by
    # name rather than location, use this option. Note that this will
    # NOT prevent certain binaries from showing up in the second-row
    # set of tools. Most notably, MokManager.efi is in this blacklist,
    # but will show up as a tool if present in certain directories. You
    # can control the tools row with the showtools token.
    # The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
    #dont_scan_files shim.efi,MokManager.efi
    # Scan for Linux kernels that lack a ".efi" filename extension. This is
    # useful for better integration with Linux distributions that provide
    # kernels with EFI stub loaders but that don't give those kernels filenames
    # that end in ".efi", particularly if the kernels are stored on a
    # filesystem that the EFI can read. When uncommented, this option causes
    # all files in scanned directories with names that begin with "vmlinuz"
    # or "bzImage" to be included as loaders, even if they lack ".efi"
    # extensions. The drawback to this option is that it can pick up kernels
    # that lack EFI stub loader support and other files. Passing this option
    # a "0" value causes kernels without ".efi" extensions to NOT be scanned;
    # passing it alone or with any other value causes all kernels to be scanned.
    # Default is to NOT scan for kernels without ".efi" extensions.
    scan_all_linux_kernels
    # Set the maximum number of tags that can be displayed on the screen at
    # any time. If more loaders are discovered than this value, rEFInd shows
    # a subset in a scrolling list. If this value is set too high for the
    # screen to handle, it's reduced to the value that the screen can manage.
    # If this value is set to 0 (the default), it's adjusted to the number
    # that the screen can handle.
    #max_tags 0
    # Set the default menu selection. The available arguments match the
    # keyboard accelerators available within rEFInd. You may select the
    # default loader using:
    # - A digit between 1 and 9, in which case the Nth loader in the menu
    # will be the default.
    # - Any substring that corresponds to a portion of the loader's title
    # (usually the OS's name or boot loader's path).
    #default_selection 1
    default_selection "vmlinuz-linux"
    # Include a secondary configuration file within this one. This secondary
    # file is loaded as if its options appeared at the point of the "include"
    # token itself, so if you want to override a setting in the main file,
    # the secondary file must be referenced AFTER the setting you want to
    # override. Note that the secondary file may NOT load a tertiary file.
    #include manual.conf
    # Sample manual configuration stanzas. Each begins with the "menuentry"
    # keyword followed by a name that's to appear in the menu (use quotes
    # if you want the name to contain a space) and an open curly brace
    # ("{"). Each entry ends with a close curly brace ("}"). Common
    # keywords within each stanza include:
    # volume - identifies the filesystem from which subsequent files
    # are loaded. You can specify the volume by label or by
    # a number followed by a colon (as in "0:" for the first
    # filesystem or "1:" for the second).
    # loader - identifies the boot loader file
    # initrd - Specifies an initial RAM disk file
    # icon - specifies a custom boot loader icon
    # ostype - OS type code to determine boot options available by
    # pressing Insert. Valid values are "MacOS", "Linux",
    # "Windows", and "XOM". Case-sensitive.
    # graphics - set to "on" to enable graphics-mode boot (useful
    # mainly for MacOS) or "off" for text-mode boot.
    # Default is auto-detected from loader filename.
    # options - sets options to be passed to the boot loader; use
    # quotes if more than one option should be passed or
    # if any options use characters that might be changed
    # by rEFInd parsing procedures (=, /, #, or tab).
    # disabled - use alone or set to "yes" to disable this entry.
    # Note that you can use either DOS/Windows/EFI-style backslashes (\)
    # or Unix-style forward slashes (/) as directory separators. Either
    # way, all file references are on the ESP from which rEFInd was
    # launched.
    # Use of quotes around parameters causes them to be interpreted as
    # one keyword, and for parsing of special characters (spaces, =, /,
    # and #) to be disabled. This is useful mainly with the "options"
    # keyword. Use of quotes around parameters that specify filenames is
    # permissible, but you must then use backslashes instead of slashes,
    # except when you must pass a forward slash to the loader, as when
    # passing a root= option to a Linux kernel.
    # Below are several sample boot stanzas. All are disabled by default.
    # Find one similar to what you need, copy it, remove the "disabled" line,
    # and adjust the entries to suit your needs.
    # A sample entry for a Linux 3.3 kernel with its new EFI boot stub
    # support on a filesystem called "KERNELS". This entry includes
    # Linux-specific boot options and specification of an initial RAM disk.
    # Note uses of Linux-style forward slashes, even in the initrd
    # specification. Also note that a leading slash is optional in file
    # specifications.
    menuentry Linux {
    icon EFI/refind/icons/os_linux.icns
    volume KERNELS
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
    # A sample entry for loading Ubuntu using its standard name for
    # its GRUB 2 boot loader. Note uses of Linux-style forward slashes
    menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refined/icons/os_linux.icns
    disabled
    # A minimal ELILO entry, which probably offers nothing that
    # auto-detection can't accomplish.
    menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
    # Like the ELILO entry, this one offers nothing that auto-detection
    # can't do; but you might use it if you want to disable auto-detection
    # but still boot Windows....
    menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
    # EFI shells are programs just like boot loaders, and can be
    # launched in the same way. You can pass a shell the name of a
    # script that it's to run on the "options" line. The script
    # could initialize hardware and then launch an OS, or it could
    # do something entirely different.
    menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.icns
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
    # Mac OS is normally detected and run automatically; however,
    # if you want to do something unusual, a manual boot stanza may
    # be the way to do it. This one does nothing very unusual, but
    # it may serve as a starting point. Note that you'll almost
    # certainly need to change the "volume" line for this example
    # to work.
    menuentry "My Mac OS X" {
    icon \EFI\refind\icons\os_mac.icns
    volume "OS X boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
    cat /etc/fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda2
    UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda4
    UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda1
    # UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    UUID=5447-7409 /boot vfat noatime 0 2
    # /dev/sda3
    UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
    This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
    EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
    EDIT2: @swordfish Removed /boot/EFI/arch.
    Last edited by donniezazen (2013-04-04 06:37:07)

    I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
    I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that  I have in /boot/EFI/tools/Shells.
    ls -R /boot
    /boot:
    EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
    /boot/EFI:
    drivers refind tools
    /boot/EFI/drivers:
    ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
    /boot/EFI/refind:
    icons refind.conf refind_x64.efi
    /boot/EFI/refind/icons:
    ### Icons
    /boot/EFI/tools:
    Shell.efi
    # refind.conf
    # Configuration file for the rEFInd boot menu
    # Timeout in seconds for the main menu screen. Setting the timeout to 0
    # disables automatic booting (i.e., no timeout).
    timeout 5
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner (built-in or loaded via "banner")
    # label - boot option text label in the menu
    # singleuser - remove the submenu options to boot Mac OS X in single-user
    # or verbose modes; affects ONLY MacOS X
    # safemode - remove the submenu option to boot Mac OS X in "safe mode"
    # hwtest - the submenu option to run Apple's hardware test
    # arrows - scroll arrows on the OS selection tag line
    # hints - brief command summary in the menu
    # editor - the options editor (+, F2, or Insert on boot options menu)
    # all - all of the above
    # Default is none of these (all elements active)
    #hideui singleuser
    #hideui all
    # Set the name of a subdirectory in which icons are stored. Icons must
    # have the same names they have in the standard directory. The directory
    # name is specified relative to the main rEFInd binary's directory. If
    # an icon can't be found in the specified directory, an attempt is made
    # to load it from the default directory; thus, you can replace just some
    # icons in your own directory and rely on the default for others.
    # Default is "icons".
    #icons_dir myicons
    # Use a custom title banner instead of the rEFInd icon and name. The file
    # path is relative to the directory where refind.efi is located. The color
    # in the top left corner of the image is used as the background color
    # for the menu screens. Currently uncompressed BMP images with color
    # depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
    #banner hostname.bmp
    #banner mybanner.png
    # Custom images for the selection background. There is a big one (144 x 144)
    # for the OS icons, and a small one (64 x 64) for the function icons in the
    # second row. If only a small image is given, that one is also used for
    # the big icons by stretching it in the middle. If only a big one is given,
    # the built-in default will be used for the small icons.
    # Like the banner option above, these options take a filename of an
    # uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
    # or a PNG image. The PNG format is required if you need transparency
    # support (to let you "see through" to a full-screen banner).
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    # Set the font to be used for all textual displays in graphics mode.
    # The font must be a PNG file with alpha channel transparency. It must
    # contain ASCII characters 32-126 (space through tilde), inclusive, plus
    # a glyph to be displayed in place of characters outside of this range,
    # for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
    # may be of any size, although large fonts can produce display
    # irregularities.
    # The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
    #font myfont.png
    # Use text mode only. When enabled, this option forces rEFInd into text mode.
    # Passing this option a "0" value causes graphics mode to be used. Pasing
    # it no value or any non-0 value causes text mode to be used.
    # Default is to use graphics mode.
    #textonly
    textonly
    # Set the EFI text mode to be used for textual displays. This option
    # takes a single digit that refers to a mode number. Mode 0 is normally
    # 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
    # modes. Mode 1024 is a special code that tells rEFInd to not set the
    # text mode; it uses whatever was in use when the program was launched.
    # If you specify an invalid mode, rEFInd pauses during boot to inform
    # you of valid modes.
    # CAUTION: On VirtualBox, and perhaps on some real computers, specifying
    # a text mode and uncommenting the "textonly" option while NOT specifying
    # a resolution can result in an unusable display in the booted OS.
    # Default is 1024 (no change)
    #textmode 2
    textmode 1024
    # Set the screen's video resolution. Pass this option either:
    # * two values, corresponding to the X and Y resolutions
    # * one value, corresponding to a GOP (UEFI) video mode
    # Note that not all resolutions are supported. On UEFI systems, passing
    # an incorrect value results in a message being shown on the screen to
    # that effect, along with a list of supported modes. On EFI 1.x systems
    # (e.g., Macintoshes), setting an incorrect mode silently fails. On both
    # types of systems, setting an incorrect resolution results in the default
    # resolution being used. A resolution of 1024x768 usually works, but higher
    # values often don't.
    # Default is "0 0" (use the system default resolution, usually 800x600).
    #resolution 1024 768
    #resolution 3
    resolution 1024 768
    # Launch specified OSes in graphics mode. By default, rEFInd switches
    # to text mode and displays basic pre-launch information when launching
    # all OSes except OS X. Using graphics mode can produce a more seamless
    # transition, but displays no information, which can make matters
    # difficult if you must debug a problem. Also, on at least one known
    # computer, using graphics mode prevents a crash when using the Linux
    # kernel's EFI stub loader. You can specify an empty list to boot all
    # OSes in text mode.
    # Valid options:
    # osx - Mac OS X
    # linux - A Linux kernel with EFI stub loader
    # elilo - The ELILO boot loader
    # grub - The GRUB (Legacy or 2) boot loader
    # windows - Microsoft Windows
    # Default value: osx
    #use_graphics_for osx,linux
    # Which non-bootloader tools to show on the tools line, and in what
    # order to display them:
    # shell - the EFI shell (requires external program; see rEFInd
    # documentation for details)
    # gptsync - the (dangerous) gptsync.efi utility (requires external
    # program; see rEFInd documentation for details)
    # apple_recovery - boots the Apple Recovery HD partition, if present
    # mok_tool - makes available the Machine Owner Key (MOK) maintenance
    # tool, MokManager.efi, used on Secure Boot systems
    # about - an "about this program" option
    # exit - a tag to exit from rEFInd
    # shutdown - shuts down the computer (a bug causes this to reboot
    # EFI systems)
    # reboot - a tag to reboot the computer
    # Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
    #showtools shell, mok_tool, about, reboot, exit
    showtools shell, about, reboot, exit
    # Directories in which to search for EFI drivers. These drivers can
    # provide filesystem support, give access to hard disks on plug-in
    # controllers, etc. In most cases none are needed, but if you add
    # EFI drivers and you want rEFInd to automatically load them, you
    # should specify one or more paths here. rEFInd always scans the
    # "drivers" and "drivers_{arch}" subdirectories of its own installation
    # directory (where "{arch}" is your architecture code); this option
    # specifies ADDITIONAL directories to scan.
    # Default is to scan no additional directories for EFI drivers
    #scan_driver_dirs EFI/tools/drivers,drivers
    scan_driver_dirs EFI/tools/drivers,drivers
    # Which types of boot loaders to search, and in what order to display them:
    # internal - internal EFI disk-based boot loaders
    # external - external EFI disk-based boot loaders
    # optical - EFI optical discs (CD, DVD, etc.)
    # hdbios - BIOS disk-based boot loaders
    # biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
    # cd - BIOS optical-disc boot loaders
    # manual - use stanzas later in this configuration file
    # Note that the legacy BIOS options require firmware support, which is
    # not present on all computers.
    # On UEFI PCs, default is internal,external,optical,manual
    # On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
    #scanfor internal,external,optical,manual
    scanfor internal,external,optical,manual
    # Delay for the specified number of seconds before scanning disks.
    # This can help some users who find that some of their disks
    # (usually external or optical discs) aren't detected initially,
    # but are detected after pressing Esc.
    # The default is 0.
    #scan_delay 5
    # When scanning volumes for EFI boot loaders, rEFInd always looks for
    # Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
    # and scans the root directory and every subdirectory of the /EFI directory
    # for additional boot loaders, but it doesn't recurse into these directories.
    # The also_scan_dirs token adds more directories to the scan list.
    # Directories are specified relative to the volume's root directory. This
    # option applies to ALL the volumes that rEFInd scans UNLESS you include
    # a volume name and colon before the directory name, as in "myvol:/somedir"
    # to scan the somedir directory only on the filesystem named myvol. If a
    # specified directory doesn't exist, it's ignored (no error condition
    # results). The default is to scan the "boot" directory in addition to
    # various hard-coded directories.
    #also_scan_dirs boot,ESP2:EFI/linux/kernels
    # Partitions to omit from scans. You must specify a volume by its
    # label, which you can obtain in an EFI shell by typing "vol", from
    # Linux by typing "blkid /dev/{devicename}", or by examining the
    # disk's label in various OSes' file browsers.
    # The default is "Recovery HD".
    #dont_scan_volumes "Recovery HD"
    # Directories that should NOT be scanned for boot loaders. By default,
    # rEFInd doesn't scan its own directory or the EFI/tools directory.
    # You can "blacklist" additional directories with this option, which
    # takes a list of directory names as options. You might do this to
    # keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
    # another boot loader or to exclude a directory that holds drivers
    # or non-bootloader utilities provided by a hardware manufacturer. If
    # a directory is listed both here and in also_scan_dirs, dont_scan_dirs
    # takes precedence. Note that this blacklist applies to ALL the
    # filesystems that rEFInd scans, not just the ESP, unless you precede
    # the directory name by a filesystem name, as in "myvol:EFI/somedir"
    # to exclude EFI/somedir from the scan on the myvol volume but not on
    # other volumes.
    #dont_scan_dirs ESP:/EFI/boot,EFI/Dell
    # Files that should NOT be included as EFI boot loaders (on the
    # first line of the display). If you're using a boot loader that
    # relies on support programs or drivers that are installed alongside
    # the main binary or if you want to "blacklist" certain loaders by
    # name rather than location, use this option. Note that this will
    # NOT prevent certain binaries from showing up in the second-row
    # set of tools. Most notably, MokManager.efi is in this blacklist,
    # but will show up as a tool if present in certain directories. You
    # can control the tools row with the showtools token.
    # The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
    #dont_scan_files shim.efi,MokManager.efi
    # Scan for Linux kernels that lack a ".efi" filename extension. This is
    # useful for better integration with Linux distributions that provide
    # kernels with EFI stub loaders but that don't give those kernels filenames
    # that end in ".efi", particularly if the kernels are stored on a
    # filesystem that the EFI can read. When uncommented, this option causes
    # all files in scanned directories with names that begin with "vmlinuz"
    # or "bzImage" to be included as loaders, even if they lack ".efi"
    # extensions. The drawback to this option is that it can pick up kernels
    # that lack EFI stub loader support and other files. Passing this option
    # a "0" value causes kernels without ".efi" extensions to NOT be scanned;
    # passing it alone or with any other value causes all kernels to be scanned.
    # Default is to NOT scan for kernels without ".efi" extensions.
    scan_all_linux_kernels
    # Set the maximum number of tags that can be displayed on the screen at
    # any time. If more loaders are discovered than this value, rEFInd shows
    # a subset in a scrolling list. If this value is set too high for the
    # screen to handle, it's reduced to the value that the screen can manage.
    # If this value is set to 0 (the default), it's adjusted to the number
    # that the screen can handle.
    #max_tags 0
    # Set the default menu selection. The available arguments match the
    # keyboard accelerators available within rEFInd. You may select the
    # default loader using:
    # - A digit between 1 and 9, in which case the Nth loader in the menu
    # will be the default.
    # - Any substring that corresponds to a portion of the loader's title
    # (usually the OS's name or boot loader's path).
    #default_selection 1
    # Include a secondary configuration file within this one. This secondary
    # file is loaded as if its options appeared at the point of the "include"
    # token itself, so if you want to override a setting in the main file,
    # the secondary file must be referenced AFTER the setting you want to
    # override. Note that the secondary file may NOT load a tertiary file.
    #include manual.conf
    # Sample manual configuration stanzas. Each begins with the "menuentry"
    # keyword followed by a name that's to appear in the menu (use quotes
    # if you want the name to contain a space) and an open curly brace
    # ("{"). Each entry ends with a close curly brace ("}"). Common
    # keywords within each stanza include:
    # volume - identifies the filesystem from which subsequent files
    # are loaded. You can specify the volume by label or by
    # a number followed by a colon (as in "0:" for the first
    # filesystem or "1:" for the second).
    # loader - identifies the boot loader file
    # initrd - Specifies an initial RAM disk file
    # icon - specifies a custom boot loader icon
    # ostype - OS type code to determine boot options available by
    # pressing Insert. Valid values are "MacOS", "Linux",
    # "Windows", and "XOM". Case-sensitive.
    # graphics - set to "on" to enable graphics-mode boot (useful
    # mainly for MacOS) or "off" for text-mode boot.
    # Default is auto-detected from loader filename.
    # options - sets options to be passed to the boot loader; use
    # quotes if more than one option should be passed or
    # if any options use characters that might be changed
    # by rEFInd parsing procedures (=, /, #, or tab).
    # disabled - use alone or set to "yes" to disable this entry.
    # Note that you can use either DOS/Windows/EFI-style backslashes (\)
    # or Unix-style forward slashes (/) as directory separators. Either
    # way, all file references are on the ESP from which rEFInd was
    # launched.
    # Use of quotes around parameters causes them to be interpreted as
    # one keyword, and for parsing of special characters (spaces, =, /,
    # and #) to be disabled. This is useful mainly with the "options"
    # keyword. Use of quotes around parameters that specify filenames is
    # permissible, but you must then use backslashes instead of slashes,
    # except when you must pass a forward slash to the loader, as when
    # passing a root= option to a Linux kernel.
    # Below are several sample boot stanzas. All are disabled by default.
    # Find one similar to what you need, copy it, remove the "disabled" line,
    # and adjust the entries to suit your needs.
    # A sample entry for a Linux 3.3 kernel with its new EFI boot stub
    # support on a filesystem called "KERNELS". This entry includes
    # Linux-specific boot options and specification of an initial RAM disk.
    # Note uses of Linux-style forward slashes, even in the initrd
    # specification. Also note that a leading slash is optional in file
    # specifications.
    menuentry Linux {
    icon EFI/refind/icons/os_linux.icns
    volume KERNELS
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
    # A sample entry for loading Ubuntu using its standard name for
    # its GRUB 2 boot loader. Note uses of Linux-style forward slashes
    menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refined/icons/os_linux.icns
    disabled
    # A minimal ELILO entry, which probably offers nothing that
    # auto-detection can't accomplish.
    menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
    # Like the ELILO entry, this one offers nothing that auto-detection
    # can't do; but you might use it if you want to disable auto-detection
    # but still boot Windows....
    menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
    # EFI shells are programs just like boot loaders, and can be
    # launched in the same way. You can pass a shell the name of a
    # script that it's to run on the "options" line. The script
    # could initialize hardware and then launch an OS, or it could
    # do something entirely different.
    menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.icns
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
    # Mac OS is normally detected and run automatically; however,
    # if you want to do something unusual, a manual boot stanza may
    # be the way to do it. This one does nothing very unusual, but
    # it may serve as a starting point. Note that you'll almost
    # certainly need to change the "volume" line for this example
    # to work.
    menuentry "My Mac OS X" {
    icon \EFI\refind\icons\os_mac.icns
    volume "OS X boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
    Thanks for suggesting to try older ISO.
    UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
    Last edited by donniezazen (2013-04-04 06:43:16)

  • Is there a way to disable the blue triangle warning tag?

    I created a formula to generate dates a week apart (see screen grab below).  It works, but in most months, I get a blue triangle error tag stating that the day was greater than 31.  This happens when the previous date was the 25th of the month or later and the intermediate calculation generates a day of 32 or above, even though the displayed date does increment the month and display the correct single digit day. 
    I know I can manually sellect each blue triangle individually and "ignore" it, but the more dates I generate the more blue triangle warnings I get.
    It there a way to programatically / automatically not display blue triangle warning tags in a select set of cells?
    or
    Is there a better formula that I can use to generate dates a week apart that will not generate blue triangle warnings?

    Warning triangles: No way that I've found.
    Incrementing dates: Method 1—use auto-fill.
    First date in A2, Second date in A3.
    Select both cells, then drag the Fill control down the column. Dates will increment according the difference between the two starting dates.
    Incrementing dates: Method 2—use a simple formula:
    First date in A2.
    In A3: =A2+7
    Select A3 to the bottom of the column (see note below)
    Go Insert > Fill > Fill down.
    Done.
    Regards,
    Barry
    NOTE: re selecting;
    Click any cell to make the table active and show the row and column reference tabs.
    Click the reference tabe for column A to select the entire column.
    Command click A1, then A2 to remove these two from the selection.
    NOTE 2: The information here is also readily accessible in the Numbers '09 User Guide, an easily read pdf file well worth spending an hour or two browsing. The guide may be downloaded via the Help menu in Numbers.
    B

  • My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you

    My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you think it is? It won't recognize any hard drive I put in the machine, so might it be the sata cable?

    Boot the Recvoery USB, use Disk Utility to select the internal drive makers namea and size on the left.
    Now select erase and select the midde option and click erase, it will take a bit to complete but it's best for the drive.
    Now select Partiton tab, click the big box and Options: GUID and then Format: OS X Extended journaled and click apply.
    Quit and you should be able to install OS X now with your Apple ID and password.
    see
    http://osxdaily.com/2011/08/08/lion-recovery-disk-assistant-tool-makes-external- lion-boot-recovery-drives/

  • The list of extensions for InDesign now have a yellow triangle warning symbol in front of a good many of the extensions and when moused over i get one of two messages:  "Extensions may not function properly because it does not meet the dependency conditio

    The list of extensions for InDesign now have a yellow triangle warning symbol in front of a good many of the extensions and when moused over i get one of two messages:
    "Extensions may not function properly because it does not meet the dependency condition."
    OR
    Extension Status is not consistent with extension set configuration."
    The reason I opened the Extension Manager in the first place was to check to see if I had installed a third party extension.  And I was presented with these warning symbols.  I haven't added anything, I haven't done anything that would cause this.
    Does anyone know how to fix this???
    I am running OSX 10.9.5; Indesign CS6 version 8.0.2 And Adobe Extension Manager version  6.0.8.28.
    Thanks in advance!
    Nina

    Many InDesign pre-installed extensions (Those extensions you have immediately after InDesign installation) define dependency rules in their mxi files. Dependency means that one extension works well only if one or more other extensions are installed and enabled. If this condition is not met, the yellow triangle warning will be shown.
    You can select an extension with warning, click "Advanced" tag page in the lower right panel. You will see "This extension has dependency on: <extension name> ...". Check whether every extensions listed here are available and enabled. If not, enable them. Repeat these steps for all the extensions which have warning.

  • Arch & Windows 8 Dual Boot -- Windows Boot Loader loads grub-rescue

    Arch works fine,but as it always happens Windows boot went down. Both OS are EFI.
    Note that boot secure and fast boot were disabled for Windows 8.
    I used os-prober, but did not fix anything; so, I removed it. I tried to hack things out using boot-repair from Ubuntu, but it requires a repository, grub-efi, from Ubuntu that Arch doesn't have.
    I am trying to modify files in grub.d and grub.cfg and hopefully fix something.
    Exact description:
    - archgrub loads and shows 3 entries. Two for Arch that load the sys succesfully and one for Windows 8 that fails.
    - When I try to execute Windows from grub, it brings me to a grub rescue>
      and shows error /boot/grub/x86_64-efi/normal.mod not found
      As far as I am concerned this .mod is from Linux, so I don't know why it is being called into Windows loading procedures.
    lsblk returns:
    [jav@localhost ~]$ lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 931.5G 0 disk
    |-sda1 8:1 0 1000M 0 part
    |-sda2 8:2 0 260M 0 part
    |-sda3 8:3 0 1000M 0 part
    |-sda4 8:4 0 128M 0 part
    |-sda5 8:5 0 605.3G 0 part
    |-sda6 8:6 0 5.4G 0 part /boot/efi
    |-sda7 8:7 0 25G 0 part
    |-sda8 8:8 0 20G 0 part
    |-sda9 8:9 0 244.1G 0 part /
    `-sda10 8:10 0 29.3G 0 part
    sr0 11:0 1 1024M 0 rom
    Here's the output of fdisk. Another weird thing is that sometimes ubuntu would show on my terminal. See the first line below, "jav@ubuntu"?!
    [jav@ubuntu ~]$ sudo fdisk -l
    [sudo] password for jav:
    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: [i deleted this]
    Device Start End Size Type
    /dev/sda1 2048 2050047 1000M Windows recovery environment
    /dev/sda2 2050048 2582527 260M EFI System
    /dev/sda3 2582528 4630527 1000M unknown
    /dev/sda4 4630528 4892671 128M Microsoft reserved
    /dev/sda5 4892672 1274335231 605.3G Microsoft basic data
    /dev/sda6 1847777280 1859151871 5.4G EFI System
    /dev/sda7 1859151872 1911580671 25G Microsoft basic data
    /dev/sda8 1911580672 1953523711 20G Windows recovery environment
    /dev/sda9 1335775232 1847777279 244.1G Linux filesystem
    /dev/sda10 1274335232 1335775231 29.3G Microsoft basic data
    And, bootinfoscript output:
    Boot Info Script 0.61 [1 April 2012]
    ============================= Boot Info Summary: ===============================
    => No boot loader is installed in the MBR of /dev/sda.
    sda1: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    sda2: __________________________________________________________________________
    File system: vfat
    Boot sector type: Windows 7: FAT32
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
    /efi/ubuntu/grubx64.efi
    sda3: __________________________________________________________________________
    File system: vfat
    Boot sector type: Windows 7: FAT32
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
    /efi/ubuntu/grubx64.efi /bootmgr /boot/bcd
    sda4: __________________________________________________________________________
    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''
    sda5: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
    sda6: __________________________________________________________________________
    File system: vfat
    Boot sector type: SYSLINUX 6.02 ... :..(:,:0:4:8:....D:H:L:[.T:[.\:`:d:[.l:p:t:x:|:.:.:.:.:.:.:.:.....................
    Boot sector info: Syslinux looks at sector 99102 of /dev/sda6 for its
    second stage. SYSLINUX is installed in the /syslinux
    directory. No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /grub/grub.cfg /syslinux/syslinux.cfg
    /syslinux/ldlinux.sys
    sda7: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    sda8: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    sda9: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Arch Linux ()
    Boot files: /etc/fstab
    sda10: _________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files:
    ============================ Drive/Partition Info: =============================
    Drive: sda _____________________________________________________________________
    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
    GUID Partition Table detected.
    Partition Start Sector End Sector # of Sectors System
    /dev/sda1 2,048 2,050,047 2,048,000 Windows Recovery Environment (Windows)
    /dev/sda2 2,050,048 2,582,527 532,480 EFI System partition
    /dev/sda3 2,582,528 4,630,527 2,048,000 -
    /dev/sda4 4,630,528 4,892,671 262,144 Microsoft Reserved Partition (Windows)
    /dev/sda5 4,892,672 1,274,335,231 1,269,442,560 Data partition (Windows/Linux)
    /dev/sda6 1,847,777,280 1,859,151,871 11,374,592 EFI System partition
    /dev/sda7 1,859,151,872 1,911,580,671 52,428,800 Data partition (Windows/Linux)
    /dev/sda8 1,911,580,672 1,953,523,711 41,943,040 Windows Recovery Environment (Windows)
    /dev/sda9 1,335,775,232 1,847,777,279 512,002,048 Data partition (Linux)
    /dev/sda10 1,274,335,232 1,335,775,231 61,440,000 Data partition (Windows/Linux)
    "blkid" output: ________________________________________________________________
    Device UUID TYPE LABEL
    /dev/sda1 CE62D9F062D9DCF1 ntfs WINRE_DRV
    /dev/sda10 150a8788-6049-45ed-85af-ded92a2c0801 ext4
    /dev/sda2 16DC-8816 vfat SYSTEM_DRV
    /dev/sda3 7CDD-0403 vfat LRS_ESP
    /dev/sda4
    /dev/sda5 40E4E0CFE4E0C7EC ntfs Windows8_OS
    /dev/sda6 9C3F-2A9E vfat
    /dev/sda7 7240E43740E40427 ntfs LENOVO
    /dev/sda8 422CE5EA2CE5D945 ntfs PBR_DRV
    /dev/sda9 1a765403-f251-43d8-8edf-c191475d3837 ext4
    ================================ Mount points: =================================
    Device Mount_Point Type Options
    /dev/sda6 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    /dev/sda6 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    /dev/sda9 / ext4 (rw,relatime,data=ordered)
    ============================= sda6/grub/grub.cfg: ==============================
    # 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
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    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_gpt
    insmod ext2
    set root='hd0,gpt9'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
    else
    search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    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-1a765403-f251-43d8-8edf-c191475d3837' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt6'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
    else
    search --no-floppy --fs-uuid --set=root 9C3F-2A9E
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /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-1a765403-f251-43d8-8edf-c191475d3837' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt6'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
    else
    search --no-floppy --fs-uuid --set=root 9C3F-2A9E
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ## Attempt at fixing grub
    # insmod fat
    # set root='hd0,gpt6'
    ### BEGIN /etc/grub.d/30_os-prober ###
    #menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
    # insmod part_gpt
    # insmod fat
    # set root='hd0,gpt2'
    # if [ x$feature_platform_search_hint = xy ]; then
    # search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
    # else
    # search --no-floppy --fs-uuid --set=root 16DC-8816
    # fi
    # chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    menuentry "Windows 8 UEFI" {
    set root='(hd0,gpt2)'
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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 ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    ========================= sda6/syslinux/syslinux.cfg: ==========================
    # Config file for Syslinux -
    # /boot/syslinux/syslinux.cfg
    # Comboot modules:
    # * menu.c32 - provides a text menu
    # * vesamenu.c32 - provides a graphical menu
    # * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
    # * hdt.c32 - hardware detection tool
    # * reboot.c32 - reboots the system
    # To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
    # If /usr and /boot are on the same file system, symlink the files instead
    # of copying them.
    # If you do not use a menu, a 'boot:' prompt will be shown and the system
    # will boot automatically after 5 seconds.
    # Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
    # The wiki provides further configuration examples
    DEFAULT arch
    PROMPT 0 # Set to 1 if you always want to display the boot: prompt
    TIMEOUT 50
    # You can create syslinux keymaps with the keytab-lilo tool
    #KBDMAP de.ktl
    # Menu Configuration
    # Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
    UI menu.c32
    #UI vesamenu.c32
    # Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
    MENU TITLE Arch Linux
    #MENU BACKGROUND splash.png
    MENU COLOR border 30;44 #40ffffff #a0000000 std
    MENU COLOR title 1;36;44 #9033ccff #a0000000 std
    MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
    MENU COLOR unsel 37;44 #50ffffff #a0000000 std
    MENU COLOR help 37;40 #c0ffffff #a0000000 std
    MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
    MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
    MENU COLOR msg07 37;40 #90ffffff #a0000000 std
    MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
    # boot sections follow
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda3 rw
    INITRD ../initramfs-linux.img
    LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda3 rw
    INITRD ../initramfs-linux-fallback.img
    #LABEL windows
    # MENU LABEL Windows
    # COM32 chain.c32
    # APPEND hd0 1
    LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32
    LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32
    LABEL poweroff
    MENU LABEL Poweroff
    COM32 poweroff.c32
    =================== sda6: Location of files loaded by Grub: ====================
    GiB - GB File Fragment(s)
    ================= sda6: Location of files loaded by Syslinux: ==================
    GiB - GB File Fragment(s)
    ============== sda6: Version of COM32(R) files used by Syslinux: ===============
    syslinux/cat.c32 : not a COM32/COM32R module
    syslinux/chain.c32 : not a COM32/COM32R module
    syslinux/cmd.c32 : not a COM32/COM32R module
    syslinux/config.c32 : not a COM32/COM32R module
    syslinux/cptime.c32 : not a COM32/COM32R module
    syslinux/cpuid.c32 : not a COM32/COM32R module
    syslinux/cpuidtest.c32 : not a COM32/COM32R module
    syslinux/debug.c32 : not a COM32/COM32R module
    syslinux/disk.c32 : not a COM32/COM32R module
    syslinux/dmitest.c32 : not a COM32/COM32R module
    syslinux/elf.c32 : not a COM32/COM32R module
    syslinux/ethersel.c32 : not a COM32/COM32R module
    syslinux/gfxboot.c32 : not a COM32/COM32R module
    syslinux/gpxecmd.c32 : not a COM32/COM32R module
    syslinux/hdt.c32 : not a COM32/COM32R module
    syslinux/hexdump.c32 : not a COM32/COM32R module
    syslinux/host.c32 : not a COM32/COM32R module
    syslinux/ifcpu.c32 : not a COM32/COM32R module
    syslinux/ifcpu64.c32 : not a COM32/COM32R module
    syslinux/ifmemdsk.c32 : not a COM32/COM32R module
    syslinux/ifplop.c32 : not a COM32/COM32R module
    syslinux/kbdmap.c32 : not a COM32/COM32R module
    syslinux/kontron_wdt.c32 : not a COM32/COM32R module
    syslinux/ldlinux.c32 : not a COM32/COM32R module
    syslinux/libcom32.c32 : not a COM32/COM32R module
    syslinux/libgpl.c32 : not a COM32/COM32R module
    syslinux/liblua.c32 : not a COM32/COM32R module
    syslinux/libmenu.c32 : not a COM32/COM32R module
    syslinux/libutil.c32 : not a COM32/COM32R module
    syslinux/linux.c32 : not a COM32/COM32R module
    syslinux/ls.c32 : not a COM32/COM32R module
    syslinux/lua.c32 : not a COM32/COM32R module
    syslinux/mboot.c32 : not a COM32/COM32R module
    syslinux/meminfo.c32 : not a COM32/COM32R module
    syslinux/menu.c32 : not a COM32/COM32R module
    syslinux/pcitest.c32 : not a COM32/COM32R module
    syslinux/pmload.c32 : not a COM32/COM32R module
    syslinux/poweroff.c32 : not a COM32/COM32R module
    syslinux/prdhcp.c32 : not a COM32/COM32R module
    syslinux/pwd.c32 : not a COM32/COM32R module
    syslinux/pxechn.c32 : not a COM32/COM32R module
    syslinux/reboot.c32 : not a COM32/COM32R module
    syslinux/rosh.c32 : not a COM32/COM32R module
    syslinux/sanboot.c32 : not a COM32/COM32R module
    syslinux/sdi.c32 : not a COM32/COM32R module
    syslinux/sysdump.c32 : not a COM32/COM32R module
    syslinux/vesainfo.c32 : not a COM32/COM32R module
    syslinux/vesamenu.c32 : not a COM32/COM32R module
    syslinux/vpdtest.c32 : not a COM32/COM32R module
    syslinux/whichsys.c32 : not a COM32/COM32R module
    syslinux/zzjson.c32 : not a COM32/COM32R module
    =============================== sda9/etc/fstab: ================================
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda9
    UUID=1a765403-f251-43d8-8edf-c191475d3837 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda6
    #UUID=9C3F-2A9E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    UUID=9C3F-2A9E /boot vfat defaults 0 2
    UUID=9C3F-2A9E /boot/efi vfat defaults 0 1
    ============== sda9: Version of COM32(R) files used by Syslinux: ===============
    boot/syslinux/cat.c32 : not a COM32/COM32R module
    boot/syslinux/chain.c32 : not a COM32/COM32R module
    boot/syslinux/cmd.c32 : not a COM32/COM32R module
    boot/syslinux/config.c32 : not a COM32/COM32R module
    boot/syslinux/cptime.c32 : not a COM32/COM32R module
    boot/syslinux/cpuid.c32 : not a COM32/COM32R module
    boot/syslinux/cpuidtest.c32 : not a COM32/COM32R module
    boot/syslinux/debug.c32 : not a COM32/COM32R module
    boot/syslinux/disk.c32 : not a COM32/COM32R module
    boot/syslinux/dmitest.c32 : not a COM32/COM32R module
    boot/syslinux/elf.c32 : not a COM32/COM32R module
    boot/syslinux/ethersel.c32 : not a COM32/COM32R module
    boot/syslinux/gfxboot.c32 : not a COM32/COM32R module
    boot/syslinux/gpxecmd.c32 : not a COM32/COM32R module
    boot/syslinux/hdt.c32 : not a COM32/COM32R module
    boot/syslinux/hexdump.c32 : not a COM32/COM32R module
    boot/syslinux/host.c32 : not a COM32/COM32R module
    boot/syslinux/ifcpu.c32 : not a COM32/COM32R module
    boot/syslinux/ifcpu64.c32 : not a COM32/COM32R module
    boot/syslinux/ifmemdsk.c32 : not a COM32/COM32R module
    boot/syslinux/ifplop.c32 : not a COM32/COM32R module
    boot/syslinux/kbdmap.c32 : not a COM32/COM32R module
    boot/syslinux/kontron_wdt.c32 : not a COM32/COM32R module
    boot/syslinux/ldlinux.c32 : not a COM32/COM32R module
    boot/syslinux/libcom32.c32 : not a COM32/COM32R module
    boot/syslinux/libgpl.c32 : not a COM32/COM32R module
    boot/syslinux/liblua.c32 : not a COM32/COM32R module
    boot/syslinux/libmenu.c32 : not a COM32/COM32R module
    boot/syslinux/libutil.c32 : not a COM32/COM32R module
    boot/syslinux/linux.c32 : not a COM32/COM32R module
    boot/syslinux/ls.c32 : not a COM32/COM32R module
    boot/syslinux/lua.c32 : not a COM32/COM32R module
    boot/syslinux/mboot.c32 : not a COM32/COM32R module
    boot/syslinux/meminfo.c32 : not a COM32/COM32R module
    boot/syslinux/menu.c32 : not a COM32/COM32R module
    boot/syslinux/pcitest.c32 : not a COM32/COM32R module
    boot/syslinux/pmload.c32 : not a COM32/COM32R module
    boot/syslinux/poweroff.c32 : not a COM32/COM32R module
    boot/syslinux/prdhcp.c32 : not a COM32/COM32R module
    boot/syslinux/pwd.c32 : not a COM32/COM32R module
    boot/syslinux/pxechn.c32 : not a COM32/COM32R module
    boot/syslinux/reboot.c32 : not a COM32/COM32R module
    boot/syslinux/rosh.c32 : not a COM32/COM32R module
    boot/syslinux/sanboot.c32 : not a COM32/COM32R module
    boot/syslinux/sdi.c32 : not a COM32/COM32R module
    boot/syslinux/sysdump.c32 : not a COM32/COM32R module
    boot/syslinux/vesainfo.c32 : not a COM32/COM32R module
    boot/syslinux/vesamenu.c32 : not a COM32/COM32R module
    boot/syslinux/vpdtest.c32 : not a COM32/COM32R module
    boot/syslinux/whichsys.c32 : not a COM32/COM32R module
    boot/syslinux/zzjson.c32 : not a COM32/COM32R module
    ======================== Unknown MBRs/Boot Sectors/etc: ========================
    Unknown GPT Partiton Type
    e7afbfbf4fa38a449a5b6213eb736c22
    ========= Devices which don't seem to have a corresponding hard drive: =========
    sdb
    =============================== StdErr Messages: ===============================
    cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
    cat: /tmp/BootInfo-p9ML2Cte/Tmp_Log: No such file or directory
    /dev/cdrom: open failed: No medium found
    /dev/sdb: open failed: No medium found
    No volume groups found
    mdadm: No arrays found in config file or automatically
    Any ideas?
    Here's my grub.cfg:
    # 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
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    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_gpt
    insmod ext2
    set root='hd0,gpt9'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 1a765403-f251-43d8-8edf-c191475d3837
    else
    search --no-floppy --fs-uuid --set=root 1a765403-f251-43d8-8edf-c191475d3837
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    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-1a765403-f251-43d8-8edf-c191475d3837' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt6'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
    else
    search --no-floppy --fs-uuid --set=root 9C3F-2A9E
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /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-1a765403-f251-43d8-8edf-c191475d3837' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt6'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 9C3F-2A9E
    else
    search --no-floppy --fs-uuid --set=root 9C3F-2A9E
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=1a765403-f251-43d8-8edf-c191475d3837 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /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/30_os-prober ###
    menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-16DC-8816' {
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 16DC-8816
    else
    search --no-floppy --fs-uuid --set=root 16DC-8816
    fi
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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 ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    Last edited by knowNothing23 (2013-12-30 00:17:02)

    Hi,
    New to this forum, joined today in anticipation of trying an install of AL...For whatever this may be worth:
    I have an HP Pavillion desktop that came with Windows 8 (now 8.1), & has, of course, a UEFI boot system. I tried earlier to install Ubuntu Studio (which I currently run) on the same disk as Windows (/dev/sda), I made (I believe) a huge mistake in trying to install as LVM/ext4... wiped out my Windows install & made the UEFI unavailable... I had to do a complete re-install of Windows (fortunately, I did the recommended system backup, using 4 DVD's!) so then I tried a (non LVM) install on an external usb 3.0, with the Grub 2 on the external disk (great access time, & it worked fine...  IMO)...
    One other item: as I have been trying to find the right flavor of Linux for my main purposes, I have been trying various distros. & having to try to learn to negotiate the UEFI, secure/legacy procedures (still learning)... As I was unsure of installing rEFind... I did down load the .iso, burn it to a CD...
    http://www.rodsbooks.com/refind/getting.html
    & in  legacy mode, found that simply putting it (rEFind CD into the CD/DVD player, which in the UEFI it is labeled something like HP/UEFI CD/DVD), & then launching it, rEFind worked for some other distros...that is, I was able to boot into my Linux distros, even bypassing Grub), as well as having the option of booting Windows. It may seem trivial that I say this (it maybe is), but I have not seen anywhere (I have scoured the internet rather well) this mentioned as a possibility (though it, of course, would not make such a good permanent solution, especially for computers like mine that have only one CD/DVD player).
    HenryP

  • Bootcamp not showing up in boot loader

    Today I needed to resize my Windows Vista Ultimate partition for work, so I used Disk Utility to crate an image from the partition. After that I used Boot Camp Assistant to remove the partition, and then create a larger partition. After this was done I went back into Disk Utility and restored the partition using the image I created earlier.
    In OS X I can mount the partition and access the files and it seems everything was restored correctly. When I restart my machine and hold down the Option key to bring up the boot loader, Bootcamp is no longer an option. The only partition I can boot from is HD.
    Please help! Thanks

    Did you actually Install a version of Windows into that Boot Camp Partition? It doesn't sound like you did.
    You'll need a copy of Windows 7 or 8, 64bit, and a valid license key code for whatever version you plan on installing.
    Ethan_Fidler wrote:
    I have sucessfully partitioned my macbook pro (thanks Ds Store!) and now I have another problem, When booting up I hold down option to choose my startup disc all that shows up is macintosh HD and recovery, BOOTCAMP is not showing up, even though it showes up in devices please help me!!
    - Ethan

  • Cannot mount Windows partition with boot loader on Mac OS 10.8

    I took out my hard drive of my Windows 7 PC, which has 3 partitions on it: C drive which contains the OS and the boot loader that the computer boots into, D drive which contains my data, and a third called "System Reserved" a few megabyte in size that I have no idea what so ever what it does besides that I cannot modify or delete it, which probably means that it is important.  Now I put the hard drive inside an USB 3.0 enclosure and I am trying to mount this hard drive onto my OS X Lion Macbook air.  Something strange is happening, in that the computer takes about 30 seconds or more to detect the drives presence, and then it just freezes after that.  On the initial try, the system actually successfully launched DiskUtility, and I can see the drive mounted in the list of detected drives and 3 partitions "SD1, SD2, SD3" under that drive, but after  repeating the procedure a few more times, nothing seems to be happening after the system freeze.
    Anyone have any idea what's going on?  I am trying to access the data partition for my stuff.
    I have Tuxera NTFS installed, and I should probably also mention that my Macbook Air is mid 2011 with only USB 2.0 ports.
         Thanks in advance.

    Ok, I figured out the freezing part; apparently, I had to connect to the USB port on the left side next to the power supply or the disk does not have enough power and causes the system to crash.  So, now Disk Utility can see the hard drive with no problem.
    But now, the partitions are detected as XFAT format and no volumes are mounted to the desktop.  Disk Utility displays the disk description as:
      Disk Description : INTEL SS DSA2M160G2GC Media  Total Capacity : 160.04 GB (160,041,885,696 Bytes)
      Connection Bus : USB  Write Status : Read/Write
      Connection Type : External  S.M.A.R.T. Status : Not Supported
      USB Serial Number : CVPO049000W0160AGN    Partition Map Scheme : Master Boot Record
    Why is the status "not supported"?  How should I go about mounting the data volume so I can access the files on my Mac?

  • A white patch has appeared on my Sony Bravia LCD TV.

    A white patch has appeared on my Sony Bravia LCD TV. The patch is slowly growing in size and obstructing the picture. Unable to see what is under the patch. Does this forum also involve customer care?  We bought the TV almost 3 years back. Not sure if the international warranty that I got still exists. Need to check. Appreciate help. Cheers!

    I am having the same issue. My LCD's model is KLV-32BX300. I bought that TV 4 years back. The TV was working fine before that issue. The amazing thing is that the patch was initially a small spot and it size got increased within 2 days even the TV was powered off. Please help...

  • White triangles appear in Favorites page

    Hi all,
    I am having some trouble with Safari's favorites page: when the bookmarks bar is open, white triangles appear on the page. Furthermore, when a webpage is open, one appears at the bottom of the bookmarks bar (beside the Edit button). They tend to move around arbitrarily, and it is difficult to get a screenshot as they have a habit of hiding. I did manage to grab one, however. Any ideas what this is or how to fix it?
    I'm running 10.10.1 on a mid-2010 MBP, 2.66GHz, Nvidia GeForce GT 330M 512MB.
    Thanks!

    Might be a cookies, cache, extensions, or plug-ins issue.
    From your Safari menu bar click Safari > Preferences then select the Privacy tab.
    Click:   Remove All Website Data
    Then delete the cache.
    Open a Finder window. From the Finder menu bar click Go > Go to Folder
    Type or copy paste the following
    ~/Library/Caches/com.apple.Safari/Cache.db
    Click Go then move the Cache.db file to the Trash.
    Quit and relaunch Safari to test.
    If that didn't help, from the Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that OFF, quit and relaunch Safari to test.
    If that helped, turn one extension on then quit and relaunch Safari to test until you find the incompatible extension then click uninstall.
    If it's not an extensions issue, try troubleshooting third party plug-ins.
    Back to Safari > Preferences. This time select the Security tab. Deselect:  Allow plug-ins. Quit and relaunch Safari to test.
    If that made a difference, instructions for troubleshooting plugins here.

Maybe you are looking for