|
Hi Dean, The reason NT is better has nothing to do with the Task Manager allowing you to kill the BPCS job. NT simply does not lock up in BPCS. Please read prior threads defining what a 'lock up' is versus what is a simple application 'hang' on the PC. I still have found no reports of a real 'lock up' on the NT platform. If you had a true lock up, the task manager would not even be available because the keyboard does not respond. The PC lock up as described on BMR43360 is non-application related, whereas a hang can always be traced to some sort of application problem, usually on the server job. Because hangs are caused generally by application errors on the server, and if you end the server job, the PC will free up. You should always check the server if the PC is hanging and see if a job is sitting in MSGW or is looping for that user profile. The Task Manager is NOT the reason that NT does not lock up or works better with BPCS. It is the operating system kernel of NT that makes it more stable, and apparently is either correcting whatever our code does poorly on WIN95, or is not allowing our code to do what it does on WIN95 or is missing the code that conflicts with ours on WIN95. Thanks Genyphyr Novak SSA -----Original Message----- From: DAsmussen@aol.com <DAsmussen@aol.com> To: BPCS-L@midrange.com <BPCS-L@midrange.com> Date: Tuesday, February 22, 2000 12:41 AM Subject: Re: PC's Locking up when in BPCS >Terry, > >In a message dated 2/17/00 5:20:07 AM Eastern Standard Time, >terry.gilligan@duval.co.uk writes: > >> We are running BPCS 6.1 C/S on AS/400 , from day 1 we have experienced >> unusually high PC crashes when in BPCS . Would be interested to here if >> anyone else is experiencing the same problems, all our PC's are high spec >> machines with 64Mb ram, running office 97 + Microsoft outlook. It was >> suggested that we turn off our anti-virus protection on our PC's ??? > >My current client is in the same boat, but was told that they wouldn't have >that problem under NT. Just left a client with NT, the reason the machines >didn't lock is that the task manager works better and allows you to kill the >BPCS job when it dies. Perhaps someone out there has a better solution than >"get NT"? SSA certainly isn't offering to pay for it as quickly as they >offer it as a solution... > >Regards, > >Dean Asmussen >Enterprise Systems Consulting, Inc. >Fuquay-Varina, NC USA >E-mail: DAsmussen@aol.com > >"Never use an axe to remove a fly from your friend's forehead." -- Chinese >Proverb >+--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.