Can't install XP from physical CD

[OldBill]

Very recently downloaded the new version of Virtual Box. It installed Ok but now cannot get the guest OS to install (trying to install Xp Pro). This process keeps wanting & looking for an .ISO file but I only have a normal install CD from Microsoft - which parts is apparently invisible to Virtual Box, as the setup.exe file never shows, just folders,
(and not any way for me to create an .ISO from that CD).

So how to resolve this? Help-suggestions-comments really appreciated!

In years past and with older versions of VB I used this same CD on my desktop system and 32-bit Windows-7.

My Computer (new) = An RCA Cambio 2n1 tablet; 2-Gb memory, with 17-Gb of 32-Gb available storage plus 32-Gb SD card installed w/ nothing on it, 32-bit Win-10. external USB CD-DVD reader.

During installation of VB, I could NOT get it to install to or create the VHD on my SD card, why?

Reader NOTE, herein the term VB refers to Virtual Box.

[mpack]

You are prompted for an ISO or a host CD drive... if the host has a CD drive. You can also manually mount the host drive (containing CD) before starting the VM.

Obviously if you have a CD but no CD drive then that presents a teeny problem. In this case, go to a PC with a CD drive. Use ImgBurn to create an ISO image of the CD, transport ISO to original PC.

Tip: probably not worth it for a one off, but another solution is to buy a USB connected CD drive. These are not suitable for booting a VM from a CD, but they should be suitable for converting a CD to an ISO. Also handy for ripping audio CDs to MP3.

Edit: Ah, I missed the sentence where you said you had one of the latter already.

[socratis]

The OP does have an external CD. The question is, can VirtualBox see that and use it as the "Host's CD"? I don't know...

@OldBill
See if you can do the following (in the image). If you can't, follow mpack's advice:

[mpack]

An external USB CD drive is usually not seen as a CD drive by VirtualBox. Presumably it's seen as USB mass storage, and thus uses a simulated filesystem (similar to a shared folder).

Edit: thinking about it, it wouldn't be like a shared folder since mass storage doesn't have a standard filesystem. So possibly the overlay does nothing at all except report it as a hard drive (not a CD). Next level would be to translate between 512 and 2048 byte sector sizes to match expectations of hdd.

[socratis]

OK, thanks for verifying.

PS. I still can't believe that in this day and age, Windows doesn't offer a built-in solution for creating an ISO.

[mpack]

For all I know there's some obscure tool tucked away somewhere which can do it, but I'm happy with the ImgBurn solution.

[BillG]

Recent versions of Windows have a built-in ISO burner. You right-click the ISO and select Burn disk image. Not sure when it started but it was in 8.1 and is in 10.

[socratis]

Not sure when it started but it was in 8.1 and is in 10.

Windows 7 beta 1 (source: https://technet.microsoft.com/en-us/lib ... 51080.aspx).
But the thing is that you can only Burn, not Create. I guess you can't win them all...

[OldBill]

My thanks to all that replied.
No success!
I used my Mom's Xp computer as mine does not have a CD writer.
Downloaded and installed "IMGBURN"
Used Imgburn to copy/create/? an ISO image from my Xp CD,
The result was a few files on the CD, TOTAL length only 1.93 Mb (NO directories visible)
The CD would open on my reader and do a few things from the menu, but would not install Xp-Pro

Any ideas what I am doing wrong?

[mpack]

You don't need a CD writer to read CDs to make an image.

And it is an image of the CD which you need to make, not just copy files from the root folder.

Finally, if the image really is only a few MB then it can't be an XP install CD, it might just be a service pack. The label should give you a big clue.

[OldBill]

You don't need a CD writer to read CDs to make an image. MY Error < Stupid me!

And it is an image of the CD which you need to make, not just copy files from the root folder.
I USED IMGBURN TO ATTEMPT making the .ISO Image - NO ATTEMPT BY ME TP COPY SPECIFIC FILES TO_FROM ANYWHERE!


Finally, if the image really is only a few MB then it can't be an XP install CD, it might just be a service pack. The label should give you a big clue. THE RESULTANT CD I MADE ONLY COPIED THE FEW FILES O-U-T-S-I-D-E those in folders, and certainly labeled by MS as a SETUP disk.!

[BillG]

Did you look at the contents of the CD while you had it mounted on your mother's machine? How big is it? Does it have a setup.exe file?

It should be about 600MB and should have five folders and a few other files (including setup.exe). No point in trying to convert it to an ISO if it isn't really a Windows install CD.

[OldBill]

I think I have clearly and concisely answered these questions already!

It IS a Microsoft issued Xp Pro CD. It has a small number of separate files - one of which is a setup program. It has a modest number of folders (i386, etc.). During my 10 year ownership I have used it a least 4 times to install/reinstall Xp on some or another computer. When booted a menu is displayed with some 6-8 choices = INCLUDING an install Xp option. The used space on the original source CD is near 600 Mb.

The only thing imgburn copied were the separate files - NO folders. The files were visible when viewing the CD as standard looking Windows files = and total size of COPIED files were 1.93 Mb. NO .ISO

I started this post looking for help installing Xp into VB-5, not to debate some program or procedure - that did not work as I expected - probably because I goofed somewhere, never having used any .ISO media.

THANKS ** HELP

[erdeslawe]

It sounds as if you've selected the option to copy files in ImgBurn instead of selecting to create an ISO image. I suggest you check what you did against the step-by-step guide here: http://forum.imgburn.com/index.php?/top ... g-imgburn/

[mpack]

Either :-

(A) it isn't an XP install CD, or ...
(B) You are not imaging the CD - you are copying files.

Take your pick. The only other option is physical damage to the CD, but that would be visually obvious, plus you'd get an error message when imaging.