textfiles/messages/ALANWESTON/1994/OCEAN08_23.txt

N


Public Message 
Message # 2532 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 15Aug94
Date    : 94/08/15  18:11:00

From: James Jones <jejones@microware.com>
Date: Mon, 15 Aug 1994 10:06:02 -0500
Subj: Re: Fido Relay 14 August 1994

Concerning 8Mbyte memory boards, David Graham writes:
>Orders for 8 meg memory boards are now being accepted by BlackHawk
>Enterprises, Inc. with a shipping date of mid October 1995 expected.

Um, was that a typo, or did he really mean 199>5<?

James

Opinions, if any, herein are those of the author and not necessarily
those of any organization.

From: Boisy Pitre <boisy@microware.com>
Date: Mon, 15 Aug 1994 10:59:00 -0500 (CDT)
Subj: K-Windows Logo

Has anything ever been thought out on the K-Windows logo?

I would really like to include it in my program before Atlanta.

Boisy G. Pitre - Microware Systems Corporation; Des Moines, Iowa
Internet: boisy@microware.com OS-9 -- Clearly Superior.
The opinions expressed herein, unless otherwise stated, are mine only.

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2533 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 16Aug94
Date    : 94/08/16  18:08:00

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Mon, 15 Aug 94 08:28:32 -0700
Subj: Re: Fido Relay 14 August 1994

On Sun, 14 Aug 1994 18:25:04 -0500, MM1 Developer Grou wrote:

> From: David Graham
> To: All Msg #24, 94-08-12 08:15:04 est
> Subject: MM/1 8 meg memory boards
>
> Orders for 8 meg memory boards are now being accepted by BlackHawk
> Enterprises, Inc. with a shipping date of mid October 1995 expected.
^
^
I know David is being careful not to be overly optimistic but
that must be a slip of the keyboard ! Maybe his key caps got switched !
I have yet to see the original msg. on Fido but with a date of the
12th may be why, our local net 202 has had loss of backbone aquisition
for last 3-4 days.

> MM/1 Technical manuals are now in stock items......

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Tue, 16 Aug 1994 04:48:49 -0400 (EDT)
Subj: OS-9 Clipboard

Just another brief message regarding the forthcoming OS-9 Clipboard
library... Currently, the G-Windows implementation is being ported by a
good friend of mine. Before releasing the K-Windows implementation and
the Generic implementation I want to be sure the parameters I've
provided are adequate for the G-Windows port to provide consistency in
the libraries.

Thanks for all of the email and interest in this project. Several
programmers who have looked at the library have already said they are
excited about how it works, how easy it is to use, and are committed to
supporting it in their software! This comes from K-Windows programmers,
G-Windows programmers, and others, which means we may finally have found
the bridge we've needed for data transfer between applications!

The library will be available very shortly (for free, of course!) for
general use.

Best wishes,

Joel Mathew Hegberg

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Tue, 16 Aug 1994 04:46:34 -0400 (EDT)
Subj: K-win logo

> Has anything ever been thought out on the K-Windows logo?
> I would really like to include it in my program before Atlanta.

I agree with Boisy... we must come to an agreement on the K-Windows logo
very quickly. Some new members have joined this list, and we also now
have the audience of the MM/1 Tech echo, so perhaps I should fill in the
holes here.

A while ago, a few of us posted a few possibilities for an official
K-Windows graphical logo. We have a couple GIF files of the samples.
I'd like to get a vote on which one people like best in the next week.
So, here's a plan that might work. Go ahead and review the gif files.
Anyone who does not have the GIF files, send me a message and I'll email
you the UUEncoded gif's to look at. In a few days, I'll call for a
vote and may the best logo win! :)

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Tue, 16 Aug 94 09:02:21 -0700
Subj: Re: Fido Relay 15 August 1994

On Mon, 15 Aug 1994 18:55:03 -0500, MM1 Developer Grou wrote:
> From: Paul Myles
> To: Warren Hrach Msg #25, 94-07-30 02:28:22 est
> Subject: Re: MAXTOR LXT-340SY
>
> WH> I just installed a Maxtor 7290S 290meg drive as /H1 and had
> WH> similar format problem. I do not know it you have similar problem as
> WH> the 7290S is a scsi 1. What I found after setting the cntl=8 and
> WH> calling format I got the error msg, 'sector size to small'. Finally a
> WH> quick call to David Graham (who formatted my previous Maxtor) and found
> WH> out that one needs to use the format option -c=2 and away it went did
> WH> both physical and logical and verify and took about 45 min.
> WH> +ONE MORE IMPORTANT NOTE+ Be sure and tmode nopause !
>
> Warren,
> I also had to do this very same option for my Quantum 340meg. -c=2 was for
> 2 size of the clusters. Took me a few tries to get it right. Just add this
to
> your list of helpfull hints.
>
> Paul Myles
> theburgh@theboardwalk.com

Paul,
Actually if I had just did a 'format -?' I would have found the key
to the error msg. I got when attempting to format. The error msg alone
tells you 'cluster size to small, must be at least 2' or something to
that effect.
What I would like to know is if SCSI 2 drives will work correctly
on the MM/1 with the drivers we have ?
-Warren

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Tue, 16 Aug 94 09:13:43 -0700
Subj: Re: K-win logo

Joel, Can you send me the Kwindows logo samples. UUencoded of
course.
-Warren

From: Colin McKay <cmckay@northx.isis.org>
Date: Tue, 16 Aug 1994 16:59:20 -0400
Subj: Clipboard

Hi, Joel.

