It was a short while (Tue, 6 Apr 1999 21:09:10 +0100) since Stephen Harris mentioned
some stuff about Re: [netconnect] Netconnect BUG??.
> Is this before or after you have quitted NC? If you set up as per question
> ie; run NC, then close using 'esc' or close button then click on NO, You should find
>that 'Status' reveals an NC process
No NC process is ever listed when I type 'status'. I presume this is
because it is run form a WB icon? My process list is simply:
13.System:> status
Process 1: Loaded as command: WBStart Handler
Process 2: Loaded as command: VisualPrefs
Process 3: Loaded as command: markabletextDTclass
Process 4: Loaded as command: ConClip
Process 5: Loaded as command: XpkMasterPrefs
Process 6: Loaded as command: NewIcons
Process 7: Loaded as command: Workbench
Process 8: Loaded as command: C:Birdie
Process 9: Loaded as command: L:WBStart-Handler
Process 10: Loaded as command: AmiTCP:kernel/AmiTCP.020
Process 12: Loaded as command: AmiTCP:bin/inetd
Process 13: Loaded as command: status
So I don't see how you can send a break to it to kill the running of
it. Anyway it's a commodity so Exchange or HandleCX should be used to
control it.
Dinky do,
Mike.
--
.--------------------------------- ---- - -- --------.
| AMiGA 1200EZT 060/PPC@240Mhz,50Mb RAM __/\__ |
| 4 HDD,DD&HD FD,5 CD-ROMS,CDRW,EZ135, \ o0 / bUDDa/S^D|
| SCSI+IDE,56kModem,BVGfX,19"VDU /_ v_\ |
`------------------------------- --- - \/ -- ------'
http://fly.to/BuddasWurld ICQ: 29173597
