

#: 20775 S1/General Interest
    18-Feb-95  16:54:17
Sb: #help
Fm: tom farrow 72701,543
To: all

Does anyone have pt68k4 in which you use the Alt-86 with PROCOMM if so can you
tell me how to set it up? Tom Farrow (DENVER CO)

There is 1 Reply.

#: 20783 S1/General Interest
    19-Feb-95  13:45:31
Sb: #20775-#help
Fm: Bud Hamblen 72466,256
To: tom farrow 72701,543 (X)

Tom,

I've got a PT68K-4 that had an ALT86 in it until the ALT86 went intermittent.
The ALT86 looks like an XT to MS-DOS software.  Although I didn't spring for a
copy of PROCOMM, there's no reason why it shouldn't work (unless you bought the
Windows version by mistake).

Bud

There is 1 Reply.

#: 20787 S1/General Interest
    20-Feb-95  18:49:02
Sb: #20783-#help
Fm: tom farrow 72701,543
To: Bud Hamblen 72466,256 (X)

When I hook up the modem line I get almost all the lights on or none at all. I
might need to get some help getting the I.O. port set up . The only real reason
that I need to do this is because my work place doesn't have a real good system
when it comes to OS9. I followed the instructions on the card , but to no
avail. Thanks Tom Farrow

There is 1 Reply.

#: 20788 S1/General Interest
    20-Feb-95  22:07:59
Sb: #20787-#help
Fm: David Breeding 72330,2051
To: tom farrow 72701,543 (X)

 > When I hook up the modem line I get almost all the lights on or none at
 > all. I might need to get some help getting the I.O. port set up .

 >  I followed the instructions on the
 > card , but to no avail. Thanks Tom Farrow

Tom,

You are trying to set up a System 4?  Are you using the built-in ports or a
serial card.

If you are using the built-in ports, they are not set up for modem connections.
The wires going to the 25-pin connector are switched so that they can be
connected to a terminal, or possibly another computer.  I have a System 5, and
made up some more connectors from scratch, but you should be able to switch the
pins (push them out from the front side and reinsert them.  If you'll look
closely, the 25-pin connector will have some little numbers by the pin holes.
Here's the connection I got.  Note: I'm giving these #'s as the WIRE NUMBERS on
the FLAT CABLE.  NOT the connector numbers that plug into the Motherboard.  By
"connector" I mean the 25-pin connector you plug your modem cable into.

   #1 DCD (This should have a little paint along its length to let you know
          it is #1)  should go to pin 8 on the connector, but I don't think
          it was connected originally
   #2  <no connection>
   #3  RX pin 3
   #4  RTS pin 4
   #5  TX  pin 2
   #6  CTS pin 6
   #7  DTR pin 20  (Uhhh... maybe it was _this_ one that was not connected,
              and not DCD)...
   #9  Gnd pin 7
   #10  <no connection>

If you're trying to install a serial card, you cannot directly install one in
the computer. I think it has to have a minor modification done to it to make it
work.  I know the internal modem does.  If you want to use a card, I suggest
getting one from Delmar.  They will make the modification for you _AND_
warranty it.


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

There is 1 Reply.

#: 20795 S1/General Interest
    21-Feb-95  22:15:53
Sb: #20788-help
Fm: tom farrow 72701,543
To: David Breeding 72330,2051

Thanks for the info and I'll talk with Delmar in the future. I really
appreciate the help I get from the OS9 folks. Tom Farrow.

#: 20778 S5/OS9 Users Group
    19-Feb-95  00:44:37
Sb: #20763-In search or a COCO III 
Fm: LARRY OLSON 72227,3467
To: - Visitor 75262,1257


   If you are looking for a Gime chip, the following post might be
   helpful.



91447 Thu 19-Jan-95 12:46 General Information (0)
     Gime Chip Source
  From: MARTYGOODMAN To: ALL

The following was posted on Internet by Glenn A. Emelko:

Just to let all you Coco III folks out there know....

Performance Concepts, Inc (my company) produced a large number of
Coco-III based imbedded systems in the late 80's and early 90's, and
when the Coco-III was officially phased out we purchased the remaining
supply of GIME chips (the main custom graphics controller in the
Coco-III) direct from Tandy as a Tandy VAR.  We still have a fair
supply of these chips left, and though we must keep some as repair
stock we may be willing to sell about 50 of them.  Please contact me
if you are interested.

Glenn A. Emelko
(216) 974-9550
Performance Concepts, Inc.

#: 20791 S6/Applications
    21-Feb-95  18:06:17
Sb: #20743-DYUV Graphics
Fm: Craig S. German 72752,2336
To: Kevin Darling 76703,4227 (X)

Kevin,

Thanks for the info.  I checked out Multimedia Forum (again!) and found someone
who had mentioned DYUV in a message.  Wish me luck!

The box we're using is for Bell Atlantic's interactive video trial.  It uses
the CD-I chipset for graphics display.  If you're interested in a vendor name,
try Adaptive Microware in Ft. Wayne(?), IN.  Unfortunately, I don't have the
number handy, but you should probably be able to locate them without much
trouble.  If you can't find them under this name, try Stellar One.

