TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Tim Berkeley 75240,1316 (X)
from: Martin Raabe 100347,1334
date: 1995-01-29 03:32:19
subject: HELP - login gives error

#: 20726 S12/OS9/68000 (OSK)
    29-Jan-95  03:32:19
Sb: HELP - login gives error
Fm: Martin Raabe 100347,1334
To: Tim Berkeley 75240,1316 (X)

Hello Tim,
The reason is:
  1. There is a "System Device Name Entry" in the "init"-module.
  2. The Init.a-Sources force the Name-Entry to be 0, when no device is to be
initialized on coldboot.
  3. The Module-Sync-Byte is $4AFC (which is in ASCII:  "Ju") has the Module
offset "0".
  4. If you want to know the System Device Name, you get the pointer from the
Modulestartaddress + the Name-Entry.
  5. Login is a Microware-Utility which needs to know, where the password-file
is.
  6. The password-file is defined to be at //SYS/password
      (for Microware-utilities only!).

So when OS-9 forks the login-utility, it tries to read the password-file by
using
the chd-command. When your init-module can't says the System Device
is called "Ju" and thereis no device with this name
then you receive the errormessage: "Can't chd to "Ju"!!!!

To change this behavior you have to change the init-module!
Since I have no ideas what a CD-I maschine looks like (ROMbased, diskbased,
remoteboot from Network, ...) I can't give any other hints to solve the
problem.
If you can chasnge the init-module change the System Device Name !

Hope I helped you out!

Ciao Martin Raabe

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.