read new nonstop follow
92539 7-MAY 15:25  General Information
     RE: Fest (Re: Msg 92538)
     From: CARL_D       To: 01GEN40

Whoops Lv 2. actually.  I've seen Lv 3. or at least most of it up and running
at the last cocofest.  Needs a little work but I think it will be available as
a set of patches.

-*-

92540 7-MAY 16:06  General Information
     RE: Fest (Re: Msg 92539)
     From: MITHELEN     To: CARL_D

Actually, it is Level 2, Version 3.0... The "Mythical" Upgrade... Level 3
OS-9 was something done in Japan (from my understanding) and supported
virtual memory (using disk space as additional RAM). I've never seen
it, just heard rumors of it. I don't think anyone in the US has a copy of
it... I believe it ran on a 6809 system by Fuji...
--
Paul

-*-

92545 8-MAY 00:17  General Information
     RE: Fest (Re: Msg 92540)
     From: CARL_D       To: MITHELEN

Ahh... well I'm sure you know better than I.  I'm still an OS-9 neophyte trying
to get Multi-vue running the way I want.

-*-

92579 14-MAY 11:40 General Information
     RE: Fest (Re: Msg 92539)
     From: 01GEN40      To: CARL_D

  I would guess, that to get a true "Level 3", that these patches
would have to be done to the "out-of-box" OS-9 Level 2.  I have
done quite a lot of patching to get "MY" OS-9 to where it is to-
day.
  After having a bad hard drive crash some months ago, I had to
rebuild my whole boot.  The only backup I had was that of my
floppy boot days and it had very few patches done.  I now have a
backup boot, on floppy, that is identical to the boot on
this hard drive, with a few exceptions such as drivers and dis-
criptors.  I still have some tweeking to do such as when I am
online, I am getting lost characters again and I get "garbage"
characters now and then when text is being displayed.  I thought
I had the right comm driver and discriptors, or maybe it was some-
thing else that I did to fix this.  I have to make the time to
research my steps and fix it.  I suppose I could sacrifice watch-
ing Star Trek, but I do not like that idea so...
  Thanks for the reply...  See ya among the stars....

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

92590 14-MAY 22:29 General Information
     RE: Fest (Re: Msg 92579)
     From: DBREEDING    To: 01GEN40

 > The only backup I had was that of my
 > floppy boot days and it had very few patches done.  I now have a
 > backup boot, on floppy, that is identical to the boot on
 > this hard drive,

I kept a CONFIG_DIR on my hard drive that contained a complete MODULES
dir and all the good stuff, along with a few bootlists for different
applications.  In addition to this, I kept a backup of this on a floppy
disk.  That way, I could always os9gen a new boot disk..

Umm, from your message, it appears you boot from the HD.. but my method
should work, too..

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92658 21-MAY 12:21 General Information
     RE: Fest (Re: Msg 92590)
     From: 01GEN40      To: DBREEDING

Hi Dave,
  Yes, I do boot from my HD.  I hate waiting an hour (exageration) for
the CoCo to boot from floppy.  I do have a floppy that I keep custom
modules on but for some reason I never thought to save ALL of my mod-
fied modules as well.  I did have a backup boot for my           HD, on floppy
but I found that I could not boot from it, reason unknown.  I do have
a bootable backup of my current HD now, as a matter of fact, I boot
from it when I tried to get this RLL HD setup.  I am going to use the
RLL HD as an MFM and will keep a bootable floppy copy as well.  I am
going to save my modified modules to directory on it as well, maybe
even on a seperate floppy.  There IS something to be said for redun-
dancy, I guess!
  Thanks for the reply...  See ya among the stars...

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

92668 21-MAY 15:07 General Information
     RE: Fest (Re: Msg 92658)
     From: DBREEDING    To: 01GEN40 (NR)

 > Yes, I do boot from my HD.  I hate waiting an hour (exageration) for
 > the CoCo to boot from floppy.  I do have a floppy that I keep custom
 > modules on but for some reason I never thought to save ALL of my mod-
 > fied modules as well.  I did have a backup boot for my           HD, on
 > floppy
 > but I found that I could not boot from it, reason unknown.

I'd guess that you would have to have 2 seperate versions of the stuff that
goes on track 34 to get the different boots..  That's one reason I never
attempted to get a HD boot going.  Ummm.. when you say boot, you have your
OS9Boot on HD, too?  I did modify my stuff to look on the HD for the startup,
grfint, shell, etc.

 >  I do have
 > a bootable backup of my current HD now, as a matter of fact, I boot
 > from it when I tried to get this RLL HD setup.  I am going to use the
 > RLL HD as an MFM and will keep a bootable floppy copy as well.  I am
 > going to save my modified modules to directory on it as well, maybe
 > even on a seperate floppy.  There IS something to be said for redun-
 > dancy, I guess!