Was thinking about one addition -- a method of copying one
block of memory to the clipboard, and then back to memory.
This would be needed (I think) under systems with a SSM.

mem_to_clip() - copies a block of memory to the clipboard
clip_to_mem() -        the clipboard        a block of memory

TTYL. Colin.

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2539 *MM1 TECH Echo*
To      : All
From    : Russ Magee
Subject : Re: KWin Cursor
Date    : 94/08/13  19:19:00

  HI all,
 
  Seeing this talk about pushing/popping/reading the cursor's position
reminded me that I have found a set of display codes that push and pop the
cursor's position:
 
 $1b37 <col> <row> - push cursor position
 $1b38 <col> <row> - pop cursor position
 
I don't know of any way to READ the cursor's current position, though.
 
 -Russ Magee

--- Maximus/2 2.01wb
 * Origin: The MM/1 Keyboard [Calgary, AB 403-246-6943 HST/DS] (1:134/67)


Public Message 
Message # 2541 *MM1 TECH Echo*
To      : All
From    : Warren Hrach
Subject : Echo rules
Date    : 94/08/18 13:02:57

                       (Updated 94/08/18)
                MM1_TECH Fido echo rules and regulations.
 
I shall moderate this echo until a suitable replacement is available.
I do not want to moderate on a permanent basis since I am also a
Mfgr. Rep. for the MM/1 computer.
 
The rules are simple and please follow them as listed below:
 
1.  No commercial business may be conducted.
2.  No commercial advertising, only announcements of new products
    that become available for the benifit of MM/1 users. Prices
    should also not be quoted but a range may be stated.
3.  Absoulutly no flaming or bad language. Use of such tactics may
    result in your source loosing the echo.
4.  The use of quoting someone elses msg. in making up a reply should
    be limited to only quote the lines that relate to your reply.
5.  When  relating a problem and asking for help please include as
    much data about your configuration and boot as possible, include
    edition #'s and CRC of a module in question. Also your hardware
    configuration.
6.  This echo is for information and help so please refrain from 
    leaving personal mail that has no benifit for other users.
 
For information on sources of hardware and software for the MM/1 call
The Ocean Beach BBS.  The Ocean Beach BBS is also the Fido region 10
OS9CN OSK library.

The Ocean Beach BBS tel. # is (619) 224-4878 1,200-16,800 baud 8N1.
 
Your MM1_TECH Fido echo moderator, Warren Hrach
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message 
Message # 2546 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 17Aug94
Date    : 94/08/17  19:06:00

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Mon, 15 Aug 94 08:28:32 -0700
Subj: Re: Fido Relay 14 August 1994

On Sun, 14 Aug 1994 18:25:04 -0500, MM1 Developer Grou wrote:
> From: David Graham
> To: All Msg #24, 94-08-12 08:15:04 est
> Subject: MM/1 8 meg memory boards
>
> Orders for 8 meg memory boards are now being accepted by BlackHawk
> Enterprises, Inc. with a shipping date of mid October 1995 expected.
^
I know David is being careful not to be overly optimistic but
that must be a slip of the keyboard ! Maybe his key caps got switched !
I have yet to see the original msg. on Fido but with a date of the
12th may be why, our local net 202 has had loss of backbone aquisition
for last 3-4 days.

> MM/1 Technical manuals are now in stock items......

-Warren

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Tue, 16 Aug 1994 04:48:49 -0400 (EDT)
Subj: OS-9 Clipboard

Just another brief message regarding the forthcoming OS-9 Clipboard
library... Currently, the G-Windows implementation is being ported by a
good friend of mine. Before releasing the K-Windows implementation and
the Generic implementation I want to be sure the parameters I've
provided are adequate for the G-Windows port to provide consistency in
the libraries.

Thanks for all of the email and interest in this project. Several
programmers who have looked at the library have already said they are
excited about how it works, how easy it is to use, and are committed to
supporting it in their software! This comes from K-Windows programmers,
G-Windows programmers, and others, which means we may finally have found
the bridge we've needed for data transfer between applications!

The library will be available very shortly (for free, of course!) for
general use.

Best wishes,

Joel Mathew Hegberg

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Tue, 16 Aug 1994 04:46:34 -0400 (EDT)
Subj: K-win logo

> Has anything ever been thought out on the K-Windows logo?
> I would really like to include it in my program before Atlanta.

I agree with Boisy... we must come to an agreement on the K-Windows logo
very quickly. Some new members have joined this list, and we also now
have the audience of the MM/1 Tech echo, so perhaps I should fill in the
holes here.

A while ago, a few of us posted a few possibilities for an official
K-Windows graphical logo. We have a couple GIF files of the samples.
I'd like to get a vote on which one people like best in the next week.
So, here's a plan that might work. Go ahead and review the gif files.
Anyone who does not have the GIF files, send me a message and I'll email
you the UUEncoded gif's to look at. In a few days, I'll call for a
vote and may the best logo win! :)

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Tue, 16 Aug 94 09:02:21 -0700
Subj: Re: Fido Relay 15 August 1994

On Mon, 15 Aug 1994 18:55:03 -0500, MM1 Developer Grou wrote:
> From: Paul Myles
> To: Warren Hrach Msg #25, 94-07-30 02:28:22 est
> Subject: Re: MAXTOR LXT-340SY
>
> WH> I just installed a Maxtor 7290S 290meg drive as /H1 and had
> WH> similar format problem. I do not know it you have similar problem as
> WH> the 7290S is a scsi 1. What I found after setting the cntl=8 and
> WH> calling format I got the error msg, 'sector size to small'. Finally a
> WH> quick call to David Graham (who formatted my previous Maxtor) and found
> WH> out that one needs to use the format option -c=2 and away it went did
> WH> both physical and logical and verify and took about 45 min.
> WH> +ONE MORE IMPORTANT NOTE+ Be sure and tmode nopause !
>
> Warren,
> I also had to do this very same option for my Quantum 340meg. -c=2 was for
> 2 size of the clusters. Took me a few tries to get it right. Just add this
> to your list of helpfull hints.
>
> Paul Myles
> theburgh@theboardwalk.com

