Phil,

I've included Jon's reponse below, because it deserves repeating.

By whichever way you acquire a command interface, I suggest that you
make the following temporary modification to your \config.sys ...
rem SET RUNWORKPLACE=d:\OS2\PMSHELL.EXE
SET RUNWORKPLACE=d:\OS2\CMD.EXE
substituting d for your boot partition

When this loads, you'll have a "Workplace Shell" command window from
which you can "start pmshell" to load a killable desktop.

You'll need a process killer in order to kill the desktop; and you'll
need a means to access it.  For the latter (access), you might be able
to Ctl-Esc to bring up the Window List from which you could select
Workplace Shell from which you could run Top.

It also sounds like .ini file maintenance is required. I've always
found these to be tricky situations because it frequently takes more
than one run to get the job done; and too many runs can be noticeably
devastating.

Persevere, ...

--Maynard

On Thu, 22 Dec 2005 18:13:36 -0800 (PST), Jon Harrison wrote:

>You have made the wrong assumption.  The boot from alt-F1 uses a
>different config.sys (actually it uses \os2\boot\config.x). 
>Therefor, any changes you have made since that file was created
>will not be processed.

>And since you have brought this up, if you want to be
>adverturesome, you could always boot to the commandline (or as Kris
>suggested, use the management console  when booting from the CD)
>and then rename your config.x to something else, like config.x.sav
>and then copy your existing config.sys to \os2\boot\config.x.

>Then boot again to the Alt-F1 commandline.  If it is successful,
>and if you can run chkdsk /f (or /f:2) then you might be able to
>safely make the statements that the config.sys loads ok.

>As for alt-f2, it has been my experience that the last driver you
>see load before the desktop is PMShell.  If it is indeed failing at
>the desktop load then you should see drivers up to PMShell.  What I
>don't know is if there is a problem with the desktop does this also
>mean there is a problem w/ pmshell.

>The advise given to run chkdsk from a maintenance partition is the
>best advise.  And the advise to run it from the CD is the quickest
>way to do this if you don't have a maintenance partition.  Bootos2
>doesn't work anymore because the drivers are too big and won't fit
>on floppies.  The CD has been an outstanding replacement for the
>lack of a bootable solution.

>Unless you have weird hardware, you should be able to boot from the
>CD, accept all the defaults, enter your registration and instead of
>selecting install choose the little checkbox that (IIRC) is near
>the lower left portion of the screen.

>Running chkdsk this way assures you are operating on files that are
>not in use.  

>Good luck,
>jon




------------------------ Yahoo! Groups Sponsor --------------------~--> 
Most low income homes are not online. Make a difference this holiday season!
http://us.click.yahoo.com/5UeCyC/BWHMAA/TtwFAA/E8folB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2user/

 To unsubscribe from this group, send an email to:
    os2user-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



---