Well, for the way my system (and probably everyone else's) is patched, I'd
hate to have to go back and recreate all the patches.  I don't think anyone
could get _too_ redundant on making backups of your config disk <G>

One other thing I did was that I kept a text file (UpDateLog or something)
that listed all the CRC's approximate insallation date, and short description
for each file (patched ones, at least) in my modules dir..

Then, too, I had PowerBoost, so I kept a 6809 Modules directory and a PBoost
modules directory...  and the list goes on  <hehe>

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

End of Thread.

-*-

92541 7-MAY 19:40  OSK Applications
     Linkup
     From: MRGOOD       To: BOISY

Boisy,

Just wanted to send some kudos your way for Linkup.  It has become
a very nice program.  The only other thing I would add is the ability to
attach sounds to buttons.  That way, I could use the "click" sound file!

Hugo

-*-

92542 7-MAY 19:46  OSK Applications
     RE: Linkup (Re: Msg 92541)
     From: RICKLT       To: BOISY

I wanted to also add my thanks.  Rick

-*-

92544 7-MAY 23:41  OSK Applications
     RE: Linkup (Re: Msg 92541)
     From: JOHNBAER     To: MRGOOD


  Hugo, Boisy,

> The only other thing I would add is the ability to attach sounds
> to buttons.  That way, I could use the "click" sound file!

  Neat idea!  And Boisy, did any of the sound files I sent to you
work out?  I know some were `off the wall'.  :)

  John -


-*-

End of Thread.

-*-

92543 7-MAY 23:37  General Information
     RE: os-9 HALP!!! (Re: Msg 92533)
     From: DBREEDING    To: CARL_D

 > Not so atuomatically at all.  MV want's unmodified disks to install on.  I
 > edited the bootlist.mv files for 40d.dd but when I try to use os9gen I
 > get error #21

I don't think I had any problems like this when I installed it.  MV simply
does system read and write calls and wouldn't have any problem with what
kind of drive you are using.. You can go to floppies, HD's or ramdisk,
or whatever.

Just went to my coco and checked for error 21.. It says "Illegal Dimension".
This looks like a Basic09 error..

Is this error coming in when you try to run "os9gen"?  Ummm... did you also
change your "/dd" descriptor?  It accesses "/dd", so this could be your
problem.

 > Not sure just what I'm doing wrong.  Thanks in advance for any help.

Well, I'm sure you will get it worked out, but the problem is not in
M-V itself.  It's probably some little thing that is so simple you're
overlooking it.  Be sure your /dd is fixed, too.  This is a very good
possibility, although, you should have gotten a different error.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92546 8-MAY 00:20  General Information
     RE: os-9 HALP!!! (Re: Msg 92543)
     From: CARL_D       To: DBREEDING

That should have been #216, Delphi hiccuped right then and I didn't realize
that it had dropped the last digit.  Still haven't got it going on 40d.dd is it
possible to start MV from the OS-9 command line rather than booting driectly
from the MV disks?  This would really solve my problems easily.

-*-

92549 8-MAY 21:07  General Information
     RE: os-9 HALP!!! (Re: Msg 92546)
     From: DBREEDING    To: CARL_D

 > That should have been #216, Delphi hiccuped right then and I didn't
 > realize that it had dropped the last digit.

OK.. That sounds more like it.. Then it's looking for a file and not
finding it.  Is it showing this error on bootup?  Before you see any
OS9 command line or anything?  Usually, if startup errors, it just quietly
goes to the command line and says nothing, but whatever was supposed to
have happened after that error does not happen.

Error 216 means that it's looking for a file (program) that is not there.
You _DO_ have startup, on that disk??  For MultiVue, you need several files
and programs.  In your CMDS dir, you need "MULTISTART", "GSHELL", and
"CONTROL".  Also, if you have a copy of "MULTISTart" in the cmds dir,
with the filename "AUTOEX", then it will autoboot into M-V on startup.
Otherwise, you can include the command "multistart" as the last line of
startup.  If you don't have "autoex" in your cmds dir and want it, all you
have to do is chd to cmds and type "copy multistart autoex".  This will give
you an exact copy of "multistart" but will execute as soon as "startup" is
done.

One other file you need, and I would bet this is the one that is causing the
error... You need the file "env.file" in your SYS directory.

 > Still haven't got it going on 40d.dd is it
 > possible to start MV from the OS-9 command line rather than booting
 > driectly from the MV disks?  This would really solve my problems easily.

Sure.  Just type "multistart"..  But I don't think this is the cause of your
problem.. You have one or more files missing.

If you don't have the file env.file in your SYS directory (it is on the
distribution disk), if you have the docs, there is a listing for that file
in there.  You can input it with any text editor.  You might want to change
a few things.  It specifies how much memory you have, what disk devices you
have, custom palette colors, printer specs, and several other things.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92550 8-MAY 22:02  General Information
     RE: os-9 HALP!!! (Re: Msg 92549)
     From: CARL_D       To: DBREEDING

Thanks David.
Yes I have the docs for MV, original and unopened in the shrink wrap yet. The
problem comes in when I try to create a new boot disk from the MV disks.
It puts the first file name on the screen and then errors with #216.  The
second file in bootlist.mv is init, I checked and it's in there.  Oh and
I did change the env.file to 512K.

-*-

92552 9-MAY 01:15  General Information
     RE: os-9 HALP!!! (Re: Msg 92550)
     From: DBREEDING    To: CARL_D

 > Yes I have the docs for MV, original and unopened in the shrink wrap yet.
 > The problem comes in when I try to create a new boot disk from the MV
 > disks. It puts the first file name on the screen and then errors with
 > #216.

Do you mean you get this error when running "os9gen"?  Are you doing this
straight with os9gen or are you using "config" (or whatever that name is...).
I never did use it.  I always used os9gen.  If you are getting this error
using os9gen, then you probably have one of your filenames not correct for
what you have in your directory.

 > The second file in bootlist.mv is init, I checked and it's in there.

Is it init that it's not finding?  Do you have it with a different filename
and in the correct directory?  Remember that os9gen is looking for a filename,
not necessarily a module name.  What I did was put all my boot modules in
one MODULES directory.  Like, when I got MV, I copied all those modules to
the directory with the rest of the modules.

One thing  you might do.  If os9gen is bombing on you..  You should have
a file on your new disk, probably "tmpboot".  Do an "ident -s" on that
file and see exactly what modules have been included.  You mention filenames
being echoed to the screen.  I can't remember this, but maybe so.. Oh, if
it puts one filename on the screen, then this first one may be the one
that it can't find..  and I suspect it _is_ this first one... check your
filenames.  Your ident will tell you.  Whatever the next filename after
the last one is the culprit.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92556 9-MAY 12:35  General Information
     RE: os-9 HALP!!! (Re: Msg 92552)
     From: CARL_D       To: DBREEDING

I'll try that and let you know, thanks.

-*-

End of Thread.

-*-

92547 8-MAY 00:31  General Information
     RE: RLL HD Troubles. (Re: Msg 92537)
     From: WDTV5        To: 01GEN40

An RLL as an MFM? ubetcha! I'm doing exactly that at the office right
now, useing a clapped out St-238r as an ST-225. The only diff there in
fact was that the 238 had plated disks which were supposedly better
quality. In use, they aren't, I have 2 of them around and they both
couldn't keep a fat table intact for a month on a million dollar bet!
One was in a pc, and one was on my coco for several years. I'm usning
the old pc drive as the second drive on my office coco, and alltho its
mainly for a backup image, so far in a month it hasn't lost anything
as an MFM drive. Its got some bad sectors marked out, something the
pc utils wouldn't let me do, but the coco can! If you can get the 85 megger,
that would be ideal. I've collected nearly everything around here, plus
I try to maintain all versions of whatever I've written and still have
only about 60 megs of this Maxtor 7120s in use. If I lose this drive,
I'm dead as there isn't a good way to back it up that doesn't take 2
days to do. I'd love to be able to just network it overe to the amiga
where I could back it off to a videotape in 2 hours or less.
I've given thought to attempting that on the coco, but its screen updates
are 50x slower. And no real way to get the data back into it at that
speed either.
Something will turn up in due time though.
Cheers Gene, Gene

-*-

92580 14-MAY 11:58 General Information
     RE: RLL HD Troubles. (Re: Msg 92547)
     From: 01GEN40      To: WDTV5

Hello Gene,
  Well, I think the 85 Megger is no longer available.  The 386
was not up to snuff for use as a server so the boss opted for a
dedicated server and the 386 will be used as one of the worksta-
tions.  I guess I will try to use this RLL as an MFM and see where
that will lead me.  It is quite a shame that an IDE cannot be
interfaced with the CoCo.  Although,  I just had another thought,
maybe I should look into going SCSI.  That is a doer!  Problem
is I would hate to just "throw away" my XT interface with all the
$$$, time and sweat I put into it for the past few years.  Then
again, I could spend some more $$$ and get this ST-238 fixed.  The
darned thing will not hold is speed.  Spindle comes up then just
stops spinning.  I really like the ST-238, much faster than this
clunky old ST-225.  Quieter too!  Oh well, I am getting closer to
having my 486 up and running.  I could just use it, online, in the
interum.  Thanks for the reply...  See ya among the stars...

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

92587 14-MAY 20:54 General Information
     RE: RLL HD Troubles. (Re: Msg 92580)
     From: WDTV5        To: 01GEN40

Tell ya what Gene, the 238 and 225 are identical drives EXCEPT for the
platter coating! The 238 will run as mfm just fine, I'm doing it. I converted
to scsi a year back or a bit more now on my coco, and it was the best thing I
ever did for it. The RLL setup was always in need of file repairs due to
miss-writes covering up already allocated disk area. That was due to some
thing in the interface that would, about once a day, return a sector full
of zero's when the FAT was being read in its search for free disk space.
I changed the controller card from a WD1002-27x to a Seagate St-11r with only
minimal effect on the problem. ALL of the problems went away when I changed
over to a SuperController II with a 4n1. The B&B I had/have was an earlier
all black one which may have had something to do with it. I have a later
Gold colored one at the office merrily running a 10 meg Tandon and a 238 as
a 20 megger in the mfm mode. No mistakes of that nature have ever been made
on THAT system by that setup. It has the MFM version of the ST-11 controller
in it.
If that older B&B was a problem, I would have expected Chris to advise me
of it, but in all our talks, he never said it could be a problem. I was
probably one of the first 10 or so he sold!
Me, I'd go for the scsi myself. On that system (I'm on the amiga at the
moment) I now get a megaread time of 13 seconds! The B&B started out at
71 seconds, and with some fine tuning got down to 49 seconds, but even with
the early pbooster or nitros9, never went any lower. The speed I got from
the scsi using the registerd scsisys2.1 makes all the $ well spent IMO.
Cheers Gene, Gene

-*-

92657 21-MAY 12:06 General Information
     RE: RLL HD Troubles. (Re: Msg 92587)
     From: 01GEN40      To: WDTV5

Hello Gene,
  Thanks for the info.  I have allocated time this afternoon to set
the 238 up as an MFM.  I may seriously think about SCSI!  Our dedi-
cated server (new 486) at work has a SCSI drive in it and I am really
impressed with the speed.  You may find this hard to believe, I do,
but the server is a DX/33Mhz and it seems to be faster than the
486DX2/66Mhz that I am using right now.
  Right now, all we have is an old 386DX/25Mhz networked to the
server and it seems to access much faster than it did when networked
to my DX2/66.  But then, we were running Novel Personal Netware, now
we have Netware 3.1, (a real network software).  I will keep you
posted as to my progress with the 238, thanks for your insight.
  Thanks for the reply...  See ya among the stars...

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

92660 21-MAY 13:10 General Information
     RE: RLL HD Troubles. (Re: Msg 92657)
     From: WDTV5        To: 01GEN40

It should oughta work just fine. If it doesn't, I'll be *very* surprised.
Cheers Gene, Gene

-*-

End of Thread.

-*-

92548 8-MAY 04:22  General Information
     RE: mpi 26-3124 (Re: Msg 92343)
     From: TFLATLEY     To: TAULBORG

Steve,
     Were you able to purchase the upgraded multipak that someone offered,
or do you still need to upgrade the one that you have?  If the latter,
what sort of help do you seek... how-to instuctions, hardware, both?
Please let me know and perhaps I can offer some assistance.   ---tom

-*-

92567 13-MAY 00:17 General Information
     RE: mpi 26-3124 (Re: Msg 92548)
     From: TAULBORG     To: TFLATLEY

I have a friend here in the area that is planning to upgrade my other
multipak for me,he is making the upgrade himself but please keep in
touch be cause if we can't do it here I will send it to Marty.
He has done work for me before and even helped me the price.
If you have an upgraded multipak for sale or any info on upgrade
kits please let me know.
Thanks,Steven P Taulborg

-*-

92568 13-MAY 01:30 General Information
     RE: mpi 26-3124 (Re: Msg 92567)
     From: NIMITZ       To: TAULBORG

I have an upgraded Multipak in stock.  Bought on request of another CoCo
owner who now no longer  lives at the previous contact address.  Please
EMail me if you are interested in this.



-*-

92600 16-MAY 00:11 General Information
     RE: mpi 26-3124 (Re: Msg 92568)
     From: TAULBORG     To: NIMITZ

How much including shipping for the upgraded multipak?

-*-

92610 17-MAY 01:20 General Information
     RE: mpi 26-3124 (Re: Msg 92600)
     From: NIMITZ       To: TAULBORG


I'd like $65 + $5 S/H.

-*-

92621 17-MAY 23:30 General Information
     RE: mpi 26-3124 (Re: Msg 92610)
     From: TAULBORG     To: NIMITZ

Sorry but for me right now that is a little steep.Thanks anyway!!

-*-

End of Thread.

-*-

92551 9-MAY 00:05  General Information
     linkup
     From: WA2EGP       To: ALL

I've heard some cheers for uplink but I can't seem to get it running on my
MM/1.  Once I click the mouse on the OK, the arrow disappears and a second
or so later, the machine reboots.  I am using windio #54.  What simple thing
did I forget?  Help is appreciated.

-*-

92557 9-MAY 20:49  General Information
     RE: linkup (Re: Msg 92551)
     From: JOHNBAER     To: WA2EGP


> I am using windio #54.  What simple thing did I forget?

  Did you make a directory on /dd called `samples' (just in case) ?
That's the only thing I can think of at the moment...

  I just put all exec. files in cmds, made the /dd/samples directory
and put the sound files there.  The first time I called it, I used
the redirection thing..  `linkup <>>>/w&' and I was sitting at /dd
also.  Other than that, I don't know :(

  John -


-*-

92558 9-MAY 20:56  General Information
     RE: linkup (Re: Msg 92557)
     From: WA2EGP       To: JOHNBAER

I'll check.  Geez...been a week since I played with it so I don't remember.
Thanks for the help.

-*-

92572 13-MAY 23:23 General Information
     RE: linkup (Re: Msg 92551)
     From: BOISY        To: WA2EGP

Hey Robert,

Are you running with WCF?  Do a dump of your /term and /w descriptors
to see if you are using WCF as the file manager.

I'm puzzled by this, as I cannot find anyone else with a 68070
who's using LInkUp and encountering this problem.

Why don't you send me a mdir -u of your system.

-*-

92601 16-MAY 00:33 General Information
     RE: linkup (Re: Msg 92572)
     From: WA2EGP       To: BOISY

OK, Will send in email.

-*-

End of Thread.

-*-

92553 9-MAY 09:16  General Information
     Visability
     From: TMF          To: ALL

I full agree that we need to be seen more on Delphi and on Compuserve .

-*-

92560 9-MAY 21:27  General Information
     RE: Visability (Re: Msg 92553)
     From: THETAURUS    To: TMF

 We need to be seen whereve
er' wherever we can flash our mugs<G>.

 Course it gets me down to always see OS-9 on Milk Cartons....

 >Chris<
 OS-9 User's Group Project Co-ordinater

-*-

92581 14-MAY 12:16 General Information
     RE: Visability (Re: Msg 92560)
     From: 01GEN40      To: THETAURUS

Hi Chris,

<OS-9 on Milk Cartons....>

  Are you trying to tell us that OS-9 is a missing and/or exploited
child?

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

92582 14-MAY 13:31 General Information
     RE: Visability (Re: Msg 92581)
     From: THETAURUS    To: 01GEN40

 >> Are you trying to tell us that OS-9 is a missing and/or exploited child?

  O mI mean to say that I hope we don't get so low in promotion abilities that
 we have to put OS-9 on a carton, sayin "Have you seen me?" <G>

 >Chris<

-*-

92656 21-MAY 11:48 General Information
     RE: Visability (Re: Msg 92582)
     From: 01GEN40      To: THETAURUS

Hi Chris,
  I do not know about the rest of the country, or world for that mat-
ter, but, here in San Diego, Ca. there is a yearly Computer/Software
Expo that is put on by the S.D. Computer Society and a leading compu-
ter magazine publishing company.  They have exhibit booths with MAJOR
computer/software/etc. companies displaying their wares.  Our own
OS-9 Users Group has a booth set up to display/demonstrate all flavors
of OS-9.
  I went to the one last year and saw that there were quite a number
of people observing and or asking questions about OS-9.  This goes on
for 4 days, at least it will this year.  I only went last year because
I found out that OS-9 was going to be there.  I am not very active in
the group (what with time constraints and whatnot), but I will be
there again this year as a "spectator".
  I think this would be an excellent way to get OS-9 into the minds
of the masses.  If they can see what OS-9 can do, right along side of
MS-DOS, I think they may become more interested.  At least those who
do not rely on WINDOSE to do there work for them.
  Thanks for the reply...  See ya among the stars...

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

92674 21-MAY 22:22 General Information
     RE: Visability (Re: Msg 92656)
     From: THETAURUS    To: 01GEN40 (NR)

 Agreed. Hopefully we will be able to get OS-9 represented in many more
 future computer shows(besides JUST the Cocofests). We need to get a
 list of annual shows compiled(part of the sourcebook), and then maybe
 develope some sort of promotional compaign that can be in use at the fests.
  I agree, it is a great way to get our foot in the door, and would love to
 see someone take that up!

  Chris Perrault

  OS-9 Users' Group
  Sourcebook Coordinator

-*-

92677 22-MAY 00:56 General Information
     RE: Visability (Re: Msg 92656)
     From: NIMITZ       To: 01GEN40 (NR)

True story, as far as it goes.  But sales are still made at OS-9 only fests,
not mixed fests.  Advance marketing, as full a vendor attendence as
possible, and no outside competetion are going to be key factors in building
the sales from the existing market, in order to have the revenue to grab
attention of people outside the current OS-9 users base.  We have to work at
both, and I see lots of attention to getting new users, but little work to
lay the financial groundwork necessary to pay for the marketing work.



-*-

End of Thread.

-*-

92554 9-MAY 09:45  Users Group
     RE: 6309 cpu (Re: Msg 92530)
     From: JEJONES      To: WILLIAMSON68

 > Does anyone know if the hd63c09e is compatible with nitros or will nitros
 > run only with the 6309b variety?

The letter A, B, C indicates the maximum clock speed the chip is rated for.
C = 3 MHz, so it should run just fine with the (slightly under) 2 MHz clock
that the CoCo feeds the CPU.

Opinions herein are solely those of their respective authors.

-*-

92555 9-MAY 09:45  Programmers Den
     CDL BASIC question
     From: JEJONES      To: FHOGG

How would one write the following in CDL BASIC?

PROCEDURE fibonacci
   PARAM i,term:INTEGER
   DIM  penult,antepenult:INTEGER

   IF i < 3 THEN
      result:=1
   ELSE
      RUN fibonacci(i-1,penult)
      RUN fibonacci(i-2,antenpenult)
      result:=penult+antepenult
   ENDIF
   END


Opinions herein are solely those of their respective authors.

-*-

92561 10-MAY 08:49 Programmers Den
     RE: CDL BASIC question (Re: Msg 92555)
     From: JEJONES      To: JEJONES

Duh..."term" should of course be "result".  Just goes to show that testing
is important. :-)

Opinions herein are solely those of their respective authors.

-*-

92593 14-MAY 23:09 Programmers Den
     RE: CDL BASIC question (Re: Msg 92561)
     From: FHOGG        To: JEJONES

 >How would one write the following in CDL BASIC?

Well perhaps I'm not with the program as it were but I can't get this to run
under
68K Basic. I passed this on to Mike and he is not sure what you are looking
for. Could you enlarge on this.

Frank

-*-

92612 17-MAY 07:42 Programmers Den
     RE: CDL BASIC question (Re: Msg 92593)
     From: JEJONES      To: FHOGG

 > Well perhaps I'm not with the program as it were but I can't get this to
 > run under
 > 68K Basic. I passed this on to Mike and he is not sure what you are
 > looking for. Could you enlarge on this.

Basically, I'm asking whether CDL BASIC functions can be recursive.


Opinions herein are solely those of their respective authors.

-*-

92626 18-MAY 01:04 Programmers Den
     RE: CDL BASIC question (Re: Msg 92612)
     From: NIMITZ       To: JEJONES

James, the functions should certainly be recursive.

give me an example in Basic09 and I'll translate and  run it for you.



-*-

92639 20-MAY 10:43 Programmers Den
     RE: CDL BASIC question (Re: Msg 92626)
     From: JEJONES      To: NIMITZ

 > give me an example in Basic09 and I'll translate and  run it for you.

The Fibonacci sequence procedure in my message to FHOGG (with the correction
in the reply <blush>) should do fine.

Opinions herein are solely those of their respective authors.

-*-

End of Thread.

-*-

92559 9-MAY 21:26  OSK Applications
     VCDP
     From: VAXELF       To: ALL

  What is the correct VCDP file to use with the double speed CDROM that
was sold at Chicago Fest??? I have tried each one and they all lock up
my MM/1. The CDROM is working great. I can access CDROMS just fine and the
data on them. It's when I try and use a music CD and VCDP that it goes
bonkers.

John D.

-*-

92566 12-MAY 23:48 OSK Applications
     RE: VCDP (Re: Msg 92559)
     From: TEDJAEGER    To: VAXELF

 > What is the correct VCDP file to use with the double speed CDROM that
 > was sold at Chicago Fest??? I have tried each one and they all lock up
 > my MM/1. The CDROM is working great. I can access CDROMS just fine and
 > the data on them. It's when I try and use a music CD and VCDP that it
 > goes bonkers.

 I've been here before! My VCDP has a CRC of $AE0F14. BUT, the problem I
 had was that my MM1 I/O board had an early Western Digital SCSI chip,
 not revision A, and I had to change my chip before I could use VCDP. You
 must have revision A of that SCSI chip for VCDP to work.



Bests
---TedJaeger

-*-

92570 13-MAY 18:00 OSK Applications
     RE: VCDP (Re: Msg 92566)
     From: WDTV5        To: TEDJAEGER

Sounds about right, we have had a heck of a time with earlier WD33C93's
over on the Amiga's. I think you want to locate a revison 8 chip. Check
out the adds in any amiga rag.
Cheers, Gene

-*-

92571 13-MAY 21:33 OSK Applications
     RE: VCDP (Re: Msg 92566)
     From: VAXELF       To: TEDJAEGER

  Chris from Hawksoft also mentioned that. Also you need ED #27 of
SCSI_M1D too. Since mine is a Paul Ward system, I suppect it may well be
the chip. Thanks for the reply.

John D.

-*-

92573 13-MAY 23:43 OSK Applications
     RE: VCDP (Re: Msg 92571)
     From: RANDYKWILSON To: VAXELF

John,

 My MM/1 is very early production PKW; number 27 I believe. It has the correct
chip in it. I suspect it is only the first 10 or so units, or maybe some
later ones.

   Randy

-*-

92577 14-MAY 10:55 OSK Applications
     RE: VCDP (Re: Msg 92571)
     From: TEDJAEGER    To: VAXELF

 > Chris from Hawksoft also mentioned that. Also you need ED #27 of
 > SCSI_M1D too. Since mine is a Paul Ward system, I suppect it may well be
 > the chip. Thanks for the reply.

 I forgot to say that not only the revision of the chip (need revision A)
 but also the mask number is critical. Apparently the MM1 was designed
 around mask #2 or mask #4 of the prototypes of that Western Digital
 SCSI chip. In the Amiga World they refer to these as PROTO versions of
 the chip because PROTO is printed on it. So having the right chip to
 work with VCDP requires the WD33c93 revision A, mask #2 or mask #4,
 with PROTO also printed on the chip. My machine was a Paul Ward MM1
 to and the SCSI chip was not revision A and  therefore minus a few
 instructions that VCDP needs.

Bests
---TedJaeger

-*-

92578 14-MAY 10:55 OSK Applications
     RE: VCDP (Re: Msg 92573)
     From: TEDJAEGER    To: RANDYKWILSON

 > My MM/1 is very early production PKW; number 27 I believe. It has the
 > correct
 > chip in it. I suspect it is only the first 10 or so units, or maybe some
 > later ones.

 Randy,
         Where does one look to find the production number of their MM1?
I happen to have one that was originally won in a raffle by a lady (from
Tennesee I think) at a CocoFest in Atlanta when the MM1 was first introduced.
David Myers (CoCoPro fame) later bought the machine from her and I bought it
from David. Later I bought the I/O board from someone named Colin in Oklahoma
who had bought an early Paul Ward MM1. This assortment of circuity has
worked perfectly for years now with the exception of my needing to replace
that WD33c93 (no revision A) chip. I guess I'd just like  to know something
more about the historical lineage of these pieces!

Bests
---TedJaeger

-*-

92583 14-MAY 15:36 OSK Applications
     RE: VCDP (Re: Msg 92573)
     From: VAXELF       To: RANDYKWILSON

  Mine is SN 120877, so it might have the right chip. I still need to take
the top off and look. If it is the right chip, then all I need is to replace
my SCSI_MM1D ED #25 with ED #27.
  Thanks for the info. BTW RIBBS_OSK is doing real well. Contact Warren and
he has his up and running each night from 5 to 9 PM PDT. I can provide you
with a BETA disk. We are on the verge of having real FIDO net mail. When
we do and is reliable, then Warren plans to switch to RIBBS_OSK. It is
running with LOCK baud support. Bill Chapple figured out how to use the
DTR line on the uarts to hang up the bbs. A bunch of people got copies at
Chicago Fest. We had two MM/1's running, with one with RIBBS_OSK at 38400
baud locked and the other running KTerm V3.0. Real impressive. Warren and
I have been looking at interfacing RIBBS_OSK and UUCP for Internet Access.
It works until you logoff UUCP, then it locks up. Calvin Dodge thinks the
problem is in "checkcd". He has done a fantastic job with the assembly code.
Ribbs_OSK is real stable. Under normal operating, it has yet to bomb with
a 103 or 102 error. If it does error, it has always recycled. TTY,ANSI, &
OS9 modes are working great.
  If you get a chance call Warren's BBS durning the evening and see the
fruits of all our labors.

John D.

-*-

92584 14-MAY 15:39 OSK Applications
     RE: VCDP (Re: Msg 92577)
     From: VAXELF       To: TEDJAEGER

  Randy K. Wilson, who also has a PKW MM/1, thinks it maybe only the
earlier versions of the MM/1. His has the correct chip.

John D.

-*-

92585 14-MAY 17:43 OSK Applications
     RE: VCDP (Re: Msg 92577)
     From: VAXELF       To: TEDJAEGER

  I just checked my SCSI chip. Looks like I am in luck and only need to
upgrade my SCDI_MM1d to ED 27. here is what I got off my chip

WD33C93A-PL

00 - 04 PL
PROTO


John D.

-*-

92586 14-MAY 19:24 OSK Applications
     RE: VCDP (Re: Msg 92578)
     From: RANDYKWILSON To: TEDJAEGER

I'm not sure about the prototypes. The first batch of production boards
had serial numbers of 1208xx. Mine is 27. I ordered mine at the cocofest
that that raffle/drawing took place. Deliver happened.... ummm... a bit
later. My two boards have matched numbers, but it appears yours won't.
Non-matching numbers will cost you points in the next concourse. :>

 Randy

-*-

92596 15-MAY 02:09 OSK Applications
     RE: VCDP (Re: Msg 92570)
     From: NIMITZ       To: WDTV5

Does this mean you might know of a source for earlier 33c93 chips?

I could use some to fix about 20 MM/1 I/O boards.......


David


-*-

92597 15-MAY 21:23 OSK Applications
     RE: VCDP (Re: Msg 92585)
     From: TEDJAEGER    To: VAXELF

 > I just checked my SCSI chip. Looks like I am in luck and only need to
 > upgrade my SCDI_MM1d to ED 27. here is what I got off my chip
 >
 > WD33C93A-PL
 >
 > 00 - 04 PL
 > PROTO

 You're in perfect working order!! I must have been the only lucky soul
 to obtain a WD33c93 chip!

Bests
---TedJaeger

-*-

92598 15-MAY 22:32 OSK Applications
     RE: VCDP (Re: Msg 92596)
     From: WDTV5        To: NIMITZ

Not in that quantity I'm afraid. In this case, I think I'd be tempted to
contact the author of the driver and see if he could bring it up to later
standards. Or share the source with someone who really does breath the
scsi1 and scsi2 language. The earier chip did have some bugs, in fact
the inside front cover of the AA I got today has an add for (an ex GVP empl)
latest revision of the scsi.device rom with workaraounds for all known
variations of that chip. So it can be done. I wish I had better advice
David. Can you spec the exact version you need to the wholesalers and
convince them that later versions just won't fly in this app? There might
be a few laying around, and its one of those projects that will blow the
fone budget all to he!!. I know, I've done that a couple of times finding
the exact item I needed there at the station. I've got one chip I think,
lemme check it. Its on an A2090a commie hd board I took out. The scsi on
this board is considered unusable by most, but thats more the rom version
than the chip I think, it didn't support any "scsi direct" commands, an
item that MUST be fully implemented if a cdrom is ever going to work.
The chip on this board is: WD33C93-PL on the second line, has an "85 date
on the top line with line 3=00-02 8736
This one shared space with a KONAN MFM controller and was supposed to be
able to handle 2 MFM drives and 5 scsi drives. As I said, few ever made the
scsi work, and the commie folks themselves say even the latest rom they
have for it isn't worth the effort to plug in. But you are welcome to it
if you can use that revision. This one doesn't say "PROTO" anywhere on it.
Cheers David, Gene

-*-

92609 17-MAY 01:20 OSK Applications
     RE: VCDP (Re: Msg 92598)
     From: NIMITZ       To: WDTV5

Gene, I'd appreciate it if I can get a copy of that article, as it may have
some direct bearing on my problem.  We switched from 40 pin DIP package to
PLCC in the new I/O boards.  This may be a big help.  BTW - my own chip does
not say proto, but does note the mask number.  I might well be able to use
that chip.  How much do you want??



-*-

92618 17-MAY 22:40 OSK Applications
     RE: VCDP (Re: Msg 92596)
     From: TEDJAEGER    To: NIMITZ

 > Does this mean you might know of a source for earlier 33c93 chips?
 >
 > I could use some to fix about 20 MM/1 I/O boards.......

 David,

     When I went looking for a replacement chip for my WD33c93 chip I
posted on USENET to Amiga groups and got 6 offers of people willing to
sale me the needed WD33c93A mask #2 or mask #4. They had upgraded SCSI
controllers (to deal with larger capacity HDs in some cases) and were
happy to unload the PROTO chips for around $10-15. I installed a
socket and things work fine.

Bests
---TedJaeger

-*-

92619 17-MAY 22:41 OSK Applications
     RE: VCDP (Re: Msg 92609)
     From: WDTV5        To: NIMITZ

Unforch, those quotes (or unquotes) are from hints and tips passed on
over in the Ami forum and usenet over the last year. The general consensus
seems to be that the only clean chip in the lot has a -08 on the end, but
that it may in turn require later versions of "scsi.device", the driver
software thats normally part of the card/eprom for the scsi interface.
As I said, mine is early, 40 pinner, and between it and the early eproms,
it is crash city if you try to run a cdrom with it, and normally locks
up the buss requireing a reboot hourly or more often.  The lockups can
happen in mid-write, leaving the drive invalidated, a major headache to
clear at times. We've even had to format and start all over!  Price?
Make me an offer in my mailbox here. Cheers david, gene

-*-

92627 18-MAY 01:04 OSK Applications
     RE: VCDP (Re: Msg 92618)
     From: NIMITZ       To: TEDJAEGER

Thanks, Ted.  I'll try that!



-*-

92641 20-MAY 19:16 OSK Applications
     RE: VCDP (Re: Msg 92627)
     From: TEDJAEGER    To: NIMITZ

 > Thanks, Ted.  I'll try that!

 David,
       Miraculously, I still have the email communications from a couple
of  people who offered to sell me their WD33c93A SCSI chips. Try

 1. IN%"maji@u.washington.edu"
 2. IN%"tibor.ecst.csuchico.edu"

Both responded to my message on comp.sys.amiga.marketplace offering the
chip.

Bests
---TedJaeger

-*-

End of Thread.

-*-

92562 10-MAY 19:35 General Information
     68020 - 16   $10
     From: MARTYGOODMAN To: ALL

I have a Motorola pin grid array packaged 68020 - 16 CPU chip
that I removed from what I believe was a working card.
At least, the memory I removed from the same card all tested fine.
I'll happily sell it for $10, shipping included, and if you decide
for any reason you don't want it in the first week after
getting it I'll refund half your purchase price upon return of
the chip.   But I'm pretty sure this is a good chip.    ---marty

-*-

92563 10-MAY 21:50 Users Group
     Users' Group Sourcebook Project
     From: THETAURUS    To: ALL

                    The OS-9 User's Group Sourcebook

         This posting is an overview of the latest OS-9 User's Group
       project. For any updates on this project please refer to the  'The
       OS-9 User's Group' MOTD newsletter, where all official information
       regarding the project will be published as an ongoing series of
       articles. If you are not an OS-9 User's Group member please
       contact the UG at one of the addresses below for more information
       on becoming a member.

         'The OS-9 User's Group' Sourcebook is a project within the UG,
       set up to build and maintain a group of databases containing
       information important within the OS-9 community. The purpose of
       this project is to help keep a centralized source of information
       for people from many ends of the OS-9 world, while preventing
       fragmetation of the this ever changing community. As the
       information is gathered and the sourcebook begins to grow, we, the
       User's Group, will be able to use it as our information foundation
       and as a springboard for launching future projects more quickly,
       as less time will have to be spent gathering information related
       what we will be working with. As a sidenote, I am already planning
       future UG projects that will rely on this very sourcebook.

         Technically, this will not be a hardcopy 'book', as the title
       might have you believe, although any queries coming in from US
       Mail(snail mail) will be answered with the resulting data being
       mailed on paper of course.

         As this will be a permanent, ongoing project we expect that more
       topics will be added in the future, as we get feedback from the
       membership, but these are categories that will be collected first
       to get the sourcebook started:

         USERLIST:  This will contain names of individuals like you and
       me who use OS-9 for any purpose. A form will be added in the
       following post for users to fill out and return at the appropriate
       address(below). Whether you use it at home or at work or wherever,
       we want your name added to this list so we can keep EVERYONE in
       touch. It is especially important that we get the names of people
       who don't have the benefit of a modem or an Online service. If you
       know someone in your area who fits this criteria, please let them
       know what is going on, and have them send the information
       requested in the form!

         Local Clubs and User Groups:  Small regional clubs in the OS-9
       world sometimes go on unheard of even by people IN THEIR AREA, let
       alone in the national online scene. If you are a member of such a
       group please fill out the form that will be posted in the near
       future(all forms will also be in the MOTD for people to mail in
       through US Mail). It is the intent of the UG to help keep members
       and clubs plugged in to eachother and avoid dwindling membership.
       A future project will tackle this issue.

         Bulletin Board Services,Online services, and Internet sites:
       Well these will actually be three seperate databases, but you
       probably already get the idea on these. It will be similar to many
       other independently kept BBSlists, but will be kept more up to
       date and will serve as the official OS-9 BBS database.

         Publications:  All OS-9 related Magazines and newsletters.

         Vendors:  If you run a business selling OS-9 Products or
       services, we will be able find customers for you and you for the
       customers that are looking!

         Business' working with OS-9:  If you are a business that uses
       OS-9 within the workplace, including those in our large industrial
       marketplace, we will have an entry form released for you also!

         These are the categories that we will begin with. Keep in mind
       this sourcebook is going to grow with time and input from the OS-9
       community. Once the initial categories are built up, we do plan to
       add an 'Orphanware' topic, but that will be saved for later,due to
       the amount of work it may take to collect all that software.

         You do NOT have to be a member of 'The OS-9 User's Group' to be
       placed in the the sourcebook, but you are of course encouraged to
       become a member and become involved in the future of OS-9. Being
       included in the sourcebook does NOT oblige you to do anything as
       it is a service to the community.

         The entry forms for each category will be individually posted
       online within a short time of eachother. 'The OS-9 User's Group'
       will print each one following the MOTD updates. The first one, to
       be included in the following post, will be the Userlist entry
       form. The next one to appear within a few weeks will be the BBS
       entry form, which Sysops should be aware of.

         If you have any comments, questions, suggestions, or if you want
       membership information you can contact 'The OS-9 User's Group'  at
       the following online addresses:

          os9ug@sandv.chi.il.us [Internet]
          cmckay@northx.isis.org(Colin McKay President) [Internet]


         Or at the following U.S. Mail address:

         The OS-9 User's Group, Inc.
         6158 West 63rd Street
         Suite 109
         Chicago, Il. 60638
         U.S.A

         To be added to the Sourcebook, send your entry form information
       to the Email addresses below. If you wish to send via U.S. Mail,
       use the address above. Also feel free to send any
       questions,comments, or suggestions to these addresses.

          Thetaurus@Delphi.Com  [Internet]
          Chris Perrault at 1:324/117 [Fido Net Address]
          Chris.Perrault%Mvug@e-tech.havr.ma.us

-*-

92564 10-MAY 21:53 Users Group
     RE: Users' Group Sourcebook Project (Re: Msg 92563)
     From: THETAURUS    To: THETAURUS

OS-9 Sourcebook Information Form
--------------------------------
  Name:
       ---------------------------------------------------------------
  Business:
           -----------------------------------------------------------
  Address:
          ------------------------------------------------------------
  City:                 State:                ZIP:
       ----------------       ---------------     --------------------
  Country:                 Telephone:(    )       -
          ----------------           ---------------------------------
  EMail Address:
                 -----------------------------------------------------


  Signature:                                      Date:     /    /
            ------------------------------------         DD   MM   YY

Would you like information on
joining the OS-9 Users Group?         o Already a Member!  o Yes  o No

Can this information be passed to OS-9 vendors?            o Yes  o No

Are you available to act as a volunteer for OS-9           o Yes  o No
projects from time to time?  This isn't a commitment.

Please indicate your area(s) of interest:

   o OS-9/6809      o OS-9/68000      o OS-9000

   o Programming    o Hardware          Other ________________________

You use OS-9 primarily for what purpose:

   o personal use   o industrial system     o both

Please describe briefly your OS-9 computer system(s):



Please describe briefly your computer and OS-9 experience:



Please describe your OS-9 interests (things you would like to see the
UG do, or see in the MOTD), or list any other questions or comments:





-*-

End of Thread.

-*-

92565 11-MAY 23:01 General Information
     hi
     From: VESTALJ      To: ALL

This is Jim Vestal (formally jevestal).

I just wanted to let everyone know that I'm giving up Delphi for a while
in favor of a local internet account.

Do not email this account past the 1st of June and my old account is gone.
You can contact me via email at jevestal@calweb.com

I do read comp.os.os9 once in a while and the CoColist regually so I am
at least keeping in touch.

Later,

Jim

-*-

92574 14-MAY 10:24 General Information
     RE: Atari OS-9 (Re: Msg 92494)
     From: DSRTFOX      To: CARL_D

On 27-APR 16:40 CARL_D said to DBREEDING
   > Someone else mentioned that.  I had no idea it was so expensive, kind
   >of obviates the cheapness of the system.

Atari OS-9 is only $200-$250. Still available from Cumana.. actual cost is
150 pounds sterling...


Francis (Frank) Swygert
Publisher, "the world of 68' micros" Magazine

`[1;30;42mRainbow V 1.11 for Delphi - Registered

-*-

92575 14-MAY 10:24 General Information
     RE: OS-9/68K (Re: Msg 92493)
     From: DSRTFOX      To: DBREEDING

On 27-APR 01:21 DBREEDING said to CARL_D
   > > Actually you can probably find a used Atari ST pretty cheap
   > > these days.  I believe this 68K machine has a version of OS-9
   > > for it.  Could be wrong tho'
   > The only problem with the Atari is that OS9 is ridiculously
   >expensive.  I think it's around $600?  Didn't look, but I think that's
   >right.  You can almost get a terminal system complete with OS9 and all
   >for that price.
   > -- David Breeding --
   > CompuServe : 72330,2051             Delphi :  DBREEDING
   > *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

OS-9 for the ST is 150 pounds sterling from Cumana in the UK.... about
$200-$250. Little support though. Some SCSI systems for the Atari don't seem
to work well with the supplied drivers either.


Francis (Frank) Swygert
Publisher, "the world of 68' micros" Magazine

`[1;32;42mRainbow V 1.11 for Delphi - Registered

-*-

92589 14-MAY 22:29 General Information
     RE: OS-9/68K (Re: Msg 92575)
     From: DBREEDING    To: DSRTFOX (NR)

 > On 27-APR 01:21 DBREEDING said to CARL_D
 > > > Actually you can probably find a used Atari ST pretty cheap
 > > > these days.  I believe this 68K machine has a version of OS-9
 > > > for it.  Could be wrong tho'
 > > The only problem with the Atari is that OS9 is ridiculously
 > >expensive.  I think it's around $600?  Didn't look, but I think
 > that's >right.  You can almost get a terminal system complete with OS9 and
 > all >for that price.

 > OS-9 for the ST is 150 pounds sterling from Cumana in the UK.... about
 > $200-$250. Little support though. Some SCSI systems for the Atari don't
 > seem to work well with the supplied drivers either.

OK, I stand corrected <G>.. Seems like there's SOME platform that OS9 costs
that much, though, isn't there?

Anyway, I would be a little hesitant to try to do anything serious with an
Atari with the Cumana system..  You would probably have lots of things to work
out, and support would be a little uncertain, IMO.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

End of Thread.

-*-

92576 14-MAY 10:24 New Uploads
     CoCoFest
     From: DSRTFOX      To: ALL

We also found a loose part in the rear brakes, which put more of the
stopping effort on the front disks (something I added to the car later...
didn't have those in '63!), and was a definate factor in causing the front
wheel lock-up that actually caused the accident in the first place. Had an
uneventful trip back to Georgia from Chicago.

I took a couple extra days off work when I got back. went down to my dad's
house in South Carolina (4 hour trip), met with some old friends, then took
a fender off a parts car I have there. You don't decide to drive a 30 year
old car on a daily basis unless you know you have repair parts available!
Replaced the damaged fender AND totally rebuilt the rear brakes just because
I had the time and was able to get the new parts locally. Now EVERYTHING
works just great!

All that's left to do is get the thing painted. Unfortunately, while Chicago
was a good trip again, it wasn't quite THAT good! So I'll be driving around
with a faded pink-looking fender for a while. I WAS able to pay for all
other repairs... about $250 including the brakes (biggest expense was
radiator)... and all expenses though. Maybe Atlanta will be good enough for
a paint job.....   Of course, I'll accept all donations.... ;>


Francis (Frank) Swygert
Publisher, "the world of 68' micros" Magazine

`[1;35;46mRainbow V 1.11 for Delphi - Registered

-*-

92588 14-MAY 21:59 OSK Applications
     Ghostscript ver 3.33
     From: JOHNREED     To: ALL

Ghostscript version 3.33 should appear soon in the new uploads
database.

For those who are not familiar with it, Ghostscript is a
Postscript emulator written by L.Peter Deutsch, of Aladdin.
It allows you to display (with a proper driver) and print
Postscript files on just about any decent printer.  With
Ghostscript and the TeX system uploaded by Tim Kientzle,
users can produce documents using just about any font
you can imagine, include graphics, colors if your printer
can do it, design your own letterhead or company logo,
print your own forms, etc.

The following is the "readme.1st" file included in
the upload.
***
Ghostscript version 3.33 was released in April 1995 by Aladdin.

I have ported version 3.33 to OS-9/68000 on the MM/1, and put
together a collection of the files needed to run it, with an
assortment of fonts and demos.  Except for the "kwin" Kwindows
driver, it SHOULD run on any OSK machine.

The complete source, and compiled binaries for MSDOS and some
other systems can be found on ftp.cs.wisc.edu /ghost/aladdin.

This release carries a different Copyright notice than earlier
GNU/FSF releases.  Its in the file called "public".  Read it.

Quick summary of new features since the last version I posted
(version 2.6.1) :  (for a full description of all
changes in recent versions, see files "news", "current", and
"history".)

Reads Adobe PDF (Acrobat) format files.
Reads JPEG files.
 Had a few confusing moments with the JPEG reader -- it bombed
 on the test files supplied with the JPEG-5A lib.  Then I tried
 the "jpegshow" program recently uploaded to DELPHI -- it said
 the files I was trying to read were defective (?!!).  Downloaded
 a couple other JPEG files and found both "jpegshow" and Ghostscript
 read them just fine.
Full Postscript Level II support.
No GIF output -- previous versions would convert a Postscript
 file to a GIF - this has been dropped by the author to avoid
 any possible legal difficulties due to a copyright or patent
 claim on the compression method used in GIF files.  The
 author of Ghostscript, L. Peter Deutsch of Aladdin, posted
 an explanation in comp.lang.postscript.

The Kwindows display driver in this compiled version has a slightly
bigger display - you can read smaller fonts on the screen - and some
improvements in speed in some of the graphics routines.

The printer drivers now send their output to "/p" by default - use
the "-sOUTPUTFILE=<path>" switch in the command line to change it.

In order to keep it small enough to run on a 3-meg computer, I have
NOT included the "debug" features and I picked an assortment of
output drivers that I hope will cover most users.  Apologies to those
I left out. The output drivers included in this version are:

        kwin deskjet djet500 epson epsonc eps9mid eps9high ibmpro
        st800 ap3250 laserjet ljetplus ljet2p ljet3 ljet4 cdeskjet
        cdjcolor cdjmono cdj550 pj pjxl pjxl300 bj10e bj200
        dfaxhigh

If you want to run Ghostscript, and your printer is not (and cannot
emulate) one of the above, let me know.  Maybe I could post some other
versions with different drivers.  (Or in individual cases -- mail a
disk). ((johnreed@delphi.com))

The program passed my 3-meg test (make a 6+meg ramdisk to tie up
memory and try to run it).  There was not a lot of room to spare.

***
Have fun.

John Wainwright

-*-

92592 14-MAY 22:56 OSK Applications
     RE: Ghostscript ver 3.33 (Re: Msg 92588)
     From: DBREEDING    To: JOHNREED

 > Ghostscript version 3.33 should appear soon in the new uploads
 > database.
 >
 > In order to keep it small enough to run on a 3-meg computer, I have
 > NOT included the "debug" features and I picked an assortment of
 > output drivers that I hope will cover most users.  Apologies to those
 > I left out. The output drivers included in this version are:
 >
 > kwin deskjet djet500 epson epsonc eps9mid eps9high ibmpro

Is one close to Epson ESC/P2?  (would epsonc be it?).

 > The program passed my 3-meg test (make a 6+meg ramdisk to tie up
 > memory and try to run it).  There was not a lot of room to spare.

I have a 4 meg system, and GhostScript was the first one to get me down
close to the ragged edge <G>

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92603 16-MAY 19:09 OSK Applications
     RE: Ghostscript ver 3.33 (Re: Msg 92592)
     From: JOHNREED     To: DBREEDING



RE Ghostscript 3.33 drivers for Epson ESC/P2.

 the epsonc driver is for 24-pin color printers.

 the ESC/P2 driver now defines TWO drivers, st800 and
 ap3250.  They are about the same, except for the
 pre-defined margins.  Use the st800 for inkjets, and
 the ap3250 for "Action Printer xxx".

JohnW

-*-

End of Thread.

-*-

92591 14-MAY 22:38 System Modules (6809)
     Booting from another drive
     From: DOMM         To: ALL

I wonder if someone could tell me just what one has to do (patches...etc.),
to be able to boot os9 from ...say...Drive 2, instead of from Drive 0?

THANKX!

---Dom

-*-

92594 14-MAY 23:26 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92591)
     From: RANDYKWILSON To: DOMM

From the OS9 side, it would take modifications to Boot, CC3Go, Init, and
possibly your StartUp. I have no idea what it would take from the DECB
side. You'd have to get the "DOS" command code to look at the new drive.

   Randy

-*-

92595 15-MAY 00:14 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92594)
     From: DOMM         To: RANDYKWILSON

I found that if I "dir 2" in DECB with the OS9 Boot disk in drive 2, then
wait for the File Structure error - OK -, and then DOS... I get the OS9
Boot screen. After a short while it move to /d0.

I just for starters Dmoded all Drive discriptors to be /d2 and then moved
them to the front of the BootFile. I figuered it would take a few patches
to Boot or Init but the next question would be what are the patches or
where could I locate them?

---Dom

-*-

92599 15-MAY 22:53 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92595)
     From: RANDYKWILSON To: DOMM