Paul,
Actually if I had just did a 'format -?' I would have found the key
to the error msg. I got when attempting to format. The error msg alone
tells you 'cluster size to small, must be at least 2' or something to
that effect.
What I would like to know is if SCSI 2 drives will work correctly
on the MM/1 with the drivers we have ?
-Warren

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Tue, 16 Aug 94 09:13:43 -0700
Subj: Re: K-win logo

Joel, Can you send me the Kwindows logo samples. UUencoded of
course.
-Warren

From: Colin McKay <cmckay@northx.isis.org>
Date: Tue, 16 Aug 1994 16:59:20 -0400
Subj: Clipboard

Hi, Joel.

Was thinking about one addition -- a method of copying one
block of memory to the clipboard, and then back to memory.
This would be needed (I think) under systems with a SSM.

mem_to_clip() - copies a block of memory to the clipboard
clip_to_mem() - the clipboard a block of memory

TTYL. Colin.

From: cramer@catt.ncsu.edu (Comrad Cramer)
Date: Tue, 16 Aug 1994 18:09:10 -0400 (EDT)
Subj: Re: Fido Relay 15 August 1994

>From: Paul Myles
>To: Warren Hrach Msg #25, 94-07-30 02:28:22 est
>Subject: Re: MAXTOR LXT-340SY
>
>WH> I just installed a Maxtor 7290S 290meg drive as /H1 and had
>WH> similar format problem. I do not know it you have similar problem as
>WH> the 7290S is a scsi 1. What I found after setting the cntl=8 and
>WH> calling format I got the error msg, 'sector size to small'. Finally a
>WH> quick call to David Graham (who formatted my previous Maxtor) and found
>WH> out that one needs to use the format option -c=2 and away it went did
>WH> both physical and logical and verify and took about 45 min.
>WH> +ONE MORE IMPORTANT NOTE+ Be sure and tmode nopause !
>
>Warren,
>I also had to do this very same option for my Quantum 340meg. -c=2 was for
>2 size of the clusters. Took me a few tries to get it right. Just add this to
>your list of helpfull hints.
>
>Paul Myles
>theburgh@theboardwalk.com

Think about it people (we've been through this before.) The bitmap size is
two bytes. Each bit is one cluster (usu. one sector) thus you can have
65536*8 clusters. At 512 bytes per sector (1 sector per cluster) that gives
you 256MB per disk. You can change the sector size or the cluster size or
partition the drive.

From: VAXELF@delphi.com
Date: Tue, 16 Aug 1994 21:42:38 -0400 (EDT)
Subj: Re: K-win logo

Joel,
send me another copy. I seem to have lost mine.

john@wb5dgq.hounix.org

From: cramer@catt.ncsu.edu (Comrad Cramer)
Date: Wed, 17 Aug 1994 00:04:58 -0400 (EDT)
Subj: Re: K-win logo

<begin butthead voice>
Yea, um, like send me one two <huh huh>
<end butthead voice>

From: KSCALES@delphi.com
Date: Tue, 16 Aug 1994 23:46:02 -0400 (EDT)
Subj: OS-9 Clipboard

> From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
> Subj: OS-9 Clipboard
>
> Just another brief message regarding the forthcoming OS-9 Clipboard
> library... Currently, the G-Windows implementation is being ported by a
> good friend of mine. Before releasing the K-Windows implementation and
> the Generic implementation I want to be sure the parameters I've
> provided are adequate for the G-Windows port to provide consistency in
> the libraries.

Glad to hear that things have been moving along, opening the library to
non KW environments.

A question comes to mind: is there any provision for maintaining
ownership of the clipboard info (i.e., userid)?

Example 1: If my son saves something in the clipboard, will my daughter
be able to access it if she later logs in? (Each has their own userid
on the system.) Ideally, she should have her own private clipboard.

Example 2: On a KiX30 with running G-Windows on multiple MGA boards,
will ownership integrity be maintained? Similarly, on any other system
with multiple users logged in simultaneously?

Hopefully, you've already covered this, or else it won't be too tough
to implement.

Cheers... / Ken

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Wed, 17 Aug 1994 03:14:10 -0400 (EDT)
Subj: MM/1 Dev Group note!

Recently, I've added a few new people to this developers list.
First of all, glad to have all of you!

The reason I'm writing this message is because I just realized I added
these people without filling them in on what _not_ to do on this list!
The problems stem from the way the mail server works... namely, it's not
a mail server, rather just a user account with a shell script doing the
work. This works fine in most cases, but...

NEVER EVER EVER send a message with an astrick character in it... not
even in your signature!! You see, each word in your message is
considered to be a parameter to the shell script forwarding your mailing
(which is why additional spaces between words is stripped out). The
astrick is taken to be a wild-card character and is replaced by all the
filenames in mushroom's directory... which is many many many!! Please
review your signature files and remove any astricks, and try to remain
aware and alert to any astricks that may be in your messages. C source
code files are especially treacherous!

Also, if the system that receives your electronic email will expire, go
down, or for any other reason bounce mail back to the mushroom "server",
please try and alert me _before_ this will occur! There appears to be an
inifinite loop problem as the shell script does not handle the error
condition properly and everyone on the list gets flooded with tons of
email error messages continuously until someone goes up and stops it
some way (Boisy, can you tell me how you stopped it last time?).

Don't be troubled by this message... the system has worked very well for
all of us so far. The inifinite loop thing has only happened once, and
if you do accidently include an astrick or two in your message, you'll
notice it real fast when your message is sent back to you and quickly
learn not to do it again. :) Thanks for your time.

 Joel Mathew Hegberg.

