Update Installer USB

I have an install USB for OS X Mavericks, but it seems to be on OS X 10.9.0. Is there a way I can update it to 10.9.1?
Also I recently used it to reinstall OS X to create a recovery partition, but it hasn't. How can I create a recovery partition?

cclloyd wrote:
I have an install USB for OS X Mavericks, but it seems to be on OS X 10.9.0. Is there a way I can update it to 10.9.1?
I would say that you need to download the latest Mavericks installer from App Store, which will be 10.9.1, and then make your USB boot again.

Similar Messages

After the OS X Lion installation, my USB modem doesn't work. I already updated the USB drivers, but nothing happened. Any suggestion?

After the OS X Lion installation, my USB modem doesn't work. I already updated the USB drivers, but nothing happened. Any suggestion?

You might want to do a search here on the forums re. usb modems - I've seen several threads and the opinion appears to be that faxing is no longer supported (especially since the "Fax" is now missing from the Print Preference Pane in System Preferences). I am faxing with an all-in-one printer which is connected to a landline, but I have to use the printer's control panel - can't use it from the iMac.

Making a Windows 7 Installation USB Stick

This is a discussion of making a bootable Windows 7 Installation USB-stick Media. It might apply to making other USB connected "Disks" like Smartcards bootable too.
I recently had to do this (a Laptop with no build-in DVD drive and no USB DVD drive around). And it turned out to be surprisingly simple, using nothing but build in Windows tools from the Disk. I only found
this german langauge guide and nothing in english (but I might just have searched after the wrong terms, google has been wierd regarding langauge lately), so I thought I write it up (along with some problems I ran into).
Making a USB-Stick into a bootable Windows 7 (and propably Vista) Media is a 3 step process:
1. Create a Active, Primary, FAT32 Partition of 4+ GB on the stick
2. use bootsect.exe from Windows Disk to create the MBR and Partition Boot Record for that Partition
3. Copy all files from the Disk to said Partition
4. Test if it boots
Detail analysis:
Step 1 is so simple I doubt it needs explanations. Create enough free space on the USB disk (at worst delete all previous Partitions). Make a Priamry Partition of 4+ GiB. Mark it as Active. Format it in FAT32. The Guide used Diskpart,
but this step can be done with any Partition Tool under any Windows, Linux, UNIX or DOS.
While the choice of FAT32 seems a bit outdated, theye propably did not gave the relevant bootlaoder the ability to read NTFS. Or maybe they just though FAT32 is enough for a media that is mostly read. I have not tried what happens if I format it in NTFS, but
it might be possible.
Step 2 was the only tricky part. You need the programm "boot\bootsect.exe" from the Installation Media. It also must be run on a non-UEFI booted OS (otherwise it cancels out).
I had a Windows 8 on a new Laptop so I had a UEFI booted system. Luckily I also had a VMWare Windows 7 lying around. I just assigned the Windows 7 ISO image to the Windows 7 VM, then connected the USB drive to the host.
Once you have the USB stick in a a proper Windows mount the Parttion you created under 1 under any driveletter (should happen automatically under Windows), and open a console as Administrator (asumes DVD is drivletter is D: and the USB stick's partition
ins Driveletter E:):
//Go into the boot directory on the Install DVD
D:
cd boot
//You should see a command promt like "D:\BOOT>"
//Run bootsect.exe
bootsect.exe /nt60 d:
Step 3 is to either copy the contents of the DVD media (copy and paste) or the Image (Mount into Virtual DVD Drive and copy/paste, unpack ISO images contents) into the partition.
How does this compare to other Distribution ways?
To DVD:
There is no need for a DVD drive. Even if a bootable USB-DVD drive is avalible, the Stick or Card will only need only USB port (most USB drives need 2 Ports due the 1 Ampere energy need of the drives).
Flash Media has no seek times and much better throughput (the old weakpoint of any Disk and DVD/CD in particular)
A FAT32 partition is inherently writeable. So modifications to the "Installation media" like Implementing Service Packs and other Windwos Updates, Modifying ei.cfg/preactivation/setup answer files, implementing special Disk/RAID drivers into the Windows
PE or adding stuff that should be installed with Windows is easy (and do not requrie reburning a 4 GiB Image file).
Since it only needs a 4 GiB partition, on a big USB stick there would still be place for other Data Partitions
Since it relies on old techniques (Generic Bootloader + Active Primary Partition + partition boot loader), multiple Installation media on a big enough stick might be feasible (with a more advanced bootloader like GRUB). Have to test that part.
However, the cost/media is a lot higher then a DVD. So if you need multiple Medias it will propably be cheaper to use the old DVD approach.
Due to the needs of bootsec.exe, first creating the media can be more difficulty then just burning an image. But once it is bootable this programm is no longer needed.
To PXE/network Distrubution:
If you have the nessesary setup already (DHCP/PXE Server, powerfull network), the USB stick is likely inferior. The USB stick should beat a 100 MBIT Network easily, but will propably be beaten by a 1 GBIT Network. Network isntallation uses existing infrastructure
(that you need for other reasons anyway) so the cost per media is even lower then the DVD.
The PXE way also has even better modifyability - sending out different answer files or even automatically booting different images based on the Compuers MAC adress are tried techniques.
If you lack the nessesary setup, the USB stick is a lot easier to implement and a lot easier to transport.
Advanced things:
Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
Need to check if using a advanced boot manager techniques (like Grub or modifciations to the BCD of the Windows PE) allows me to put multiple install media on one Stick (with one primary partition per "media"). Especially combining the x32/x86 and
x64 Windows Installation Media would be worthwhile. As would be inlcuding a Window 8 or Vista installation media.
Current Step 3 and 2 can propably be switched. I see no reason bootsect could not run from the USB stick as it runs from the DVD (it only accesses the MBR and
VBR of the Disk, areas not in use by Windows)
Steps 1 through 3 might be possible from the Windows PE environment. If so, only a computer with legacy BIOS boot would be nessesary (no actuall installation).
Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary.
Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

