Views
956
Replies
0
Status
Closed
After I first installed CS3, it would randomly lock up as it initialized itself, right after the "searching for TWAIN drivers" message. The apparent cause was an NTVDM crash, which means it was loading some 16-bit component.
I’ve had problems with random NTVDM crashes for a while, which hasn’t been a problem because I seldom use 16-bit applications. But it became a showstopper because of CS3 (I never saw anything like that with CS2). Fortunately, that inspired me to research the problem. It turns out that NTVDM is allergic to some dual-core processors. In hindsight, the problem started right after I upgraded my computer’s CPU to an Athlon 64 X2 4600. I found a tool that can patch an application’s processor affinity table. Setting NTVDM.EXE to run only in Core 0 seems to have solved the problem.
But the question remains: Why is CS3 running a 16-bit component that needs NTVDM? I never saw that with CS2, and the third-party plug-ins are the same ones I’ve been using all along. Rather strange.
I’ve had problems with random NTVDM crashes for a while, which hasn’t been a problem because I seldom use 16-bit applications. But it became a showstopper because of CS3 (I never saw anything like that with CS2). Fortunately, that inspired me to research the problem. It turns out that NTVDM is allergic to some dual-core processors. In hindsight, the problem started right after I upgraded my computer’s CPU to an Athlon 64 X2 4600. I found a tool that can patch an application’s processor affinity table. Setting NTVDM.EXE to run only in Core 0 seems to have solved the problem.
But the question remains: Why is CS3 running a 16-bit component that needs NTVDM? I never saw that with CS2, and the third-party plug-ins are the same ones I’ve been using all along. Rather strange.
MacBook Pro 16” Mockups 🔥
– in 4 materials (clay versions included)
– 12 scenes
– 48 MacBook Pro 16″ mockups
– 6000 x 4500 px