#: 20672 S12/OS9/68000 (OSK)
    04-Jan-95  18:01:07
Sb: #TeX Program
Fm: John R. Wainwright 72517,676
To:  Steve Wegert 76703,4255 (X)
Steve,
 Some time ago, Tim Kientzle uploaded his latest port of TeX and LaTeX to that
other place where a lot of OS9 types hang out.  This is a pretty complete
typesetting system for OS9. It includes Metafont (font building program), and
`dvips', which converts the TeX `DVI' output files to PostScript and allows
other PostScript files to be included in the final document, which can then be
printed on a PostScript printer, or (via Ghostscript) previewed on the MM/1 and
printed on most any decent printer.
 Tim K. included three versions of the main executable files in the archive,
for small, medium, and large memory machines. His install script and
instructions make it easy to install and run - but reference books on TeX and
LaTeX are recommended.
 I can run things on my MM/1 and DeskJet and Epson that look like they came
from a print shop.
 The good news: I can upload it here.
 The bad news: Tarred and Zipped, its 2.27 MEGAbytes long.
 Can you find that much room in Lib 12?
JohnW
           ********************************
       A stitch in time --------------------
               ------ is worth two in the bush
 John R. Wainwright <<CIS -- 72517,676>> <<DELPHI -- JOHNREED>>
There are 2 Replies.

#: 20674 S12/OS9/68000 (OSK)
    05-Jan-95  09:18:15
Sb: #20672-#TeX Program
Fm: Mark Griffith 76070,41
To: John R. Wainwright 72517,676 (X)
John,
Got tired of Lout eh?  (grin)
There is 1 Reply.

#: 20683 S12/OS9/68000 (OSK)
    06-Jan-95  20:30:37
Sb: #20674-TeX Program
Fm: John R. Wainwright 72517,676
To: Mark Griffith 76070,41
 >
 > Got tired of Lout eh?  (grin)
 >
 I still have Lout on the system, but I have to have TeX for the same reason
that I have a messydos computer --- the rest of the world is using it.  (OK
maybe not ALL of the rest of the world -- there are a few misguided souls using
WordPerfect and such). ;)
Lots of the GNU/UNIX stuff I have looked at has docs in TeX format. LaTeX makes
TeX ALMOST as easy as Lout, anyway.
           ********************************
       A stitch in time --------------------
               ------ is worth two in the bush
 John R. Wainwright <<CIS -- 72517,676>> <<DELPHI -- JOHNREED>>

#: 20681 S12/OS9/68000 (OSK)
    06-Jan-95  17:32:31
Sb: #20672-TeX Program
Fm: Steve Wegert 76703,4255
To: John R. Wainwright 72517,676 (X)
John,
I'm not certain, John .... space is pretty tight at the moment. Let me bounce
it upstairs and see what Wayne can do for us.
*- Steve -*

#: 20678 S12/OS9/68000 (OSK)
    06-Jan-95  03:31:17
Sb: PC <--> OS/9 via TCP/IP?
Fm: Ingo Pakleppa (ECS) 100041,102
To: all
Hello,
I'm developed a PC application that should talk to an OS/9 system (68k) via the
FTP protocol.
Most of the time, this works just fine - but sometimes, my TCP/IP package on
the PC end reports odd errors that I have not been able to track down.
I suspect some subtle incompatibility between the PC's flavor of FTP and the
OS/9 flavor. Distinct (the supplier of the PC TCP/IP software) was unable to
help me. Therefore, I now decided to bite the bullet and rewrite my software,
using a different package.
My questions are these:
- I am using Distinct TCP/IP 3.20. Does anybody possibly have experience with
the combination OS/9 - Distinct and know what might be the problem?
- has anybody successfully connected a PC with an OS/9 system? With which
TCP/IP software?
Some configuration information:
In the installation in question, two OS/9 systems are connected with a
(reliable) Ethernet connection. There are quite a few PCs connected to the same
Ethernet; they access a Novell server. One single PC actually talks to both the
Novell server and the OS/9 systems; both protocols are installed on top of the
same network adapter card.
I have also tried a connection between the two OS/9 systems and a PC only,
disconnected from the Novell network - same result. Therefore, I'm sure that
there is not just a conflict between the different network protocols.
The error I get apparently usually occurs during an ftp_get or ftp_put
function, and it returns error code 451 (which seems to indicate a local abort
- something I definitely did not trigger).
Thanks in advance for any hints, either regarding a different TCP/IP library or
finding the cause of the problem!
Ingo
Press <CR> !>

#: 20706 S12/OS9/68000 (OSK)
    13-Jan-95  17:48:07
Sb: #20678-PC <--> OS/9 via TCP/IP?
Fm: DTR 100302,3271
To: Ingo Pakleppa (ECS) 100041,102
Sehr Interessant Ihre Entwicklung! Bitte senden Sie uns einmal eine
detaillierte Beschreibung.
DTR Kiel
Bremer Str.2
D-24118 Kiel
Fax 0431-86511
* We supply OS-9 software *

#: 20684 S12/OS9/68000 (OSK)
    07-Jan-95  04:30:17
Sb: #library 12
Fm: Ed Gresick 76576,3312
To: SYSOP (X)
I've uploaded 3 files to library 12.  I need to upload 1 more (10k) to complete
the set but there isn't any more space.  Can you make some more space??
Ed Gresick - DELMARCO
There is 1 Reply.

#: 20685 S12/OS9/68000 (OSK)
    07-Jan-95  08:06:42
Sb: #20684-library 12
Fm: Mike Ward 76703,2013
To: Ed Gresick 76576,3312 (X)
Give it a shot now.

#: 20686 S12/OS9/68000 (OSK)
    07-Jan-95  10:22:42
Sb: #HELP - login gives error
Fm: Tim Berkeley 75240,1316
To: ALL
Hi all
I am having a problem trying to get a telnet session into my osk system. After
it connects it generates the following message and disconnects.
I get the exact same message when I execute login from an existing shell.
Anybody seen this before?
Thanking you in anticipation
Tim Berkeley
There is 1 Reply.

#: 20691 S12/OS9/68000 (OSK)
    08-Jan-95  13:12:09
Sb: #20686-#HELP - login gives error
Fm: Steve Wegert 76703,4255
To: Tim Berkeley 75240,1316 (X)
Tim,
What error message are you getting? What software are you using to run a telnet
session? What hardware platform are you running OS9 under?
*- Steve -*
There is 1 Reply.

#: 20693 S12/OS9/68000 (OSK)
    08-Jan-95  19:07:05
Sb: #20691-#HELP - login gives error
Fm: Tim Berkeley 75240,1316
To: Steve Wegert 76703,4255 (X)
Opps - sorry about the incomplete message
The hardware running OS9 is a Philips CDI 605 T, the TCP/IP stack that I am
using is the 32bit Windows for Workgroups stuff from Microsoft. The error
message I get from login is:
        "login: can't chd to "Ju". Error #000:215".
Thanks for your time.
Tim
There is 1 Reply.

#: 20694 S12/OS9/68000 (OSK)
    09-Jan-95  11:54:16
Sb: #20693-HELP - login gives error
Fm: Pete Lyall 76703,4230
To: Tim Berkeley 75240,1316 (X)
Tim -
Sounds like your password file is pointing to an initial login directory for
the user that:
 a) Doesn't exist
 b) Doesn't have permissions set right
 c) Isn't owned by the user
Also - a corrupt password file entry may be the candidate.
Pete
P.S. I have also seen similar errors when OS9 tries to execute an executable as
a shell script.

#: 20687 S12/OS9/68000 (OSK)
    07-Jan-95  22:56:52
Sb: #unix functions
Fm: Bob van der Poel 76510,2203
To: all
Does anyone happen to know what the functions lockf() or flock() do in the unix
environment? Is there an equivalent OS9ism?
There are 3 Replies.

#: 20695 S12/OS9/68000 (OSK)
    09-Jan-95  11:59:48
Sb: #20687-unix functions
Fm: Pete Lyall 76703,4230
To: Bob van der Poel 76510,2203 (X)
Locks, unlocks, and tests for locks on a Unix file. Calling syntax is
'lockf(fd,cmd,size)', where fd and cmd are ints, and size is a long.
Command tokens are:
   F_ULOCK 0 /* unlock a previously locked section */
   F_LOCK  1 /* lock a section for exclusive use */
   F_TLOCK 2 /* test and lock a sexction (non-blockking) */
   F_TEST  3 /* test section for other processes' locks */
I'm sure you could implement this with SS_LOCK etc on an RBF device.
Pete

#: 20698 S12/OS9/68000 (OSK)
    11-Jan-95  21:12:26
Sb: #20687-#unix functions
Fm: Bob van der Poel 76510,2203
To: Bob van der Poel 76510,2203 (X)
>Locks, unlocks, and tests for locks on a Unix file. Calling syntax is
>'lockf(fd,cmd,size)', where fd and cmd are ints, and size is a long. >
>Command tokens are: > >   F_ULOCK 0 /* unlock a previously locked section */ >
F_LOCK  1 /* lock a section for exclusive use */ >   F_TLOCK 2 /* test and lock
a sexction (non-blockking) */ >   F_TEST  3 /* test section for other
processes' locks */ > >I'm sure you could implement this with SS_LOCK etc on an
RBF device.
1. If you do something like lockf(fd, F_LOCK, 1234) which 1234 bytes would be
   locked out?
2. If you use F_TLOCK what does non-blocking mean? After all, the idea of
   doing a lock is _to_ lock (ie. block?) a part of a file?
Thanks Pete!
There is 1 Reply.

#: 20699 S12/OS9/68000 (OSK)
    12-Jan-95  10:47:15
Sb: #20698-unix functions
Fm: Pete Lyall 76703,4230
To: Bob van der Poel 76510,2203 (X)
I'm guessing the lock would be placed at wherever the current file pointer is..
You could seek to any part of the file, and apply the lock.
In the case of question 2, I have no idea. Guessing, but even OS9 has blocking
and non-blocking locks. You can read a file that has an EOF lock on it (up to
the lock, of course), but you can't read a file that has a locksize of
0xffffffff applied, etc.

#: 20701 S12/OS9/68000 (OSK)
    13-Jan-95  00:28:27
Sb: #20687-unix functions
Fm: Kim Kempf 71161,3221
To: Bob van der Poel 76510,2203 (X)
 >> Does anyone happen to know what the functions lockf() or flock() do in the
unix environment? Is there an equivalent OS9ism? <<
 RBF provides implicit locks when a file is opened for update (read/write).
When a process does a read() when the file is opened for update the bytes in
the file that were read are implicitly "locked".  If another process (or the
same process on a different path) tries to read or write within the locked byte
range, the call will block until the reading process performs a write(),
another read() or _ss_lock(0).
 An explicit lock can be set with _ss_lock(len) which will lock the bytes from
the current file position for "len" bytes.  If len == ~0, then the entire file
is locked.  A program can limit the time it's blocked waiting for the lock by
calling _ss_tiks(val) where "val" is the maximum number of ticks to wait for
the lock before returning E_LOCK.  E_DEADLK is returned when two locks by the
same or different processes would result in a "deadly-embrace".
 That was the one paragraph dissertation on OS-9/RBF record locking.  There is
also a special EOF lock.  If anyone is interested, I can give a one paragraph
dissertation on that, too!

#: 20688 S12/OS9/68000 (OSK)
    07-Jan-95  23:52:48
Sb: #unix functions
Fm: LARRY OLSON 72227,3467
To: Bob van der Poel 76510,2203 (X)
   Bob,
       Have you had a chance to try mm2hp30 yet ?
   Just wondering if found any problems, that -f option should get around
   the problem of the program not being able to determine the screen type
   on its own, for now.
    hint: most pictures come out best with
          a brightness value around -v=45 to -v=65
     Is there any option available for your laser that you would like
   to see in the program ?
There is 1 Reply.

#: 20692 S12/OS9/68000 (OSK)
    08-Jan-95  16:56:04
Sb: #20688-#unix functions
Fm: Bud Hamblen 72466,256
To: LARRY OLSON 72227,3467 (X)
Bob,
Here's what "man flock" produced on my LINUX box:
    FLOCK(2)            Linux Programmer's Manual                FLOCK(2)
    NAME
           flock - apply or remove an advisory lock on an open file
    SYNOPSIS
           #include <sys/file.h>
           int flock(int fd, int operation)
    DESCRIPTION
           Apply  or  remove  an  advisory lock on an open file.  The
           file is specified  by  fd.   Valid  operations  are  given
           below:
                  LOCK_SH   Shared lock.  More than one process may
                            hold a shared lock for a given file at a
                            given time.
                  LOCK_EX   Exclusive  lock.   Only  one  process may
                            hold an exclusive lock for a  given  file
                            at a given time.
                  LOCK_UN   Unlock.
                  LOCK_NB   Don't  block when locking.  May be speci-
                            fied (by or'ing) along with  one  of  the
                            other operations.
           A  single file may not simultaneously have both shared and
           exclusive locks.
           A file is locked (i.e., the inode), not the file descrip-
           tor.   So,  dup(2)  and fork(2) do  not  create multiple
           instances of a lock.
    RETURN VALUE
           On success, zero is returned.  On error, -1  is returned,
           and errno is set appropriately.
    ERRORS
           EWOULDBLOCK
                  The   file  is  locked  and  the  LOCK_NB flag  was
                  selected.
    NOTES
           Under Linux, flock is implemented  as  a  call  to  fcntl.
           Please see fcntl(2) for more details on errors.
    SEE ALSO
           open(2), close(2), dup(2), execve(2), fcntl(2), fork(2),
    Linux 0.99.11                22 July 19
I guess _ss_lock() for Mircoware C 3.2 or _os_ss_lock() for Ultra C would be
the nearest OS-9/68000 equivalnets.
"Man lockf" produced nothing.
Bud
There is 1 Reply.

#: 20696 S12/OS9/68000 (OSK)
    09-Jan-95  20:58:19
Sb: #20692-unix functions
Fm: Bob van der Poel 76510,2203
To: Bud Hamblen 72466,256
Thanks, Bud, for the man page. I _think_ that _ss_lock() may be used to
impliment a similar function under os9. But, I really don't understand what the
various flock options do...

#: 20704 S12/OS9/68000 (OSK)
    13-Jan-95  15:15:57
Sb: #module permissions
Fm: Bob van der Poel 76510,2203
To: all
I'm a bit confused.... I have my osk system set up to let other family members
login from a remote terminal. For some reason, they can't use VED, even though
it has its permissions set properly. An attr of ved shows
     --e--ewr
and ident shows
    Owner:           0.0
    Permission:      $555        -----e-r-e-r-e-r
    ...
If superuser loads VED into memory, all works fine. But, if user 3.3 or 4.4
types "ved foo" at the keyboard they receive an error 164. I tired setting
public read and write attributes, but it made no difference. Also, I checked
the directory attributes--they give public access (proven by setting the read
bit and then doing an ident, which works).
I have some other modules with similar attributes and they work fine. Also, I'm
sure that this used to work!!!
There is 1 Reply.

#: 20708 S12/OS9/68000 (OSK)
    14-Jan-95  11:55:19
Sb: #20704-module permissions
Fm: Kim Kempf 71161,3221
To: Bob van der Poel 76510,2203
 >> I have some other modules with similar attributes and they work fine. Also,
I'm sure that this used to work!!! <<
 Be sure the file attributes match the module attrbutes.  In this case, dir -e
should show the file being owned by 0.0, use chown to change if required.
Press <CR> !>

#: 20710 S12/OS9/68000 (OSK)
    15-Jan-95  12:07:33
Sb: #20708-module permissions
Fm: Bob van der Poel 76510,2203
To: Kim Kempf 71161,3221
Yes, dir -e shows VED as being owned by user 0.0. Also, it shows public execute
permisssion. And the module attributes show it being owned by user 0.0...and it
has public exec. permission. That is why this is so strange...if there is a
problem with attributes you get an error 214. However, I am getting an error
164! Hey guys...this is really bugging me...any suggestions are welcome!

#: 20712 S12/OS9/68000 (OSK)
    15-Jan-95  14:12:33
Sb: #20708-#module permissions
Fm: Bob van der Poel 76510,2203
To: Kim Kempf 71161,3221
Oh, this is interesting. I just checked the output of dir -e again...only to
discover that the owner of VED is 31.0. Now, I have no idea of how this was
changed from the normal 0.0...espcially since I am the only one who can compile
it <g>. So, I changed the ownership to 0.0 and now user 5.5 can execute the
program...just like things should be.
However, I still don't understand this:
 - file owner 31.0, public exec permission
 - module owner 0.0, public exec permission
 - attempts by user 5.5 to execute program generate error 164.
I thought that if the public exec bit was set, then anyone could exec the
program, no matter what the program's ownership? Could someone explain this?
There is 1 Reply.

#: 20717 S12/OS9/68000 (OSK)
    18-Jan-95  00:06:33
Sb: #20712-#module permissions
Fm: Kevin Darling 76703,4227
To: Bob van der Poel 76510,2203 (X)
Bob,
But does your program do anything that only a superuser can do?  Like use
F$Permit, or try to set the user id, etc?
kev
There is 1 Reply.

#: 20720 S12/OS9/68000 (OSK)
    20-Jan-95  16:22:14
Sb: #20717-module permissions
Fm: Bob van der Poel 76510,2203
To: Kevin Darling 76703,4227 (X)
>But does your program do anything that only a superuser can do?  Like use
>F$Permit, or try to set the user id, etc?
No, not at all. Well, not right away. In any event, since the program has the
GHOST bit set, it should still load into memory before it craps out. I've done
some more sleuthing...on my mm/1 I can duplicate the problem with other
programs which, for sure, don't do anything funny. Don't know if there is
anything magic about user 31.0, but try setting a program to that user and then
log in as user 5.5. You should get the 164 error. However, on my MVME running
os9 3.0 I don't get the error. Looks like MW fixed something???
Bob

#: 20716 S12/OS9/68000 (OSK)
    17-Jan-95  20:11:59
Sb: #20708-module permissions
Fm: Bob van der Poel 76510,2203
To: Kim Kempf 71161,3221
I discovered why my copy of ved had its ownership changed from 0.0 to 31.0. On
my other machine I used gtar to save all files on the HD to tape and then
reformatted the HD and restored the files. ALL THE FILES ON THE HD ARE NOW
OWNED BY 31.0!
I don't like this. I will have to play with gtar to see if this is avoidable.
In the meantime, I am running chown to restore my file ownerships.

#: 20713 S12/OS9/68000 (OSK)
    15-Jan-95  15:21:46
Sb: PC <--> OS/9 via TCP/IP?
Fm: Nick Hall 100330,2555
To: Ingo Pakleppa (ECS) 100041,102
Hi Ingo,
Yep - I've written some simple apps using the Distinct VBX's talking to OS-9
via TCP/IP. These PC apps actually sat on top of NetManage stack and
communicated at the WinSock level.
I had chosen the NetManage stack before I became aware of the Distinct tools;
however, no major problems so far. BUT we are using the Telnet VBX  and not
FTP.
I did have some minor problems and contacted Distinct. No firm solutions were
found, but shortly after the problem seemed to go away!!
Shout if you want to discuss your problems further - I might be able to help
:-)
Regards,
Nick
[England]
[Internet: nhall@dircon.co.uk]

