rosalate naunton jannique
Osman Briseno
Then I launch vbox virtual machine. Arch Linux medium menu is shown and I choose first option. Ok, it boots correctly and I install Arch without problems by following step by step the arch linux installation guide.
Once installed I reebot into the new installed system in vhd.
Ok, no problem til here.
Imagine now, I need to boot from arch iso medium to make something through arch-chroot because for example something has happended and I cannot boot from the new installed system.
At this point there is no way to boot into arch iso medium anymore with EFI option enabled in configuration -> motherboard. The only way to boot into arch iso medium is to disable EFI option in virtual machine settings.
It seems like virtualbox give priority to the vhd instead of arch iso medium despite of boot order is set to optical in first place and then hard drive in second place.
The only way to boot into arch linux medium (in UEFI mode) once you have installed your new UEFI-based system and with the EFI setting enabled in virtualbox virtual machine is by doing the following through the boot loader, in my case GRUB (so don't forget to install a boot loader at the end of the installation process before rebooting).
2) Then you will be redirected to the virtualbox virtual machine firmware menu. Once in that menu, select "Boot Manager" option and you will be redirected to another window. On that window choose "UEFI VBOX CD-ROM VB0-01f003f6" (maybe ID VB0-01f003f6 could change in your case, note as well that "UEFI VBOX HARDDISK ..." is my vhd where arch is installed) option.and press enter as below screenshot shows:
It seems like when EFI setting (under configuration -> system -> motherboard) is enabled in virtualbox virtual machine, boot order is ignored (it is only taken into account if EFI setting is disabled, that is in BIOS mode).
I bought an Acer AM 5802 computer about 14 months ago with Windows 7 64-bit. Just before the year warranty expired, the DVD drive started to fail, so I replaced it. Just after the warranty expired, the graphics card, Nvidia GeForce GT220 1024MB, began to act up. Every time I used a full-screen application that had any 3D graphics, it would kill the computer after only a few minutes. The screen would turn black and the computer would stop, though it didn't power down. Restarting it would solve the problem, though I still couldn't use those applications. Then it would periodically begin doing the same thing just playing video on the web. I run dual monitors and every time the screen saver came on, it would switch to only a single monitor on being woken, requiring me to go change it back in the desktop settings.
I figured the card was starting to go, so I bought an XFX ATI Radeon HD 4650 graphics card with 1 GB DDR2 memory. It's a little older card, but it still met my requirements and it didn't break the bank.
When I went to install the new card, I removed the old card, and replaced the new one, just like the instruction manual said and I didn't touch anything else. When I booted up my PC, the Acer screen appeared as usual, but then Windows wouldn't load. Instead, there is a message that says: "CD-ROM Boot Priority...No Medium Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key".
At this point, I'm not quite sure what to do. From what I can tell from reading online, this usually means that the hard drive isn't connected properly. I hadn't touched the hard drive and it has been working fine, but I rechecked the connections anyways to no avail. I don't have a boot disk and I don't want to try reinstalling Windows. I also tried reinstalling my old graphics card, but it now results in the same message. Can anyone help? I'm just not sure what to try next. This hasn't been quite the plug-n-play experience I was hoping for.
Make sure there is no CD in the CD-ROM drive. Normally if the CD isn't bootable it will skip it and go onto the next boot device, but I've gotten this error after leaving a driver disc in the drive.
The next thing I would do is go into the BIOS (Del or F2 on startup, may vary) and change the boot priority so that the hard disk is first. While you're in the BIOS, check the SATA/IDE configuration to make sure your device is being picked up. If the system sees the drive it will tell you details such as the model number, size, interface type/speed and S.M.A.R.T status among other information.
This of course can only be done in case you had included this drive's image in the virtual box machine's "Storage" settings where you can attach the VDI image of your installation to either a virtual IDE, or a virtual SATA port:
Although I have accepted the answers above, I realize that from the point of view of a complete noob to linux and operating systems in general, the concept of images ,ISO files etc is still confusing. I remember it taking me a while even after reading them. Primarily because Ubuntu had been installed on my PC by a friend, and I had zero experience there.
When you install VirtualBox, it does not automatically come with the ability to run all the listed operatings systems (as I used to think ). An external file called the ISO or system image file is needed.This is the "bootable medium " referenced above .It generally has the .iso file extension. This file can be found on the website of the OS you want, and must be downloaded. This file is also used if you actually want to install the particular OS on your PC/laptop.
I think pretty much no 486 system can boot from CD-ROM. Perhaps some really REALLY late ones are the exception to that rule, but certainly not an ISA-only system, that would be a very early 486.
As far as I recall, booting from CD-ROM wasn't added to the BIOS until the late Pentium/Pentium II era.
My 'medium era' Pentium 133 (I think 1996) cannot boot from CD-ROM at least, and my 486 certainly can't.
And there's that, too. I remember that our 486 (VLB board) could not boot from CD-ROM at all and also couldn't recognize any CD-ROM drives in the BIOS. My father had added a Mitsumi CD-ROM (supposedly ATAPI compatible, but it wouldn't work without its special controller card), and that also couldn't boot from CD-ROM. IIRC, the CD-ROM drive also lacked a Master/Slave jumper.
My best bet for the problem of the OP is that his CD-ROM drive is too new for any of the controller boards, so they simply won't recognise it. Furthermore, the Mitsumi board won't work without a suitable Mitsumi ATAPI CD-ROM drive, by which I mean a drive made for working with the card (later IDE Mitsumi drives won't work either).
To be able to boot from CD-ROM he'd need a controller card with its own BIOS chip with support for booting from any CD-ROM drive.
The BIOS doesn't have to detect the CD-ROM drive in order for it to work though (in DOS that is).
All you need is:
1) The CD-ROM drive connected to a compatible controller
2) The controller configured to a free IO port (interrupts aren't required, oldskool polling IO is good enough)
3) A compatible driver for the controller is loaded, configured for the correct IO port (if required, usually they just check the default ports for the first and second IDE controller, and find the CD-ROM automatically).
4) MSCDEX.EXE loaded, connecting to the driver
What might be a good idea is to download an image of a Windows 9x bootdisk. Because computers couldn't boot from CD-ROM back in those days, the floppy contains a basic installation of DOS and all the popular CD-ROM drivers. It will load them all with trial-and-error, and will usually get your CD-ROM drive working, if you don't have a super-exotic interface. Most IDE and SCSI drives should work at least.
I know a lot of people like to be period authentic, but I prefer to use a IDE dvd burner in my 486 and other retro pc's, also a 40gig hdd formatted via Ontrack software.
I can boot from floppy, cdrom, or from hdd into win95.
I copy what files I want onto a DVD-RW and copy onto the hdd from win95. Without USB and a network card it's the best way.
I think it was my Athlon system that was the 1st I could boot from cdrom, there really wasn't a need before that. You needed a boot floppy
to access the cdrom then could install windows or whatever.
1) The CD-R not being recognized by the BIOS is expected, as noted by Scali.
2) Have you tested it in another computer, either via an IDE cable or USB to IDE adapter?
3) Do that. If it fails, use another drive. If it works, you may be looking at driver issues, resource contention, chipset compatibility, etc.
Have you tried replacing the IDE cable yet? If the system works with either the hard disk or the CD-ROM connected to the IDE interface on the motherboard, but not with both drives connected to it, then my first suspicion would be a faulty IDE cable. My second guess would be a faulty power connector or weak power supply causing the CD-ROM drive to not get any juice, but if the CD-ROM drive tray opens fine we can likely eliminate that possibility.
Do you have another IDE CD-ROM or DVD drive that is known to be good and that you could try? Frankly, being able to test all of the cards in another system to check whether they behave differently would be very helpful in eliminating possible causes...
Got it working, had to switch the IO board for another one so I could make the cable stretch.
As for the above: Yes I tried replacing it. The system simply would not boot /at all/ with CD connected to SB16 and no HDD connected.