read new nonstop follow
92147 22-MAR 20:18 General Information
     RE: Editor (Re: Msg 92145)
     From: CLTUCKER     To: ISC

I have also ordered WPShell from Color Systems. Hope it works with
VED. Well see.(g)
cl

-*-

92150 22-MAR 22:59 General Information
     RE: Editor (Re: Msg 92147)
     From: CHARLESAM    To: CLTUCKER

Oh yeah, it does.. matter of fact, the author of WPShel recommends Ved. Great
program, wpshel, and ved too. Now you just have to configure your system for
a serial mouse, if you haven't already done so, and your really cooking. Good
luck. Regards Charlie

-*-

92161 23-MAR 23:47 General Information
     RE: Editor (Re: Msg 92147)
     From: ISC          To: CLTUCKER

> I have also ordered WPShell from Color Systems. Hope it works with
> VED. Well see.(g)
> cl
>
CL,

It works very well with VED.  I use it a lot.  I recommend that you also get
TSSpell from Tandy to use as your spell checker.  It is IMHO the best spell
checker written for OS-9.  In addition, I use the VU text viewer from Vaughn
Cato here in the database as the text viewer with WPShel.  Incorporate VPrint
into WPShel as your text formatter for printing and voila! -- a word
processing package.  Really a bright idea.

Let us know if you need any setup advice.

Good Luck.

Bill

-*-

End of Thread.

-*-

92148 22-MAR 21:12 General Information
     RE: CMDS (Re: Msg 92142)
     From: DBREEDING    To: JOHNREED

 > Let me add one little point to the other replies -- because this
 > used to confuse me.
 >
 > Lets say you have your commands dir set to `/d0/cmds'  and everything
 > is working fine.
 >
 > Now you put a different disk in `/d0'.  This disk also has a directory
 > `/d0/cmds'  BUT  unless it is an exact copy of the original disk -- that
 > is one made with `backup' or something similar -- your commands dir
 > setting is no longer valid.

Hadn't thought about that.  This could be his problem..

I think you're alright if you always create your CMDS directory at the
same spot all the time.. I.E.. if you "makdir CMDS" first each time you
format a disk, then you can read them, but it's safest to assume this is
not the case.

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

