Okie2003 wrote:I thought I had been clear that I do not think this is a VirtualBox bug. I think the coders changed something in the updates to a nonstandard code that VBox rightly rejects and wine and Windows installs over look. I tried to make this clear from the beginning.
Yes, you said that, but then you went on to assume a state of affairs that could only be accounted for by a VBox bug. Specifically, filesystem corruption. Did you do the check I suggested? It would settle the matter in minutes, and remove the need for speculation.
Incidentally, I don't see how the choice of Win2K, XP, Vista etc can have any bearing on this. The error message is quite clear about what the problem is, and I'm struggling to see why the exact variant of 32bit NT used could create this effect.
A question for Wine experts if you please: if you were to take a Linux executable and run it on Windows then you would get a "Not a Win32 executable" message. What would happen if you ran the same executable under Wine? Wine obviously has the capacity to recognize and run that file, but would it?