Note to all: Any mail going from Fidonet to Internet/Mushroom is first
filtered for any asterisk characters. -- Colin

<continued>

--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2547 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 17Aug94 2/2
Date    : 94/08/17  19:21:00

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Wed, 17 Aug 1994 03:14:32 -0400 (EDT)
Subj: Clipboard

Colin,

> Was thinking about one addition -- a method of copying one
> block of memory to the clipboard, and then back to memory.
> This would be needed (I think) under systems with a SSM.
>
> mem_to_clip() - copies a block of memory to the clipboard
> clip_to_mem() - the clipboard a block of memory

There are calls to copy raw memory to the clipboard, but the method is
currently associated with "display codes". I like the mem_to_clip() and
clip_to_mem() ideas, so I think I'll add those to make things even
simpler. Thanks!

From: "Boisy G. Pitre" <boisy@os9er.waukee.ia.us>
Date: Wed, 17 Aug 94 06:44:33 -0500
Subj: Re: MM/1 Dev Group note!

Once upon a time, MM1 Developer Grou eloquently stated:
> Also, if the system that receives your electronic email will expire, go
> down, or for any other reason bounce mail back to the mushroom "server",
> please try and alert me _before_ this will occur! There appears to be an
> inifinite loop problem as the shell script does not handle the error
> condition properly and everyone on the list gets flooded with tons of
> email error messages continuously until someone goes up and stops it
> some way (Boisy, can you tell me how you stopped it last time?).

I ftp'ed a new 'members' which didn't have the e-mail address of the
problem site (Microware being the problem that time, with mine and
James' address)

Boisy G. Pitre
Internet: boisy@os9er.waukee.ia.us Delphi: BOISY
The opinions expressed herein, unless otherwise stated, are mine only.

From: "Boisy G. Pitre" <boisy@os9er.waukee.ia.us>
Date: Wed, 17 Aug 94 06:46:54 -0500
Subj: Joystick Info

I got this last night from Mike Haaland, and thought it would be
good to pass around in case anyone hasn't seen it.

  -----

For the last few years I've had this real strange problem with the MM/1
joystick ports. It seems that the values it returns are bogus.

Well, I finally needed to use the port and this is what I discovered.

From ground to the high side of the pot in the joystick I get approx.
.85 volts. From ground to the center poll of the pot I was getting 1.7
volts. Wierd.

Problem:

Joystick centered returned. x=80, y=80.
Joystick Upper Left returned. x=0 , y=0.
Joystick Lower Right returned. x=60, y=60.

Solution:

Remove pin 5 (+5V) the joystick internally.

Now I get,

Joystick centered returned. x=80, y=80.
Joystick Upper Left returned. x=0 , y=0.
Joystick Lower Right returned. x=110, y=110.

Problem solved.

NOTE:

It turns out some of the earlier MM/1 I/O boards have 100 Ohm
resisters installed as R-13 and R-14. This is causing the problem.

Better solution:

If the resistors R-13 and R-14 are 100 Ohm, replace them with
200 Ohm resistors. After replacing them I get the following
values:

Joystick centered returned. x=100, y=100.
Joystick Upper Left returned. x=0 , y=0.
Joystick Lower Right returned. x=127, y=127.

I'm not sure why but the above values tend to float by +/-5.

I just might try 220 Ohm resistors to see if I can bring the
center values down to around 65. Any ideas?


Here's the program I use to test it with.

/* ssjoy.c - Mike Haaland <mike@htsmm1.las-vegas.nv.us> */

#include <stdio.h>

#define XADDR 0xE00100
#define YADDR 0xE00101

#define JSELA 0xE00199
#define CLRJY 0xE00385

#define BADDR 0xE00381

#define BMASK 0x0C
#define BUTN1 0x04
#define BUTN2 0x08

int firstime = 1;
char orig_jsel;

#define STDOUT 1

main()
{
    char packet[4];
    char ch;

    while (_gs_rdy(0) < 1) {
        getjoy(packet);
        printjoy(packet);
        tsleep(10);
    }
    read(0,&ch,1);
    resetjoy();
}

printjoy(packet)
char *packet;
{
    printf(" x = %04d, y = %04d, Butns: 1 = %d - 2 = %dn",
    packet[0], packet[1], packet[2], packet[3]);
    tsleep(0x80000010);

}

getjoy(jpack)
char *jpack;
{
    char *sel, *clr, *butts, *x, *y, buttons;

    /* Set input to come from joystick port */
    if (firstime) {
        sel = (char *)JSELA;
        orig_jsel = *sel & 0xff;
        sel[0] |= 0x01;
        /* Clear the buttons */
        clr = (char *)CLRJY;
        clr[0] &= 0xF3;
        sel = clr = NULL;
        firstime = 0;
    }
    /* read info */
    /* point to x and y values */
    x = (char *)XADDR;
    y = (char *)YADDR;
    /* store em */
    jpack[0] = *x & 0xff;
    jpack[1] = *y & 0xff;
    /* point to button values */
    butts = (char *)BADDR;
    /* grab 'em */
    buttons = *butts & BMASK;
    /* make all the pointers point to NULL */
    x = y = butts = NULL;
    /* Mask out the buttons */
    jpack[2] = (buttons & BUTN1) ? 0 : 1;
    jpack[3] = (buttons & BUTN2) ? 0 : 1;
}

resetjoy()
{
    char *sel;

    /* restore input to re-enable sound / disable joystick */
    sel = (char *)JSELA;
    *sel = orig_jsel & 0xff;
    sel = NULL;
}

/* End of SSJoy.c */

--
Boisy G. Pitre
Internet: boisy@os9er.waukee.ia.us Delphi: BOISY
The opinions expressed herein, unless otherwise stated, are mine only.

From: Boisy Pitre <boisy@microware.com>
Date: Wed, 17 Aug 1994 09:30:55 -0500 (CDT)
Subj: OS-9 in "Wired"

The September 1994 issue of "WiReD" Magazine has a 5 page article
on Microware and OS-9. It's a very good expose, and is worth the
read.

Boisy G. Pitre - Microware Systems Corporation; Des Moines, Iowa
Internet: boisy@microware.com OS-9 -- Clearly Superior.
The opinions expressed herein, unless otherwise stated, are mine only.

From: Boisy Pitre <boisy@microware.com>
Date: Wed, 17 Aug 1994 10:25:11 -0500 (CDT)
Subj: OS-9 in "Wired"

In my previous message, I wrongly referred to the WiReD magazine
article as an expose. The word was intended to be 'exposition.'

Grrrgfmm....

Boisy G. Pitre - Microware Systems Corporation; Des Moines, Iowa
Internet: boisy@microware.com OS-9 -- Clearly Superior.
The opinions expressed herein, unless otherwise stated, are mine only.

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2550 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 18Aug94
Date    : 94/08/18  19:28:00

From: cramer@catt.ncsu.edu (Comrad Cramer)
Date: Wed, 17 Aug 1994 20:36:09 -0400 (EDT)
Subj: Re: Fido Relay 17 August 1994

>From: David Graham
>To: All Msg #29, 94-08-15 12:57:58 est
>Subject: WANTED!!!!!
>
>Wanted, Preferably alive, if not kicking!!!!!
>
>1 C Language Programmer.
>
>Must be proficient in C. Familiar with ANSI standard or own copy of
>Plauger's book. Must be willing to provide leadership and organization
>for volunteers, or work like a herd - cheap!! (read FREE! ;))
>
>Objective is to create ANSI C STANDARD library for OSK GCC 1.42 and
>2.5.8.
>
>Apply via E-Mail to above address.
>
>This is a public service project!!!

