Hello all,

Been running slack on a nice Athlon XP 1300+ w/ a gig of memory for a while now w/ no issues. I would like to be able to boot my old w2k server drive in vmware. I installed the drive and am able to boot off of it by changing the boot configuration in the bios. All works well if I boot directly to one drive or the other.

I did a chmod 666 /dev/hdb to make it read/write and installed vmware on Slack. (I'd rather run VMware on the stable OS of course). But after a complete install and setup of the virtual system pointing to the slave drive I try to start up w2k in vmware and right when it gets to a point where I should enter in a user ID/Pass for w2k I get a blue screen.

Any ideas on how to work with this one?

Thanks!

What does the Blue Screen say?

Trying to boot an existing drive is going to be trouble. The install that you already have is set up to boot with your actual hardware, whereas vmware emulates an entirely different virtual machine. The only advice I can give you is to boot your computer into w2k server, then remove ALL the drivers, then reboot into Slack and try booting vmware. Then you'll need to install new drivers that are compatible with the virtual machine. After this, you won't be able to boot the (actual, physical) machine into w2k.

Good Luck, and keep us posted.

Enjoy!
--- Cerbere

Well I have an extra 40 gig on my main drive so maybe I'll just use 20 of it for a w2k server install via vmware and copy all existing files that I need from the slave drive over. I guess that would be acceptable (if not a bit more work than I anticipated).

I didn't think I needed to go through all that as I've done w2k installs on vmware previously and never had to load vmware drivers (that I remember). As always thanks for the info