Need help with Windows 2003 Server

[sciurius]

I have been a long time VMware user but getting Server 1 to run under modern kernels becomes more and more a problem. In fact, I cannot upgrade my system anymore since VMware won't run on the newer version. Upgrading to Server 2 is something I'd want to avoid.
For this and several other reasons I prefer VirtualBox to VMware and so far I have sucessfully migrated all my VMs -- except one. This is a Windows 2003 Server that contains software that I cannot reproduce and that I absolutely need.
Attempts to get this system running under VB have failed so far. I don't get any farther than a BSOD 0x7B even after trying the tricks I found on the net.
I would appreciate if someone who actually accomplished such a task would be willing to help me with the migration.

[vbox4me2]

There are dozens of methodes and hacks, without knowing what you've tried and done its near impossible to figure out why, as with any migration you need to de-install and de-activate as much as possible thats OS related.

[vbox4me2]

See also: http://www.google.nl/search?hl=nl&sourc ... .org&meta=

[Sasquatch]

The base of the problem seems the SATA driver. How is the disk attached in the VM settings? Use IDE to make sure it works, IDE controller mode PIIX4 (should be default).

[sciurius]

In VMware, the disk is attached through SCSI.

[sciurius]

I changed the disk to IDE and now it boots fine. I'll see how far I'm getting this time.
Thanks for the suggestions!

[Sasquatch]

What SCSI setting did you use for the VM at first? SCSI (LsiLogic)?

[vbox4me2]

I can't for the life of me understand why ppl still attempt to convert scsi to scsi... its virtual after all to some degree and alot slower at that...

[Sasquatch]

It's the problem with VMWare, that uses SCSI by default I think, at least their older versions (as the TS is using v1), especially if you select a server as Guest.