EUFI CD/DVD Boot Option

I have a Qosmio X870-BT3G23 running Win8. It will not boot from the CD/DVD drive. The message is as follows:
"System doesn't have any CD/DVD boot option. Please select other boot option in Boot Manager Menu."
The problem is that there aren't any other boot options. A call to Toshiba support revealed that in order to have
the CD/DVD option, I would have to pay for premium service call.

you need to order this CD/DVD from toshiba. Or i guess (but not familiar with this for 100%) you can create your own with windows recovery tool. Otherwise you can use standard win iso if you have a windows key to activate it later.

Similar Messages

DVD Boot option on K7t 266 ver 2

I don't see where I can and I don't see a bios uodate that will let me. And I can't get the system to do it. Is this the way it is or am I missing something
Thanks,
Ahumado

Quote from: Ahumado on 15-February-07, 04:03:53
I don't see where I can and I don't see a bios uodate that will let me. And I can't get the system to do it. Is this the way it is or am I missing something
What is your question? Do you want to know if you can set DVD rom as boot device? If this your question the answer is yes. Just set cdrom as first boot device and board will boot from any optical drive connected, no matter if this is dvd-rom, cd-rom, cd burner or dvd burner.

Windows 8 does not have a USB boot option

QuestionHow can I boot my Windows 8 laptop from a USB device? I created a recovery disk on a USB thumb drive.
So far I have:
Entered into the UEFI (BIOS) and set USB to boot first.
Disabled secure boot.
I tried to reboot using the general setup options for startup in the windows settings page. I choose boot from USB through the UEFI, but got an error message that system does not have a USB boot option.
To confirm I also created a bootable DVD with an ISO burner, but my laptop cannot detect a DVD boot option either.
I assumed that the firmware of the UEFI for this computer allowed a bootable USB but in practice I cannot seem to get this work.
AnswerTo assist with not being able to boot from a USB device on a Windows 8 laptop, perform the following:
Plug in USB bootable device.
Hold down F12 when restarting and access UEFI menu (option is below drive list). If system is set to fast boot, CLICK HERE for instructions on entering the UEFI.
Go to UEFI and make USB "1st boot".
Disable secure boot.
Go to the "Advance" Tab, select "System".
Change boot order from UEFI to CSM.
Save changes and exit (F10).
Computer will restart and boot from USB drive.
When finished go back into the UEFI and set defaults then save changes and exit (F10). Windows 8 will reboot normally next reboot.

Done that, only choices are "Set up Firefox to Sync" & "Pair a Device". No ''UNLINK THIS DEVICE". Your turn.

No boot option after Windows 7 install on Mac Pro

Hi,
I have problem and it is very frustrating.
My configuration
Mac Pro 1.1 2x2.66
RAM 5 GB
HDs
Bay1 500GB (have a Mac OSx 10.6)
Bay2 250GB (install Windows 7 Ultimate 64bit)
Bay3 250GB (in raid Mac OSX 10.6.6) primary system
Bay4 250GB (in raid Mac OSX 10.6.6)
I have install Windows 7 via Bootcamp from system 10.6.6 and format and install Windows 7 on HD in Bay2. After installation I try to choose which operating system I want to run (with option key) but nothing happen.
It was grey screen without apple logo and system boot to Windows 7 only.
I try everything to boot with different options (key shift,x,c,...) but nothing happen. I can only boot with windows 7 and if is the windows 7 DVD in drive first ask to boot with DVD, after that boot on Windows 7.
I try to put Mac OS system DVD but still don't want to run.
I also try to remove HD from Bay1(macosx) and Bay2 (windows7) and boot from Raid HD and I have error that there is no boot system.
In windows 7 I run Paragon HFS+ and I can see HD500 in Bay1 but cant see in Bay3 and 4 (RAID hd). In disk utility I can see all hard drives.
I try to reset PRAM but while booting what ever I press nothing happens and boot only windows 7.
I need solution for this problem, please help me with this issue, thx