Advanced things:
Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary.
I converted the stick to NTFS using the convert.exe and it continued booting. So chances are high they only choose FAT32 in the example because no feature of NTFS was per nessesary in a "almost only reading" scenario like installation media.
The second part depends on the BIOS. I have a more advanced one where I can choose legacy boot options (like USB stick) in the boot option menu even when the default setting is UEFI, as long as I don't need Secure boot (wich I do not).
Another question arose: Windows 7 has the Kernel/BCD level ability to boot from .VHD Files. The only thing preventing version below corporate from using this feature is a license check that is run just before the login (so way after the booting has been
completed).
Starting with 3.0 Windows PE is based on the kernel of Windows 7. So the instlaltion system might have the ability to boot from .VHD too and might have no such check in place. If so, I could put both versions of the Windows 7 installer into .VHD, reducing the
need to have physical primary partitions for those.
Windows bootprocess vs. Linux boot process under BIOS:
The BIOS goes over all the boot media. If it finds one with a MBR, that one is executed and the BIOS part of the boot process is officially over.
-> Under Windows the MBR contains the "generic boot loader". A simple piece of code as old as BIOS (25 Years) that looks for the primary partition with "Active" Flag on "it's" disk. If it finds one, the Partition Boot Record of that parition is executed.
The MBR has done it's part
    -> NTLDR (NT too 2000), this one reads the boot.ini file and gives/executeds apropirate options
    -> BOOTMGR (Vista, 7), this one reads the BCD files
      -> Since Windows 7 BOOTMGR can also chainload the Partition Boot Record that is inside a .VHD File
    -> Wicher was used in Windows 3.X/95/98/ME
Higher versions can chainload lower versions, but must be designed for this and (re)installed in the proper "order".
The sometimes odd behavior that Windows 7 tries to keep 100 MiB in a seperate primary partition is there to have proper places for later additions to the BOOTMGR settings. Specifically it allows multiple BOOTMGR OS to use/edit the same BOOTMGR instace without
running into problems with "whose partition is active?" (since it is always the System Reserved one). It's not disimilar to having an extra /boot partition in Linux or how a GRUB's stage 2 works.
-> Under a typical Grub Legacy the MBR contains the Stage 1. It directly reads the Stage 2 from the proper partition/file system with a hardcoded path, but due to size limit of the MBR cannot do more. In some cases it starts a stage 1.5 wich has more
space to do work (63 sectors between MBR and first partition), but I never used this Setup
    -> Stage 2 loads the Grub Configuration from the disk. From here it depends on what OS you want to boot.
        -> For Linux or Unix the kernel is started directly.
        -> Any Windows OS up to 7 can be booted using the chainloader command. For the OS this is identical to having the partition choosen by the Generic Bootloader.
