Okie2003 wrote:It seems to me that the obvious problem is some change in BW code. The programmer of BW is fairly responsive to problems, but not focused on running it is this fashion.
Okie2003 wrote:now when I try to start it I get this error: not a valid Win32 application
mpack wrote:. . . this problem has nothing whatever to do with VirtualBox.
mpack wrote:Since my expectation is that the problem is in the install/update program, I wouldn't expect to see anything in a VB or Windows event log: in any case there is no mystery here - your problem is simply that xxx is not a legal Win32 executable, plain and simple. . . .
BillG wrote:Windows 2000 is pretty old. The real test would be to see if the updates would install on a physical machine running W2k. The developers probably do not test each release on systems before XP.
mpack wrote:. . . which it would have to do if you are correct and this is a VBox bug . .
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.
Users browsing this forum: J.Dow and 19 guests