Craig German

#: 20781 S9/Utilities
    19-Feb-95  12:13:34
Sb: #20765-#crc
Fm: Bob van der Poel 76510,2203
To: Paul Hanke 73467,403 (X)

Why not just use dsave to copy the disk file by file. When it craps out, you'll
know which file is fried.

There is 1 Reply.

#: 20786 S9/Utilities
    20-Feb-95  11:46:26
Sb: #20781-#crc
Fm: Paul Hanke 73467,403
To: Bob van der Poel 76510,2203 (X)

Dsave did the trick.  I'd never used dsave before so it was a good learning
process.  Turns out there were 3 files which could have been the culprit.  On
each of them dsave crashed with a 248 error, media full.  Dir e showed that
somehow the file length report was corrupt indicating something like $8 eb5d.
After deleting the suspect files, dsave completed the process.  Before and
after the deletions, free /dd  indicated the same amount tho.   thx,  -ph-

There is 1 Reply.

#: 20790 S9/Utilities
    21-Feb-95  11:45:48
Sb: #20786-crc
Fm: David M. Horn 73260,242
To: Paul Hanke 73467,403 (X)

Paul,

I worked on a system where file sizes larger than the media were reported.  It
was a situation where the system was crashing while a database was being
accessed.  The file headers were corrupted in the process.  Just deleting the
bad files did not completly heal the file system.  You may want to do some more
sanity checks on your files before you trust the drives file structure.

#: 20784 S10/OS9/6809 (CoCo)
    19-Feb-95  18:53:30
Sb: #20756-CoCo 3 Emulator and OS9
Fm: Ian Hodgson 72177,1762
To: John Murphy 73077,2305 (X)

There is no point in going to the trouble converting to single-sided 80 track;
I'm just as happy to keep using the CoCo where it is appropriate to do so.

Yes, I do have the demo version of OS9MAX; the real one might do but the demo
version is not much use.

Oh, the reason for transferring files? I have a lot of stuff in text,
spreadsheet, database etc. form that will be exchanged between the two. For
example, the PC has much nicer database entry than the CoCo, but won't run the
specialized report generator I wrote for OS9. I expect to transfer stuff back
and forth for some time to come.

Ian



#: 20779 S10/OS9/6809 (CoCo)
    19-Feb-95  00:44:46
Sb: #20769-#Basic09 windows
Fm: LARRY OLSON 72227,3467
To: Rogelio Perea 72056,1204 (X)

 > Hello:
 >
 > Is there a way I can coax a Basic09 program to test certain location on
 > the text screen (any 24 row screen, 32 col, 40 col or 80 col) and find
 > which character is lying there?. In RSDOS I have ways to do PEEKs to
 > return the ASCII code of a character, and in Hi-Res text I have HSTAT to
 > find more than the ASCII code..... I have looked all over the OS9 LII docs
 > to find something but to no avail.
 >
 > I need this for a short arcade-style game I am writing, I do have the
 > RSDOS version (I wrote it way back in school time). I had done some of the
 > scrolling and player-moves routines, but lack of a proper method to test
 > if the player has crashed or not...
 >
 > Any help, hints?
 >
 > Rogelio Perea Nogales Sonora MEXICO
 >

     As far as I know, there isn't any legal way to get the screen information
   in Basic09. Depending on what the program does, you can get the info in
   a round about way. If you are using a 80x24 screen, setup an array
   Scrn(80,24), and whenever you write to the screen you also write to the
   array. Then to check for a particular character at a certain location,
   you would just look in the array.
        The array could be Scrn(80,24):STRING[1] or Scrn(80,24):INTEGER
     depending on if you want to work with character strings or character
     values.




There is 1 Reply.

#: 20793 S10/OS9/6809 (CoCo)
    21-Feb-95  19:26:05
Sb: #20779-#Basic09 windows
Fm: Rogelio Perea 72056,1204
To: LARRY OLSON 72227,3467 (X)

I had thought about doin' the STRING thing, but it will s-l-o-w down the
program considerably, beign it an arcade type text screen game. mmmmm, maybe I
will have to try with OS9 Pascal ... sheesh!

Rogelio

There is 1 Reply.

#: 20796 S10/OS9/6809 (CoCo)
    22-Feb-95  00:53:11
Sb: #20793-Basic09 windows
Fm: LARRY OLSON 72227,3467
To: Rogelio Perea 72056,1204

 > I had thought about doin' the STRING thing, but it will s-l-o-w down the
 > program considerably, beign it an arcade type text screen game. mmmmm,
 > maybe I will have to try with OS9 Pascal ... sheesh!
 >
 > Rogelio
 >

   Not knowing what you are trying to do, I can't say how much the program
