I run it on a few dual processor machines under NT 4.0. Suhaib's previous version did as well as did the commercial version. I've not tested it on a dual processor with Win2K. Obviously, the exec onlys runs serially, but NT does a fair job of keeping the exec on one cpu and the ui on the other...
Suhaib Siddiqi <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 04/05/2001 01:41:57 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: "'[email protected]'" <[email protected]> cc: Subject: RE: [opendx-dev] DX on W2k I have not tested it on a dual processor CPU. Have you? Suhaib > -----Original Message----- > From: Chris Pelkie [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 05, 2001 12:38 PM > To: [email protected] > Subject: RE: [opendx-dev] DX on W2k > > > OK, I modified the editor.bat to do > "dx -script" which should launch the dxexec. > > Running from the DOS shell, I see > Starting DX executive > Open Visualization Data Explorer > More info... blah blah > > Version - 4.1.1 > Error during initialization > getmem can't commit memory > cannot initialize DX library > > C:\opendx\bin> > > This is a dual 300Mhz Pentium (Dell 410) with 1Gb of RAM and 1.5Gb > page space on C and 3Gb page space on D. As mentioned, W2K was just > installed (clean) a couple days ago, so it's certainly possible that > there is some config item that isn't right. > > Any other ideas of things I can check or try? Thanks. > > Chris Pelkie > Vice President/Scientific Visualization Producer > Conceptual Reality Presentations, Inc. > 30 West Meadow Drive > Ithaca, NY 14850 > [EMAIL PROTECTED] >
