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.
-
Archives
- September 2009
- August 2009
- December 2008
- October 2008
- September 2008
- July 2008
- May 2008
- April 2008
- February 2008
- December 2007
- May 2007
- March 2007
- January 2007
- December 2006
- November 2006
- October 2006
- January 2006
- November 2005
- May 2005
- April 2005
- February 2005
- December 2004
- September 2004
- July 2004
-
Meta
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
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.
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.
Thanks for the heads up Seppo – it’s all fixed now.
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.