Bug 1139394 - cannot recognize any of windows {7,8,8.1} evaluation isos from MS site
Summary: cannot recognize any of windows {7,8,8.1} evaluation isos from MS site
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libosinfo
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabiano Fidêncio
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-08 20:09 UTC by Vladimir Benes
Modified: 2018-09-07 19:43 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-09-07 19:43:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Vladimir Benes 2014-09-08 20:09:08 UTC
Description of problem:
I've downloaded several isos from MS evaluation page:

for 8.1 enterprise
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-8-1-enterprise

Version-Release number of selected component (if applicable):
libosinfo-0.2.7-10
and
libosinfo-0.2.11-1

can I do somthing to provide more information? some iso tools? not sure if you use these:

win 7 idwbinfo.txt
[BUILDINFO]
BuildArch=amd64
BuildType=fre
BuildBranch=win7_rtm
OfficialBuild=TRUE
MainBuild=FALSE
Coverage=FALSE

win 8
[BUILDINFO]
BuildArch=x86
BuildType=fre
BuildBranch=win8_rtm
OfficialBuild=TRUE
MainBuild=FALSE
Coverage=FALSE

win 8.1
[BUILDINFO]
BuildArch=amd64
BuildType=fre
BuildBranch=winblue_rtm
OfficialBuild=TRUE
MainBuild=FALSE
Coverage=FALSE

Comment 1 Christophe Fergeau 2014-09-09 08:24:01 UTC
The output of 'isoinfo -d -i $filename' is what libosinfo uses (filename of the iso is also useful).

Comment 3 Fabiano Fidêncio 2018-09-07 19:43:28 UTC
Unfortunately the evaluation ISOs for Windows 7, 8 and 8.1 are not available anymore.

After discussing this issue with Vlad, we've decided to support the current windows version available for evaluation (win10) and to close this issue as "NEXTRELEASE" (as per his request).

master:
 552bba12


Note You need to log in before you can comment on or make changes to this bug.