October 22, 200322 yr No it's the same in essence. And I figured out what was wrong. It's a problem within Virtual PC 5.2. What exactly, I don't know. But I know that once I switched to VMware 4.0.5 everything has worked flawlessly on test runs.I think it goes back to what I said earlier in the thread
Create an account or sign in to comment