I'm a german developer and have following problem. I upgrated from v9 to v10 on my workbook with Windows 7 32 bit. Everything works fine.
Now I tried to make this on my private MacBookPro on a bootcamp partition with Windows XP SP2 32bit.
After restart I got to login, everything seems to be loaded. I see the new v10 and the old icon v9 of DirOpus.
Now the moment comes where DirOpus want to stop and exchange the DLL's I assume, I get a bluesreen and Windows reboots.
I tried to start up with F8 to safety mode, but after loading all drivers, the startup shows me a cursor on left upper corner and
nothing more happens.
What can I do, to get Windows work?? Anybody an idea?
The V10 DLLs would already have been installed by the time you saw a login prompt. That happens very early in the boot process. (If you still see a V9 icon, it's due to a bug in Windows 7. See the recent FAQ entries for details and a quick fix.)
The BSOD and inability to enter safe mode must be due to driver bugs or a hardware malfunction. Application-level software like Opus cannot cause a BSOD on its own. Check you have the latest drivers / firmware / bootcamp etc. installed on the machine.
Anti-virus and virtual-disk-mounting tools can also be a culprit, since parts of them run at the kernel level (where if something crashes it can cause a BSOD). No part of Opus itself runs at the kernel level so no part of Opus itself can cause a BSOD.