- 22 Mar, 2010 40 commits
-
-
André Hentschel authored
-
André Hentschel authored
-
Ilya Basin authored
-
Alistair Leslie-Hughes authored
-
Christian Costa authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
Roderick Colenbrander authored
-
Roderick Colenbrander authored
-
Roderick Colenbrander authored
-
Andrew Nguyen authored
-
Andrew Nguyen authored
-
Eric Pouech authored
-
Eric Pouech authored
-
Eric Pouech authored
-
Eric Pouech authored
-
Eric Pouech authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Vincent Povirk authored
This value is stored in the storage file header. We currently hard-code it to 0x1000. I don't expect to see files in the wild with other values, but according to MS this is a valid configuration. For now, just fail if we see another value. I've also upgraded the message for unexpected values in storage file headers to a fixme, since they are valid according to MS.
-