A
arachnid
There must be something wrong with the iso file, it does not have an
autorun.inf which most boot CDs have.
autorun.inf is a Windows thing. I'd have to look to be sure, but I don't
think Linux install CD's use it.
I downloaded it twice from different sources, and compared them byte for
byte and they are identical, but my guess is that both are faulty.
freespire_1.0.2.iso is the name
According to distro-watch, the md5 should be:
bf7fb4eb41b234f6749514c1d29a93d0
If you get that then you have an uncorrupted image. If you don't have an
md5 utility for Windows then you'll find plenty via Google.
I think I have solved that problem. When looking at other burnt CDs with
explorer or my file manager the folder boot.images is invisible for
some reason.
So it is probably there, I just can't see it, even though both file
managers are set to show hidden and system files.
Conclusion, the Freespire_1.0.2.iso that is available right now on the
web is faulty, or incompatible with my CD-unit somehow.
Sounds to me like Linspire *may* have screwed up the Joliet options when
they created the Freespire ISO. Or maybe they simply didn't care since
there's no reason Windows needs to see the filesystem.
To explain: There are several different ways to point to to the data on a
CD. Windows uses Joliet (I think???) and Linux uses Rockridge. A CD
can be burned to have both Joliet (so Windows can see the files) and
Rockridge (so Linux can see them). There are many settings for Joliet,
some of which are unofficial and don't work on all systems. So it's easily
conceivable that the files could be there and yet Windows can't see them,
while Freespire can.
There is a slight delay when booting, the computer looks at the CD, but
decides to ignore it and boots into windows as usual.
The only things I can think of have already been ruled out. If bittorrent
will work through my firewall then I'll see about downloading the image
tomorrow and try to figure out what's going on. However, if you're doing
everything right and the MD5 is good, then most likely the boot code is
hitting some hardware incompatibility that it can't handle and passing
control back to the normal BIOS boot routine.