this is cool, I guess I can work with it some. I've got a heavy load this
semester and a job with the data aq. lab doing all kinds of fun stuff.

--cramer

From: "Boisy G. Pitre" <boisy@os9er.waukee.ia.us>
Date: Wed, 17 Aug 94 22:48:10 -0500
Subj: K-Windows logo

Maybe it's a good idea to wait and bring up the logo at the MM/1
developer's meeting in Atlanta. That way, we can all see what's
on the table, then pick and choose from there.

Thoughts on this?

From: cramer@catt.ncsu.edu (Comrad Cramer)
Date: Thu, 18 Aug 1994 18:49:08 -0400 (EDT)
Subj: Directory access

Ok kiddies, I'm getting ready to open my machine up for network access, but
the d*mned shells on OS-9 systems have to have write access to chd to them.
The was a shell fix for this but it isn't working on the MM/1. The shell
in the kernel module directory is supposed to have this anoying "feature"
fixed. All the other shells use the defaults in the cio trap library or
the clib library. What I want is to fix the libraries so this doesn't happen
and then fix the existing applications (shell, sh, bash, etc.)

--cramer

PS: anybody interested in seeing about getting OSK 3.0 on the MM/1, SYS 4 & 5,
KiX, TC70 ???

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2552 *MM1 TECH Echo*
To      : David Graham
From    : Floyd Resler
Subject : Gem Quest
Date    : 94/08/19 15:24:14

Hello.  Just wondering if you forgot about me.  Last time we talked, you 
were going to send me out the list of escape sequences so I could get
Gem Quest to work without needing BGFX.  My address is:
 
   Floyd Resler
   432 Elberon Ave. #1
   Cincinnati, OH 45205
 
Thanks!
 
--- RiBBS v2.10  
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message (Rec)
Message # 2585 *MM1 TECH Echo*
To      : Warren Hrach
From    : Clyde Price
Subject : Re: MM/1 new news
Date    : 94/08/18  13:30:00
Next Reply is Message 2588

Warren,
        I haven't exactly been a happy customer with my existing MM/1, 
but if there's a prospect of having a sturdy, reliable portable 
(notebook? or luggable?) OSK machine, I'm VERY interested!
  
        What kinds and sizes of harddrives are being considered? How 
many serial ports? What other kinds of I/O? Any hopes for PCMCIA* 
support? Internal modem? Sound support? Color/Mono choice? Support for 
external keyboard/monitor for console user?
  
        Hmmm... I just realized I'd immediately need a Dvorak Keyboard 
program to use a "standard" portable 'puter keyboard.
  
        I'm still intensely interested.  This might be enough to put my 
beloved little Model 100 into semi-retirement. (I'm using it online 
now.)
  
--Clyde Price  (404) 262-0712
P.O.Box 667, Red Oak GA 30272-0667

--- QuickBBS 2.76a
 * Origin: ACS Inc. BBS 404-636-2991 (1:133/510)