Another thing that might be close...
I've installed Win7 64-bit on a second HDD. It is Ok to choose boot with 'option' key, but another option is missing: while in win7 apple's bootcamp control panel shows both MacHD and Win7 bootable partitions, so I can tell 'software way' to boot to win or to Snow Leo. It's OK. However when I open 'startup disk' in OS X there's only Mac HD so if I need to reboot to windows I can't just do it with several clicks. I actually have to shut down OS X, wait for boot screen, press option and then wait for the boot options to appear and them choose. It's 'a bit' annoying, let alone windows version of bootcamp seems to do the job smarter. And it really is a good thing to choose "reboot into desired OS" with a click and go to kitchen for tea or something and not seat in front of the machine waiting for boot screen...
Am I missing something? Is it done the other way then 'system preferences>startup disk'?

After installing lion, windows 7 boot option disappeared.

I had a macbook with snow leopard and windows 7 together. Yesterday I installed macosx lion. After installing it, windows 7 selection disappeared in boot menu. I tried to select boot options by pressing "alt key". I saw a new partition which is Recovery HD. There was no bac up files. So what happened to my windows 7 part? How can I restore system?
I tried to use disk utility in lion. I realized that the name of the windows 7 part was changed, now it is disk1s4 but before it was disk0s3 etc..
I removed my macbook HDD and attach with as external HDD to a desktop computer. But I could not find any solution.
In a forum, Someone suggest to create RAW diskimage by using a program named "active and undelete"
Firstly delete windows 7 partition on HDD and create new partition. And then set up it with windows 7 DVD and use RAW diskimage and restore your old settings.
is this logical?
Or is there any simple way to rescue my system? For example If I reinstall Snow Leopard, come my windows 7 partition back?

I could not remember this selection but if I choose one, I choose complete install..

HOW TO YOU ADD USB FLASH DRIVE TO BOOT OPTION

i HAVE TWO LAPTOPS SAME MODEL NUMBER ONE CRASHED, hp SUPPORT TALKED ME THROUGH F11 TO RECOVER TO FACTORY CONDITION THE LAPTOP STOP AT 100% WITHN1 MINUTE LEFT TO CMPLETE. HP TOLD ME TO ESCAPE AN DO F2 TO CHECK THE HARD DRIVE. THAT WORK IT SHOWED ALL THE CHECKS PASSED. IT TOOK 2 + HOURS SO WHEN i CALLED BACK DIFFERENT PERSON SAID $350 SEND IT THEY WILL FIX. iT'S NOT IN WARRANY SINCE FEB2014 i ONLY PAID $399 FOR IT, CANNOT AFFORD THAT. SO HP TECH SAID USE SECOND PC TO MAKE A FLASH DRIVE . (I MADE CD'S WHEN I FIRST GOT IT BUT THEY DID NOT WORK). SO GOT A FLASH DRIVE WTH 32GIGS (I THOUGHT SHE SAID I NEEDED AT LEAST 20 GIGS) COPIED THE RECOVERY PROGRAM, NOW THE USB WILL NOT OPEN. FROM AN EARLIER WRITTER HE WAS TOLD TO F10 BIOS, ESC LOOP FOR BOOT OPTIONS TO SEE IF USB FLASH DRIVE IS THERE. MY PROBLEM ITS NOT ON MY PC SO HOW DO I ADD IT SO THE USB WILL OPEN.
RIGHT NOW PC IN A LOOP WHEN POWERED ON HP AND TIME COMES UP, LITTLE WHILW A BLOCK WITH HP/DAT/TIME COMES UP AND A CMD ON BOTTOM OF SCREEN, IT GOES BY TOO FAST T CLICK ON IT AND GOES BACK TO HP LOGO. IF I COULD ADD USB FLASH AS AN OPTION IT MIGHT MAKE IT OPEN ANY HELP APPRECIATED.

The flash drive is not going to show up if it is not bootable. To make a bootable Recovery on flash you have to use Recovery Manager just like you do to create cd/dvd Recovery.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Satellite L675-S7052 - USB boot option available?

