Text 1687, 123 rader
Skriven 2012-01-11 17:36:49 av Doug Bissett
Ärende: Re: Upgrade to 6 core CPU...now desktop hangs?
======================================================
mail-complaints-to="news_AT_tioat_DOT_net"
comp.os.os2.misc:3816
From: "Doug Bissett" <dougb007!SPAM@Use-Author-Supplied-Address.invalid>

On Wed, 11 Jan 2012 04:33:22 UTC, "Dariusz Piatkowski" 
<dariusz@_NO-SPAM_mnsi.net> wrote:

> Hi Trevor!
> 
> On Tue, 10 Jan 2012 21:36:30 UTC, "Trevor Hemsley" 
> <Trevor.Hemsley@mytrousers.ntlworld.com> wrote:
> 
> > On Tue, 10 Jan 2012 05:01:30 UTC in comp.os.os2.setup.misc, "Dariusz
Piatkowski"
> > <dariusz@_NO-SPAM_mnsi.net> wrote:
> > 
> > > This is with "PSD=OS2APIC.PSD /P=6 /APIC" in CONFIG.SYS and the BIOS set
to 
> > > support MPS 1.4 version (which was my previous setting, working OK with
the 4 
> > > core CPU).
> > 
> > /APIC never got much beyond the beta stage so you might try it without.
> > 
> > Also, I have got past many issues like you describe by using SET 
> > RESTARTOBJECTS=NO in config.sys
> 
> 
> Yup, as Lars suggested, I tried dropping the /APIC option, however that did
not 
> appear to improve teh situation.
> 
> Now, regarding the follow-up suggestion of yours, I attempted the following 
> (based on some previous Intenet searches):
> 
> SET RUNWORKPLACE=G:\OS2\CMD.EXE
> SET RESTARTOBJECTS=NO
> SET SHELLEXCEPTIONHANDLER=OFF
> SET SHAPIEXCEPTIONHANDLER=OFF
> 
> ...the result was a hard-lock however...what I haven't tried was leaving the
full
> CONFIG.SYS setup as-is in my 4-core configuration and attemptign the SET 
> RESTARTOBJECTS=NO on it's own. 
> 
> I will try that tomorrow and will follow-up with my results.
> 
> So far, strangely enough (to me anyways) it doesn't appear like I'm going to 
> have much luck moving to the 6-core configuration. 
> 
> I wish that the eCS ACPI solution could be tried out on some type of a trial 
> basis...because if it works I would be happy to pay the price and move along
to 
> more happy times...LOL...yes, but I'm just getting 'greedy' here trying to
get 
> the full 6 cores running...

This is actually a very old problem, known as a "startup conflict". It
can usually be caused/fixed, by simply changing the order of starting 
things in CONFIG.SYS, so that they don't step on each other. 
Unfortunately, it is not possible to say "do this" and have positive 
results (just as often, the results are negative). You need to play 
with things, to work around the problem.

FWIW, one of the main causes of that problem (but not the only one), 
is the same thing that causes looping sounds at startup. The fix for 
that one is to use the mmfix.exe program, which comes with eCS 2.1. 
See "A Note About Repeating System Sounds" at:

> http://svn.netlabs.org/uniaud/

for more information about that.

The latest indication, that I saw, happened after I installed the new 
ACPI package to my T43. It worked perfectly (well as perfectly as ACPI
has ever worked) with eCS 2.0, but in eCS 2.1, boot stopped at not 
being able to load LANMSGEX.EXE (the message indicated that it 
couldn't read the file). The work around turned out to be to use 
BASEDEV=BOOTDLY.SYS /D:2
(comes with eCS 2.1) immediately after 
PSD=ACPI.PSD

Previous to that, I have seen many other things that have caused the 
problem, and it still happens intermittently, without changing 
anything. Reboot always works, in that case.

Your problem is probably caused because OS2ACPI.PSD takes a little 
longer to get 6 processors going, or, 6 processors can get other 
things started sooner than was possible with only 4 processors. 

You must also remember that all RUN, and CALL statements, in 
CONFIG.SYS, are started at the same time that STARTUP.CMD is executed.
The programs can step on each other. The work around for that is to 
take things out of STARTUP.CMD, and start things by making an icon in 
the STARTUP folder (you can do the same with RUN and CALL statements 
that are in CONFIG.SYS, but that can cause more trouble than it 
fixes). That delays the program startup slightly, but STARTUP.CMD is 
not stepped on). Of course, then you can have the problem where all 
programs in the STARTUP folder get started at the same time. The fix 
for that is to use REXX AUTOSTART to start the STARTUP folder 
contents, one at a time. Startup may take a few extra seconds, but you
don't have conflicts (once you get it adjusted properly). I find that 
it is essential to use REXX AUTOSTART if there are more than about 4 
items in the STARTUP folder:

> http://www.7cities.net/~mckinnis/rxautost/index.html

The startup sound is also involved, so turning that off/on can also 
change the timing.

Note that startup conflicts can, and do, cause problems at startup, 
while running, and at shutdown. It all depends on exactly what the 
conflict is.

Hope something here helps...
-- 
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)


--- Internet Rex 2.31
 * Origin: The gateway at Omicron Theta (1:261/20.999)