For Init and CC3go, you will just have to change all occurances of /d0 to /d2.
Boot is a different animal. It directly accesses the hardware. You would
have to patch the point it selects drive 0 to select the drive you want.
I do not know exactly where this is, or how to do it. Sorry.


   Randy

-*-

92602 16-MAY 00:34 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92599)
     From: DOMM         To: RANDYKWILSON

I don't have any assembly knowledge or access to a assembler/dissasembler.
As far as viewing the module(s) in a disk zapper...I haven't looked yet
but I doubt that I could do anything. I just thought that someone had
done these patches along the way and had actual patch data. While reading
the description of a file in the data base, it was mentioned that some
people patch modules to boot from hard drive. Being that a descriptor is
a descriptor, maybe the conversion would be minimal. ???

Thanks anyway!

---Dom

-*-

92604 16-MAY 21:32 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92591)
     From: DBREEDING    To: DOMM

 > I wonder if someone could tell me just what one has to do
 > (patches...etc.), to be able to boot os9 from ...say...Drive 2, instead of
 > from Drive 0?

Is there any particular reason?  You would have to patch your Boot module,
but then you would be stuck.  I think some of the disk roms support
something like dos 2, and I think if you issue the command drive 2, then
if you immediately type "DOS", then it will initially access that drive,
I guess it loads your kernel, but then Boot takes over and tries to read
drive 0.

