Hi Eric,
On 9/28/06, Eric J. Ray <Eric.Ray at sun.com> wrote: > > > > Sarah Jelinek wrote: > > Well... iso is a standard so these utilities should just burn the image. > > But, I have never used them. I am wondering if there is a special set of > > options or something you have to specify to disable some Windows > weirdness. > > Nope--an ISO is an ISO. I've successfully burned Solaris Express CDs > from Windows, Linux, and Solaris. That said, the most common > gotcha with most of those utilities is to burn a single data file > (the .iso file) to a data CD, as opposed to replicating the ISO > file as the CD, if that makes sense. It'd be interesting to see > what it looks like on the Windows system. > > I've known people who write the ISO file to the CD as a file in a new filesystem, instead of streaming the contents of the ISO directly to the disk. That's not what I've done. When I put the disk back in a windows machine, I don't see the .iso file, I see what I expect to see the files that should be on CD1: Solaris_11 .cdtoc .install_config .slicemap _volume.inf Copyright JDS-THIRDPARTYLICENCEREADME Well there's a difference. It's supposed to be '.volume.inf' but I suspect that windows just doesn't like the leading . when there is another one later and is changing how it is displaying the name. I mean if the file name were recorded differently on the CD wouldn't the MD5SUM change? What is in the .volume.inf file? and when is it used? is that the 'disk label' or 'disk label package' the error's refer to? If not where on the disk is the label? -Kyle -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20060928/c4ce384b/attachment.html>
