Win2k3 Sp2 in VMware 6.5 hangs at boot on acpitabl.dat

I have a VMware image that has worked on 4 different machines without issue but on my laptop the Win2k3 VMware image hangs on acpitabl.dat. I'm using VMware Workstation 6.5 with 32bit Vista as the host system. When I boot into safe mode the boot hangs on acpitabl.dat and locks up my laptop completely. Ctr-Alt-Del will not even allow me to kill VMware.

I've read a few places where SP1 caused this issue which I would expect to be a dated issue? The other is HAL, but I'm not sure what to change in the image to correct this. The solution was a bit vague. One poster mentioned that acpitabl.dat was not even the real issue.

The image was created within VMware with a single CPU. What's strange is that this image will work on every other machine I try it on but this laptop.

Does anyone have any idea of what I can do to solve this? I desperately need this image to work on my laptop.

Thank you,
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bryan ButlerCommented:
A quick search shows a bunch of folks asking this, or is that all you ;)  I know if the hardware that the image is created on is "too much" different, then you will have issues.  There's not too much in the docs where "too much".  Are the 4 machines different as far as brand, mobo's, or anything?
jasonbnixonAuthor Commented:
Three of the machines were Dell laptops and one was a custom built desktop using an Asus motherboard. I just thought with so many machines the image worked on without issue that I could somehow get it to work on this one laptop.

But you are correct in that most of the machines that this image has worked on has been Dell equipment.

I'll keep at and hopefully someone else will be able to chime in with some more helpful tips. This is the first time I've asked for help with this issue. I found 3 other questions here at EE but were not detailed enough. At least for me and my lack of knowledge with VMware.

Thanks again,
Bryan ButlerCommented:
Your welcome and thanks for the additional info.  I would bet that is the problem then.  Can you run other VM images on the Asus?  Like one created on it.  Then run that on the Dells?  Cheers,
jasonbnixonAuthor Commented:
I've determined that the hardware on the odd machine is causing the issue as developedtester has suggested.

Thanks for the help.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.