Public Message 
Message # 2588 *MM1 TECH Echo*
To      : Clyde Price
From    : Warren Hrach
Subject : Re: MM/1 new news
Date    : 94/08/20 10:50:37
Previous Reply is Message 2585   

            On Thursday, August 18th, 1994 - Clyde Price wrote:
 
CP> but if there's a prospect of having a sturdy, reliable portable 
CP> (notebook? or luggable?) OSK machine, I'm VERY interested!
CP>         What kinds and sizes of harddrives are being considered? How 
CP> many serial ports? What other kinds of I/O? Any hopes for PCMCIA* 
CP> support? Internal modem? Sound support? Color/Mono choice? Support 
CP> for  external keyboard/monitor for console user?
CP> Hmmm... I just realized I'd immediately need a Dvorak Keyboard 
CP> program to use a "standard" portable 'puter keyboard.
CP> I'm still intensely interested.  This might be enough to put my 
CP> beloved little Model 100 into semi-retirement. (I'm using it online 
CP> now.)
 
Clyde,
     Why not call David Graham and tell him about your interest.
The only thing I can tell you is the 2.5" hard drives would be used.
-Warren
 
--- RiBBS v2.10 
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message 
Message # 2597 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 19Aug94
Date    : 94/08/19  18:16:00

From: "David M. Graham" <NIMITZ@delphi.com>
Date: Fri, 19 Aug 1994 01:42:09 -0400 (EDT)
Subj: OS-9 Source Book

To get your products listed in a new OS-9 source book (not by Microware)
send info to Tom Farrel - 660 El Paso Blvd. Denver, CO 80221.

Tom may be reached at TMF@delphi.com also.

DAvid

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Fri, 19 Aug 1994 02:44:07 -0400 (EDT)
Subj: OSk 3.0

> PS: anybody interested in seeing about getting OSK 3.0 on the MM/1, SYS 4
> & 5, KiX, TC70 ???

I would be for the MM/1. I though I heard a rumour David was checking
on that? David?

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Fri, 19 Aug 1994 02:43:40 -0400 (EDT)
Subj: K-Win logo

Boisy,

> Maybe it's a good idea to wait and bring up the logo at the MM/1
> developer's meeting in Atlanta. That way, we can all see what's
> on the table, then pick and choose from there.

Hm? Developer's meeting in Atlanta? I did not hear about this. Sounds
fine to me. It looks like I'll actually be there, with the airline
deals I've found.

From: knudsen@ihades.att.com
Date: 19 Aug 94 18:25:00 GMT
Subj: Re: Directory access

Would someone care to post a short list of the advantages of OSK 3.0
over 2.4? Also, was there ever a 2.5, or did Mware go straight from
2.4 to 3.0? Thanks, mike k

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2629 *MM1 TECH Echo*
To      : David Graham
From    : James Gifford
Subject : 5 1/4 coco disk read
Date    : 94/08/21 10:59:00

David;
I think there must have been a mistake in in the message system. I have
not been able to get my TEAC FD55 dual speed drive to work.
   What drivers do I need to use and how should I set it up.
   Any help would be greatly appreciated
   Thanks,   Jim.
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message 
Message # 2638 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 19Aug94
Date    : 94/08/20  17:25:00

From: Warren Hrach <warren@ocnbeach.jd.com>
Date: Fri, 19 Aug 94 14:38:43 -0700
Subj: RiBBS sources

John,
Just a note on the RiBBS createmb source. It may only work
for RiBBS V2.02. However there is another source for cvthdr210
that was intended to fix the HDR file. So if you have trouble
creating a Message Base use cvthdr210 on it and follow prompts.
I am also sending a CC to the mm/1 developers list as a
test.
-Warren

From: Colin McKay <relay@northx.isis.org>
Date: Fri, 19 Aug 1994 18:11:41 -0400
Subj: Re: Directory access

Hi, Mike.

In addition to the following, it also comes with the Ultra C compiler, which
is, I think, ANSI compliant.

TTYL. Colin.

From: gjm@mserv1.dl.ac.uk (g.j.milne)
Subject: Re: Unix program fo
Date: 17 Nov 1993 08:48:48 GMT

In article 173@rcisnet.org, rcisnet2!rcis_hq!coco_hacker () writes:
:PCF is included with OS-9, as far as I know. Its a PC-DOS file manager,
:which allows you to access PC-DOS disks as if they were OS-9 disks (well
:almost).

According to Microware's White Paper on OS-9 V3.0 the PCF software will form
part of the "disk-based" and "extended" OS-9 configurations.

With V3.0 Microware has changed from having Industrial OS-9 and Professional
OS-9. There will be 6 different configurations:

1. Atomic OS-9
2. Atomic Node OS-9
3. Embedded OS-9
4. Embedded Node OS-9
5. Disk-Based OS-9
6. Extended OS-9

and the software that each comprises is summarised below:

1 2 3 4 5 6 ! OS-9 Software Modules
---------------+-------------------------
x x x x x x ! Atomic Kernel
- - x x x x ! Standard Kernel
x x x x x x ! IOMan
- - x x x x ! PIPE (named/unnamed pipes)
- - x x x x ! SCF (serial/parallel)
- - x x x x ! Embedded OS-9 Utilities
- - - - x x ! RBF (disk)
- - - - x x ! PCF (DOS disks)
- - - - x x ! SBF (Tape)
- - - - x x ! Disk-based OS-9 utilities
- x - x - x ! ISP (TCP/IP)
- x - x - x ! NFS Client
- x - x - x ! Extended OS-9 Utilities
+-+-+-+-+-+----+--------------------------
! ! ! ! ! !
! ! ! ! ! +---> Extended
! ! ! ! +-----> Disk-Based
! ! ! +-------> Embedded Node
! ! +---------> Embedded
! +-----------> Atomic Node
+-------------> Atomic

