vhdTools v0.3.1 Released

This release is a bugfix release and fixes bugs caused by using 32-bit integers (size_t is not 64-bit!) which caused problems with images > 2GB. Grab it here

Note: the 0.3.0 release link is symlinked to the 0.3.1 release.

This entry was posted on Thursday, November 30th, 2006 at 6:24 pm PST and is filed under Coding. Find similar posts by selecting any of the following tags: . You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Comments so far

  1. haha. you’re right, size_t isn’t 64-bit – but that depends on the compiler! It’s unsigned long, by default. I think that most compilers interpret ‘long’ to be 32-bit, but that’s not guaranteed. I am surprised you’re not abstracting the data types even more so that there’s never any ambiguity – in case you actually want to start porting your code ;-)

  2. Yeah I’m now using uint64_t where I need 64bit unsigned integers. I usually use this style of typing but bowed to size_t to get rid of some warnings with the mistaken assumption that it was 64-bit – who knows where I got that thought from.

  3. Not related to this blog entry, but I entered your site via the amd64 page (www.kelley.ca/amd64/), where you have putty x64 and that some other software I’ve never heard of. Anyways, the link for FileDisk points to a dubious site… Needs cleanup.

  4. Thanks for the heads up Seppo – it’s all fixed now.

  5. Congratulations for this program, I was looking for something like this.
    Now one question: Are you evaluating wrong parameters given by the user from the console? If not this probably a bug: when i typped “vhdConvert -help” the aplication did terminate in an unusual way… So well, i’ll give you the job of making a default routine for handling unexpected parameters :) .
    Well for now i do not have anything else to say you, so again thanks for your hard work.

Have your say

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.