Using VirtualBox version 3.2.8
Host OS Windows 7 64bit
Guest OS Windows XP SP3 32bit.
Encountered the same problem symptoms above: on an attempt to initiate Dragon, Dragon Splash (logo,banner) screen would appear and then the process would hang at this phase - just displaying the splash screen. This occurred in an XP Guest that was installed to a VirtualBox VM (not p2v). This guest was configured to support IO-APIC and multiprocessors (2) cores. Dragon 10.0 was initially installed from a CD and when this didn't work, installed service pack 1 for 10.0. Still no luck. Since I had been experimenting with single/multi processor support, I decided to disable the multi processor IO-APIC support and configure with only a single processor. To do this:
1. Obtain a copy of the single processor HAL kernel drivers. They're on the CD somewhere but it was easier for me to simply install the OS. Make sure that you're installing or will upgrade to the same XP service pack level as the multiprocess XP Guest that hosts the Dragon software.
1.1. Create VM with typical defaults but ensure IO-APIC and multprocessor support is disabled.
1.2. Install Windows XP to this newly created VM.
1.3. Copy the following files: hal.dll, ntkrnlpa.exe, and ntoskrnl.exe from the "?:\Windows\System32" directory of this newly installed single processor image to a USB key.
2. Return to the running multiprocessor Windows XP Guest.
3. Make copies of the multiprocessor HAL kernel drivers - permits you to easily restore (dynamically) multiprocessor support.
4. Copy the HAL single processor drivers, from the USB key, over the current multiprocessor ones located in the "?:\Windows\System32" directory.
5. Windows Hardware wizard will notify you of a change that requires a reboot. Turn Off the machne.
6. Change the VM settings to disable IO-APIC and reduce the supported processor total back to one.
7. Start the VM.
When you power up the VM, you'll be running a single process non IO-APIC configuration. Once you are able, start Dragon Naturally speaking. It will now finish loading itself and be ready for training.
I credit "Scott R" for providing the necessary procedure to affect the HAL kernel drivers in his blog here: http://scottr27.blogspot.com/2010/03/adding-multi-processor-support-to-32.html
. As stated in his blog, I'm not responsible if the above procedure renders your VM unbootable.