#2.1>>>Shell Process 5?
21 messages in this thread
I just installed 2.1. Among other subtle changes, I have noticed that the
SHELL is now in the System drawer. When I click on shell, it opens as
process 5 (5>). I don't have any other shell windows active, shouldn't this
be 1>? Is there something going on behind the scenes of WB 2.1? BTW, the
next shell window I open comes up as 1> !
A. Pagan
Angel,
What have you got in the WBStartUP Drawer? If you have four items in there
I think the shell will be #5. Have you had it tell you there is no disk in
df0: yet? It seems that when a command can't be found now, it tries to
look in DF0: too, and then tells me there is no disk in it. I can't figure
that one out. I checked my startup scripts, no references at all to df0:
Is this a problem with 2.1, or the setpatch program?
Chris
Chris,
If Angel had four items in his WBStartUp Drawer, you said the first
Shell he opened would be #5. Then how come the next Shell he opens is #1?
Dom Fontana
<– Sent from New York via AutoPilot –>
Dom,
I missed that part of Angel's message. Hmmmm…. I need to think some
about this one. That is weird. But nothing surprises me these days, not
after the failures I experienced yesterday.
Chris
Chris,
It hasn't asked for a disk in df0:. Whenever I type in a bad command,
AmigaDos tells me so. I typed Status and I am told that Workbench, conclip,
and iprefs are running, along with another application I have in my
user-startup. I quess the new shell accounts for processes/applications a
little differently than 2.04 did.
A. Pagan
Chris,
Hmmm, I don't have that problem (df0:). What does your path command
say?
_______________________________________________________
| WShell 7 at 0x003F0F50 [7505080 Free] >>>DL_Library2:|
|______________________________________________________|
R(0);00.049 9:02PM> path
Current_directory
Ram Disk:
DL_Library2:c
DL_Library2:Utilities
DL_Library2:Rexxc
DL_Library2:System
DL_Library2:s
DL_Library2:Prefs
DL_Library2:WBStartup
DL_Library2:Tools
DL_Library2:Tools/Commodities
AM-100c:
AM-100c:c
Vic,
In a shell I type a command that isn't available and the requester pops up
and says
__________________
| |
| No disk present |
| in device DF0 |
|__________________|
______ ________
| Retry| | Cancel |
—— ———
R(0);00.066 9:12PM> assign
Volumes:
PSFONTS [Mounted]
AM-100a [Mounted]
AM-100b [Mounted]
AM-100c [Mounted]
AM-100d [Mounted]
Ram Disk [Mounted]
DL_Library2 [Mounted]
Directories:
spritz AM-100b:Paint/Spritz
print AM-100a:WordProc/WP/Print
wp AM-100a:WordProc/WP
whap AM-100a:Tele/Whap
TERM AM-100d:Term2.2B
insight AM-100a:Khalid/Insight
AP AM-100a:Tele/AP
Turbotext AM-100c:TurboText
LOCALE DL_Library2:Locale
KEYMAPS DL_Library2:Devs/Keymaps
PRINTERS DL_Library2:Devs/Printers
REXX DL_Library2:REXX
CLIPS Ram Disk:Clipboards
<continued>
T Ram Disk:
ENV Ram Disk:ENV
ENVARC DL_Library2:Prefs/Env-Archive
SYS DL_Library2:
C DL_Library2:c
S DL_Library2:s
LIBS DL_Library2:libs
DEVS DL_Library2:Devs
FONTS DL_Library2:Fonts
L DL_Library2:l
Devices:
DHR NULL CON PIP CNC
DH0 DH1 DH2 DH3 PC3
PC1 PC0 AUX PIPE RAM
RAW SER PAR PRT DHR1
DF0 DF3
Chris
| WShell 7 at 0x003F0F50 [7505080 Free] >>>DL_Library2:|
|______________________________________________________
|
R(0);00.049 9:02PM> path
Current_directory
Ram Disk:
DL_Library2:c
DL_Library2:Utilities
DL_Library2:Rexxc
DL_Library2:System
DL_Library2:s
DL_Library2:Prefs
DL_Library2:WBStartup
DL_Library2:Tools
DL_Library2:Tools/Commodities
AM-100c:
AM-100c:c
Vic,
In a shell I type a command that isn't available and the requester pops
upand says
__________________
| |
| No disk present |
| in device DF0 |
|__________________|
______ ________
| Retry| | Cancel |
—— ———
R(0);00.066 9:12PM> assign
Volumes:
PSFONTS [Mounted]
AM-100a [Mounted]
AM-100b [Mounted]
AM-100c [Mounted]
AM-100d [Mounted]
Ram Disk [Mounted]
DL_Library2 [Mounted]
Directories:
print AM-100a:WordProc/WP/Print
wp AM-100a:WordProc/WP
TERM AM-100d:Term2.2B
AP AM-100a:Tele/AP
Turbotext AM-100c:TurboText
LOCALE DL_Library2:Locale
KEYMAPS DL_Library2:Devs/Keymaps
PRINTERS DL_Library2:Devs/Printers
REXX DL_Library2:REXX
CLIPS Ram Disk:Clipboards
<continued>
Chris
There's probably a WShell configuration reference to DF0: (maybe in the
global path ?) that is accessing DF0:. I've heard about this one
frequently (almost every new WShell owner/upgrader it sometimes seems) and
apparently there's a DF0: reference in one of the default configuration
files that you need to remove.
andy
andy,
Found it! Fixed it!
The first time I installed WSHell 2.0 I did it manually, and kept my
old global path. This time I let the install do it, so I never experienced
this problem before. I still have the old path file but I didn't restore
it from the tape.
Luckily, I noticed a problem with my hard drive and made an immediate
backup/verify to tape (plus the three older versions). So I have all my
data files, just need to replace drive. I'm thinking of getting a bumper
sticker made up that reads:
Have you backed up your hard drive today?
Chris
Chris,
Iv'e got 8 progs in wbstartup but the first shell window comes up as
process 6. Why this should be I don't know. It works, thats the main thing
🙂
Pete from Dorset in Englands West Country – via Whap!
Pete,
If you try and quit the Workbench, it should tell you,
"Cannot quit yet, there are xn Workbench launched program(s). Some
programs seem to detach themselves from the Workbench, while others do
not, see how many are attached and compare it to the number in WBStartup
before you open the shell.
Chris
Angel,
Type STATUS at the CLI prompt to see what the other tasks are. You'll have
Workbench, conclip, iprefs, etc. running.
Denny,
Thnks for enlightening me! I see now that there are four other applications
running, not counting Virus Checker in my WB Startup drawer. I never
noticed this with the 2.04 shell, it always came up as 1>.
A. Pagan
The way shell works is that it grabs the first open process and that is
the number that it uses for the shell. When you opened the first shell
there were 4 things using processes, when you opened the next process 1
was free. When I open my first shell it is usually 15. The numbers really
have nothing important to do with the shell. Just a little bit of info. If
you want to know what it going on, when you open a shell do a status, by
typing status full at the prompt. This will give you a list of the shell
processes being used by the system.
Greg
Greg Givler – CBMSER Sysop
Commodore Product Assurance
Greg,
I never noticed this under 2.04, has the shell been overhauled for 2.1?
What confuses me the most is that when I do a status check, Process 1 is
not accounted for, only 2-5. After 5 the next shell I open will be one and
the one after that is 6! A little confusing if you ask me.
A. Pagan
I really can't tell you exactly why things act the way the do, all I know
is that they do. Anyway, I have a question, and I am curious and not
trying to be smart. Why does it matter what the number of the CLI process
is? It has no bearing on how things work. It is just there for your
convenience. In fact if you change your shell-startup you can remove the
number completely from the prompt. See the documentation of the prompt
command for details. Honest, Angel, it doesn't matter to the system
whether your first shell is numbered 1 or 100, there is no difference in
operation.
Greg
Greg Givler – CBMSER Sysop
Commodore Product Assurance
Greg,
I understand where you are coming from, but belittling an observation is
not the way to go about it. I have used the shell in 1.3 and 2.04 for
extended periods of time, and never has a process other than 1> come up. I
install 2.1 and viola, my first shell window is now 5>, and the one after
that is 1>. Has the arabic number system changed with 2.1? Should we count
2,3,4,5,1,6 also? I appreciate the changes in 2.1, and I think it's a fine
operating system on the whole, it's just that I am understandably curious
as to why 2.1 accounts for processes in such an unorthodox fashion, or at
least not in the same way as other releases of the OS did. BTW, I have
already altered the shell-startup.
A. Pagan
Angel,
I think your initial CLI process on boot is 1. The startup run other
things (2-4) and your shell (5). Then the startup CLI number (1) is
available again.
Malcolm
Angel,
I am not belittling your observation. I was just pointing out that
operationally shell 5 works just the same as shell 1. I will try to get a
better explanation as to what is happening in 2.1, and will let you know.
Greg
Greg Givler – CBMSER Sysop
Commodore Product Assurance