Unless there were some good reason, it doesn't seem worth the effort.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92606 16-MAY 22:52 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92604)
     From: DOMM         To: DBREEDING

Actually, the reason I'd be interested in doing this is because I recently
added a 3.5" disk drive to both my CoCo setups. My choice was to make it
(on both systems) Drive 2 because that way I could keep all the 5.25 boot
disks as they are rather than changing everything. With 720k, I would use
the 3.5's as storage/work disks. Now, however, if I could get an 80 track
disk to boot from Drive 2 (the 3.5), I could have a larger Boot Disk to
work with when necessary. (It's not really a necessity but just a thought.)

I,ve tried doing a "Drive 2" then "DOS" . Doesn't seem to work. What does
work though, is doing a "DIR" on the os9 disk while in RSDOS. Then wait for
the File Structure error and "OK" cursor.A "DOS" after that does bring up
the boot screen (which then goes to /d0).

I've since played around with looking at the modules with kwikzap and have
been able to locate a couple of places in INIT and CC3go where I substituted
"D2" for anything resembling a drive descriptor. (h0,d0,dd)
On the Boot module, there only seems to be one spot "D0", so I changed
that to d2 also. It still doesn't boot, but does seem to stay on drive
2 while booting. (actually it does flash to drive 0 and back to Drive 2
at one point but doesn't stay at drive 0 even with no disk in it.

It seems close to working but not knowing exactly what I'm doing is kind
of a hinderance. <g>

---Dom

-*-

92611 17-MAY 03:21 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92606)
     From: COCOKIWI     To: DOMM

I did it a differnt way!..I put in a switch to change the drive 0 from a
STD..40 track to 3.5" and used it for DOS and Os9........

drive 1 was a 40 track......Drive 2 was an 80 track 5.25"
I could use the 3.5" as a 80 track DOS disk...D0/D2...front/back
and a full Double sided 80 track in os9...bootable!
and to copy to it..I used an 80 track RAMDISK..ala Ext-ADOS-3...to move stuff
back and forward.....Has worked for me now for a number of years!

all it takes is a single pole double throw switch..or a double pole,double throw

.if one want an indicator LED...........


         D0 select line   > o    o >LED-------X------B+

         MAIN D0 line <Car> o    o >470 ohm resistor to ground!

  Second D0 select line   > o    o >LED-------X------B+

   Use a double LED..<red/green>in one case!.....


Dennis

-*-

92613 17-MAY 18:38 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92602)
     From: RANDYKWILSON To: DOMM

