Windows XP virtual disk gets corrupted all the time.

[ASGR]

Hey,

I'm running 4.3.2 on OSX Maverick and I'm encountering problems when booting Windows XP.

Everything installs OK but when starting up I get a check disk blue screen and it looks like
it is checking the disk for several minutes. It starts to list cross-linking and allocation errors.

I've created a webm movie but this site don't like the file format even thou it's produced by
one of it's products. If it will help I'll upload it somewhere else or grab some pics...

TIA.

[ASGR]

Checked VB logs and nothing extra-ordinary
that I can tell. log attached.

[mpack]

I don't know of any problem in VirtualBox which would cause these symptoms. I can think of several host problems that might, e.g. bad sectors on the host drive. Certain self-inflicted manual configuration errors might also cause it, e.g. if someone has been borrowing drives owned by another VM etc.

[ASGR]

To conclude this post, I used NTFS instead of
FAT32 at and the problem disappeared.

[loukingjr]

To conclude this post, I used NTFS instead of
FAT32 at and the problem disappeared.

You used NTFS instead of FAT32 for what?

[mpack]

I'd guess that the filesystem wasn't properly formatted to begin with. Either that or the OP has been shutting down the VM by closing the window (i.e. cutting the virtual power). That can easily corrupt a FAT partition.

And certainly you should never install XP on a FAT32 partition, though the reason is poor performance and constraints on filesize it creates, not because XP can't handle it.

[ASGR]

Hey guys,

It was quite weird. It was one of the low level OS type errors
you get on a well used drive when the directory gets corrupted
(cross-referencing errors) but on a fresh install!

Whilst the windows initiation process was executing, I just got
endless disk error message with the option to try and fix the disk
issues that didn't help.

I did try repeatedly to delete the host files and create new VB
images and reload WXP but the problem just would not resolve
itself until I chose the NTFS format.

I used the same WXP install disk on an old iMac with BootCamp
and it worked as expected so I can only assume that it can only
be a bug in the VB code.