It might work, but definitely not with the drivers supplied so far!

If you do release something better, of course I will try is ASAP

sebus

OK, I managed to install Server 2003 on one hardware just fine.

But no matter what I try I can NOT get converted machine to start, as it always BSoD

As I said, it is not a rocket science to move 2003 from one hardware to another, but in this case it does not work

sebus

Ok, here it goes, I was wrong & you were right (surprise?)

Server 2003 R2 works absolutely fine, but one needs to install ALSO the driver for the physical HD controller

So in my case I was not getting 07B error from vboot, but from Standard Dual Channel IDE Controller (pci\cc_0101)

Once this was added to CriticalDeviceDatabase - support.microsoft.com/kb/314082
Server 2003 R2 converted image (with VMDK(VMWare) to VHD Converter)
works absolutely fine

sebus

So far in my testing I used different 2003 images & done few clean installs.

On overall it works fine, but I have one image created from existing hardware that works perfectly fine on that hardware. So while booted to it I installed vboot with devcon & created .vhd from this partition

No matter what I do, image booted with vboot this will ALWAYS give 07B BSoD
I spent so far 2 days testing, redoing the image, adjusting services/drivers etc

Other images on same hardware convert/install fine, but NOT this one

This vhd works absolutely fine when used in Vmlite Workstation

So there must be something that does not agree with vboot BIG time (yet I have no idea what! it could be)

sebus

Are you booting the vhd on the same computer? Sometimes, there are hard disk signature problems, as your cloned vhd has exactly same disk signature as your host. You can try to change the disk signature of the vhd.

If nothing works, you can try to attach a debugger to check if vbootsmp.sys is indeeded loaded at boot stage. You will need 2 pcs to debug, and install windbg on the host pc, and change boot.ini to enable debug option inside vhd file.

If vbootsmp.sys is loaded well, you will see it from debugger module list.

The disk signature of the vhd is distinctly different from the signature of the disk (partition) it was created from (so this is not the issue)

Would that be for debugging?

www.microsoft.com/whdc/devtools/debugging/debugstart.mspx#a

sebus