The container was in a huge drive that was mostly filled, so this is the only large contiguous space left. Hopefully that's where the container used to be and it wasn't fragmented elsewhere in the other bits of empty space winhex is also showing.
Do I go about testing each 512 bytes of this contiguous free space for the header, and if so, with what software? I only have the evaluation copy of winhex, and it's the only software I know of that shows these clusters as free space, the free hexeditors just show the bytes they don't point out that it's free space or currently occupied by other files.
Should I get winhex working on a virtualbox with one of the dodgy (or not dodgy) keygen cracks that claim to get it working? And if so, how does one proceed with doing this on winhex anyways? We export the clusters to a text file and somehow that's the file? Surely that doesn't make sense, right?
aa06259810