Thanks, Bill - I'll take a look. Unfortunately, no-one asked me about the new machine.
Yes, I'm well aware of multi-processor issues. I spent most of my career in the large IBM mainframe environment as a systems programmer - early on we ran a dual-processor IBM 360-67. The code involved in making sure things worked properly was horrendous. We used to joke about our famous "four o'clock lock" - fairly often at around 4 in the afternoon, the system would hang with a lock set. Not nice. At 11:15 AM 2/17/2007 -0500, you wrote: >Search "disable dual core" for a lot of stuff on the subject. Seems >you're not the only one to run into problems. Frankly, dual-core is one >advance that I'd stay a mile away from until I'm convinced it's been >proven over time. I worked with it mainframe land, and recall fixing a >bug that required clearing the processor's instruction cache. Not that >we as app developers should every have to worry about such things, but >the whole thing involves really tricky timing considerations that I >would have thought impossible for Windows to deal with (message-driven >vs interrupt-driven). Obviously they've got it to work - most of the >time - but I really wonder if it can be made to work reliably ALL of the >time. > > >Bill > Larry Bradley Orleans (Ottawa), Ontario, CANADA --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