While it can be chainloaded by the Generic Bootloader from the active primary partition, GRUB and thus Linux has no
requirement for any Primary Partitions. Stage 1 is designed to directly access the specific File System containng the Stage 2. In fact it does not even need to reside on the same disk (as the Generic Bootloader has to).
If one does not need the Active Flag to control the Generic Bootloader (because a proper Stage 1 is installed in MBR) it is adviseable to mark wichever Windows Partition is chainloaded as active (up to Vista at least I had very odd behavior if the Windows boot
partition was not marked active, down to randomly shredded Partition boot managers).
After running a Windows Setup usually the Stage 1 has to be restored, as Windwos Setup will always write it's Generic Bootloader in the MBR. In order to get "rid" of a Grub all one has to do is overwrite the MBR with the Generic Bootloader and set the active
flag properly.
Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

[Solved] Boot process hangs for installed Arch and installation usb

Hi. I've been using Arch Linux for around 6 months now and I'm in love with it. It is now my primary OS. However, I might have done something or performed some update, and I can no longer boot into Arch. The boot process hangs right before it should show the login screen (I'm using Gnome 3.6 with GDM). I see the following messages on the screen:
Loading Linux core repo kernel ...
Loading initial ramdisk ...
/dev/sda3: recovering journal
/dev/sda3: clean, 330610/1749664 files, 5585671/6996827 blocks
And then it hangs right there. I have to hard-reboot after this.
I then tried to boot using the Arch Linux Installation USB (archlinux-2012.12.01-dual.img), which also hangs at a particular point, before it should show me the prompt. I took a picture of the screen where it hangs: Screen Capture. This is an issue with just my laptop, because the USB boots just fine on another laptop I tried.
I also have Windows 7 and Ubuntu 12.10 installed on my system, and I'm able to boot into both of them.
I have 2 hard drives: /dev/sda is a 120GB SSD, and /dev/sdb is a 500GB hard disk. My partitions are as follows:
sda1 - Windows 7 100MB System Reserved Partition (boot flag enabled)
sda2 - Windows 7 OS
sda3 - ArchLinux (boot flag enabled)
sdb1 - Ubuntu 12.10 (boot flag enabled)
sdb2 - Just data
I ran bootinfoscript and below is the output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
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: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: /dev/sda3 already mounted or sda3 busy
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 12.10
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
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:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
/dev/sda2 206,848 178,466,084 178,259,237 7 NTFS / exFAT / HPFS
/dev/sda3 * 178,466,085 234,440,703 55,974,619 83 Linux
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 63 20,948,759 20,948,697 83 Linux
/dev/sdb2 20,964,824 976,771,071 955,806,248 7 NTFS / exFAT / HPFS
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/mmcblk0p1 6665-3162 vfat
/dev/sda1 CA6A20CC6A20B75B ntfs System Reserved
/dev/sda2 1EE242D5E242B137 ntfs
/dev/sda3 65db0c59-9f04-46f1-975d-8a4c28132137 ext4
/dev/sdb1 bb9818db-ce7c-43a4-8ad5-8d3702001aed ext4
/dev/sdb2 3C2E3A4E2E3A0206 ntfs
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/mmcblk0p1 /media/dhaval/6665-3162 vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
/dev/sdb1 / ext4 (rw,errors=remount-ro)
=========================== sdb1/boot/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 ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
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 recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; 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='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
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_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 13,37,73; then
clear
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
initrd /boot/initrd.img-3.5.0-21-generic
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
menuentry 'Ubuntu, with Linux 3.5.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.5.0-21-generic ...'
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-21-generic
menuentry 'Ubuntu, with Linux 3.5.0-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.5.0-21-generic ...'
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-21-generic
menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-generic
menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-generic
### 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+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux16 /boot/memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-CA6A20CC6A20B75B' {
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 CA6A20CC6A20B75B
else
search --no-floppy --fs-uuid --set=root CA6A20CC6A20B75B
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### 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 ###
=============================== sdb1/etc/fstab: ================================
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb1 during installation
UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed / ext4 errors=remount-ro 0 1
=================== sdb1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
4.564525127 = 4.901121536 boot/grub/grub.cfg 1
5.130507946 = 5.508840960 boot/initrd.img-3.2.0-29-generic 2
5.851592541 = 6.283099648 boot/initrd.img-3.5.0-21-generic 2
6.317649364 = 6.783524352 boot/vmlinuz-3.2.0-29-generic 1
4.965751171 = 5.331934720 boot/vmlinuz-3.5.0-21-generic 2
5.851592541 = 6.283099648 initrd.img 2
5.851592541 = 6.283099648 initrd.img.old 2
4.965751171 = 5.331934720 vmlinuz 2
4.965751171 = 5.331934720 vmlinuz.old 2
I tried adding nomodeset and acpi=off to the boot parameters, but the boot process still hangs. Please let me know if I should provide any other information.
Last edited by dhavalparmar (2012-12-30 11:45:25)

Ok.. So my Arch Linux randomly decided to work. I'm sure I didn't do anything between my last "not working" state and my current "working" state. Below are a few things I tried:
I thought of trying an earlier build of ArchLinux, and downloaded archlinux-2012.11.01-dual.iso and made a bootable USB out of it. It still hung.
I was getting error messages during Arch boot that the last access time for the disks was at a future date. I found out that Ubuntu was using localtime instead of UTC and screwing up my hardware clock. I fixed it, and thought maybe the time issues were causing the boot problem. But fixing time didn't solve my problem.
I chrooted into Arch from my Ubuntu install, ran 'sudo pacman -Syyu' and updated my Arch install.
I thought maybe GDM isn't starting up. I re-enabled the service using 'systemctl enable gdm.service'.
I removed OpenNTPd and installed NTPd. Enabled the daemon using 'systemctl enable ntpd'
None of the above solved the problem, and rebooting to Arch still hung the system. So I stopped fiddling with it yesterday. Today, as usual, I just tried logging into Arch.. And it just worked out of the blue. The solution to me is as mysterious as the problem.
I told this to my friend who introduced me to Arch, and this is what he said:
Damn it computers, you were supposed to be deterministic!

Verizon Software Update Installer??

have my S4 connected to my PC via USB... in the autoplay no Verizon Software Update Installer shows up.. how do I d/l the installer software.. trying to set this up for when the new Update comes thru for my S4.. should be soon from what i am reading... tried d/l Kies to the PC from Samsung.. all it does is freeze my FF and Chrome.. so this Verizon Software Update Installer should work hopefully once I get it d/l..
any help appreciated...

I finally got it to Pop-up after numerous tries... it then took 1 hr 20 minutes to complete from start to finish... whew... all I cared about was putting just about all my apps on the 32gb micro-sd card rather than have them take up all that space on the phone
thanx

How do I install the FM10 licensing fix when Adobe Update Installer won't run?

Adobe Update Installer won't run so can't install FM10 licensing fix
This question is Not Answered.(Mark as assumed answered)
Aug 9, 2013 12:09 PM
Tags (edit): none (add)
Because FM10 began crashing with "fatal" errors whenever I tried to generate a TOC for a small (65 page) book, I researched workarounds and none of them worked. Now that I have delivered a crippled deliverable via Acrobat manipulations, I would like to fix FM. I uninstalled it and reinstalled it, got some updates, and then received the "licensing fix" error that popped up in January. I'm wondering why this fix was included not in the updates. That said, the licensing fix package, first, would not unzip so I downloaded it again. I unzipped it but I got a message that Adobe Updater Installer could not run and after several clicks I found that file. I reinstalled Adoble Update Installer but it still does not run.
I am running Windows XP and have TCS 3.5.I uninstalled FM and RH but not Acrobat, Captivate, or Photoshop.
So, now what? Listen to my supervisor who says never use FM again?
P.S. Why do I have to enter a title for my question and then do it again when this page opens??

Give Adobe Support a call or contact the TCS team at [email protected] - something in your environment is causing the installer to fail (I'd guess).

The update installation on my iPod touch failed and erased everything.

I plugged in my iPod touch (1st generation)into my computer and opened iTunes. A message popped up saying that there was a new update for my iPod, so i clicked on the download and install button. I downloaded the update and while it was installing, another message popped up saying the installation failed. so I was like ok I'll just click on the download again and reinstall it. But now my iPod wasn't showing on iTunes. I disconnected it and reconnected it and my iPod still didn't show. Then I noticed that the download wasn't there either. I turned on my iPod and all it showed was a picture with a connection cord pointing up to the iTunes logo. I think that the failed update installation must have completely erased my iPod touch's software. I have tried looking for the update download all over my computer but found nothing. what do I do now? Is there a way for me to download the software again or something? thank you

foxbat123 wrote:
Thanks Jason, I will try the troubleshooting steps. Will they still work even if my iPod touch isn't even being recognized as an iPod by iTunes or my computer?
If the iPod is not recognized and cannot be restored from the other user account, try the tips in this article: http://support.apple.com/kb/HT1852
You can quickly isolate the issue by trying to restore from another computer.
If the issue is not present on another computer try the tips in the article above.
If the iPod touch has the same issue on another computer, it may need repair.
To get the iPhone repaired in Kenya, visit an Orange store http://www.orange.co.ke/
-Jason

I am getting the following error messages Extension Manager 6.0.8 Update Installation failed. Error Code: U44M1P7

When I tried to install latest updates to Lightroom I am getting the following error messaage:
Extension Manager 6.0.8 Update
Installation failed. Error Code: U44M1P7
Ca you explain what I need to do to resolve this?

Jjmarmour please see Installation failed. Error U44M1P7 | Updates - http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html for information on how to resolve the U44M1P7 error.

Failed Updates every time!! Error message: Adobe Premiere Elements 12.1 Update Installation failed. Error Code: U44M1P7 Adobe Photoshop Elements 12.1 Update Installation failed. Error Code: U44M1P7

Adobe Premiere Elements 12.1 Update
Installation failed. Error Code: U44M1P7
Adobe Photoshop Elements 12.1 Update
Installation failed. Error Code: U44M1P7
Failed updates everyone on an iMac 27" running Mavericks- what can i do to get the latest updates which include support for my Sony A7 digital camera?
[email protected]

Update 12.1 installation errors | Photoshop Elements, Premiere Elements

11.0.4 Updater installation failed - error U44M1P7

For the benefit of others, I wanted to post the steps that fixed this issue for gbrozk1:
Open Extension Manager CS5.
Select Dreamweaver on the left, and then remove the HTML5Pack (11.0.3 Updater) extension.
Repair the installation of Dreamweaver using your original installation media.
To do this, insert your original installation DVD, or double-click the downloaded DMG file, and then double-click Set-Up.app to begin the installation.
When given choices of which products to Install/Re-install, uncheck everything except Dreamweaver. (That is, we need to be sure Dreamweaver is selected to be re-installed. Re-installing repairs the installation.)
Follow the remaining on-screen instructions to complete the re-install/repair of Dreamweaver.
Restart your computer.
Install the 11.0.4 update.
Hope that helps someone!

I have had the same problems as you @davert2
Dreamweaver CS5 11.0.4 Updater
Installation failed. Error Code: U44M1P7
I have done the following to try and rectitfy the error:
1. I tried Carey Burgesses help here - http://forums.adobe.com/thread/848587?start=0&tstart=0
2. Installing the update manually from here - http://www.adobe.com/support/dreamweaver/downloads_updaters.html
3. As suggested - removing the /AAMUpdater folder here - http://forums.adobe.com/thread/847350?start=0&tstart=0
4. Tried the "fix" link - http://kb2.adobe.com/cps/902/cpsid_90241.html - dead link
I am not going to reinstall CS5 because I can't get a fix, I'm not all together sold that THAT would fix the error either...
Anyone have an actual solution for this?
That was the post from me in November...
As of today, I've had the Adobe Application Updater run 3 times this morning, all with the same result.
I am on a Mac, 10.7.2 and am running CS5 - Dreamweaver runs fine there are no issues there, I have now 3 Adobe Application Manager updates in my tool bar... As soon as it runs again, I'll have 4...
Anyone have any answers that DON'T involve reinstalling Dreamweaver?

How to boot from Windows 7 installer USB-thumbdrive?

I have created a Windows 7 installer USB-thumbdrive from .ISO image using Boot Camp Assistant.
What I can't figure out how to make my Mac Mini boot from USB to start the Windows 7 installer. The USB-thumbdrive does not show up in the boot menu when pressing ALT during startup (I'm using generic PC keyboard) nor is it available for selection in System Settings --> System --> Startup Disk.
My computer is early 2009 Mac Mini, Intel Core 2 Duo, 4Gb RAM, OS X Mountain Lion 10.8.4.

Anyone?
Additional question: is a 2009 Mac Mini able to boot from USB to begin with?
The situation has become particular annoying, because my Mac Mini's optical drive appears to be damaged and therefor I'm not able to boot from any kind of Windows install DVD.

HT4407 When installing Windows 7 using Bootcamp, I get message: "Need 64-bit Windows Installation USB drive or DVD." I thought my install disk was for 32 or 64 bit. What does this mean?

When Installing Windows 7 using Bootcamp, I get message: "Need 64 bit Windows installation USB drive or DVD." What does this mean?

It means you need the 64 bit Version of Windows on a USB stick or DVD.

Bootcamp does not recognize Windows 7 Installation USB

I have a 2010 iMac running the current 10.10 Yosemite build. Bootcamp version is 5.1.2.
I want to install Windows 7 via Bootcamp on a partition on one of my internal hard drives.
I created an installation USB drive using bootcamp resulting in a MS-DOS FAT formatted USB flash drive containing ~4.75GB of data. The OS installation and the current Bootcamp tools. The drive is named WININSTALL .
When I start up Bootcamp to do an installation I get an error saying "The installer disc could not be found."
How do I tell Bootcamp to install off of the USB instead of looking for an installer disc?

You might wan't to ask in the Boot Camp forum where the Boot Camp gurus hang out.
https://discussions.apple.com/community/windows_software/boot_camp
It sounds like you have not yet completed the Windows installation process by installing the Windows drivers.

How can I delete the update installation files? Or which files are useless and safe to delete?

ThinkVantage System Update application will find the appropriate updates, download them and install them. This is convenient. But when it finishes the updates, it will not clean the installation files it has downloaded, which I think are not useful any more since the update installation is completed, right?
I think the update appliction stores the downloaded files in the folder: C:\Program Files\Lenovo\System Update\ , this folder of mine is over 1.32GB big now. But I just don't know which files and subfolders in it are safe to delete.
Or rather, the preload system occupies a large space on the disk. Which files are no longer used and safe to delete?
Would any experts help with this? Thank you very much!
Norm

I've been experimenting. Now I figure it out. Automatic System Update downloads and stores files in C:\Program Files\Lenovo\System Update\ Sessions\, and in Sessions' subfolders, all files are not used once update is completed except those ending with .xml. Thus those unnacessary files are safe to delete.
This is what I find out so far.
Continuing to experiment.
Message Edited by normyy on 05-31-2009 11:12 PM

Adobe Media Encoder CC 7.2.2 Update Installation failed. Error Code: U44M1P7

So, I get this strange error when I try to update AME CC 7.2.2. What to do?
Adobe Media Encoder CC 7.2.2 Update
Installation failed. Error Code: U44M1P7

[ Mac 10.9.3 / Indesign CC update fail / Premiere update fail / Adobe Media Encoder 7.2.2 update fail ]
AME:lle ei ole omaa unistalleria, vaan sen asentavat muut CC:n ohjelmat käyttöönsä.
Mulla ei onnistunut ID CC:n ja Premierin päivitys. Niihin olisi ollut tulossa vain tuo AME:n päivitysosa. Ainakin mulla ongelmia näytti aiheuttavan MCMHMPEGVideoCodec.framework, joka esti AME:n päivittämisen. Poistin sen käsin AME:n sisältä.
Poistin Premieren (uninstall) ja asensin sen uudestaan. Buuttasin koneen. Sen jälkeen molempien päivitys onnistui.
There's no separate uninstaller for AME. My ID CC and Premiere couldn't be updated (for the AME7.2.2 update). MCMHMPEGVideoCodec.framework seemed to be the factor.
I uninstalled Premiere (only), after having manually removed MCMHMPEGVideoCodec.framework from inside AME. After boot I installed it again and voilà, both (ID & Premiere) updates went trough fine. The MCMHMPEGVideoCodec.framework was on place inside AME too.

Update Installer USB

Similar Messages

Maybe you are looking for