Dom,

 First lets go through a quick-n-dirty os9 boot, coco style.

 1> You type "dos". The DECB rom code reads track 34 of the floppy, loads it
    into memory, and executes the code at a set point.

 2> The execute point is REL. REL moves the loaded code into high memory, and
    jumps into the kernel; os9p1.

 3> The kernel takes a look around and can't find his usual cronies. So the
    Kernel calls BOOT.

 4> BOOT knows nothing about DECB or OS9 disk structures. It only knows to look
    at one given point to find out where to start reading, and how much. This is

    why OS9Boot files must be contiguous. Effectively boot loads Os9Boot.

 5> Now the kernel is happy, grabs some defaults from Init, and executes CC3go.

 There are, as has been mentioned, three points that need to be fixed to use
another drive as boot. You apparently have found a way around the first one;
the DECB dos command. The third one is simple. Patch the drive/device names in
Init and CC3go. It's the second one that is a problem.

 "Boot" is nothing more than a very dumb loader program. It is hard coded, very
hard coded, to the coco disk controller, drive 0. At the point boot is running,
DECB is gone, but OS9 hasn't started yet. There are no descriptors, or drivers,
or managers. It's boot's job to load the file containing them.

 While I do know asm, I do not know how to program/control the floopy
controller. If we could come up with sufficient data on drive select, it should
be possible to form a patch.

 Many people claim to boot from a hard drive. Some just patch CC3Go and Init so
