1171
Setup & Installation / Re: Dreaded Desktop/blue screen SMP hang....
« on: November 26, 2014, 04:52:57 am »Quote
Doug: great advice regarding the DELAY.SYS driver...I had previously gone down exactly the route you suggested, "dumbed down" the CONFIG.SYS to literally the bare essentials, still got stuck. This time around I deployed the DELAY with a 30 sec pause however there are other drivers that load beyond this one, so in my case this had no imapct. I have XWorkplace installed here, so my native OS/2 startup folder has been replaced with the XWorkplace one, it is already on a 5 sec start-up delay, then each object has a 1 sec delay in-between...as best as I can tell the WPS boot never actually gets that far though. To rule our WarpCenter I had re-moved it from the "SET AUTOSTART=TASKLIST,FOLDERS,WARPCENTER" statement and tossed it in the XWorkplace start-up...still no go.
That is why I suggest using DELAY.SYS at the front, AND end, of CONFIG.SYS. It is a device driver, so it executes after the BASEDEV statements. If you use it at the front, it should delay starting other device drivers. At the end, it should delay the next step, and allow the device drivers to complete. There is no reason to delay more than a couple of seconds, unless you have something odd that is really in trouble. Of course, after the delay, you get STARTUP.CMD, the system sound, and other automatically started items. Your problem seems to be in that section.
XWorkplace folder should be okay, but I have to question why you would even consider using WarpCenter, which is known to be buggy, when you can use the far superior XCenter (perhaps even two of them).
I doubt if OS/4 will affect this problem.
Quote
VIRTUALADDRESSLIMIT=2560
I have heard that the best value is 1536, but many things can affect that.
Quote
Can anyone explain/identify any other methods I could use to actualy peak behind the covers here?
That is beyond what I have tried to do. I expect that you will need help from one of the real experts, and they don't have much time to work on such things.
One thing to try, is to complete your install (add all of your programs), using a limited number of cores, then open it up to see if it works. I had one system that was having real problems after the initial install. By the time I got it completely installed, it worked every time. (more stuff in CONFIG.SYS seems to help).