#: 20714 S12/OS9/68000 (OSK)
    15-Jan-95  19:54:36
Sb: module permissions
Fm: David Breeding 72330,2051
To: Bob van der Poel 76510,2203 (X)
RE : can't load VED from terminal
 > If superuser loads VED into memory, all works fine. But, if user 3.3 or 4.4
 > types "ved foo" at the keyboard they receive an error 164.
Do you mean they can run it if it is loaded?  If they can't run it at all,
could it be that the attrib of some support files might be wrong, or maybe even
the text file(s) themselves, and the error report could be coming from within
the program?  Being a relative newcomer to OSK, it's still a little new to me,
but this error #164 looks a little odd.  I would think it is not coming from
the shell load itself.
 > problem with attributes you get an error 214. However, I am getting an
 > error 164! Hey guys...this is really bugging me...any suggestions are
 > welcome!
I know what you mn doing an ident, which works).
I have some other modules with similar attributes and they work fine. Also, I'm
sure that this used to work!!!

#: 20708 S12/OS9/68000 (OSK) Sat 14-Jan-95  12:55:19 Sb: #20704-module
permissions Fm: Kim Kempf 71161,3221 Tove been playing around with login
myself..  Seems like I've seen some posts about all this stuff before, but
they've disappeared somewhere.
If I understood my manual correctly, it said you had access to a file as long
as your Grp #'s matched _OR_ your User #'s matched.  However, in playing around
with my system, you could access a file _ONLY_ if your User #'s matched.
Different Grp #'s would lock you out.. Is this the way it's supposed to be?  I
just _KNOW_ I've seen this discussed before, but I've lost it.. sorry.
Also, it appears that "motd" is displayed if the GRP # is either 0 or 1, with
any user #, but not displayed for a higher Grp #.  Is this the way it is?
                   -- David Breeding --
                 CompuServe :  72330,2051
                     Delphi :  DBREEDING
         ***  Sent via CoCo-InfoXpress V1.01 ***
                       ^^^^ ^^^^^^^^^^
Press <CR> !>

#: 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 /<System Device Name>/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

#: 20727 S12/OS9/68000 (OSK)
    31-Jan-95  22:37:52
Sb: #Windio #54
Fm: Boisy G. Pitre 74464,3005
To: all
Windio #54 has been uploaded to forum 12 (OS-9/68000)
There is 1 Reply.

#: 20731 S12/OS9/68000 (OSK)
    02-Feb-95  17:33:15
Sb: #20727-Windio #54
Fm: Steve Wegert 76703,4255
To: Boisy G. Pitre 74464,3005 (X)
 > Windio #54 has been uploaded to forum 12 (OS-9/68000)
That's great news, Boisy. But lemme ask .... what changed David's mind?
When I inquired about versions after 51 being available he indicated he was
charging for the thing.
How about a quick rundown of the improvements/fixes from say 51?
*- Steve -*
Press <CR> !>

#: 20772 S12/OS9/68000 (OSK)
    17-Feb-95  23:07:47