that the process starts on a floppy; the enter boot comes from floppy; then
continues on the hard drives. some people, me included have replaced their
boot module with a different one so that most of the boot comes from the
hard drive. A few have replaced everything including the DECB rom to boot
totally from a hard drive. Only the first, least effective, is done with
patching.


   Randy

-*-

92615 17-MAY 19:16 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92606)
     From: DBREEDING    To: DOMM

 > Actually, the reason I'd be interested in doing this is because I
 > recently added a 3.5" disk drive to both my CoCo setups. My choice was to
 > make it (on both systems) Drive 2 because that way I could keep all the
 > 5.25 boot disks as they are rather than changing everything.

That makes sense.  However, if you really wanted to make your 3.5's boot
disks, I believe the best way would be to make your 3.5 drive 0.  You have
to modify your Boot module.  This is why right now it is going back to
0 each time.  I don't know if it would be any hassle if you set the 3.5 as
drive 0 down the road or not.  All you would have to do would be to copy
all your boot disks to 3.5's.. Actually, if you don't have a HD, I would
suggest getting 2 3.5's for one of your computers.  You would want to keep
at least one 5.25 for compatibility.

 > I've since played around with looking at the modules with kwikzap and
 > have been able to locate a couple of places in INIT and CC3go where I
 > substituted "D2" for anything resembling a drive descriptor. (h0,d0,dd)
 > On the Boot module, there only seems to be one spot "D0", so I changed
 > that to d2 also. It still doesn't boot, but does seem to stay on drive
 > 2 while booting. (actually it does flash to drive 0 and back to Drive 2
 > at one point but doesn't stay at drive 0 even with no disk in it.

A "d0" in the "BOOT" module is not a reference to d0 (I don't think).  It
is a strictly m/l program that does a raw load of your os9boot file from
disk.  You will need to gain a knowledge on disk controller commands to do
this.  IMO, it would just not be worth it.

 > It seems close to working but not knowing exactly what I'm doing is kind
 > of a hinderance. <g>

I know what you mean there!  Again, I think It would be much easier to just
set your 3.5 as drive 0.  If you do this, you may need a few pointers to do
this.. I'm not sure exactly what you have to do to get this completed.  I
think you have to first connect a 3.5 as drive 1 or 2, then make a boot disk
on it, with d0 as the 3.5, then switch your drives and boot from this..

Again, 2-3.5's would be a good setup.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92622 17-MAY 23:55 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92611)
     From: DOMM         To: COCOKIWI

Thanks for the reply! I'll have to think about this for awhile.
I don't have time right this second to read and understand exactly
what you have written but I'm always interested on alternative solutions.

---Dom

-*-

92623 18-MAY 00:10 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92613)
     From: DOMM         To: RANDYKWILSON

Randy---
You've given me the "whats happening" step by step knowledge that is
very useful if I'm to understand this thing and make an inteligent decision
about it. In a way, it's too bad that I seem to be on the right track
on "two points" out of three because I hate to give up on anything.
However, from what you say about the m/l part of the "Boot" module,
my quest for a drive 2 boot is a little out of reach.

Thanks!

---Dom

-*-

92624 18-MAY 00:25 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92615)
     From: DOMM         To: DBREEDING

At this point any way, I believe you are right about the easiest and
least complicated way to boot from the 3.5 is to make it drive 0.
Right now however, I would have to change a lot of disks over and there
is this saying thats seems appropriate:
("If it ain't broke - don't fix it!")

I have two Coco setups with two 5.25s and one 3.5 apiece. Also, I have
five 5.25s waiting in the wings in case of trouble. If I were to change
over to a 3.5 format, I'd have to change alot of stuff. ($$$)

I've learned a lot though! Thanks!

---Dom

-*-

92625 18-MAY 00:49 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92623)
     From: RANDYKWILSON To: DOMM

Dom,

 Definately not out of reach. But it may be a lot more trouble than it's
worth. The next step would be to procure the control information for the
coco floppy controller. I believe the info needed is about the register
at addr $FF40, but am not totally sure. Then the code to Boot would have
to be examined and a patch strategy laid out. It *may* be a simple, one
byte, patch. Or it may require extensive logic modifications to keep
other portions of the code from stomping on the drive 2 select.

   randy

-*-

92628 18-MAY 01:21 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92613)
     From: COCOKIWI     To: RANDYKWILSON

the location for drive select is $FF40....the bits in there are what control
which drive....and are what is changed to get double sided drives to use the
back side.....cannot find my book on it right now...
used to do it all the time<grin>
dennis

-*-

92630 18-MAY 18:16 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92625)
     From: RANDYKWILSON To: DOMM

Domm,

 Alright already. I went digging through the databases, and found a os9
defsfile that had the floppy info. Try doing:

 os9> modpatch
 l boot
 c 33 09 0c
 c b5 29 2c
 c 13a 09 0c
 v
 <escape>

 Now hit reset and see which drive lights up.

   Randy

-*-

92632 18-MAY 22:44 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92630)
     From: DOMM         To: RANDYKWILSON

Randy---
THATS GREAT! I still can't get it to boot though.?? What was the description
of the floppy info in the defsfile? I'll have to look this over a while to
make sure I have the changes correctly in place. Gut feeling however says
what I did - I did. Whether or not I need to change something else or what,
I don't know.

So far, I patched Init and CC3go to /d2 descriptors. Init has been patched
to get CC3go in /d2/cmds. Also patched boot with your modpatch file.

While I'm rechecking, any thoughts???


(Thanks again for the research!)

---Dom

-*-

92633 19-MAY 00:11 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92623)
     From: WDTV5        To: DOMM

I don't think its impossible, but lemme do a little snooping before I grab a
saw and start on this limb I'm on. Later, Gene

-*-

92634 19-MAY 01:47 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92630)
     From: DOMM         To: RANDYKWILSON

Randy---
Well...so far it still won't boot (Boot Fail). I did all the patches
over, reformated /d2 to 40 tracks, made a new boot disk with changes..
including /dd set to drive 2 and making sure /dd and d2 are 40 track.

It does stay firmly on drive 2 when the boot screen is present though.

I changed two places in CC3go from /H0 to /D2.
I changed one place in INIT from /dd to /d2.

One place I might question is in the init. The sequence goes:"(.-Init.CMDS/
CC3go/dd/TermBoot..M"
Now, I changed the /dd to /d2 only. May be this should be done differently?

At least now - It stays steady on drive 2 and gets all the way to Boot Fail.


Any sugestions???

---Dom

-*-

92635 19-MAY 18:10 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92634)
     From: RANDYKWILSON To: DOMM

Dom,

 At the moment, my coco is not running, so I can't verify this. I do believe
that the strings in Init and CC3go should have the high bit set on the last
char.  If this is true, the /d2 in init should be (hex) 2F 64 B2. Same thing
for the spot in CC3go that used to be /H0, not /H0/cmds. In reality, the
two /h0 strings in cc3go could stay unmolested. That's where it *attempts*
to switch over to the hard drive. If it errors (no hard drive or /h0) it
shrugs and continues with the current floppy. :>


   Randy

-*-

92636 19-MAY 20:36 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92624)
     From: DBREEDING    To: DOMM

 > At this point any way, I believe you are right about the easiest and
 > least complicated way to boot from the 3.5 is to make it drive 0.

 > I have two Coco setups with two 5.25s and one 3.5 apiece. Also, I have
 > five 5.25s waiting in the wings in case of trouble. If I were to change
 > over to a 3.5 format, I'd have to change alot of stuff. ($$$)

Well, not a lot, would there?  You'd just have to put all your boots
onto your 3.5's, and perhaps any other data disks that had to be in

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92637 19-MAY 23:42 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92634)
     From: WDTV5        To: DOMM

Nosey me again, Randy had the right idea on boot patches, but as I recall
from patching the step rate, there's two of them puppies. Can you verify
that Randy? From the rest of the message, I think it should have worked.
I'd be interested in the final how-to myself.
Cheers Domm, Gene

-*-

92638 19-MAY 23:56 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92637)
     From: RANDYKWILSON To: WDTV5

Gene,

 My CoCo is only partially working. As such I can not test anything. I do
have some coco disasm's on the mm/1, including boot. With the info found
in FDDefs (programmers db), I found three points in the code that set the
base value of FF40. From those bases, it appears to "or" in the needed
control bits. The mod patch I gave should change those three bases. No
guarantees. I've never messed with raw floppy i/o before. :>

   Randy

-*-

92640 20-MAY 18:05 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92635)
     From: DOMM         To: RANDYKWILSON

Randy---
WELL-WELL-WELL--- I think we're gettin there! I finally got the thing to BOOT!
I'm having a little trouble during "startup" where at one point I have a list
of "Display" changes to different windows.(Seems to jam and slowly gives the
seek error #247 repeatedly. This could be related to something with merging
because I was getting that situation at a different point where I was sending
GUIB graphic boxes to some windows. I changed my startup line where I was
merging stdfonts from /d0 to /dd and got this. I then changed /dd to /d2 and
that
situation cleared up. I'm not sure at this point though.)

At this point, what I did was change back to the original CC3go with its
H0 descriptors and placed it back within the boot. Changed back the Init
to get CC3go in the boot and changed as you sugested , 2F 44 32 to 2F 64 B2.
The 32 to B2 change, is the differance it seems.(44=D 64=d probally doesn't
matter). Is this the high bit set on the last character?

What I'll do now is to change my boot disk back to what I had before with
CC3go in CMDS and go from there.

SO FAR SO GOOD!

---Dom

-*-

92645 20-MAY 20:31 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92640)
     From: RANDYKWILSON To: DOMM

Amazing! :>

 Yah, 44=D and 64=d; OS9 doesn't care about that in this situation. The high
bit set is indeed the B2 raather than 32. Normal ascii is in the range of
00 to 7F; a seven bit standard. Rather than using/wasting another byte to
mark the end of a string like Basic09 (FF) and C (00), OS9 internals often
use the high (eigth, unused) bit as a flag. Setting the high bit effectively
adds $80 to the chars value.

  Randy