92155 23-MAR 21:41 General Information
     RE: CMDS (Re: Msg 92146)
     From: DBREEDING    To: ISC

 > >  Lets say you have your commands dir set to `/d0/cmds'  and everything
 > > is working fine.
 > >
 > >  Now you put a different disk in `/d0'.  This disk also has a directory
 > > `/d0/cmds'

 > It is important to remember that there is a sensor in the diskette drive
 > which tells the computer that the diskette has been removed.

John is referring to the case where you take a disk out and then reinsert
another.. If the CMDS directory doesn't happen to be listed at the exact
same spot on the disk, OS9 can't find the directory listings.

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

92175 25-MAR 12:05 General Information
     RE: CMDS (Re: Msg 92133)
     From: JEJONES      To: CLTUCKER

 > Can someone tell me why:
 > When I copy a cmds pgm from one disk to cmds on another disk I have to
 > reboot from the new disk before the pgm will work? I have a ptr
 > routine that I made from Procedure then packed it. Works OK on the
 > original disk. When I copy it to the cmds dir of a new disk it
 > will not work. Any ideas?(g)

What error do you get?  If you didn't chx to the new disk, did you give
an absolute pathname?

Opinions herein are solely those of their respective authors.

Clipper Chip: Big Brother Inside

-*-

92181 25-MAR 18:09 General Information
     RE: CMDS (Re: Msg 92146)
     From: WDTV5        To: ISC

Hate to belabor the point, but John was correct in msg 92142. While the
sensor may be in the drive, 1773's, CoCo's, and os9 all uniformly ignore
the thing! The real problem is that the "cmds" dir that he is "chx'd" to
is not in all probability located in the exact same sector of the disk
for a starting point on the second disk unless its an exact, made by
backup copy of the first disk. No op-sys that I know of stores its pointers
to the current directory as a text string that would require a search of
the disk from sector zero to find each time. What they all do is store the
address of the starting sector of that directory. If the disk is changed,
and the new disk doesn't have exactly the same address for the file
descriptor that describes the cmds dir, then the system is lost until
the operator issues a "chx (or d) /device/pathname/pathname" so that
os9 is then required to do this search, from square one, and find the location
of this new directory which it then stores as the sector offset address in
its own internal drive table.
Cheers, Gene

-*-

92182 25-MAR 19:45 General Information
     RE: CMDS (Re: Msg 92175)
     From: CLTUCKER     To: JEJONES

I have found the problem. It is me.(g)
cl

-*-

End of Thread.

-*-

92149 22-MAR 22:56 General Information
     CHX /dd
     From: CLTUCKER     To: ALL

Now that CHX pblm is resolved how about the case where I placed a pgm
in the CMDS dir and cannot list, rename, or delete it?(g)
cl

-*-

92151 22-MAR 23:02 General Information
     RE: CHX /dd (Re: Msg 92149)
     From: CHARLESAM    To: CLTUCKER

Did you set the attributes. If you attr filename r w e, you should be in
business. Luck, Charlie

-*-

92153 23-MAR 20:12 General Information
     RE: CHX /dd (Re: Msg 92151)
     From: CLTUCKER     To: CHARLESAM

Now what I need is the info on how to config for the serial mouse. Any
ideas?(g)
cl

-*-

92157 23-MAR 22:38 General Information
     RE: CHX /dd (Re: Msg 92153)
     From: CHARLESAM    To: CLTUCKER

Go to "data app" and do a search for "smouse". The docs are there. Have you got
Nitros9,use a MPI. If so, the job gets a little involved. But I believe its
worth it. I'm still ironing out the bugs on an 'IRQ hack'. I'm close, but not
finished yet. First things first, get smouse installed(cc3io) and get back to
 By then I should have my system up to snuff. Good luck. Charlie

-*-

End of Thread.

-*-

92152 23-MAR 01:35 General Information
     RE: Tymenet/Sprintnet (Re: Msg 92066)
     From: AJMLFCO      To: DBREEDING

Even though you live in a small town, your local (free calling)
area may be large enough to justify it for all in that zone.  I
am also not sure that calling Delphi direct at 14,400 is such a bad
deal.  We only have 2400 baud here and there are 65,000 people in the
lacal area.  2400 sucks!

Allen

-*-

92167 24-MAR 23:47 General Information
     RE: Tymenet/Sprintnet (Re: Msg 92152)
     From: DBREEDING    To: AJMLFCO (NR)

 > Even though you live in a small town, your local (free calling)
 > area may be large enough to justify it for all in that zone.

It's possible.. It might be worth looking into.. One of Our BBS's, it
hasn't gotten going full force yet, is contemplating getting some internet
stuff.  This will be good.. They will call somewhere and get some of the
newsgroups, I assume, and the users can read from their database.. We
might have enough people to get something going, if only one service, it
would be good.
  I
 > am also not sure that calling Delphi direct at 14,400 is such a bad
 > deal.

I've tried the direct #, but the line was busy often.  Too, I've had
trouble getting connections sometimes.

 > We only have 2400 baud here and there are 65,000 people in the
 > lacal area.  2400 sucks!

We don't have that many people, but we still might have enough dedicated
callers to get something going.

Yes, 2400 is really a drag once you get used to something faster.. I call
long distance for my Tymnet connect here and for my CI$ connections.  The
Tymnet is supposed to be 9600, but the CI$ is supposed to be 14.4, but it
winds up at 9600 over half the time.. Guess they have lots of older modems
still connected.

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

End of Thread.

-*-

92154 23-MAR 21:41 General Information
     RE: Looking for IMS info. (Re: Msg 92143)
     From: DBREEDING    To: JEJONES

 > > I think you can get a 500 meg for maybe $300 or so now (SCSI might be a
 > > little higher, but not much).
 >
 > It's not.  These days you can get a Quantum LP540 SCSI hard drive for
 > something like $260.

I knew there was not much difference, if any.  I was just quoting off the
top of my head.  One thing's for certain, they are becoming quite reasonable.

It was just a few years ago I gave over $300 for an 80 meg.. a 500 meg
at that time (that would have been a _huge_ drive then) would have been
up towards $1000, if not more.

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

92158 23-MAR 22:43 General Information
     RE: Looking for IMS info. (Re: Msg 92154)
     From: CHARLESAM    To: DBREEDING

I believe I bought my SCSI 65meg in 92 and I paid $550. Of course that was
with power supply and case with Kenton adaptor and RGB-DOS. Still, $550?
Now I know to wait awhile when I want something, its bound to come down.
Charlie

-*-

92163 24-MAR 01:53 General Information
     RE: Looking for IMS info. (Re: Msg 92084)
     From: KNOT1        To: DBREEDING

Yes, it doesn't look like he'll be able to help as far as past IMS
obligations go, but can help me with getting new stuff.  And well,
I've been around, but not active on-line here.  And other than when
I was at campus, using my MM/1 as basicly a terminal for my modem, I
haven't been using it, no.  Currently I can do more with my Coco, since
I have a hard drive and C compiler.  I like using my own term program. :-)
Well, here's to hoping things work out!  Thanks for everyones' help here.

  -- Jamie (KNOT1) --

-*-

92177 25-MAR 13:00 General Information
     RE: Looking for IMS info. (Re: Msg 92158)
     From: DBREEDING    To: CHARLESAM (NR)

 > I believe I bought my SCSI 65meg in 92 and I paid $550. Of course that
 > was with power supply and case with Kenton adaptor and RGB-DOS. Still,
 > $550? Now I know to wait awhile when I want something, its bound to come
 > down.

Well, waiting is OK, up to a point.  But, to be honest, I'd hate to take
what I gave for my original HD and give up the usage I got out of it..
I have never regretted paying the price I gave.

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

92178 25-MAR 13:01 General Information
     RE: Looking for IMS info. (Re: Msg 92163)
     From: DBREEDING    To: KNOT1 (NR)

 > Yes, it doesn't look like he'll be able to help as far as past IMS
 > obligations go, but can help me with getting new stuff.

That's good to hear..  I'm sure he'll do the best he can.
 >  And other than when
 > I was at campus, using my MM/1 as basicly a terminal for my modem, I
 > haven't been using it, no.  Currently I can do more with my Coco, since
 > I have a hard drive and C compiler.

I think that when you get your HD and all up and running, you'll be thrilled.
I'm really impressed with OSK.  There might be a few aspects where the OSK
systems have not caught up with the coco yet, but in most cases, they are
equal or superior.  For one thing, most of the util commands have more
options that come in handy.  The coco has most of these features, but you
have to call up more different commands to  do them. One thing that comes
to mind is dsave's "-e" function, where you can execute dsave's commands
rather than piping into a shell.. Also, you have the option of overwriting
files on the destination disk if the source file is newer.  Small features,
but nice.

RE: the C compiler.. Didn't you get a C compiler with your system?

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

End of Thread.

-*-

92156 23-MAR 22:35 General Information
     RE: coco3 problems (Re: Msg 92028)
     From: NEALSTEWARD  To: THIB

Have you done the usual stuff list remove and reseat the GIME or make sure
the 512k board's pins are not presses too far in that they touch the Coco's
motherboard?  (list above was supposed to be "like")

-*-

92166 24-MAR 20:34 General Information
     RE: coco3 problems (Re: Msg 92156)
     From: THIB         To: NEALSTEWARD

 Hmmm.. why would I need to reseat the GIME on a computer just out of the box?
 (second computer)

 I was unaware that the 512 boards pins could go TOO far.. isn't that why there
 are plugs to put the board into?

 Andy

-*-

92179 25-MAR 13:30 General Information
     RE: coco3 problems (Re: Msg 92166)
     From: NEALSTEWARD  To: THIB

For some reason or another, many coco3 problems occured because the GIME
chip wasn't seated properly into it's socket.  Use a couple jewelers
screwdrivers to GENTLY pry it out, clean the contacts with alcohol or
tape head cleaner and firmly press it back into the socket, making sure
to align it correctly.  The is one corner on the chip with a bevel that
will match in the socket.  If that doesn't work, pull the 512k upgrade
up so the pins don't press all the way through the header connectors,
as they can short out on some of the traces on the motherboard.  Both
of these things have "fixed" ECCCC members computers in the past.
A good investment is "Tandy's Little Wonder" distributed by Farna
Systems for around $20-$25.  It has many tips on repairing, upgrading
it contains schematics, past and present software and suppliers.  It

is a handy book to have around as a reference.  Also, if the above
doesn't fix your coco, direct questions to Marty Goodman, if anyone
can help, he probably can.  But first search through the message
forum for messages with subjects that sound like they are related
to see if anyone else has had and solved similar problems.


-*-

92186 26-MAR 19:49 General Information
     RE: coco3 problems (Re: Msg 92179)
     From: THIB         To: NEALSTEWARD (NR)

 thanks for the info.. I doubt I will contact Marty Goodman, tho.. the last
couple of times I asked a questions about hardware.. he essentially asked "why
do you wanna do that" instead of helping me .
 Andy

-*-

End of Thread.

-*-

92159 23-MAR 22:51 General Information
     IRQ Hack.
     From: CHARLESAM    To: ALL

I did all the proper steps and doubled checked them. I can run my mouse from
any slot and my communications from any slot but still not together. I don't
have SIO in my boot, would including that module help? I know I'm close but
there's something I missed. HELP! Anybody out there running with a MPI and
two rs232s. I'm also 6309-Nitros'd. Thanx Charlie

-*-

92164 24-MAR 04:23 General Information
     RE: IRQ Hack. (Re: Msg 92159)
     From: BROWN80      To: CHARLESAM

I do not have two RS232's running, but I'll throw my two cents in.  On one of
your RS232's you have to do a hardware modification to change the address it
recognizes.  If you have a connect RS232 it is a mater of moving a jumper.
The instructions come with it.  Once you have modified the RS232 then the
driver must be modified so that it works with the new address.  I believe
this is documented in the database and in the instructions that come with
the connect RS232.
                               John Brown

-*-

92171 25-MAR 07:52 General Information
     RE: IRQ Hack. (Re: Msg 92164)
     From: CHARLESAM    To: BROWN80

I'll look in the database and for that info. Thanx Charlie

-*-

End of Thread.

-*-

92160 23-MAR 22:56 General Information
     IRQ Hack.
     From: CHARLESAM    To: ALL

   I just completed my IRQ hack as Cocokiwi. I checked it out by doing a
continuity check from pin #26 on my 6551p in my RS232 deluxe pak to pin #3
on my CPU. Alls well to that point. I can get either rs232 to work but I
crash if I use both and try to run supercomm. I have a modified rs232 I
use for my serial mouse. Again, it works great alone but not when I put in
my telecommunications pak. Any help here will be really appreciated.
   Thanx
 ...Charlie...

-*-

92162 24-MAR 01:22 General Information
     RE: IRQ Hack. (Re: Msg 92160)
     From: KSCALES      To: CHARLESAM

 > I just completed my IRQ hack as Cocokiwi. I checked it out by doing a
 > continuity check from pin #26 on my 6551p in my RS232 deluxe pak to pin
 > #3 on my CPU. Alls well to that point. I can get either rs232 to work but I
 > crash if I use both and try to run supercomm. I have a modified rs232 I
 > use for my serial mouse. Again, it works great alone but not when I put
 > in my telecommunications pak. Any help here will be really appreciated.

Charlie -

To get both ports working at the same time, you will need to strap all
of the "pin 8"s together on the MPI so that the interrupt gets through
regardless of which slot is selected as active.

Good luck... / Ken
 --------------------------------------------------------------------------
 Ken Scales   Delphi:KSCALES   Internet:kscales@delphi.com   CIS:74646,2237

-*-

92168 25-MAR 02:04 General Information
     RE: IRQ Hack. (Re: Msg 92160)
     From: COCOKIWI     To: CHARLESAM

I have never used supercomm...I used Vterm<basic> had to turn off one line!
under os-9 I used Osterm along with the Serial mouse with no problems for the
last few years.....with the addition of the faster software and HD6309E..
anything could happen here! new area of travel! I have not been able to use
mine since my 2400 bd modem was sniched......and now i,m using 28.8K on
<the other machine>........
Dennis

-*-

92169 25-MAR 02:10 General Information
     RE: IRQ Hack. (Re: Msg 92162)
     From: COCOKIWI     To: KSCALES

Kev..my hack uses the UNUSED pin 40 on the MPI...which is linked on all slots.
was the old SEL line....I noticed it was connected to all slots,and was the
reason..for my quick fix!......both RS232 ports should be wired to pin 40 on the

plugin card!.....tis possible be did not do the other port<Rs232 pak>to pin40
and left it on the FIRQ instead! who knows what that would do!<grin>
Dennis

-*-

92170 25-MAR 07:50 General Information
     RE: IRQ Hack. (Re: Msg 92162)
     From: CHARLESAM    To: KSCALES

I'll give that a go, thanx Ken.

-*-

92172 25-MAR 07:56 General Information
     RE: IRQ Hack. (Re: Msg 92168)
     From: CHARLESAM    To: COCOKIWI (NR)

Dennis, what about what Ken suggested, namely strapping pin 8 in the MPI?
Are yours strapped? I ask because theres no mention of it in your hack.
I'll be back Sunday night. Charlie

-*-

End of Thread.

-*-

92165 24-MAR 13:53 System Modules (6809)
     RE: File Managers (Re: Msg 92099)
     From: JRB          To: RANDYKWILSON (NR)

I take it thats the same for all the file manager entries? &&& therefore by
logical deduction the parameters to the OS9I$ calls can be obtained from
the PD.RGS location??
thanks a lot.
Jon.

-*-

92173 25-MAR 08:38 General Information
     RE: Audio CD a last (Re: Msg 92118)
     From: TEDJAEGER    To: HAWKSOFT

 >
 > YAY!!! YAY!!! YAY!!! YAY!!! YAY!!! YAY!!! YAY!!! YAY!!! YAY!!! YAY!!!
 > YAY!!!
 > Glad to hear that you were able to find one!!!!!!!!!!!!!!!!!!!!!!!!
 >
 > A copy of the newest version of VCDP is on it's way!!!!
 >
 I second those exclamations. And thanks much for the update. I do
 dearly love making my IBM clone jealous of the MM1! BTW, is there
 a way to start VCDP in the startup file and begin playing a CD
 without touching the keyboard? The equivalent of having the computer
 press the p key to play?

Bests
---TedJaeger

-*-

92174 25-MAR 08:38 OSK Applications
     RE: MM/1 joystick (Re: Msg 92105)
     From: TEDJAEGER    To: LARRYOLSON

 > Help....
 > A couple of month's ago Mike Haaland left a message about a problem
 > with the MM/1 joystick. I thought that I had saved the message, but I
 > can't find it anywhere. Is there anyone that might have a copy of that
 > message, that they could re-post.

 Larry,
        I dont have the message but the last page in the Gold Runner 2000
manual (which I do have) has some info about problems with the MM1
joystick and fixes. The info is credited to Mike. Perhaps I can tell you
what you need to kknow?


Bests
---TedJaeger

-*-

92183 26-MAR 04:16 OSK Applications
     RE: MM/1 joystick (Re: Msg 92174)
     From: LARRYOLSON   To: TEDJAEGER


 > I dont have the message but the last page in the Gold Runner 2000
 > manual (which I do have) has some info about problems with the MM1
 > joystick and fixes. The info is credited to Mike. Perhaps I can tell you
 > what you need to know?


Ted
   Thanks for pointing out the joystick info in the GoldRunner manual. The
values that Eric got after changing resistor values, is what I get now.
 The Centered values are around 100, with upper left 0, and lower right 127.

   I debating whether to go in and change the resister values so the center
values are around 64. If I do that, then I won't be compatable with all the
other MM/1's. This problem and the little thing about not being able to read
the joystick while playing sound, has me wondering if the joystick port
should be forgotten, and something else used in its place, like one of the
serial ports and a serial type control pad, like on the CD-I machines or the
Nintendo machines. Do you know if anyone has looked into or played around
with what would be needed to be able to plug(with appropriate gender changes),
one of these serial type control pads, into an MM/1 serial port ? Something
like this would sure make it easier on everyone.

Larry


-*-

End of Thread.

-*-

92176 25-MAR 12:36 General Information
     RE: HD (Re: Msg 92144)
     From: JEJONES      To: CLTUCKER

 > Can you tell me the source to purchase a /h1 for the 4IN1? Those sounded
 > like reasonable prices. Huh?(g).

Yup...It just bugs me that the price just happened to go down a month after
I bought my current hard drive. :-)

Seriously, just head for the bookstore or supermarket, find the magazine
rack, and buy a copy of *Deforestation Monthly*--er, *Computer Shopper*.
Look about anywhere therein.

 > Also cables and necessary drivers.

Ditto for cables; heck, you can probably buy the connectors and 50-pin
ribbon cable and roll your own.

Drivers...hmmm.  It's been a while since I had a CoCo, and when I did,
I didn't have a SCSI drive on it, so I'm probably not the best source
for driver information, but I think the way to go these days is to get
Matt Thompson's SCSI software for the CoCo.

Opinions herein are solely those of their respective authors.

Clipper Chip: Big Brother Inside

-*-

92180 25-MAR 17:51 Programmers Den
     Hard drive prob
     From: WDTV5        To: ALL

Howdy all; Once again I seem to have a puzzler here. Trying to make a 2nd
hard drive work on my office CoCo3/OS9 system. Using a B&B XT-RTC interface,
with an ST-11m controller. Drive 0 has been working for several years, its
an older Tandon 252, the one the shack sold as a 10 meg kit 10 years ago for
their pc type machines. I've been able to declare an old L.E. model D dead,
and grabbed the ST-238r out of it. Now this is exactly the same as an St-225
except this drive had plated disks, and it can be used as an MFM drive using
exactly the same descriptor one would use for an ST-225. You only get 21 megs
that way instead of 32, but thats 21 I didn't have before. The problem is that
I can't get it to verify past 10 megs when formatting it. Before someone says
the drive is actually bad, I have 2 of them and they both work identically!
When the first one wouldn't work, I brought my own old 238 in and tried it.
Same problem, verify kicks out continuous errors for any sector address
above $A209. It not track related, I can shut it down to a single side
and get all 614 tracks. Double headed, maybe... I think it worked once...
Turn on all 4 heads and its dead at that address. I've checked the head
select lines at the connector (pins 14 and 18) while its formatting and
the expected activity is there. So I wrote a quicky little basic proggy
to scan the drive after telling it n for the verify question. Then it
does not show the expected head select activity! I'm thinking maybe there
is a bug in BBFHDisk.dr (crc unk, len $6B6) that only shows up for drive
one. And then again, the other drives capacity is about a track short
of triggering it if its also a bug for drive zero. Anybody care to take
a stab at this one? I'm stumped, short of swapping the drive assignments,
a not very trivial job due to the requirements of bootup, I don't know
how else to attack this problem. Any and all help, hints etc (cases of
IceHouse?) gladly accepted.
Cheers, Gene Heskett, WDTV5@delphi.com

-*-

92184 26-MAR 16:02 System Modules (6809)
     Powerboost Problem???
     From: DBREEDING    To: ALL

I've just come across what may be a problem with Powerboost.

A little history.  I had written a database program, originally for the coco
in Basic09.  I've now redone it for OSK in "C".  I had a database of
315 entries, consisting of a date and 6 integers each.  Being the lazy type,
I decided to write a filter to read an ascii text output from the old
program, and send it to stdout, where I could pipe it into the program,
thus eliminating a bunch of tedious typing.

I did it...  Ran it under OSK and it worked apparently perfectly.  I then
compiled the program on the CoCo (both the program and the filter).
But...  the thing wouldn't work.. The way the filter worked, it first "typed
in" a "1" (menu choice) and then "typed in" the filename of the database
the program was going to use (the ascii file was hardcoded in).

But the thing would get all confused.  I worked a couple of days changing
the input methods around, thinking it was a compiler thing, but finally, I
tried something else.. I had been running under Powerboost.  I booted under
6809 mode and it finally worked like a charm (went back to my original
code).  I even tried just running the program with input redirected from
a file created by the filter (the filter was sending the correct data to
standard out).

Apparently, somewhere, data was being lost somewhere in the pipe.  Wrong
values were being received by the program.  I suspect that if data
was being supplied when the program was not ready to accept it, it was
just being shot out into never-never-land.

I wonder if this might be a major problem for Powerboost users.  (I think
it's _got_ to be in this.  If I remember correctly, Powerboost modified
_original_ modules, so it should not be caused by other hacks - or so I
would think.

                         -- David Breeding --
       CompuServe : 72330,2051              Delphi :  DBREEDING
           ***  Sent via   InfoXpress/OSK - Vr. 1.02   ***

-*-

92185 26-MAR 16:57 OSK Applications
     RE: My_Mail (Re: Msg 92114)
     From: GREGL        To: VAXELF (NR)

Did you ever get your E-mail problem solved? I meant to send a message to
SERVICE for you a few days ago, but just got back online today after
struggling with a hardware problem. The problem itself wasn't that bad, but
was very time consuming to fix. Anyway, let me know how you've made out so
far and I'll get it taken care of if it still exists.

        -- Greg

-*-


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