Sb: IRQ Stack
Fm: David Breeding 72330,2051
To: Steve Wegert 76703,4255 (X)
Steve,
I'll address this to you, since, it was you who was involved in the
conversation (way back in '92).  In reviewing some of my old msg saves, I came
across a thread where you were discussing serial port woes, and you and Kevin
Darling were discussing IRQ Stack size..  You said yours was originally 512,
you upped yours to Kevin's size.. 4096.  Were you talking word-size or byte
size?  My moded gives this size in words, and mine is now set to 256 (1024
bytes).  If you were discussing word size, then I should probably up mine.  I
think Kevin thought your 512 was rather small. (Of course, if you were talking
bytes, then I'm probably in pretty good shape.)
                         -- David Breeding --
   CompuServe : 72330,2051                  Delphi :  DBREEDING
         ***  Sent via       InfoXpress/OSK - Vr. 1.02    ***
Press <CR> !>

#: 20776 S12/OS9/68000 (OSK)
    18-Feb-95  17:32:40
Sb: #20772-#IRQ Stack
Fm: Steve Wegert 76703,4255
To: David Breeding 72330,2051 (X)
Hi David!
Geeze .... back to 1992 eh?
Leseee .... reviewing the init module of my current os9boot with moded I see
that the IRQstack size parameter reported is 1024. I believe I did indeed bump
that up from a previously reported 512.
I do believe we're speaking in "word size" here so in bytes, that would be
4096.
*- Steve -*
There is 1 Reply.

#: 20777 S12/OS9/68000 (OSK)
    18-Feb-95  23:09:24
Sb: #20776-#IRQ Stack
Fm: David Breeding 72330,2051
To: Steve Wegert 76703,4255 (X)
 > Geeze .... back to 1992 eh?
Yeah, I save anything that looks like it might be useful.. (I was looking
forward to going to OSK for a long time..  All that stuff was Greek back then,
but it is meaningful, now.. <G>
 > Leseee .... reviewing the init module of my current os9boot with moded I
 > see that the IRQstack size parameter reported is 1024. I believe I did
 > indeed bump that up from a previously reported 512.
 >
 > I do believe we're speaking in "word size" here so in bytes, that would
 > be 4096.
Long word is what my moded reports..  Mine was 256 (words)..  I bumped mine up
to 512 last night, might go on up.
Thanks, Steve.
                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***
There is 1 Reply.

#: 20789 S12/OS9/68000 (OSK)
    21-Feb-95  11:38:51
Sb: #20777-IRQ Stack
Fm: David M. Horn 73260,242
To: David Breeding 72330,2051
David,
Microware sets the IRQ stack size intentionally low to get good minimum memory
numbers for marketing.  If your system has a significant amount of IRQ activity
(such as serial I/O), this number should be increased generously.  I was
working with a system that had 32 high speed intelligent serial ports, upto 28
more conventional serial ports, and lots of hard disk activity.  I think we
increased the IRQ stack to 32k long words.  OS-9 does not always report IRQ
stack problems gracefully, so increasing the IRQ stack is a good thing to try
if you can't figure out strange behavior in a complex system.
David Horn
Press <CR> !>

#: 20798 S12/OS9/68000 (OSK)
    23-Feb-95  20:04:09
Sb: #20789-IRQ Stack
Fm: David Breeding 72330,2051
To: David M. Horn 73260,242 (X)
 > Microware sets the IRQ stack size intentionally low to get good minimum
 > memory numbers for marketing.  If your system has a significant amount of
 > IRQ activity (such as serial I/O), this number should be increased
 > generously.
Thanks, David,
I think I'll follow Steve's lead and set it for about 1K Words.  Actually, I
don't have an _extremely_ lot of IRQ's to contend with, Steve probably has a
more intense usage than me, so this should probably take care of me.
I'll keep your info filed away, as it appears to be pretty inforative.
                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***
Press <CR> !>
The OS-9 Forum+ Messages Menu
Message age selection = [New]
 1 SELECT (Read by section and subject)
 2 READ or search messages
 3 CHANGE age selection
 4 COMPOSE a message
 5 UPLOAD a message
Enter choice !>2
The OS-9 Forum+ Read Menu
Read
 1 [NEW] messages
 2 Message NUMBER
 3 WAITING messages for you (0)
Search [new] messages
 4 FROM (Sender)
 5 SUBJECT
 6 TO (Recipient)
Enter choice !>1

#: 20833 S12/OS9/68000 (OSK)
    10-Mar-95  16:35:59
Sb: #20421-I could use a favor
Fm: bas de jong 100573,2001
To: Daniel Cyran 73750,1020
Hey there,
I had a simular problem trying to get my home-build 68000 system running. You
could try to 'undelete' the directory-entries in the CMDS directory. (first
character is wiped out to zero). Just write a small program to read and write
the disk.... I use SCSI, so commands $08 and $0A do wonders (read resp. write).
All info read in byte, special articles (2) 5 years ago. Hope I helped a bit,
more info available if wanted.
Greetings, Bas

#: 20822 S12/OS9/68000 (OSK)
    03-Mar-95  21:18:35
Sb: #20678-PC <--> OS/9 via TCP/IP?
Fm: Jost Eberbach 73502,2041
To: Ingo Pakleppa (ECS) 100041,102
Hi Ingo,
I have successfully connected a PC with an OS-9 System using TCP/IP-software
from Beame&Whiteside. It worked pretty well, I never ran into any major
problem. Beame&Whiteside offer DOS and Windows Software, it's pretty sleek...
Jost

#: 20809 S12/OS9/68000 (OSK)
    26-Feb-95  22:25:45
Sb: CDL Basic demo uploaded
Fm: Frank Hogg of FHL 70310,317
To: all
I have just uploaded the following files to the OS9/68000 data lib #12.
The file 'CBManual' is a straight text file of the mini manual for
the demo of CDL Basic, a true native code 68000 compiler for
OS9/68000. You don't need this if you download either of the archives as this
is included in both of them.
The file 'cbdemo.lzh' is the complete demo with the mini manual
compressed with:
 'LHa Vrs. 2.01 for OSK - Ported June 15, 1992 M.Haaland'
The file 'cbdemo.ar' is the complete demo with the mini manual
compressed with:
 'Ar V2.00 - archive file manager'
This is a complete working demo of CDL Basic Version 1.0 that is
only limited in the size of the program you can compile. Many
examples are included that will compile with the demo.
Enjoy
Frank Hogg - FHL

#: 20810 S12/OS9/68000 (OSK)
    26-Feb-95  22:27:07
Sb: #CDL Basic demo
Fm: Frank Hogg of FHL 70310,317
To: sysop (X)
Hi,
I just uploaded three files to data lib 12. Could you please make these
available.
Thanks
Frank
There is 1 Reply.

#: 20811 S12/OS9/68000 (OSK)
    27-Feb-95  04:09:34
Sb: #20810-CDL Basic demo
Fm: Mike Ward 76703,2013
To: Frank Hogg of FHL 70310,317 (X)
Sure thing!

#: 20821 S12/OS9/68000 (OSK)
    03-Mar-95  21:18:29
Sb: #OS9 on the MVME162
Fm: Jost Eberbach 73502,2041
To: all
Is anybody here using the Motorola MVME162 board with OS9?
I have worked a lot with the board, using both OS9 version 2.4 and 3.0. I'd
like to share my experiences with others interested in the topic, and maybe
learn some new things...
Jost
There are 2 Replies.

#: 20823 S12/OS9/68000 (OSK)
    04-Mar-95  16:15:42
Sb: #20821-#OS9 on the MVME162
Fm: Timothy J. Martin 71541,3611
To: Jost Eberbach 73502,2041 (X)
Yes, I use MVME162 and 162LX, also 147 and 167. 162LX serial port descriptors
need to have upper two descriptors on a different vector than the lower two
descriptors, else a port will lock up during simultaneous interrupts.  Happened
all the time when doing 9600 baud input on say /term and /t2.
Also, note that the init module for V2.4 162 distribution has the patternize
memory bit enabled.  free of big chunks of memory may cost you missed
interrupts if patternize memory is enabled.
There is 1 Reply.

#: 20825 S12/OS9/68000 (OSK)
    05-Mar-95  13:21:45
Sb: #20823-OS9 on the MVME162
Fm: Bob van der Poel 76510,2203
To: Timothy J. Martin 71541,3611 (X)
I have a MVME 147S-1 and see with interest that you have used one for quite
awhile. A question: Have you ever managed to get the serial ports working using
hardware handshaking? I would like to use one for the serial ports for a
printer, but xon/off is out of the question. It would also make the use of a
highspeed modem a possibility.

#: 20824 S12/OS9/68000 (OSK)
    05-Mar-95  08:01:51
Sb: #20821-OS9 on the MVME162
Fm: Joachim Terasa 100421,2472
To: Jost Eberbach 73502,2041 (X)
Hi Jost,
 >> I have worked a lot with the board, using both OS9 version 2.4 and 3.0. I'd
like to share my experiences with others interested in the topic, and maybe
learn some new things... <<
 I've worked for years with a MVME147-system and OS-9 versions 2.0 to 2.4. That
means I have a lot of experiences with OS-9 at any level.
 End of this week I'll get my new VME-System based on a MVME162. I think we'll
have to talk a lot in advance!
 Jochen
  -Joachim Terasa
!^NavFont01F000BIGOHG9CHH67401E

#: 20831 S12/OS9/68000 (OSK)
    08-Mar-95  16:26:57
Sb: #OS9 on the MVME162
Fm: Jost Eberbach 73502,2041
To: Joachim Terasa 100421,2472 (X)
Hallo!
Vielen Dank fur die Message! Ich nehm mal einfach an, ich kann in Deutsch
schreiben...
Ich will mal ein bischen uber mich und meine Beziehung zum geliebten OS9-162
BSP erzahlen:
Ich lebe seit zwei Jahren in Ohio, USA, und seit anderthalb Jahren mache ich
jetzt schon mit dem MVME162 rum. Anfangs war es ganz schon schwierig, ich hatte
keinerlei Erfahrung mit OS9, aber mittlerweile hab ich die Sache gut im Griff.
Microware macht es einem nicht gerade einfach!
Meine Applikationen sind spezielle Regelkreise fur Walzwerke, mit vielen Timer-
und I/O-Interrupts, Ethernet-Communication, etc..
Ich hab mit OS9-Version 2.45 angefangen, bin dann auf 3.0 umgestiegen. Jetzt
benutz ich beide Versionen, weil es noch nicht viel Device Driver fur 3.0 gibt.
Eigentlich kein grosses Problem, aber wenn man ein serial interface board
benutzen will, ist ein fertiger Treiber ziemlich hilfreich...
Ich benutze die Extended Version vom BSP, und hab sowohl Self-Hosted
Development als auch PCbridge (beides Ultra-C) zur Verfugung. FasTrack hab ich
leider noch nicht...
Als I/O benutze ich GreenSpring IP-Module, und zwar IP-16ADC, IP-DAC,
IP-Quadrature und IP-Dual PI/T.
Ich habe ein paar Utilities geschrieben, mit denen man das Flash-Eprom fur OS9
zuganglich machen kann. Das OS9-162 BSP unterstutzt das Flash-Eprom nur
schwach, und ich wollte es unbedingt benutzen, weil mir die 512
batteriegepufferten Static Ram zu wenig waren.
Ich hab auch ein bischen mit G-Windows rumgespielt, und mit einer Software
namens ControlCalc. Beides hat mir aber am Ende nicht so richtig zugesagt. C
ist
doch das beste. Und fur toll aussehende Benutzerschnittstellen sind PCs mit
Windows besser geeignet, meiner Meinung nach jedenfalls.
Soviel zu mir...
Mich wurd mal interessieren, wie Du das Bord einzusetzen gedenkst?
Jost
There is 1 Reply.

#: 20832 S12/OS9/68000 (OSK)
    09-Mar-95  16:41:36
Sb: #20831-OS9 on the MVME162
Fm: Joachim Terasa 100421,2472
To: Jost Eberbach 73502,2041 (X)
Hallo Jost,
 wie man liest, hab ich keine Probleme mit deutsch, ich hab das Land nur
urlaubsmasig verlassen und lebe jetzt im Landkreis Munchen und bin da
Mitinhaber einer kleinen (aber guten) Firma mit Namen ComIng, Kurzel fur
Computer und Ingenieure, womit gesagt sein soll, das wir uns vor allem
imtechnischen Bereich bewegen. Damit ist OS-9 eins unserer Themen.
 Mir ist hier meine Message-Base voll abgeschmiert, deshalb bin ich mir nicht
ganz sicher, was ich schon gesagt habe. Daher nochmal von vorn:
 OS-9 68k kenne ich seit Version 2.0 und habe bis Version 2.4 ( die
Compilerversionen gehen in die hunderte) das System lieben und Microware hassen
gelernt. Mit Microware hatte ich hier praktisch nichts zu tun, mehr mit Dr.
Keil, dem Exclusivvertreiber. Beispielhafte Systeme waren auf VMEbus-Basis und
lebten mit eigenentwickelter Hardware und entsprechend neuen Devicetreibern und
naturlich angemessener Anwendungssoftware. Glanzstucke waren ein
In-Crcuit-Emulator fur einen Mil-exotenrechner und ein
Hardware-In-the-loop-Integrationssystem fur Sensor-Aktor-Busse in KFZ.
 Unser aktuelles Projekt Projekt bewegt sich im Bereich der
 Fahrzeugverfolgung im Guterverkehr mit GPS usw und der 162er (heute neu
gekriegt!) wir vor allem als Source-Debugging-Plattform dienen. Ich habe ehen
mit Cross-Umgebungen immer5 nur negative Erfahrungen gemacht.
 Target wird ein 68030er System sein mit extrem spezieller Peripherie, aber bei
einem entsprechenden Systemdesign last sich mit OS-9 ja einiges an Komplexitat
nehmen, indem man auf low-level-Systemdienste zuruckgreift (pipes, shared mem),
an die Testbeds locker anklinken konnen.
 Ok, Jost, ich mus mit unserem neuen System erst mal ein paar Erfahrugen
sammeln, daqnn gibts weiteres!
 Wir bleiben in Kontakt!?
 Jochen
  -Joachim Terasa @ 100421,2472 on 09-Mar-1995 23:41:04 CET
   Making software is getting hard, wherever you look.

#: 20834 S12/OS9/68000 (OSK)
    10-Mar-95  19:07:51
Sb: #UUCP/SMTP
Fm: ole hansen 100016,3417
To: sysop (X)
Hello everyone. Does anyone know if UUCP and/or SMTP has been ported to
OS9000/386 ?? Does anyone have SMTP running on OSK ?? Is there another UUCP
available, than the one from TOP-Munic-package ??
regards
ole@danelec.dk
There is 1 Reply.

#: 20835 S12/OS9/68000 (OSK)
    12-Mar-95  05:28:47
Sb: #20834-UUCP/SMTP
Fm: Boisy G. Pitre 74464,3005
To: ole hansen 100016,3417
 > Hello everyone. Does anyone know if UUCP and/or SMTP has been ported to
 > OS9000/386 ?? Does anyone have SMTP running on OSK ?? Is there another
 > UUCP available, than the one from TOP-Munic-package ??
 >
 > regards
 >
 > ole@danelec.dk
 >
Hi there,
There is another UUCP package available here on the OS-9 Forum.  It's
UUCPbb 2.1, and I use it every day.  It works well on my 68340 OS-9
3.0 system, and several people have commented that it is better than
the TOP version.  I worked on the project myself, along with Bob Billson
and a few others.  It is a considerably solid package.  It has not been ported
to OS-9000 *yet* but work on that should be starting soon.
I am not aware of any SMTP clients ported to OS-9000 or OS-9.
Hope this helps.
--
Boisy G. Pitre__    __  __              Delphi:  BOISY
          |_   _|   \ \/ /              CompuServe:  74464,3005
I use...   _| |_     >  <               Internet:  boisy@os9er.waukee.ia.us
          |_____|NFO/_/\_\PRESS 1.2.0   OS-9 -- King of Operating Systems
Press <CR> !>

#: 20849 S12/OS9/68000 (OSK)
    21-Mar-95  08:25:15
Sb: #20835-UUCP/SMTP
Fm: ole hansen 100016,3417
To: Boisy G. Pitre 74464,3005
Hello Boisy
Thanks for the info.. I grapped it and will try it out. The reason for wanting
SMTP on OS-9/OS-9000 is that we today use a UNIX-system to handle mail too, but
UNIX is hard to maintain in good shape..
ole@danelec.dk

#: 20839 S12/OS9/68000 (OSK)
    12-Mar-95  18:23:43
Sb: #CDL Basic demo reupload
Fm: Frank Hogg of FHL 70310,317
To: sysop (X)
Hi,
I re uploaded both 'CBDEMO.AR' and 'CBDEMO.LZH'. The previous upload would not
work 100% with 68000 based cpus. Please replace the original with the current
one.
Sorry for any inconvience this may have caused.
Frank
There is 1 Reply.

#: 20842 S12/OS9/68000 (OSK)
    13-Mar-95  17:32:33
Sb: #20839-CDL Basic demo reupload
Fm: Steve Wegert 76703,4255
To: Frank Hogg of FHL 70310,317 (X)
All taken care of, Frank. Thanks for the uploads!
*- Steve -*

#: 20846 S12/OS9/68000 (OSK)
    17-Mar-95  14:45:49
Sb: #OS9 v3.0 ISP
Fm: Niels Peter Bogholm 100566,2262
To: sysop (X)
Hi everyone !
I'm using OS9 v 3.0 developing client (unix) / (realtime)server (os9)
applications and this (the os9-part) certainly keeps me busy producing
questions, here just a few:
WHY is it not possible to let a connectionrequest signal an event
(_ss_sevent(..) only signals event on data ready). Did you all not always miss
such a function (look at unix-select) cause how can you ever create ONE process
that waits on more events (ethernetcommunication / shm-event/..) at the same
time or with other words:
WHY is the user access to ISP not eventoriented (like TLI - oh by the way when
will
that be implemented !!) so that the user could request the state (ex.
connection-
request arrived, connectiont closed,...)
WHY does the ISP crash when more than ca. 500 connections (499 TIME_WAIT and 1
established). Well I know why (namely 500 connections) but that's bad stuff...
WHY is the internal TCP-process (or is it IP or XY-process) slow. Try this
programstructure for a client:
 while(..){
  sock=socket(type and family)
  bind(localaddress&port);
  connect(to the server);
  write (stuff);
  read (stuffstuff);
  close(sock); /* this must be done after the server so that this endpoint will
be free */
             /* now this endpoint has the state "closed" */
  }
The second bind--call returns EADDRINUSE although the endpointstate is closed!?
WHY did microware not test this package (oh did they..what about all my
questions) or listen(sock, maxrequests) <-this does not work.
If you still reading (I know my WHY's are very specific) I will be apriciated
to hear from you and your experiences with developing realtime and IP-software
with os9. Perhaps we could open a WHY-club (all questions cc:microware) so that
the next os9-version (os9 v 4.0 = os9-95?!) will be a real improvement with
lots of new features..
By the way: How can I get a subscription on PIPELINE.
Thank God for the word WHY and some answers !
Niels Boegholm.
Does anyone have experience with the ISP Package (v 2.0)   
There is 1 Reply.

#: 20847 S12/OS9/68000 (OSK)
    17-Mar-95  23:05:19
Sb: #20846-#OS9 v3.0 ISP
Fm: Pete Lyall 76703,4230
To: Niels Peter Bogholm 100566,2262 (X)
Actually, if you contact Microware, I believe they have a version of the
select() call that you can have as an example. It's been a while since I
os9'ed, but I recall having a similar problem when writing socket based code
under os9/68k.
Pete
There is 1 Reply.

#: 20850 S12/OS9/68000 (OSK)
    21-Mar-95  14:57:43
Sb: #20847-#OS9 v3.0 ISP
Fm: Niels Peter Bogholm 100566,2262
To: Pete Lyall 76703,4230 (X)
Hi Pete !
Thanks for your Info! I'll try to contact MW although I at the moment don't
know how to contact them from my residence in Munich,Germany (- MW's
Inetaddress ?). Anyway the point is how did (do) they realise the select, with
events/signals or by polling (unacceptable cause waste of CPUtime) ?
Niels.
There is 1 Reply.

#: 20851 S12/OS9/68000 (OSK)
    22-Mar-95  12:09:57
Sb: #20850-OS9 v3.0 ISP
Fm: Pete Lyall 76703,4230
To: Niels Peter Bogholm 100566,2262
Niels -
I don't recall - I haven't looked at OS9 in over a year now. I believe
Microware is accessable via the Internet by using username@microware.com.
Start with Kim Kemf (kkemf? Kim.Kemf?) @microware.com.
Pete
Press <CR> !>

#: 20852 S12/OS9/68000 (OSK)
    22-Mar-95  20:09:49
Sb: #20851-OS9 v3.0 ISP
Fm: Boisy G. Pitre 74464,3005
To: Pete Lyall 76703,4230 (X)
Try: info@microware.com
Kim Kempf is no longer with Microware.

#: 20854 S12/OS9/68000 (OSK)
    23-Mar-95  19:53:00
Sb: #20851-#OS9 v3.0 ISP
Fm: Wendell Benedetti 72766,2605
To: Pete Lyall 76703,4230 (X)
Pete,
If you have NOT looked at OS9 in over a year, WHAT are you looking at? :-)
Wendell - I want my SGI.
There is 1 Reply.

#: 20855 S12/OS9/68000 (OSK)
    24-Mar-95  02:52:43
Sb: #20854-OS9 v3.0 ISP
Fm: Pete Lyall 76703,4230
To: Wendell Benedetti 72766,2605 (X)
Well, it was Unix, but now the flavor of the month is Windows NT...
Pete

#: 20858 S12/OS9/68000 (OSK)
    25-Mar-95  04:19:56
Sb: #20851-#OS9 v3.0 ISP
Fm: Niels Peter Bogholm 100566,2262
To: Pete Lyall 76703,4230 (X)
HI Pete,
Thanks for the addresses, I'll try'em ...
I'm just curious, what did you do at your os9-days and why did you drop this
wonderful (hmm) OS-world ?
As you may have noticed, I'm quite new in this forum and wondering if nobody
else are working with network-software on os9 (or are they all satisfied with
MW's TCP/IP implementation - I can't believe that .. )
Well, my cc is finished so I'll go back to work..
Niels, Munich
There is 1 Reply.

#: 20861 S12/OS9/68000 (OSK)
    25-Mar-95  05:35:56
Sb: #20858-OS9 v3.0 ISP
Fm: Pete Lyall 76703,4230
To: Niels Peter Bogholm 100566,2262 (X)
Os9 was fun, but a very small percentage of the world uses it compared to Unix
or Windows... I decided I'd like a regular income, so a portable skill set was
my objective.
MW's TCP/IP implementation left lots to be desired... socket options for one
(grrr....).
Pete

#: 20856 S12/OS9/68000 (OSK)
    24-Mar-95  11:30:38
Sb: #20850-#OS9 v3.0 ISP
Fm: Jost Eberbach 73502,2041
To: Niels Peter Bogholm 100566,2262 (X)
Niels,
you can also try HOTLINE@MICROWARE.COM, thats the main email address for their
technical support group
Jost
There is 1 Reply.

#: 20859 S12/OS9/68000 (OSK)
    25-Mar-95  04:20:03
Sb: #20856-#OS9 v3.0 ISP
Fm: Niels Peter Bogholm 100566,2262
To: Jost Eberbach 73502,2041 (X)
Hi Jost,
thanks for your reply, I'll try that address too.
Are you working with os9 (specially networking) and if yes, what experiences
have you made with the networking-support for os9 ?
Niels.
There is 1 Reply.

#: 20871 S12/OS9/68000 (OSK)
    27-Mar-95  12:45:11
Sb: #20859-OS9 v3.0 ISP
Fm: Jost Eberbach 73502,2041
To: Niels Peter Bogholm 100566,2262 (X)
Hi Niels,
I have very little networking experience with OS-9.
All I ever did is setup the ISP, and I used TCP/IP and TELNET to communicate
with a WindowsNT server and a Windows workstation running Beame&Whitehead
TCP/IP software. All I can say is: it worked!
I never tried socket connections etc., so I can't be be of much help with that.
I don't think there are gonna be many problems with that though.
In general, my opinion about OS-9 is that it has many flaws and weaknesses, but
it's still a good bang for the buck when you use Motorola CPUs. For  Intel CPUs
I would rather use QNX as a lowcost OS. OS9000 is a piece of shit, it doesn't
even boot on many PC's.
Jost

#: 20857 S12/OS9/68000 (OSK)
    25-Mar-95  04:19:26
Sb: #OS-9 Networking
Fm: Niels Peter Bogholm 100566,2262
To: all,
Hi os9-experts,
I (would like to) have a master-server who waits for connectionrequests and
then after reading some info "gives" the socket-fd to a slave-server which will
continue communicating with the client. I can't do dup+close+fork cause the
slave-serves have to be started at boot-time, but I certainly can ask some
questions:
Does anybody know, if there's an "official" way for more processes to share
global(!) filedesc (socketdesc) ? It's easy to get process A's global-fd from
it's local-fd (using F$FindPD and the pathdesc-structure) but how can process B
open a path knowing the global-fd# (well it's possible to open a dummy-path,
get procdesc table with F$GrpDBT and change it - but 1) MW says DON'T and 2) if
internal structures change this wouldn't work..)
Does anybody know, why MW didn't implement a true unix-fork ? From my point of
view it would be quite easy (os9 shares code-segment so it just have to create
a new processdesc and copy the old processes datasegment..) and it certainly
would make it more easy to write portable code.
Thanks for any answers,
Niels, Munich.
There is 1 Reply.

#: 20860 S12/OS9/68000 (OSK)
    25-Mar-95  05:33:23
Sb: #20857-#OS-9 Networking
Fm: Pete Lyall 76703,4230
To: Niels Peter Bogholm 100566,2262 (X)
I have done something very similar to this, but a master server listened and
then spun off child servers to provide client services. Why must you start
everything at boot time?
Pete Lyall
There is 1 Reply.

#: 20866 S12/OS9/68000 (OSK)
    26-Mar-95  06:20:34
Sb: #20860-#OS-9 Networking
Fm: Niels Peter Bogholm 100566,2262
To: Pete Lyall 76703,4230 (X)
Hi Pete,
First some backgroundinfo: My "slave-servers" do manage different VME-Boards
(vacuumcontrol, highvoltage, comm with external robots,..). The slow
communication
(unix-clients or other servers) is realized over network and realtime-comm
between servers on same host with shm. Many servers have a control-loop they
must exec cyclic  (checks pressure, voltage,..).
My solution uses a seperate "network-IO-process" for every server. This waits
for network-actions, does all the communication and then notifies it's server
with events and shm (data). This is fine(usable) for now, but may not be useful
for later projects.
Did your master/slaves share the socket-fd's ?
If yes did you use close,dup,fork (well MW fork isn't a fork (unix!) but a much
slower fork+exec) or did you find a way to share global fd's ?
Do you know if it's  possible to let the system signal an event when a
connectionrequest(!) arrives (cause then one could use ev_wait instead of
accept and this open a hole new world of possibilities..)?
Niels.  
There is 1 Reply.

#: 20882 S12/OS9/68000 (OSK)
    31-Mar-95  09:34:38
Sb: #20866-OS-9 Networking
Fm: Pete Lyall 76703,4230
To: Niels Peter Bogholm 100566,2262 (X)
Niels -
I used the forked approach... In fact I lifted in nearly verbatim from a SCO
unix TCP/IP programming manual (making allowances for OS9's deviation from
Unix, of course).
Re: events - I have used them in over a year, so I can't remember. Try Kevin
Darling - he's still in the thick of that project, I believe.
Pete Lyall

#: 20868 S12/OS9/68000 (OSK)
    26-Mar-95  22:10:31
Sb: New Uploads
Fm: Bob van der Poel 76510,2203
To: all
I have uploaded two small programs to lib 12 in the last few days. The first is
HPSET.LZH. This program lets you set up a HP compatible laser/inkjet printer
using a visual onscreen selector. Comes with source.
CAL.LZH is a complete calendar printing/display program. Lots of
features...inlcuding the ability to print holidays, etc. if you want. This is
shareware--I request a $20.00 donation, however $10.00 of that is refundable if
you buy a commercial product from me. Sounds like a good deal to me <g>.
So, have a look. Comments welcome.
Press <CR> !>

#: 20895 S12/OS9/68000 (OSK)
    09-Apr-95  17:17:11
Sb: #Disk Junked?
Fm: David Breeding 72330,2051
To: all
I just had a file on my HD junked and can't figure out just what's going on.
Last night, I had zipped a bunch of files into one huge one to put onto a PC
disk for a friend.  In the process, I got  it too big for the disk and had to
"zip -d ..." a few.  I then copied the one file to the PC disk.
I cannot remember exactly what all I did last night.. I later came on here with
"ix".  I also may have used an experimental telecom program, too, but don't
think any of this caused it.
Anyway, today, apparently the FD pointer for that file was pointing to a
section (or all) of the file CompuServe.usg, written by "ix".  Dcheck showed
"Bad FD Segment" for stuff in the zip file, and showed that ".usg" was using a
a sector already allocated.
I could not find the true FD for that file.. I finally located a previously zip
file and repointed my FD to that one, but of course none of the sectors were
allocated in the bitmap.  I couldn't delete, deldir or attr -nd that file till
I did that.  (got error 244).   (Oh, somehow, I did get a glitched directory
entry last night, too, but was able to del that file.
I finally just "del"ed that file with the bitmap not set, was not sure what
would happen, but dcheck reported everything OK after that.
I'm just wondering what happened?  I can't remember, but apparently, after
copying the file, I must have deleted it, or the sectors used by the file would
have been still allocated, right?  If this is the case, then somehow when I did
the "del" (if I did), the bitmap was reset but the entry in the directory was
not killed off.  Could it have been some combination of the programs I was
using?  Perhaps somehow the PC driver left a PC-type setup in the system and
when I did del, without doing a specific full path, it got confused?  Could
"zip" have done something?  But the file _did_ copy to the PC disk correctly,
so dunno... it's a real mystery.
                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.3.2  ***
There is 1 Reply.

#: 20900 S12/OS9/68000 (OSK)
    10-Apr-95  19:09:45
Sb: #20895-#Disk Junked?
Fm: Bob van der Poel 76510,2203
To: David Breeding 72330,2051 (X)
When this happens it is usually a good idea to make sure that everything on the
HD is backed up, reformat it, and restore all the data. Could be that you have
a sector acting up.
If you just have one file which you can't read (due to a bad sector, etc) it is
easy to lock out the entire file (including the bad sector) by using DED to set
the first character in the filename in the directory to '0'. That way the file
disappears, but the storage remains allocated...at least that way nothing else
can use it.
There is 1 Reply.

#: 20901 S12/OS9/68000 (OSK)
    10-Apr-95  22:00:51
Sb: #20900-Disk Junked?
Fm: David Breeding 72330,2051
To: Bob van der Poel 76510,2203 (X)
 > When this happens it is usually a good idea to make sure that everything
 > on the HD is backed up, reformat it, and restore all the data. Could be
 > that you have a sector acting up.
around with it today trying to get it to happen on my floppy.  Oh, it happened
again last night. (Make that Sunday, might not u/l this on Mon, when I'm
composing).. I had gone online abt. 10 PM.  Had composed a QWK reply, taking up
two 512-byte sectors + 1 for File Descr.  About 11PM began doing some more
zipping.. I was zipping severaly files, ranging from 40K - 600K (before
compression).  I wound up getting about 1.75 meg in file.. I did "zip -d" for a
few to get it down to fit in 1.44M floppy.  I _think_ a time or two, I had run
dcheck, can't remember exactly what I'd done..  Then I copied the file to a PC
disk.  I then del'ed the zip file.  Then I did dcheck had 3 sectors "not in
bitmap" - traced them to be the QWK reply.  I just "del'ed" that file and
everything was OK.
I don't think I had run dcheck immediately before copying to PC disk, but I'm
sure I had done it at times during the zipping, after my previous observations.
I suspect that somewhere along the way, "zip" walked right over the little
file, probably occupying a sector immediately below that file and then just
going right across it.  I'm beginning to suspect that the trouble might be in
zip with large files.  It writes temp files and it _could_ be it cheats or
something, possibly rewriting to the disk directory structure, but this is just
a guess.
I tried to duplicate the error staying strictly in the floppy, writing small
files and having plenty of fragmentation... Finally did get an error with
beaucoup "not in bitmap".  The only thing is that with my system, our floppies
are dreadfully slow.. Actually, when this error had occurred, I had rewritten a
device descriptor (/f0) and changed the step rate to 3 (6ms) hoping to get it
faster, so this could have been the prob.
 > If you just have one file which you can't read (due to a bad sector, etc)
 > it is easy to lock out the entire file (including the bad sector) by using
 > DED to set the first character in the filename in the directory to '0'.
 > That way the file disappears, but the storage remains allocated...at least
 > that way nothing else can use it.
So far, I've not had unreadable files as such, it's the bitmap that's getting
munged, I think mostly from files writing to the same sector. (The FD gets set
correctly, apparently, but the bitmap is not being followed correctly.
I feel it is either one of my programs (either zip or my PC disk driver) or my
system is writing to the disk when it is not positioned correctly.
                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

#: 20897 S12/OS9/68000 (OSK)
    09-Apr-95  21:42:17
Sb: #Install Intrpt Handler
Fm: Taji S. Abraham 76760,2232
To: all
Hi,
Is there a way to install an interrupt handler without using device
drivers? I am new to OS9. I just want to handle VME interrupts on
a Motorola MV162 board. A short example would be extremely helpful.
I tried the _os9_irq call but it gave me a runtime error (Errno = 208)
Thanks
There is 1 Reply.

#: 20902 S12/OS9/68000 (OSK)
    11-Apr-95  05:28:56
Sb: #20897-Install Intrpt Handler
Fm: Boisy G. Pitre 74464,3005
To: Taji S. Abraham 76760,2232
 > Hi,
 >
 > Is there a way to install an interrupt handler without using device
 > drivers? I am new to OS9. I just want to handle VME interrupts on
 > a Motorola MV162 board. A short example would be extremely helpful.
 > I tried the _os9_irq call but it gave me a runtime error (Errno = 208)
You must be in system state to install an interrupt service routine, but
you don't have to do it inside of a driver.  You have several options:
        - write a dummy driver which just installs an interrupt service
        routine in the INIT routine and deinstalls it in the TERM routine.
        - write a system state application that uses _os9_irq to install
        the interrupt service routine.
        - write a system state trap handler which can be called from a user
        state program.  The trap handler can install the interrupt service
        routine.
I usually opt for the middle suggestion: a system state application.
If you write your interrupt service routine in C, you'll have to write
some glue code in 68K assembly to move contents of registers around.
I don't have any example code on my system, but you need to tell C
compiler that your program is a system state program:
        /* I'm assuming you're using Ultra C because of your _os9_ call */
        _asm("_sysattr: equ $A000");
You then need to write a small assembly language routine which moves
registers and does a bsr to your actual C interrupt service routine.
Be aware that paths are subtly different in system state vs. user state.
Again, sorry.  I'm typing all of this from memory, and don't have example
code in front of me.  Feel free to pass any other questions along.
 >
 > Thanks
 >
--
Boisy G. Pitre__    __  __              Delphi:  BOISY
          |_   _|   \ \/ /              CompuServe:  74464,3005
I use...   _| |_     >  <               Internet:  boisy@os9er.waukee.ia.us
          |_____|NFO/_/\_\PRESS 1.2.0   OS-9 -- King of Operating Systems

#: 20906 S12/OS9/68000 (OSK)
    14-Apr-95  13:30:26
Sb: #20897-Install Intrpt Handler
Fm: Jost Eberbach 73502,2041
To: Taji S. Abraham 76760,2232
Hi Taji!
I have a lot of experience with the MVME162 board. Installing an interrupt
handler without using a device driver is not a problem.
The following programs is an example of how to install a timer interrupt
service routine with C. Some assembler code is required, but I think newer
versions of the Ultra C compiler provide functions that you can use instead of
the Assembler code. The lastest compiler versions even allow using floating
point instructions inside an interrupt service routine. This was always a
problem with the old versions, as the 68040 has some unimplemented floating
point instructions, which were be handled by the trap handler (CSL). The old
trap handler was not 100% reentrant. The new compiler has a new trap handler.
It can also generate code for 68040 by emulating the unimplemented instructions
in software.
If you need more help, send me an email. Maybe I can do some consulting for
you. I have developed code for several Greenspring IP-modules. I also wrote a
utility to use the onboard flash-memory, it allows you to store your
application as well as OS9 in the Flash and boot from flash-memory.
Here is the example code:
#include <stdio.h>
#include <stdlib.h>
#include <module.h>
#include <procid.h>
#include <setsys.h>
#include <errno.h>
#include <memory.h>
#include <sgstat.h>
#include <modes.h>
/* VMEchip2 definitions */
/* This chip is integral to the MVME162 board */
#define   VMEchipBase    0xFFF40000
#ifndef   _UCC
#define   volatile  /* the old compiler doesn't understand 'volatile' */
#endif
#ifdef DEBUG
#define volatile
#endif
typedef volatile struct vmechip {
     u_int SLAVE1;  /* Slave 1 address registers */
     u_int SLAVE2;  /* Slave 2 address registers */
     u_int SLAVE1TR;     /* Slave 1 address translation registers */
     u_int SLAVE2TR;     /* Slave 2 address translation registers */
     u_int SLAVEWPSM;/* Slave write post, snoop, address modifier */
     u_int MASTER1; /* Master 1 address registerS  */
     u_int MASTER2; /* Master 2 address registers  */
     u_int MASTER3; /* Master 3 address registers  */
     u_int MASTER4; /* Master 4 address registers  */
     u_int MASTERTR;     /* Master address translation registers  */
     u_int MASTERAM;     /* Master address modifier registers  */
     u_int GCSRETC; /* GCSR and other control bits   */
     u_int dum0 [7]; /* not defined yet */
     u_int MCNTL;   /* Prescale register */
     u_int T1CMP;   /* Timer 1 compare register */
     u_int T1CNT;   /* Timer 1 counter */
     u_int T2CMP;   /* Timer 2 compare register */
     u_int T2CNT;   /* Timer 2 counter */
     u_int CNTL;         /* Control registers */
     u_int PRESCALER;
     u_int IRQ;          /* Interrupt source register */
     u_int EIRQ;         /* Enable Interrupt register */
     u_int SETIRQ;  /* Software Interrupt register*/
     u_int CIRQ;         /* Clear Interrupt register */
     u_int ILVL1;        /* Interrupt level register 1*/
     u_int ILVL2;        /* Interrupt level register 2*/
     u_int ILVL3;        /* Interrupt level register 3*/
     u_int ILVL4;        /* Interrupt level register 4*/
     u_int VBASE; /* Vector base and I/O Control register*/
} *VMEchip;
#define        VMEChip   ((VMEchip)VMEchipBase)   /* properly casted
constant */
/* For now, I've only provided the register definitions I've needed. */
/* Feel free to add those required, but please keep them in order of */
/* occurrance in the VMEchip.                                         */
/* Remember : only 32bit write operations are supported by the VMEchip2 */
/* Fixed interrupt vector offsets */
#define        VMEVT1         0x68      /* Timer 1 */
#define        VMEVT2         0x69      /* Timer 2 */
#define        SFTW0          0x78      /* Software interrupt 0 */
/*make this program system state */
_asm("_sysattr: equ 0xA001");
volatile unsigned int s_cnt, start_cnt = 0;
VMEchip vmechip = VMEChip;
#define PRIORITY 1
int _f_irq();
int irqsvc_t1();
void cleanup()
{
     register procid *prc = sysglob(procid*, D_Proc);
     prc->_path[0]=0;
     prc->_path[1]=0;
     prc->_path[2]=0;
}
char *term = "/term"; /* default terminal */
int kbhit(){
     int keyboard, hit;
     keyboard = open(term, 0x3);
     if (_gs_rdy(keyboard)==-1) hit = 0;
     else hit = 1;
     close(keyboard);
     return(hit);
}
main()
{
     int i=0;
     char *hwptr = (char *)vmechip;
     char prior = PRIORITY;
     register int error;
     register procid *prc = sysglob(procid*, D_Proc);
     /* fix up standard i/o for a system state process */
     stdin  -> _fd = prc->_path[0];
     stdout -> _fd = prc->_path[1];
     stderr -> _fd = prc->_path[2];
     _from_new(stdin); _from_new(stdout); _from_new(stderr);
     if (error = _f_irq((char)VMEVT1, prior, irqsvc_t1, get_global_base(),
hwptr))
          exit(_errmsg(error, "Can't install timer1 interrupt service
routine.\n"));
     else{
          printf ("Timer1 Interrupt service routine installed!\n");
     }
     /* Setup VMEchip2 to produce timer interrupts */
     /* |= or &= operators cannot be used on the VMEchip */
     /* because the compiler might produce byte-wide write operations */
     vmechip->MCNTL = (vmechip->MCNTL & 0xffffff00L) | 0x000000E7L; /* set
prescaler for 25 MHz */
     vmechip->T1CMP= 1000L;   /* 1 millisecond */
     vmechip->T1CNT= 0L;      /* clear counter */
     vmechip->CNTL = vmechip->CNTL | 0x00000007L; /* enable timer1, reset on
compare */
     vmechip->ILVL1 = (vmechip->ILVL1 & 0xfffffff0L) | 0x00000006L; /* set irq
level */
     vmechip->ILVL3 = (vmechip->ILVL3 & 0xfffffff0L) | 0x00000006L; /* set irq
level */
     vmechip->VBASE = (vmechip->VBASE & 0x007fffffL) | 0x67800000L; /* set irq
base vector, enable interrupts*/
     vmechip->EIRQ = vmechip->EIRQ | 0x01000100L; /* enable timer 1 and
software0 interrupts */
     /* do anything here, e.g. : */
     while (!kbhit()) {
          printf("ticks : %6d\n", ticks);
     }
     vmechip->EIRQ &= 0xfeffffef; /* disable timer 1 and software0 interrupts
*/
     ipic->IP_D_INT0 = 0x00; /* disable IPIC Interrupt */
     ipquad->CG[0].CHCR  = 0x40; /* Interrupt disabled */
     _f_irq((char)VMEVT1, prior, NULL, get_global_base(), hwptr); /*remove
ISR*/
     system ("tmode pause -w=1");
     cleanup();
     exit(0);
}
irq_timer1(char *system_globals, register char *hwptr)
{
     if (!(vmechip->IRQ & 0x01000000L)){ /* is timer1 the interrupter ?*/
          return(-1);                             /* if not :return error */
     }
     vmechip->CIRQ = 0x01000000L; /* clear interrupt */
     ticks++;
     /* do your interrupt service here */
     return(0);
}
_asm("params equ 8");
_asm("irqsv set 0");
_asm("static set 4");
_asm("port set 8");
_asm("_f_irq: link a5,#0");
_asm(" movem.l d1/a0/a2-a3,-(sp)");
_asm(" move.l irqsv+params(a5),a0");
_asm(" move.l static+params(a5),a2");
_asm(" move.l port+params(a5),a3");
_asm(" os9 F$IRQ");
_asm(" bsr.s HandleErr");
_asm(" movem.l (sp)+,d1/a0/a2-a3");
_asm(" unlk a5");
_asm(" rts");
_asm("HandleErr bcs.s HandleErr10");
_asm(" moveq.l #0,d0");
_asm(" rts");
_asm("HandleErr10 ext.l d1");
_asm(" move.l d1,d0");
_asm(" rts");
_asm("irqsvc_t1: move.l a6,-(a7)");
_asm(" move.l a6,d0");
_asm(" movea.l a2,a6");
_asm(" move.l a3,d1");
_asm(" fsave -(a7)");
_asm(" fmove.l fpsr,-(a7)");
_asm(" bsr irq_timer1");
_asm(" fmove.l (a7)+,fpsr");
_asm(" frestore (a7)+");
_asm(" move.l d0,d1");
_asm(" beq.s irq_done");
_asm(" ori.b #01,ccr");
_asm("irq_done movea.l (a7)+,a6");
_asm(" rts");
_asm("get_global_base:");
_asm(" move.l a6,d0");
_asm(" rts");
#ifdef OSK
_asm("mask_irq:");
_asm(" clr.l -(sp)");
_asm(" move.w sr2(sp)");
_asm(" move.w d0,sr");
_asm(" move.l (sp)+,d0");
_asm(" rts");
#endif

#: 20918 S12/OS9/68000 (OSK)
    22-Apr-95  08:14:02
Sb: #Help with VG Machines!
Fm: Jesus Lazaro 100255,504
To: All
Hi,
We are working with VG Machines to do the teletext in Spain. We need to write
the teletext on a PC and import that text into a VG Machine.
Please, help us!
Thanks a million.
Jesus Lazaro
Madrid, Spain.
There is 1 Reply.

#: 20919 S12/OS9/68000 (OSK)
    22-Apr-95  13:07:40
Sb: #20918-#Help with VG Machines!
Fm: Jost Eberbach 73502,2041
To: Jesus Lazaro 100255,504 (X)
what is a VG machine?
There is 1 Reply.

#: 20921 S12/OS9/68000 (OSK)
    24-Apr-95  06:19:41
Sb: #20919-Help with VG Machines!
Fm: Jesus Lazaro 100255,504
To: Jost Eberbach 73502,2041 (X)
The VG Machines are special computers used to write teletext (yo know it, the
text associated to TV signal). These machines use OS-9 and we need to know how
it works (th VG Machines) because we must do several projects about it.
Thanks a million.
Jesus Lazaro
Madrid, Spain
Press <CR> !>

#: 20959 S12/OS9/68000 (OSK)
    15-May-95  22:11:22
Sb: #20897-Install Intrpt Handler
Fm: Jost Eberbach 73502,2041
To: Taji S. Abraham 76760,2232
Taji,
did the code I sent you abouy the ISRs work?
Jost

#: 20932 S12/OS9/68000 (OSK)
    26-Apr-95  20:24:02
Sb: #20921-#Help with VG Machines!
Fm: Jost Eberbach 73502,2041
To: Jesus Lazaro 100255,504 (X)
Jesus,
>> These machines use OS-9 and we need to know how it works<<
Seems you hace real problem here. Have you considered hiring a consultant who
is knowledgable about OS-9? Actually, the people who you bought those machines
from should be able to help you out...
Joey
There is 1 Reply.

#: 20938 S12/OS9/68000 (OSK)
    28-Apr-95  16:40:25
Sb: #20932-Help with VG Machines!
Fm: Jesus Lazaro 100255,504
To: Jost Eberbach 73502,2041 (X)
Jost,
Thanks a million for your help, but... I don't know any expert in OS-9 here in
Spain. Do you know anoybody?
Thanks again.
Jesus Lazaro
Madrid, Spain

#: 20943 S12/OS9/68000 (OSK)
    05-May-95  17:59:12
Sb: Help with VG Machines!
Fm: Jesus Lazaro 100255,504
To: Jost Eberbach 73502,2041 (X)
Jost,
Thanks again for your help. Our Tech Department is working very hard and they
have some solutions, so we hope to do all work in a couple of weeks.
Thanks a million.
Jesus

#: 20923 S12/OS9/68000 (OSK)
    25-Apr-95  06:16:54
Sb: #Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: all
I appear to have a problem with OS-9 alarms 'disappearing'.  After a
successfull call to alm_set() I get no signal returned when the alarm expires.
Also, I have a utility that shows what the system is up to, including a list of
active alarms.  The alarm just set doesn't show up, as if it was never
successfully set.  The function call, however, returns a valid alarm id.
Has anyone else experienced a problem like this?  The same code can work for
10's of iterations, then fail.
I'm using v2.4.4 of OS-9 and Ultra 'C' v1.1.  I've tried old and new-style
function calls, both with the same effect.
Like all itermittent problems, this is proving a real pain.  (It took half a
day to get the system to misbehave while I was monitoring it.)  Any help VERY
welcome.
There is 1 Reply.

#: 20924 S12/OS9/68000 (OSK)
    25-Apr-95  07:47:39
Sb: #20923-#Alarms 'disappearing'
Fm: Joachim Terasa 100421,2472
To: Ian J Shearer 100410,2733 (X)
 >> I appear to have a problem with OS-9 alarms 'disappearing'. <<
 What you are talking about seems to be a similar problem I had 2 years ago
also with OS-9 2.4. In my case it was not an alarm problem rather than a
problem of lost signals.
 My application had to wait for characters from several pipes. So each pipe was
set up with a signal. In some very rare cases it happened that two signals were
generated within a very short time. That means, the second signal appeared
right in the moment when the process was leaving the sleep(0). The mechanism as
shown in the examples that store the signal number in a global variable inside
the signal handler and the evaluates it inside the process was not usable any
more. Do you see something you can use?
 Jochen
  -Joachim Terasa
There are 2 Replies.

#: 20926 S12/OS9/68000 (OSK)
    25-Apr-95  14:50:59
Sb: #20924-#Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: Joachim Terasa 100421,2472 (X)
Thanks for the advice, but I think I'm seeing something different.  Two
reasons; first, the utility that shows what is happening in the system doesn't
recognise that the alarm is ever being set.  Second, I've tried putting a
printf() in the signal handler (not good practice, but really useful for
debugging) and this doesn't see the signal ever arriving.
I'm told that it is impossible for OS-9 to 'drop' a signal.  If one is sent it
is ALWAYS seen by the signal handler.  The only way to loose the information is
by using the normal technique of setting a global variable, then finding that
you've over-written it before it is processed.  This is the problem you saw.
If my reasoning is correct the signal never gets to the process because the
alarm isn't correctly set.  Does this make sense??
Thanks anyway; any more advice gratefully received.
There is 1 Reply.

#: 20927 S12/OS9/68000 (OSK)
    25-Apr-95  20:15:21
Sb: #20926-#Alarms 'disappearing'
Fm: Kevin Darling 76703,4227
To: Ian J Shearer 100410,2733 (X)
Hi Ian,
How about posting a sample of the code you're using to set the alarm and to
process it?  Perhaps someone here will notice something.
best - kev
There is 1 Reply.

#: 20931 S12/OS9/68000 (OSK)
    26-Apr-95  13:40:00
Sb: #20927-Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: Kevin Darling 76703,4227 (X)
Kev
The code is so trivial there's not a lot to say about it; it's shown below.  As
I said initially, it DOES work for many iterations before a failure occurs.
Two functions are shown.  The first sets the timer going, the second is the
signal handler.  The function setTimer() is just a wrapper for the OS-9
function call.  The handler does the usual of setting a global variable and
masking out further signals until this one is dealt with.  (The printf
statement was included when I first saw the problem.)  If you can see anything
wrong with this I'd love to know; it appears to be so simple it's hard to see
where it can fail.
Ian.
/*****************************************************************************/
int setTimer(int i_Event, int i_Time)
/*****************************************************************************
 * Sets an OS-9 alarm going to generate a signal after the specified time.
 *
 *      Inputs: i_Event          signal/event to be generated
 *              i_Time          time interval (in 1/10 of a sec.) before
 *                              signal generated
 *
 *      Returns:        -1              if an error occurs
 *              0               else
 *****************************************************************************/
{
        register int    i = 0;
        int             i_err,
                        i_rval,
                        i_AlarmID;
        /*
         *      Set an OS-9 alarm for the desired signal/time
         */
        if ((i_err = _os_alarm_set(&i_AlarmID, i_Event, ALM_TIME(i_Time))) !=
0)
        {
                err_report(i_err,__LINE__,__FILE__);
                i_rval = -1;
        }
        return i_rval;
}
/*****************************************************************************/
void handler(int i_signo)
/*****************************************************************************
 *OS-9 signal handler.  If the received signal is SIGQUIT, set flag to
 *abort process.
 *
 *      Inputs: i_signo         OS-9 signal received
 *
 *      Returns:        ---
 *
 *****************************************************************************/
{
        switch (i_signo)
        {
                case SIGQUIT:
                        i_ProzessEndeFlag = TRUE;
                        break;
                case SIG_SIMTRACE:
                        i_Trace = TRUE;
                    break;
                default:
                        printf("<<%d>>",i_signo);
                        fflush(NULL);
                        e_Event = (BiteEvent)i_signo;
                        sigmask(TRUE);
                        break;
        }
}

#: 20928 S12/OS9/68000 (OSK)
    26-Apr-95  03:00:48
Sb: #20924-#Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: Joachim Terasa 100421,2472 (X)
Another thought about the situation you describe.  Normally, you would call
sigmask(1) from within the signal handler routine to make sure that signals are
masked out until the next time you reach the sleep(0) statement.  This SHOULD
make sure that if two signals arrive in quick succession the second one doesn't
get lost.  Were you doing this?
There is 1 Reply.

#: 20929 S12/OS9/68000 (OSK)
    26-Apr-95  04:17:50
Sb: #20928-#Alarms 'disappearing'
Fm: Joachim Terasa 100421,2472
To: Ian J Shearer 100410,2733 (X)
I solved the problem exactly this way. But don't be sure that the sleep(0) is
the only sleep in your software. There are several system calls, especially
i/o-services including sleeps implicitly. So it's really not trivial to protect
your sleep/signal-mechanisms from side effects. And it is getting chaotic if
you are not only using sleep/signal but additionally events in one process!
  -Joachim Terasa
There is 1 Reply.

#: 20930 S12/OS9/68000 (OSK)
    26-Apr-95  13:22:30
Sb: #20929-#Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: Joachim Terasa 100421,2472 (X)
I am using events as well.  What has surprised me, is that the problem still
occurs if I reorganise my function calls to make sure that setting an alarm is
the last thing I do before sleeping.  If it wasn't for this I'd believe that
ev_wait() or some such was waking up without the signal being fully processed.
Ian
There is 1 Reply.

#: 20933 S12/OS9/68000 (OSK)
    27-Apr-95  02:39:31
Sb: #20930-#Alarms 'disappearing'
Fm: Joachim Terasa 100421,2472
To: Ian J Shearer 100410,2733 (X)
 >>  If it wasn't for this I'd believe that ev_wait() or some such was waking
up without the signal being fully processed. <<
 Hanging on an _ev_wait() the function will awake with a signal, the signal
will be completely processed. You would have to check if the event condition is
really true after the _ev_wait. Hanging on a sleep() an event will not affect
your program.
 Jochen
  -Joachim Terasa
There is 1 Reply.

#: 20968 S12/OS9/68000 (OSK)
    24-May-95  13:22:10
Sb: #20933-#Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: Joachim Terasa 100421,2472 (X)
If you're interested, I found the cause of my problem.  If you delete an alarm
at the same time as it expires, it is possible to accidentally delete a
completely different alarm from another process.  It goes something like this;
        Task A starts to delete an alarm
        The alarm being deleted expires
        A task/process switch occurs
        Task B creates a new alarm, which uses the old 'slot' of the
          task A alarm
        Task A completes deleting the alarm, but gets the new alarm
          from task B by mistake
This is something to do with OS-9 marking an alarm 'slot' as free before it
truely is.  Version 3.0 gives a partial solution, since you can prevent a task
from deleting alarms  with other owner IDs; if you spawned all the tasks from
one parent, as I did, this won't help.
The workaround is to use periodic (repeating) alarms, then kill them in
response to the first signal they generate.  In other words, the ONLY safe way
to use alarms is to avoid single-shot alarms like the plague.  Disappointing
but true.
There are 2 Replies.

#: 20970 S12/OS9/68000 (OSK)
    26-May-95  02:28:54
Sb: #20968-Alarms 'disappearing'
Fm: Joachim Terasa 100421,2472
To: Ian J Shearer 100410,2733 (X)
 >>  In other words, the ONLY safe way to use alarms is to avoid single-shot
alarms like the plague. <<
 Thanks very much for this info. I'll keep it in mind!
  -Joachim Terasa

#: 20976 S12/OS9/68000 (OSK)
    31-May-95  17:24:34
Sb: #20968-Alarms 'disappearing'
Fm: Joerg Hofstetter 100112,2561
To: Ian J Shearer 100410,2733
I made the same experience with OS-9 alarms: Single-Shot alarms are sometimes
disappearing. I always use alm_cycle().
It's great that you found an explanation. Thank you.
I hope Microware is also reading .....

#: 20944 S12/OS9/68000 (OSK)
    08-May-95  15:59:45
Sb: #HP Jet Direct Net-Interf
Fm: Alptekin Aydogan 100527,324
To: all
Who has experience with HP Jet Direct EX Network Interface for printers ? I'm
using OS9 Ver. 2.4 with TCP-IP + NFS and would like to connect my
OS9-developing system to  a HP Deskjet-Printer which has this interface.
There is 1 Reply.

#: 20955 S12/OS9/68000 (OSK)
    13-May-95  13:54:20
Sb: #20944-HP Jet Direct Net-Interf
Fm: Joachim Terasa 100421,2472
To: Alptekin Aydogan 100527,324 (X)
Hi,
 >> Who has experience with HP Jet Direct EX Network Interface for printers ?
<<
 Would also be helpfully for me! If you've found a solution - let me know.
Because it is a thin based on TCP/IP-sockets it may be portable. I will also
keep my eyes open!
 Jochen
  -Joachim Terasa

#: 20947 S12/OS9/68000 (OSK)
    11-May-95  18:24:45
Sb: #How to link I2C to OS-9
Fm: Martin Kreutzer 100020,2550
To: all
I have to port an OS-9 to a target system that has some devices
on a I2C-Bus (driven by a PCF8584).
Now I wonder what`s the "OS-9-like" way to link I2C to the System.
 I2C has commands like "write 2 bytes, then read 5 bytes answer"
 I see three ways to handle this:
 1) leave the I/O System alone and make a system-state module to
    handle I2C.
 2) use the I/O System. Delay write requests until I get the
    corresponding read request. I see some problems to keep
    the whole procedure atomic. Furthermore I think
    I have to write a new filemanager, because I need the sizes
    of the I/O requests in the device drivers.
 3) use the I/O System but handle the requests in SetStat calls.
    If I handle pure reads and writes with SetStats too, I can
    connect the device driver to a standard Filemanager (e.g. SCF).
 Right now I prefer Version 3 but I`m open to suggestions.
 Please give me your opinion..
Martin Kreutzer
There are 3 Replies.

#: 20948 S12/OS9/68000 (OSK)
    11-May-95  19:58:35
Sb: #20947-How to link I2C to OS-9
Fm: Jost Eberbach 73502,2041
To: Martin Kreutzer 100020,2550 (X)
Martin,
If I were to do that, I would definitely prefer version 1, >>leave the I/O
System alone and make a system-state module to handle I2C.<<
If you do it yourself, you can at least be sure, that OS-9 doesn't mess with
your data! It also seems to be the simplest methods. Of course, the other
versions are more challenging...
I have broken my head over OS-9 too much I guess, I really try not to use it at
all if possible. I do all my hardware related stuff in system state modules
and/or ISRs, I don't bother to try and write an OS-9 driver etc.
Just my opinion...
Jost

#: 20949 S12/OS9/68000 (OSK)
    12-May-95  01:38:19
Sb: #20947-How to link I2C to OS-9
Fm: Joachim Terasa 100421,2472
To: Martin Kreutzer 100020,2550 (X)
 >>  Please give me your opinion.. <<
 I also prefer version 3, especially if you don't have to develop a device
driver from the scratch, but just have to modify something existing. If you are
not experienced in writing OS-9 device drivers version 1 would be the better
way.
 Jochen
  -Joachim Terasa

#: 20953 S12/OS9/68000 (OSK)
    12-May-95  21:40:36
Sb: #20947-How to link I2C to OS-9
Fm: Bob van der Poel 76510,2203
To: Martin Kreutzer 100020,2550 (X)
You might want to contact Kevin Darling on this forum...I believe he wrote (or
started to write???) a driver for the i2c chip on the mm/1. Kevin?

#: 20964 S12/OS9/68000 (OSK)
    18-May-95  13:23:34
Sb: #buffers
Fm: LARRY OLSON 72227,3467
To: Kevin Darling 76703,4227 (X)
Kevin,
   I have a question about Kwindows get/put buffers, that I hope you could
help me with.
   It concerns allocating memory for the get/put buffers.
   How do I allocate memory for an entire GROUP.
   I know of the  1B 29 GRP BUF HCT LCT , function, but I have about 50
separate object buffers under 1 group(P_ID) number. These buffers vary in size
from 3 x 3 to 15 x 10.  Do I need to define each one, or is there a way to
allocate memory for the entire GROUP ? Does the function work like KILBUF, where using 0 for the buffer number applies to all buffers in
the GROUP ?
   I thought of splitting some of the buffers off into another GROUP, like
(P_ID + 1) but wouldn't you then run the risk of hitting the GROUP number of
another process
   I hope you can set me straight,
   Larry
There is 1 Reply.

#: 20971 S12/OS9/68000 (OSK)
    28-May-95  13:17:42
Sb: #20964-#buffers
Fm: Kevin Darling 76703,4227
To: LARRY OLSON 72227,3467 (X)
Hi Larry,
Unfortunately, there isn't a way to allocate memory for a group of buffers
ahead of time.  The internal system has to know where each "object" will begin
so it can make better decisions about storing it.
If you run out of buffers, some people use P_ID+128, although that may not be
safe on everyone's system.
best - kev
There is 1 Reply.

#: 20975 S12/OS9/68000 (OSK)
    31-May-95  12:47:48
Sb: #20971-buffers
Fm: LARRY OLSON 72227,3467
To: Kevin Darling 76703,4227 (X)
 > Unfortunately, there isn't a way to allocate memory for a group of
 > buffers ahead of time.  The internal system has to know where each
 > "object" will begin so it can make better decisions about storing it.
 >
 > If you run out of buffers, some people use P_ID+128, although that may not
 > be safe on everyone's system.
   Kevin,
       Thanks, I'll keep that P_id + 128 in mind. What brought the question
up was as usual, another dumb mistake of mine. I kept getting the error
message - can't allocate memory -, when I was trying to run this program and
I thought the problem was in allocating memory for the GET/PUT buffers. I had
forgotten that I had changed another part of the program, that was loading a
sound file. Well now the sound file wasn't where the program thought it was
and that was where the program kicked out the -can't allocate memory- error.
  Ok, I'll get back to playing with these GET/PUT buffers again, I havn't
got it figured out completely yet but the GET appears to be sensitive about
where the object is on the screen, because some objects when they are later
put to the screen, the rightmost pixels of the object are missing. I thought
I had it figured out by drawing the objects so that they fall on the 8 bit
boundries, and for some of the objects this worked, but not for all.
   Thanks again Kevin
   larry

#: 20973 S12/OS9/68000 (OSK)
    30-May-95  13:22:57
Sb: #Alarms 'disappearing'
Fm: Paul N. Leonard 72477,774
To:  100421,2472 (X)
   I just now saw your messages about disapearing alarms.  It is true  that
   you  can unintentionally delete an alarm but it is definitely avoidable.
   Rather than use the sequence sited in your  messages  use  the  sequence
   shown  below  and  you won't have any problems.  You must be consistent,
   however, because if you do it incorrectly in one  place,  you  are  back
   where you started.
      For each alarm that is created set a unique flag to  indicate  it  is
      active.
      When the alarm handler receives that alarm it clears the proper  flag
      to indicate the alarm has fired.
      When it comes time to delete an alarm set the signal mask to  prevent
      alarms from firing.
      Check the status of the flag.
        If it is still set, then it has not fired and you can safely delete
        the alarm and clear the flag.
        If it is clear, then there is no need to clear the  alarm  or  flag
        because it has already fired.
      Clear the signal mask so signals can be received again.
   We are using this scheme on our product which can have up  to  24  tasks
   running at one time of which 10 are creating and deleting alarms a great
   deal of the time.  We had the same problem until we came  up  with  this
   solution and it hasn't been a problem since.
   Hope this helps.
   Paul N. Leonard
There is 1 Reply.

#: 20974 S12/OS9/68000 (OSK)
    30-May-95  14:10:52
Sb: #20973-Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: Paul N. Leonard 72477,774 (X)
Paul,
Thanks for the tip; I see how it works.  What you're doing is basically
compensating for a weakness in OS-9; have you any idea why there is no internal
mechanism for preventing the problem?  Microware are obviously aware of the
difficulty.  Unfortunately the 'fix' in Version 3.0 is of very limited value.
Ian
Press <CR> !>

#: 20978 S12/OS9/68000 (OSK)
    02-Jun-95  17:21:39
Sb: #20849-UUCP/SMTP
Fm: M. Raabe 100327,1526
To: ole hansen 100016,3417 (X)
Hi ole,
what did I miss?
Are you having a solution for my problem?
I'm using the TOP-UUCP to connect a OS-9 based EMail Net company-wide
(>20  68020/30/40 based computers). There are (unfortunately) PC-users
who want to be connected to the UUCP-EMail from their MHS / Novel / TCP/IP /
...
worlds.
I'd love to hear from you.
TIA Martin Raabe (mraabe@mrehome.eltec.de)

#: 20977 S12/OS9/68000 (OSK)
    02-Jun-95  17:10:12
Sb: #20850-OS9 v3.0 ISP
Fm: M. Raabe 100327,1526
To: Niels Peter Bogholm 100566,2262 (X)
Hallo Niels,
in Deutschland gibt es mehrere Hersteller guter TCP/IP stacks.
Fur welche Plattform wird es denn benotigt?
Ich arbeite bei einem VMEbus-board Hersteller.
Wir haben das MW-ISP 2.0 und OS9TCP 2.0 von ASS im Programm, um Probleme wie
die Ihren in den Griff zu bekommen. Man kann halt nicht alles (von MW) haben!
Ciao Martin Raabe

#: 21004 S12/OS9/68000 (OSK)
    18-Jun-95  20:07:52
Sb: #20955-HP Jet Direct Net-Interf
Fm: Mike Haaland 72300,1433
To: Joachim Terasa 100421,2472 (X)
The OS-9 to HP-Jet Direct card is one I'm dealing with also.  Our problem is no
real
way to 'spool' the files on the OS-9 side.  Without a spooler I'm seeing
printjobs
disappearing.  I've got an Idea that just might work, (the spl package from
here
printing to a socket instead of a device or pipe), but havn't had a chance to
play
with it yet.
I'll let you all know if it works,
 - Mike -

#: 20980 S12/OS9/68000 (OSK)
    02-Jun-95  17:22:03
Sb: #20974-#Alarms 'disappearing'
Fm: M. Raabe 100327,1526
To: Ian J Shearer 100410,2733 (X)
Hi Ian,
as far as I know the fix of OS-9 V3.0.1 should be ok, isn't it?
Ciao Martin Raabe
mraabe@mrehome.eltec.de
There is 1 Reply.

#: 20983 S12/OS9/68000 (OSK)
    08-Jun-95  11:17:04
Sb: #20980-Alarms 'disappearing'
Fm: Ian J Shearer 100410,2733
To: M. Raabe 100327,1526 (X)
Martin,
Not really.  All the 'fix' does is to prevent a task from deleting alarms
sourced by a different user ID.  If you have several tasks spawned by the same
parent this provides no protection at all.
Ian

#: 20982 S12/OS9/68000 (OSK)
    06-Jun-95  14:14:28
Sb: Consulting in NYC area
Fm: Michael A. Cohen 73304,3026
To: All,
***URGENT/IMMEDIATE NEED***
Spectrum Concepts Consulting Corp., an information technology consulting firm
providing leading-edge consulting expertise to the NYC area since 1979, is
looking for an OS-9 Specialist to work ON-SITE at one of our most prestigious
clients in the NYC area.  The contract is immediate and at least one year
length.
Skills Required:
* OS-9 Expertise
Skills Desired:
*  C Programming
*  CD-i
*  David
*  Interactive TV
The project involves designing and developing the software component for an
interactive TV hardware box based on OS-9.
For More Details please contact:
Michael Cohen, Technical Recruiter
Spectrum Concepts Consulting Corp.
150 Broadway, Suite 600, New York, NY  10038
phone (212)791-4800 x248
fax resumes to (212)791-6639
***Referral Fees Paid . . . Refer your friends/associates!!!**

#: 21016 S12/OS9/68000 (OSK)
    22-Jun-95  20:06:47
Sb: #OS-9000 help
Fm: John R. Wainwright 72517,676
To: All
OK, OS-9000 users.  New Guy here.  A few questions.
OS-9000 us up and running on my "486DX4/100", and I am slowly getting it to
obey.  I have some OS-9 experience, COCO I,II,III and OS-9/68000 on my MM/1a,
so I am not completely lost, but there are a couple little things I still can't
get to work.
1. Comm ports.  I can use T1 and T2.  Even had STERM talking to CIS when I had
the (internal) modem on T2 (COM2).  Then I moved the modem to T4 (COM4).  T2 is
now a simple serial port.  T2 still works, I can plug it into an external modem
or null-modem to the MM/1, but I cannot get OS-9000 to talk to T4.  Messydos &
Windoze and even OS/2 can find that modem, but OS-9000 cannot.  COM2 and COM4
are BOTH using IRQ3, but I am not trying to use them at the same time.
2. Printer.  I am using LPT1.  The address of the port seems right accord to
the BIOS and the information with the OS-9000 system. It even makes the lights
blink and puts the Deskjet through its INIT routine when I load and init
p.lpt1.  When I try to print something, the lights blink on the printer and the
system hangs. LPT1 works fine with the other operating systems, of course.
Current method of printing from OS-9000 is to pass it via null modem to the
MM/1.
3. Disk formats.  No big deal here, but I sure can't get the MM/1 and the
OS-9000 system to agree on what a "universal disk" is.  I CAN get them both to
read and write on a High density messydos disk, so I use that for transfers.
4. Graphics.  Anything available to get OS-9000 to speak to the Trident 94xx
VGA card in this beast?  I need a CGFX_VGA.L  lib (grin).
Suggestions welcome.
John Wainwright (johnreed@delphi.com   72517.676@compuserve.com)
There are 2 Replies.

#: 21017 S12/OS9/68000 (OSK)
    23-Jun-95  08:57:01
Sb: #21016-#OS-9000 help
Fm: Pete Lyall 76703,4230
To: John R. Wainwright 72517,676 (X)
John -
Well, I don't know if this helps any, but usually COM3 and COM4 share
interrupts with COM1 and COM2 (IRQ 4 and IRQ 3 respectively). That's where I
would start looking.
Pete
There is 1 Reply.

#: 21018 S12/OS9/68000 (OSK)
    24-Jun-95  13:22:18
Sb: #21017-OS-9000 help
Fm: John R. Wainwright 72517,676
To: Pete Lyall 76703,4230 (X)
 > John -
 >
 > Well, I don't know if this helps any,
 > but usually COM3 and COM4 share
 > interrupts with COM1 and COM2 (IRQ 4
 > and IRQ 3 respectively). That's where I
 > would start looking.
 >
 > Pete
 >
 Yeah, COM2 and COM4 are both using IRQ3.  BUT -- I don't try to use them at
the same time.  In fact, with OS-9000, I only load one of the device
descriptors.  Messydos and OS/2 on the same box let me get away with that.  I
hate to start playing IRQ-Roulette on the 486 - everything you fix breaks
something else.
 Thanks,
 John

#: 21020 S12/OS9/68000 (OSK)
    25-Jun-95  05:10:37
Sb: #21016-#OS-9000 help
Fm: Ed Gresick 76576,3312
To: John R. Wainwright 72517,676 (X)
 John,
 Congratulations on getting OS9000 up and running.  Which version are you
 running?  Using the release sold at the CocoFest in Chicago a few years ago
 *may* account for some of your problems.  As I recollect, there were many
 bugs in it.  The latest version is 1.3. - much smoother.  I think its worth
 spending $200 per year for the support contract.  In addition to hotline
 support, you should be able to get the latest version of OS9000 as part of
 the package.  The people at MW say version 2.0 should be released in the
 next couple of months.
 > 1. Comm ports.  I can use T1 and T2.  Even had STERM talking to CIS when I
 > had the (internal) modem on T2 (COM2).  Then I moved the modem to T4
 > (COM4).  T2 is now a simple serial port.  T2 still works, I can plug it
 > into an external modem or null-modem to the MM/1, but I cannot get OS-9000
 > to talk to T4.  Messydos & Windoze and even OS/2 can find that modem, but
 > OS-9000 cannot.  COM2 and COM4 are BOTH using IRQ3, but I am not trying to
 > use them at the same time.
 If MSDOS, etc. can find and speak to the modem correctly, its safe to say you
 have the card configured correctly.  Check the data for the descriptor to
 be sure it matches your modem configuration.  This information is stored
 in '/dd/PORTS/PCAT/systype.h'.  Use '/dd/PORTS/PCAT/mk.scfdesc' to make a
 new descriptor.  BTW, I use an internal modem on t3 - no problems.
 > 2. Printer.  I am using LPT1.  The address of the port seems right
 > accord to the BIOS and the information with the OS-9000 system.
 > It even makes the lights blink and puts the Deskjet through its
 > INIT routine when I load and init p.lpt1.  When I try to print
 > something, the lights blink on the printer and the system hangs.
 > LPT1 works fine with the other operating systems, of course.
 > Current method of printing from OS-9000 is to pass it via null
 > modem to the MM/1.
 Don't have any suggestions for this one.  I've had no problems.  Currently,
 I'm using either an old OKI 192 or a HP 4+.  Both work fine.  You might
 try calling MW's hotline.
 > 3. Disk formats.  No big deal here, but I sure can't get the MM/1
 > and the OS-9000 system to agree on what a "universal disk" is.  I
 > CAN get them both to read and write on a High density messydos
 > disk, so I use that for transfers.
 OS-9/68000 and OS9000 'universal formats' are not the same.  If I remember
 correctly, the main difference is where the FAT is placed.  Using 'os9copy'
 or 'os9dsave' located in the '/dd/CMDS/UNSUPPORTED' directory, you should
 be able to read OS-9/68000 universal format disks.  Otherwise, you're doing
 what most of us are doing - transferring via MSDOS disks or via the serial
 port.
 > 4. Graphics.  Anything available to get OS-9000 to speak to the
 > Trident 94xx VGA card in this beast?  I need a CGFX_VGA.L  lib
 > (grin).
 Well, I have G-WINDOWS for OS9000.  Have 2 drivers that should work with your
 card'.  These are generic drivers giving a resolution of 640x480x16.  I have
 additional drivers for specific cards (the Trident isn't included) providing
 resolutions up to 1200x1024x256.  With the  optional Developer's Pak, you
 have what you need to write software for gfx using G-WINDOWS.  Alternatively,
 you can purchase RAVE.  I don't think there is a driver for the Trident cards,
 but a skeleton driver is included you can fill in to make your own driver.
 Ed
There is 1 Reply.

#: 21021 S12/OS9/68000 (OSK)
    25-Jun-95  21:56:26
Sb: #21020-#OS-9000 help
Fm: John R. Wainwright 72517,676
To: Ed Gresick 76576,3312 (X)
Ed,
 Thanks for the advice on the serial and printer ports.
Mine is the system that was sold at that Chicago Fest - I bought it from
another user.
 (Update) - I have managed to get both /T2 and /T4 drivers working, had to
remove all serial ports from the boot, and load ONLY the one I plan to use.  To
use the other one, I must reboot (sometimes twice) and start over.  DEINIZ and
UNLINK don't seem to remove enough of one to let the other work.
 Printer - I am beginning to suspect my cables.  When I put the "accelerator"
68340 board in the MM/1, I discovered that I had to switch to short shielded
cables for the printer - something kinda marginal in the timing with the faster
system. Maybe a similar problem (486 has a ribbon cable on the printer port).
 GWINDOWS sounds attractive.  I couldn't quite convince myself to buy it when
you made the offer for an MM/1 port, but the MM/1 already has graphics, the 486
with OS-9000 does not.
I am presently in "Father of the Bride" mode - not a lot of extra bucks for a
couple months, but I should recover by Fall.
Thanks again for the help. John Wainwright
There are 2 Replies.

#: 21031 S12/OS9/68000 (OSK)
    28-Jun-95  05:22:59
Sb: #21021-OS-9000 help
Fm: Ed Gresick 76576,3312
To: John R. Wainwright 72517,676 (X)
 John,
 I had forgotten some of the problems I had when I went to a 'fast' 486.
 Originially, I used 25 and 33 MHz machines and didn't have any problems
 running OS9000 attributable to hardware.  When I went to my current hardware,
 a DX-2/66, I did have many problems.  (Unfortunately, I didn't document them.)
 MW suggested I remove all caching.  I did this and things worked properly.
 Started adding caching until problems cropped up.  Turned out I couldn't
 enable 'External Cache Memory'.  BOIS is AMI.  Since you're running at 100
 MHz, you may have a similar problem.
 > (Update) - I have managed to get both /T2 and /T4 drivers working, had to
 > remove all serial ports from the boot, and load ONLY the one I plan to use.
 > To use the other one, I must reboot (sometimes twice) and start over.
 > DEINIZ and UNLINK don't seem to remove enough of one to let the other work.
 I have t1 and t2 in my boot file and load t3 in the startup file.  I use
 t1 for a terminal, t2 is my mouse and t3 my internal modem.  I've had no
 conflicts between t1 and t3.  I haven't tried running a modem from t1, but
 I have run the modem (t3) from a terminal on t1.  I don't remember if I had
 problems putting t3 in the boot or I just didn't get around to making a new
 boot.
 I don't remember whether earlier version of OS9000 included them but version
 1.3 includes descriptors and a driver for the DigiTech Serial card.  These
 are in the PORTS/PC8 directory.  They use the higher irqs available on
 16 bit buses.  I haven't tried them yet, but it seems they may work as
 written or with a minor modification with modem cards that permit accessing
 these irqs.
 > Printer - I am beginning to suspect my cables.  When I put the "accelerator"
 > 68340 board in the MM/1, I discovered that I had to switch to short shielded
 > cables for the printer - something kinda marginal in the timing with the
 > faster system. Maybe a similar problem (486 has a ribbon cable on the
printer
 > port).
 Well, maybe.  But I think you said the printer worked properly under DOS and
 WINDOWS.  This suggests that the hardware is OK.  I'd suspect either the
 hardware's caching or the 'pcpll' driver.  I don't remember if I had problems
 with the earlier version of OS9000 but I don't with 1.3.  I go through about
 15 feet of cable and 2 printer switches (definitely not recommended).
 Several GFX programs I wrote work OK as does 'PSF'.  You mentioned (re
 serial ports) you had to remove the serial ports from the boot and load them.
 I load 'lpt2' and 'pcpll' from the startup file.  Don't remember why.
 (Sometimes I do things the 'easiest' way and don't get around to doing them
 'properly'.)
 > I am presently in "Father of the Bride" mode - not a lot of extra bucks for
 > a couple months, but I should recover by Fall.
 Congratulations!  Didn't you know in this mode you are supposed to have
 bottomless pockets <g>?  E-mail me your mailing address and I'll send you
 a demo copy of G-WINDOWS.
 Ed Gresick - DELMAR CO

#: 21035 S12/OS9/68000 (OSK)
    28-Jun-95  21:51:52
Sb: #21021-OS-9000 help
Fm: David Breeding 72330,2051
To: John R. Wainwright 72517,676 (X)
 > GWINDOWS sounds attractive.  I couldn't quite convince myself to buy it
 > when you made the offer for an MM/1 port, but the MM/1 already has
 > graphics, the 486 with OS-9000 does not.
John, I would like to put in a plug for GWINDOWS.  I got it with my system when
I bought it from Ed.  I am totally impressed.  It has features that I still
cannot believe.  Of course, with everything, I can compose a little wish list
for it, but basically, I don't think I could live without it now.
It did take me a little time to get over the jet lag from coming over from the
coco.  I liked a lot of its features.  Not being able to just jump from one
screen to another took a little getting used to, but now, everything seems
quite natural.
One small feature that I am really endeared to is its cut and copy feature. It
seems to have 1000 uses.  One thing I have done with it, although my need for
it is my fault, is that I have dialed up a BBS which uses hard-to-remember
passwords.  Rather than use file transfers or whatnot, I can just list it to a
screen, cut, and double-click on the telecom window and transmit it that way.
You can even send a small file this way.  I know this particular usage is not
necessary, as there are other ways, but I just use this to demonstrate what
_can_ be done.
When you can see your way clear, I would definitely go for it.
                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

#: 21022 S12/OS9/68000 (OSK)
    25-Jun-95  22:34:37
Sb: MM/1 System for Sale
Fm: Ernest Withers Jr. 71545,1117
To: ALL
For Sale:       Complete MM/1 System, S/N 120848 with IMS manuals
        Includes:       IMS Slimline case & power supply
                        I/O board
                        OS-9/68000 v2.4 with Microware manuals
                        3 megabytes RAM
                        4 serial ports (/t0, /t1, /t2, & /t3)
                        2 parallel ports (/p & /p1)
                        2 1.4MB floppy drives
                        105 MB Quantum hard drive
                        101 key XT/AT switchable keyboard
                        Logitech 3 button Series 9 serial mouse
                        Magnavox 8CM515 color monitor
                        MM/1 Technical Manual
        Software:               FHL's FBU & FRS backup/restore software
        (Includes original      FHL's DynaStar & DynaForm for 68000
          disk & manual)        BGFX
                                Fontasee font editor
                                WriteRight word processor
                                Speedisk disk defragmenter
                                Ved, Vprint, & Vmail
                                EthaGUI
                                Desktop
                                TasCOM
                                ColorSystems Game Pack
                                Lots of public domain software
Asking $700.00 for the complete system. I will bring this system to the Atlanta
'Fest if anyone is seriously interested.
If interested, leave E-Mail.
Ernest Withers   CIS: 71545,1117      Delphi: ERNIEWITHERS
Press <CR> !>

#: 21055 S12/OS9/68000 (OSK)
    16-Jul-95  13:03:07
Sb: #I'm up on Cumana OSK! :)
Fm: PaulSeniura 76476,464
To: all
Hello, I'm back!  :)  I'm up on OSK v2.3 for Atari STs by Cumana (U.K.) and
Reccoware (Germany)!
My ST hardware itself was upgraded long ago to match a Mega-4 model (16MHz with
instruction cache that can't be turned off, 4meg RAM, ICD's SCSI host adaptor,
etc.).
I wired up a switchable dual flip-flop chip to double the serial port speed --
when it's 'on', it's locked at 38400 bps.
I have a USRobotics 28800 Courier modem with its latest Flash ROM updates (that
I can find).  Yesterday I tested OSK with CompuServe's 14400 dial-up lines here
in Okla. City.  I'm using STerm v1.5.1 with RZ & SZ v3.24, /T1 port set with
type=80 to do RTS/CTS handshaking, my TERM environment variable is set to
'st48' or 'st50' (I love the 80x50 monochrome video mode), I told CompuServe's
host I have a VT52.  Everything is cooking & working fine!
Had to patch /TERM, it has a keyboard translate table hard-coded in the
descriptor's extended area.  Cumana provides 'english' and 'german' /TERM
descriptors & sources, neither one matches my 'u.s.a.' keyboard completely.
There were *no* docs supplied on how this table works, but I studied it &
guessed it was in Atari key-scan-code order.
After I figured out what to zap where in /TERM, I used FIXMOD to get its
Revision upped & checksum corrected so I can LOAD my new version.  The STCon
(ST Console) driver would not use my new copy after I LOADed it, altho it did
get loaded as proved by MDir, so I ended up having to patch OS9Boot directly:
Easiest way was to use BEAV, Binary Editor And Viewer, I found on CompuServe.
I patched the actual /TERM module which was merged into OS9Boot directly,
complete with proper checksums etc.
We're missing some of the tools we have with the CoCo3 Level 2 system such as
EZGen (I bought a legal copy of it some time back) which would make these kinds
of patches much easier to accomplish.
I still have lots to do to get the MAKE stuff working properly, or I would've
simply compiled a new 'term.usa' module, Cumana/Reccoware does provide enough
source code to do this BUT WITH NO DOCS or Comments!  So this patch approach
was probably the only way for me to get the keys fixed at this time.
Now I can type a shift-2 and get an '@' sign as it shows on my keys, rather
than the U.K.'s '"' double-quote.  Several other keys were different, too.  I
can provide complete details how to do the "fix" if needed.
Last year, Reccoware mailed me updates to their STHD (ST SCSI Hard Disk) driver
and other things (PTY & VTerm etc.).  I removed the Seagate ST277N drive that
was "sleeping" on me, if y'all remember. Started using and dedicated a whole
CDC (Seagate) 96meg WORM3 unit for OSK.  It's wired in at SCSI ID0 LUN0.  It's
been partitioned with ICD's latest formatter which can produce AHDI-compatible
part'n tables.  I made a small /H0 boot part'n (5meg) and 3 27meg part'ns (/H1,
/H2, & /H3).  My /DD points to /H3, where I'll have my SYS & C libs etc.  I
think I left an unused cylinder in-between each part'n just in case of bugs if
it runs out of room (seems to happen with any h.d. driver for Ataris!).  Each
part'n needs to be Type 'OS9' (not 'GEM' or 'BGM' or whatever) for Reccoware's
drivers to find 'em.
The Atari OSK booter can find OS9Boot on /H0 just fine!  (I still have to use a
copy of their 3.5" floppy to kick things off; I don't have the ST auto-boot ROM
cartridge Cumana sells.)  But, as it is now, this is perfect anyway: I can pick
what to boot, TOS/GEM/ICD or OSK, and they'll come up in less than 30 seconds.
;)  (Take THAT, OS/two and MSWindoz, put it in your pipe to smoke!!)
I'm still using my (other) Seagate 1-gig drive at SCSI ID0 LUN2 for standard ST
stuff, which TOS/GEM can find automatically.  This second drive has the "first"
GEM partition on it which becomes Drive C:, and TOS 1.04's own booter can find
& load ICDBOOT.SYS and the AUTO folder & ACCs just fine.
(Use even-numbered LUNs for all your drives to get around an older ICD host
adaptor card bug.)
No matter which way I boot, I'll leave Cumana's OSK boot diskette in Drive A:
(not their GEM diskette, but the actual OSK System Master diskette).  TOS & ICD
can find C: no matter what is in the floppy drives.  Once I boot up TOS/GEM,
all I have to do to boot up OSK is double-click on any copy of BOOTFOSK.PRG.
For completely automatic OSK boots, I _could_ put BOOTFOSK.PRG in my AUTO
folder, too.  This way, OSK should come up even if the power goes out & back
on.  Really!  :)
I need some help, tho.  Firstly, (this may be a FAQ but I couldn't find the
answer), some OSK software I've downloaded says it can't install a traphandler
due to my version of CIO, or something like that.  I've also tried downloading
& installing the Ultra-C stuff e.g. 'LOAD CSL FPU' then 'P2INIT FPU' as the
docs say, and I still get the traphandler CIO mismatch problem.  I'd love to
install SCREEN & its PTY stuff so I can have cheap multiple shell tasks on my
screen (in lieu of MGR or G- or K-Windows), but SCREEN is one that gripes about
my CIO.  SPACE and VUE also gripe.
Secondly, I'm back harping again on how I could get one of those GUIs for my
OSK/ST.  I didn't get much help last time I asked. Reccoware wants close to
US$800 for the MGR run-time and Development pkgs, yes I'll need both since I
want to write some new apps.  Their MGR runs in ST monochrome mode only, that'd
be ok for me, but forget it!:  My 1-gig SCSI drive cost less than that, full
retail price! Remember this is just a hobby for me!  Who can I
call/write/e-mail to find out more about MGR/GWin/KWin/other GUIs for my
OSK/ST?
Please do post your answer publicly for the time being -- I'm going to change
Internet providers very very soon, e-mail may bounce.
Thank you in advance for helping.  -- Paul Seniura (in OkC)
(P.S.  Once I get my compiler libs set up, I'll begin hacking on pgms to print
GIFs & JPGs in full dithered color on a Canon BJC-600 in 360dpi!  8-)
There are 2 Replies.

#: 21056 S12/OS9/68000 (OSK)
    16-Jul-95  20:36:05
Sb: #21055-I'm up on Cumana OSK! :)
Fm: Bud Hamblen 72466,256
To: PaulSeniura 76476,464 (X)
The traphandler mismatch comes about when you try to run with version 2.3
programs that have been compiled to use the version 2.4 or later trap handlers
for library functions.  If the programmer had linked his program with the
library that doesn't use traps you would have been OK.  Of course, if the
source is available, you can always compile it for your own system.
Bud
(Running a PT68K-4)

#: 21057 S12/OS9/68000 (OSK)
    16-Jul-95  22:11:50
Sb: #21055-I'm up on Cumana OSK! :)
Fm: Bob van der Poel 76510,2203
To: PaulSeniura 76476,464 (X)
Nice to see you back and active.
>some OSK software I've downloaded says it can't install a traphandler >due to
my version of CIO, or something like that.
It is CIO. The fpu stuff from ultra c will not help. If you can't beg, borrow
or steal (not my suggestion) a newer version of cio you'll have to recompile
the programs you have. I have not hear of any problems with programs compiled
for an earlier verion of cio having problems with a later...but the other way
sure does complain.
The verion of screen I posted here awhile ago does come with source (hmmm, I
think I posted the source). If not, shout. Easyest just to compile without the
-i switch for cc.

#: 21058 S12/OS9/68000 (OSK)
    17-Jul-95  00:06:48
Sb: #CDL Basic ver 2.0 demo
Fm: Frank Hogg of FHL 70310,317
To: sysop (X)
Hi,
I've just uploaded 4 files pertaining to the new version 2.0 of the CDL Basic
compiler demo. I would appricate your making them available as soon as you can.
Thanks
Frank
There is 1 Reply.

#: 21059 S12/OS9/68000 (OSK)
    17-Jul-95  03:40:53
Sb: #21058-#CDL Basic ver 2.0 demo
Fm: Mike Ward 76703,2013
To: Frank Hogg of FHL 70310,317 (X)
Sure thing!
There is 1 Reply.

#: 21065 S12/OS9/68000 (OSK)
    18-Jul-95  23:13:25
Sb: #21059-#CDL Basic ver 2.0 demo
Fm: Frank Hogg of FHL 70310,317
To: Mike Ward 76703,2013 (X)
Thanks a lot. Should I inform the forum that it is there or will that info be
put in a notice or something?
There is 1 Reply.

#: 21066 S12/OS9/68000 (OSK)
    19-Jul-95  02:30:44
Sb: #21065-#CDL Basic ver 2.0 demo
Fm: Mike Ward 76703,2013
To: Frank Hogg of FHL 70310,317 (X)
Hi Frank.
SInce this section is read by all the interested parties I'd bet you get some
mileage if you posted a new product announcement right here in a message.
Best,
Mike
There is 1 Reply.

#: 21068 S12/OS9/68000 (OSK)
    19-Jul-95  22:06:50
Sb: #21066-CDL Basic ver 2.0 demo
Fm: Frank Hogg of FHL 70310,317
To: Mike Ward 76703,2013 (X)
Good idea, I'll put something together.
Thanks
Frank

#: 21063 S12/OS9/68000 (OSK)
    18-Jul-95  18:23:26
Sb: MVME162FX OS-9/68040
Fm: ole hansen 100016,3417
To:  100016,3417 (X)
Hello out there...
Does naybody need OS-9/68040 running on the MOTOROLA MVME162FX-board ??
I have a MVME162FX running OS-9/68040 V2.4 32MHz and GWINDOWS on a Snijder
IP-UVGA. I also have a V3.0 running without GWINDOWS.
Please contact me if it has interrest. All you need, is a standard MVME162
Board Support Pak and a new bootprom/bootdisk from me.
I can be reached by Email:
ole@danelec.dk
or here at CIS: 100016,3417
Press <CR> !>^C
Control-C Intercepted Menu
 1 Continue
 2 Return to menu/prompt
 3 Return to forum top
 4 Exit this forum
 5 Log off
Enter choice: ^B

#: 21096 S12/OS9/68000 (OSK)
    07-Aug-95  11:34:13
Sb: #OS-9 for MVME333
Fm: Manfred Berger 76570,2207
To: All
Does anybody know if there's a version of OS-9 that runs on the Motorola
MVME333 serial communication board ?
Best regards,
Manfred Berger
There are 2 Replies.

#: 21098 S12/OS9/68000 (OSK)
    07-Aug-95  17:22:02
Sb: #21096-OS-9 for MVME333
Fm: ole hansen 100016,3417
To: Manfred Berger 76570,2207 (X)
Hello Manfred
From the sources I have, I think you can get it directly from Microware. The
z8530-driver has ifdef's for MVME333 in it.
regards
ole@danelec.dk

#: 21102 S12/OS9/68000 (OSK)
    08-Aug-95  11:07:38
Sb: #21096-OS-9 for MVME333
Fm: Mark Wuest 76702,2253
To: Manfred Berger 76570,2207 (X)
Ole is correct - Microware did a port to it for a company I worked for
a few years back. If *they* don't there is a consultant in Connecticut
(Bill ?) who does - they should have his name...
Mark

#: 21128 S12/OS9/68000 (OSK)
    15-Aug-95  23:13:17
Sb: #NeedHelpToTrapError107!?
Fm: David A. Ferguson 73737,2471
To: all
Help!,
I need to know how to trap a floating point error.  Currently my program is
aborted when the result of a floating point operation 'under flows' to zero.
The following program will generate the error on my system (which is an
Allen-Bradley 1771-DMC):
      void main ()
           {
           float g;
           for (g = 1.0; ; g /= 3.1415)
                printf("g=%g\n", g);
           }
Following are the last few lines that are printed before the program is dumped.
      g=1.62876e-37
      g=5.18466e-38
      g=1.65038e-38
      Error #000:107
      $
Error 107 is documented to be:
      E_TRAPV  /* TrapV instruction TRAP 7 occurred */
Any help would be greatly appreciated.
Thanks...David
There is 1 Reply.

#: 21140 S12/OS9/68000 (OSK)
    18-Aug-95  00:55:07
Sb: #21128-NeedHelpToTrapError107!?
Fm: David Breeding 72330,2051
To: David A. Ferguson 73737,2471
 > Help!,
 >
 > I need to know how to trap a floating point error.  Currently my program
 > is aborted when the result of a floating point operation 'under flows' to
 > zero.
 >
 > void main ()
 > {
 > float g;
 >
 > for (g = 1.0; ; g /= 3.1415)
 > printf("g=%g\n", g);
 > }
 >
 > Following are the last few lines that are printed before the program is
 > dumped.
 > g=1.62876e-37
 > g=5.18466e-38
 > g=1.65038e-38
 > Error #000:107
 > $
I tried the same thing (using MW cc 3.2), and got the same thing as you did.
However, changing the variable to a double eliminated that error, for some
reason.  Here's the output at the time it got so small it started to just print
zero's:
   g=1.84685e-307
   g=5.87888e-308
   g=1.87136e-308
   g=0
   g=0
   g=0 Error #000:003     <<< I hit CTRL-C
I let it run for some time, and it never did error.  Dunno if this will help or
not, but maybe..
                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***
Press <CR> !>

#: 21172 S12/OS9/68000 (OSK)
    07-Sep-95  18:12:35
Sb: #20609-#PowerBasic
Fm: David L. Kaleita 72657,2775
To: Frank Hogg of FHL 70310,317 (X)
Hey Frank, how's it going?
Yes, I'm still alive. I work at Ford Motor Company in Dearborn now, and nobody
around here has any idea what OS-9 is.
Do you still work with the Hazelwood folks?
There is 1 Reply.

#: 21178 S12/OS9/68000 (OSK)
    10-Sep-95  23:29:42
Sb: #21172-PowerBasic
Fm: Frank Hogg of FHL 70310,317
To: David L. Kaleita 72657,2775 (X)
See my 'other' reply to you.

#: 21146 S12/OS9/68000 (OSK)
    22-Aug-95  17:15:57
Sb: #OS-9 on MVME162LX
Fm: Manfred Berger 76570,2207
To: All
Are there any problems running the BSP for MVME162 version 3.0 on a MVME162LX
model ?
Thanks,
Manfred Berger
There are 2 Replies.

#: 21147 S12/OS9/68000 (OSK)
    23-Aug-95  05:46:24
Sb: #21146-OS-9 on MVME162LX
Fm: Jost Eberbach 73502,2041
To: Manfred Berger 76570,2207 (X)
>>Are there any problems running the BSP for MVME162 version 3.0 on a MVME162LX
model ?<<
Manfred,
as far as I know, MW offer a special BSP version for the MVME162LX. The PROM
socket on the MVME162LX is different from the one for the regular MVME162. The
special BSP also supports all four serial ports, the regular one only two.
BTW, I work as a freelance engineer in the fields of software and automation
systems. I have a lot of experience with the MVME162. If you need some help,
let me know!
Jost Eberbach

#: 21161 S12/OS9/68000 (OSK)
    30-Aug-95  17:38:13
Sb: #21146-OS-9 on MVME162LX
Fm: ole hansen 100016,3417
To: Manfred Berger 76570,2207
Hello Manfred
I have been running it on MVME162LX fora year, and I don't recall any problems,
beside that you have to make the device-descriptors for the additional 2 serial
ports yourself. The only problem that might come up, is if the MVME162LX is
equipped with ECC-memory, as the standard bootprom does not know how to set
this up. I might be able to help you out with that too ??
regards
ole@danelec.dk

#: 21160 S12/OS9/68000 (OSK)
    28-Aug-95  12:19:52
Sb: OS-9 Job wanted
Fm: Jost Eberbach 73502,2041
To: all
Electrical engineer, 35 yrs., located near Wetzlar/Germany. I am looking for a
job as project engineer for process control and automation, preferrably using
OS-9 and the MVME162.
Here is my profile:
Education:
Studies of electrical engineering/automation systems at University of Siegen,
graduated in 1987, bacchelor's degree. 8 yrs. of professional experience in
Germany and the US.
Occupations:
     Project management
     Specifications
     Design of drive systems
     Design of automation systems
     Electrical circuit drawings
     Layout of control cabinets
     Software design/development for
          - automation systems
          - control systems
          - SPC systems
          - Process visualization, MMI
          - GUI
     Startup and commisioning
     Documentation and functional descriptions
Professional skills:
     Programming languages: C/C++, Pascal, Assembler
     Operating systems: OS-9, VAXELN, MS-DOS/Windows, OS/2
     LAN: TCP/IP, DECnet, MS-LAN-Manager, SINEC H1
     PLC: Simatic S5, Reliance Automax, Westinghouse
     AutoCad
     WordPerfect
     Database Borland Paradox
     Mechanical and hydraulic skills, especially in the area of rolling mills
     Analog control systems
     Bilingual German/English
If you're interested, please send an email to: Jost Eberbach, User ID
73502,2041 or call (Germany) (06403) 78088.
Thanks a lot!

#: 21169 S12/OS9/68000 (OSK)
    04-Sep-95  18:20:50
Sb: #new version of ar
Fm: Carl Kreider 71076,76
To: sysop (X)
I have uploaded two new versions of ar.  There was an obscure bug where you
couldn't extract a file if the first byte was an 0xff. I also included a static
linked (non-cio) version for those who don't have v2.4 osk.
Could you replace older versions using the old verbiage?  I apologize for not
taking time to do a proper job of uploading, but I don't have much free time
with the 306 project.
Carl
There is 1 Reply.

#: 21173 S12/OS9/68000 (OSK)
    09-Sep-95  04:31:17
Sb: #21169-#new version of ar
Fm: Mike Ward 76703,2013
To: Carl Kreider 71076,76
Thanks Carl. I'll take a crack at it.
Mike
There is 1 Reply.

#: 21176 S12/OS9/68000 (OSK)
    10-Sep-95  18:30:57
Sb: #21173-new version of ar
Fm: Steve Wegert 76703,4255
To: Mike Ward 76703,2013 (X)
Mike,
Sorry I didn't see your note earlier. Looks like Carl's given you the scoop on
the "mystery" files.
*- Steve -*

#: 21177 S12/OS9/68000 (OSK)
    10-Sep-95  23:28:26
Sb: #CDL Basic
Fm: Frank Hogg of FHL 70310,317
To: David L. Kaleita 72657,2775 (X)
Hey Yourself,
Yep I still work with Mike at Hazelwood. As you can see from the header we
changed the name to CDL Basic. Seems the 'other' name was taken. I 'thought'
that Ford as well as the other car companies used OS9 a lot. But maybe it's
embedded in some robot or something and 'they' don't see it. Years ago one of
my customers was constantly going over to England to do OS9 things at Ford etc.
If my fading memory serves me it did have something to do with the robots on
the line.
Nice hearing from you.
Frank Hogg
There is 1 Reply.

#: 21181 S12/OS9/68000 (OSK)
    15-Sep-95  15:18:29
Sb: #21177-CDL Basic
Fm: David L. Kaleita 72657,2775
To: Frank Hogg of FHL 70310,317
Well, you're right. OS-9 is EVERYWHERE on the lines, but here in "product
engineering-land" nobody's ever heard of it.
My job is doing project management for Electronic Engine Controllers (EECs).
It's good to hear from somebody from the past, Frank!
Press <CR> !>

#: 21183 S12/OS9/68000 (OSK)
    16-Sep-95  21:03:07
Sb: backup
Fm: Steve Bliss 75716,117
To: carl kreider
Carl No, our business isn't backups.  We do require a five floppy disk
installation set though.  Non-technical people need to be able to make them and
use them.  That was the inspiration for arf.
You got me thinking though.  Do you suppose a person could make a living as an
itinerant backup artist, going from door to door offering to back up hard
disks?  How about doing it over the phone line.  Would anyone pay the telephone
charges?  We could get a 900 number and offer a monthly service complete with
virus extermination.  I guess those with high-speed internet connections could
do it via the internet.
Steve B

#: 21184 S12/OS9/68000 (OSK)
    16-Sep-95  21:03:46
Sb: product
Fm: Steve Bliss 75716,117
To: carl kreider
Carl I don't know what we call our product.  We do what MCI-mail and CIS-email
do.  I guess you could call it a private e-mail system.  They used to be called
store-and-forward message switchers, but not many people know what that is.
We need machines with from 4 to 12 serial ports.  I need to be able to modify
the driver code.  I add communication protocol code to the driver for increased
speed and efficiency.
I am not familiar with MIPS numbers.  What's the MIPS of my uq20 at 12 (or 16)
MHz?  Are the 16 byte FIFO serial ports the 68681 DUART, or do these boards
have 4 ports total?
I don't know anything about PC's.  What kind of serial port boards are
available for the AT bus?  Are they DMA type devices?  Are there any that use
Motorola chips.  All I know about Intel chips is that they always install them
upside down, so the low order byte comes before the high order byte.
Is a TBA anything I ought to know about?  I guess it's where you connect the
monitor.
Steve B
Press <CR> !>

#: 21216 S12/OS9/68000 (OSK)
    12-Oct-95  15:38:47
Sb: #21147-OS-9 on MVME162LX
Fm: Manfred Berger 76570,2207
To: Jost Eberbach 73502,2041
Dear Jost;
Thanks for your reply.  I'm up running on my MVME162LX and so far so good.   I
do have some problems in accessing off-board memory with OS-9.  The MVME162Bug
is able to access this memory but ROMBug only gives me a bus error.  Do you
have any experience with off-board memory ?
Secondly, I'm was trying to set up my serial ports to run at 38400 Baud, but
OS-9 doesn't let me do that.  Have you tried 38400 ?
Best regards,
Manfred Berger

#: 21215 S12/OS9/68000 (OSK)
    12-Oct-95  15:37:55
Sb: #21161-#OS-9 on MVME162LX
Fm: Manfred Berger 76570,2207
To: ole hansen 100016,3417 (X)
Dear Ole;
I'm up running on my MVME162LX and so far so good.   I do have some problems in
accessing off-board memory with OS-9.  The MVME162Bug is able to access this
memory but ROMBug only gives me a bus error.  Do you have any experience with
off-board memory ?
Secondly, I'm was trying to set up my serial ports to run at 38400 Baud, but
OS-9 doesn't let me do that.  Have you tried 38400 ?
Best regards,
Manfred Berger
There is 1 Reply.

#: 21217 S12/OS9/68000 (OSK)
    12-Oct-95  16:46:49
Sb: #21215-OS-9 on MVME162LX
Fm: ole hansen 100016,3417
To: Manfred Berger 76570,2207
Hello Manfred
Which memory-address are you trying to access from rombug, that gives you
bus-error ?? I don't have any problem with my MVME162LX's. It can only be
rombug(or sysinit) that sets up the MVMEchip2 master decoders wrong ?? Do you
have the programming-manuals for the MVME162LX, so you could check this. I
think the ports can only run 19200 BAUD with the clock supplied to the
85230-chip. In fact if you run the port from MVME162Bug in the eprom-socket,
then it is only safe to run 9600 BAUD, because of the eprom is only 8-bit wide
!! regards ole@danelec.dk
Press <CR> !>

#: 21222 S12/OS9/68000 (OSK)
    16-Oct-95  02:28:19
Sb: #21216-#OS-9 on MVME162LX
Fm: Jost Eberbach 73502,2041
To: Manfred Berger 76570,2207 (X)
Hello Manfred,
regarding the off-board memory Ole Hansen already gave you some good hints. The
VMEchip needs some registers initialized, before you can access the VMEbus
safely. The OS-9 debugger does that automatically for you, but apparently not
the Mototrola Rombug.
For the serial ports, I also tried to use higher baud rates. I found out, that
with OS-9 version 2.4 the device driver is not able to use a higher baud rate
than 19200, although the chips are specified to go up to a speed of 38.4kbaud.
I think with OS-9 3.0 this is fixed, but I'm not sure, I never tried it. Ole is
right, that it doesn't make much sense to use more than 9600 baud on the
console (/term) port, because the debugger uses that baudrate as default, and
it's not easy to change that. But it makes some sense to use a higher baud rate
on serial port 2 (/t1), especially if you use it to download files.
Regards,
Jost
There is 1 Reply.

#: 21244 S12/OS9/68000 (OSK)
    21-Oct-95  14:40:03
Sb: #21222-#OS-9 on MVME162LX
Fm: Manfred Berger 76570,2207
To: Jost Eberbach 73502,2041 (X)
Hello Jost;
I have tried tmode and I wrote my own program to set the baud rate to 38400 but
OS-9 3.0 doesn't allow me to do so.   Since I am cross developing it would
really nice to speed up the download time and I'm also planning to do real-time
data acquisition and transfer the data over the RS-232 port.  Since I only have
the BSP product I don't have source code for the serial driver so I can't
change it and I really don't want to write my own driver.
Manfred
There is 1 Reply.

#: 21245 S12/OS9/68000 (OSK)
    24-Oct-95  11:41:56
Sb: #21244-OS-9 on MVME162LX
Fm: Jost Eberbach 73502,2041
To: Manfred Berger 76570,2207 (X)
Manfred,
>>I have tried tmode and I wrote my own program to set the baud rate to 38400
but OS-9 3.0 doesn't allow me to do so.   Since I am cross developing it would
really nice to speed up the download time and I'm also planning to do real-time
data acquisition and transfer the data over the RS-232 port.  Since I only have
the BSP product I don't have source code for the serial driver so I can't
change it and I really don't want to write my own driver.<<
Weel, I guess you have to accept what MW did, if you don't want to write your
own driver. Have you considered using Ethernet (TCP/IP) for transfering the
data? Another option is to purchase a third party serial board for higher baud
rates, incl OS-9 driver, and use that. But make sure you get a driver for OS-9
3.0, the ones for earlier version might not work...
I know of an english company who have such boards and drivers. If you like, I
can give you their address, I don't have it right now, but I can find it
somewhere.
Regards,
Jost

#: 21227 S12/OS9/68000 (OSK)
    16-Oct-95  21:10:39
Sb: Ram Card
Fm: Brother Jeremy, CSJW 76477,142
To: All
Dear friends:
I am looking to buy a DISTO 512K Ram Pak.  This was a 512k ram disk that
plugged into a multipak.  I will buy either in working or reasonably fixable
condition.  I would also need any associated software.
With all best wishes,
Brother Jeremy, CSJW

#: 21240 S12/OS9/68000 (OSK)
    20-Oct-95  11:24:50
Sb: #OS9 3.0 crashes if ...
Fm: Rainer Thieringer 100544,1230
To: All
Hello,
the last few weeks I've had serious trouble with OS9/68000. I hope this message
will prevent anyone out there from spending lonely nights face to face with a
crashed system.
Scenario 1: A board in my system produces asynchronous interrupts.
Unfortunately the interrupt level switched to the VME bus had intermediate
states (e.g. IRQ 6 was for a few us an IRQ 2). This should be reported as
SPURIOUS IRQ followed by a system reset if not handled by a user trap (or 3.0's
SpurIRQ flag). What I've had was a total CRASH !!! Not even ROMBUG could help.
I (and my hardware vendor) suppose that this SPURIOUS IRQ message will not
appear, if immediately after the first (bad) IRQ another (good) IRQ happens.
This crashes OS-9 completely.
Workaround: a) I set the SpurIRQ-flag in the init modules COMPAT Byte to ignore
Spurious IRQs. b) I jumpered the board with IRQ 2 so that no intermediate IRQ
states could happen.
Scenario 2: Together with that SpurIRQ flag I set the PrivAlm flag which should
keep OS-9 from accidentialy deleting foreign alarms. After I did so I've had
system crashes (w/o any notification) every couple of minutes. After resetting
the flag everything worked fine again. As I've heard on the SYSTEMS this is an
know bug. Microware offers an update.
BUT ONCE AGAIN MICROWARE DID NOT INFORM US DEVELOPERS ABOUT A KNOWN BUG!
I hope this was the last serious surprise with 3.0x (knock on wood).
There is 1 Reply.

#: 21246 S12/OS9/68000 (OSK)
    24-Oct-95  12:49:31
Sb: #21240-#OS9 3.0 crashes if ...
Fm: Ian J Shearer 100410,2733
To: Rainer Thieringer 100544,1230 (X)
Rainer,
 >>I (and my hardware vendor) suppose that this SPURIOUS IRQ message will not
appear, if immediately after the first (bad) IRQ another (good) IRQ happens.
This crashes OS-9 completely.<<
 This isn't really down to OS-9, is it?. If a 680x0 processor gets an exception
during an exception-handling routine, it resets. It looks as if your problem
was poor hardware rather than poor OS.
 >>I set the PrivAlm flag which should keep OS-9 from accidentialy deleting
foreign alarms<<
 The PrivAlm seems to be something of a workaround for slightly flaky alarms.
Doesn't it only work to protect other UserID's (no use for tasks with a common
parent)? You can use semaphores to guard against accidental deletes, which
avoids the M'ware bug.
 >>BUT ONCE AGAIN MICROWARE DID NOT INFORM US DEVELOPERS ABOUT A KNOWN BUG!<<
 Microware have NEVER been good at advertising their faults.
 >>I hope this was the last serious surprise with 3.0x (knock on wood).<<
 Now that would be surprising!!
 Ian
  -Ian J Shearer
There is 1 Reply.

#: 21255 S12/OS9/68000 (OSK)
    02-Nov-95  03:57:18
Sb: #21246-#OS9 3.0 crashes if ...
Fm: Rainer Thieringer 100544,1230
To: Ian J Shearer 100410,2733 (X)
Hello Ian,
nice to get some response.
 > This isn't really down to OS-9, is it?. If a 680x0 processor gets an
 >exception during an exception-handling routine, it resets. It looks as if
your
 >problem was poor hardware rather than poor OS.
 > OK Ian, I must admit, that I am not very familiar with the 680x0 processors.
Fact is, that I haven't ever had problems with OS9 2.4. That doesn't mean that
I haven't ever got spurious IRQs! Boy, I really got a hell lot of them, but OS9
2.4 told me that it has caught one before the system resets. So probably you
are right, but if so I hope that my report gives someone having these
mysterious crashes a hint.
 > The PrivAlm seems to be something of a workaround for slightly flaky alarms.
 >Doesn't it only work to protect other UserID's (no use for tasks with a
common
 >parent)? You can use semaphores to guard against accidental deletes, which
 >avoids the M'ware bug.
 > In OS-9 Technical Manual pg. 2-29 the description to M$Compat says: "Only
the *process* that created an alarm can delete it". If you know more about that
flag, please let me know.
- Rainer Thieringer
  HAAS LASER GmbH
  Germany
There is 1 Reply.

#: 21256 S12/OS9/68000 (OSK)
    03-Nov-95  08:57:05
Sb: #21255-OS9 3.0 crashes if ...
Fm: Ian J Shearer 100410,2733
To: Rainer Thieringer 100544,1230 (X)
Rainer,
 >> The PrivAlm seems to be something of a workaround for slightly flaky
alarms.
 >>Doesn't it only work to protect other UserID's (no use for tasks with a
common
 >>parent)? You can use semaphores to guard against accidental deletes, which
 >>avoids the M'ware bug.
 > In OS-9 Technical Manual pg. 2-29 the description to M$Compat says: "Only
the *process* that created an alarm can delete it". If you know more about that
flag, please let me know.
 You're right, that's what the manual says. I was basing my comments on
information from Microware Technical Support in the UK. To quote . . .
 "On Ver3.0 OS-9 this may be partially prevented by setting a field in the init
module, which causes a check such that when an alarm is deleted, it must be in
the same user/group."
 I queried the statement at the time, and was told (verbally) that sibling
processes sharing the same user/group ID could still accidentally delete each
others alarms. Since this didn't solve my problem, I used a workaround rather
than M$Compat.
 Not a complete answer, I know, but the best I can do for now. Hope it helps.
  -Ian J Shearer, Onyx Systems Ltd.

#: 21252 S12/OS9/68000 (OSK)
    30-Oct-95  22:50:36
Sb: #SCF hardware handshake
Fm: Doug Bailey 73612,2146
To: sysop (X)
I am writing an OS-9 application to a device that uses RTS/CTS flow control.  I
need to enable my SCF device to handle this flow control but do not know how.
I have looked at changing the device descriptor but nothing seems obvious
there.  I see that the SCF device has a static structure that signals when to
enable the RTS/CTS but don't know how to access it?
Anybody with any advice?
Thanks for the help!!
Doug Bailey
There are 2 Replies.

#: 21253 S12/OS9/68000 (OSK)
    31-Oct-95  05:35:40
Sb: #21252-#SCF hardware handshake
Fm: Marc Tritschler 100344,2706
To: Doug Bailey 73612,2146 (X)
The ability of your system to work with CTS/RTS flow control depends on two
things - the ability of your actual serial communications device to handle flow
control, and the device driver itself having the ability to configure the
device to do so.
It is safe to assume that your serial device has the ability to handle flow
control, but the device driver is another question. The device driver will
have, most likely, been supplied to you by the company you have bought your
hardware from, and so I would recommend that you speak to them to get an
accurate answer.
I will give you an example of my SCF device driver experiences. In the SCF
device drivers that I have, CTS / RTS flow control is enabled by using the
xmode utility to set the XON and XOFF properties to certain values not normally
used for XON and XOFF e.g. both to 0. The device driver, when it picks this up,
puts the device into CTS / RTS flow control mode.
Unfortunately, however, the manufacturers definition of flow control was not
the same as mine - they asserted RTS permanently (whether or not data was ready
to be transmitted) and waited for CTS to be asserted before transmitting data,
whereas I required to assert RTS only when I had data available to send, and
wait for CTS to be asserted before sending it, then de-assert RTS after the
data was sent. In order to achieve this I had to modify the device driver
itself, which required fairly in-depth knowledge about the device.
Obviously, if you dont have this knowledge, and need to do a similar
modification, it is better to get the manufacturer / device driver supplier to
do it for you.
I hope this puts things into perspective.
Cheers,
Marc.
There is 1 Reply.

#: 21254 S12/OS9/68000 (OSK)
    31-Oct-95  21:46:09
Sb: #21253-SCF hardware handshake
Fm: Doug Bailey 73612,2146
To: Marc Tritschler 100344,2706 (X)
Thanks for the info Marc.
My situation is that I'm running on a MVME167 box wwith a 68681 UART device.
However, the eventual target is a custom box again using a 68681 UART.  I have
source code for the driver and it has a flag stored in the SCF static data
field that allows me to activate the hardware flow control.  It seems I need to
get to this flag before driver initialization.
I guess my best bet is as you recommended and talk to the driver's author.
Thanks again,
Doug Bailey

#: 21257 S12/OS9/68000 (OSK)
    03-Nov-95  09:29:53
Sb: #21252-#SCF hardware handshake
Fm: Jost Eberbach 73502,2041
To: Doug Bailey 73612,2146 (X)
Doug,
there is an OS-9 system call that you could use to enable RTS/CTS flow control.
The name of the call is I$SetStt. Among others, there are function codes
available to disable and enable the RTS hardware handshake lines. From C, you
can use that call by calling _os_ss_dsrts(path) to disable or
_os_ss_enrts(path) to enable RTS (see your C-library manual). Of course, this
requires that your driver as well as your hardware support RTS. You could
simply try it, or consult your hardware manufacturer, in case your manuals
don't tell you enough about RTS and CTS (mine don't, I'm using an ELTEC board
right now). They should be able to help you.
Regards,
Jost
There is 1 Reply.

#: 21258 S12/OS9/68000 (OSK)
    03-Nov-95  12:25:20
Sb: #21257-SCF hardware handshake
Fm: Doug Bailey 73612,2146
To: Jost Eberbach 73502,2041 (X)
Thanks for the info.  I'll try it out.
Doug Bailey

#: 21259 S12/OS9/68000 (OSK)
    04-Nov-95  14:10:29
Sb: Windio #56/Screen Saver
Fm: Boisy G. Pitre 74464,3005
To: All
Windio #56 is now available in section 12 of the library.
Press <CR> !>

#: 21261 S12/OS9/68000 (OSK)
    06-Nov-95  03:28:22
Sb: #21256-OS9 3.0 crashes if ...
Fm: Rainer Thieringer 100544,1230
To: Ian J Shearer 100410,2733 (X)
Ian,
since it the difference between user/group and task is very important for me I
will try to find out the real truth about these Private Alarms. My hardware
vendors support division is happy about questions like this one! So whenever I
know something new, I will let you know.
Bye
- Rainer Thieringer
  HAAS LASER GmbH
  Germany

#: 21263 S12/OS9/68000 (OSK)
    10-Nov-95  04:08:40
Sb: #ftpd source ?
Fm: Gerd Gotthard 100135,262
To: all
Hello,
I would like to write an application similar to the Microware implementation of
ftpd. It would be great if someone could supply the sources of ftpd or a
similar utility.
ftpd solves some programming problems:
  - ftpdc has no parent process (parent ID: 0), but it is forked by ftpd.
  - ftpd has to F$WAIT for ftpdc. But it doesn't. ftpd accepts immediatly new
client
    connections.
  - ftpd cleans up any socket resource (no 'address already in use' errors)
Any help will be appreciated
        Gerd
There is 1 Reply.

#: 21264 S12/OS9/68000 (OSK)
    10-Nov-95  08:27:08
Sb: #21263-ftpd source ?
Fm: Pete Lyall 76703,4230
To: Gerd Gotthard 100135,262
Check the LINUX archives. LINUX is a FREE implementation (and a GOOD one) of
Unix, and the sources to everything in it are available. You'll hav to do a
little bet surfing.
A good place to start would be ftp.infomagic.com or sunsite.unc.edu.
Pete Lyall
Press <CR> !>

#: 21268 S12/OS9/68000 (OSK)
    14-Nov-95  04:10:21
Sb: #21263-ftpd source ?
Fm: Jost Eberbach 73502,2041
To: Gerd Gotthard 100135,262 (X)
ftpd source, Linux:
In Germany LINUX is also available on CD-ROM, it comes with a special issue of
the CHIP magazine, available wherever CHIP is sold. cost 49 DM.
Jost

#: 21271 S12/OS9/68000 (OSK)
    17-Nov-95  15:40:26
Sb: OS-9 Ver 3.0 Bug
Fm: Paul N. Leonard 72477,774
To: all
                     ////// OS-9 Version 3.0 BUG //////
     The tsleep() function behaves differently in version 3.0 than
     it prior to version 3.0,  and the result is very intermittent
     and can lock up your task.  We had created  a  macro  called
     hard_tsleep() to insure that we slept for a specified period.
     It worked fine before we started using OS-9 ver. 3.0.
     In  OS-9  version 3.0  tsleep(1)  returns  1,  not  0!  This
     causes the first macro below to loop endlessly. If you do any
     sort of checking for tsleep returning 0, you may want to keep
     this in mind.
     /* original version, works under OS-9 prior to version 3.0 */ #define
hard_tsleep(T)    { unsigned l; l=(T); while ((l=tsleep(l))!=0); }
     /* new version, overcomes bug in OS-9 version 3.0 */ #define
hard_tsleep(T)    { unsigned l; l=(T); while ((l=tsleep(l)) >1); }
  / Paul N. Leonard pnl@sgs.com / KE6PIJ Santa Clara ARES/RACES   /
 /_   Internet: pnl@sgs.com    /_ ke6pij@sgs.com                 /_
  /   CompuServe: 72477,774     / ke6pij@n0ary.#nocal.ca.usa.noam /
Press <CR> !>n