would be slowed down, but I don't believe it would even be noticeable.

   When you do a print to the screen, are you doing something like this:

   RUN gfx2("curxy", 20,10)
   Print "X";

   How much time would you lose by doing this:

   RUN gfx2("curxy", 20,10)
   Print "X";
   ScreenArray(20,10) = 88      REM 88 = decimal ascii X

   Then to check for a character at a particular screen location just look
   in the ScreenArray at that x,y.

       There was another way of getting screen info legally, but I'm not
   up on exactly how its done, it involves using the GET function to get
   a portion of the screen, and then looking in the GET buffer.

   Larry


#: 20782 S10/OS9/6809 (CoCo)
    19-Feb-95  12:13:35
Sb: #20769-#Basic09 windows
Fm: Bob van der Poel 76510,2203
To: Rogelio Perea 72056,1204 (X)

If you want to know what is in a certain location on the screen you'll have to
remember what you put there <g>. Since OS9 is designed to be run on a
terminal...and terminals usually don't tell. Easy enuf to set up an array to
duplicate the screen (dim screen(80,24):byte) and then just copy the values
into the array as you "print" them onto the screen.

There is 1 Reply.

#: 20794 S10/OS9/6809 (CoCo)
    21-Feb-95  19:29:56
Sb: #20782-#Basic09 windows
Fm: Rogelio Perea 72056,1204
To: Bob van der Poel 76510,2203 (X)

Gee-whizzz.... As I was telling Larry Olson, I had thought about storing the
text lines in an array, but with a corresponding loss of speed.... Is there a
way to do it in assembly language?. I do not know if the text screens of (text)
windows share the same hardware RAM locations, if so, then it would be a matter
of PEEKing in RAM, but as I said, there's some information lacking 'bout the
video RAM....

Rogelio Perea Nogales Sonora MEXICO

There is 1 Reply.

#: 20797 S10/OS9/6809 (CoCo)
    22-Feb-95  16:57:40
Sb: #20794-Basic09 windows
Fm: Bob van der Poel 76510,2203
To: Rogelio Perea 72056,1204

One never knows till you try...but I'd be willing to bet a cup of coffee (ya
gotta come to my place to collect <g>) that it'd be faster to store the status
of the characters, etc. in a byte array and then to check that for further
action than it would be to use PEEKs to check the actual screen data. Probably
not a bad method to use in any event since if you are using graphic-type
screens you will not have any choice at all. Give it a try...if it is too slow
you can always recode parts into assemebler--but if you are using a text screen
I'm sure that any slowdowns will come from other areas besides this.

#: 20792 S10/OS9/6809 (CoCo)
    21-Feb-95  19:24:02
Sb: #20773-Basic09 Windows part 2
Fm: Rogelio Perea 72056,1204
To: Pete Lyall 76703,4230 (X)

Seems like I have some more reading to do... :-) GREAT!!, everyday I can learn
something new...

Rogelio

#: 20776 S12/OS9/68000 (OSK)
    18-Feb-95  17:32:40
Sb: #20772-#IRQ Stack
Fm: Steve Wegert 76703,4255
To: David Breeding 72330,2051 (X)

Hi David!

Geeze .... back to 1992 eh?

Leseee .... reviewing the init module of my current os9boot with moded I see
that the IRQstack size parameter reported is 1024. I believe I did indeed bump
that up from a previously reported 512.

I do believe we're speaking in "word size" here so in bytes, that would be
4096.


*- Steve -*


There is 1 Reply.

#: 20777 S12/OS9/68000 (OSK)
    18-Feb-95  23:09:24
Sb: #20776-#IRQ Stack
Fm: David Breeding 72330,2051
To: Steve Wegert 76703,4255 (X)

 > Geeze .... back to 1992 eh?

Yeah, I save anything that looks like it might be useful.. (I was looking
forward to going to OSK for a long time..  All that stuff was Greek back then,
but it is meaningful, now.. <G>

 > Leseee .... reviewing the init module of my current os9boot with moded I
 > see that the IRQstack size parameter reported is 1024. I believe I did
 > indeed bump that up from a previously reported 512.
 >
 > I do believe we're speaking in "word size" here so in bytes, that would
 > be 4096.

Long word is what my moded reports..  Mine was 256 (words)..  I bumped mine up
to 512 last night, might go on up.

Thanks, Steve.

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

There is 1 Reply.

#: 20789 S12/OS9/68000 (OSK)
    21-Feb-95  11:38:51
Sb: #20777-IRQ Stack
Fm: David M. Horn 73260,242
To: David Breeding 72330,2051

David,

Microware sets the IRQ stack size intentionally low to get good minimum memory
numbers for marketing.  If your system has a significant amount of IRQ activity
(such as serial I/O), this number should be increased generously.  I was
working with a system that had 32 high speed intelligent serial ports, upto 28
more conventional serial ports, and lots of hard disk activity.  I think we
increased the IRQ stack to 32k long words.  OS-9 does not always report IRQ
stack problems gracefully, so increasing the IRQ stack is a good thing to try
if you can't figure out strange behavior in a complex system.

David Horn

Press <CR> !>