I am sure you will find the above table interesting. It provides some
interesting pointers to the way things are going. In particular the NFS
client support in Atomic-Node, Embedded-Node and Extended is a clear
indicator that FasTrak is Microware's strategic technology for development in
the future.

BTW can anyone say whether FasTrak will be ported to platforms other than
SUN3, SUN4 and HP9000? What about SG machines? This is especially important
since Unibridge is available for SG machines and the single-workstation
Unibridge is not good value when compared against a 5 workstation FasTrak!

Get a copy of the White Paper ... it contains interesting information.

Ciao!

Gordon
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Gordon J. Milne Data Handling & Controls Group.
SERC Daresbury Laboratory, Warrington, WA4 4AD, UK.
E-mail: g.j.milne@dl.ac.uk Voice: +44-925-603169 Fax: +44-925-603275

From: Joel Mathew Hegberg <JOELHEGBERG@delphi.com>
Date: Sat, 20 Aug 1994 04:01:40 -0400 (EDT)
Subj: Gone Temporarily

This is just a quick note. Any mail sent to me may not get a reply for
a couple days, depending on the local SprintNet node (actually phone
connections). The problem is due to a very bad storm that hit DeKalb
yesterday (at least 4 funnel clouds sighted, 2 touched down on my side
of town). There really isn't lots of damage... trees down and snapped
telephone poles, downed power lines, streets littered with branches and
such. The SprintNet connection is very sporadic now as repairs go
underway, and power will be out for a bit tomorrow as they try to
restore power to the South East side of town and to right the telephone
poles.

I was at work when the storm hit (I work at a restaurant to get me
through college) and was safe inside the store's cooler while one of the
tornadoes passed by, while others hid under the tables. (I'm not sure
why they did that... really no protection and there are about 10 huge
glass windows in the main room, which would really cause some injuries
if they were blown in!)

I'm connecting to Delphi via the local University using a friend's
system, but won't be on again until SprintNet comes back up, so talk to
everyone shortly!

-- Joel Mathew Hegberg.

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2661 *MM1 TECH Echo*
To      : All
From    : Colin McKay
Subject : Mushroom 21Aug94
Date    : 94/08/21  18:53:00

From: tcs@tcs.knoware.nl (Peter Tutelaers)
Date: Sun, 21 Aug 94 10:45:34 WET DST
Subj: MM/1 developers list

Although I currently don't have an MM/1 anymore I would like to be
up-to-date on any developments for it. Could you please add me to the MM/1
developers list, thanx..

Peter Tutelaers

From: "David M. Graham" <NIMITZ@delphi.com>
Date: Sun, 21 Aug 1994 08:58:36 -0400 (EDT)
Subj: Re: OSk 3.0

I'm working on that, but it can't be done untill I get the MM/1 sales
back up. (I.E. MW wants $15000 in maintenance fees to transfer the
license over to me fully and then they'll talk about an upgrade). That
however, is on it's way, as the 8 meg backplane and I/O boards are enroute
to me as we speak. I'll need some engineering QA checks, then MicroLith
Digital can start building working boards.....

David

<EOF>


--- Maximus/2 2.01wb
 * Origin: BABYLON-5 (OS/2) 300/14,400 (819) 669-7462 (1:243/68)


Public Message 
Message # 2702 *MM1 TECH Echo*
To      : Colin Mckay
From    : Eric Crichlow
Subject : Re: Mushroom 04Aug94 6/7
Date    : 94/08/22 22:43:11
Previous Reply is Message 2149   

             On Thursday, August 4th, 1994 - Colin Mckay wrote:
 
CM> I'm rethinking a few parts of the proposal as I write it. I've added a
CM> 'sound' type for clipboard data, which distiguishes between 
CM> mono/stereo, and stores the frequecy data. I'm also thinking about 
CM> forgetting RLE encoding inside the clipboard for graphics... how 
Joel,
    Unfortunately I didn't get around to reading this until long after
you posted it, but I thought I would add my 2 cents worth anyway. About
a year ago I wrote out a MM/1 Clipboard Standard. I just never took the
time to implement it. There's two points that I think need to be made
about your proposal.
    Even though no one may ever take the time to write the software to
do it, I think its necessary to prepare for every reasonable
possibility, and by reasonable I mean whatever the "mainstream" systems
are doing. The standard I wrote accomodated for text only, graphics
only, sound only, animation w/out sound and animation w/sound. As far as 
the animated clips go, I was thinking of supporting Apple's QuickTime
format, but I was never able to get ahold of the specs for it. We may
never use it, but it would be nice to know that it was provided for if
someone ever wanted to give it a try.
    I'm not quite sure exactly what you have in mind for displaying
clipboard item(s) once they've been saved to the clipboard. From your
proposal I couldn't tell if the program had to have its own routine for
looking into the clipboard or if it would be a system function. I
believe we should "borrow" the basics of the Mac's method. A program
should simply call the universal clipboard accessing routine, and that
routine would pop up a window over the program and display the clips,
allowing you to scroll through them. The program would also be able to
tell the clip viewer when it calls it exactly which types of clips it
can support, and the clip viewer would only display those clips that fit 
the description, (i.e. a word pro would ask for only text clips, and the 
viewer would then ignore everything else.)
    From the sounds of your last messages it sounds as though it's too
late to even consider this, but oh well, I'll just have to react faster
next time.
...Eric...
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message 
Message # 2703 *MM1 TECH Echo*
To      : David Graham
From    : Eric Crichlow
Subject : Re: MM/1 Tech Manuals
Date    : 94/08/22 22:56:58
Previous Reply is Message 2348   

             On Tuesday, August 9th, 1994 - David Graham wrote:
 
DG> I have started shipping MM/1 Tech Manuals from this date. 
David,
    Exactly what does this Tech Manual consist of? Any info that would
be of use to programmers?
...Eric...
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message 
Message # 2704 *MM1 TECH Echo*
To      : All
From    : Eric Crichlow
Subject : New MM/1 Game Announcement
Date    : 94/08/22 22:58:51

    Digital Fronteir Productions, (formerly VideoSonic Productions,) the 
company that brought ShellMate, Image Master and Gambit to the MM/1, is
now very proud to announce the release of the first full-screen
animation, arcade style, action game ever for the MM/1.
 
Introducing...
 
                    Gold Runner 2000
 
    This name may be familiar to long-time CoCo users, as Gold Runner
and Gold Runner 2: The Sequel, (both of which were clones of the
immensely popular game Lode Runner from Broderbund for mainstream
computer systems,) were two of the most popular games in Color Computer
history. As its name implies, however, Gold Runner 2000 is a variation
on the theme that's decades beyond its early 80's predecessors.
 
Gold Runner 2000 Features:
 
  * Full screen horizontal and vertical scrolling on a 312 x 208 x 256
    screen
 
  * 30 levels of play, each consisting of a 3 x 3 screen playing field
 
  * Over 16 Megabytes of graphics data
 
  * A complete digital stereo soundtrack consisting of seperate tracks
    for each level as well as intro and outro music
 
  * Over 6 Megabytes of stereo sound data
 
 
Gold Runner 2000 System Requirements:
 
  * 3Meg MM/1 or MM/1a
 
  * Hard drive (highly recommended)
 
  * Stereo speakers (highly recommended)
 
  * Joystick (optional)
 
 
    Gold Runner 2000 will begin shipping on Thursday, August the 25th.
For ordering information, see the complete release announcement on
Delphi or Compuserve, or leave me e-mail.
 
...Eric Crichlow
...Delphi: MREGC
...C-Serve: 71051,3516
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)


