Well, this is probably a longshot, however... I'm helping a client migrate some legacy systems to VMs in preparation for some technical updates. One of these systems is a venerable Windows 2000 Server system running SQL Server 7.0. Old as it is, it's done its job handily over the years.
For various reasons, simply imaging the drive and pressing it into service is not our first choice, though we can if we have to. Instead, we've tried to bring up a new VM from scratch. With the drive delay feature described in the manual, we've been able to get Windows 2000 Server to install, update, etc. SQL Server 7.0 is another story. As near as I can tell, this product still includes some 16-bit Windows code running via what some of us will remember as "thunking". This blows sky-high in the VM, but apparently doesn't on real metal. Any thoughts? Has anyone run into any odd issues with 16-bit code running in Windows 2000 VMs (or other Windows versions) under VirtualBox? Obviously, this is old software that needs to be replaced. However, since there is data that needs to be read out first, an update is not "step one". So! Any clever ideas, thoughts, humorous anecdotes, or troubleshooting tips? Thanks, Matt _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