-*-

92646 20-MAY 22:00 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92645)
     From: DOMM         To: RANDYKWILSON

Randy---
I think it's a "go"!

I made a 80 track boot off of Drive 2, with CC3go in CMDS. I'm still having
trouble at a certain spot of my startup but if I take that section out -
everything seems OK.

The boot disk in question is a little complicated so just to see I made a
40track boot disk of an editor disk I have. Once the changes have been done,
seems to boot off of drive 2 without any problems.

Do you think this information should be posted or what?
(Maybe a little more trying out is in order?)

---Dom

-*-

92647 20-MAY 22:10 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92636)
     From: DOMM         To: DBREEDING

David---
I seem to have about 10 bootdisks not counting the abandoned two-disk M.V.
ones. Then, I have 3 coppies of everything. So, about 30 change overs would
necessary. Since I now only have two 3.5 drives at different locations, and
four 5.25s setup with five more backups, I would rather stress out the drives
that I can redily replace.

Besides that, it seems that I now can boot up sucessfully from Drive 2.
(hear that knocking sound? It's me knocking on wood! <g>

---Dom

-*-

92648 20-MAY 22:23 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92637)
     From: DOMM         To: WDTV5

Gene---
So far so good! I think a little more checking/use should be done but the
changes seem to work ok.

I'll use the changwes for a little whi
changed disks for a little while and try to get the results
posted.

---Dom

-*-

92649 20-MAY 22:49 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92638)
     From: WDTV5        To: RANDYKWILSON

I did a couple fof times, but its not for the faint-hearted! In os9 I've
confined myself to doing the 6ms patches to it, and there are 2 places
in the BOOT module for that, or were. Question, what happened to the CoCo3?
Maybe I can help if its not a bad GIME.
Cheers Randy, Gene

-*-

92650 20-MAY 22:50 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92648)
     From: WDTV5        To: DOMM

I'll be waiting!

-*-

92652 20-MAY 23:44 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92649)
     From: RANDYKWILSON To: WDTV5

Gene,

 My CoCo went south.. well even farther south.. about the same time RickU
informed me Fast232 was a solid go. At first I thought I was having
software problems. Finally, I determined that my MPI was dieing... at
which time it went totally.

 Thanks to the kindness of John Wainright (JOHNREED), I now have a partial
CoCo that I can bring up for testing as needed. Not easily, though. Keyboard
and m/b connector are gone.... replaced with a ribbon cable and db25. I
have to jam an old keyboard mylar up against the  ribbon solder points
steady enough and long enough to type "dos". :> John's old system was
obviously well and lovingly used.

 I have also located another MPI. So, since I really do all my CoCo
software development and assembling on the mm/1, and the coco is used
for testing, I ought to be set for another ten years or so. :>

  Thanks for the thought...

     Randy

-*-

92659 21-MAY 13:09 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92652)
     From: WDTV5        To: RANDYKWILSON

Or the mpi could be fixed, either Marty or I could probably handle that.
Cheers Randy, Gene

-*-

92664 21-MAY 14:03 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92647)
     From: DBREEDING    To: DOMM

 > I seem to have about 10 bootdisks not counting the abandoned two-disk
 > M.V. ones. Then, I have 3 coppies of everything. So, about 30 change overs

Well, to tell the truth, that sounds about what I had - well still have them.
Especially before I got my HD, I had a standard boot disk, a C boot, a
B09 Boot, a MV boot, and so on, and so on.  After getting my HD, of course
I didn't have to have so many.. I actually just kept this one disk in
maybe a couple other instances.  But I still kept most of my disks.
Actually, I should not have kept so many, but I always wanted to keep
myself on the safe side.

 > would necessary. Since I now only have two 3.5 drives at different
 > locations, and four 5.25s setup with five more backups, I would rather
 > stress out the drives that I can redily replace.

Yeah, that is a point, but of course you can use just about any floppy
drive.  I guess you are aware that you can use 1.44 drives, too, in
case you have to buy one and would like to have something to put into
another computer. All you have to do is just always use the DD disks, and
not use the HD ones..

As for floppy drive life, I still have the same 5.25's I bought some
10-12 years ago..   Wish my modems and printers would hold up that well <G>

 > Besides that, it seems that I now can boot up sucessfully from Drive 2.
 > (hear that knocking sound? It's me knocking on wood! <g>

Yes, I saw your post previously.  Did you find a modified Boot module or
did you modify it yourself?  I think I have the disassembled source code
for Boot, somewhere.  Had intended on looking for it, and see if I could
fix it, but if you have it working there's no need, I guess.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92665 21-MAY 14:03 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92648)
     From: DBREEDING    To: DOMM


 > So far so good! I think a little more checking/use should be done but the
 > changes seem to work ok.
 >
 > I'll use the changwes for a little whi
 > changed disks for a little while and try to get the results
 > posted.

Oh, another thought.. are you going to change your /dd descriptor to point
to your modified boot drive?

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92666 21-MAY 14:47 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92665)
     From: DOMM         To: DBREEDING

David---

> ............are you going to change your /dd descriptor to point to
> your modified boot drive?

So far, yes. The dd descriptor matches the d2 descriptor which should
reflect the type of disk (80-40 tracks) used.

---Dom

-*-

92671 21-MAY 20:04 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92659)
     From: RANDYKWILSON To: WDTV5

Gene,

 I did basic power checks (was hacked for AT p/s), solder joint inspection,
and swapped out all the TTL. I'm down to pointing a finger at the vlsi
surface-mount thingie.

  Time for a new one.

  Randy

-*-

92676 21-MAY 23:47 System Modules (6809)
     RE: Booting from another drive (Re: Msg 92671)
     From: WDTV5        To: RANDYKWILSON

Humm, its a later mpi I take it. I spose, but then again, I'd be surprised
if the shack couldn't supply it once we figure out the part number assigned
to it *today*. It isn't so big that it couldn'tcome off destructivly which
would make the replacement a whole bunch easier. As in using an exacto
or ? to slice thru the leads near the body, then bulk remove the leftovers
with some solder-wick. Wash it up and plant the new one. Sounds like a
walk in the park from this end. In any event, don't toss it. Its like
dirt, they don't make any new dirt. Dirt, as in real estate. They aren't
making any new mpi's either. I have a manual, and can look it up if that
would help.
Cheers Randy, Gene

-*-

End of Thread.

-*-

92605 16-MAY 22:23 General Information
     chd's in ftp
     From: DBREEDING    To: ALL

Is there some command to toggle the case of your characters while in
an ftp site?  I just was at chestnut, tried to get into OSK sub.  My
characters were echoed in uppercase (the directory was in u/c), but it
returned "osk" in lowercase and said no such directory..  The only dir
I could access was 6809 it was first one, but no alpha characters, so
I suspect chestnut was getting lowercase, or interpreting it as such.

I may have a text file about this, will check.

Thanks

-*-

92608 17-MAY 00:37 General Information
     RE: chd's in ftp (Re: Msg 92605)
     From: MITHELEN     To: DBREEDING

You need to put uppercase, or mixed case names between quote characters.
--
Paul

-*-

92617 17-MAY 19:29 General Information
     RE: chd's in ftp (Re: Msg 92608)
     From: DBREEDING    To: MITHELEN

 > You need to put uppercase, or mixed case names between quote characters.

Thanks, Paul, CARL_D also told me... If I knew it, I had lost the info..

I thought I tried it, but apparently not.

I want to try and see if the versions of zip/unzip are more up-to-date
than mine..  I need this pair for QWK packets, and I believe the ones I
have (Zip 1.0, 29 Sept 1991 and unzip 5.0 21 Aug 1992) are trashing my
directories..  I posted this once and someone (BROWN80?) said he didn't
think we had any better versions, but I want to give it a shot.

I don't feel safe using zip any more... may do my reading from floppy,
but that will be slow.. and more inconvenient..