Hi guys,
my friend just bought new laptop from US (Satelitte L675-7052), and he would like to install Windows 7 from USB. His BIOS is AMI v1.4. USB legacy is enabled in BIOS but USB boot option still doesn't appear in boot menu.
Does anybody have solution for that BIOS (laptop model) , please? He sent me some screenshots as well:
[http://www.pixhost.org/show/1907/5070022_dsc_8298.jpg]
[http://www.pixhost.org/show/1907/5070029_dsc_8299.jpg]
[http://www.pixhost.org/show/1907/5070036_dsc_8300.jpg]
[http://www.pixhost.org/show/1907/5070049_dsc_8301.jpg]
[http://www.pixhost.org/show/1907/5070057_dsc_8302.jpg]
[http://www.pixhost.org/show/1907/5070063_dsc_8303.jpg]
Thx for any reply :)

Hey, thx for reply.
It's my friend's laptop and not mine :) And the reason why he wants to install Windows 7 from USB is that I adviced that to him. As I have older Satellite laptop and I prefer to install it in that way - it's faster and i guess more precise :) Plus, my Mat****a DVD mechanic has been screwed for one year now (and I am not going to pay 200 $ for a new internal DVD mechanic at all).

TS2951 Is there a way to make a dvd Boot Start Up Copy for Lion 7.4.1 ? on a MAC PRO 2011

Hello,
Is there a way to make a dvd Boot Start Up Copy for Lion 7.4.1 ? on a MAC PRO 2011 ? I only have the Newest
Lion Thumb Drive 7.0 and will not allow me to ever Reinstall my MAC. Which I like to do from time to time....
Is the Thumb Drive Suppose to reinstall the entire computer or just upgrade ? Apple Store does not know what
level each customer is at so the Thumb Drives must Totally Start from Scratch.
It worked Once in Nov a Month after I Bought the MAC PRO in 2011 by customer care telling me to Hold down the Option Key When I Turn on the MAC ? I hope That is Correct.
SO WHAT I AM REALLY WANTING TO KNOW ABOUT MACS IS CAN YOU MAKE A BOOT DVD and NOT with Time Machine or an External Hard Drive.
- THANK YOU, JEFF June 22,2012 3:10pm Pacific Time

See if this is of any value for you:
http://blog.gete.net/lion-diskmaker-us/
Ciao.

[SOLVED] Board no longer sees uefi as boot option

Hi,
I installed Arch on an ssd and was using rEFind to boot the system. It was working fine until I unhooked the ssd from the Mobo to install a hard drive with an old version of arch.( I was going to use the hd for extra space) However, when I hooked my ssd back up the bios did not detect the uefi. It shows the ssd but not the option to boot with uefi.
When I run lsblk -f from my old installation I can see that the ssd is not mounted to anything. I can mount the ssd with the old installation and see all my files. I just can't boot to the ssd. Any Ideas?
I have an Asus mobo and a Kingston ssd. Probably not relevant info but thought I would mention it just in-case.
Last edited by Mgrim (2013-03-08 05:42:47)

ls -l /dev/disk/by-partuuid/ output
lrwxrwxrwx 1 root root 10 Mar 4 15:12 0c20bfb2-b03b-467f-9faf-d8f7311027ec -> ../../sdb4
lrwxrwxrwx 1 root root 10 Mar 4 15:12 38362986-f8ad-416d-86eb-659f7e78f8c3 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Mar 4 15:12 628b4764-b385-4f6c-a92c-8c1ccc551e19 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Mar 4 15:12 82e01db0-b264-4555-910d-aa020bccb086 -> ../../sdb2
-not sure how to do this for sda drive
refind.conf
# 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 20
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner
# label - 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
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# all - all of the above
#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.
#banner hostname.bmp
# 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.
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Use text mode only. When enabled, this option forces rEFInd into text mode.
#textonly
# Set the screen's video resolution. Pass this option two values,
# corresponding to the X and Y resolutions. 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
# 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
# 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
# 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
# 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. If a specified
# directory doesn't exist, it's ignored (no error condition results).
# The default is to scan no additional directories.
#also_scan_dirs boot,EFI/linux/kernels
# 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.
#dont_scan_dirs 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,MokManager.efi,TextMode.efi,ebounce.efi,GraphicsConsole.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. Most notably, if you
# want to give a kernel a custom icon by placing an icon with the kernel's
# filename but a ".icns" extension in the same directory as the kernel, this
# option will cause the icon file to show up as a non-functional loader tag.
# 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
# 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
Last edited by Mgrim (2013-03-05 16:07:44)

A friend bought second hand macbook air mid 2011 with crossed circle on the display, we tried recovery from partition and same thing happened, after internet recovery it stays the same except now it asks for password for boot option, what happened?

A friend bought second hand macbook air mid 2011 with crossed circle on the display and give to me to try to recover the system, I tried recovery from partition and same thing occured, after internet recovery it stays the same-crossed circle after reboot, then we tried to boot from USB with mac os 10.8 on it, it installs something,like it has being finishing installation, rebootes, and now it asks for password for boot option.We have no idea what that password could be.What happened!!!

I forgot to write down my computer specs:
iMac 27 Mid 2011
2.7 GHz Intel Core i5
4 GB 1333 MHz DDR3
AMD Radeon HD 6770M 512 MB
OS X 10.9.2

How can I boot to USB device if no USB boot option in BIOS

I just purchased a Toshiba NB305-N410BL but am concerned as to how I would image the 250GB HDD if I can not boot from an external cdrom drive. I tried to backup to shared network folder but none show up on list. Only boot options in BIOS are HDD, FDD, and LAN. Thanks for all help in advance.

Hi, buddy-erp.
I don't know if my instructions apply to you because I only have the NB305 model. However, if you say you have followed all instructions, that is, 1) insured that no other USB devices are connected to your computer at bootup time and 2) have pressed F12 to enter the boot menu; 3) and then designated the USB flash drive as the source of the bootable restoration software you may need Toshiba technical support. I wonder if there is a BIOS update for your computer too. This may need to be downloaded and installed prior to beginning the restoration process. Nevertheless, as stated, I have a NB305 model and the instructions are clear. FYI (for your information), a virus infected my system and made certain changes to this process. Toshiba technical support informed me that the information displayed was wrong and the process outlined was unnecessary but did require technical support to restore it to the OEM default options.
Good luck.
Sincerely,
Bi-Ill
Good luck!
Sincerely,
Bill5960

HT4818 I have installed bootcamp that worked properly. Then I have partitioned the OS X 10.8.2 and installed another OS X 10.8.2 and I have got two MAC boot options and Bootcamp disappeared from the Option menu. How can I boot Windows again and keep both

I have installed bootcamp by the bootcamp assistant and worked properly.
Then I have partitioned the OS X 10.8.2 and installed another Mountain Lion System and I have got two MAC boot options and Bootcamp disappeared from the Option menu. However, Bootcamp still remained in the Startup Disk in the System Preferences. When I tried to boot Bootcamp using the Startup Disk it did not boot and received a message that there is no bootable device. I have not lost any data and can read Bootcamp partition from both OS X systems. Please advise how can I boot Windows / Bootcamp again? Thank you.

Recommendation 1: Use a VM for this. It's essentially a giant C.F. to do this with native booting, and is potentially fragile.
But if you're going to ignore that and do this anyway, realizing that it can break anytime in particular with OS upgrades, and that it's very difficult to impossible to resize the three volumes once you've installed the systems:
1. create three partitions, setting each to be the size for OS X copy 1, copy 2, and Windows respectively. The Windows partition needs to be set to MS-DOS format (actually FAT32) which later in the Windows installer you'll reformat as NTFS. Do not use Boot Camp Assistant to resize/partition the disk, it simply won't work for this use case.
2. install OS X copy 1
3. install OS X copy 3
4. Use gdisk (available at sourceforge) which is a command line only application, to create a new hybrid MBR adding only the last partition (Windows) to the hybrid MBR and setting it to be bootable. As a concequence you will not be able to see/share either OS X volume from within Windows. The Windows NTFS volume will be visible from within OS X.
5. Install Windows to the only partition its installer should see (confirm size), you'll need to format it NTFS first, and I suggest using the fast format option if available.

AVCHD to DVD: Export Options?

Hi
I'm currently editing a school show in FCE, shot on a multi-cam, AVCHD camcorder set-up. I'm editing the files in native format because a few copies on Blu-Ray will be needed. My problem is this; what export settings do I need to apply to the finished edit to optimise it for DVD burning, as 95% of required copies are on this format? I've tried the standard Export/Quicktime Movie option, and whereas I can burn lovely, pristine Blu-Ray copies from this file, (using Toast 10 Titanium), when I try to burn the file as a DVD, (using Toast's DVD burn option), the disc when viewed is of a pretty low quality and horribly interlaced on anything that moves even slightly. I'v tried customising the settings in Toast, specifically selecting "progressive" in the "Field Dominance" option, but the burn still looks crap!
I'm wondering whether my problem starts within Final Cut Express somewhere. If so, what is the optimum export setting with a view to creating decent-looking DVDs?
Thanks

The mismatch is probably the root cause of the problem. You are in a PAL country; if you shot 1080i50 then you should be using a matching Easy Setup in FCE, not 1080i60. I don't know how this would affect bluray, but it would cause issues for standard def.
Try this -
Make a backup copy of your FCE project file. +(Very important. Don't skip this. Always make a backup before experimenting.)+
Then, control-click your sequence in the FCE Browser. In the window that opens, click Settings. In the next window click Load Sequence Preset. Select AVCHD-Apple Intermediate Codec 1920x1080i50. This will change your sequence to 1080i50.
Then export to QT Movie; import into iDVD or Toast and burn a DVD. You may want to try this with a short video segment first just to see what the results may be.

Boot options duplicated; Boot Camp Assistant newly non-functional

Short version:
1. Up to tonight, my hard drive was encrypted using PGP Whole Disk Encryption -- secure boot and all. Had Boot Camp working fine with it.
2. Attempted to install OS X 10.6.5 despite PGP warnings to decrypt first. Ended up with an unbootable OS X partition. Decrypted drive in Windows, got back into OS X.
3. Disk Utility returned a few errors on OS X partition. Quickly fixed those by booting from Snow Leopard CD and running it.
4. What I'm now noticing is that when I hold down the option key, I'm given duplicate options. Instead of "OS X Partition Name Here" and "Windows 7 Name Here", I've got a duplicate for the former. So my options are "OS X", "OS X", or "Windows".
5. And, when I try to run Boot Camp Assistant out of curiosity, I'm told that I either need one big non-partitioned drive, OR existing partitions created by Boot Camp. I already did that.
Any thoughts on fixing #4 or #5? Resetting PRAM doesn't help. Windows does not show as an option in "Startup Disk" in system preferences. But the Windows partition boots just fine when holding option on restart.

And since I can't edit my original post any longer, here's what fixed the redundant boot option thing:
http://hints.macworld.com/article.php?story=20091111185717745
Worked like a charm. Fixed the duplicate "OS X" option on boot, and both OSes boot normally. Can now click past the first few options in Boot Camp Assistant, so I'm assuming that's working normally now also.
Still no Windows option in Startup Disk, but apparently that's related to my use of NTFS-3g? Thought that was fixed.
sudo fdisk /dev/rdisk0 is now:
Disk: /dev/rdisk0 geometry: 30401/255/63 [488397168 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 423624704] HFS+
*3: 07 1023 254 63 - 1023 254 63 [ 424298496 - 64098304] HPFS/QNX/AUX
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Only thing I'm worried about now is whether I might have damaged any files though any of this crap. Don't know if I can check for that, or if I should worry about it.

Boot options on satellite l655-1dv

hallo , I recently had to find advanced boot options menu to set EFI etc ... I was trying to find something in BIOS (setup) with no luck . A few minutes ago I pushed by mistake something on keyboard on TOSHIBA screen and a screen appeared with information that I was trying to find !! (boot manager etc) . Unfortunately it was a mistake and I am trying to find the key I pressed but I cant go to this menu again . At startup TOSHIBA screen , it says that the only available "commands" is boot menu (F12) and setup (F2) . How can I go to this menu again ?
Thanks !

your support site is here
hit the F12 key over and over while powering up
L305-S5955, T9300 Intel Core 2 Duo, 4GB RAM, 60GB SSD, Win 7 Ultimate 64-bit

EUFI CD/DVD Boot Option

Similar Messages

Maybe you are looking for