Forum: UltraISO
Topic: MSDN DVD extracts to corrupt files
started by: ptr727

Posted by ptr727 on Mar. 27 2006,15:16
I just installed the Microsoft MSDN May 2006 library after extracting the DVD contents using UltraISO 7.6.6.1308.

The MSDN failed to launch after installation, and after further consultation with Microsoft, they recommended I test the files for corruption.

I then compared the DVD image when burned to DVD with the extracted files, and many of the files extracted by UltraISO differ (corrupt) from the DVD.

Btw, the May 2006 MSDN DVD is UDF.

Is this a known bug with UltraISO?
When will it be fixed?

Pieter


Posted by Taz on Mar. 27 2006,16:42
How come you have the May 2006 MSDN so soon?

Tell me, does this edition include documentation about Managed DirectX 2.0? (which seems to be completely missing from both the SDK and msdn2.microsoft.com, I can only find v1.0).
Posted by ptr727 on Mar. 27 2006,20:13
Quote
How come you have the May 2006 MSDN so soon?

It is available for download from the MSDN subscriber site.

Quote
Tell me, does this edition include documentation about Managed DirectX 2.0? (which seems to be completely missing from both the SDK and msdn2.microsoft.com, I can only find v1.0).

I'm not at the machine with the May 2006 MSDN installed, but I do recall the new DirectX SDK including docs:

From: < http://msdn.microsoft.com/directx/ >
Quote
We are pleased to announce the availability of the February 2006 DirectX SDK. This SDK includes the initial release of the Cross-Platform Audio Content Tool (XACT), plus new Managed DirectX 2.0 beta libraries, and an updated Direct3D 10 Preview.    (March 24, Announcement)

Posted by Taz on Mar. 28 2006,12:36
Yes I have the 2006 DirectX SDK with the "Managed DirectX 2.0 beta libraries" (it's freely downloadable separately), but there is absolutely no reference documentation included (I have to rely on the samples to figure things out, I don't like that, I like a good, solid reference).
Posted by ptr727 on Mar. 28 2006,14:43
Taz, I did a quick search and could not find anything specific in the May 2006 MSDN.

Now, can we get back to the actual problem ;)

Should I submit a support email instead of posting?
Posted by xoben on Mar. 29 2006,07:56
Thanks ptr727 for the bug report. We will try to fix this bug soon.