It seems that the darn thing is writing right over other files, writing
its data over the other file's data and allocating the bitmap for itself,
and when the file is deleted, the bitmap for the original file is also
deallocated (but the data is garbaged anyway.

I have the source for zip, and I believe it does its own thing for writes,
haven't looked at it closely yet.


                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

End of Thread.

-*-

92607 16-MAY 23:30 General Information
     ftp
     From: CARL_D       To: DBREEDING

Enclose uppercase directories in quotes.   as in cd "OSK".

-*-

92616 17-MAY 19:29 General Information
     RE: ftp (Re: Msg 92607)
     From: DBREEDING    To: CARL_D

 > Enclose uppercase directories in quotes.   as in cd "OSK".

Thanks... I thought I tried that, but I guess not.


                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

End of Thread.

-*-

92614 17-MAY 19:09 General Information
     IDE Hard drive adapter?
     From: DISTO        To: ALL

How many people would be interested in an IDE hard disk adapter for the/our
COCO 3? More details to follow! -Tony.

-*-

92620 17-MAY 23:23 General Information
     RE: IDE Hard drive adapter? (Re: Msg 92614)
     From: REVKAK       To: DISTO

I would be *very* interested in an IDE adapter.  IDE is so much easier to
find small to mid size drives. New and/or used. Count me in! -Keith

-*-

92629 18-MAY 01:22 General Information
     RE: IDE Hard drive adapter? (Re: Msg 92614)
     From: COCOKIWI     To: DISTO

VERY!<grin>
Dennis

-*-

92653 20-MAY 23:54 General Information
     RE: IDE Hard drive adapter? (Re: Msg 92614)
     From: WILLIAMSON68 To: DISTO (NR)

 I would be interested. Also, I'm looking for an origional 6309chip, any
ideas?

-*-

92661 21-MAY 13:17 General Information
     RE: IDE Hard drive adapter? (Re: Msg 92614)
     From: 01GEN40      To: DISTO (NR)

I SURELY WOULD, OH MIGHTY ONE!!!!!

LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!

Peace and Long Life...

Siran of Vulcan (CMDR)

-= GEN =-

-*-

End of Thread.

-*-

92631 18-MAY 22:13 General Information
     IDE Hard drive adapter.
     From: CARL_D       To: DISTO

I would, very much so!  IDE drives are cheap, fast and easy to get.

-*-

92642 20-MAY 19:16 General Information
     CDL BASIC
     From: TEDJAEGER    To: ALL

Hi All,
       Been looking at CBdemo and docs. I read in the docs that one can
do system calls form this BASIC but see no examples how. What would be
the CDL BASIC equivalent of:

 Type registers=d(8),a(8),pc:INTEGER
 DIM regs:registers
 DIM callcode:INTEGER
 callcode=$0c
 run syscall(callcode,regs)
 id=regs.d(1)

 Since there is no syscall in CDL, I'm wondering how to get a BASIC
 variable loaded with the result of the system call and how to execute
 that call as well. I do see in the docs the indication that one can
 mix assembler with CDL BASIC but there is no example of how to use
 that technique and return a value from a system call. Thanks...


Bests
---TedJaeger

-*-

92654 21-MAY 02:28 General Information
     RE: CDL BASIC (Re: Msg 92642)
     From: NIMITZ       To: TEDJAEGER

Ted, as you can see from further reading on the docs, one has direct access
to all registers.  Do it as you would in assembler.  Load regs and issue an
the call assember style.



-*-

92680 22-MAY 21:21 General Information
     RE: CDL BASIC (Re: Msg 92654)
     From: TEDJAEGER    To: NIMITZ

 > Ted, as you can see from further reading on the docs, one has direct
 > access to all registers.  Do it as you would in assembler.  Load regs and
 > issue an the call assember style.

 Could you give an example? I figure to get a process ID one goes:

  os9 F$ID

 There are no entry conditions so no registers to load, no? This leaves me
 with the process ID in register d1. So how do I get the ID number out of
 d1 to a BASIC variable? Does that too have to be done in assembler? A
 move command? Perhaps the printed manual would/should cover this as, in my
 experience, nothing too serious can be done in BASIC without system
 calls.

 I bet HAWKSOFT could do this one in his sleep! Chris, are you there? Its
 CDL BASIC Chris.

Bests
---TedJaeger

-*-

End of Thread.

-*-

92644 20-MAY 20:09 General Information
     Usenet Messages?
     From: DBREEDING    To: ALL

I have a question.  In reading the usenet messages, I keep getting a lot of old
stuff
that I have already read.  Today, I got messages dating back to March.  What
I do is have them in Personal Favorites, and read from there.  I thought
maybe you needed to go back in and mark them or something, but to test, I
came back in and attempted a read of unread messages and It replied "No
unread messages"  Am I doing something wrong or is this just the way it
is?

-*-

92655 21-MAY 08:31 General Information
     RE: Usenet Messages? (Re: Msg 92644)
     From: JOHNBAER     To: DBREEDING


   David,

> I have a question.  In reading the usenet messages, I keep getting a lot
> of old stuff that I have already read.

  First, let me say that Marking messages does work.  Now, I'll admit
to doing my reading from the Internet Sig, and I use the usenet reader..
Not the NN (Net News) reader.  NN is more powerful.. I've tried it, and
like to use the other simpler one.

  You don't say where you are doing the reading from, and which reader
you are using.  More info would be of help.

  John -


-*-

92667 21-MAY 15:07 General Information
     RE: Usenet Messages? (Re: Msg 92655)
     From: DBREEDING    To: JOHNBAER

 > > I have a question.  In reading the usenet messages, I keep getting a
 > lot > of old stuff that I have already read.
 >
 > First, let me say that Marking messages does work.  Now, I'll admit
 > to doing my reading from the Internet Sig, and I use the usenet reader..
 > Not the NN (Net News) reader.

 > You don't say where you are doing the reading from, and which reader
 > you are using.  More info would be of help.

I've been doing it from within the OS9 Sig.  Just go in, choose Peronal
Favorites, have cocolist and comp.os9 there.  choose first one, then the
other.. in each, let's see..  you get a prompt , unread is default.  I
press enter, it tells you how many msgs & threads are there.. I then
type 1-<# threads> nonstop, having my capture turned on..

I had thought that I might need to "Mark", but I came right back in,
attempted to read messages again, but it told me "No unread messages"
so I would assume that marking is not necessary....

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

End of Thread.

-*-

92651 20-MAY 22:54 Telecom (6809)
     usenet
     From: WDTV5        To: ALL

I'm in the same boat, I just went back into the bit.listserv.coco (35)
area and was told there were over 100 msgs I haven't read since last time.
Yeah, sure, I was there last night and got them all, should be maybe 10:15
msgs, I looked at the headers and I had read them all!
Just to be sure I marked them before I left.
Cheers all, Gene

-*-

92663 21-MAY 14:02 Telecom (6809)
     RE: usenet (Re: Msg 92651)
     From: DBREEDING    To: WDTV5

 > I'm in the same boat, I just went back into the bit.listserv.coco (35)
 > area and was told there were over 100 msgs I haven't read since last
 > time.

I assume you are responding to my message...  At least I'm not the only
one <G>.  I had been noticing it and thought maybe it was just a fluke,
but today, it's a bunch..  It could be some that are recirculating around
or something.  I've seen it on the other nets where I suppose the messages
come in from two different sources..

It wouldn't be so bad but I'm paying long distance and kinda hate to pay
for the time to get duplicates, but it might not be something that can be
avoided.

One other thing, when I went back in, it said that in coco, I believe, that
there had been some 160(?) messages in the past 14 days, that I'd read
approx. 66, but when I called for unread messages, it said "no unread msgs".

Actually, thinking about it, that sounds like maybe duplicates _are_ coming
in..

Oh, well, I can think of worse things than that..

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92675 21-MAY 23:41 Telecom (6809)
     RE: usenet (Re: Msg 92663)
     From: WDTV5        To: DBREEDING

Maybe, but in the quick scan I did, I'd not noticed that the mail dates
etc were different. But then I wasn't paying that much attention either.
It could be dups, but that many? Nahhh.
Cheers David, Gene

-*-

92678 22-MAY 01:16 Telecom (6809)
     RE: usenet (Re: Msg 92675)
     From: DBREEDING    To: WDTV5

 > Maybe, but in the quick scan I did, I'd not noticed that the mail dates
 > etc were different. But then I wasn't paying that much attention either.
 > It could be dups, but that many? Nahhh.

I'm thinking we could be getting an echo, or if the ones using a different
reader are not getting them, then either we are doing something wrong or
our reader is goofing up..  As I said, I went back in and it told me I
didn't have any unread mail, so if I get dups again, then it would be
apparent to me that the dups are caused by something besides my technique.


                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92682 22-MAY 23:11 Telecom (6809)
     RE: usenet (Re: Msg 92678)
     From: WDTV5        To: DBREEDING (NR)

Thats possible, but I'd rather blame it on a flacky ethernet card someplace
in the delphi system. What I'm told happens is that you may get a different
machine the next time on, and it doesn't kknow (yet) that you've been
there and read the stuffs. Problems of that nature for me went away after
an amiga conference blew up in delphi's face resulting a bunch of very
irate users, me among 'em. Subsequent troubleshoot found a bad card that
had rather effectively divided the system up into 2 pieces. Those who
got a connection on one side got into the conference, those on the other
side were told that no such conference existed! I was one of the un-lucky
ones in 3 tries that nite, and irate wasn't an adequate description of
my mood, that conference had been highly publicised (sp) for 2 weeks
ahead of time. So that maybe whats going on here. It can also result in
files you've received in mail, then deleted, mysteriously comeing back
to haunt us. I had lots of that, but after that bad card was repalced,
(sp) my probs with previously deleted mail re-appearing pretty much
went away.
Cheers David, Gene

-*-

End of Thread.

-*-

92662 21-MAY 13:58 System Modules (6809)
     Drive Two Boot
     From: DOMM         To: RANDYKWILSON

RANDY---
I just tracked down what was giving me ERROR #247-Seek errors while trying
to boot from drive 2 with the first experimental disk I was using.

It seems that on that disk I had two programs which used guib to draw
boxes on another window. With the original 5.25 disk in drive 0, I was
able to use the ">" path descriptor to send only the output. Now, with
the 3.5 disk in drive 2, I must use the full "<>>>". The only other
change in my startup was changing d0 to d2 concerning my merge of stdfonts.

Those two programs have a status check for the version of guib. Maybe this
was where it was hanging?

Otherwise, I now have two 80 and one 40 track Drive two "working" boot disks!

If its ok with you, and you are pretty confident about the modpatch you
devised, I'll work up a text file briefly explaining what we did. (???)

---Dom

-*-

92672 21-MAY 20:09 System Modules (6809)
     RE: Drive Two Boot (Re: Msg 92662)
     From: RANDYKWILSON To: DOMM

Sure, no problem. Publish away. :>

 For the record, the three patch points are in the form of $xy. $x9 is drive0,
$xA is drive1, and $xC is drive2.

   Randy

-*-

92673 21-MAY 20:30 System Modules (6809)
     RE: Drive Two Boot (Re: Msg 92672)
     From: DOMM         To: RANDYKWILSON

Randy---
Sorry...but I have no idea what you mean $xy - ($x9=/d0 $xA=/d1 $xC=/d2)???

My assembly knowledge is practically zip. Which would bring another
question.....I,d like to get some kind of assemblerisassembler for OS9.
Any sugestions? (may be someone has one for sale???)

---Dom

-*-

92679 22-MAY 01:16 System Modules (6809)
     RE: Drive Two Boot (Re: Msg 92673)
     From: DBREEDING    To: DOMM

 > My assembly knowledge is practically zip. Which would bring another
 > question.....I,d like to get some kind of assemblerisassembler for OS9.
 > Any sugestions? (may be someone has one for sale???)

You have a couple of options for an assembler.  You don't have OS9 Level
1?  It has an assembler in it.  Your other choice is to find the Development
Pak. It has a C-compatible compiler - well, you have 3 choices, really,
an earlier version of the Dev-Pak assembler is included with the C Compiler,
too, and you could use it.

I have a really good disassembler.  It is Dynamite+ from the same people who
published Dynacalc.  I don't know if they are still in business or not.

I believe a pd disassembler is here, too.. I believe it's name is "dasm".
I got it, but never did use it.. Dynacalc is so good that it wasn't worth the
effort to learn the syntax <G>.

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

End of Thread.

-*-

92669 21-MAY 15:08 OSK Applications
     More on ZIP
     From: DBREEDING    To: ALL

Hey, everyone.

I guess everyone remembers me crying a while back about ZIP messing up
on the directory structure.  I kept getting occasional instances when
the bitmap for the file was not allocated.

The version I have is 1.0  Someone said it was buggy, but I have had pretty
good luck in unzipping (different program, of course), other files and
have had no complaints on files I've zipped.

I even grabbed a new zip (1.9) from chestnut, but _it_ seemed to do mess
up more often than 1.0.

I finally went in and began studying the code that came with zip, and I
_believe_ I have discovered the problem..

When all files are zipped, it has created a new temp file, usually with
the name _Z00*.  On exit, it first deletes the original *.zip, if present.
Next, it goes to a function called link().  It attempts to overwrite the
temp filename with that of the destination *.zip name, inc the link
count in the file descriptor.  (Otherwise, if any part fails, it comes
back and does a straight copy).  In either case, it calls unlink()
to delete the tempfile name.  I found that link() failed often, and
the moderately rare cases when link() was successful, were when the
file structure got munged.

The problem:

I believe I've found it.  In the file "osk.c", the main function that link()
uses is a multi-purpose one, and it optionally will get the sector size
from the device driver, or will read the disk.  Two defines are used
to control the program flow.   "FROM_DRIVER" and "FROM_DISK". My code
defines FROM_DISK, but...  somehow, the author, down around line 750,
when he wants to read the disk, uses the switch #ifdef "FROM_MEDIA"
instead of "FROM_DISK".  When I changed this to FROM_DISK, it appears
in my test program that link() is working much more often and that
the few times I have tried it, it is now fixed... (I was a little chicken
to try it on my HD <G> - but did)

If anyone is using zip, it might be well to fix this.  Actually, I wonder
if it would be safest to just eliminate this link() call from the procedure,
as I wouldn't mind its doing a copy, as my main use for it is in small
QWK replies and large copies to floppy for MS-DOS systems is not all that
frequent.

Is there someone who should be notified about this?  I couldn't determine
who might be in charge of the OS-9 end of it..

                         -- David Breeding --
       CompuServe : 72330,2051             Delphi :  DBREEDING
    *** Composed with InfoXpress/OSK Vr. 1.02 & VED Vr. 2.4.0  ***

-*-

92670 21-MAY 16:36 System Modules (6809)
     os2/os9
     From: DOMM         To: ALL

Could someone tell me the differances/sames of OS9 compared to OS2 aside
from the obvious hardware?

I thought someone said that os2 wasn't re-entrant but someone else told
me it is.  (???)

---Dom

-*-

92681 22-MAY 23:02 New Uploads
     File Upload to Delphi
     From: DOMM         To: ALL

HELP! I seem to have uploaded two text files with the same name and need
to make sure that they use only the last upload.

I left a message in the trouble section but fear that wasn't the way to fix
things.

How do I make sure of this?

---Dom

-*-


FORUM>Reply, Add, Read, "?" or Exit> 