4667 lines
156 KiB
Plaintext
4667 lines
156 KiB
Plaintext
read new nonstop follow
|
||
88291 30-JUN 19:05 OSK Applications
|
||
MM/1 Teac FD55FGR setup??
|
||
From: NIMITZ To: ALL
|
||
|
||
Can anyone give me information regarding software and hardware setup of
|
||
and FD55FGR floppy? I need to set this up to read 360K CoCo diskettes on
|
||
an MM/1 I want to ship in the am tomorrow. I do have the drive working,
|
||
and setup as drive 1. But I can't get it to format a 360K diskette, or read
|
||
one.
|
||
|
||
I would rather set the drive to spin at 300 rpm, than adjust the CPU
|
||
board settings. Thanks!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88294 30-JUN 20:18 OSK Applications
|
||
RE: MM/1 Teac FD55FGR setup?? (Re: Msg 88291)
|
||
From: DSRTFOX To: NIMITZ
|
||
|
||
David, your best bet is to try and get Marty Goodman. Second best: there
|
||
are a couple files covering use of a Teac 55 as a 360K drive in the CoCo SIG,
|
||
and some files covering several drives and settings. Check the hardware section
|
||
of the database!
|
||
|
||
-*-
|
||
|
||
88301 1-JUL 01:06 OSK Applications
|
||
RE: MM/1 Teac FD55FGR setup?? (Re: Msg 88291)
|
||
From: COCOKIWI To: NIMITZ
|
||
|
||
THAT! problems was in my EPROM....The "SLOW" command had been zapped by
|
||
a BUG ...one bit changed "SLGW" So I,m thinking it was in SLOW mode,and it
|
||
was STILL in FAST mode<Shheee>a bit slipped in my Eprom....There is no CPU
|
||
settings as you put it<g> the only ajustment is a Ajustable preset pot on
|
||
the Motor board<sometimes>.SPEED is set to +/- 4 at 300 rpm..mine were
|
||
at 300/2
|
||
|
||
-*-
|
||
|
||
88302 1-JUL 01:26 OSK Applications
|
||
RE: MM/1 Teac FD55FGR setup?? (Re: Msg 88294)
|
||
From: NIMITZ To: DSRTFOX
|
||
|
||
Thanks, Frank. I let the magic smoke out of a drive cable trying one
|
||
suggestion this morning. Thank God it was not a system component like the I/O
|
||
board!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88292 30-JUN 20:11 General Information
|
||
RE: OS-9 Books (Re: Msg 88271)
|
||
From: DSRTFOX To: CPERRAULT
|
||
|
||
I cover a good deal about Level II in "68' micros" magazine... that might be
|
||
what you want...
|
||
|
||
-*-
|
||
|
||
88293 30-JUN 20:15 General Information
|
||
RE: nitro/lha (Re: Msg 88286)
|
||
From: DSRTFOX To: JRUPPEL
|
||
|
||
Actually, Gene sent me the older version of LZH, and I tried downloading the
|
||
LZH version. That did the trick! There is apparently a bad "xlh" file in the
|
||
AR archive!! Someone else needs to d/l the AR file and burst it to see if
|
||
they get the same results before it is condemned though.
|
||
|
||
-*-
|
||
|
||
88295 30-JUN 20:55 General Information
|
||
RE: nitro/lha (Re: Msg 88293)
|
||
From: MITHELEN To: DSRTFOX
|
||
|
||
I just downloaded the lha 2.11c AR file, and it appears to be fine to me. I
|
||
even extracted it, and did an ident on the xlh file, and it all checked
|
||
out fine.
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88299 30-JUN 23:15 General Information
|
||
RE: nitro/lha (Re: Msg 88293)
|
||
From: JRUPPEL To: DSRTFOX
|
||
|
||
Well, no need to condemn the file yet! I downloaded the AR'd version (it took a
|
||
few tries), but all is working fine! The only thing I haven't figured out is
|
||
how to melt non-lzh files with it. I gathered from the docs that this can be
|
||
done
|
||
but Ihaven't had any success yet. I tried to upload that xlh file,BTW, and the
|
||
ol' bitbanger just isn't up to it. Too much for it to handle, I think. I can
|
||
send a copy Snail Mail, if you'd like. Let me know.
|
||
|
||
John Ruppel
|
||
CocoNuts in Lansing
|
||
|
||
-*-
|
||
|
||
88330 2-JUL 22:30 General Information
|
||
RE: nitro/lha (Re: Msg 88260)
|
||
From: DBREEDING To: DSRTFOX
|
||
|
||
> When I tried using the "old" LHA, I got errors on EVERY file. When I used
|
||
> the 2.11c version in the NEW UPLOADS section, the only error was on the
|
||
> xlh file. And I DID d/l the .AR version!
|
||
|
||
Which old LHA are you referring to? What I've experienced is that the old
|
||
"unlzh" works pretty good. The Matt Thompson version cannot handle extended
|
||
headers, and it inserted an extended header of its own - unless you excluded
|
||
it - that no other lha could burst. I have 2.11c, but haven't fooled with
|
||
it much. It won't be able to burst arcs with the Matt Thompson header.
|
||
|
||
I may be off-track here, but thought this might be your problem.
|
||
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88375 4-JUL 10:32 General Information
|
||
RE: nitro/lha (Re: Msg 88330)
|
||
From: DSRTFOX To: DBREEDING
|
||
|
||
That was indeed the problem, David! I WAS using the Matt Thompson LHA at
|
||
first. Got 2.11c working now, for some reason the two times I d/l'd the
|
||
.AR version, the xlh file was bad.. maybe a bad sector on the disk? AnyWAY,
|
||
I d/l'd the /lzh file after soemone sent me Matt's LZH via mail. Worked like
|
||
a charm! Thanks for the input!
|
||
|
||
-*-
|
||
|
||
88452 7-JUL 00:07 General Information
|
||
RE: nitro/lha (Re: Msg 88375)
|
||
From: DBREEDING To: DSRTFOX (NR)
|
||
|
||
> That was indeed the problem, David! I WAS using the Matt Thompson LHA at
|
||
> first. Got 2.11c working now, for some reason the two times I d/l'd the
|
||
> .AR version, the xlh file was bad.. maybe a bad sector on the disk?
|
||
> AnyWAY, I d/l'd the /lzh file after soemone sent me Matt's LZH via mail.
|
||
> Worked like a charm! Thanks for the input!
|
||
|
||
You mean my msg worked? I actually intended to delete the request to send
|
||
it but it slipped by. <G> After entering it and reading subsequent msgs,
|
||
it seemed that there was a glitch in one of the archives. It was a few
|
||
days before I uploaded and forgot. Guess a blind hog will find an acorn
|
||
occasionally ;-)
|
||
|
||
I like the 2.11 quite well, from what little I've used it. Seems maybe a
|
||
little faster than Matt Thompson's. Matt's seemed to work OK, but it
|
||
didn't seem to enter _its_ extended header correctly so other lha's could
|
||
unarc its files, and it seemed to have trouble with other systems' extended
|
||
headers.
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88296 30-JUN 21:24 General Information
|
||
RE: IX Test (Re: Msg 88258)
|
||
From: HAWKSOFT To: BOISY
|
||
|
||
> Boisy G. Pitre__ __ __ Delphi: BOISY
|
||
> |_ _| \ \/ / CompuServe: 74464,3005
|
||
> I use... _| |_ > < Internet:boisy@os9er.waukee.ia.us
|
||
> |_____|NFO/_/\_\PRESS 1.2.0 OS-9 -- King of Operating Systems
|
||
|
||
Hey Boisey! Isn't that . . . . . . . . OSK -- the Operating System King?
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88300 1-JUL 00:41 General Information
|
||
RE: IX Test (Re: Msg 88296)
|
||
From: BOISY To: HAWKSOFT
|
||
|
||
Hey, I never thought of that! Good catch!
|
||
|
||
-*-
|
||
|
||
88329 2-JUL 22:29 General Information
|
||
RE: IX Test (Re: Msg 88258)
|
||
From: DBREEDING To: BOISY
|
||
|
||
> IX Test... Please ignore.
|
||
>
|
||
> Muchas Gracias.
|
||
> --
|
||
> Boisy G. Pitre__ __ __ Delphi: BOISY
|
||
> |_ _| \ \/ / CompuServe: 74464,3005
|
||
> I use... _| |_ > < Internet: > boisy@os9er.waukee.ia.us
|
||
|_____|NFO/_/\_\PRESS 1.2.0 OS-9 -- King of
|
||
> Operating Systems
|
||
|
||
Gret signature! Love it.
|
||
|
||
How do you like it? Great, huh? I've messed around and not ordered mine
|
||
yet. Course I do have the coco version, so I'm not that desperate.
|
||
|
||
With ix, bet you don't learn to navigate over on CIS as quickly as you
|
||
would if you didn't have it. <G>
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88341 3-JUL 11:06 General Information
|
||
RE: IX Test (Re: Msg 88329)
|
||
From: SCWEGERT To: DBREEDING
|
||
|
||
> With ix, bet you don't learn to navigate over on CIS as quickly as you
|
||
> would if you didn't have it. <G>
|
||
>
|
||
|
||
In my case, it's the other way around. Never could figure out the Delphi
|
||
command structure. :-)
|
||
|
||
|
||
|
||
*- Steve -*
|
||
|
||
|
||
-*-
|
||
|
||
88451 7-JUL 00:06 General Information
|
||
RE: IX Test (Re: Msg 88341)
|
||
From: DBREEDING To: SCWEGERT
|
||
|
||
> > With ix, bet you don't learn to navigate over on CIS as quickly as you
|
||
> > would if you didn't have it. <G>
|
||
|
||
> In my case, it's the other way around. Never could figure out the Delphi
|
||
> command structure. :-)
|
||
|
||
Same here. I started over on CIS. Never _REALLY_ mastered it there, but did
|
||
learn how to get around. Now with ix, you don't have to <G>.
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88297 30-JUN 21:24 General Information
|
||
RE: Mucked up CM-8 (Re: Msg 88277)
|
||
From: HAWKSOFT To: ILLUSIONIST
|
||
|
||
Mike!
|
||
|
||
John is 100% right! I used a R/S bulk tape eraser to de-gauss
|
||
my CM-8 screen. In fact I did one at a Glenside meeting. Looks REAL NEAT
|
||
if you have the monitor on and a picture showing!!! When you do it, just
|
||
turn on the de-gausser a couple of feet away from the screen and slowly
|
||
get closer and closer moving it evenly around/across the screen area and then
|
||
just a slowly move away. That should clear it up. My CM-8 had a green spot
|
||
about 10 inches across when I got it, but, it's fine now.
|
||
|
||
Chris
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88298 30-JUN 22:58 System Modules (6809)
|
||
RE: RBF32 (Re: Msg 88248)
|
||
From: VE3DAC To: WDTV5
|
||
|
||
You got it right about the stack. If I can get the msg to you, he gives a
|
||
few hints on what the problems might be. I gather he disassembled some of
|
||
RBF32 from what he said. I keep forgetting, theres no quoted stuff ahead
|
||
of this reply. I'll try to get the stuff to you this weekend from Gene K.
|
||
Merv
|
||
|
||
-*-
|
||
|
||
88305 1-JUL 22:23 System Modules (6809)
|
||
RE: RBF32 (Re: Msg 88298)
|
||
From: WDTV5 To: VE3DAC
|
||
|
||
Yeah, Paul just said he thought Chris was doing something to restore the
|
||
normal 6809 stacking order. Thats too bad if thats the case, it wastes
|
||
time in the time critical inerrupt(interrupt) service routine, something
|
||
that this chip doesn't really have time to do if its goinf to service
|
||
a non-fifo'd comm chip at speeds above 9600 baud. Not have had any msgs
|
||
from Chris in a year or so, I haven't had any indicators as to how he
|
||
was planning on doing his. Can someone further enlighten us on that please!
|
||
Cheers, Gene
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88303 1-JUL 13:14 General Information
|
||
RE: Sony Service Anecdote (Re: Msg 88289)
|
||
From: MARTYGOODMAN To: PRCORWIN
|
||
|
||
Thanks for that tip! The drive, if it works, will be used
|
||
just to play around with on SCSI systems... just to test out
|
||
systems... not as a repository for valuable data. But again,
|
||
thanks for the warning.
|
||
|
||
---marty
|
||
|
||
-*-
|
||
|
||
88435 6-JUL 01:42 General Information
|
||
RE: Sony Service Anecdote (Re: Msg 88303)
|
||
From: PRCORWIN To: MARTYGOODMAN
|
||
|
||
no problem...
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88304 1-JUL 15:03 General Information
|
||
MSDOS SOFTWARE
|
||
From: MROWEN01 To: ALL
|
||
|
||
Does any one know of a MS-DOS package that will read an OS-9 disk? I checked
|
||
out the colorc program, but it only reads RS-DOS format. I know I can use
|
||
PCDos to write from OS-9 to DOS, but I want to read directly from the OS-9
|
||
disk to a PC. I'm running OS9 on a COCO3. I'm specifically looking to read
|
||
an
|
||
80trk OS-9 disk. Thanks!
|
||
-Mike
|
||
|
||
-*-
|
||
|
||
88314 2-JUL 12:36 General Information
|
||
RE: MSDOS SOFTWARE (Re: Msg 88304)
|
||
From: PHXKEN To: MROWEN01
|
||
|
||
I believe that the only programs to read/write os-9 disks from ms-dos
|
||
machine are commercial ones. I have not been able to find a shareware
|
||
version. As to your question on the Development Package, many of the
|
||
utilities found therein are also in the Level One Package which you
|
||
might find at a cheaper price. Someone told you that he heard that
|
||
tsmon was not so good but it does the job if you want to connect another
|
||
machine to your os-9 system without using terminal programs on each.
|
||
You can use your ms-dos machine to LOGIN to the CoCo and see what is on
|
||
the CoCo Disks. There are a few programs from the level One package
|
||
that give Level II fits but most of the stuff found in the Dev Pak and
|
||
also on Level One works okay. Many of the Dev Pak items also have been
|
||
improved with shareware items found on Delphi.
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88306 1-JUL 22:43 Programmers Den
|
||
BASIC09/Microware BASIC INT function
|
||
From: JEJONES To: ALL
|
||
|
||
I was taking a look at a BASIC09 program in the latest *UpTime*, and in the
|
||
process of modifying it, I tripped over something that I figured is worth
|
||
passing along to others.
|
||
|
||
I was trying to move some coordinate conversion into a call to gfx2 (bgfx
|
||
for those of us with MM/1s), and figured I could turn the moral equivalent
|
||
of
|
||
|
||
xs := x0 + mx * x
|
||
ys := y0 + my * y
|
||
rs := mr * r
|
||
RUN gfx2(path,"circle",xs,ys,rs)
|
||
|
||
into
|
||
|
||
RUN gfx2(path,"circle",INT(...),INT(...),INT(...))
|
||
|
||
replacing the ellipses with the right hand sides of the assignments
|
||
to the corresponding variables (which were declared integer, of course).
|
||
|
||
BLAMMO! It barfed--but why? INT() returns the greatest integer less
|
||
than or equal to its argument, doesn't it?
|
||
|
||
It finally occurred to me--yes, INT() does return that--but it returns
|
||
it as a REAL! I changed the INT() into FIX(), and all was well.
|
||
|
||
Kind of subtle, eh?
|
||
|
||
Opinions herein are solely those of their respective authors.
|
||
|
||
Clipper Chip: Big Brother Inside
|
||
|
||
-*-
|
||
|
||
88320 2-JUL 16:37 Programmers Den
|
||
RE: BASIC09/Microware BASIC INT function (Re: Msg 88306)
|
||
From: JOHNBAER To: JEJONES
|
||
|
||
|
||
James,
|
||
|
||
> xs := x0 + mx * x
|
||
> ys := y0 + my * y
|
||
> rs := mr * r
|
||
> RUN gfx2(path,"circle",xs,ys,rs)
|
||
>
|
||
> into
|
||
>
|
||
> RUN gfx2(path,"circle",INT(...),INT(...),INT(...))
|
||
> ^^^^
|
||
|
||
I asume you did change the `gfx2' to bgfx right.. and this is
|
||
just a typo here <g>.
|
||
|
||
I'm confused as it is. Don't make it worse! <Big Grin>.
|
||
|
||
|
||
-*-
|
||
|
||
88323 2-JUL 18:05 Programmers Den
|
||
RE: BASIC09/Microware BASIC INT function (Re: Msg 88320)
|
||
From: JEJONES To: JOHNBAER
|
||
|
||
> I asume you did change the `gfx2' to bgfx right.. and this is
|
||
> just a typo here <g>.
|
||
|
||
To run on the MM/1, yes, I did change it to bgfx. The original
|
||
said gfx2, since it ran on the CoCo.
|
||
|
||
> I'm confused as it is. Don't make it worse! <Big Grin>.
|
||
|
||
I guess I just wanted company--I was confused, too. :-) I'm
|
||
still a little puzzled--the resulting display is clearly symmetric,
|
||
but taking advantage of that may take some thought.
|
||
|
||
I'm still considering how to re-eliminate the recursion after having
|
||
put it back in so I could make sure I understood how it worked. One
|
||
can either store the true depth with the stack entry so that entries
|
||
are thrown out after use, or one can add a Boolean that tells whether
|
||
the routine is on its way down or on its way up, and I'm not sure
|
||
which is better. I'll probably try both of them, just to see whether
|
||
I can make it any faster--but the recursive version is much shorter
|
||
and clearer. Eliminating recursion can be a very good thing, but for
|
||
pedagogical purposes, IMHO the explicit stack twiddling can distract
|
||
the reader.
|
||
|
||
Opinions herein are solely those of their respective authors.
|
||
|
||
Clipper Chip: Big Brother Inside
|
||
|
||
-*-
|
||
|
||
88340 3-JUL 10:37 Programmers Den
|
||
RE: BASIC09/Microware BASIC INT function (Re: Msg 88320)
|
||
From: JEJONES To: JOHNBAER
|
||
|
||
Well...I think I've about gotten as unconfused as possible, unless I decide
|
||
to investigate tweaking some of the parameters. It's been a LOOOOOOOONG
|
||
time since I did a real live proof by induction, but it paid off, because
|
||
it showed where the added symmetry is and cut the recursive calls in half,
|
||
and will do the analogous thing if I re-eliminate the recursion. It's
|
||
now about five and a half times faster than it was, but it will bug me
|
||
until I polish it off by seeing whether recursion elimination will speed
|
||
it up any more.
|
||
|
||
Opinions herein are solely those of their respective authors.
|
||
|
||
Clipper Chip: Big Brother Inside
|
||
|
||
-*-
|
||
|
||
88346 3-JUL 12:48 Programmers Den
|
||
RE: BASIC09/Microware BASIC INT function (Re: Msg 88340)
|
||
From: JOHNBAER To: JEJONES
|
||
|
||
|
||
> It's now about five and a half times faster than it was, but
|
||
> it will bug me until I polish it off by seeing whether recursion
|
||
> elimination will speed it up any more.
|
||
|
||
James, I'd like to see that code when your done. Would love
|
||
to learn from it. Let me know...
|
||
|
||
--
|
||
John -
|
||
|
||
< Posted with Ved 2.3.1 & IX 1.2.0 >
|
||
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88308 1-JUL 23:47 General Information
|
||
Drives
|
||
From: REVWCP To: ALL
|
||
|
||
Dear Friends:
|
||
I recently received a large number of 5-1/4 80 tracks disks. I have a drive
|
||
from a Tabdy 2000 which is capable of reading them, but I am not certain
|
||
what to dmode it to. Any suggestions?
|
||
With all best wishes,
|
||
Brother Jeremy, CSJW
|
||
OS9 User's Group Treasurer
|
||
|
||
-*-
|
||
|
||
88309 2-JUL 08:38 General Information
|
||
RE: Drives (Re: Msg 88308)
|
||
From: DONALDS To: REVWCP
|
||
|
||
I have a couple of the same types of drives that I have used and I set them
|
||
the same as I would my 3.5 drive 80trk, 6ms, ilv 2, etc. I hope that helps
|
||
don
|
||
|
||
-*-
|
||
|
||
88321 2-JUL 17:25 General Information
|
||
RE: Drives (Re: Msg 88308)
|
||
From: JRUPPEL To: REVWCP
|
||
|
||
The original 80 track Device descriptor in the BASIC09/CONFIG disk was actually
|
||
for the 5-1/4 drive...96 tracks per inch...Just Dmode to that, or plug your
|
||
drive in where you presently have your 3-1/2 80 track drive. It's a direct
|
||
substitution.
|
||
Hope this helps!
|
||
John Ruppel
|
||
CocoNuts in Lansing
|
||
|
||
-*-
|
||
|
||
88322 2-JUL 17:50 General Information
|
||
RE: Drives (Re: Msg 88321)
|
||
From: NIMITZ To: JRUPPEL
|
||
|
||
John, were the 5.25 inch 40 track drives at 48 tpi, or 96tpi???
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88337 3-JUL 02:40 General Information
|
||
RE: Drives (Re: Msg 88322)
|
||
From: JRUPPEL To: NIMITZ
|
||
|
||
Dave,
|
||
The 40 tracker's were 48 tpi, the 80's were 96. They had descriptors written
|
||
in the MODULES file for both. Luckily for us, the 80 track dd works just fine
|
||
with a 3.5" drive.
|
||
John Ruppel
|
||
CocoNuts in Lansing
|
||
|
||
-*-
|
||
|
||
88349 3-JUL 12:55 General Information
|
||
RE: Drives (Re: Msg 88337)
|
||
From: NIMITZ To: JRUPPEL
|
||
|
||
Thanks, John. I'm trying to get this Teac FD55FGR to read 40 track DSDD
|
||
diskettes. It's been awhile since I used the CoCo. Hopefully someone
|
||
who has done this will come along and tell me how they did it.
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88361 3-JUL 22:24 General Information
|
||
RE: Drives (Re: Msg 88349)
|
||
From: WDTV5 To: NIMITZ
|
||
|
||
Hi David; I'm probably blowin smoke 'cause yer on an MM/1 instead of OS9
|
||
level 2 & a CoCo. However, to remind all, if the dmode "dns" var is set
|
||
correctly, then the drive can read both 96 tpi and 48 tpi disks. What
|
||
happens is that rbf goes and snoops thru sector zero in one of its seeks,
|
||
gets that var from the PD data. On finding a disk whose "dns"=01 in a drive
|
||
whose descriptor is set at dns=03, cc3disk will proceed to dbl-step the
|
||
drive thereby keeping the heads fairly well centered on the data written
|
||
by a 40 track, 48 tpi drive. I would hope that the floppy driver for the
|
||
MM/1 is at least that smart. To recap, you *can* format and use 96tpi drives
|
||
just fine with the dns set to $01, but the driver won't know what to do
|
||
when a genuine 48 tpi, 40 track disk is in that 80 track drive. If dns=03
|
||
for the 96 tpi drive, then it converts to dbl-step automaticly.
|
||
Cheers, Gene
|
||
|
||
-*-
|
||
|
||
88376 4-JUL 10:39 General Information
|
||
RE: Drives (Re: Msg 88349)
|
||
From: DSRTFOX To: NIMITZ
|
||
|
||
David, I didn't realize you ere doing this on a CoCo! I remember reading
|
||
somewhere that the device descriptor has a double-step flag. I THINK you can
|
||
use dmode to set the bit for double step, and it will double step to read a 40
|
||
track disk in an 80 track drive. Check it out! Then you just set your 80T
|
||
drive as such, flag it to allow double step, and go!
|
||
|
||
-*-
|
||
|
||
88397 4-JUL 21:18 General Information
|
||
RE: Drives (Re: Msg 88376)
|
||
From: NIMITZ To: DSRTFOX (NR)
|
||
|
||
I'm not working on a CoCo, Frank. This is the next MM/1 to shipl.
|
||
|
||
I am probably going to call a client in the morning to say it will take longer
|
||
to figure out, and try to ship without the 5.25 drive.
|
||
|
||
David
|
||
|
||
PS - it is now working fine as a HD drive 1.32 Meg!
|
||
|
||
-*-
|
||
|
||
88405 5-JUL 00:35 General Information
|
||
RE: Drives (Re: Msg 88349)
|
||
From: LARRYOLSON To: NIMITZ
|
||
|
||
|
||
David,
|
||
|
||
Here is a dmode that I use on my MM/1 to read CoCo3 OS9 lvII disks.
|
||
|
||
|
||
name=c1
|
||
drv=1 stp=3 typ=$20 dns=$01 cyl=40 sid=2 vfy=0 (on) sct=18 t0s=18
|
||
sas=8 ilv=3 tfm=0 toffs=0 soffs=1 ssize=256 cntl=$0000 trys=0 lun=0
|
||
wpc=0 rwr=0 park=0 lsnoffs=0 totcyls=80 ctrlrid=0 rates=$10
|
||
scsiopt=$0000 maxcount=65535
|
||
|
||
larry olson
|
||
|
||
----- Larry Olson -----
|
||
|
||
-*-
|
||
|
||
88408 5-JUL 01:17 General Information
|
||
RE: Drives (Re: Msg 88405)
|
||
From: KSCALES To: LARRYOLSON
|
||
|
||
Larry -
|
||
|
||
> Here is a dmode that I use on my MM/1 to read CoCo3 OS9 lvII disks.
|
||
>
|
||
> name=c1
|
||
> drv=1 stp=3 typ=$20 dns=$01 cyl=40 sid=2 vfy=0 (on) sct=18 t0s=18
|
||
> sas=8 ilv=3 tfm=0 toffs=0 soffs=1 ssize=256 cntl=$0000 trys=0 lun=0
|
||
> wpc=0 rwr=0 park=0 lsnoffs=0 totcyls=80 ctrlrid=0 rates=$10
|
||
> scsiopt=$0000 maxcount=65535
|
||
|
||
Critical information to put the above info into context:
|
||
1) what type of CC3 LvII diskettes are you reading? (Assumption from
|
||
the "dns=$01" is that you are using 5.25 double-sided 360K diskettes,
|
||
since 40-track 3.5" drives are pretty rare.)
|
||
2) what type of drive are you using on the MM/1?
|
||
- Hi-density 1.2M 5.25"?
|
||
- 720K double-density double-sided 80-trk 5.25"?
|
||
- 360K double-density double-sided 40-trk 5.25"?
|
||
|
||
Cheers... / Ken
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88409 5-JUL 06:48 General Information
|
||
RE: Drives (Re: Msg 88405)
|
||
From: NIMITZ To: LARRYOLSON
|
||
|
||
Thanks, Larry. I'll give that a shot!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88431 6-JUL 01:13 General Information
|
||
RE: Drives (Re: Msg 88408)
|
||
From: LARRYOLSON To: KSCALES
|
||
|
||
|
||
Ken,
|
||
I'm sorry, I should have added a little more information with that post,
|
||
so....
|
||
|
||
The drives on the CoCo are 5-1/4 double sided 360k.
|
||
|
||
The drive in the MM/1 is a teac 55b 5-1/4 double sided 360k.
|
||
|
||
----- Larry Olson -----
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88310 2-JUL 10:20 OSK Applications
|
||
MM/1 drive cabling?
|
||
From: NIMITZ To: ALL
|
||
|
||
I'm still looking for help with my 5 1/4 drive problem. Apparently I have
|
||
my Dmode parameters set right, and Frank Swygerts note lead me to information
|
||
that confirms this. But the drive persists in giving a seek error on attemp
|
||
to read a dir, or write formating info. I've tried a Teac FD55FGR set to s
|
||
|
||
720K mode with dual speed mode set. (This one burned up the drive cable when
|
||
I tried to toggle J13 (to set line 2 high). I also tried a Chinon FR-506.
|
||
|
||
Any more clues clues guys?? I'm hurting here!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88377 4-JUL 10:42 OSK Applications
|
||
RE: MM/1 drive cabling? (Re: Msg 88310)
|
||
From: DSRTFOX To: NIMITZ
|
||
|
||
I don't think you can FORMAT a 40T disk in the 80T drive, but CAN read and
|
||
wirte to it. Hmmm.. but format DOES allow specifying tracks... but then that
|
||
might not double-step the drive, just format teh first 40. You'll have to
|
||
try that!
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88311 2-JUL 10:34 Applications (6809)
|
||
RE: CRC RS 232 (Re: Msg 88084)
|
||
From: AUTOTECH To: MRUPGRADE
|
||
|
||
|
||
The ribbon cable supplied with the CRC RS232 pack should have a stripe
|
||
on one side. The stripped side goes to pin 1 of the header connector of
|
||
the pack.
|
||
|
||
|
||
. . . . . . . * pin 1
|
||
. . . . . . .
|
||
===================== <--- circuit board
|
||
|
||
|
||
The above diagram should be enough to get you hooked up.
|
||
|
||
Ron
|
||
|
||
|
||
-*-
|
||
|
||
88312 2-JUL 10:43 General Information
|
||
slowio
|
||
From: AUTOTECH To: ALL
|
||
|
||
I have been looking for the program "slowio" and it doesn't appear
|
||
in any of the databases I've looked in here. Does anybody know if it's
|
||
here or where I could find it.
|
||
|
||
Thanks, Ron
|
||
|
||
|
||
-*-
|
||
|
||
88315 2-JUL 13:14 General Information
|
||
RE: slowio (Re: Msg 88312)
|
||
From: MITHELEN To: AUTOTECH
|
||
|
||
Go to the Applocations Database, and do a SEARCH SLOW... That will point you
|
||
to it.
|
||
--
|
||
Paul Jerkatis
|
||
Assistant OS-9 Database Manager
|
||
|
||
-*-
|
||
|
||
88394 4-JUL 21:03 General Information
|
||
RE: slowio (Re: Msg 88315)
|
||
From: AUTOTECH To: MITHELEN
|
||
|
||
Thanks for the info on finding slowio. I never thought to shorten my
|
||
search to "slow".
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88313 2-JUL 11:29 General Information
|
||
OS-9 Live!
|
||
From: BOISY To: ALL
|
||
|
||
Just a reminder:
|
||
|
||
The next OS-9 Live! conference is coming next Saturday (July 9th). The
|
||
topic of discussion will be using termcap. I will be out of town that
|
||
weekend, and thus will not be able to attend the conference. However,
|
||
my esteemed colleague, James Jones, will moderate the conference in my
|
||
absence.
|
||
|
||
At the Midwest Internet Expo held here in Des Moines last week, I picked
|
||
up a copy of the O'Reilly and Associates book, "Using Termcap and Terminfo"
|
||
which will be consulted during the conference. I hope the conference
|
||
will be helpful to you.
|
||
--
|
||
Boisy G. Pitre__ __ __ Delphi: BOISY
|
||
|_ _| \ \/ / CompuServe: 74464,3005
|
||
I use... _| |_ > < Internet: boisy@os9er.waukee.ia.us
|
||
|_____|NFO/_/\_\PRESS 1.2.0 OS-9 -- King of Operating Systems
|
||
|
||
-*-
|
||
|
||
88339 3-JUL 09:54 General Information
|
||
RE: OS-9 Live! (Re: Msg 88313)
|
||
From: JOHNREED To: BOISY
|
||
|
||
> Just a reminder:
|
||
>
|
||
> The next OS-9 Live! conference is coming next Saturday (July 9th). The
|
||
> topic of discussion will be using termcap.
|
||
|
||
Great timing, Boisy. Err, I mean the subject, not your absence (GRIN).
|
||
|
||
I just installed COHERENT on my "386" (missed the "deal" on OS-9000
|
||
a couple fests ago - and I want to learn more about UNIX anyway).
|
||
Right now, I am up to my ears in Termcaps and Terminfo. By the time
|
||
of the conf, I might be able to describe how I put a terminfo entry
|
||
for the MM/1 into the 386-box ---- or describe how I failed and beg
|
||
for assistance );
|
||
|
||
********************************
|
||
A stitch in time --------------------
|
||
------ is worth two in the bush
|
||
|
||
John R. Wainwright <<CIS -- 72517,676>> <<DELPHI -- JOHNREED>>
|
||
|
||
-*-
|
||
|
||
88350 3-JUL 13:37 General Information
|
||
RE: OS-9 Live! (Re: Msg 88339)
|
||
From: KSCALES To: JOHNREED
|
||
|
||
Hi, John -
|
||
|
||
> Right now, I am up to my ears in Termcaps and Terminfo. By the time
|
||
> of the conf, I might be able to describe how I put a terminfo entry
|
||
> for the MM/1 into the 386-box ---- or describe how I failed and beg
|
||
> for assistance );
|
||
|
||
Great fun. I set up a Terminfo on my HP-UX box at work for the MM/1,
|
||
which I used until I got a good VT100 emulator running on it <g>.
|
||
|
||
Basic steps from memory (with Coherent, your milage may vary):
|
||
|
||
- copy the MM/1 TermCAP entries to a file (say mm1_termcap)
|
||
- enter: captoinfo <mm1_termcap >mm1_terminfo
|
||
- enter: mkdir JRWINFO
|
||
- enter: mkdir JRWINFO/term
|
||
- enter: setenv TERMINFO JRWINFO
|
||
- enter: tic mm1_terminfo
|
||
|
||
This will probably create up to 36 directories under JRWINFO/term.
|
||
Some of these directories may be empty, but there should be files under
|
||
k (k2), m (mm1), v (vsc), etc. Any empty directories could be deleted.
|
||
BTW, this is the same basic sequence that I used for creating the
|
||
Terminfo libraries for the OSK ports of 'sc' and 'rogue'.
|
||
|
||
Now, if you have Superuser access <g>, you can add the new files into the
|
||
standard system Terminfo library (maybe under /etc/term, or somesuch).
|
||
At work, I had to set my login profiles to include the equivalent of
|
||
'setenv TERMINFO JRWINFO' to tell the system to check my local custom
|
||
Terminfo library first.
|
||
|
||
Hope I haven't taken away all the fun ;-)
|
||
|
||
Good luck... / Ken
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88359 3-JUL 20:59 General Information
|
||
RE: OS-9 Live! (Re: Msg 88350)
|
||
From: JOHNREED To: KSCALES
|
||
|
||
Thanks for the info Ken. Looks just like the OSK procedure I
|
||
went through to get a terminfo entry for an old Fortune terminal
|
||
I picked up. So far, Coherent looks just like OS9, but it comes
|
||
with a huge file system and things are scattered all over the
|
||
place. I know there is a terminfo setup in there -- all I have to
|
||
do is find all the parts. (GRIN). This IS fun. It even has
|
||
a crippled version of MicroEmacs. It also came with X-Windows, but
|
||
all I can do is play a little with that -- the 4 megs in the 386 box
|
||
are bare minimum to run X-Windows (sort of like Multivue in 128k).
|
||
Super manual - the book is the size of a big-city phone book and
|
||
fairly well organized. Good online help too.
|
||
|
||
-*-
|
||
|
||
88413 5-JUL 20:52 General Information
|
||
RE: OS-9 Live! (Re: Msg 88350)
|
||
From: HAWKSOFT To: KSCALES
|
||
|
||
Ken:
|
||
> This will probably create up to 36 directories under JRWINFO/term.
|
||
> Some of these directories may be empty, but there should be files under
|
||
> k (k2), m (mm1), v (vsc), etc. Any empty directories could be deleted.
|
||
> BTW, this is the same basic sequence that I used for creating the
|
||
> Terminfo libraries for the OSK ports of 'sc' and 'rogue'.
|
||
|
||
That's where those directories came from!!!!! I've been scratching my head
|
||
ever since I ran across them a couple of weeks ago. It was 'sc' that
|
||
dood it!
|
||
|
||
BTW anything new on the G-Windows front?? I've been playing around a lot!
|
||
If you are interested, I can send a digital sound file player that works
|
||
under G-Windows! (THEY said it couldn't be done). I also wrote a file-
|
||
recognizer that recognizes 8SVX (.iff) sound files and shows a custom icon
|
||
for them. Simply double-click on the icon to play!
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88434 6-JUL 01:21 General Information
|
||
RE: OS-9 Live! (Re: Msg 88413)
|
||
From: KSCALES To: HAWKSOFT
|
||
|
||
> That's where those directories came from!!!!! I've been scratching my
|
||
> head ever since I ran across them a couple of weeks ago. It was 'sc' that
|
||
> dood it!
|
||
|
||
<g> Yes, the current 'sc_616_2' needs that Terminfo library.
|
||
|
||
> BTW anything new on the G-Windows front?? I've been playing around a lot!
|
||
> If you are interested, I can send a digital sound file player that works
|
||
> under G-Windows! (THEY said it couldn't be done). I also wrote a file-
|
||
> recognizer that recognizes 8SVX (.iff) sound files and shows a custom
|
||
> icon for them. Simply double-click on the icon to play!
|
||
|
||
Just installed a second hard drive, so I finally have some room to play
|
||
around in here. Hopefully, now I will be able to spend more time playing
|
||
with G-Windows.
|
||
|
||
Would really like to try out your sound player and file-recognizer stuff!
|
||
|
||
Cheers... / Ken
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88436 6-JUL 04:29 General Information
|
||
RE: OS-9 Live! (Re: Msg 88413)
|
||
From: EDELMAR To: HAWKSOFT
|
||
|
||
Chris,
|
||
|
||
> BTW anything new on the G-Windows front?? I've been playing around a lot!
|
||
> If you are interested, I can send a digital sound file player that works
|
||
> under G-Windows! (THEY said it couldn't be done). ...
|
||
|
||
Curious, who said it couldn't be done? Perhaps what they meant is that
|
||
G-WINDOWS doesn't include a sound manager ala RAVE, CD-RTOS or DAVID.
|
||
|
||
> ... I also wrote a file-recognizer that recognizes 8SVX (.iff) sound
|
||
> files and shows a custom icon for them. Simply double-click on the icon
|
||
> to play!
|
||
|
||
That's one of the nice things about G-WINDOWS. I'm hoping that programmers
|
||
writing for G-WINDOWS will also include file recognizers and icons with their
|
||
software when it will benefit the user.
|
||
|
||
Ed Gresick
|
||
DELMAR CO
|
||
|
||
-*-
|
||
|
||
88446 6-JUL 21:54 General Information
|
||
RE: OS-9 Live! (Re: Msg 88436)
|
||
From: HAWKSOFT To: EDELMAR
|
||
|
||
Hi ED !!
|
||
|
||
>> under G-Windows! (THEY said it couldn't be done). ...
|
||
>
|
||
> Curious, who said it couldn't be done? Perhaps what they meant is that
|
||
> G-WINDOWS doesn't include a sound manager ala RAVE, CD-RTOS or DAVID.
|
||
|
||
I'm sure thats what they meant. Most sound players will work IF you
|
||
redirect the appropriate path to a K-Windows window.
|
||
|
||
> > ... I also wrote a file-recognizer that recognizes 8SVX (.iff) sound
|
||
> > files and shows a custom icon for them. Simply double-click on the
|
||
> icon > to play!
|
||
>
|
||
> That's one of the nice things about G-WINDOWS. I'm hoping that
|
||
> programmers writing for G-WINDOWS will also include file recognizers and
|
||
> icons with their software when it will benefit the user.
|
||
|
||
Sounds like a GOOD idea! It's a shame that you weren't able to get enough
|
||
orders to do the port. I'm eagerly awaiting ed #52 from (FHL).
|
||
|
||
This is some SERIOUS software!!!!!!!!!!
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88457 7-JUL 02:39 General Information
|
||
RE: OS-9 Live! (Re: Msg 88446)
|
||
From: JOELHEGBERG To: HAWKSOFT
|
||
|
||
Chris,
|
||
|
||
> Sounds like a GOOD idea! It's a shame that you weren't able to get
|
||
> enough orders to do the port. I'm eagerly awaiting ed #52 from (FHL).
|
||
|
||
Any news about when this will be available?
|
||
|
||
> This is some SERIOUS software!!!!!!!!!!
|
||
|
||
I take it you like G-Windows? <g> Did you find the money to get the
|
||
dev. pack yet? Oh, and did you find another video mode that gave a
|
||
little better colorset than the darker gray being used?
|
||
|
||
|
||
|
||
=============================================================================
|
||
Joel Mathew Hegberg M.O.T.D. Editor
|
||
(JoelHegberg@delphi.com) 68'micros Columnist
|
||
Sub-Etha Software Programmer
|
||
=============================================================================
|
||
|
||
|
||
-*-
|
||
|
||
88468 7-JUL 21:51 General Information
|
||
RE: OS-9 Live! (Re: Msg 88457)
|
||
From: HAWKSOFT To: JOELHEGBERG
|
||
|
||
Hi Joel!
|
||
|
||
|
||
> > Sounds like a GOOD idea! It's a shame that you weren't able to get
|
||
> > enough orders to do the port. I'm eagerly awaiting ed #52 from (FHL).
|
||
>
|
||
> Any news about when this will be available?
|
||
|
||
Not so far
|
||
|
||
> > This is some SERIOUS software!!!!!!!!!!
|
||
>
|
||
> I take it you like G-Windows? <g> Did you find the money to get the
|
||
> dev. pack yet? Oh, and did you find another video mode that gave a
|
||
> little better colorset than the darker gray being used?
|
||
|
||
YES!!!!!!!! Maybe, I probably sould do some checking with Ed and/or
|
||
Frank to feel out the potential market. If there would be enough interest
|
||
and the SCSI drivers on other machines will support it, I'd like to port
|
||
my Audio CD player program to G-Windows! And... Frank has tried a couple
|
||
of times to send me a new video driver that supports a Color Lookup Table
|
||
so the colors can be changed, but, Delphi (or somebody) keeps shorting me on
|
||
the archive's file size. The MM/1 has only two modes that are high enough
|
||
for gwindows (640x420 and 768x480 ??). But, my Maggie monitor looks a lot
|
||
better (brighter) than the CM8 I use at the shows.
|
||
|
||
When are YOU going to get G-Windows?????? <g>
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88472 8-JUL 02:01 General Information
|
||
RE: OS-9 Live! (Re: Msg 88468)
|
||
From: JOELHEGBERG To: HAWKSOFT
|
||
|
||
Chris,
|
||
|
||
> > I take it you like G-Windows? <g> Did you find the money to get the
|
||
> > dev. pack yet? Oh, and did you find another video mode that gave a
|
||
> > little better colorset than the darker gray being used?
|
||
>
|
||
> YES!!!!!!!!
|
||
|
||
Very cool... that was my big complaint.
|
||
|
||
> Frank to feel out the potential market. If there would be enough interest
|
||
> and the SCSI drivers on other machines will support it, I'd like to port
|
||
> my Audio CD player program to G-Windows!
|
||
|
||
I think that would be great, Chris! I'd say, go for it! ;)
|
||
|
||
> When are YOU going to get G-Windows?????? <g>
|
||
|
||
Sigh... when I get some money. ;) (School likes to take it all for
|
||
itself, unfortunately.) I don't even have a compiler yet for my
|
||
Macintosh... that's sad. I can't believe I have a computer in my house
|
||
that I can't write programs for! :(
|
||
|
||
Oh, you didn't mention... did you get the developer's package for
|
||
G-Windows yet?
|
||
|
||
|
||
=============================================================================
|
||
Joel Mathew Hegberg M.O.T.D. Editor
|
||
(JoelHegberg@delphi.com) 68'micros Columnist
|
||
Sub-Etha Software Programmer
|
||
=============================================================================
|
||
|
||
|
||
-*-
|
||
|
||
88485 9-JUL 03:04 General Information
|
||
RE: OS-9 Live! (Re: Msg 88472)
|
||
From: KSCALES To: JOELHEGBERG (NR)
|
||
|
||
> > When are YOU going to get G-Windows?????? <g>
|
||
>
|
||
> Sigh... when I get some money. ;) (School likes to take it all for
|
||
> itself, unfortunately.) I don't even have a compiler yet for my
|
||
> Macintosh... that's sad. I can't believe I have a computer in my house
|
||
> that I can't write programs for! :(
|
||
|
||
Wellll.... I don't know if I would put it that way. I consider the Mac
|
||
to be more of an appliance than a computer.
|
||
|
||
I just returned from a two-day business trip, and found three boxes had
|
||
been dumped next to my desk at work. Guess I will spend next week setting
|
||
up yet another Mac... They delivered a Quadra 610 just before Christmas,
|
||
but once I got it half-configured, they gave it to someone else, and
|
||
replaced it with a noisy old Mac II that wasn't good enough for one of
|
||
the secretaries anymore. I _refused_ to spend the $1800 to upgrade that
|
||
dinosaur to handle Ethernet and MacX (plus $1700 for a two-page monochrome
|
||
monitor), and they eventually put me on the waiting list for this new
|
||
machine. It's a 7100...
|
||
|
||
Cheers... / Ken
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88491 9-JUL 12:38 General Information
|
||
RE: OS-9 Live! (Re: Msg 88446)
|
||
From: DBREEDING To: HAWKSOFT (NR)
|
||
|
||
> > That's one of the nice things about G-WINDOWS.
|
||
>
|
||
> Sounds like a GOOD idea! It's a shame that you weren't able to get
|
||
> enough orders to do the port. I'm eagerly awaiting ed #52 from (FHL).
|
||
>
|
||
> This is some SERIOUS software!!!!!!!!!!
|
||
|
||
You better believe it. I've had my system (a System 5) for about a
|
||
month, haven't even scratched the surface yet. Just recently played
|
||
around with the auto-ex capabilities. Truly awesome. For example,
|
||
if you click on a makefile... she'll do the make, automatically.
|
||
|
||
I think G-Windows is the way to go to give us a truly universal
|
||
platform to work from. Hopefully, enough MM/1 owners will get into
|
||
it to become a standard for you guys.
|
||
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88494 9-JUL 14:10 General Information
|
||
RE: OS-9 Live! (Re: Msg 88491)
|
||
From: NIMITZ To: DBREEDING (NR)
|
||
|
||
Actually, David, the ability to click on an Icon and get make to autoexecute
|
||
is already there on the MM/1 Desktop.
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88316 2-JUL 13:25 OSK Applications
|
||
KWindow Mouse freeze
|
||
From: NIMITZ To: BRUCEGERST (NR)
|
||
|
||
Bruce, was it you who mentioned to me at the fest that you had found a fix for
|
||
a KWindows mouse problem?? (The one where the mouse freezes on the screen?) If
|
||
so, could you post it here please? Thanks!
|
||
|
||
|
||
-*-
|
||
|
||
88326 2-JUL 21:38 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88316)
|
||
From: KSCALES To: NIMITZ
|
||
|
||
> Bruce, was it you who mentioned to me at the fest that you had found a fix
|
||
> for a KWindows mouse problem?? (The one where the mouse freezes on the
|
||
> screen?) If so, could you post it here please? Thanks!
|
||
|
||
Hi, David -
|
||
|
||
I might have mentioned to you that I have a fixed mouse driver -- but it
|
||
is the one for FHL's G-Windows package.
|
||
|
||
The KWindows mouse problem is caused by lack of proper error
|
||
handling/recovery in the driver. The mouse transmits data at 1200 baud,
|
||
which means roughly one character in 1/120 (0.0083) second. If the system
|
||
is unable to process the incoming characters fast enough, the MC68901
|
||
creates an over-run error, from which the driver cannot recover. (This
|
||
is similar to the /t0 lock-up problems folks used to have. Again, the
|
||
early /t0 drivers did not have proper error recovery, so would lock up
|
||
after over-run, parity, or framing errors. Typically a change in baud
|
||
rate, such as Delphi/Tymnet's autobauding sequence, could trigger the
|
||
problem.)
|
||
|
||
Long message continues...
|
||
|
||
Two primary causes of mouse-buffer over-run are:
|
||
- a maxcount value of 65535 used on a fast hard drive. For example,
|
||
if the drive has a transfer rate of 1.8M/sec, then the system will
|
||
go into DMA mode for about 0.036 seconds at a time when doing large
|
||
block reads -- if the mouse is moved during this time, it locks. (I
|
||
was disappointed to see that the descriptors in the upgrade from
|
||
Blackhawk still use the 65535 value.) I have mine set at 2048, and
|
||
while _some_ disk reads are a bit slower, I haven't had a mouse lockup
|
||
due to this problem in well over a year.
|
||
|
||
- large graphic updates in the high resolution modes. I am not aware of any
|
||
current fix for this problem, other than the workaround attached below.
|
||
|
||
Following is an excerpt from Appendix D of the OSTerm 68K Reference Manual,
|
||
which describes this problem and provides a workaround.
|
||
------------------------------------------------------------------------
|
||
MOUSE LOCKUPS, LOST CHARACTERS AND MAXCOUNT
|
||
|
||
Several MM/1 owners have experienced problems with the mouse cursor
|
||
disappearing and lost characters through the serial ports while doing disk IO.
|
||
This is generally experienced by those using very fast hard drives, such as
|
||
the Quantum 105. This shouldn't be a problem for those using slower drives.
|
||
|
||
The serial mouse, for example, is constantly sending data to the mouse port at
|
||
1200 baud. If the mouse driver doesn't get time allocated to read the port,
|
||
then an overflow condition occurs. When the mouse driver is given time by the
|
||
system to read the port, it doesn't detect the overflow, the driver locks and
|
||
the mouse cursor disappears.
|
||
|
||
A similar condition occurs with lost characters received through the serial
|
||
ports. The system is too busy, and misses a character when it is received.
|
||
|
||
There are two solutions to this problem. The first one will cure both the
|
||
problem with the disappearing mouse cursor and lost characters through the
|
||
serial port. The second solution will restore control of the mouse if it ever
|
||
disappears.
|
||
|
||
Solution #1.
|
||
This solution has been described on various information services. One of the
|
||
great virtues of the MM/1 is its great hard drive speed. However, this comes
|
||
at a price. While the system is doing DMA, it sometimes doesn't have the time
|
||
to take care of other necessary tasks. That is what causes lost characters
|
||
through the serial ports.
|
||
|
||
To reduce the duration of each DMA burst, and thus increase the number of
|
||
times your MM/1 has to check for data coming into the serial ports, reduce the
|
||
maxcount of your hard drive descriptors.
|
||
|
||
Moded may be used to modify the descriptor within the OS9Boot file.
|
||
|
||
This can also be accomplished using dmode as follows:
|
||
|
||
dmode /dd maxcount=2048
|
||
|
||
Save the /dd module, update its CRC and create a new boot disk, and your mouse
|
||
lockups and lost characters through the serial port should be greatly reduced.
|
||
This size of maxcount (2048 bytes) has been found to virtually eliminate lost
|
||
characters and serial mouse lockups on the systems that it has been tested on.
|
||
A larger maxcount can be used, but will increase the chance of lockups and
|
||
lost characters.
|
||
|
||
|
||
|
||
D-1
|
||
OSTerm 68K Reference Manual Appendix D MM/1 Technical Notes
|
||
|
||
|
||
The disadvantage of this method is that it slows down disk IO. The choice is
|
||
yours. One 'trick' that can be used, however, is to have a second disk
|
||
descriptor available if you need to do speedy disk IO. For example, if /dd is
|
||
your hard drive, you can set maxcount to 2048 on your /dd descriptor, while
|
||
leaving it at 65535 on /h0.
|
||
|
||
Solution #2
|
||
Regaining control of a 'lost' mouse cursor. This solution was described by
|
||
Mike Haaland on Internet.
|
||
|
||
Create a script file called 'fixmouse', set its execution attributes, and
|
||
stick the file in your commands directory. This fix will work if your mouse
|
||
is running on port /t2.
|
||
|
||
load sc68901 Serial driver
|
||
load t2.dd Port descriptor
|
||
xmode /t2 baud=1200 Mouse baud rate
|
||
iniz t2 Resets the port
|
||
|
||
If your mouse cursor ever disappears, simply move to another window, and type
|
||
'fixmouse' at a shell prompt. The script will load in the serial port driver
|
||
and descriptor, and reset the port.
|
||
|
||
The mouse cursor may also disappear during updates of the high resolution
|
||
interlaced screens (90x60 for example). This is a separate problem, though
|
||
Solution #2 will restore the lost cursor.
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88347 3-JUL 12:48 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88326)
|
||
From: NIMITZ To: KSCALES
|
||
|
||
Thanks, Ken. I needed that. Now if I can just figure out this floppy
|
||
installation problem....... ;)
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88355 3-JUL 15:13 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88347)
|
||
From: KSCALES To: NIMITZ
|
||
|
||
> Thanks, Ken. I needed that. Now if I can just figure out this floppy
|
||
> installation problem....... ;)
|
||
|
||
Glad it helps.
|
||
|
||
I have an 80-track 720K 5.25 drive here (not a 1.2M; sorry). I thought
|
||
I would try looking into your floppy problem to see if I can help shed some
|
||
light, but...
|
||
|
||
I discovered that when I installed my new hard drive, that I had forgotten
|
||
to re-install the power line to my 5.25 drive. Took the system apart, and
|
||
found that I had used its power line for the HD, and there weren't any
|
||
left ;-(
|
||
|
||
So, I disconnected one of my 3.5s (actually, it was an accident, but
|
||
while it was disconnected, I decided to try hooking it to the 5.25 to
|
||
continue the experiment.)
|
||
|
||
Well, only partial success here. I am able to read some disks (best
|
||
luck with single-sided), but frequently hit error 247s (Seek Error),
|
||
especially with double-sided diskettes when trying to access the second
|
||
side (i.e., when 'dump -c /c2@' tries to access Addr 12xx). Could be
|
||
an alignment problem between my 720K drive and one or both of my CC3 360K
|
||
drives. (Remember, the 720K drive has to be double-stepped, and reads a
|
||
"finer track" than the 360Ks.)
|
||
|
||
Here's a dmode of my /c2 descriptor, for what it's worth.
|
||
name=c2
|
||
drv=2 stp=3 typ=$24 dns=$03 cyl=80 sid=2 vfy=0 (on) sct=18 t0s=18
|
||
sas=8 ilv=3 tfm=0 toffs=0 soffs=1 ssize=256 cntl=$0000 trys=0 lun=0
|
||
wpc=0 rwr=0 park=0 lsnoffs=0 totcyls=80 ctrlrid=0 rates=$10
|
||
scsiopt=$0000 maxcount=65535
|
||
|
||
Not sure whether any of this would be of any use for you setting up the
|
||
1.2M drive.
|
||
|
||
Regards... / Ken
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88356 3-JUL 15:26 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88355)
|
||
From: NIMITZ To: KSCALES
|
||
|
||
Thanks, Ken. I think that will help at least ot read 720 K diskettes
|
||
as this drive is a dual speed drive that can be set in 720k mode.
|
||
|
||
I may have to see if my client will accept shipment without that drive,
|
||
which was an afterthought on his part. Hate to do it, but I can't even get
|
||
a 360K floppy to work on the machine (either mine or his!).
|
||
|
||
Davi
|
||
|
||
(I mean using an actuall 360 K drive from Chinon)
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88415 5-JUL 20:52 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88326)
|
||
From: HAWKSOFT To: KSCALES
|
||
|
||
Hey Ken!
|
||
> I might have mentioned to you that I have a fixed mouse driver -- but it
|
||
> is the one for FHL's G-Windows package.
|
||
|
||
What G-Windows mouse problem??? Of course, NOW I'll have a problem <g>!
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88416 5-JUL 20:52 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88356)
|
||
From: HAWKSOFT To: NIMITZ
|
||
|
||
David:
|
||
|
||
Re: your floppy drive problem. Are you connecting the 5 1/4 as a third
|
||
(or fourth) drive on an MM/1?? I've heard of many problems with more than
|
||
2 drives. (And had a few myself!)
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88433 6-JUL 01:21 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88415)
|
||
From: KSCALES To: HAWKSOFT
|
||
|
||
> Hey Ken!
|
||
> > I might have mentioned to you that I have a fixed mouse driver -- but
|
||
> it > is the one for FHL's G-Windows package.
|
||
>
|
||
> What G-Windows mouse problem??? Of course, NOW I'll have a problem <g>!
|
||
|
||
Hi, Chris -
|
||
|
||
Guess I didn't phrase that very well. Let's try again ;-)
|
||
|
||
"I might have mentioned to you that I have a mouse driver that does not
|
||
exhibit this lockup problem. It is the one that came with G-Windows."
|
||
|
||
Nope, never had any G-Windows mouse problem -- Ray Tremblay's mouse driver
|
||
for G-Windows handles the error conditions properly.
|
||
|
||
Hopefully, this will prevent you from encountering any problems! <g>
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88437 6-JUL 07:21 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88416)
|
||
From: NIMITZ To: HAWKSOFT
|
||
|
||
No, Chris, this is a second drive. I did manage to get a Teac FD55BR to work.
|
||
It's the 360K version. I could manage to get the FD55FGR to read the root, but
|
||
nothing more.
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88444 6-JUL 21:54 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88437)
|
||
From: HAWKSOFT To: NIMITZ
|
||
|
||
Hi David!
|
||
> No, Chris, this is a second drive. I did manage to get a Teac FD55BR to
|
||
> work. It's the 360K version. I could manage to get the FD55FGR to read
|
||
> the root, but
|
||
> nothing more.
|
||
|
||
Sounds crazy! Just thought I'd check on the drive #, 'cause I had had
|
||
a lot of problems getting a third floppy to work. Did finally work, but,
|
||
only if I set it to the fourth drive (and called it #3).
|
||
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88445 6-JUL 21:54 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88433)
|
||
From: HAWKSOFT To: KSCALES
|
||
|
||
> Guess I didn't phrase that very well. Let's try again ;-)
|
||
>
|
||
> "I might have mentioned to you that I have a mouse driver that does not
|
||
> exhibit this lockup problem. It is the one that came with G-Windows."
|
||
>
|
||
> Nope, never had any G-Windows mouse problem -- Ray Tremblay's mouse
|
||
> driver for G-Windows handles the error conditions properly.
|
||
>
|
||
> Hopefully, this will prevent you from encountering any problems! <g>
|
||
|
||
Whew! <g>
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88455 7-JUL 00:09 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88356)
|
||
From: DBREEDING To: NIMITZ
|
||
|
||
> Thanks, Ken. I think that will help at least ot read 720 K diskettes
|
||
> as this drive is a dual speed drive that can be set in 720k mode.
|
||
>
|
||
> I may have to see if my client will accept shipment without that drive,
|
||
> which was an afterthought on his part. Hate to do it, but I can't even
|
||
> get a 360K floppy to work on the machine (either mine or his!).
|
||
|
||
Dave, I've been seeing this thread, and haven't been paying all that much
|
||
attention, but I have one suggestion. If I paid enough attention, you're
|
||
trying to get to get the MM/1 to read a 360k floppy on a 1.2 meg? If so,
|
||
it would be a little more expense for your customer, but would it be
|
||
possible to convince him to install a 720K 3.5" on the coco? This would
|
||
make it a lot simpler, as the 1.44 automatically senses a 720K disk.
|
||
|
||
If he could be talked into doing this, I think it would solve a lot of
|
||
problems.
|
||
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88487 9-JUL 09:23 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88455)
|
||
From: NIMITZ To: DBREEDING
|
||
|
||
David, I agree it would solve a lot of problems, but one of the problems it
|
||
would not solve is increasing the amount of CoCo compatibility promised by the
|
||
IMS design team. I don'
|
||
t plan on reaching the level promised, but I do plan on making some progress.
|
||
I don't buy the "MM/1 can't do this" approach some folks have previously
|
||
suggested to me. If the CoCo can do it, the MM/1 can do it better........
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88493 9-JUL 13:44 OSK Applications
|
||
RE: KWindow Mouse freeze (Re: Msg 88487)
|
||
From: DBREEDING To: NIMITZ
|
||
|
||
> David, I agree it would solve a lot of problems, but one of the problems
|
||
> it would not solve is increasing the amount of CoCo compatibility promised
|
||
> by the IMS design team. I don't
|
||
> plan on reaching the level promised, but I do plan on making some
|
||
|
||
Very good point. At one time, I envisioned being able to take a coco source
|
||
file and being able to compile it without any modifications. However, I
|
||
found this to be quite impractical. I would love to see as much backward
|
||
compatibility as possible, but apparently you see, as I do, that stressing
|
||
it too strongly will hamper the machine's development.
|
||
|
||
> progress. I don't buy the "MM/1 can't do this" approach some folks have
|
||
> previously suggested to me. If the CoCo can do it, the MM/1 can do it
|
||
> better........
|
||
|
||
Right! The very reason to upgrade. The coco is fantastic. It can do
|
||
about anything you desire, but I must admit that now, some things, like
|
||
unzipping a file, for example, do seem slow after doing it on the OSK
|
||
machine.
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88318 2-JUL 15:24 Games & Graphics
|
||
shanghai
|
||
From: DENNYWRIGHT To: EARTHER (NR)
|
||
|
||
Ii am having trouble getting shanghai for os9 to run. I see the title screen
|
||
then it clears and I get an error #201 and the os9 prompt back. Any ideas what
|
||
could be the problem? I have tried it under os9 and MV but niether way seems to
|
||
work. I get the same
|
||
error #201.
|
||
|
||
-*-
|
||
|
||
88319 2-JUL 16:09 OSK Applications
|
||
C question
|
||
From: NIMITZ To: ALL
|
||
|
||
I am trying to port a program from UNIX. It uses a menu fashion user interface.
|
||
|
||
The problem is, it mungs the input. I.E. it asks for input, but when you type
|
||
the requested input it does not accept it properly.
|
||
hmmm.. Still not clear.....
|
||
|
||
It asks for an option. it does not accept the option until <enter> is pressed,
|
||
then it immediately presents another input prompt, and the first key presented
|
||
to that prompt acts like a carriage return - so it never accepts the file name.
|
||
now if you type all the answers to the promp in response to the first input
|
||
prompt, you do get P
|
||
ARTIAL response to the subsequent inpput prompts. This program uses getch to
|
||
get the initial menu response, then gets to get the following strings. I
|
||
suspect a buffering problem, but can't quite remember what!
|
||
|
||
Thanks!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88449 7-JUL 00:00 OSK Applications
|
||
RE: C question (Re: Msg 88319)
|
||
From: CHYDE To: NIMITZ
|
||
|
||
I would suspect that it's using either readln() or one of the std. lib
|
||
functions (gets() or scanf()). There are differences in the way Unix
|
||
O. For the option, since you want it to be a "hot key"
|
||
try using,
|
||
|
||
read(0, $ans, 1);
|
||
|
||
where ans is a char (oops should be &ans).
|
||
|
||
To get the filename use either,
|
||
|
||
readln(0, fname, 81);
|
||
|
||
or
|
||
|
||
gets(fname);
|
||
|
||
or
|
||
|
||
scnaf("%s", fname);
|
||
|
||
If you are going to mix system and library calls (read's and gets for example)
|
||
you should flush the I/O buffers before reading and after writing. Normally
|
||
it's better if you stick with one way or the other.
|
||
|
||
Hope this helps.
|
||
|
||
Chris
|
||
|
||
-*-
|
||
|
||
88488 9-JUL 09:27 OSK Applications
|
||
RE: C question (Re: Msg 88449)
|
||
From: NIMITZ To: CHYDE (NR)
|
||
|
||
Thanks, Chris, I'll try to adjust that and get a fixed version uploaded.
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88324 2-JUL 19:12 Telecom (6809)
|
||
VT100
|
||
From: SES To: ALL
|
||
|
||
I am trying to get VT100 emulation. I keep getting Header and CRC errors when
|
||
dearcing "KBCom.ar". Are these errors in this program or is this my equipment?
|
||
I need VT100 for so many contacts on the Internet.
|
||
|
||
-*-
|
||
|
||
88450 7-JUL 00:04 Telecom (6809)
|
||
RE: VT100 (Re: Msg 88324)
|
||
From: CHYDE To: SES (NR)
|
||
|
||
It sounds like you've got a bad download. ry downloading the file again.
|
||
It could also be the version of ar you're using the most current version is
|
||
1.3. If you're using an older version that could be the problem.
|
||
|
||
Chris
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88325 2-JUL 20:24 General Information
|
||
RZSZ
|
||
From: CLTUCKER To: WDTV5
|
||
|
||
Am trying to use Zdow with the Disto 4IN1 no halt cont. or a ram dr. I grabbed
|
||
RZSZ_3_29_COCO.lzh and UnLzh=7.ar. Can you tell me how to u e this un-arc
|
||
pgm. ar-x "pgm" dosen't work.(g)
|
||
CL
|
||
|
||
-*-
|
||
|
||
88332 2-JUL 22:48 General Information
|
||
RE: RZSZ (Re: Msg 88325)
|
||
From: WDTV5 To: CLTUCKER
|
||
|
||
I haven't THAT much experience with unlzh. I only keep two versions of
|
||
that basic family of crunchers on my hard drive here, Matthew Thompsons
|
||
somewhat flawed "lzh", and now thats its availaable, "lha2_11c", which
|
||
apparently has grown enough smarts to handle the files made by lzh.
|
||
|
||
I noticed the revision number was 3_29, is that something I missed in the
|
||
databse? I helped a wee bit on 3_24, and thot it was the newest. That, if its a
|
||
miss-print, was crunched by lha2.11b, aka lha. The default extension of all
|
||
of these crunchers seems to be ".lzh".
|
||
|
||
On a side note, how many of you have noted that the PGP code which was
|
||
claioimed (claimed) to take 40 quadrillion years to break when it was
|
||
first defined back in 1977, accompanied by a $100 reward for the first
|
||
person to send then the cleartext of the message ppublished with the
|
||
article, has indeed been broken and the prize claimed (and paid) by
|
||
a group of 600 internetters who broke the problem down into manageable
|
||
pieces between them.. That was a 129 digit code, but not to worry, they
|
||
also have a 150 digit and a 229 digit version! Clipper chip my a$$!
|
||
|
||
Cheers all, just thought you'd like to know. See this mnths Scientific
|
||
American for clarification.
|
||
|
||
Gene
|
||
|
||
-*-
|
||
|
||
88338 3-JUL 03:07 General Information
|
||
RE: RZSZ (Re: Msg 88332)
|
||
From: MITHELEN To: WDTV5
|
||
|
||
Heh... That must have been a typo on the RZSZ version, since the most current
|
||
version is 3.24 R3 (3rd revision) I don't think I have put the latest revision
|
||
on Delphi, but it was just minor bug fixes. One of these days, I'll check to
|
||
see if there has been a new source distribution again, and do another complete
|
||
update.
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88360 3-JUL 22:00 General Information
|
||
RE: RZSZ (Re: Msg 88338)
|
||
From: WDTV5 To: MITHELEN
|
||
|
||
Sounds like a winner to me. Have a happy 4th Paul.
|
||
Cheers, Gene
|
||
|
||
-*-
|
||
|
||
88372 4-JUL 06:31 General Information
|
||
RE: RZSZ (Re: Msg 88338)
|
||
From: BOISY To: MITHELEN
|
||
|
||
> Heh... That must have been a typo on the RZSZ version, since the most
|
||
> current version is 3.24 R3 (3rd revision) I don't think I have put the
|
||
> latest revision
|
||
> on Delphi, but it was just minor bug fixes. One of these days, I'll check
|
||
> to see if there has been a new source distribution again, and do another
|
||
> complete
|
||
> update.
|
||
> --
|
||
> Paul
|
||
>
|
||
|
||
Hi Paul,
|
||
|
||
There is now ZModem 3.25. I've seen it at some FTP sites.
|
||
--
|
||
Boisy G. Pitre__ __ __ Delphi: BOISY
|
||
|_ _| \ \/ / CompuServe: 74464,3005
|
||
I use... _| |_ > < Internet: boisy@os9er.waukee.ia.us
|
||
|_____|NFO/_/\_\PRESS 1.2.0 OS-9 -- King of Operating Systems
|
||
|
||
-*-
|
||
|
||
88380 4-JUL 11:50 General Information
|
||
RE: RZSZ (Re: Msg 88372)
|
||
From: MITHELEN To: BOISY
|
||
|
||
Thanks Boisy, I'll keep an eye out for it.
|
||
|
||
-*-
|
||
|
||
88402 4-JUL 23:39 General Information
|
||
RE: RZSZ (Re: Msg 88325)
|
||
From: DBREEDING To: CLTUCKER
|
||
|
||
> Am trying to use Zdow with the Disto 4IN1 no halt cont. or a ram dr. I
|
||
> grabbed RZSZ_3_29_COCO.lzh and UnLzh=7.ar. Can you tell me how to u e
|
||
> this un-arc pgm. ar-x "pgm" dosen't work.(g)
|
||
> CL
|
||
|
||
Are you using the Disto RS-232? If so, it may be hard to get rz/sz to work
|
||
well. They depend heavily in RTS/CTS flow control, and these are hard-wired
|
||
high, where they cannot be used for this.
|
||
|
||
To use "ar" just ar -x unlzh7 the use of ".ar" is optional
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88407 5-JUL 00:46 General Information
|
||
RE: RZSZ (Re: Msg 88402)
|
||
From: MITHELEN To: DBREEDING
|
||
|
||
As long as the download is at 2400 baud, fixed rate, there would be no
|
||
problems with not haveing flow control on the port.
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88327 2-JUL 22:27 General Information
|
||
RE: OSK Software (Re: Msg 88233)
|
||
From: DBREEDING To: 01GEN40
|
||
|
||
> Just my 2 cents worth... It is quite funny you should mention memory
|
||
> limitations on PCs. I just learned something about that this past week.
|
||
> From the way I understand it, there is no 640K limit on a PC. That limit
|
||
> is with MESSY-DOS. OS-2, on a PC recognizes ALL available memory on it
|
||
|
||
I think you're right, but I'm not sure.
|
||
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88344 3-JUL 12:35 General Information
|
||
RE: OSK Software (Re: Msg 88327)
|
||
From: COLORSYSTEMS To: DBREEDING
|
||
|
||
>> From the way I understand it, there is no 640K limit on a PC.
|
||
>> That limit is with MESSY-DOS. OS-2, on a PC recognizes ALL available
|
||
>> memory on it
|
||
|
||
> I think you're right, but I'm not sure.
|
||
|
||
Yes, he is right. However, OS-2 (or UNIX or OS9K or some other OS) will not
|
||
run on a machine less than a 80386. The 640K barrier was originally due to
|
||
a design "characteristic" of the pre-80386 Intel processors.
|
||
|
||
|
||
------------------------------------
|
||
Zack C Sessions
|
||
|
||
They say, "Money talks". But all mine ever says is, "Goodbye".
|
||
|
||
|
||
-*-
|
||
|
||
88357 3-JUL 15:50 General Information
|
||
RE: OSK Software (Re: Msg 88250)
|
||
From: 01GEN40 To: COCOKIWI
|
||
|
||
All I know, from what I read a few weeks ago is: With a486 machine having
|
||
16Meg memory, running MS-DOS you have 640 BASE memo. Runni OS etc.,
|
||
you have 16Meg to play wth. No 640 BASE limit.
|
||
|
||
LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!
|
||
|
||
-= 01GEN40 =-
|
||
|
||
-*-
|
||
|
||
88358 3-JUL 15:53 General Information
|
||
RE: OSK Software (Re: Msg 88327)
|
||
From: 01GEN40 To: DBREEDING
|
||
|
||
Thanks David. I did not think I was just blowin' smoke.
|
||
|
||
LONG LIVE OS-9! <FOREVER> ** In whatever form it is in!
|
||
|
||
-= 01GEN40 =-
|
||
|
||
-*-
|
||
|
||
88362 4-JUL 00:15 General Information
|
||
RE: OSK Software (Re: Msg 88344)
|
||
From: JOELHEGBERG To: COLORSYSTEMS
|
||
|
||
> >> From the way I understand it, there is no 640K limit on a PC.
|
||
> >> That limit is with MESSY-DOS. OS-2, on a PC recognizes ALL available
|
||
> >> memory on it
|
||
>
|
||
> > I think you're right, but I'm not sure.
|
||
>
|
||
> Yes, he is right. However, OS-2 (or UNIX or OS9K or some other OS) will
|
||
> not run on a machine less than a 80386. The 640K barrier was originally
|
||
> due to a design "characteristic" of the pre-80386 Intel processors.
|
||
|
||
Actually, the 8086 Intel chip can address up to 1 MB of memory. The
|
||
640K barrier is simply because IBM declared addresses above 640K to be
|
||
I/O hardware addresses not to be used by RAM.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88390 4-JUL 19:25 General Information
|
||
RE: OSK Software (Re: Msg 88362)
|
||
From: COLORSYSTEMS To: JOELHEGBERG
|
||
|
||
> Actually, the 8086 Intel chip can address up to 1 MB of memory. The
|
||
> 640K barrier is simply because IBM declared addresses above 640K to be
|
||
> I/O hardware addresses not to be used by RAM.
|
||
|
||
I've been told that there was some deficiency in indexing registers in
|
||
pre-80386 class Intel MPU's. I don't know the whole story.
|
||
|
||
|
||
------------------------------------
|
||
Zack C Sessions
|
||
|
||
They say, "Money talks". But all mine ever says is, "Goodbye".
|
||
|
||
|
||
-*-
|
||
|
||
88403 5-JUL 00:28 General Information
|
||
RE: OSK Software (Re: Msg 88390)
|
||
From: JOELHEGBERG To: COLORSYSTEMS
|
||
|
||
> > Actually, the 8086 Intel chip can address up to 1 MB of memory. The
|
||
> > 640K barrier is simply because IBM declared addresses above 640K to be
|
||
> > I/O hardware addresses not to be used by RAM.
|
||
>
|
||
> I've been told that there was some deficiency in indexing registers in
|
||
> pre-80386 class Intel MPU's. I don't know the whole story.
|
||
|
||
That may be... I would never want to give Intel too much credit... <g>
|
||
We _had_ to learn 8086 assembly for a required Computer Science course
|
||
at my university, and it was not that much fun. Sure it can address
|
||
1MB, but only by combining 2 registers, which you _had_ to do. It was a
|
||
terrible way to write code. It's very easy to see why comparable
|
||
programs on Motorola chips are significantly smaller in size than their
|
||
Intel chip counterparts!
|
||
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88429 6-JUL 00:01 General Information
|
||
RE: OSK Software (Re: Msg 88057)
|
||
From: BERGMANN To: COCOKIWI
|
||
|
||
I just wish that the DOS/Windows machines that I use at home and at work
|
||
had some of the capabilities of OS-9 & OSK. The EXTREMELY STUPID 640K limit
|
||
forces so much disk access, constant, constant disk access....
|
||
On my old CoCo, I could copy floppy disks faster than I can with a 486, since
|
||
OS-9 let me add more memory to the process. Oh, it would sure be nice if
|
||
DOS and Windows could just load a whole program into memory all at once,
|
||
without ".OVL" files. Too much to ask for.
|
||
|
||
Still, from my CoCo, I graduated to Lotus, WordPerfect, Pagemaker, Quicken,
|
||
Microsoft Works, Word, and AutoSketch, not to mention a few others. I'm
|
||
totally spoiled by that and can never go back.
|
||
|
||
I'm about to move up to CD-ROMs, Kodak Photo CDs, CorelDraw, and Aldus
|
||
Photostyler, if I can convince my boss to put up some cash.
|
||
|
||
In other words, I am a user.
|
||
|
||
--- Dean
|
||
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88328 2-JUL 22:29 General Information
|
||
RE: Os9 and Osk (Re: Msg 88252)
|
||
From: DBREEDING To: DWHILL
|
||
|
||
> It may be the PC crowd is rude at times because they don't know as much
|
||
> as we do about the inner workings of our respective operating systems.
|
||
|
||
I kinda think you're right, at least on most instances. These people
|
||
probably like to come of as experts and have to resort to bluff and
|
||
bluster to cover up. I've thought this for some time.
|
||
|
||
> I'm using DOS/Windows quite a lot lately, but my Coco's never turned off.
|
||
> I'm still search for the same range of tools and utilities for the PC that
|
||
> I'm accustomed to having for OS-9.
|
||
|
||
Yes, we have a _BUNCH_ of good stuff for the coco.
|
||
|
||
> I'm just sorry my budget won't let me migrate to a 68K machine for the
|
||
> forseeable future. But as long as useful tools and applications like
|
||
> adq and lha keep popping up (I've got InfoXpress on order), my Coco will
|
||
|
||
I love ix. Coco ix doesn't have buffer capture, which would be useful for
|
||
file browsing etc. It does support B transfer protocol for CIS, where
|
||
you can go online manually (it'll autodial for you). For Delphi, you'll
|
||
have to use an external protocol for d/l's. One other tip. If you are
|
||
using SHELL+, you will probably have to modify it to cut down on the
|
||
memory it allocates to a program, or what I did was just rename the
|
||
stock shell (I renamed it "ohell"). Then I go into a window and do an
|
||
"ex ohell i=/1". Shell+ allocates 8k data to a program, and somehow
|
||
ix refuses to run. The latest version of "ar" (1.92?) also balks on the
|
||
13-bit compression with shell+.
|
||
|
||
> remain a useful tool. That multitasking is just too addicting!
|
||
|
||
And how! I don't think I could live without it. My OSK system doesn't
|
||
support windowing in the hardware text mode, and I miss being able
|
||
to clear to another window. Of course GWindows has it all, strictly
|
||
graphics, however, and a little slower on text display.
|
||
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88331 2-JUL 22:31 General Information
|
||
512K upgrades
|
||
From: MARTYGOODMAN To: ALL
|
||
|
||
I just received via Internet Mail the following letter. It may
|
||
be of interest to those seeking 512K upgrades for their Color Computer 3's:
|
||
|
||
Hi, Marty.
|
||
|
||
A while ago I mentioned to you that the Toronto Color Computer Club
|
||
was selling 512k SIMM upgrades on Fidonet.
|
||
|
||
These are now available from my business, Northern Xposure. Most of
|
||
the of the profit goes to the Toronto Club.
|
||
|
||
TTYL. Colin.
|
||
|
||
512K SIMM Memory Upgrade 512k $44.95 Zero k $39.95
|
||
|
||
o runs cooler and uses less power than standard upgrades
|
||
o uses two 8 or 9 chip 256k SIMMs, 80-150ns
|
||
|
||
They are available from:
|
||
|
||
Northern Xposure (613)736-0329
|
||
7 Greenboro Cres
|
||
Ottawa, ON
|
||
Canada
|
||
K1T 1W6
|
||
|
||
US Funds, check or money order please. Shipping and Handling included.
|
||
--
|
||
Colin McKay | Lasciate ogni speranza, voi ch'entrate.
|
||
Northern Xposure | Dante (1265-1321) 'Inferno', Canto iii
|
||
cmckay@northx.isis.org | [ Inscription over the gate to Hell ]
|
||
|
||
-*-
|
||
|
||
88333 3-JUL 00:22 Programmers Den
|
||
Named Pipes
|
||
From: JOELHEGBERG To: ALL
|
||
|
||
I have an OSK question that I don't know the answer to...
|
||
|
||
Everyone knows that when you type 'dir' at the shell prompt it sends
|
||
output to standard out and then ends. Same thing with the 'free'
|
||
command. How come when I redirect standard output to a named pipe,
|
||
the shell prompt never comes back until I send a BREAK? When I list the
|
||
named pipe after trying, only a small part of the anticipated output is
|
||
contained within the file.
|
||
|
||
Examples:
|
||
dir >/pipe/named (freezes)
|
||
free >/pipe/named (same thing happens)
|
||
|
||
Any ideas?
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88334 3-JUL 00:43 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88333)
|
||
From: BOISY To: JOELHEGBERG
|
||
|
||
Hi Joel,
|
||
|
||
You're experiencing blocking due to the nature of named pipes.
|
||
Unless there is a reader process to read the data from the named
|
||
pipe concurrently, the process writing to it will block when
|
||
writing one more character than the size of the named pipe
|
||
buffer. That size is specified in the /pipe device descriptor
|
||
(not sure of the offset, but the size is around 90 bytes).
|
||
|
||
While you're running the dir command to the named pipe, try
|
||
listing the named pipe in another window. You'll find that the
|
||
dir will exit properly, and list will show the entire file.
|
||
|
||
-*-
|
||
|
||
88335 3-JUL 02:07 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88333)
|
||
From: JEJONES To: JOELHEGBERG
|
||
|
||
> Everyone knows that when you type 'dir' at the shell prompt it sends
|
||
> output to standard out and then ends. Same thing with the 'free'
|
||
> command. How come when I redirect standard output to a named pipe,
|
||
> the shell prompt never comes back until I send a BREAK?
|
||
|
||
Because the pipe is implemented as a fixed-size buffer (size determined
|
||
at the time it's created), so that when the buffer fills, the process
|
||
writing to the pipe blocks, waiting for something to read the pipe so
|
||
it can keep writing.
|
||
|
||
> When I list the
|
||
> named pipe after trying, only a small part of the anticipated output is
|
||
> contained within the file.
|
||
|
||
Probably then you've killed the writing process, so that it didn't get
|
||
the chance to write all the stuff it was going to.
|
||
|
||
To see whether this is happening, try:
|
||
|
||
dir >/pipe/stuff &
|
||
list /pipe/stuff
|
||
|
||
and see whether you get all the output you expect.
|
||
|
||
Opinions herein are solely those of their respective authors.
|
||
|
||
Clipper Chip: Big Brother Inside
|
||
|
||
-*-
|
||
|
||
88336 3-JUL 02:18 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88333)
|
||
From: KSCALES To: JOELHEGBERG
|
||
|
||
Hi, Joel -
|
||
|
||
> Everyone knows that when you type 'dir' at the shell prompt it sends
|
||
> output to standard out and then ends. Same thing with the 'free'
|
||
> command. How come when I redirect standard output to a named pipe,
|
||
> the shell prompt never comes back until I send a BREAK? When I list the
|
||
> named pipe after trying, only a small part of the anticipated output is
|
||
> contained within the file.
|
||
>
|
||
> Examples:
|
||
> dir >/pipe/named (freezes)
|
||
> free >/pipe/named (same thing happens)
|
||
|
||
The default size of the /pipe FIFO is 90 bytes. Once it fills, the
|
||
process writing to the named pipe will block until another process starts
|
||
pulling data out the other end (by reading it).
|
||
|
||
dir >/pipe/named (blocks after 90 bytes)
|
||
Then go to another window, and:
|
||
list /pipe/named
|
||
|
||
The 'list' command should list the entire output from the 'dir' command,
|
||
and when you go back to the original window, it should no longer be
|
||
"frozen".
|
||
|
||
The size of the FIFO buffer can be changed when a program opens a path
|
||
to a named pipe by using the "initial_size" option of the 'create()'
|
||
function, along with the S_ISIZE flag in the 'mode' parameter. (See
|
||
modes.h)
|
||
|
||
I used named pipes for some of the 'sc' spreadsheet functions. Worked
|
||
great. Didn't need to fiddle with the size of the FIFO buffer in that
|
||
case, tho.
|
||
|
||
Hope this helps!
|
||
|
||
Cheers... / Ken
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88343 3-JUL 11:51 Programmers Den
|
||
<20>|JTJr$TZ<54>es (Re: Msg 88333)
|
||
From: RHELLER To: JOELHEGBERG
|
||
|
||
The problem is that the size of the FIFO buffer for a pipe is small, too small
|
||
to hold the entire output of dir or free. What you should do is this:
|
||
|
||
$ dir >/pipe/named &
|
||
$ list /pipe/named
|
||
|
||
Programs that write to pipes (named or not) hang when the pipe gets full. As
|
||
the pipe is read from (by some other process), space becomes available and the
|
||
writing process starts writing more data to the pipe.
|
||
|
||
Robert
|
||
|
||
-*-
|
||
|
||
88345 3-JUL 12:35 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88333)
|
||
From: COLORSYSTEMS To: JOELHEGBERG
|
||
|
||
> Examples:
|
||
> dir >/pipe/named (freezes)
|
||
> free >/pipe/named (same thing happens)
|
||
|
||
JOEL!!! RTFM!!!! :-)
|
||
|
||
When a named (or unnamed, for that matter) pipe is created by the shell as a
|
||
result of IO redirection, it is created to be only so big. I don't have
|
||
my manual handy, it something like 60 or 90 bytes or something like that.
|
||
When whatever command is writing to it gets that far, it goes into a wait
|
||
until the contents of the pipe are flushed so it can write more to it.
|
||
|
||
For example, you have a shell in W1 and W2. In the W1 shell you enter:
|
||
|
||
$ dir >/pipe/temp
|
||
|
||
After a very short time, this command will freeze. "CLEAR" over to the
|
||
shell in W2 and do a:
|
||
|
||
$ list /pipe/temp
|
||
|
||
As the contents are listed, the dir command W1 kicks back off again, and
|
||
eventually the whole thing completes. You can do this in a single window.
|
||
Change the dir command to:
|
||
|
||
$ dir >/pipe/temp&
|
||
|
||
Then follow it up with the list command.
|
||
|
||
One difference is when the command writing to the pipe is the copy command.
|
||
When the output pipe is created in this case, it is sized to be the same
|
||
as the input file. You can, of course, in your own program, create a
|
||
pipe of any size using the S_ISIZE modifier.
|
||
|
||
|
||
|
||
------------------------------------
|
||
Zack C Sessions
|
||
|
||
They say, "Money talks". But all mine ever says is, "Goodbye".
|
||
|
||
|
||
-*-
|
||
|
||
88363 4-JUL 00:15 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88334)
|
||
From: JOELHEGBERG To: BOISY
|
||
|
||
Boisy,
|
||
|
||
> You're experiencing blocking due to the nature of named pipes.
|
||
|
||
I remembered that shortly after posting the message. The reason why I
|
||
got confused was the "copy" command works perfectly fine to pipes no
|
||
matter what size the file is. I had an installation routine for
|
||
single-disk systems that would copy an entire 150k file to a named pipe
|
||
(using the OS-9 standard 'copy' utility) and then let the user swap
|
||
disks and my program would decode the pipe file. This did not happen
|
||
concurrently, so the pipe actually did fill up to 150k. I guess "copy"
|
||
must use the S_ISIZE option when creating a file.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88364 4-JUL 00:15 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88335)
|
||
From: JOELHEGBERG To: JEJONES
|
||
|
||
James,
|
||
|
||
> Because the pipe is implemented as a fixed-size buffer (size determined
|
||
> at the time it's created), so that when the buffer fills, the process
|
||
|
||
Yep... I had a mind-blank for a moment. I got confused when the "copy"
|
||
command works fine when copying a 150k file to a named pipe, while
|
||
redirecting output from "dir" only allows 90 bytes before it puts the
|
||
command to sleep. I think I get it now... "copy" must use the S_ISIZE
|
||
parameter.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88365 4-JUL 00:15 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88336)
|
||
From: JOELHEGBERG To: KSCALES
|
||
|
||
Ken,
|
||
|
||
> The size of the FIFO buffer can be changed when a program opens a path
|
||
> to a named pipe by using the "initial_size" option of the 'create()'
|
||
> function, along with the S_ISIZE flag in the 'mode' parameter. (See
|
||
> modes.h)
|
||
|
||
That's what must have confused me. I knew about the default size limit,
|
||
but completely forgot about it after the "copy" command would let me
|
||
copy a 150k file to a named pipe.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88366 4-JUL 00:15 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88343)
|
||
From: JOELHEGBERG To: RHELLER (NR)
|
||
|
||
> Programs that write to pipes (named or not) hang when the pipe gets full.
|
||
> As the pipe is read from (by some other process), space becomes available
|
||
> and the writing process starts writing more data to the pipe.
|
||
|
||
Thanks for your (and everyone elses) reply.
|
||
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88367 4-JUL 00:15 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88345)
|
||
From: JOELHEGBERG To: COLORSYSTEMS
|
||
|
||
Zack,
|
||
|
||
> JOEL!!! RTFM!!!! :-)
|
||
|
||
But it's so much easier just to let everyone else scream the answer at
|
||
me... <grin>
|
||
|
||
> One difference is when the command writing to the pipe is the copy
|
||
> command. When the output pipe is created in this case, it is sized to be
|
||
> the same as the input file. You can, of course, in your own program,
|
||
> create a pipe of any size using the S_ISIZE modifier.
|
||
|
||
That's what confused me. I rarely ever use named pipes, and after using
|
||
the "copy" command for a while with a 150k file, I just decided to
|
||
forget about the small buffer that is normally allocated and think
|
||
everything worked the way "copy" does... which would be nice.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88454 7-JUL 00:08 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88366)
|
||
From: DBREEDING To: JOELHEGBERG
|
||
|
||
> Thanks for your (and everyone elses) reply.
|
||
|
||
If you don't want answers around here, better not ask a question, right? <G>
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88490 9-JUL 11:08 Programmers Den
|
||
RE: Named Pipes (Re: Msg 88367)
|
||
From: RICKMAC To: JOELHEGBERG (NR)
|
||
|
||
Are you talking about this situation?...
|
||
dir [device] > [filename]
|
||
|
||
If so, I just successfully executed the above command sequence without it
|
||
"hanging up". Are you using ShellPlus? Using ShellPlus with the "noblock"
|
||
feature turned on should solve your problem.
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88342 3-JUL 11:38 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88130)
|
||
From: RHELLER To: COLORSYSTEMS
|
||
|
||
|
||
Look on pagethe page where os9exec() is described in the OSK C functions
|
||
reference
|
||
manual. It shows exactly the code to fork rename. as the example for using
|
||
os9exec and os9fork.
|
||
|
||
Robert
|
||
|
||
-*-
|
||
|
||
88348 3-JUL 12:52 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88342)
|
||
From: COLORSYSTEMS To: RHELLER (NR)
|
||
|
||
> Look on pagethe page where os9exec() is described in the OSK C functions
|
||
> reference
|
||
> manual. It shows exactly the code to fork rename. as the example for
|
||
> using os9exec and os9fork.
|
||
|
||
That's all well and good and shows how to pass the environment to a module
|
||
in a child process, in this case, rename. However, the system still needs
|
||
to find rename if it is not in memory. If the programmer expects for the
|
||
module of the child process to be available via a PATH in the environment,
|
||
then you'd still have to write your own procfunc front end to os9fork().
|
||
|
||
|
||
------------------------------------
|
||
Zack C Sessions
|
||
|
||
They say, "Money talks". But all mine ever says is, "Goodbye".
|
||
|
||
|
||
-*-
|
||
|
||
88354 3-JUL 15:13 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88106)
|
||
From: KSCALES To: JOELHEGBERG
|
||
|
||
---- Message re-uploaded to avoid "/" as first character in some lines ----
|
||
|
||
Hi, Joel -
|
||
|
||
> I'd like to rename a file under C, but I don't seem to see a function to
|
||
> handle that for me. Is there one, or must I take care of this myself?
|
||
>
|
||
> -- Joel Mathew Hegberg
|
||
|
||
Picking up on this thread again, I ran across a file here while doing some
|
||
hard drive maintenance that I thought you might find interesting.
|
||
|
||
Cheers... / Ken
|
||
|
||
PS - "doing some hard drive maintenance" = installing a new 340 megger.
|
||
FINALLY should be able to do something productive without first routing
|
||
through files looking for something to archive or delete!
|
||
|
||
---------File starts----------------------------------------------------
|
||
This is from Microware.
|
||
|
||
Following is a C-binding to call SS_Rename.
|
||
|
||
SS_Rename is used by OS-9/N.F.S. because the traditional method of
|
||
renaming a file on OS-9 is incompatible with the underlying NFS
|
||
protocol. (One cannot simply open a directory on an NFS device, rewrite
|
||
or add an entry, and move an FD address around.)
|
||
|
||
Not all OS-9 file managers support this SS_Rename setstat. To allow
|
||
renaming NFS files, the OS-9 utility "rename" was changed to issue the
|
||
SS_Rename setstat. If the return status indicates the call is not
|
||
supported by the file manager, rename manipulates the directory in the
|
||
historical manner. It is Microware's intent to support a "rename" C
|
||
library function in the future as part of POSIX compliance.
|
||
|
||
By the by, the same type of problem exists for a "delete directory"
|
||
operation. OS-9/N.F.S. supports a SS_Rmdir setstat, called by the
|
||
"deldir" utility.
|
||
|
||
/* open a path to the directory we'll manipulate */
|
||
|
||
if ((path=open(defdir,openmode)) == ERROR)
|
||
exit(_errmsg(errno,"can't open \"%s\". ",defdir));
|
||
|
||
/* try an SS_Rename call */
|
||
|
||
if (_ss_rename(path,oldname,newname,&errstat) == -1) {
|
||
if (errstat != E_UNKSVC)
|
||
exit(_errmsg(errno,"can't rename file. "));
|
||
else {
|
||
|
||
/* SS_Rename not supported, we need to set the highbit in the last
|
||
character of newname, seek to the correct entry in the directory,
|
||
and rewrite the name. (Assumes we've already done a getstat to
|
||
locate the position of the directory entry. Kids, don't try this
|
||
at home... ;-) */
|
||
|
||
*(newname+strlen(newname)-1) |= HIGHBIT;
|
||
fnamepos = gsbuffer.sg_dirptr;
|
||
if (lseek(path,fnamepos,0) != fnamepos)
|
||
exit(_errmsg(errno,"can't seek. "));
|
||
if (write(path,newname,strlen(newname)+1) == ERROR)
|
||
exit(_errmsg(errno,"can't write new name. "));
|
||
}
|
||
}
|
||
if(close(path) == ERROR)
|
||
exit(_errmsg(errno,"can't update new name. "));
|
||
|
||
/*-------------------------------------------
|
||
* _ss_rename(p,from,to,ret) - call file manager to rename file/dir.
|
||
*
|
||
*-------------------------------------------
|
||
*/
|
||
#asm
|
||
stkto set 4
|
||
stkret set 8
|
||
_ss_rename:
|
||
move.l stkto(a7),d3 to name
|
||
move.l d1,d2 from name
|
||
move.l #SS_Rename,d1 ss_rename function
|
||
os9 I$SetStt call setstat
|
||
bcs.s _rename_err if error
|
||
moveq #0,d0 no error
|
||
rts
|
||
_rename_err
|
||
move.l stkret(a7),a0 error code address
|
||
move.l d1,(a0) return error code
|
||
moveq #-1,d0 indicate error
|
||
rts
|
||
#endasm
|
||
|
||
Mike Burgher
|
||
Microware Systems Corporation
|
||
---------File ends----------------------------------------------------
|
||
--------------------------------------------------------------------------
|
||
Ken Scales Delphi:KSCALES Internet:kscales@delphi.com CIS:74646,2237
|
||
=-=-=-=-=-= Intel: Putting the backward in backward compatible =-=-=-=-=-=
|
||
|
||
-*-
|
||
|
||
88368 4-JUL 00:15 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88354)
|
||
From: JOELHEGBERG To: KSCALES
|
||
|
||
Hey, Ken...
|
||
|
||
> Picking up on this thread again, I ran across a file here while doing
|
||
> some hard drive maintenance that I thought you might find interesting.
|
||
> ---------File starts----------------------------------------------------
|
||
> This is from Microware.
|
||
>
|
||
> Following is a C-binding to call SS_Rename.
|
||
|
||
Of course... duh. That file looks remarkably similar to a file I have
|
||
on my hard drive! In fact, it is the same one! :) I got that (over
|
||
the CoCoList I think) a long time ago when I was not yet proficient in
|
||
the C programming language, so I did not pay much attention to it, but
|
||
since it looked important, I never-the-less filed it away for later use.
|
||
Too bad I forgot about it when the time came to use it! :)
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88414 5-JUL 20:52 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88348)
|
||
From: HAWKSOFT To: COLORSYSTEMS
|
||
|
||
Zack:
|
||
> That's all well and good and shows how to pass the environment to a
|
||
> module in a child process, in this case, rename. However, the system still
|
||
> needs to find rename if it is not in memory. If the programmer expects for
|
||
> the module of the child process to be available via a PATH in the
|
||
> environment, then you'd still have to write your own procfunc front end to
|
||
> os9fork().
|
||
|
||
Doesn't the C version of fork look in memory and then the exec dir?? The
|
||
assembler call does!
|
||
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88420 5-JUL 22:11 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88247)
|
||
From: CPERRAULT To: ILLUSIONIST
|
||
|
||
Since you guys are one the subject...<G>, what are Multiple Links
|
||
to files? I'm assuming it is some method that allows several files to
|
||
reference one file at once?
|
||
See Ya
|
||
>Chris<
|
||
|
||
-*-
|
||
|
||
88427 5-JUL 23:15 Programmers Den
|
||
RE: Renaming a file in C (Re: Msg 88420)
|
||
From: ILLUSIONIST To: CPERRAULT
|
||
|
||
Yep, basically it allows several directory entries to access the same
|
||
file..so, like in my case I have /DD/USR/BIN and /DD/SYSMAN/BIN contain
|
||
"mirror images" of all commands in /DD/CMDS, this way, I can have only
|
||
one copy of say, EDIT on the disk, but it can be accessed from any
|
||
of the other directories...
|
||
|
||
it saves disk space, but it doesnt really get along with the rest of OS-9
|
||
|
||
-* Mike
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88352 3-JUL 14:04 Telecom (6809)
|
||
RE: Portland, Oregon BBS (Re: Msg 75863)
|
||
From: MARKRUDY To: JEFFKOPP (NR)
|
||
|
||
love your "bill the cat "---ack !!
|
||
|
||
-*-
|
||
|
||
88353 3-JUL 14:18 General Information
|
||
RE: forsale (Re: Msg 85992)
|
||
From: MARKRUDY To: DONALDS
|
||
|
||
In reguards to the hard drive you have {had ?} for sale. What will this
|
||
HD work on ?? I have a TRS-80 model 16 running off an 8 meg HD and am
|
||
looking to upgrade. I'm currently running off of trsdosII operating
|
||
system, and hope to upgrade that too somehow. I'll be leaving the
|
||
net in a week or so, but can be reached at :
|
||
|
||
Mark Rudy
|
||
56 Highland Terrace
|
||
Donora, Pa. 15033
|
||
(412) 379-6209
|
||
thanks,
|
||
MJR
|
||
|
||
-*-
|
||
|
||
88373 4-JUL 09:44 General Information
|
||
RE: forsale (Re: Msg 88353)
|
||
From: DONALDS To: MARKRUDY (NR)
|
||
|
||
see EMAIL ; I have sold drive.
|
||
Don
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88369 4-JUL 01:02 General Information
|
||
Atlanta Fest
|
||
From: MRUPGRADE To: ALL
|
||
|
||
I just added the Atlanta Fest announcement to the UPGRADE which goes out Tue.
|
||
I'm gonna try and make this one. And haven't seen AL Dages on Delphi for
|
||
some time. Do we have any ACS Official types on line?
|
||
Til then,,, Terry Simons
|
||
|
||
-*-
|
||
|
||
88388 4-JUL 18:37 General Information
|
||
RE: Atlanta Fest (Re: Msg 88369)
|
||
From: JEJONES To: MRUPGRADE
|
||
|
||
> I'm gonna try and make this one. And haven't seen AL Dages on Delphi
|
||
> for some time. Do we have any ACS Official types on line?
|
||
|
||
I don't recall any; I think you'll have the best chance of seeing Al on
|
||
the FIDO OS-9 or CoCo echoes.
|
||
|
||
Opinions herein are solely those of their respective authors.
|
||
|
||
Clipper Chip: Big Brother Inside
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88370 4-JUL 04:27 General Information
|
||
Practical Peripherals
|
||
From: MARTYGOODMAN To: ALL
|
||
|
||
Can anyone give me the telephone number for Practical Peripherals,
|
||
the folks who make modems? They are located in or around Atlanta, Georgia.
|
||
Thanks! ---marty
|
||
|
||
-*-
|
||
|
||
88371 4-JUL 05:00 General Information
|
||
RE: Practical Peripherals (Re: Msg 88370)
|
||
From: EDELMAR To: MARTYGOODMAN
|
||
|
||
|
||
Marty,
|
||
|
||
Practical Peripherals -
|
||
|
||
31245 La Baya Drive
|
||
Westlake Village, CA 91362
|
||
1-818-991-8200
|
||
FAX 1-818-706-2474
|
||
|
||
Ed
|
||
|
||
-*-
|
||
|
||
88459 7-JUL 14:03 General Information
|
||
RE: Practical Peripherals (Re: Msg 88371)
|
||
From: MARTYGOODMAN To: EDELMAR
|
||
|
||
Thanks VERY much Ed. ---marty
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88374 4-JUL 09:53 General Information
|
||
Dynacalc
|
||
From: DONALDS To: ALL
|
||
|
||
I am using DYNACALC. for my record keeper. I have noticed that when I
|
||
print the spread sheet it asks for a name to call the spread sheet then
|
||
when it prints it ( prints this name then gives 4 or 5 linefeeds the
|
||
starts printing the spread sheet. what I would like is to delete this
|
||
header from the printing process. for it already has a name in the top
|
||
row of the spread sheet. so the name request that it wants just wastes 6
|
||
to 8 lines of paper for me. Can someone give my problem a sulutions to
|
||
eliminate these extra lines.
|
||
don
|
||
|
||
-*-
|
||
|
||
88383 4-JUL 14:51 General Information
|
||
RE: Dynacalc (Re: Msg 88374)
|
||
From: ISC To: DONALDS
|
||
|
||
Don,
|
||
|
||
In Dynacalc, if you turn off pagination, the program will not ask you for
|
||
a title. On the command line type: /APP. This is a toggle command which
|
||
will turn pagination off as well as omitting the title.
|
||
|
||
|
||
Bill
|
||
|
||
-*-
|
||
|
||
88476 8-JUL 09:08 General Information
|
||
RE: Dynacalc (Re: Msg 88383)
|
||
From: DONALDS To: ISC
|
||
|
||
Thanks Bill. I forgot about that. I will try that for the results.
|
||
Don
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88378 4-JUL 10:48 General Information
|
||
RE: SCSI info (Re: Msg 80440)
|
||
From: DSRTFOX To: MIKE_GUZZI
|
||
|
||
Mike, try the sources I listed in the last "68' micros". They have a lot of
|
||
remanufactured drives, you'll have to call and ask for the size/type you want!
|
||
|
||
-*-
|
||
|
||
88379 4-JUL 10:58 General Information
|
||
RE: SCSI info (Re: Msg 80321)
|
||
From: DSRTFOX To: DETHMASTER (NR)
|
||
|
||
I replied to this earlier, but will go through again for others benefit! IDE
|
||
stands for "Integrated Drive Electronics". The controller is built on the
|
||
drive, similar to SCSI. The drive itself MIGHT be SCSI, or MFM, or RLL, etc.,
|
||
but isusually a proprietary
|
||
format that varies the amount of data on each track... longer (outer) tracks
|
||
can have more sectors than shoertr (inner) tracks. You DON'T low level format
|
||
IDE drives normally, but if you do the controller ROM knows how to fortmat the
|
||
sectors. As for the b
|
||
us, the connector for IDE was designed to be almost identical to the PC/AT 16
|
||
bit bus. So it is extremely cheap for a motheboerad manufacturerto intergrate
|
||
an IDE interface on the motherboard. It requires a few inverted lines.... five
|
||
nickel chips will ma
|
||
ke an IDE interface out of a standard PC/AT bus connector (nickel in large
|
||
quantities!)! Some of the lines are inverted. An 8 bit card is more expensive
|
||
because the 8 bits have to be cached and sent out as 16 bits and vice versa,
|
||
and there are more signal
|
||
conversions. Theoretically, an 8 bit card SHOULD work in a B&B interface with
|
||
the B&B drivers. All IDE drives have an "emulation" mode where they will
|
||
emulate a certain type MFM or RLL drive. The manula with the drive will state
|
||
something about what drive
|
||
type (sectors/heads/etc.) to use if your computer doesn't have a programmable
|
||
drive type. OS-9 may not like that though, so if ytodecide to try that, you're
|
||
on your own!
|
||
|
||
-*-
|
||
|
||
88381 4-JUL 14:18 General Information
|
||
RE: SCSI info (Re: Msg 88378)
|
||
From: MIKE_GUZZI To: DSRTFOX (NR)
|
||
|
||
well im not going to put any money into this drive now, if i get lucky to
|
||
find a board for it fine, if not oh well. (i don't really need it since
|
||
I now have two 85 meggers on one machine and a 20 megger on the other)
|
||
|
||
Mike
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88382 4-JUL 14:24 General Information
|
||
hard drives
|
||
From: MIKE_GUZZI To: DSRTFOX (NR)
|
||
|
||
Oh i just read the message you replied to, thats an OLD message!
|
||
yeah what happned is i was looking to upgrade from my 30 meggers to something
|
||
larger. (i still have that B&B + 2 X 30 meg drives system) what i ended
|
||
up doing was buying a ken-ton SCSI adaptor and an 85 meg drive. I had sitting
|
||
on the side a Quantum pro drive which was supposed to be used for my MM/1
|
||
which i never got, so i put that online with the 85 megger. Then, i made a trade
|
||
|
||
to obtain another 30 meg SCSI drive, but upon hooking it up, i blew out the
|
||
Quantum drive AND the 30 meg seagate (the power connector was reversed!)
|
||
The seagate drive's logic board is dead, but mechanically its ok. So im
|
||
looking for a new board for it (not killing myself to do so)
|
||
So i ended up buying a second 85 meg SCSI drive for my system, threw out
|
||
the quantum drive and am running with 170 megs now for the BBS.
|
||
|
||
My old system (B&B 30 meg X 2) is sitting on the shelf, never sold it. my
|
||
second coco has a B&B 20 meg system, and for that machine, 20 meg is plenty.
|
||
I figured since i had to upgrade, i went to SCSI which is far faster.
|
||
(megareads are down to 18 seconds on this system!)
|
||
|
||
Mike
|
||
|
||
-*-
|
||
|
||
88386 4-JUL 15:31 General Information
|
||
RE: hard drives (Re: Msg 88382)
|
||
From: MITHELEN To: MIKE_GUZZI
|
||
|
||
Gesh... and I'm short of space with 2 250meg, and a 540 meg on SandV... I'm
|
||
considering selling my car and getting a 9Gig drive for the sucker...
|
||
That would hold me for a year or so...
|
||
|
||
-*-
|
||
|
||
88411 5-JUL 20:40 General Information
|
||
RE: hard drives (Re: Msg 88386)
|
||
From: MIKE_GUZZI To: MITHELEN
|
||
|
||
i mainly need the space for my bbs, my second coco has a 20 meg and is
|
||
quite enough
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88385 4-JUL 15:14 General Information
|
||
DynaCalc
|
||
From: CLTUCKER To: ALL
|
||
|
||
In using DynaCalc for record storage and retrieval what is the capacity
|
||
for record storage? Can records of any size be found, blockmarked and
|
||
printed? I use SimplyBetter for the same purpose. Works great and fast.
|
||
Just curious. (grin)
|
||
CL
|
||
|
||
-*-
|
||
|
||
88412 5-JUL 20:50 General Information
|
||
RE: DynaCalc (Re: Msg 88385)
|
||
From: ISC To: CLTUCKER
|
||
|
||
C. L.,
|
||
|
||
Dynacalc files can be of varying size depending on the size of the spreadsheet
|
||
in question although I do not know what is the maximum size. As far as
|
||
printing.......as FOR printing Dynacalc files, the Dynacalc function for
|
||
storing text files is nearly useless because Dynacalc inserts numerous
|
||
blanks and > characters in its test files. There is a utility here in the
|
||
database for translating Dynacalc files called Cal2text, but I have never
|
||
been able to make it work.
|
||
|
||
Upon consulting the Dynacalc manual, Dynacalc spreadsheets can be max 256
|
||
x 256 columns and rows. Memory used for each cell varies widely.
|
||
|
||
Bill
|
||
|
||
-*-
|
||
|
||
88417 5-JUL 20:55 General Information
|
||
RE: DynaCalc (Re: Msg 88412)
|
||
From: CLTUCKER To: ISC
|
||
|
||
Thanks for the info Bill. Where can DynaCalc be obtained? (g)
|
||
CL
|
||
|
||
-*-
|
||
|
||
88418 5-JUL 21:06 General Information
|
||
RE: DynaCalc (Re: Msg 88417)
|
||
From: ISC To: CLTUCKER
|
||
|
||
C. L.,
|
||
|
||
I believe that Dynacalc is still available from Tandy via the special
|
||
order system. There is a book which most Radio Shack stores have
|
||
hidden behind the counter for ordering this type of "old" merchandise.
|
||
The prices have become quite reasonable. OR call (800) 321-3133 and
|
||
ask them to connect you to the special order line for CoCo software.
|
||
|
||
Bill
|
||
|
||
-*-
|
||
|
||
88419 5-JUL 21:58 General Information
|
||
RE: DynaCalc (Re: Msg 88418)
|
||
From: JRUPPEL To: ISC
|
||
|
||
Bill,
|
||
The prices that RS has on the Consumer Mail Catalogue items is REDUCED...
|
||
still not in line with a used copy
|
||
which should be readily available in the Classifieds here. If someone out
|
||
there is set on getting an Original copy with a tyo
|
||
typed label, and photocopied docs, Consumer Mail at the Shack is where to go...
|
||
otherwise, check here with the folks that do resell...
|
||
Just my (photocopied) 2 cents worth ;)
|
||
John Ruppel
|
||
CocoNuts
|
||
|
||
-*-
|
||
|
||
88424 5-JUL 22:35 General Information
|
||
RE: DynaCalc (Re: Msg 88419)
|
||
From: ISC To: JRUPPEL
|
||
|
||
John,
|
||
|
||
Good Point....support your local CoCoist! Absolutely!
|
||
|
||
Bill
|
||
|
||
-*-
|
||
|
||
88447 6-JUL 22:38 General Information
|
||
RE: DynaCalc (Re: Msg 88417)
|
||
From: ISC To: CLTUCKER
|
||
|
||
C. L.,
|
||
|
||
After some time I realized that you should also know that there is in the
|
||
database here a utility called Dynacolm which allows Dynacalc to use a
|
||
smaller font thereby enabling the user to display more columns and rows on
|
||
an 80-column screen. I think you will find several utils if you search the
|
||
apps database for "Dynacalc".
|
||
|
||
Bill
|
||
|
||
-*-
|
||
|
||
88453 7-JUL 00:08 General Information
|
||
RE: DynaCalc (Re: Msg 88385)
|
||
From: DBREEDING To: CLTUCKER
|
||
|
||
> In using DynaCalc for record storage and retrieval what is the capacity
|
||
> for record storage? Can records of any size be found, blockmarked and
|
||
> printed?
|
||
|
||
I think your record storage is limited by your memory. With level 2, (you
|
||
_are_ using a coco, aren't you) I think you can get about 32K or so. You
|
||
can get more if you dump help, I think. Never used it much, but it seems
|
||
to be pretty good.
|
||
|
||
-- David Breeding --
|
||
CompuServe : 72330,2051
|
||
Delphi : DBREEDING
|
||
|
||
*** Sent via CoCo-InfoXpress V1.01 ***
|
||
^^^^ ^^^^^^^^^^
|
||
|
||
-*-
|
||
|
||
88466 7-JUL 21:38 General Information
|
||
RE: DynaCalc (Re: Msg 88418)
|
||
From: RICKULAND To: CLTUCKER
|
||
|
||
Dynacalcs are always available. The most it will possibly cost
|
||
is $20 for a new one (from CoNect...the $30 price is a typo). Used are less
|
||
I expect.
|
||
-ricku
|
||
x
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88387 4-JUL 16:35 Programmers Den
|
||
OS9000
|
||
From: PHILSCHERER To: ALL
|
||
|
||
Does anyone know how to do some simple graphics stuff on OS9000 like change
|
||
screen colors ?? Any help is appreciated! <Phil>
|
||
|
||
-*-
|
||
|
||
88389 4-JUL 19:22 Programmers Den
|
||
RE: OS9000 (Re: Msg 88387)
|
||
From: ILLUSIONIST To: PHILSCHERER
|
||
|
||
Well, this is a guess, and for the record I dont even have OS-9000
|
||
but here goes..
|
||
|
||
For the most part, I'd say you need G-windows for OS-9000 to do any
|
||
real heavy graphics stuff..but for simple stuff, I think all you would
|
||
need is a C lib. function to do it, if Mware hasnt included such a thing
|
||
then I would be willing to say that they havent included provisions for
|
||
it with OS-9000, they do offer a package called QD Menu Maker or some
|
||
such thing, that will allow you to make color text based GUI's that
|
||
you see painted on the face of many DOS apps...I suppose the best way
|
||
to do graphics stuff with OS-9000 would be to get Gwindows, the next best
|
||
would be to launch a DOS session and use a DOS based programming language
|
||
|
||
-* Mike
|
||
|
||
BTW, have you checked the manual for any kinds of screen codes that could
|
||
be sent like on the CoCo ? I doubt it is possible without some external
|
||
stuff like QD menu maker or Gwindows, although, you COULD probably write
|
||
routines to manipulate the video card yourself...
|
||
|
||
|
||
-*-
|
||
|
||
88391 4-JUL 19:27 Programmers Den
|
||
RE: OS9000 (Re: Msg 88387)
|
||
From: COLORSYSTEMS To: PHILSCHERER
|
||
|
||
> Does anyone know how to do some simple graphics stuff on OS9000 like
|
||
> change screen colors ?? Any help is appreciated! <Phil>
|
||
|
||
The /term device in OS9K is an ANSI device. So the ANSI codes to
|
||
change the colors are what you need to use.
|
||
|
||
Lessee, I got that info around here somewhere, let me go looking ...
|
||
|
||
Here is a file you might want to capture and save:
|
||
|
||
Villanova University
|
||
Campus Computing - Terminal Emulation
|
||
Includes VT100 and VT52 Terminal and Control Codes
|
||
|
||
This file contains control and terminal codes for the VT100 terminals,
|
||
ANSI terminals, and VT52 terminals. Many of the codes were derived from PC -
|
||
INTERCOMM, from Mark of the Unicorn Software. I have researched some of them
|
||
and added some of my own.
|
||
|
||
Thank you,
|
||
Jim Mc Ree (209507097@VUVAXCOM.BITNET)
|
||
|
||
(* ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** *)
|
||
|
||
CONTROL SEQUENCE SUMMARY
|
||
|
||
* For additional information on the DEC VT100 and VT102 terminals, please
|
||
consult the VT100 USER GUIDE and VT102 USER GUIDE, published by Digital
|
||
Equipment Corporation as part numbers EK-VT100-UG and EK-VT102-UG.
|
||
|
||
|
||
CONTROL CHARACTERS:
|
||
------------------
|
||
|
||
Character
|
||
Name Decimal Action Taken
|
||
---------------------------------------------------------------
|
||
NUL 0 Fill character; ignored on input.
|
||
ENQ 5 Transmit answerback message.
|
||
BEL 7 Ring the bell.
|
||
BS 8 Move cursor left.
|
||
HT 9 Move cursor to next tab stop.
|
||
LF 10 Line feed; causes print if in autoprint.
|
||
VT 11 Same as LF.
|
||
FF 12 Same as LF.
|
||
CR 13 Move cursor to left margin or newline.
|
||
SO 14 Invoke G1 character set.
|
||
SI 15 Invoke G0 character set.
|
||
XON 17 Resume transmission.
|
||
XOFF 19 Halt transmission.
|
||
CAN 24 Cancel escape sequence and display checkerboard.
|
||
SUB 26 Same as CAN.
|
||
ESC 27 Introduce a control sequence.
|
||
DEL 127 Fill character; ignored on input.
|
||
|
||
* All characters less than 32 decimal which are not listed above are ignored.
|
||
|
||
(* ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** *)
|
||
|
||
ANSI MODE SUMMARY:
|
||
-----------------
|
||
|
||
*In ANSI sequences, parameters are given as a string of ASCII digits
|
||
('0' - '9') seperated by semicolons. Pn refers to a number whose value
|
||
used directly. Ps refers to a number used as a selector.
|
||
|
||
CURSOR MOVEMENT:
|
||
---------------
|
||
|
||
Cursor Up: Esc [ Pn A
|
||
Cursor Down: Esc [ Pn B
|
||
Cursor Left: Esc [ Pn C
|
||
Cursor Right: Esc [ Pn D
|
||
|
||
Direct Addressing : Esc [ Pn(row);Pn(col);H or
|
||
Esc [ Pn(row);Pn(col);f
|
||
|
||
ie. (Pascal)
|
||
Writeln (Esc,'[',Row:1,';',col:1,';','H');
|
||
|
||
Index: Esc D
|
||
New Line: Esc E
|
||
Reverse Line: Esc M
|
||
|
||
Save cursor & Attributes: Esc 7
|
||
Restore cursor & attributes: Esc 8
|
||
|
||
ERASING:
|
||
-------
|
||
|
||
Cursor to end of line Esc [ K
|
||
Beginning of line to cursor Esc [ 1 K
|
||
Entire line Esc [ 2 K
|
||
Cursor to end of screen Esc [ J
|
||
Beginning of screen to cursor Esc [ 1 J
|
||
Entire screen Esc [ 2 J
|
||
|
||
MODES:
|
||
-----
|
||
|
||
Set with Esc [ Ps h
|
||
Reset with Esc [ Ps l
|
||
|
||
Mode name Ps Set Reset
|
||
-------------------------------------------------------------------
|
||
Keyboard action 2 Locked Unlocked
|
||
Insertion 4 Insert Overwrite
|
||
Send - Receive 12 Full Echo
|
||
Line feed/New line 20 New line Line feed
|
||
Cursor key ?1 Application Cursor
|
||
ANSI/VT52 ?2 ANSI VT52
|
||
Column ?3 132 80
|
||
Scrolling ?4 Smooth Jump
|
||
Screen ?5 Reverse Normal
|
||
Origin ?6 Relative Absolute
|
||
Wraparound ?7 Wrap Truncate
|
||
Auto key repeat ?8 Repeating No repeat
|
||
Print form feed ?18 Yes No
|
||
Print extent ?19 Full screen Scrolling region
|
||
|
||
Keypad application Esc =
|
||
Keypad numeric mode Esc >
|
||
|
||
EDITING:
|
||
-------
|
||
|
||
Insert line Esc [ Pn L
|
||
Delete line Esc [ Pn M
|
||
Delete character Esc [ Pn P
|
||
Scrolling region Esc [ Pn(top);Pn(bot) r
|
||
|
||
PRINTING:
|
||
--------
|
||
|
||
Print screen or region Esc [ i
|
||
Print cursor line Esc [ ? 1 i
|
||
Enter auto print Esc [ ? 5 i
|
||
Exit auto print Esc [ ? 4 i
|
||
Enter print controller Esc [ 5 i
|
||
Exit print controller Esc [ 4 i
|
||
|
||
LINE SIZE:
|
||
---------
|
||
|
||
The following is a list of the available styles of printing on the
|
||
screen. "Yes" in any column means that the option is supported by the escape
|
||
code on that line. "No" means that the option is not supported by the escape
|
||
code on that line; however, it may, and almost certainly is, supported by
|
||
another escape sequence. Double height and double width double the size of the
|
||
characters in their respective ways (ie. Double height is twice as tall as
|
||
usual). _Line designates underlining. Blink is for blinking characters. Side
|
||
is the orientation of the character. Normal means that there is no orientation.
|
||
|
||
Top and bottom refers to the position of the character in order to make a
|
||
complete character. The top and bottom sequences will be important if you use
|
||
the double height option. You will need to print the line twice to get a
|
||
complete line. The first printing will print the top part of the characters and
|
||
|
||
the second printing will print the bottom part. Inverse refers to the condition
|
||
|
||
of the character. "No" indicates that the character will be printed in the
|
||
color it normally is printed in with its usual backround. "Yes" means that the
|
||
character will be printed in the backround color and the character's backround
|
||
will be the color it is usually printed in. Shade refers to the brightness of
|
||
the character. Normal is the standard brightness of the character. Bright is
|
||
bold type. Dark is a darker brightness than usual. The escape code is the
|
||
command you would type before the text you want to print to get the indicated
|
||
effects. This section was greatly expanded in version 1.1 of this file.
|
||
|
||
Double Double
|
||
Height Width _Line Blink Side Inverse Shade Escape Code
|
||
-----------------------------------------------------------------------
|
||
No No No No Normal No Normal <ESC>[0m
|
||
Yes Yes No No Top No Bright <ESC>#3<ESC>[1m
|
||
Yes Yes No No Bottom No Bright <ESC>#4<ESC>[1m
|
||
Yes Yes No No Top No Dark <ESC>#3<ESC>[2m
|
||
Yes Yes No No Bottom No Dark <ESC>#4<ESC>[2m
|
||
Yes Yes No No Top No Normal <ESC>#3<ESC>[3m
|
||
Yes Yes No No Bottom No Normal <ESC>#4<ESC>[3m
|
||
Yes Yes Yes No Top No Normal <ESC>#3<ESC>[4m
|
||
Yes Yes Yes No Bottom No Normal <ESC>#4<ESC>[4m
|
||
Yes Yes No Yes Top No Normal <ESC>#3<ESC>[5m
|
||
Yes Yes No Yes Bottom No Normal <ESC>#4<ESC>[5m
|
||
Yes Yes No No Top Yes Normal <ESC>#3<ESC>[7m
|
||
Yes Yes No No Bottom Yes Normal <ESC>#3<ESC>[7m
|
||
No Yes No No Normal No Normal <ESC>#6<ESC>[0m
|
||
No Yes No No Normal No Bright <ESC>#6<ESC>[1m
|
||
No Yes No No Normal No Dark <ESC>#6<ESC>[2m
|
||
No Yes Yes No Normal No Normal <ESC>#6<ESC>[4m
|
||
No Yes No Yes Normal No Normal <ESC>#6<ESC>[5m
|
||
No Yes No No Normal Yes Normal <ESC>#6<ESC>[7m
|
||
No No No No Normal No Bright <ESC>#7<ESC>[1m
|
||
No No No No Normal No Dark <ESC>#7<ESC>[2m
|
||
No No Yes No Normal No Normal <ESC>#7<ESC>[4m
|
||
No No No Yes Normal No Normal <ESC>#7<ESC>[5m
|
||
No No No No Normal Yes Normal <ESC>#7<ESC>[7m
|
||
|
||
* Some codes have been eliminated due to a repitition of effects. To the best
|
||
of my knowledge, these codes are complete and correct. If you should find
|
||
any errors, or you find some new sequences/effects, please inform me.
|
||
|
||
* <ESC>#3 and <ESC>#4 behave in the same way as <ESC>#3[3m and <ESC>#4[4m.
|
||
|
||
CHARACTER SETS:
|
||
--------------
|
||
|
||
Character set G0 G1
|
||
-----------------------------------------------------
|
||
United Kingdom (UK) Esc ( A Esc ) A
|
||
United States (US) Esc ( B Esc ) B
|
||
Graphics Esc ( 0 Esc ) 0
|
||
Default ROM Esc ( 1 Esc ) 1
|
||
Alternate ROM Esc ( 2 Esc ) 2
|
||
|
||
Switch to G0/G1 Esc O Esc N
|
||
|
||
TAB STOPS:
|
||
---------
|
||
|
||
Set tab at current column Esc H
|
||
Clear tab at current column Esc [ g
|
||
Clear all tabs Esc [ 3 g
|
||
|
||
MISCELLANEOUS:
|
||
-------------
|
||
|
||
Reset Esc c
|
||
|
||
Character attributes Esc [ Ps m
|
||
0 - All attributes off
|
||
1 - Bold on (also high intensity for colors)
|
||
4 - Underscore on
|
||
5 - Blink on
|
||
7 - Reverse on
|
||
(Forground)
|
||
30 - Black/Gray (normal/high intensity)
|
||
31 - Red/Bright Red
|
||
32 - Green/Bright Green
|
||
33 - Brown/Yellow
|
||
34 - Blue/Bright Blue
|
||
35 - Magenta/Bright Magenta
|
||
36 - Cyan/Bright Cyan
|
||
37 - White/Bright White
|
||
(Background)
|
||
40 - Black
|
||
41 - Red
|
||
42 - Green
|
||
43 - Brown
|
||
44 - Blue
|
||
45 - Magenta
|
||
46 - Cyan
|
||
47 - White
|
||
|
||
Programmable LEDs Esc [ Ps q
|
||
0 - All LEDs off
|
||
(1 - 4) - Turn respective LED on
|
||
|
||
Fill screen with "E"s Esc # 8
|
||
|
||
(* ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** *)
|
||
|
||
NON - VT100 CONTROL SEQUENCES:
|
||
-----------------------------
|
||
|
||
*Some VT100 terminal programs also understand a few other escape
|
||
sequences than the standard VT100. I cannot guarantee any of these
|
||
non - standard codes will work with any particular terminal, but they
|
||
may be useful if they do work.
|
||
|
||
Transmit a file Esc { T filenameCR ---> CR = Carriage Return
|
||
Receive a file Esc { R filenameCR ---> CR = Carriage Return
|
||
Append to a file Esc { A filenameCR ---> CR = Carriage Return
|
||
Save collected text Esc { S
|
||
Save collected text Esc S
|
||
|
||
* These sequences will probably be most useful in developing a micro
|
||
version of a VT100 emulator or in adapting an existing one.
|
||
|
||
(* ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** *)
|
||
|
||
VT52 MODE SUMMARY:
|
||
-----------------
|
||
|
||
Cursor up Esc A
|
||
Cursor down Esc B
|
||
Cursor right Esc C
|
||
Cursor left Esc D
|
||
Graphics character set Esc F
|
||
ASCII character set Esc G
|
||
Home cursor Esc H
|
||
Reverse line feed Esc I
|
||
Erase to end of screen Esc J
|
||
Erase to end of line Esc K
|
||
Print cursor line Esc V
|
||
Enter print controller Esc W
|
||
Exit print controller Esc X
|
||
Cursor address Esc Y row col
|
||
Identify Esc Z
|
||
Print screen Esc ]
|
||
Enter auto print Esc ^
|
||
Exit auto print Esc -
|
||
Alternate ke<6B>]<5D>*5<><35>j$H<> Numeric keypad Esc >
|
||
Enter ANSI mode Esc <
|
||
|
||
* Row and column numbers are single characters with a bias of 31.
|
||
E.g., "$" means row/column 5.)
|
||
|
||
KEYPAD AND FUNCTION KEY SUMMARY:
|
||
-------------------------------
|
||
|
||
CURSOR CONTROL KEYS:
|
||
-------------------
|
||
Vt52 ANSI and Cursor Key modes
|
||
Arrow Key Mode Reset Set
|
||
---------------------------------------------------
|
||
Up Esc A Esc [ A Esc O A
|
||
Down Esc B Esc [ B Esc O B
|
||
Right Esc C Esc [ C Esc O C
|
||
Left Esc D Esc [ D Esc O D
|
||
|
||
AUXILLIARY KEYPAD:
|
||
-----------------
|
||
|
||
VT52 Mode ANSI Mode
|
||
Key Numeric Application Numeric Application
|
||
----------------------------------------------------------------------
|
||
0 0 Esc ? p 0 Esc O p
|
||
1 1 Esc ? q 1 Esc O q
|
||
2 2 Esc ? r 2 Esc O r
|
||
3 3 Esc ? s 3 Esc O s
|
||
4 4 Esc ? t 4 Esc O t
|
||
5 5 Esc ? u 5 Esc O u
|
||
6 6 Esc ? v 6 Esc O v
|
||
7 7 Esc ? w 7 Esc O w
|
||
8 8 Esc ? x 8 Esc O x
|
||
9 9 Esc ? y 9 Esc O y
|
||
- - Esc ? m - Esc O m
|
||
, , Esc ? l , Esc O l
|
||
. . Esc ? n . Esc O n
|
||
ENTER ^M Esc ? M ^M Esc O M
|
||
PF1 Esc P Esc P Esc O P Esc O P
|
||
PF2 Esc Q Esc Q Esc O Q Esc O Q
|
||
PF3 Esc R Esc R Esc O R Esc O R
|
||
PF4 Esc S Esc S Esc O S Esc O S
|
||
|
||
VT100 CURRENT STATES:
|
||
--------------------
|
||
|
||
Esc [ c DA:Device Attributes
|
||
|
||
or
|
||
|
||
Esc Z DECID:Identify Terminal (ANSI mode)
|
||
|
||
* Irrespective of the parameter(s) present, the
|
||
response is always
|
||
|
||
Esc [ ? 6 c
|
||
ie. a VT102.
|
||
|
||
Esc Z Identify (VT52 mode)
|
||
|
||
* The sequence Esc / Z is always returned.
|
||
|
||
Esc [ <sol> x DECREQTPARM: Request Terminal Parameters
|
||
|
||
* <sol> values other than 1 are ignored. Upon
|
||
receipt of a <sol> value of 1, the following
|
||
response is sent:
|
||
|
||
Esc[3;<par>;<nbits>;<xspeed>;<rspeed>;1;0x
|
||
|
||
* Where <par>, <nbits>, <xspeed>, and <rspeed>
|
||
are as for VT100s with the following
|
||
exceptions:
|
||
|
||
<nbits> Values of 5 and 6 bits per
|
||
character are sent as 7 bits.
|
||
|
||
<xspeed>,<rspeed>
|
||
These two numbers will always
|
||
be the same. 9600 baud is
|
||
sent for 7200 baud.
|
||
|
||
Esc [ Ps n DSR: Device Status Report
|
||
|
||
* Parameter values other than 5, 6, are ignored.
|
||
If the parameter value is 5, the sequence
|
||
Esc [ O n is returned. If the parameter value is
|
||
6, the CPR: Cursor Position Report sequence
|
||
Esc [ Pn ; Pn R is returned with the Pn set to
|
||
cursor row and column numbers.
|
||
|
||
|
||
|
||
|
||
|
||
------------------------------------
|
||
Zack C Sessions
|
||
|
||
They say, "Money talks". But all mine ever says is, "Goodbye".
|
||
|
||
|
||
-*-
|
||
|
||
88393 4-JUL 20:36 Programmers Den
|
||
RE: OS9000 (Re: Msg 88391)
|
||
From: JMURPHY To: COLORSYSTEMS
|
||
|
||
>Here is a file you might want to capture and save.
|
||
|
||
Zack, here is a file you might want to upload to the databases.
|
||
|
||
No offense.
|
||
|
||
John
|
||
|
||
-*-
|
||
|
||
88440 6-JUL 18:07 Programmers Den
|
||
RE: OS9000 (Re: Msg 88389)
|
||
From: PHILSCHERER To: ILLUSIONIST
|
||
|
||
Thanks for the reply Mike--I'm sure it has the capability because the
|
||
config menus spout color. There just isn't anything like cgfx yet or any
|
||
window descriptors like the Coco. I'll keep diggin. I'm sure there's a way
|
||
since the MW folks do it and OS9000 is written in C. <Phil>
|
||
|
||
-*-
|
||
|
||
88441 6-JUL 18:14 Programmers Den
|
||
RE: OS9000 (Re: Msg 88391)
|
||
From: PHILSCHERER To: COLORSYSTEMS
|
||
|
||
Thanks a lot for the great info file Zack--I feel like I did when I first
|
||
started learning OS9 on the Coco years ago! <Phil>
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88392 4-JUL 20:22 General Information
|
||
CD-I info
|
||
From: HAWKSOFT To: FHOGG
|
||
|
||
Hi Frank! (and ALL)
|
||
|
||
RE: msg #84597 - connecting a terminal to the CD-I player.
|
||
|
||
I was talking to my CD-I player today. NEAT! You can run several tests
|
||
on the CD-I player, including ROM and RAM tests. It occurs to me that a
|
||
CD-I disk with a few utilities (like dir and an upload program) would allow
|
||
the CD-I to be used as a CD-Rom reader! The serial connection would be a bit
|
||
slow (9600 maybe more), but, it would be cheaper than buying a CD-Rom reader
|
||
if you already have the CD-I.
|
||
|
||
Anyone else done any poking around??? IS there a magic key-sequence to
|
||
allow more access to the CD-I innards???
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88401 4-JUL 23:18 General Information
|
||
RE: CD-I info (Re: Msg 88392)
|
||
From: FHOGG To: HAWKSOFT
|
||
|
||
Sorry, I don't have any info on that. I've abandoned CD-I for the moment.
|
||
|
||
Frank
|
||
|
||
-*-
|
||
|
||
88404 5-JUL 00:28 General Information
|
||
RE: CD-I info (Re: Msg 88392)
|
||
From: JOELHEGBERG To: HAWKSOFT
|
||
|
||
> I was talking to my CD-I player today. NEAT! You can run several tests
|
||
> on the CD-I player, including ROM and RAM tests.
|
||
|
||
Wow, Chris, that is neat! Wish I had one!
|
||
|
||
> It occurs to me that a
|
||
> CD-I disk with a few utilities (like dir and an upload program) would
|
||
> allow the CD-I to be used as a CD-Rom reader!
|
||
|
||
That would be great to be able to run those utilities on your CD-I machine!
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88395 4-JUL 21:11 Programmers Den
|
||
RE: C's stack (Re: Msg 86108)
|
||
From: TIMKIENTZLE To: JEJONES
|
||
|
||
Yes, BUT compilers can certainly do such simple guesses as ``take
|
||
the largest stack requirements of any function'' to set the
|
||
stack requirement. (Better, look at the static call-graph with
|
||
recursions removed to generate an estimate.) As a friend of mine
|
||
once commented: ``if your programming requires solving the halting
|
||
problem to compile, then your programming is TOO messy!''
|
||
|
||
Simply assuming every program can get by on 3k of stack space
|
||
(as C 3.2 seems to do) is a rather weak way to estimate stack
|
||
requirements. Simple heuristics can be amazingly effective.
|
||
|
||
- Tim
|
||
|
||
-*-
|
||
|
||
88396 4-JUL 21:17 OSK Applications
|
||
RE: zmodem crash recovery (Re: Msg 87013)
|
||
From: TIMKIENTZLE To: MITHELEN
|
||
|
||
Hmmm... Since crash recovery is handled by the ZModem receiver,
|
||
and not the sender, performing crash recovery on downloads should
|
||
be possible regardless of Delphi's implementation. There are
|
||
other factors that can prevent crash recovery, and ZModem's
|
||
negotiation of such issues of crash recovery is not entirely
|
||
effective (receivers can take sender suggestions entirely
|
||
too literally), but a failure of crash recovery is generally
|
||
due either to on-the-fly file conversions which make seeking
|
||
impossible (e.g., most ZModem implementations forbid recovery
|
||
of ASCII transfers) or due to an obstinate receiver.
|
||
|
||
Also, crash recovery is thoroughly documented in Forsberg's
|
||
1988 ZModem description, which is LONG before Delphi implemented,
|
||
so there's no excuse there for Delphi not supporting it.
|
||
- Tim Kientzle
|
||
|
||
P.S. It would be interesting to know exactly why crash
|
||
recovery doesn't work for Delphi->RZ transfers. Hmmm...
|
||
|
||
-*-
|
||
|
||
88406 5-JUL 00:42 OSK Applications
|
||
RE: zmodem crash recovery (Re: Msg 88396)
|
||
From: MITHELEN To: TIMKIENTZLE
|
||
|
||
Ya, but, at least with the more current versions, all the "controls"
|
||
are on the sending end, and delphi's sending end doesn't let
|
||
you specify options likecrash recovery.
|
||
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88426 5-JUL 22:54 OSK Applications
|
||
RE: zmodem crash recovery (Re: Msg 88396)
|
||
From: JOELHEGBERG To: TIMKIENTZLE
|
||
|
||
Tim,
|
||
|
||
> Also, crash recovery is thoroughly documented in Forsberg's
|
||
> 1988 ZModem description, which is LONG before Delphi implemented,
|
||
> so there's no excuse there for Delphi not supporting it.
|
||
>
|
||
> P.S. It would be interesting to know exactly why crash
|
||
> recovery doesn't work for Delphi->RZ transfers. Hmmm...
|
||
|
||
I have no problem with ZModem crash recovery using my Macintosh with
|
||
Delphi, so I would imagine it would be something in the RZ program
|
||
itself. My Macintosh terminal program can recover from in-stream
|
||
errors, and can also continue receiving a partially received file later
|
||
on that it left off on from another session. I once had my ZModem
|
||
driver go down during a transfer (Delphi just kept on sending away, of
|
||
course), so shut off the modem, turned it back on and dialed back up and
|
||
requested the file again... ZModem picked right up where it last left
|
||
off and successfully received the file.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
88432 6-JUL 01:17 OSK Applications
|
||
RE: zmodem crash recovery (Re: Msg 88426)
|
||
From: MITHELEN To: JOELHEGBERG
|
||
|
||
Right Joel... It is the newer releases of rz/sz that have no way of
|
||
switching on recovery from the receiveing end. The OS-9 version of
|
||
RZ/SZ strictly conform to the official Omen release of the rz/sz Zmodem
|
||
sources, because they use the official sources. I imagine your Mac
|
||
software is usining its own interpetation of the zmodem description.
|
||
Perhaps in a future release I do for OS-9, I will set zmodem receive
|
||
(rz) up so crash recovery is normally switched on, or, add the extra
|
||
coimmand line option to turn it on... this would solve the "problem".
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88438 6-JUL 07:25 OSK Applications
|
||
RE: zmodem crash recovery (Re: Msg 88426)
|
||
From: NIMITZ To: JOELHEGBERG
|
||
|
||
Perhaps your RZ/SZ implementation (the one you're using, not the one you
|
||
implemented), is sending ZPROT to prevent overwrite of files??
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88492 9-JUL 12:41 OSK Applications
|
||
RE: zmodem crash recovery (Re: Msg 88406)
|
||
From: TIMKIENTZLE To: MITHELEN
|
||
|
||
Hmmm... The thinking in ZModem is that the receiver largely controls
|
||
things like that. There is a provision for the sender to provide
|
||
`suggestions' to the receiver, but it _should_ always be possible
|
||
to specify options such as crash recovery to the receiver.
|
||
Though I haven't tried it, the `rz' I have here (version 3.17,
|
||
I probably downloaded it from Delphi) claims to support crash
|
||
recovery through the `-r' option.
|
||
Last week, I uploaded a program called `xy' which supports
|
||
XModem/YModem file transfers. It's like my earlier `xydown',
|
||
except that it should be much more robust and supports both
|
||
uploading and downloading. I'm in the process of writing a
|
||
similar program called `z' which (you guessed it) supports
|
||
ZModem. One big question I have is which of ZModem's many
|
||
options people actually use. I'm interested in finding out
|
||
which ZModem options people most often use (either with `rz' or
|
||
`sz' or any other program) so I can determine which options
|
||
`z' should have. I don't want to put in every option, since
|
||
I think that's simply too complicated. `xy' can be used in
|
||
most situations with no options at all, and I'd like `z' to
|
||
be equally user-friendly.
|
||
- Tim Kientzle
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88398 4-JUL 21:29 General Information
|
||
RE: Postscript (Re: Msg 88055)
|
||
From: TIMKIENTZLE To: PAGAN
|
||
|
||
The question is: to what extent _SHOULD_ information be provided
|
||
in a manipulable format? The `Information Age' has made it amazingly
|
||
easy to rip-off other people's work. I look upon PostScript as a good
|
||
`non-manipulable' format for materials I want people to NOT be able
|
||
to manipulate. If I want people to be able to easily manipulate something,
|
||
I post it in some other format.
|
||
Food for though,
|
||
Tim Kientzle
|
||
|
||
-*-
|
||
|
||
88399 4-JUL 22:13 General Information
|
||
OS-9 fest in Dallas?
|
||
From: NIMITZ To: ALL
|
||
|
||
I am looking for OS-9'ers in Dallas to help sponsor 9Con '95 inn February of
|
||
1995. Dave Wordell - or Lee Veal have been mentioned as possible candidates
|
||
by a mutual friend also involved, if they are still in the forum, I'd like to
|
||
hear from them. I'd
|
||
also like to hear from any other volunteers. This should be a show resembling
|
||
a cocofest in that we will have sales and seminalrs, but we are focusing only
|
||
on OS-9 users and hope to project a professional image. Thanks all!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88400 4-JUL 22:15 OSK Applications
|
||
MM/1 5 1/4 Drive for CoCo Format
|
||
From: NIMITZ To: ALL
|
||
|
||
To clarify my recent requests, I'm trying to get a Teac FD55FGR to read a
|
||
CoCo style 5 1/4 disk - DSDD 40 track (360K) in an MM/1 machine. Thanks Guys!
|
||
|
||
David
|
||
|
||
-*-
|
||
|
||
88410 5-JUL 20:38 General Information
|
||
blocked IO
|
||
From: TEDJAEGER To: ALL
|
||
|
||
Spent some time with the F$Alarm syscall under os9 68K. Succeeded in
|
||
writing some BASIC code that prompts user for an alarm time, sets
|
||
alarm, goes to sleep, and then wakes up and rings the bell (PRINT
|
||
CHR$(7)) when the alarm signal is sent. Works fine from the OS9
|
||
prompt with alarm("94/07/05 17:00) for example but I had in mind
|
||
letting the user go alarm("94/07/05 17:00) & to let the alarm
|
||
process run in the background. While this runs, the alarm bell is
|
||
blocked and can only be heard if I strike <ENTER> at the keyboard.
|
||
Do I have to open a window for the alarm process to run in? Seems
|
||
like there ought to be a better way!
|
||
|
||
Bests
|
||
---TedJaeger
|
||
|
||
-*-
|
||
|
||
88425 5-JUL 22:54 General Information
|
||
RE: blocked IO (Re: Msg 88410)
|
||
From: JOELHEGBERG To: TEDJAEGER
|
||
|
||
Ted,
|
||
|
||
...
|
||
> CHR$(7)) when the alarm signal is sent. Works fine from the OS9
|
||
> prompt with alarm("94/07/05 17:00) for example but I had in mind
|
||
> letting the user go alarm("94/07/05 17:00) & to let the alarm
|
||
> process run in the background. While this runs, the alarm bell is
|
||
> blocked and can only be heard if I strike <ENTER> at the keyboard.
|
||
> Do I have to open a window for the alarm process to run in? Seems
|
||
> like there ought to be a better way!
|
||
|
||
If you find one, let me know. I've had this problem with a number of
|
||
projects (ModJukeBox, Announce, KWSaver). I generally have to open
|
||
another window. Also, even if you aren't even sending a character to
|
||
sound the alarm (sending character $07 to stdout), but rather are using
|
||
a digitized sound sample, even the _ss_play() setstat is still blocked,
|
||
so there seems to be no easy way out.
|
||
|
||
|
||
-- Joel Mathew Hegberg
|
||
Delphi : JOELHEGBERG
|
||
Internet: JoelHegberg@Delphi.com
|
||
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88421 5-JUL 22:11 Programmers Den
|
||
RE: Latest in Basic problems (Re: Msg 88273)
|
||
From: CPERRAULT To: ILLUSIONIST
|
||
|
||
>>If you want Basic source for reading in a filename..take a look
|
||
at the source for IndiPWB<<
|
||
|
||
Funny you mentioned that. I could have sworn had already DL'ed
|
||
that, but when I looked through my dirs, I couldn't find it. I guess I
|
||
was about to download it then didn't for some reason. 'Course, I was
|
||
getting it then more to check out the program itself rather than the
|
||
source, but I guess now it will serve two purposes ;-). Anyhow I have
|
||
it now, and even tho my problem has since been SOLVED(YES) I'll give
|
||
it a look anyway. It's always interesting to see how other developers
|
||
code, and I'm sure there are other things I can learn from it<I'm in
|
||
the middle of three different projects in Basic, so you guys better
|
||
plan on hearing a LOT from me<Grin>.
|
||
|
||
Btw, did you ever release a commercial version of 'Indypwb' or is
|
||
it still in the works? I'm looking forward to seeing it in action for
|
||
the first time.
|
||
|
||
>Chris<
|
||
|
||
-*-
|
||
|
||
88422 5-JUL 22:12 Programmers Den
|
||
RE: Latest in Basic problems (Re: Msg 88279)
|
||
From: CPERRAULT To: PAGAN
|
||
|
||
>>Since 'Name' isn't properly terminated yet, there is no way for
|
||
Basic09 to know where to put the $FF terminator.<<
|
||
|
||
Hmm, I'm a bit confused. I can remember which version of the
|
||
source I posted, but I've been through a lot of them, so I'll try and
|
||
remember the best I can. Isn't the name properly terminated once the
|
||
$ff is added to the entry? I was thinking that the Name=name+$ff line
|
||
would guide basic as to where it would point to in the file name?
|
||
|
||
Thanks for the info, I'm gonna be including your message in my
|
||
everygrowing, 'Basichelp' message file. The help I get from these
|
||
messages is immeasurable even in the long run, when I'm doing another
|
||
project.
|
||
|
||
>Chris<
|
||
|
||
-*-
|
||
|
||
88428 5-JUL 23:21 Programmers Den
|
||
RE: Latest in Basic problems (Re: Msg 88421)
|
||
From: ILLUSIONIST To: CPERRAULT
|
||
|
||
Nope, I never released a commercial version, as I am getting an MM/1 soon
|
||
and development for the CoCo will most likely slowdown, so, what I did
|
||
was add a bunch of features and stuff in, and release the source code so
|
||
other programmers can add features as they like, I may play with it some
|
||
more in the future, but most likely I will bring it to the MM/1 ..
|
||
|
||
While on the subject, if anyone wants it, I have a "version" of the
|
||
IndiBATCH program interpreter that supports IF/THEN/ELSE/ENDIF logic
|
||
which of course allows for really nice startup scripts for the program..
|
||
my coco is getting stripped, so, if anyone wants a copy of the code
|
||
I will have to send it on diskette via US mail..
|
||
|
||
|
||
-*-
|
||
|
||
88439 6-JUL 14:04 Programmers Den
|
||
RE: Latest in Basic problems (Re: Msg 88422)
|
||
From: ILLUSIONIST To: CPERRAULT
|
||
|
||
umm.. name=name+$FF definatley will not work. The reason is that $ff is a
|
||
number (255 in decimal) so basic thinks you are trying to add a number
|
||
to a string..obviously that will bomb out, instead try name=name+CHR$($FF)
|
||
|
||
-* Mike
|
||
PS. I think that is even gonna dump, because Basic shouldnt have to be
|
||
FORCED to adding the EOS marker..
|
||
|
||
-*-
|
||
|
||
88486 9-JUL 03:15 Programmers Den
|
||
RE: Latest in Basic problems (Re: Msg 88422)
|
||
From: PAGAN To: CPERRAULT (NR)
|
||
|
||
|
||
>>Since 'Name' isn't properly terminated yet, there is no way for Basic09 to
|
||
>>know where to put the $FF terminator.
|
||
|
||
>Hmm, I'm a bit confused. I can remember which version of the source I
|
||
>posted, but I've been through a lot of them, so I'll try and remember the
|
||
>best I can. Isn't the name properly terminated once the $ff is added to the
|
||
>entry? I was thinking that the Name=name+$ff line would guide basic as to
|
||
>where it would point to in the file name?
|
||
|
||
To add one string to another, Basic has to find the end of the first string
|
||
so it knows where to start appending the second. I recall you passed a raw
|
||
directrory entry to the routine which is terminated with high bit set so
|
||
Basic09, looking for a $FF, was unable to find the end of it. You would
|
||
have the same problem in C if you tried to do a strcat(name,"\xFF") if
|
||
'name' was a raw directory entry.
|
||
|
||
Stephen (PAGAN)
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88423 5-JUL 22:12 Programmers Den
|
||
Problem Solved
|
||
From: CPERRAULT To: ALL
|
||
|
||
|
||
This is just a note to let everyone who has been helping me that
|
||
my problem with my Protector program has been SOLVED. Special thanks
|
||
to Mike Guzzi who sent me the corrected code to get me over that
|
||
hurdle, as well as everyone else who offered suggestions and ideas,
|
||
which were very usefull. You can all count on hearing more from me in
|
||
the future ;-).
|
||
|
||
I had a longer message detailing the old code, and the fixed
|
||
version that Mike got me, but when I tried saving it with my editor,
|
||
it saved the file wrong<dunno what I did still>, and I lost that as
|
||
well as another reply I typed<so if someone here doesn't get a reply
|
||
from me, you know why<G>.
|
||
Thanks again
|
||
>Chris<
|
||
|
||
-*-
|
||
|
||
88430 6-JUL 01:10 General Information
|
||
RFI
|
||
From: MMCCLELLAND To: MARTYGOODMAN
|
||
|
||
|
||
|
||
Hi there Marty!
|
||
|
||
I received the WEFAX software in the mail and it works great. I am having
|
||
some nasty RFI problems though. This interference seems to be coming from my
|
||
CoCo, and it ruins the little reception that I can get on my old Hallicrafters
|
||
SX-71 shortwave. This interference occurs in large clusters of "spikes", which
|
||
are separated by a space about as wide as the CoCo's clock frequency. My 2
|
||
meter HT receives similar interference, except that it is so bad that all
|
||
stations in the band are wiped out completely! The problem is especially bad
|
||
during disk accesses and while using WEFAX. An outdoor antenna would probably
|
||
solve my HT's problem, but I do not have a means of connecting a better antenna
|
||
to my shortwave. I have thought of shielding my CoCo and using ferrite beads
|
||
and toroids and the like, but I don't know how to go about doing such a thing.
|
||
Any help would be greatly appreciated!
|
||
|
||
-=Mark=-
|
||
|
||
-*-
|
||
|
||
88460 7-JUL 14:10 General Information
|
||
RE: RFI (Re: Msg 88430)
|
||
From: MARTYGOODMAN To: MMCCLELLAND
|
||
|
||
I'm glad the WEFAX software is working for you. RFI can indeed
|
||
be a severe problem with systems like the CoCo, with cables going
|
||
all over the place. It's impossible to say what, if any, simple
|
||
maneuvers will significantly improve the problem. Here are few
|
||
suggestions:
|
||
|
||
(1) Get the ferrite core from an old YOKE used on a discarded
|
||
TV picture tube, and loop your disk drive cable
|
||
around it two or three times, as near to the disk controller as you
|
||
can reasonably get. This has in the past been reported to
|
||
reduce RFI during disk acess.
|
||
|
||
(2) Simply MOVE the RADIO a significant DISTANCE from
|
||
the computer installation. This might help. Since the signal
|
||
going to the computer from the radio is line level audio,
|
||
it should happily survive 25 feet of audio coax cable.
|
||
Or more. Of course, there's the question of whether that
|
||
cable is carrying RFI from the computer to the radio, but I suspect
|
||
you're dealing more with stuff picked up fron the air waves.
|
||
|
||
(3) Try wrapping any other cables that leave the computer
|
||
(joystick, printer) around torroids, too.
|
||
|
||
|
||
There are also tricks involving grounding that may be helpful...
|
||
like bringing all the grounds from everything that leaves
|
||
the computer to one central point. That can be tricky to
|
||
do on an unmodified CoCo.
|
||
|
||
You know, there's a whole SCIENCE (and art!) of making
|
||
a computer free of RFI. It's called in some places "Tempest"
|
||
technology... the code name for computers designed to be
|
||
so "silent" that you can't pick up by radio information on what
|
||
they are doing. It was a big deal in the spy business a while ago.
|
||
|
||
---marty
|
||
|
||
-*-
|
||
|
||
88465 7-JUL 21:34 General Information
|
||
RE: RFI (Re: Msg 88460)
|
||
From: RICKULAND To: MARTYGOODMAN (NR)
|
||
|
||
At one time, I had the pleasure of connecting a Sinclair ZX81 to radio.
|
||
This unit was renouned for it's rf problems- in fact used uhf36 as video
|
||
]
|
||
to get out of it's own way. It's shielding was comparable to the CoCos
|
||
(none) and it didn't even have a disk drive to toroid.
|
||
The solution on this puppy was a large sheet of aluminiu7um
|
||
($13 at the friendly builder mart for a 3x3foot) placed between the radio and
|
||
the system, and tied to earth. I had the radio on a metal shelf, in essance.
|
||
Helped quite a bit.
|
||
ricku
|
||
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88442 6-JUL 20:17 General Information
|
||
sysgo.a compile
|
||
From: TEDJAEGER To: ALL
|
||
|
||
Downloaded the sysgo archive available in new uploads. Source was
|
||
contained in the archive which allowed customization of sysgo. My
|
||
question is after you have edited sysgo per your needs, what do
|
||
you use to compile it? R68 seems to generate an inappropriate
|
||
header.
|
||
|
||
Bests
|
||
---TedJaeger
|
||
|
||
-*-
|
||
|
||
88443 6-JUL 21:29 General Information
|
||
RE: sysgo.a compile (Re: Msg 88442)
|
||
From: MITHELEN To: TEDJAEGER
|
||
|
||
r68 creates relocatable objct files, you then need to use l68 to
|
||
link in the "glue"... ie.
|
||
r68 sysgo.a -o=sysgo.r
|
||
l68 sysgo.r -l=/dd/sys/sys.l -O=sysgo
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88458 7-JUL 02:39 General Information
|
||
RE: sysgo.a compile (Re: Msg 88443)
|
||
From: JOELHEGBERG To: MITHELEN
|
||
|
||
> r68 creates relocatable objct files, you then need to use l68 to
|
||
> link in the "glue"... ie.
|
||
> r68 sysgo.a -o=sysgo.r
|
||
> l68 sysgo.r -l=/dd/sys/sys.l -O=sysgo
|
||
|
||
I don't know if this is needed or not, but I had to also reference the
|
||
usr.l library in the l68 step, so it would be:
|
||
r68 sysgo.a -O=sysgo.r
|
||
l68 sysgo.r -O=sysgo -l=/dd/lib/usr.l -l=/dd/lib/sys.l
|
||
|
||
|
||
=============================================================================
|
||
Joel Mathew Hegberg M.O.T.D. Editor
|
||
(JoelHegberg@delphi.com) 68'micros Columnist
|
||
Sub-Etha Software Programmer
|
||
=============================================================================
|
||
|
||
|
||
-*-
|
||
|
||
88464 7-JUL 20:56 General Information
|
||
RE: sysgo.a compile (Re: Msg 88458)
|
||
From: MITHELEN To: JOELHEGBERG
|
||
|
||
Possibly, I didn't try to compile the latest version. I just tried
|
||
the version I had, and it didn't need usr.l. It all depends on
|
||
what system calls that were added.
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88469 7-JUL 21:51 General Information
|
||
RE: sysgo.a compile (Re: Msg 88458)
|
||
From: HAWKSOFT To: JOELHEGBERG
|
||
|
||
Joel!!!
|
||
> > r68 creates relocatable objct files, you then need to use l68 to
|
||
> > link in the "glue"... ie.
|
||
> > r68 sysgo.a -o=sysgo.r
|
||
> > l68 sysgo.r -l=/dd/sys/sys.l -O=sysgo
|
||
>
|
||
> I don't know if this is needed or not, but I had to also reference the
|
||
> usr.l library in the l68 step, so it would be:
|
||
> r68 sysgo.a -O=sysgo.r
|
||
> l68 sysgo.r -O=sysgo -l=/dd/lib/usr.l -l=/dd/lib/sys.l
|
||
|
||
WRONG WRONG WRONG !!!!! AAAAAAANNNNNNN!!!!!
|
||
|
||
Use usr.l OR sys.l this is due to the different offsets for some of the
|
||
data (device drivers and such). The system calls and stuff are in both.
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88473 8-JUL 02:01 General Information
|
||
RE: sysgo.a compile (Re: Msg 88469)
|
||
From: JOELHEGBERG To: HAWKSOFT
|
||
|
||
Chris,
|
||
|
||
> > l68 sysgo.r -O=sysgo -l=/dd/lib/usr.l -l=/dd/lib/sys.l
|
||
>
|
||
> WRONG WRONG WRONG !!!!! AAAAAAANNNNNNN!!!!!
|
||
>
|
||
> Use usr.l OR sys.l this is due to the different offsets for some of the
|
||
> data (device drivers and such). The system calls and stuff are in both.
|
||
|
||
Hmmm... I thought I got unresolved references when I left one of those
|
||
libraries out, but didn't play around too much since including both of
|
||
them worked. I should have known to consult an official assembly
|
||
language programmer like yourself before attempting this at home. <G>
|
||
|
||
|
||
|
||
=============================================================================
|
||
Joel Mathew Hegberg M.O.T.D. Editor
|
||
(JoelHegberg@delphi.com) 68'micros Columnist
|
||
Sub-Etha Software Programmer
|
||
=============================================================================
|
||
|
||
|
||
-*-
|
||
|
||
88480 8-JUL 21:32 General Information
|
||
RE: sysgo.a compile (Re: Msg 88443)
|
||
From: TEDJAEGER To: MITHELEN
|
||
|
||
Thanks, Paul. I was whipped with no docs and all ....
|
||
|
||
Bests
|
||
---TedJaeger
|
||
|
||
-*-
|
||
|
||
88481 8-JUL 22:08 General Information
|
||
RE: sysgo.a compile (Re: Msg 88473)
|
||
From: HAWKSOFT To: JOELHEGBERG
|
||
|
||
Joel:
|
||
> Hmmm... I thought I got unresolved references when I left one of those
|
||
> libraries out, but didn't play around too much since including both of
|
||
> them worked. I should have known to consult an official assembly
|
||
> language programmer like yourself before attempting this at home. <G>
|
||
|
||
If you were assembling sysgo ( a SYSTEM module ) then sys.l would be the
|
||
library to use. If you include both, the first one with a answer (even a
|
||
wrong answer) would be used. <g>
|
||
|
||
And no, I havn't popped for the Develoers Pak yet. Frank already replied
|
||
that his machines have the hardware but, no drivers. He did suggest that I
|
||
consult Gespac as to the market.
|
||
|
||
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
88484 9-JUL 01:11 General Information
|
||
RE: sysgo.a compile (Re: Msg 88480)
|
||
From: MITHELEN To: TEDJAEGER (NR)
|
||
|
||
So was I (no docs) I figured it out by trial and error, and from
|
||
my understanding of how the C compiler steps worked...
|
||
--
|
||
Pau
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88448 6-JUL 22:51 General Information
|
||
MV Canvas
|
||
From: MRUPGRADE To: ALL
|
||
|
||
I recently found my originbnal copy of MV Canvas. there was supposed
|
||
to be an upgrade... Is MV Canvas for Os level II still being sold?
|
||
Til then,,, Terry Simons
|
||
|
||
-*-
|
||
|
||
88489 9-JUL 10:33 General Information
|
||
RE: MV Canvas (Re: Msg 88448)
|
||
From: JOHNBAER To: MRUPGRADE
|
||
|
||
|
||
> I recently found my originbnal copy of MV Canvas. there was supposed
|
||
> to be an upgrade... Is MV Canvas for Os level II still being sold?
|
||
> Til then,,, Terry Simons
|
||
|
||
Terry - contact Mike Haaland (MIKEHAALAND) here on Delphi.
|
||
He's the author of MV Canvas for Level 2, and Paint for the MM/1.
|
||
|
||
--
|
||
John -
|
||
|
||
< Posted with Ved 2.3.1 & IX 1.2.0 >
|
||
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88456 7-JUL 02:16 General Information
|
||
Monk Missing?
|
||
From: REVWCP To: ALL
|
||
|
||
Dear Friends:
|
||
I will be back east on a family visit from 7/7/94 until 7/15/94. I may get
|
||
to log on during that time. If you post any thing to me, please forgive
|
||
any delay in responding on my part.
|
||
With all best wishes,
|
||
Brother Jeremy, CSJW
|
||
OS9 User's Group Treasurer
|
||
|
||
-*-
|
||
|
||
88461 7-JUL 19:29 General Information
|
||
Bill's Book?
|
||
From: MRUPGRADE To: ALL
|
||
|
||
I am in search of a book by "Bill Barden", CONNECTING THE COCO TO THE
|
||
REAL WORLD.
|
||
Checck theh <g> stacks in your basement. there are bound oto be a few
|
||
somewhere. I'd like to get hold of a copy,, for borrow or buy??
|
||
Til then,,, Terry Simons Editor/ UPGRADE diskmagazine.
|
||
|
||
-*-
|
||
|
||
88462 7-JUL 19:34 Programmers Den
|
||
OS9000
|
||
From: PHILSCHERER To: COLORSYSTEMS
|
||
|
||
Hi Zack--For what it's worth I think I found a library that has graphics
|
||
codes for C. It's called curses.h in the defs directory. Maybe with a little
|
||
work I can get some routines going. BTW do you know how to activate the
|
||
parallell printer? I found a descriptor called p.lpt1 and loaded it. It shows
|
||
up as 'p' in memory but I cant seem to locate a driver. <Phil>
|
||
|
||
-*-
|
||
|
||
88463 7-JUL 19:45 Programmers Den
|
||
RE: OS9000 (Re: Msg 88462)
|
||
From: COLORSYSTEMS To: PHILSCHERER
|
||
|
||
> BTW do you know how to activate
|
||
> the parallell printer? I found a descriptor called p.lpt1 and loaded it.
|
||
> It shows up as 'p' in memory but I cant seem to locate a driver. <Phil>
|
||
|
||
Umm, I think the parallel printer port's driver's module name is scp68230.
|
||
|
||
|
||
|
||
------------------------------------
|
||
Zack C Sessions
|
||
|
||
They say, "Money talks". But all mine ever says is, "Goodbye".
|
||
|
||
|
||
-*-
|
||
|
||
88478 8-JUL 18:56 Programmers Den
|
||
RE: OS9000 (Re: Msg 88463)
|
||
From: PHILSCHERER To: COLORSYSTEMS
|
||
|
||
Thanks Zack--I wish the docs showed the basics a little more quickly. <Phil>
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88467 7-JUL 21:42 General Information
|
||
uud/uue
|
||
From: TEDJAEGER To: ALL
|
||
|
||
I have received a couple of text files and a program in my mail
|
||
here at Delphi that were compressed using uue. I visit Delphi
|
||
using InfoXpress which grabs my mail automatically. In each case
|
||
the compressed files have been captured but not separately from
|
||
the text message from the sender that announced the compressed
|
||
files were coming. What I see if I read the message is like:
|
||
|
||
Ted, Sending you some documentation....
|
||
and then a bunch of garbage
|
||
|
||
I can save the entire message to disk but InfoXpress gives me
|
||
no way to separate the uue compressed docs/program from the
|
||
ordinary text. Anything I can do to salvage this mess? Maybe if
|
||
I knew if there was a standard header for an uue file I could
|
||
look for it and zap the text?
|
||
|
||
Thanks for advice!
|
||
|
||
Bests
|
||
---TedJaeger
|
||
|
||
-*-
|
||
|
||
88470 8-JUL 01:22 General Information
|
||
RE: uud/uue (Re: Msg 88467)
|
||
From: MITHELEN To: TEDJAEGER
|
||
|
||
These file/messages are NOT in uue format(uuencode), that are in a binary
|
||
format used by VMS mail. You probably have no hope to "extract" them from your
|
||
OS-9 end...
|
||
--
|
||
Paul
|
||
|
||
-*-
|
||
|
||
88474 8-JUL 02:01 General Information
|
||
RE: uud/uue (Re: Msg 88467)
|
||
From: JOELHEGBERG To: TEDJAEGER
|
||
|
||
Ted,
|
||
|
||
> I can save the entire message to disk but InfoXpress gives me
|
||
> no way to separate the uue compressed docs/program from the
|
||
> ordinary text. Anything I can do to salvage this mess? Maybe if
|
||
> I knew if there was a standard header for an uue file I could
|
||
> look for it and zap the text?
|
||
|
||
The uuencoding method is quite robust, and the best thing is they do
|
||
have a standard header (a "begin" line) that contains the filename.
|
||
Because the actual encoding begins after the "begin" line, you don't
|
||
have to zap the text before (or after) the encoded message, since
|
||
uudecoder programs just ignore all text before the "begin" line.
|
||
|
||
The only problem you may have with IX and uudecoding is if the message
|
||
is long enough, sometimes Delphi will have to print the message "Press
|
||
RETURN for more..." and then a blank line, and then the rest of the
|
||
message. That will screw up the uudecoder, so you'll have to do a
|
||
search for "RETURN" and delete those lines.
|
||
|
||
|
||
|
||
=============================================================================
|
||
Joel Mathew Hegberg M.O.T.D. Editor
|
||
(JoelHegberg@delphi.com) 68'micros Columnist
|
||
Sub-Etha Software Programmer
|
||
=============================================================================
|
||
|
||
|
||
-*-
|
||
|
||
88479 8-JUL 21:26 General Information
|
||
RE: uud/uue (Re: Msg 88467)
|
||
From: HAWKSOFT To: TEDJAEGER
|
||
|
||
Ted!
|
||
> I have received a couple of text files and a program in my mail
|
||
> here at Delphi that were compressed using uue. I visit Delphi
|
||
> using InfoXpress which grabs my mail automatically. In each case
|
||
> the compressed files have been captured but not separately from
|
||
> the text message from the sender that announced the compressed
|
||
> files were coming. What I see if I read the message is like:
|
||
>
|
||
> Ted, Sending you some documentation....
|
||
> and then a bunch of garbage
|
||
>
|
||
> I can save the entire message to disk but InfoXpress gives me
|
||
> no way to separate the uue compressed docs/program from the
|
||
> ordinary text. Anything I can do to salvage this mess? Maybe if
|
||
> I knew if there was a standard header for an uue file I could
|
||
> look for it and zap the text?
|
||
|
||
The uue files are actually converted to text so they can be sent at 7
|
||
bits per byte. After you save the message to disk run 'uudecode <filename>'
|
||
and uudecode will extract the file from the message. I (almost) always
|
||
get a lot of complaints from uudecode (Checksum error in line #), but,
|
||
it always extracts properly.
|
||
|
||
I got uudecode and uuencode from the Tops disks, but, I'm sure someone
|
||
can tell you where it is here.
|
||
|
||
Chris
|
||
|
||
|
||
:-> :-> :-> :-> :-> :-> :-> Chris "HAWKSoft" <-: <-: <-: <-: <-: <-: <-:
|
||
|
||
Delphi: HAWKSOFT Internet: HAWKSOFT@DELPHI.COM
|
||
|
||
******************< Uploaded w/ InfoXpress vr. 1.01.00 >******************
|
||
|
||
-*-
|
||
|
||
End of Thread.
|
||
|
||
-*-
|
||
|
||
88471 8-JUL 02:01 General Information
|
||
OS-9 Live!
|
||
From: JOELHEGBERG To: ALL
|
||
|
||
Hi, everyone. This is just a quick reminder that this Saturday night
|
||
(July 9th) starting at 10pm, the illustrious James Jones will be the
|
||
OS-9 Live! guest host (Boisy will be on vacation) leading a discussion
|
||
on "C Programming with Termcap". This should prove to be a fascinating
|
||
topic for programmers looking to expand their horizons. Termcap will
|
||
let you do fancy footwork with a terminals cursor without knowing what
|
||
type of terminal your program is running on. Be sure to tune in, kids!
|
||
|
||
|
||
=============================================================================
|
||
Joel Mathew Hegberg M.O.T.D. Editor
|
||
(JoelHegberg@delphi.com) 68'micros Columnist
|
||
Sub-Etha Software Programmer
|
||
=============================================================================
|
||
|
||
|
||
-*-
|
||
|
||
88477 8-JUL 09:19 System Modules (6809)
|
||
PIA
|
||
From: DONALDS To: MARTYGOODMAN (NR)
|
||
|
||
Marty;
|
||
I have been experiencing some troble with my keyboard. It appears that so
|
||
sometimes when I first turn on my machine that the right arrow key will
|
||
not work for a while and also I am not able to do a shift-cntrl/break
|
||
function until the machine has been on for awhile then everything appears
|
||
to work fine. Could this be caused by a weak PIA (IC5) chip? or is it
|
||
a lead to something else.
|
||
Don
|
||
|
||
-*-
|
||
|
||
88482 8-JUL 22:41 General Information
|
||
EISA bus...
|
||
From: ROYBUR To: ALL
|
||
|
||
...and OS-9. something for the "for what it's worth" column, i received a
|
||
pack of ad cards a couple of days ago, one of which was from a company named
|
||
GMX. it describes a motherboard that accepts PC-type peripherals and has the
|
||
CPU mounted on a plug-in board. sounded a bit like a familiar concept! <g>...
|
||
.............roy
|
||
|
||
-*-
|
||
|
||
88483 9-JUL 00:38 General Information
|
||
MI & CC
|
||
From: MRUPGRADE To: ALL
|
||
|
||
It has been brought to my attention that UPTIMES magazine, made a
|
||
comment that Mid Iowa & Clountry CoCo is distributing Panet Engine.
|
||
Though unintentional by Jordan, I'm sure; this statement was in ERROR.
|
||
It was submitted for review,, interest was sparce, and it was returned
|
||
al.
|
||
we do not offer it in any form.
|
||
Terry Simons / Editor The UPGRADE
|
||
|
||
-*-
|
||
|
||
88495 9-JUL 14:58 General Information
|
||
home-brewing
|
||
From: GLOCKR To: ALL
|
||
|
||
I would like to build a computer based on the 680x0 or possibly the 6809. Are
|
||
any kits available? Also, what is a MM/1? I'd apreciate any info, I'm kind of
|
||
burned out on IBM clones. Thanks:)
|
||
|
||
-*-
|
||
|
||
|
||
FORUM>Reply, Add, Read, "?" or Exit> |