Public Message 
Message # 2705 *MM1 TECH Echo*
To      : All
From    : Eric Crichlow
Subject : MM/1 vs. CD-i
Date    : 94/08/22 23:12:44

    I originally posted this msg to Delphi, but it unfortunately got
very little response, so I figured I'd try it here. (I'd try it on the
Mushroom list if I had access! <hint> :) )
 
With the recent conversation online here about CD-i and the titles
available for it I've been thinking. As a programmer I have tapped the
limits of how much speed I can get out of a 68070 equipped MM/1 using C
to do full-screen scrolling while programming "by the rules". Yet when I 
look at some of the titles available on CD-i that do full-screen
scrolling they do it several times faster, and I'm sure CD-i programmers 
aren't programming in assembly.
 
    This leads me to 2 possible reasons for the performance difference,
(well, 3 reasons, but the most obvious, poor programming on my part,
I've ruled out since 2 other programmers whose opinion I value highly
agree that the code I'm using couldn't be done any more efficiently,)
first, it could be that CD-i programmers are using features of the 68070 
that we aren't, or second, the extra VSC chip that CD-i has is giving
them extra power to utilize.
 
    If option 1 is correct, then what are they getting out of the 68070
that we aren't? I must admit to being somewhat, if not completely
ignorant of the hardware abilities that lie outside of the normal range
of programming, but one thing that comes to mind is our DMA channels.
Maybe I'm off on what DMA really is, but, as I understand it, aren't we
using 1 DMA channel for sound and the other for SCSI device access? Is
it possible for a programmer to change this setup in a program so that
one channel gets used for sound and the other gets used to speed up
movement of screen data to screen memory?
 
    If option 2 is correct, and the second VSC chip gives them more
programming power, then the 1 VSC we have should give us SOME extra
programming power. I know the VSC has a PIXAC, and its my understanding
that the only thing we're using it for is the mouse pointer. Can we get  
access to the PIXAC from within C? Or would we have to program in
assembly? Since K-Windows is using it for the mouse pointer, would
accessp K-Windows? Are there other VSC features that we aren't using or
don't have access to?
 
    Whether DMA or the PIXAC is the answer to the CD-i speed difference, 
the reason for their underutilization on the MM/1 is tied directly to
K-Windows, and how Kevin decided to use them. As much as I love
K-Windows and regard Kevin Darling as a top-notch programmer, I don't
think he wrote K-Windows with optimizing graphics manipulation in mind,
whereas CD-i was designed with just that purpose in mind. Can we gain
access to these underutilized features of the MM/1 hardware without
wreaking havoc on K-Windows and remain "within the rules" of OS9?
 
    Are both of these options incorrect, and there's another reason for
the performance difference?
 
...Eric...
...Internet: MREGC@delphi.com
 
--- RiBBS v2.10        
 * Origin: Ocean Beach BBS 619-224-4878 MM1 TECH moderator (1:202/745)

=*= FIDO ECHO MESSAGES MENU =*=

<1> Scan  \
<2> Read   > OS9 Echo mail             
<3> Leave /
<4> Scan  \
<5> Read   > CoCo Echo mail
<6> Leave /
<7> Scan  \
<8> Read   > CoCo_Club Echo mail
<9> Leave /
<A> Scan  \
<B> Read   > MM1_TECH Echo Mail
<C> Leave /

<G>o back to Main Menu
<P>revious Menu (Messages Menu)

[57] Command >>>