Can't install Win 7 in Virtualbox in linux

[pete_h]

Perry - I tried upgrading VB and changing the BIOS virtualization setting but still get the BSOD. If you look at line 503 of the 'working' log, you'll see that in that install VT-x was disabled in the BIOS to begin with. So I don't think that particular setting is causing the problem.

mpack - Like I mentioned, I tried following your moving instructions precisely, and copying the working vdi from the second computer to the external HD works fine but copying from the external HD to the first computer is somehow causing the vdi content to become gibberish, as revealed by opening with a hex editor (Bless).

Any other ideas??

[mpack]

If you think copying VDIs is what it's all about then you were not following the instructions.

[Perryg]

mpack - Like I mentioned, I tried following your moving instructions precisely, and copying the working vdi from the second computer to the external HD works fine but copying from the external HD to the first computer is somehow causing the vdi content to become gibberish, as revealed by opening with a hex editor (Bless).

The format isn't FAT32 on the external HD is it? That will not work for files over 4GB.

[pete_h]

mpack - I realize there are other items to be copied (again, I made sure to copy the entire VM folder and contents), but my point is that the vdi copy turned out odd only during the second transfer (external HD --> local HDD) and I don't understand why.

[pete_h]

Perry - Nope, it's an NTFS external HD. Again, both computers are t60p's with essentially identical hardware specs, with the only real difference being that the working computer has a different HDD. Also like I mentioned the working computer has linux mint 17 xfce while the non-working one has LM 16 xfce...I notice you're a fellow linux user...you think it has anything to do with the kernel, updates, etc? If so then I'd be confused why it worked on my t61p which has an even older version of LM (13 cinnamon).

[Perryg]

The only thing that I know of that would cause the file to be corrupted each and every time is the drive (format) you are using. What happens if you try to copy it back to the original PC, does it work or does the file become corrupt?

[Perryg]

Oh and an external drive formated in NTFS works well in Linux mint-17, and in every Linux Distro I use.

[pete_h]

Thanks Perry. Will try that now and write back in a few min.

[pete_h]

Perry - I've just copied the vdi (and its containing folder) back to the source pc, and best I can tell, the two files are identical (based on selected comparisons using the hex editor bless). So this would seem to imply there's indeed something amiss with the transfer onto the target pc, as suspected. Not to sound like a broken record but I'm inclined to strongly suspect something weird about the target pc's HDD -- but since every other app I've installed on it works fine, this is really baffling...

[Perryg]

Now you are at a point where you are having hardware issues and I am afraid that will take a technician to figure out and fix.

[mpack]

Sounds like a bad drive (bad sectors) on the target PC or transport disk. Naturally, the larger a file is, the more likely it will be to encounter the bad areas of a disk. I suggest testing all drives involved.

[pete_h]

Turns out that the problem is apparently something weird with Linux Mint 16. I recently upgraded my machine to LM 17 (still Xfce) and that resolved everything! Thanks for all your replies.