Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

System stability issue with login. #3

Open
boisy opened this issue Sep 25, 2023 · 3 comments
Open

System stability issue with login. #3

boisy opened this issue Sep 25, 2023 · 3 comments
Labels
bug Something isn't working CoCo Foenix OS-9 Level 1

Comments

@boisy
Copy link
Collaborator

boisy commented Sep 25, 2023 •
edited
Loading

Summary

There is an issue with system stability after using the login command that appears to be related to F$Chain. I'm not certain if this is related to the fix that was implemented earlier.

Steps to reproduce

  1. Boot OS-9 Level 1 on a CoCo 2.
  2. At the shell prompt, type login [ENTER]
  3. Press [ENTER] at the username prompt, and you'll be presented with a shell.
  4. At the shell prompt, type ex [ENTER]
  5. You'll be at the shell prompt again. Type procs [ENTER]

The screen output of the procs command is garbled.
@boisy boisy changed the title System stability issue with login [OS-9 Level 1 - CoCo] System stability issue with login Nov 9, 2023
@boisy boisy changed the title [OS-9 Level 1 - CoCo] System stability issue with login System stability issue with login Nov 9, 2023
@boisy
Copy link
Collaborator Author

boisy commented Nov 9, 2023

I confirmed this also causes instability on the Foenix.

@boisy boisy added the Foenix label Nov 9, 2023
@boisy boisy changed the title System stability issue with login System stability issue with login. Nov 10, 2023
@boisy
Copy link
Collaborator Author

boisy commented Nov 25, 2023

A workaround is to type link shell after booting into NitrOS-9. This increases the shell's link count by 1 and prevents it from being removed from memory.

@boisy boisy added the bug Something isn't working label Nov 25, 2023
@jfed6000
Copy link
Collaborator

I just tried this with level 1 on a coco2:
login then procs. Shows 2 shells. mdir -e shows shell with a use count of 2. login again, procs: shows users 0-4 and 3 shells. mdir -e shows use with a count of 3. Type ex. procs works and shows 2 shells, but mdir -e shows use with a count of 1. Type ex again and procs is corrupted.

boisy pushed a commit that referenced this issue Dec 18, 2023
VTIO Edition #3, revision 0
698e87c 
Both versions:
 - Defaulted to have local Keyboard mouse settings (very helpful with GShell in EOU).
 - Modified the SS.GIP ($94) SetStat call (should be 99.9% backwards compatible):

SS.GIP (function code $94)
Entry conditions:
  A=path number
  B=$94
  X = mouse resolution; in the most significant byte
      0 = low resolution mouse
      1 = optional high resolution mouse adapter
      $FF= leave current system setting alone
      = mouse port location; in the least significant byte
      1 = right port
      2 = left port
      $FF= leave current system setting alone
  Y = key repeat start constant; in the most significant byte
      0     = no key repeat
      1-$FE = clock ticks (1/60th of a second) before key repeat starts
      $FF   = leave current system setting alone
     = key repeat delay; in the least significant byte
      0-$FE = clock ticks (1/60th of a second) before key repeats
      $FF   = leave current system setting alone
6309
  Module Size: $0969
  Module CRC:  $9FE8D3
6809
  Module Size: $097E
  Module CRC:  $32DC40
boisy pushed a commit that referenced this issue Dec 22, 2023
VTIO Edition #3, revision 0
de813b5 
Both versions:
 - Defaulted to have local Keyboard mouse settings (very helpful with GShell in EOU).
 - Modified the SS.GIP ($94) SetStat call (should be 99.9% backwards compatible):

SS.GIP (function code $94)
Entry conditions:
  A=path number
  B=$94
  X = mouse resolution; in the most significant byte
      0 = low resolution mouse
      1 = optional high resolution mouse adapter
      $FF= leave current system setting alone
      = mouse port location; in the least significant byte
      1 = right port
      2 = left port
      $FF= leave current system setting alone
  Y = key repeat start constant; in the most significant byte
      0     = no key repeat
      1-$FE = clock ticks (1/60th of a second) before key repeat starts
      $FF   = leave current system setting alone
     = key repeat delay; in the least significant byte
      0-$FE = clock ticks (1/60th of a second) before key repeats
      $FF   = leave current system setting alone
6309
  Module Size: $0969
  Module CRC:  $9FE8D3
6809
  Module Size: $097E
  Module CRC:  $32DC40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working CoCo Foenix OS-9 Level 1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@boisy @jfed6000