NTLite ISO creation issue with volume id label

xekon

New Member
I am using Windows ISO files created using NTLite to install Virtual Machines, I do this using Virt-Manager.

Virt-Manager is able to detect the OS automatically based on Volume ID, on linux:
Code:
osinfo-detect /path/windows.iso

I noticed Virt-Manager never detects the iso created by NTLite as being a windows ISO, but it detects the original pre NTLite ISO just fine.

I tried setting the volume ID to the same as the original iso in NTLite: "CCCOMA_X64FRE_EN-US_DVD9"

NTLite changes "EN-US" to "EN_US", I am hoping NTLite could allow me to use "-" characters as part of the iso label, that should solve the issue.
 
I have been trying to find a tool to Alter the ISO label after creating the ISO with NTLite, but no luck yet.
 
No one answered this, but don't blame NTLite.

Creating ISO with volume label "CCCOMA_X64FRE_EN-US_DVD9" works just fine. When opened with 7-Zip, the file properties are:
Comment: Primary Volumes:
PrimaryVolumeDescriptorNumber: 0
VolumeSequenceNumber: 1
VolumeId: CCCOMA_X64FRE_EN-US_DVD9
VolumeSetId: 151C2422CCCOMA_X64FRE_EN-US_DVD9
ApplicationId:
ImplementationId: Microsoft IMAPI2 1.0::Windows NT

Logical Volumes:
Id: CCCOMA_X64FRE_EN-US_DVD9
BlockSize: 2048
DomainId: *OSTA UDF Compliant::1.02
ImplementationId: Microsoft IMAPI2 1.0::Windows NT

File Sets:
FileSetNumber: 0
FileSetDescNumber: 0
LogicalVolumeId: CCCOMA_X64FRE_EN-US_DVD9
Id: CCCOMA_X64FRE_EN-US_DVD9
CopyrightId:
AbstractId:
DomainId: *OSTA UDF Compliant::1.02

What's happening is the osinfo-db folks have a regex error. The workaround is renaming the ISO until they fix their database file.
<volume-id>(J_)?CEDN?A_X86FRE_</volume-id>
<volume-id>(J_)?CEDN?A_X64FREE?_</volume-id>
<volume-id>^(J_)?CEN?A_X86FREV_</volume-id>
<volume-id>^(J_)?CENN?A_X64FREV_</volume-id>
<volume-id>(J_)?CESN?N?_X86FREV_</volume-id>
<volume-id>(J_)?CESN?N?_X64FREV_</volume-id>
<volume-id>CESE_X86FREE_</volume-id>
<volume-id>CESE_X64FREE_</volume-id>
<volume-id>^(J_)?CCSN?A_X86FRE_</volume-id>
<volume-id>^(J_)?(CCSN?A|C?CCOMA)_X64FREE?_</volume-id>

Here's where they went wrong (2018).
 
Back
Top