informis
/
textfiles
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
textfiles/messages/ALANWESTON/1992/CIS07_15.txt

4392 lines
146 KiB
Plaintext
Raw Normal View History

Initial commit
2021-04-15 11:31:59 -07:00
#: 15619 S7/Telecommunications
20-Jun-92 11:46:16
Sb: #15610-#WIZ Help
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Bob -
Did you scan all the Wiz modules for /d0?
Pete
There is 1 Reply.
#: 15632 S7/Telecommunications
22-Jun-92 00:48:29
Sb: #15619-#WIZ Help
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Not yet, Pete. Do you think that would matter though? It doesn't even attempt
to read from the /d0 when I run it from the H/D? It just reads from the H/D
then quits and gives me the error.
There are 2 Replies.
#: 15636 S7/Telecommunications
22-Jun-92 11:59:31
Sb: #15632-#WIZ Help
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Bob -
All we know for sure is:
a) It's looking for something that it can't find (for whatever reason)
b) You changed from /d0 to /h0 (and shifted /DD)
c) It does a disk access before the error
I suggest that the following are the most likely causes of the problem:
a) A file or directory that's required is missing from the hard disk
b) An explicit reference to another drive remains
c) You have different startup files that load different things on
the floppy or hard disk.
d) You have different versions of code on the hard disk than on the floppy.
Pete
There is 1 Reply.
#: 15640 S7/Telecommunications
22-Jun-92 19:23:57
Sb: #15636-#WIZ Help
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Pete,
This is what I found last night. I used dEd to search for any d0's,
and had no luck. Then I decided to do a verify, Bingo!! After that, it worked
fine, except the address for the 4in1 serial is different then what is actually
in the special /t2 it uses, but that is just a matter of changing it (I went
from a Slotpak & RS232 to an SCII recently). When I did a cmp of the one on
the H/D and the one I made the copy of from the floppy, there were about 17 bit
chanes???? I didn't do it. Unless dEd changed all of these during the verify,
I don't know what the heck happened. Thanks for your time, and the little
boost in effort that kept pushing to find the problem.
Bob//////
There is 1 Reply.
#: 15644 S7/Telecommunications
23-Jun-92 09:14:45
Sb: #15640-WIZ Help
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Bob -
Sorry I didn't think of CRC's... I had patched my kernel to omit the CRC check,
which made it much faster on a HD based system. This seemed rational, as a
corrupt module would either have shown up with a disk read error, or a not
ready. Also, most corrupt modules (at least in those days) were the result of
xmodem padding, which was implicitly stripped at module load time.
Good fix...
Pete
#: 15638 S7/Telecommunications
22-Jun-92 17:16:40
Sb: #15632-#WIZ Help
Fm: LARRY OLSON 72227,3467
To: BOB LEET 72020,2536 (X)
Another thing you might check is the attributes of the WIZ files and modules
that you transfered to the hard drive. You might be getting hit with a NO
PERMISSION error when WIZ tries to open a file.
Larry
There is 1 Reply.
#: 15641 S7/Telecommunications
22-Jun-92 19:26:02
Sb: #15638-#WIZ Help
Fm: BOB LEET 72020,2536
To: LARRY OLSON 72227,3467 (X)
Thanks Larry. I fixed it though. If you are interested, see the letter I sent
to Pete Lyall on what happened when I fixed it. Pretty strange.
There is 1 Reply.
#: 15798 S7/Telecommunications
06-Jul-92 23:33:38
Sb: #15641-#WIZ Help
Fm: Bob Palmer 74646,2156
To: BOB LEET 72020,2536 (X)
I'm just getting back to read the mail and am glad to see that you have
succeeded in getting your WIZ to fly. I used it (the wizpro variant) as my
telecom program of choice on the COCO for several years and was always happy
with the results. Lately I have had to switch to STERM on my TC70 (and tonight
am using TELIX on a PC because the TC70 is under the weather so to speak) but
would be very happy if there were a WIZPRO for the TC70. Come to think that
should be relatively easy to port given that wizpro is mostly basic09 but the
sources would be required.. Runtime is not going to work until a few addresses
have changed and also the screen work. Interestin project for someone, Bill
Brady has not been about for a while but I do beliwve he had been looking at a
TOMCAT 6809 machineand would bet he will be thinking. Back to your problem -
when you patched your original wizpro to take into account the new addresses -
did you verify the modules? They could have been lurking about - but I don't
know how you were loading them from floppy if that is the case. Hmm - all's
well that ends well . Bob
There is 1 Reply.
#: 15836 S7/Telecommunications
09-Jul-92 02:30:40
Sb: #15798-WIZ Help
Fm: BOB LEET 72020,2536
To: Bob Palmer 74646,2156 (X)
Bob P.,
To tell you the exact story, I never made any changes to anything in
the program. All I did, once I put my HD on the COCO, was to simply copy it to
the HD, and the weird results occurred????? Doo doo dee doo, doo doo dee doo
(Twilight Zone). See ya, Bob//////
#: 15627 S7/Telecommunications
21-Jun-92 13:56:28
Sb: #15610-#WIZ Help
Fm: Bob Palmer 74646,2156
To: BOB LEET 72020,2536 (X)
Did you by any chance have something merged with RUNB before and not now? Has
you bootfile size increased so that now there is not enough room in 64k to get
runb and all of the WIZ files? That's usually the reason for process not found.
If it was not on disk I would have expected a file not found or maybe wrong
attributes.
There is 1 Reply.
#: 15634 S7/Telecommunications
22-Jun-92 00:54:04
Sb: #15627-WIZ Help
Fm: BOB LEET 72020,2536
To: Bob Palmer 74646,2156 (X)
I did not have anything merged to RunB before, since all except it are merged
into the program itself. Yes, I have since changed my bootfile to include a
few more modules for the H/D. But, I did remake the old floppy Boot to contain
these new modules. When I run the old/new floppy Boot, it runs fine when dd is
d0. It seems like it just refuses to run off the H/D.
#: 15631 S7/Telecommunications
22-Jun-92 00:45:59
Sb: #15611-WIZ Help
Fm: BOB LEET 72020,2536
To: Kevin Darling 76703,4227 (X)
This is the original WIZ, which just has the directory COM that holds the
autodial files. It is on the H/D. Also, the program has all that it needs
except RunB, merged in it already. Even still, I have merged all the pertinant
B09 files into a Runb.1, and load it prior to running the program.
#: 15620 S12/OS9/68000 (OSK)
20-Jun-92 22:08:23
Sb: #15615-#Vprint
Fm: Bob van der Poel 76510,2203
To: SCOTT HOWELL 70270,641 (X)
Scott,
Glad to hear that Vprint is working. Yup, ya found a bug...I create some
strings to do the searching for the init file. Unfortunately, by the it gets
down to looking in /h0 my code used strcpy() instead of sprintf()!
Well, that's fixed. So fire your disk in the mail to me and I'll be glad to
update it. In the meantime, you can do one of three things:
1. Set the shell variable VPTDIR to /h0/sys,
2. Set the shell variable HOME to /h0,
3. Load a /dd descriptor which matches /h0.
Sorry about the phone call. That does sound expensive. Hmmm, that was during
prime time, wasn't it? Maybe it's time to check out rates with ATT, etc....
Up to now, we've not had any competition on longdistance phone rates in Canada.
The govt. just changed it's rules and a couple of outfits have been given
premission to interconnect and set up shop. It'll be interesting to see what
happens here with rates--they are much higher than what you are used to paying.
There is 1 Reply.
#: 15622 S12/OS9/68000 (OSK)
21-Jun-92 00:04:54
Sb: #15620-#Vprint
Fm: SCOTT HOWELL 70270,641
To: Bob van der Poel 76510,2203 (X)
Yes, the VPTDIR shell variable sounds good to me. I called MCI and AT&T and
both have about the same rates, but I do not know about the prime time vs. late
night rates. There was a consultant here at work working on software
development on our embedded system (STARIV) from Canada and his rates in
Halifax was much higher than here too. Also when calling your number it seems
that your area (central office) still has analogue switching. thanks scott
howell.
/exit
There is 1 Reply.
#: 15649 S12/OS9/68000 (OSK)
24-Jun-92 02:10:10
Sb: #15622-#Vprint
Fm: Bob van der Poel 76510,2203
To: SCOTT HOWELL 70270,641 (X)
Scott,
Even if the VPTDIR stuff works, do send the disk back anyway--there are some
other buglettes in the version you have.
Hey, how can you tell what kind of switchboard we have here? You are
right--it's an old mechanical thing (even though I'm convinced that at times
they still bring in an old gal who does the connects via phone-plugs). Until
they get a new switch here, I'm unable to tap into nicities like call waiting,
etc. Maybe just as well...my bill is high enuf. But the mechanical relays cause
lots of noice too, at times. It's been on the telephone company's list for
years now. I wonder if the coming deregulation in Canada will hinder or help
these projects?
There is 1 Reply.
#: 15656 S12/OS9/68000 (OSK)
24-Jun-92 09:09:39
Sb: #15649-Vprint
Fm: SCOTT HOWELL 70270,641
To: Bob van der Poel 76510,2203 (X)
the mechanical relays on the rings have a stronger attack than the digital
ones. I know then ATT was broken up into regional bell systems in 1983, many of
the mechanical central offices in Georgia was converted.
I will send the disk soon! thanks
#: 15621 S10/OS9/6809 (CoCo)
20-Jun-92 22:08:33
Sb: #15618-AIFs
Fm: Bob van der Poel 76510,2203
To: Kevin Darling 76703,4227 (X)
Oh, is that what they mean by .xxx. Never occurred to me that .xxx meant three
characters.... Darn, sometimes I wonder why I even turn the computer on, let
alone doing work on it!
#: 15623 S12/OS9/68000 (OSK)
21-Jun-92 12:03:46
Sb: #15560-#MM/1 RBF Bug
Fm: Jim Peasley 72726,1153
To: Bob van der Poel 76510,2203 (X)
Bob;
Booting from /d0 and finishing from /dd (HD), accessing an empty /d1 does NOT
cause any errors on my system.
RBF Ed.#79 and descriptors are all Ed.#11.
...Jim
There is 1 Reply.
#: 15650 S12/OS9/68000 (OSK)
24-Jun-92 02:10:19
Sb: #15623-#MM/1 RBF Bug
Fm: Bob van der Poel 76510,2203
To: Jim Peasley 72726,1153 (X)
This makes no sense. You're the 2nd person who reports no errors. So far, I'm
the only one reporting errors. Funny thing is that I got the errors when I
still had my single board proto system--so I'm wondering if there is something
with my hardware causing the problem? I've got a 3.5" Hitachi and a 5" CDC. No
terminator resistor--I tryed installing one and found that the system would not
access the 3" drive when I added one. Also, if I take the 5" out of the system,
I still get the error if I try just accessing the non-existant drive, so I
sort-of doubt that it is hardware. Anyone?
There are 2 Replies.
#: 15653 S12/OS9/68000 (OSK)
24-Jun-92 08:21:14
Sb: #15650-#MM/1 RBF Bug
Fm: Mark Griffith 76070,41
To: Bob van der Poel 76510,2203 (X)
Bob,
I have never heard of a problem like what you mentioned. Perhaps you should
post CRCs for the modules in question (RBF, 33C93, d0, d1, etc) and see if that
is the cause. Other than that, I'd say you have a hardware problem.
Mark
There is 1 Reply.
#: 15704 S12/OS9/68000 (OSK)
29-Jun-92 20:55:00
Sb: #15653-#MM/1 RBF Bug
Fm: Bob van der Poel 76510,2203
To: Mark Griffith 76070,41 (X)
Mark, Well, it (the crashing of floppies) is definitely a bug here on my
system. If it is a hardware bug, where do you suggest I look. Remember, this
same bug was present on my proto (single board) system. At the time I just
figured it was the software... At this point the only things the same are the
3.5" floppy (and the case).
Here are the current drivers I'm using:
d0 #14 crc - 998410
d1 #14 crc - BA83F3
rb37c65 #4 crc - 1768E9
rbf #79 crc - F098AF
For hardware, I have 3.5" floppy and a 5" 80 track. I've disconnected the 80
and still get the same results. Just to refresh the debate, here is how to get
the bug:
1. boot normally (I do it from the 3.5" and the process continues on /h0),
2. attempt to access /d1 with the drive door open (dir /d1 "works" fine),
3. after an error is generated, attempt to access /d0 (again, do something
like dir /d0)--at this point I get an error!
With no disk in d1 the light on d0 flashes after 5 seconds, then the error is
reported after another 5 secs. If I remove the drive completely, the error is
reported right after the flash.
However, if you do an access to /d0 before all this (again, dir /d0 works)
everything appears to work okay.
BTW, I don't have a terminator on /d1. I put one on to test things, but then
the 3.5 became unaccessable, even for the boot process.
There are 2 Replies.
#: 15713 S12/OS9/68000 (OSK)
30-Jun-92 09:48:32
Sb: #15704-#MM/1 RBF Bug
Fm: Mark Griffith 76070,41
To: Bob van der Poel 76510,2203 (X)
Bob,
Well, you had this bug in your prototype system, then I would think it might be
the cable or the dirve itself. I have not been able to reproduce this on my
system, nor have I heard of anyone else having this problem.
The terminating resistor may or may not be a problem. Some drives need to have
them and some don't. When you mix drives, you run into the problem of either
both drives need them, neither do, or one or the other do before you get
reliable results. The only other answer might be you are running a different
version of RBF or the floppy drivers. Check that all out (with the CRC) and
see what they are.
Mark
There is 1 Reply.
#: 15731 S12/OS9/68000 (OSK)
01-Jul-92 20:46:51
Sb: #15713-#MM/1 RBF Bug
Fm: Bob van der Poel 76510,2203
To: Mark Griffith 76070,41 (X)
Well, Mark, I did post the CRC's in my last message. I assume that they are the
latest. I did detatch the 5" drive completely, and still got the error. So I
guess that leaves the cable or the 3" drive. Sounds pretty unlikely to me that
either one could be causeing this weird problem. However, I will try a new
cable one of these days. Will the mm/1 boot from a 5" drive? Just a matter of
making a boot disk? If it's that easy I could pull the 3" drive and see if
that's causing the problem.
There is 1 Reply.
#: 15747 S12/OS9/68000 (OSK)
02-Jul-92 09:09:28
Sb: #15731-#MM/1 RBF Bug
Fm: Mark Griffith 76070,41
To: Bob van der Poel 76510,2203 (X)
Bob,
If you did post CRCs then I didn't see them. Maybe you can post them again, or
the Sysops here can go back and find that message and point me to it (hint hint
Steve).
It is very possible that the cable can be causing your problem, or the 3.5 inch
drive. If you have any other drives to try, then you should do that and see
what happens. As for booting from a 5.25 inch drive, OS-9/OSK doesn't care
what the drive type or size is. All it looks for is the LSN0 data which points
it to the sector where the bootfile is. Then it just issues a seek command to
get to that sector and it starts to read. Of course, OSK Ver 2.4 can now bring
in a bootfile that is fragmented, but older versions and OS-9 can't. The long
and the short of it is--if you can make a bootfile on the disk, it can be
booted from that disk.
I always make my boot disks on an Atari formatted disk cause I don't like to
use up a HD disk just to hold the bootfile. I have also been able to boot from
a Universal format and a CoCo format disk.
Mark
There is 1 Reply.
#: 15749 S12/OS9/68000 (OSK)
02-Jul-92 10:28:36
Sb: #15747-#MM/1 RBF Bug
Fm: Steve Wegert 76703,4255
To: Mark Griffith 76070,41 (X)
Mark,
I checked Bob's CRC's against mine .... he's up to the current revisions.
Steve
There is 1 Reply.
#: 15759 S12/OS9/68000 (OSK)
03-Jul-92 06:55:55
Sb: #15749-MM/1 RBF Bug
Fm: Mark Griffith 76070,41
To: Steve Wegert 76703,4255 (X)
Thanks Steve.
#: 15771 S12/OS9/68000 (OSK)
03-Jul-92 22:15:10
Sb: #15704-#MM/1 RBF Bug
Fm: Carl Kreider 71076,76
To: Bob van der Poel 76510,2203 (X)
I'm coming in late, but what the hey. The crc's for rbf and rb37c65 are good,
the ones for d0 and d1 probably don't matter. Booting from a 5.25" is not a
problem. The roms don't really care. This is *seriously* wierd. I wish I had
an answer.
Carl
There is 1 Reply.
#: 15849 S12/OS9/68000 (OSK)
09-Jul-92 20:21:44
Sb: #15771-#MM/1 RBF Bug
Fm: Bob van der Poel 76510,2203
To: Carl Kreider 71076,76 (X)
Carl,
I was speaking to Zack Sessions last night, and he has similar problems with
his mm/1 when he tries to read a coco disk in a HD drive, or something. He
wrote a short program which does a _ss_rset() to the device and this seems to
clear things up. Don't know if related. I sent him some of this thread and he
will post it on the other net and has promised to let you know what's up. Gotta
be a bug <grin>!
There is 1 Reply.
#: 15851 S12/OS9/68000 (OSK)
09-Jul-92 22:42:06
Sb: #15849-MM/1 RBF Bug
Fm: Carl Kreider 71076,76
To: Bob van der Poel 76510,2203 (X)
Hey, I will buy into the possibility of a bug ;). I just need a way to
duplicate the problem so I can find it.
#: 15787 S12/OS9/68000 (OSK)
05-Jul-92 13:36:20
Sb: #15650-MM/1 RBF Bug
Fm: Eric Crichlow 71051,3516
To: Bob van der Poel 76510,2203 (X)
Bob,
I haven't been online for awhile (don't get on but once a week) so I don't
know if you've solved this problem yet, but I just thought I'd let you know
that you're not alone. I believe I've seen the same problem that you're
describing on my system, only I THINK it only ocurred here after using the
reset button to reboot the system. Then /d1 was totally unfunctional. As I
remember, rebooting by turning the system off for a few seconds then back on
always solved the problem.
I hadn't seen the problem in quite awhile, but strangely enough it happened
just before I was getting ready to write this reply!
Go figure.
If you figure anything out about this let me know.
..Eric...
#: 15624 S12/OS9/68000 (OSK)
21-Jun-92 12:09:31
Sb: #Windows edition?
Fm: Jim Peasley 72726,1153
To: Kevin Darling
Kev;
I've seen references to the window driver edition #42. The one in the
upgrade disk is #38. Is there another, later edition posted somewhere?
Also, any docs available?
thanks,
...JIm
There is 1 Reply.
#: 15625 S12/OS9/68000 (OSK)
21-Jun-92 13:05:48
Sb: #15624-Windows edition?
Fm: Kevin Darling 76703,4227
To: Jim Peasley 72726,1153 (X)
Hi Jim - printed docs are still in the works; a bare reference should've been
on the upgrade disk (?).
Some people at the fest snarfed v41. V42 will be uploaded here pretty soon
with minor fixes/features derived from v41 feedback. Then the cycle will start
again :-)
thanks - kevin
#: 15626 S1/General Interest
21-Jun-92 13:48:07
Sb: #15596-#Drive help
Fm: Bob Palmer 74646,2156
To: Hugo Bueno 71211,3662 (X)
You will probably find what looks like a DIP socket with a "chip" containing 8
links in it. the links for 1 2 & 3 need to be severed and 0 made for this to
be a drive 0. If I remember rightly the board will have lables beside the plug.
Somewhere around here I have the appropriate book for Tandon drives so if this
is not enough (and if you can be patient enough for my next log on) I'll dig it
out. By the way - no need to buy a new link chip if the pin 0 is cut - just
turn it around end for end. I don't think number 8 is of any consequence to
the Tandon. - this is a single or double sided disk? Bob
There is 1 Reply.
#: 15647 S1/General Interest
23-Jun-92 20:19:19
Sb: #15626-Drive help
Fm: Hugo Bueno 71211,3662
To: Bob Palmer 74646,2156 (X)
Thanks for the reply Bob. I ended up ordering a real drive. The system gave
me a scare when it didn't work with the new drive. It did work eventually, so
maybe I have a bad cable. Now that my HD is up and running again, I don't
worry too much about the floppies.
Hugo
#: 15628 S14/misc/info/Soapbox
21-Jun-92 14:01:18
Sb: #15613-I Give Up
Fm: Bob Palmer 74646,2156
To: Mike Knudsen 72467,1111
Mike - did I hear you say that the new Ultimuse will run on the TC70 already?
or is that soon? HmW@has it gone about getting a midi port? This from a TC70
owner who is an occasional user of Ultimuse and a Yamaha PSS480. Very slick
program on the coco should be even slicker on the faster hardware. Bob
#: 15629 S1/General Interest
21-Jun-92 17:13:26
Sb: #15588-HAM LICENSE
Fm: DOUG 72667,1433
To: Wayne Day 76703,376 (X)
Congratulations also, Keith.. Have been licensed for 27 years... welcome to the
fun. Hope to see you on packet or some of the other digital modes.
Doug WA4UNS
#: 15630 S12/OS9/68000 (OSK)
21-Jun-92 21:26:28
Sb: #15593-MM/1 Mouse
Fm: GLEN HATHAWAY 71446,166
To: Steve Wegert 76703,4255 (X)
Hi Steve... True. Hmmm...
#: 15633 S10/OS9/6809 (CoCo)
22-Jun-92 00:52:33
Sb: #PCDOS
Fm: Ian Hodgson 72177,1762
To: All
Exists there a patch for the Disto no halt driver to allow it to work with
PCDOS? I am tired of having to keep switching to SDISK (and, in the process,
each time I want to transfer a file.
There is 1 Reply.
#: 15643 S10/OS9/6809 (CoCo)
22-Jun-92 21:27:03
Sb: #15633-#PCDOS
Fm: Erich Schulman 75140,3175
To: Ian Hodgson 72177,1762 (X)
The Disto driver is very different from the patch you've used on the usual
driver. I have never seen a patch such as you described. On my system I tried
using the Disto driver as though it were patched and it worked fine, not only
for PCDos but also RSDos. Try using the Disto driver as it is on disks with no
critical data on them and see if it works reliably on your system too.
Erich Schulman (KTN4CA)
There are 2 Replies.
#: 15662 S10/OS9/6809 (CoCo)
24-Jun-92 22:49:23
Sb: #15643-#PCDOS
Fm: Ian Hodgson 72177,1762
To: Erich Schulman 75140,3175 (X)
Erich,
I had already tried using the Disto no-halt driver as-is with PCDOS, but tried
it again just to be sure, with the same result. Any attempt to access a DOS
diskette with PCDOS simply results in the message "Not a DOS diskette".
Switching to SDISK corrects the problem, but leaves me without buffered I/O on
the drives. Odd that yours should work OK and mine not, though.
Ian
There are 3 Replies.
#: 15663 S10/OS9/6809 (CoCo)
25-Jun-92 01:00:24
Sb: #15662-#PCDOS
Fm: Erich Schulman 75140,3175
To: Ian Hodgson 72177,1762 (X)
Try one more time using the Disto driver, but this time use a 360K DOS disk
with no more than 1-2 files totaling no more than 100K in size. Regardless of
driver I have had a great deal of difficulty using PCDos with DOS disks
exceeding these numbers. For a 720K disk, the limit seems to be 1 file no
larger than 100K. I asked about this problem in this Forum last year and no
one came up with an answer, and I haven't figured it out either. Also be sure
you have at least 32K free memory before you load PCDos (even more is better).
I've had problems with it when less memory was free.
There is 1 Reply.
#: 15780 S10/OS9/6809 (CoCo)
04-Jul-92 07:59:39
Sb: #15663-PCDOS
Fm: Mike Guzzi 76576,2715
To: Erich Schulman 75140,3175 (X)
I have used PCDOS with 720K disks and it was full and I had no problems. I am
using Sdisk3 made for the DMC controller. I have not tried it with the patched
cc3disk (for normal controllers)
Mike
#: 15721 S10/OS9/6809 (CoCo)
01-Jul-92 16:30:49
Sb: #15662-#PCDOS
Fm: Lee Veal 74726,1752
To: Ian Hodgson 72177,1762 (X)
I've heard of others using the no-halt drivers (Disto's, that is) with PCDOS. I
use Sardis No-Halt controllers with SDISK3, so I don't encounter the problems
that you're facing. However, there are folks in my CoCo Group here that have
used PCDOS successfully with the DISTO No-halt drivers.
Lee
There is 1 Reply.
#: 15739 S10/OS9/6809 (CoCo)
02-Jul-92 00:36:11
Sb: #15721-#PCDOS
Fm: Brother Jeremy, CSJW 76477,142
To: Lee Veal 74726,1752 (X)
I use PCDOS with the Disot SC-2 with out any problems. Just remember, if it is
a file other than an ASCII file, use PCDOS-raw -get or utils suck as UNZIP will
not work. I came in late so perhaps this thread has already addressed thjis,
but any problems that I ever encountered with PCDOS was due to my failure to
use the -raw command. --Br. Jeremy, CSJW
There are 2 Replies.
#: 15740 S10/OS9/6809 (CoCo)
02-Jul-92 00:36:58
Sb: #15739-PCDOS
Fm: Brother Jeremy, CSJW 76477,142
To: Brother Jeremy, CSJW 76477,142 (X)
Sorry for the misprint, of course that should be DISTO SC-2. --Jeremy.
#: 15743 S10/OS9/6809 (CoCo)
02-Jul-92 08:53:00
Sb: #15739-PCDOS
Fm: Lee Veal 74726,1752
To: Brother Jeremy, CSJW 76477,142 (X)
Hi! Bro!
I think maybe you replied to the wrong person. I wasn't having problems with
Disto SC-2 (since I don't own one). There were some other folks that I was
responding to that were however having problems trying to get the SC-2 drivers
to work with PCDOS. It could be something as simple as trying to access a
double sided diskette on a single-sided drive. Who knows.
My response was simple to add a comment that I knew of some folks in our club
that use DISTO SC-2 successfully with PCDOS.
Lee
#: 15797 S10/OS9/6809 (CoCo)
06-Jul-92 15:15:09
Sb: #15662-PCDOS
Fm: Lee Veal 74726,1752
To: Ian Hodgson 72177,1762 (X)
There's a guy down here in Dallas, that has had to resort to basically the same
thing. That is, if he wants to use his system to read PC-created diskette,
then he reboots with a patched CC3Disk, but in this mode his No-Halt feature is
not in use. When he boots with his Disto-supplied drivers, he has the No-Halt
features, but he can't read PC-DOS diskettes. I'm still waiting to hear from
one other guy down here to see what his solutioin is, but right now it don't
look too good.
Lee
#: 15677 S10/OS9/6809 (CoCo)
25-Jun-92 21:47:25
Sb: #15643-#PCDOS
Fm: Paul Rinear 73757,1413
To: Erich Schulman 75140,3175 (X)
Which Disto driver works with PCdos ? .irq or .slp ? Neither of them work
for me. I also have a separate disk I boot with when I want to use PCdos. I've
since given up on PCdos and just connected my COCO serially to my AST286. The
COCO sends files fine at 19.2 kbaud and receives them reliably at 4800 baud.
Paul Rinear KB2JWM
There is 1 Reply.
#: 15679 S10/OS9/6809 (CoCo)
25-Jun-92 22:40:21
Sb: #15677-PCDOS
Fm: Kevin Darling 76703,4227
To: Paul Rinear 73757,1413 (X)
Right - none of the Disto SC-II drivers work with PCDOS... you have to make a
separate boot disk with the modified RS driver.
#: 15635 S15/Hot Topics
22-Jun-92 00:59:57
Sb: #6309 & /t2
Fm: BOB LEET 72020,2536
To: all
Have you heard of any others having trouble with the 6309 locking up the /t2?
Me and another member of the Phoenix Coco Club are experiencing this problem
since we installed the 6309. It is not the booster program, as I have run
terms w/ & w/o the patches, all of which have the effect, crapping out!
There is 1 Reply.
#: 15637 S15/Hot Topics
22-Jun-92 12:01:21
Sb: #15635-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Bob -
What speed are you running at? 3Mhz? IS the 6551 rated to provide service at
that rate, if so?
Pete
There are 2 Replies.
#: 15642 S15/Hot Topics
22-Jun-92 19:31:14
Sb: #15637-#6309 & /t2
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Pete,
The only thing is, it usually runs fine for a while, then just locks up
for no apparent reason. I does it quite frequently during d/ling, which
present quite a problem. I have only found it locking up once on a menu screen
of a BBS.
I was under the understanding that the 6309 only effected the modules
that were patched, and there abilities to use the extra register W. I do not
think the processor is actually faster.
Bob//////
There is 1 Reply.
#: 15645 S15/Hot Topics
23-Jun-92 09:20:02
Sb: #15642-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Bob -
Locking up after a period is an indication of overheating (or mismatched speed
rating). I used to have some EPROMS that acted like that... fine for 20 minutes
or so, then wham.
I'm not sure what the 4in1 uses for serial port chips (Steve Wegert may), but
you may want to verify that their 6551's are rated for proper speed a
coco3/1.87MHZ clocking. Also, are you using an IRQ hack line for your
interrupts? If not, this may buy you some solidity... see IRQHAK.TXT in
DL(1?)...
Pete
There is 1 Reply.
#: 15646 S15/Hot Topics
23-Jun-92 19:11:06
Sb: #15645-#6309 & /t2
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Pete-
I have since removed the Slotpak, and just have the SCII directly
plugged into the computer. That is, since I got the SCII & 4-in-1. So, I
don't have a hacked IRQ.
I found the computer locked up today in about 10 minutes, while using
Supercomm. The other day I was d/ling a 560k program, and got about 360K
before it crapped out. So, I think the heat problem is out. I believe the
4in1 uses the 6551a chips. Do you think this still may be the problem?
Bob//////
There are 2 Replies.
#: 15648 S15/Hot Topics
23-Jun-92 21:13:17
Sb: #15646-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Install the IRQ hack.
On the side, how do you arrive at "the heat problem is out"?
Pete
There is 1 Reply.
#: 15776 S15/Hot Topics
04-Jul-92 02:31:24
Sb: #15648-#6309 & /t2
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Pete,
I am trying to rule out the heat problem, since the WIZ is doing just
fine now. It has its own descriptor M2W, and isn't locking up now. Also, I
have had the computer on for about 10 minutes and then the t2 will lock up,
then I have had it on for 50 minutes and the t2 locks up.
Wouldn't the t2 lock-up about the same time every time?? If
overheatingwere the problem.
-Bob//////
There is 1 Reply.
#: 15782 S15/Hot Topics
04-Jul-92 11:07:26
Sb: #15776-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Not necessarily.... is the room ambient temerature always the same? Are you
always running the same code in similar sequence?
Suggestions:
o - Install IRQ hack o - Throw heat sinks on UART chips o - Put a fan in the
area (better yet, put a muffin fan on the box) o - Take the system apart and
reseat/clean everything
Also, is there any special reason you're using WiZ? I recall in the early days
that folks had nothing but trouble with it, and it was VERY hardware specific
(i.e. hardwired code). It required several iterations to get it working
properly. Perhaps something vanilla such as Xcom9 or Sterm is a better choice
until you get the problem resolved.
Pete
There is 1 Reply.
#: 15795 S15/Hot Topics
06-Jul-92 02:31:04
Sb: #15782-#6309 & /t2
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Pete,
I am using WIZ because it is reltively simple, and I have not had any
problems since I set it up a year ago.(barring my recent errors)
I am going to try the SACIA before I try to cool or clean. My COCO
can't be that dirty anyhow, I have had a cover on it the past 3 years and take
it apart often.
Thanks, Bob//////
There is 1 Reply.
#: 15796 S15/Hot Topics
06-Jul-92 08:51:26
Sb: #15795-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536 (X)
Bob -
It's not DIRT that's the concern... it's OXIDATION. Radio Shack, in their
dubious wisdom, used cheap (tin?) contacts on all of their 'pak' products, and
just air and moisture are enough to cause problems.
Pete
There are 2 Replies.
#: 15811 S15/Hot Topics
08-Jul-92 00:39:37
Sb: #15796-#6309 & /t2
Fm: randy pischke 75460,205
To: Pete Lyall 76703,4230 (X)
Pete- I received my 6309 in the mail today and installed it. When I tried to
download from CIS at 2400 my /t2 locked up. My coco is always covered when not
in use so is spotless inside. I have had a muffin fan in my coco for about 6
months now so cooling isn't a problem. I feel the problem is software related.
Specifically to the Powerboost software. The com program I am using is Sterm,
so your recommendation to Bob to use it won't help. Another problem I have
encountered after upgrading (not sure if that is a good term at present) is
that when I use Mmulti-vue I get vertical "ghost" lines appearing on the top
half of the screen. The lines are linked to the mouse pointer. As the pointer
moves up the lines move up and vise-versa. My coco worked perfectly before the
socalled upgrade. Any other ideas!! :-(
There are 3 Replies.
#: 15813 S15/Hot Topics
08-Jul-92 02:49:11
Sb: #15811-#6309 & /t2
Fm: Kevin Darling 76703,4227
To: randy pischke 75460,205 (X)
Randy - perhaps something got flexed during installation of the 6309. Have you
tried the usual tapping or cleaning of the GIME? Did you reinstall the bottom
circuit board shield (and make sure there were no metal shavings)?
Did you install a socket (I hope!)? If so, do you have a 6809 you could stick
in to see if it still works okay that way?
kev
There is 1 Reply.
#: 15823 S15/Hot Topics
08-Jul-92 19:05:18
Sb: #15813-6309 & /t2
Fm: randy pischke 75460,205
To: Kevin Darling 76703,4227 (X)
Kevin-
There weren't any shavings from the transplant. Yes, the shield plane is
installed. I did socket the CPU for ease of replacement in the future. I will
try 2400 baud again just to ensure that it wasn't caused by a bad phone line.
If all else fails I just may have to go back to the 6809.
Thanks Randy.
#: 15817 S15/Hot Topics
08-Jul-92 08:56:50
Sb: #15811-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: randy pischke 75460,205 (X)
Yeah - go back to the 68B09!
On the T2 issue.... are you running the IRQ hack? That really does make a big
difference.
The ghosting... hmmm. I'm not familiar with powerboost, but I do remember that
the 6309 could be clocked at 3Mhz... Has the effective rate been bumped up? Are
they doing the old 'manual video refresh'?
Pete
There is 1 Reply.
#: 15824 S15/Hot Topics
08-Jul-92 19:09:25
Sb: #15817-#6309 & /t2
Fm: randy pischke 75460,205
To: Pete Lyall 76703,4230 (X)
Pete- I have no idea what the IRQ hack consists of. Could you enlighten me. I
also don't know any details for the Powerboost software either. Strangely,
today I don't have the faint 'ghosting' vertical lines. It is really weird.
I'll try 2400 baud communications again and see if it still hangsup.
-Randy
There is 1 Reply.
#: 15827 S15/Hot Topics
08-Jul-92 21:22:29
Sb: #15824-#6309 & /t2
Fm: Pete Lyall 76703,4230
To: randy pischke 75460,205 (X)
Randy -
See IRQHAK.TXT in DL2... It physically connects the 6551's IRQ line to the
6?09's IRQ line, which avoids some of the pass through problems associated with
the hardware in the middle.
Pete
There are 2 Replies.
#: 15828 S15/Hot Topics
08-Jul-92 21:24:52
Sb: #15827-6309 & /t2
Fm: Pete Lyall 76703,4230
To: Pete Lyall 76703,4230 (X)
Whoops ... make that DL10.
Pete
#: 15853 S15/Hot Topics
10-Jul-92 01:06:04
Sb: #15827-6309 & /t2
Fm: randy pischke 75460,205
To: Pete Lyall 76703,4230 (X)
Pete-
I have installed Carl Bennett's internal RS-232 port from May 1989
Rainbow.The port is completely hard wired so no MPI problems. I put my 6809
back in and the vertical 'ghost' lines went away. They only appeared on white
backgrounds in hi res mode. This indicates a defective 6309 to me. It might
have caused the t2 lockup if it has that kind of effect on my display. (Make
any sense to you?) I appreciate the help. Will give Burke & Burke a call
tomorrow.
Randy.
#: 15842 S15/Hot Topics
09-Jul-92 09:11:49
Sb: #15811-#6309 & /t2
Fm: Mark Griffith 76070,41
To: randy pischke 75460,205 (X)
Randy,
Your problem is probably due to the powerboost code and your serial port drives
not being too happy with each other. I believe a few people over on the lesser
service (starts with a "D" - grin) were having similar problems. Don't know
what the wanswer was, if there was one. Hmmmm, I think something was said
about using Bruce Isted's SACIA driver. In any case, it is not Sterm that is
causing the problem.
Opps...that should be "serial port drivers" above. Sorry.
Mark
There is 1 Reply.
#: 15855 S15/Hot Topics
10-Jul-92 01:21:13
Sb: #15842-#6309 & /t2
Fm: randy pischke 75460,205
To: Mark Griffith 76070,41 (X)
Mark-
I am using a stock /t2 driver except for a patch to the address for the
port to work with the internal RS-232 port mod from May 1989 Rainbow. When I
tried 2400 baud yesterday it worked without a problem. Now I don't know if it
was a freak occurance from something I did or if there is really a problem. My
'ghost' line problem is getting worse though. This problem goes away when I put
the 6809 back in so it seems to indicate a bad CPU. Can't think of anything
else that would cause it. I used the same boot disk without Powerbooster
installed to test the CPUs. It was very consistant. I appreciate your input as
to what my system problems could be from. The more ideas I get, the better my
understanding of how the system works.
Many thanks to everyone on their input. Randy
There is 1 Reply.
#: 15858 S15/Hot Topics
10-Jul-92 15:07:31
Sb: #15855-#6309 & /t2
Fm: Mark Griffith 76070,41
To: randy pischke 75460,205 (X)
Randy,
What 'ghost line' problem are you having? If you are refering to a double
image problem, perhaps it is due to a slight change in horizontal sweep
frequency due to the change in the CPU. Hmmmmm...maybe not, that should be
taken care of by the GIME. But then again, the sparklies problem could be
taken care of by changing the CPU, still a 68B09 just a difference
manufacturer. I fixed mine by installing an AMD chip.
Strange.
Mark
There is 1 Reply.
#: 15911 S15/Hot Topics
15-Jul-92 01:39:37
Sb: #15858-#6309 & /t2
Fm: randy pischke 75460,205
To: Mark Griffith 76070,41 (X)
Mark-
I get these ghost vertical lines when I amon a high res screen that has a
white background and the mouse pointer is active. As I move the pointer up and
down the lines follow. With the pointer at the bottom right corner of the
screen the lines cover the top 3/4 of the screen. When the pointer is moved to
the top of the screen, the lines are gone. I am using GSHELL+ and when I press
'S' for a shell window, the lines also go away. They do come back when I close
the shell window though. The lines also get worse the longer my system is
running. It takes about 5 minutes for them to even show up. As I mentioned
earlier, I do have a muffin fan in my computer and when I put my 6809 back in
the lines never show up. It has to be a wierd 6309 since that is the only thing
that I changed. There is no reasonable explanation.
Randy.
There is 1 Reply.
#: 15913 S15/Hot Topics
15-Jul-92 09:56:59
Sb: #15911-6309 & /t2
Fm: Mark Griffith 76070,41
To: randy pischke 75460,205
Randy,
Sounds logical to me!
Mark
#: 15835 S15/Hot Topics
09-Jul-92 02:25:14
Sb: #15796-#6309 & /t2
Fm: BOB LEET 72020,2536
To: Pete Lyall 76703,4230 (X)
Pete,
Your absolutely right about the cheap tin. Come to find out, that it
was just the clock module causing all our Lock-up problems. At least as far as
me and another guy can tell. He just gave the new clock module at our Phoenix
COCO Club meeting earlier this evening. So far, 2 hours and counting, now
lock-ups. Thanks for all your input.
Thanks, Bob//////
There is 1 Reply.
#: 15841 S15/Hot Topics
09-Jul-92 08:49:13
Sb: #15835-6309 & /t2
Fm: Pete Lyall 76703,4230
To: BOB LEET 72020,2536
Great.. glad it was simple (as hoped). That's one of the more disappointing
things about the coco family... It wasn't very robust. Every now and then it'd
lock up in the middle of a term paper, the world's greatest C program, or
whatever because of the oxidization.
Pete
#: 15655 S15/Hot Topics
24-Jun-92 09:04:12
Sb: #15646-#6309 & /t2
Fm: Steve Wegert 76703,4255
To: BOB LEET 72020,2536 (X)
Bob,
I concur with Pete, install the IRQ hack.
What happens if you attempt to use Supercomm at a slower baud rate? Any lock
ups?
Steve
There is 1 Reply.
#: 15775 S15/Hot Topics
04-Jul-92 02:20:15
Sb: #15655-#6309 & /t2
Fm: BOB LEET 72020,2536
To: Steve Wegert 76703,4255 (X)
When using it at 1200 & 2400 both, the t2 will lock up.
I am going to ask a couple of other people that are having the problem, if they
have the IRQ hack. If that is the case, it must be in the t2 decriptor.
What realy gets me, is now that the WIZ is working okay, its descriptor isn't
locking up (M2W). So, it must not be the 6551 chips.
Bob
There is 1 Reply.
#: 15781 S15/Hot Topics
04-Jul-92 08:04:03
Sb: #15775-#6309 & /t2
Fm: Mike Guzzi 76576,2715
To: BOB LEET 72020,2536 (X)
I would suggest replacing ACIAPAK with SACIA and the T2 thats in the archive I
used to have problems with some lock ups and lost chars (even though I have an
IRQ hack) but once I replaced the drivers it works great. even supercomm can
handle 9600 baud ok now. where with aciapak it lost characters all the time
SACIA is in the eliminator package available here.
There is 1 Reply.
#: 15794 S15/Hot Topics
06-Jul-92 02:10:59
Sb: #15781-6309 & /t2
Fm: BOB LEET 72020,2536
To: Mike Guzzi 76576,2715 (X)
Thanks for the advice.
See ya, Bob//////
#: 15763 S15/Hot Topics
03-Jul-92 10:15:08
Sb: #15637-6309 & /t2
Fm: Fred Carter 76646,3172
To: Pete Lyall 76703,4230 (X)
Hi Bob:
If you were to design your own 6309 computer you could use a 12 MHz clock
which woul generte a 3ec Bs rate almos doubl that o the COO-3. I
6809 mode, he 630 acts just ike a 680cept that t uses lss power an
hence geneates lss heat h may be jhat yor COCOneeds!).
Regards,
Fred Carter (7,317)
#: 15639 S1/Geneterst
22-Ju-92 17
Sb: #15581-teac drve help
Ke Drexlr 7512,3427
To: Tom 6645 (X)
Thaks for he repst. It muc easiero red. (I dd fiure ou therier
version.) I am tilling to gt my cotroller trk wih the rive bt
your sagegave m a bigstep frwar.
Ken
#: 15652 S12/OS9/8000 (OSK
24-Jun-92 07:5:31
Sb: #MM/1 problems Fm: Bill Dhaus 70325,23
To: all
Help! A couple o week ago started geting the fllowing rs when I booted my MM/1:
*** cio traphandle mismach *** **** can't istall thanler ***
These messages are diplayed whe the startp file tris to lad somdules. If I turn te MM/1 off wait a litt while, and turnit back o, all s back to noral. Ths was on hapening out o 5 or ti duing bot, and neer
anyr time. 've had nootherems or sysem "werdnes", ande been using ita lot
It ts wore.....when tried to bot my M/1 last nght, I got he mssage:
Error: s stat excepion; vetor #$0008 t addr 4EF0002
Then it tries to reboot,after tsge "-- SystemReset<--". Idiscoered
that ifI unplgged y keybard, could ge thi point,all the wa to
the startup fi ut then the co errrs, mos, but n f the tie. I
actually goo boo all the ay once or (but ith no keboard plgged
Setup is MM/1 withI/O board,f memorye 31/2 HDfloppy Seagae 157N
HD, T0 (modem), T(CoCo, Loitechmouse, atestserial river, windos
v38......ad a crppy keboard :- Anybodye an is?
Bll
There are 4 Rees.
#: 15654 S12/OS9/6OSK)
24-Jun-92 08:23:b: #1552-#MM1 probems
FMark riffith 7070,41
To:ll Dckhaus 0325,53 (X)
Bill,
Doyou tr to lod the ath ad cio tra libraries wen you boot? o, mae
sure your versions o drivers fo the mous, keyboar, and eveything lse is
orect oes forthe winio verion youhave. Kevin cangedmost o them
for each ver so you ay have a ismatch thre.
Mark
There is 1 Reply.
#: 15661 S12/OS800 (OSK)
24-Jun-92 22:3835
Sb: #1565-#MM/1problemsm:Bill haus 7025,523
To: MaGriffih 76070,41 X)
Ma
I thought of hat, oo.e tred to boo from the 3 diskI got with
the MM/1, a ddn't wrk, eiher. Im wondring his is't al tiedto a
bad keyboard.I want to gt a betterone anyway so I'm ging t forone
over th next ouple f day. Any ecomendtionson a goodquality keyoard?
There is 1 Reply.
#: 15665 S12/OS9/8000 (OK)
2-Jun-92 0942:04
Sb: 1#MM/1 problms
Fm: Mark Griffith76070,41 To: Bill Dickhaus 7035,523 X)
Bill
It is possile I uppose The oot seuencesends n init to th keybard, bt
I donkno if itlooks or anyhingg back. I do't thik it dos
you can boot withoutboard nstalled. Maybe theare ging bad sice
math and cio a n there?? Just athought.
Mark
There are 2 Repes.
#: 15668 S12/OS9/68(OSK) 25-Jun-92 1:44
Sb: #15665-M/1 probleFm: Bill Dckhaus70325,23
Toark Giffth 76070,4 (X)
Mark,
I nevertried to boo withou the kyboard so I idn't now fr sureif it
would. So maye it h roms ging ba, plus he possiility thatthe
keyboard beingbad is cin the newer roblem.
Bill
#: 15676 S12/OS9/6800 (OSK)
25-J92 2:24:1
Sb: #15665-#MM/1 prblems
Fm: Bill Dickaus 70325,523
o: ark Grffith 7070,41 )
Mark (and Kevn),
The "systm stat extion was cused bythe keyboard. Ifound tht when I
turnedthe keyboa upide don I din't ge the errr. I hecked ver th
keyboard, ky by ,and fund tht the 0INS ky on te keypd wa a little
lower than a thers, takng the keycap off soved t problehis
keyboard is desined fordumpser! :-).
I still the trap handler errors almost every time I boot. I am beginning to
think you are right about the roms, if I power the system down, boot, and if it
fails, try, try, again, it eventually works.....and keeps on working until I
boot again..
Bill
There is 1 Reply.
#: 15678 S12/OS9/68000 (OSK)
25-Jun-92 22:39:29
Sb: #15676-#MM/1 problems
Fm: Kevin Darling 76703,4227
To: Bill Dickhaus 70325,523 (X)
Bill,
Ah yes... if a key is down during boot, you get an error. Dunno why...
Have you tried a different diskette for the boot, btw? I know it doesn't sound
related (and probably isn't), but you never know. The two times that I
couldn't get a boot to work it turned out that reformatting solved it. Again
tho, this doesn't sound like the case for you, but thought I'd mention it.
There is 1 Reply.
#: 15684 S12/OS9/68000 (OSK)
26-Jun-92 13:45:48
Sb: #15678-#MM/1 problems
Fm: Bill Dickhaus 70325,523
To: Kevin Darling 76703,4227 (X)
{Kevin,
Yes, it was the key stuck down that did it, I can duplicate the error by
holding any key down. I think my cat is responsible for the busted/stuck key,
he likes to stretch out across the keyboard whenever I'm out of the room, that
and the fact that its not the greatest keyboard around.
I did try booting from different disks, including a copy of the original 3M
boot disk, same result. I discovered that when I was able to get my system to
boot that the version of cio in memory had a bad CRC. It was also much larger
than the cio I have in my CMDS dir. I saved the cio with the bad CRC (I assume
this is the cio in the rom) and then verified it with DED to fix the CRC, now
all is well. Wierd.
Bill
There is 1 Reply.
#: 15686 S12/OS9/68000 (OSK)
27-Jun-92 08:38:53
Sb: #15684-MM/1 problems
Fm: Mike Ward 76703,2013
To: Bill Dickhaus 70325,523 (X)
Perhaps your cat has learned to type interesting things on your keyboard while
he's languishing there. <g>
#: 15658 S12/OS9/68000 (OSK)
24-Jun-92 16:51:04
Sb: #15652-#MM/1 problems
Fm: Kevin Darling 76703,4227
To: Bill Dickhaus 70325,523 (X)
I think the 2.4 math and cio modules are different from 2.3 and previous.
I ran into a similar thing on the TC70... I was trying to use the 2.4 "irqs"
command so I could see all the 68070 interrupt vectors, and got one of those
errors.
A lot of us have discovered that we're using old commands, btw. I finally
noticed that I'd never installed the lastest basic/runb, for instance.
kev
There is 1 Reply.
#: 15660 S12/OS9/68000 (OSK)
24-Jun-92 22:38:12
Sb: #15658-MM/1 problems
Fm: Bill Dickhaus 70325,523
To: Kevin Darling 76703,4227 (X)
If I can ever get it to boot, I'll check that out. But why it would work some
times, and not others? Could the other error I got be caused by a bad keyboard
or bad keyboard connection? I'm going to try and find another keyboard to try.
Bill
#: 15705 S12/OS9/68000 (OSK)
29-Jun-92 20:55:10
Sb: #15652-#MM/1 problems
Fm: Bob van der Poel 76510,2203
To: Bill Dickhaus 70325,523 (X)
Bill, I wonder if the ROMs are decaying? Sometimes when I boot my system the
'dir' command doesn't appear in the stuff in the ROMs, so the first dir goes to
the disk to load itself. (I found this out when I started to use a replacement
dir--sometimes I'd get the old one, sometimes the new one). My theory
(dangerous ground here) is that sometimes a bit or two in the ROM is incorrect
at the point where dir is located, so it's not mapped in. Could be that in your
case it's a bad bit in cio. Maybe I should pull the ROMS and just reburn a copy
and see what happens (but I'm too lazy). Hummm, one other thing I noticed is
that it depends on how you boot. I had more luck getting 'dir' to appear in
memory when I held RESET down for a few seconds than if I used 'break' or hit
it momentarily.
There is 1 Reply.
#: 15709 S12/OS9/68000 (OSK)
30-Jun-92 07:44:07
Sb: #15705-#MM/1 problems
Fm: Bill Dickhaus 70325,523
To: Bob van der Poel 76510,2203 (X)
Bob,
I think you're right, I'm thinking about ordering the new ROMs for the MM/1
anyway (but I'm a little annoyed at the price). It looks like just a bit or two
got messed up in the cio in the ROMs, resulting in a bad CRC. The real problem
is that the cio I have on disk is not compatible with any of the system
utilities, so I got the traphandler error. I found I was able to get the cio
module with the bad CRC to stay in memory by forcing an error during the boot
process by holding a key down (funny thing is I would never have known about
this if it weren't for a stuck key!) when the system tries to recover from that
error, the modules in ROM don't get rechecked, or something. I now have a
possibly corrupted version of cio, but so far it appears to be working.
This brings up another problem I've got. If I hit reset to reboot, it hangs
trying to ccess thehard drive I can onlyreboot by pwering of and back o.
I suspect its juimingproblem, ut where isthe prem?Any ideas?I
have a Seagatedrive and th latest (s faI now) rivers.
Bill
Te is 1 Repl.
#: 15712 S12/O000 (OS)
30-Jun-92 09:41:39
15709-#MM/1 roblems
Fm: Mark Grifith 76070,4
To: Bill Dickhaus 7025,523 (X
Bill,
You might need to set the elay tie in the nit module o wait a whiler before accessing thedrive. Diferent dives requre differen time delay
beforI controller. I have my
delay time set with a value of 50, which seems to work with whatever drive I
try.
Mark
There is 1 Reply.
#: 15714 S12/OS9/68000 (OSK)
30-Jun-92 10:13:59
Sb: #15712-MM/1 problems
Fm: Bill Dickhaus 70325,523
To: Mark Griffith 76070,41 (X)
Mark,
Thanks, I'll try that. I had it in the back of my mind (bad place to put
something :-) to look that up, but hadn't done it yet.
Bill
#: 15783 S12/OS9/68000 (OSK)
04-Jul-92 11:11:28
Sb: #15652-#MM/1 problems
Fm: Jay Truesdale 72176,3565
To: Bill Dickhaus 70325,523 (X)
Try this string of commands to test modules in memory (including ROM):
mdir -u ! grep -v sysgo ! ident -qmz
If your ROM is going south you should get bad CRCs for the ROM modules.
You can also use this method as a brute force quick and dirty memory test by
loading the entire contents of the CMDS directory into RAM and doing the same
thing. This can get tricky as some programs like to put non OS9 modules in the
CMDS directory which then won't load. I got around this by giving all of the
all of the non OS9 modules uppercase names and using the command string:
dir -u ! grep [a-z] ! load -zd
I think that's close, I'm doing this all from memory. Hope this helps.
-J
There is 1 Reply.
#: 15826 S12/OS9/68000 (OSK)
08-Jul-92 21:07:29
Sb: #15783-MM/1 problems
Fm: Bill Dickhaus 70325,523
To: Jay Truesdale 72176,3565 (X)
Thanks, Jay. I just tried what you suggested, and came up with all good crc's.
I'm beginning to think that only the cio module is bad. But I did do this after
booting and loading many modules that are probably also in rom, so its not a
good test of only what's in rom, I'll try this next time I boot. As long as I
get the right version of cio loaded right away in the startup file, all the
problems go away.
Bill
#: 15657 S6/Applications
24-Jun-92 11:42:56
Sb: #15607-#Radio control
Fm: Tom Napolitano 70215,1130
To: Kevin Darling 76703,4227 (X)
Kevin,
Hi. For sw receivers to have facility for computer control, you have to
get into the middle price range, Icom R71a for $850,list or Kenwood R5000 for
about the same price. These two are available used for about $200 cheaper.
There the JRC series give you better specs, and more features for more dough.
The Japan Radio nrd525 at about $1000 and the Drake R8 for the same price are
the next step up. Check out Monitoring Times for the latest adds, and reviews.
The JRC command set, I feel, is the easiest to program. In fact you could
control the receiver about 80% via rs232, but being a knob twiddler, I would
rather just let the computer do what it does best, keep data bases of
frequencies and let me spin the dials. You really need a fine touch to bring
in those Papua New Guinea stations.
tomn
There is 1 Reply.
#: 15659 S6/Applications
24-Jun-92 16:53:09
Sb: #15657-Radio control
Fm: Kevin Darling 76703,4227
To: Tom Napolitano 70215,1130 (X)
Thanks Tom! I've often wanted to get an SW receiver... my job in the Army was
as a knob twiddler. (We all had black thumbs, in fact!)
kev
#: 15664 S14/misc/info/Soapbox
25-Jun-92 09:38:40
Sb: #Radio War Stories
Fm: Tom Napolitano 70215,1130
To: Kevin Darling 76703,4227 (X)
Kev,
So you were a radio operator with the military? As I recall, you were
navy. Are you familiar with the R390A? That was a great receiver; still is. I
saw a couple for sale at a recent swap, $200 asking, but I saw a guy talk it
down to $80 each. As a jarhead, we got to work 6 meters with the an/prc-25.
Not as neat as the 390, but then again, I wouldn't want to carry the 390 very
far!
I've seen reviews for addons to scanner receivers that give computer
control. These are various forms of interfaces that parallel the keypads, and
invariably are associated with msdos software. But I don't do much listening
above 30 mhz.
tomn
There is 1 Reply.
#: 15673 S14/misc/info/Soapbox
25-Jun-92 15:47:47
Sb: #15664-#Radio War Stories
Fm: Kevin Darling 76703,4227
To: Tom Napolitano 70215,1130 (X)
Tom,
I was an electronic warfare voice-intercept operator/linguist for the Army
Security Agency (a military branch of NSA). Our job was to eavesdrop on and
track North Korean military transmissions. At first I operated from the NSA
Field Station in mid-South Korea, but then was transferred to a tactical outfit
up at the DMZ (I have lots of horror stories about that! :-).
Yep, I remember the 390... we trained on it, but never used it in the field.
There, we used either vans mounted on the back of 5/4 ton trucks (TRQ-23? and
later TRQ-32) or backpack receiver sets (TRQ-30), plus jeep-mounted jammers
(TLQ-17) and truck-mounted jammers (GLQ-3). Oh, and microwave DF (MLQ-??). The
gear used at the Field Station is something I probably still can't talk about.
We would've killed for a portable digital receiver/DF-unit at the time (they
got them a few years later on). Instead, we spent most of our time "knobbing"
through several bands by hand. To this day, I hate static and headphones :)
ASA is where I met Marsha, btw. She was in my Korean class, and later was at
the Field Station, which was about 50 klicks south of where I was... so I'd
often go AWOL on the weekends to see her ;-)
So you were a Marine? Yikes! <grin> - kevin
There are 2 Replies.
#: 15685 S14/misc/info/Soapbox
27-Jun-92 02:11:36
Sb: #15673-#Radio War Stories
Fm: John R. Wainwright 72517,676
To: Kevin Darling 76703,4227 (X)
Hey Kevin,
How bout that? I had about the same job in the Air Force, but I had it a
little easier. First they sent me to Syracuse Univ. to learn German, then they
sent me to Germany. Tough life, eh? I did do about 8 months as a member of an
Air Force Liaison team at an ASA site in Berlin. Those poor guys didn't even
have air conditioning at their site - and they ate out of these funny tin trays
- geez. I guess there is not a lot of work for German Linguists in that field
any more - I would like to get back to Berlin now that thw "wall" is gone.
Ditto on the earphones and static too, I remember listening to a weak signal -
far away - and then you hear a transport pilot right over your head (Berlin)
key his mike.... see if you can get to the controls before he talks and your
eardrums touch in the middle of your head. (So loud you can taste it). Did
most of my last enlistment at NSA. Got my intro to computers there. Man, what
I coulda done with this MM/1 on my desk.
John Wainwright
There is 1 Reply.
#: 15687 S14/misc/info/Soapbox
27-Jun-92 15:22:00
Sb: #15685-#Radio War Stories
Fm: Kevin Darling 76703,4227
To: John R. Wainwright 72517,676 (X)
John,
No kidding? They sent you to a University to learn German instead of to DLI?
Lucky dog! BTW, I had six years of high school and college German under my
belt when I joined up... so naturally the Army picked Korean for my language.
Figures, eh?
Yeah, at the tactical outfit we'd be complaining about how our 20-year-old
unheated quonset huts were like Swiss cheese to the Mongolian/Siberian cold
wind, while our USAF counterparts down at Osan were complaining about the tint
on their room color TV being slightly off :-) Man, you USAF had it made!
You're right; what we could've done with personal computers back then. DF, etc.
And back in the US before I got out, I made a jammer mockup out of cardboard,
wood and plastic. Boy, if we'd had even just CoCo's back then, I could've
instead done a trainer which actually "worked" and had feedback.
There's an awful lot of ex-Intel types on CIS, btw. I run into AF/Army EW and
NSA people all the time around here. I guess wanting to be in the comm links
just gets into the blood :-) cheers - kevin
There is 1 Reply.
#: 15690 S14/misc/info/Soapbox
28-Jun-92 09:00:05
Sb: #15687-#Radio War Stories
Fm: John R. Wainwright 72517,676
To: Kevin Darling 76703,4227 (X)
Kevin,
Hehe, I wanted to get into electronics when I joined - but the USAF found out I
was partly color-blind. My high school spanish teacher would have been
astounded to learn that I had an "aptitude" for languages.
The army types did have one little advantage - by the time I made SSGT (air
force E-5), most of my army friends were E-6 and had been for quite a while.
I do claim one personal record - I spent almost 8 years in the USAF and never
flew on a military airplane.
Off the subject, but I was wondering if you know of a way to generate a NULL
from the MM/1 keyboard - for printer control strings in a text file and such.
The only way I have found is to make a file containing just a NULL and then get
EMACS to insert it in my text.
JohnW
There is 1 Reply.
#: 15692 S14/misc/info/Soapbox
28-Jun-92 15:09:54
Sb: #15690-Radio War Stories
Fm: Kevin Darling 76703,4227
To: John R. Wainwright 72517,676 (X)
John,
You didn't miss anything by not flying... we got shipped around in the back
along with trucks and jeeps; it was cold, noisy and uncomfortable... and
sometimes dangerous: the vehicles sometimes broke loose on takeoff, fuel cans
with tightened lids would pop and spray fuel from pressure drops. Fortunately,
such stuff always happened to the plane in front or behind the one I was on.
Still, I'd rather drive instead :-)
In the later keyboard drivers, a CTRL-space created a null. I'm redoing the
driver again with input from Eddie Kuns and Tim Kientzle to add more.
cheers - kev
#: 15838 S14/misc/info/Soapbox
09-Jul-92 08:07:40
Sb: #15673-Radio War Stories
Fm: Tom Napolitano 70215,1130
To: Kevin Darling 76703,4227 (X)
->We would've killed for a portable digital receiver/DF-unit at the time
->(they got them a few years later on). Instead, we spent most of our ->time
"knobbing" through several bands by hand. To this day, I hate ->static and
headphones :)
We shortwave listeners have been known to stay up 'til 4 AM local time
listening to stations 2db above the static in languages we can't understand.
->was at the Field Station, which was about 50 klicks south of where I ->was...
so I'd often go AWOL on the weekends to see her ;-)
Lucky dog, you.
->So you were a Marine? Yikes! <grin> - kevin
Drafted. I'm a lover, not a fighter <grins right back>
I'm writing a more complex receiver control program now to run under
multivu on the coco3. How complicated will this be to convert to run under the
68k windowing systems? How similar are the new systems to the coco data
structures and system calls?
tomn
#: 15688 S1/General Interest
27-Jun-92 21:50:15
Sb: #OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: all
Anyone out here on CI$ getting the OS9 UNDERGROUND Magazine yet?? Just got my
first issue of the magazine, and it really looks great.
How about it? Anyone else besides me?? (and some comments if you did get your
premier issue of the magazine??)
jim
There are 3 Replies.
#: 15689 S1/General Interest
28-Jun-92 03:05:07
Sb: #15688-OS9 Underground
Fm: Kevin Darling 76703,4227
To: Jim Sutemeier 70673,1754 (X)
I got a copy of it at the fest...
In case it hasn't been mentioned here yet, "OS9 Underground" and "68xxx"
magazines have merged (as of a few days ago).
BTW, the cost of an ad in there is incredibly low right now, if there are any
programmers here who've always wanted to sell something they've done.
#: 15698 S1/General Interest
29-Jun-92 08:21:38
Sb: #15688-#OS9 Underground
Fm: Mark Griffith 76070,41
To: Jim Sutemeier 70673,1754 (X)
Jim,
Just a side comment -- CI$ is really not acceptable here. CIS is better.
Mark
There are 2 Replies.
#: 15699 S1/General Interest
29-Jun-92 12:08:08
Sb: #15698-#OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: Mark Griffith 76070,41 (X)
Shucks, Mark, you may indeed be correct that CIS is better here than CI$, but
I've been calling CIS "CI$" since 1984, both here, on the service, and
elsewhere.
If Delphi, Genie or Prodigy had an "S" in it, I'd probably transpose a "$" for
the S.
No insult is meant towards CIS, but is IS a pay-per-usage service.
I like CIS so much better than I frankly like Delphi, that I re-signed up for
the service a short while ago. (I got my start telecommunicating right here on
this service.)
I'll try to keep my S's as S's, but if a $ shows up, then no insult intended
towards either CIS or any member of this service.
jim
There are 2 Replies.
#: 15700 S1/General Interest
29-Jun-92 14:37:48
Sb: #15699-#OS9 Underground
Fm: Mark Griffith 76070,41
To: Jim Sutemeier 70673,1754 (X)
Jim,
Well, if your fingers just happen to hit the $ instead of the S, then why don't
you sign your name as Jim $utemeier?
I believe you have gotten into a habit which will take some time to break. I
for one do not like to see CI$ since it is all to often used as a cut-down for
this service, which may be more expensive then any of the others (note I say
"may"), but then, you get what you pay for don't you?
Mark
There are 2 Replies.
#: 15706 S1/General Interest
29-Jun-92 21:35:21
Sb: #15700-#OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: Mark Griffith 76070,41 (X)
I agree, Mark...this service may indeed be more expensive than the others, but
I do find the message bases here much more informative and to the point than,
say, on Delphi. The questions here are straight, to the point, and the answers
are eually straight and to the point.
I joined CI$ (CIS) back in 1983 when I got my first CoCo, and remained a member
for over 5 years. In all that time, I referred to this service as CI$...not as
an insult, but more as a reminder to those who called my BBS that this was a
pay-per-usage service (unlike my BBS, which was free, of course).
Many others called this CI$, I do not own the copyright on this phrasing.
But, I will try to not ruffle any feathers here, and try to remember CIS.
BTW, didn't you just move to St. Louis?? (My old home town....)
jim
There is 1 Reply.
#: 15710 S1/General Interest
30-Jun-92 09:30:34
Sb: #15706-#OS9 Underground
Fm: Mark Griffith 76070,41
To: Jim Sutemeier 70673,1754 (X)
Jim,
Calling this service CI$ on your BBS or on Delphi is one matter, doing it here
is another. That is my point.
Yeah, moved to the St. Louis area back in January, but just moved the family
here at the beginning of June. We all like it a lot.
See ya, Mark
There is 1 Reply.
#: 15732 S1/General Interest
01-Jul-92 20:46:59
Sb: #15710-#OS9 Underground
Fm: Bob van der Poel 76510,2203
To: Mark Griffith 76070,41 (X)
Who cares what you call this system? I'm sure that no one at H & R Block is
upset that you call it CI$--so long as you keep signing on and spending your
money.
There is 1 Reply.
#: 15736 S1/General Interest
01-Jul-92 23:29:18
Sb: #15732-#OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: Bob van der Poel 76510,2203 (X)
I agree, Bob.....I was calling CIS "CI$" clear back in 1983, right here on
CI$......as were many of the users of the service. (I sure didn't make it up
myself).
However, I don't want to ruffle any feathers, and Mark's feathers appear to be
ruffled, so I will try to refrain from something I've done for almost 10 years.
(sheesh)
jim
There are 2 Replies.
#: 15744 S1/General Interest
02-Jul-92 09:01:02
Sb: #15736-OS9 Underground
Fm: Mark Griffith 76070,41
To: Jim Sutemeier 70673,1754 (X)
Jim,
My feathers are not ruffled, I just don't like to see that and I would like you
to stop if you feel you can. If you can't, the so be it.
Mark
#: 15745 S1/General Interest
02-Jul-92 09:01:12
Sb: #15736-OS9 Underground
Fm: Lee Veal 74726,1752
To: Jim Sutemeier 70673,1754 (X)
Mark seem$ to have appointed him$elf the Compu$erve (aka CI$) apologi$t.
I don't think you need to change anything.
When someone has an allergy, an allergist will expose the patient to small
doses of the substance to which the patient is allergic. Eventually, the
person with the allergy will become desensitized to the substance.
Lee
#: 15799 S1/General Interest
06-Jul-92 23:53:43
Sb: #15700-#OS9 Underground
Fm: Bob Palmer 74646,2156
To: Mark Griffith 76070,41 (X)
MAY ? be more expensive. I have been forced down to 300 baud to read the mail
because of certain system's pricing structures. Not that they are not
extremely good services you understand, just more expensive than I like to pay
(what isn't you may well ask ). Message counts may be a good indicator of the
effects of price structures. That's the lot for this topic. Bob
There is 1 Reply.
#: 15802 S1/General Interest
07-Jul-92 09:14:17
Sb: #15799-OS9 Underground
Fm: Mark Griffith 76070,41
To: Bob Palmer 74646,2156 (X)
Bob,
If all you want to do is read mail online, then CIS is not the cheapest service
to use. If, however, you are interested in getting the best publically
available software, and download it at a reasonable cost, then CIS becomes more
competitive with the other services. For that matter, grabbing the entire
message bease every day or so, and then reading offline is much cheaper than
online reading. This is why I said "may".
Mark
#: 15702 S1/General Interest
29-Jun-92 18:44:25
Sb: #15699-#OS9 Underground
Fm: Steve Wegert 76703,4255
To: Jim Sutemeier 70673,1754 (X)
Hey Jim ... nice to see you back!
Steve
There is 1 Reply.
#: 15707 S1/General Interest
29-Jun-92 21:36:54
Sb: #15702-OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: Steve Wegert 76703,4255 (X)
Thanks, Steve, it's good to be back here. I was trying to cut down on costs
around here a couple of months back, but really missed all you guys here, and
the great discussions we have had.
Will chat with you soon. Take care.
jim
#: 15724 S1/General Interest
01-Jul-92 16:55:26
Sb: #15698-OS9 Underground
Fm: Lee Veal 74726,1752
To: Mark Griffith 76070,41 (X)
Lighten up, Mark. It was probably just a typo.
$eriously.
Lee ;-)
#: 15723 S1/General Interest
01-Jul-92 16:53:13
Sb: #15688-#OS9 Underground
Fm: Lee Veal 74726,1752
To: Jim Sutemeier 70673,1754 (X)
Yeah, I just got one, too.
They do look pretty good.
Lee
There is 1 Reply.
#: 15735 S1/General Interest
01-Jul-92 23:26:32
Sb: #15723-#OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: Lee Veal 74726,1752 (X)
Wait until you see next month's Underground, Lee....the print should be better
than the first month (although the first issue looked excellent), and there
will be many more articles in the next issue, seeing as 68XXX is now a part of
the Underground.
Shucks, I think my own article about hasing in C will make this next issue.
(sheepish grin)
This next issue should really be quite impressive.
jim
There is 1 Reply.
#: 15800 S1/General Interest
06-Jul-92 23:59:01
Sb: #15735-#OS9 Underground
Fm: Bob Palmer 74646,2156
To: Jim Sutemeier 70673,1754 (X)
Boy - I had better subscribe right away. I don't know anything about hasing in
C or any other language. :-) Bob
There is 1 Reply.
#: 15801 S1/General Interest
07-Jul-92 09:06:39
Sb: #15800-OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: Bob Palmer 74646,2156 (X)
Whoops, I sure did say "hasing", didn't I?? Meant hashing, of course....
Sorry for the typo.....
jim
#: 15691 S3/Languages
28-Jun-92 12:04:30
Sb: _ss_mgpb in MM/1 CGFX.L
Fm: Bert Schneider 70244,427
To: ALL
Is there a way to map a get/put buffer on the MM/1 like the CoCo? I have been
using _ss_mgpb(path,grpnum,bufnum) on the CoCo OS9 with cgfx.l and I would like
to do the same with the MM/1 version of CGFX.L. Is there another way to do this
or is this something entirely different? Thanks for anyones help! Bert
Schneider
#: 15693 S12/OS9/68000 (OSK)
28-Jun-92 17:03:10
Sb: #fidonet-software for OSK
Fm: ole hansen 100016,3417
To: All users
To all os-9/freeks. Does anybody know if some 'fidonet'-software has been
ported to OSK. I am trying to connect to the Danish fidonet from my OSK-system
I have in the lab at my work. I am already running Email by using the TOP's
mail-system for OSK, and this works fine
regards ole@danelec.dk
There is 1 Reply.
#: 15701 S12/OS9/68000 (OSK)
29-Jun-92 17:23:12
Sb: #15693-#fidonet-software for OSK
Fm: Robert Heller 71450,3432
To: ole hansen 100016,3417 (X)
Ole:
I too have been seeking FidoNet software for OSK. I don't think there
is anything out there. Plenty of Mess-DOS sources (Bink, Maximus, etc.).
Probably could be ported, but would be rather a pain in the rear....
Robert
There are 2 Replies.
#: 15708 S12/OS9/68000 (OSK)
29-Jun-92 21:41:31
Sb: #15701-#fidonet-software for OSK
Fm: Jim Sutemeier 70673,1754
To: Robert Heller 71450,3432 (X)
I understand that RiBBS will EVENTUALLY be ported over to OSK, but that is
supposed to be a couple of years off.
StG should be coming out with an OSK BBS for OS9 pretty soon, and they claim
that it'll have Usenet accesses, in addition to their own networking. StG,
BTW, has probably 20-30 nodes hooked up now. Not a huge network like FidoNet,
but it does have a pretty decent userbase.
jim
There is 1 Reply.
#: 15715 S12/OS9/68000 (OSK)
30-Jun-92 18:20:02
Sb: #15708-fidonet-software for OSK
Fm: Robert Heller 71450,3432
To: Jim Sutemeier 70673,1754 (X)
Well, Usenet access does me little good - there aren't any local machines
running uucp out here in Western Mass. Lots of FidoNet nodes though...
Robert
#: 15725 S12/OS9/68000 (OSK)
01-Jul-92 16:56:50
Sb: #15701-#fidonet-software for OSK
Fm: ole hansen 100016,3417
To: Robert Heller 71450,3432 (X)
hello robert I have a unix-port for a fidonet-server, but the Microware and gnu
c-compilers didn't like the dialect it was written in, so ....
regards
ole@danelec.dk
There is 1 Reply.
#: 15727 S12/OS9/68000 (OSK)
01-Jul-92 18:23:43
Sb: #15725-#fidonet-software for OSK
Fm: Robert Heller 71450,3432
To: ole hansen 100016,3417 (X)
Hmmmm. Most vanila UNIX code ports well to OSK.
Robert
There is 1 Reply.
#: 15785 S12/OS9/68000 (OSK)
04-Jul-92 14:51:23
Sb: #15727-fidonet-software for OSK
Fm: ole hansen 100016,3417
To: Robert Heller 71450,3432 (X)
hello robert I hope too. At least I found out why I had problem compiling under
unix. 1 header-file was empty, and this caused a lot of strange messages from
the compiler.
regards ole
#: 15694 S1/General Interest
28-Jun-92 17:09:47
Sb: #OS9 Underground Pricing
Fm: Jim Sutemeier 70673,1754
To: 76703,4227 (X)
You got that right, Kevin.
I wasn't sure exactly what the advertising prices were, so I gave Alan a call
this morning to see what they were.
For those who might be interested, here's a few representative prices:
1 month 3 months 6 months
1/4 page 7.50 15 30
1/2 page 10 20 34
IBC/IFC 25 50 95
Camera ready art is required for the ads, but, if you don't have something
ready, Alan is a graphics artist, and can (easily and inexpensively) whip up
something to your liking.
Shucks, a programmer could invest only $30 and have an ad displaying his work
for 6 months. I'll bet beer, for most programmers, is more than $30 for 6
months. (grin)
jim
There is 1 Reply.
#: 15695 S1/General Interest
28-Jun-92 21:01:56
Sb: #15694-OS9 Underground Pricing
Fm: Kevin Darling 76703,4227
To: Jim Sutemeier 70673,1754 (X)
Yah, I told him that his ad prices were too low :-), but he said that's to give
more people an opportunity to get started. Sounds good to me!
#: 15696 S5/OS9 Users Group
28-Jun-92 22:07:59
Sb: #15364-#announcement
Fm: John Wight 76370,2100
To: Carl Kreider 71076,76 (X)
As for OS-9 CN, we have success in communicating with those in Europe and
Australia as well. I have been thinking about the many discussions of ideas
related to OS-9 CN, and the old/new users group, in particular what you had to
say. I feel very strongly the OS-9 Community needs both. The Users' Group is
better suited to support business users, and those that can easily afford to
access such services as Delphi, CIS, and the Internet family of networks, and
to send in for membership for the Users' Group. I will apply for membership,
although the first time didn't work out well for me, or many of us. OS-9 CN has
its place, too. OS-9 CN is for amateur users of OS-9, in particular those with
an extremly small budget. Many Australian and European users are now able to
communicate with us because we use the most inexpensive means. On the other
hand, services such as Delphi are prohibitively expensive (Delphi is $18.00 an
hour for me, although CIS is $12.80 an hour living in Hawaii). It is even more
expensive for Canadian users to communicate. Because we are amateurs and use
the most inexpensive means to communicate, OS-9 users outside of the U.S. have
given OS-9 CN much support in their communications efforts. I feel we need both
groups to serve the OS-9 Community, so why not make sure there is
communications between our groups? As for an efficient means, we are working on
it. I tried Internet/UUCP, but lost my feed and don't know where to get another
affordable one. I come to CIS regularly (once every one or two weeks), so we
can start with that. Also, many other representatives of OS-9 CN visit CIS and
Delphi regularly, and I am compiling a list of user names.
There is 1 Reply.
#: 15772 S5/OS9 Users Group
03-Jul-92 22:15:48
Sb: #15696-announcement
Fm: Carl Kreider 71076,76
To: John Wight 76370,2100
Nice to see you are around. I thought you had disappeared.
I certainly think the OS-9 community needs the OS-9 User Group. I know the
first time didn't work out well. In fact, it probably bothered me more than
you to see all of my several years of hard work go down the drain. But I
believe that it will work better this time.
Living where I do, the value of OS-9 CN isn't as clear. As I have mentioned
before, I don't know where to find Fido or what I would do with it if I found
it. But I trust you judgement that it is useful to a group of OS-9 users. And
I don't see how the goals of the OS-9 UG and the OS-9 CN conflict with each
other or exclude the other. Surely some folks will want to be members of both.
I agree that effort should be put into cross pollination. For example, perhaps
the OS-9 CN would like to use the MOTD to keep non-Fido people abreast of the
OS-9 CN doings.
Like you, I don't know an efficient means to stay in communication. A local
public access Unix connection is reasonable in price, but isn't available
everywhere. For now, CIS is a common intersection. StG net is growing, but
again the cost of moving news around has to be borne by someone. Have you
tried to interest the StG guys in OS-9 CN? There appears to be some redundant
effort there.
#: 15697 S10/OS9/6809 (CoCo)
28-Jun-92 23:00:24
Sb: #15616-#6309
Fm: Brother Jeremy, CSJW 76477,142
To: randy pischke 75460,205 (X)
I glad that I could be of help. I just got back from home leave ( a time in 've
been wondering if there are other chips in the COCO that have
upgrades/replacements available.--Br. Jeremy, CSJW
There is 1 Reply.
#: 15809 S10/OS9/6809 (CoCo)
07-Jul-92 21:57:56
Sb: #15697-#6309
Fm: randy pischke 75460,205
To: Brother Jeremy, CSJW 76477,142 (X)
I received my upgrade today so I dove in and did it. Only one problem, when
using Multi-vue I get many flickering "ghost" lines at the top of the screen.
They seem linked to the mouse pointer. If I move the pointer down, the lines
move lower down on the screen. They move back up as the pointer moves up. Do
you have any similar problems?
There is 1 Reply.
#: 15829 S10/OS9/6809 (CoCo)
08-Jul-92 22:04:47
Sb: #15809-#6309
Fm: Brother Jeremy, CSJW 76477,142
To: randy pischke 75460,205 (X)
Dear Randy,
No, I do not seem to have that problem. I use the GSHELL1.24a version and have
some other patches. Unfortunately, I did not always keep good notes of how I
put the boot/system together. But I will check to see if I have anything that
greatly deviates from stock. I have the patched GRFDRV and the INIT patch to
fix the rollover problem. I know that they are here on CIS. I'll be in touch.
With all best wishes, Br. Jeremy, CSJW
There is 1 Reply.
#: 15854 S10/OS9/6809 (CoCo)
10-Jul-92 01:12:10
Sb: #15829-6309
Fm: randy pischke 75460,205
To: Brother Jeremy, CSJW 76477,142 (X)
Br. Jeremy,
I also use gshell 1.24a. Have install the grfdrv patch but haven't heard of
the INIT patch. Maybe I should get that also. Any modification that I hear of I
make to my system so I have quite a few patches to my system. As I mentioned to
Pete Lyall, I reinstalled my 6809 and the vertical 'ghost' lines that were
appearing on my hi-res screen on white backgrounds went away. I will check on
getting a replacement 6309.
Take care 'til I hear from you again. Randy.
#: 15703 S3/Languages
29-Jun-92 20:39:06
Sb: #CGFX.L for MM/1 OSK
Fm: Bert Schneider 70244,427
To: 71076,76 (X)
Carl, I am interested in porting some C code from CoCo Level II to OSK MM/1 but
I need some assistance with your CGFX library.
Does _gs_scadd do the same thing as the _ss_mgpb call in cgfx.l in CoCo OS9?
Also, do you really mean Point(path,x,y) instead of Point(path)?
99% of my code is compatible except for the loading and saving of .vef files
for graphics windows. Obviously I have to go to another format for saving the
pictures. Any suggestions?
Bert Schneider
There is 1 Reply.
#: 15711 S3/Languages
30-Jun-92 09:33:32
Sb: #15703-CGFX.L for MM/1 OSK
Fm: Mark Griffith 76070,41
To: Bert Schneider 70244,427 (X)
Bert,
You should be addressing your questions to Mike Haaland, the author of the MM/1
C graphics library. I can tell you though, if something is not in the library
that was in the CoCo version, it is probably because it is not supported by the
OSK version of windio.
If you haven't, you might what to check the libraries for the latest version of
cgfx for the MM/1. Mike did a newer version for the latest release of windio
and you might have an older copy. Look in DL16 or DL12.
Mark
#: 15716 S12/OS9/68000 (OSK)
30-Jun-92 18:59:16
Sb: #WindIO ideas?
Fm: Kevin Darling 76703,4227
To: all
Anyone have any *minor* <grin> suggestions before I post windio v42 in a couple
of days?
For example, someone suggested that the default keypad mode on boot should be
numeric (ie: hitting NUMLOCK would actually change to cursor key mode)... since
everyone has separate cursor keys and thus the numbers would be available right
away. Sounds like a good idea to me.
Stuff along those lines. Then we can start on the big stuff (allowing programs
to move/resize/etc).
thanks! - kev
There are 2 Replies.
#: 15733 S12/OS9/68000 (OSK)
01-Jul-92 20:47:07
Sb: #15716-#WindIO ideas?
Fm: Bob van der Poel 76510,2203
To: Kevin Darling 76703,4227 (X)
Not a suggestion, but I do notice that sometimes my keyboard will not switch
from NUMLOCK mode to normal. Seems that after the first toggle it doesn't want
to switch back. Don't know if this is the keyboard or the software? Also, why
not have the initial mode as an option (maybe set in /dd/sys/keyboard.env).
This file could also have other options in it (like having the Fkeys generate
values, instead of being screen selectors).
There is 1 Reply.
#: 15750 S12/OS9/68000 (OSK)
02-Jul-92 10:31:15
Sb: #15733-WindIO ideas?
Fm: Steve Wegert 76703,4255
To: Bob van der Poel 76510,2203 (X
Bob,
I note a similar problem with bth num lockand caps lck on my sstem. Itgls fine butthe lmps on he keyoard wn't reelct i's propr staus.
Not sureif it's ord prolem or ot .. I've ust goten usedit.
Steve
#: 15737 S12/OS9/6800K)
01-Jl-92 3:40:3
Sb: #15716-WindIOideas
Fm: Ken Scale 74646,227
To: Darling76703,427 (X
Openihe foodgats jus a crac...
KD>Anyone have ay *minor*in> sggestionsbefore I indiov42 in a
KD>couple y?
Maybe a few... <g>
utfirst, let e say tha the "stcript you poste tooCo the other ay ble me aay: I ad noidea soe of tose thngs wee evn on
the drawig b lt alon usabl (yea, "unspporte"). I ent rght outndstartedlookin for a new mnitor withhigherpersistnce tan my crrent
Sears/Sanyo,use mthinksa type7 scren wil get alot mre use wit those
capabilitieeent. reat jb!
Back on topic.. a cuple gltches have ncountered wih v41, tou
probably now ofmost aleady:
1) Alt-backarrow cnflicts wth ALT-TRL-B indow l(yeah a detal
left ver frhe lat-minue move eyoardmouse to CTRL-as)
2) The moue ct/pasfer eems t get te wrog sco-ordnates n
screens oher tx26 types. 3) The moue seemccssionaly getexcomunicatd (nobutton Mouse
System drive Ed 4,$F8C5A6
4) I have had a seres of sots (garbag) scatterrd acr5 (type 7
moved/resized and ith /w6 & w7 oerlaysunderstest dmo). hesespots were writen when TasOM (runnig on /w3) emtted its"CONNECT" blls.
Seemed to oupleof spots pr each of 3l. Happene twice. BTW
this is on a 9-eg mmory ma. Ba pointr in he "bel" r,
perchance? Could also e in TasCM, of cours.
Hmmm... guess I'm kinda v onight.. coninuednext mesage.
There is 1 Reply.
#: 1573S12OS9/600 (OSK)
01-Jul-2 23:44:b: #1577-WindIOideas? Fm:Scale 7464,2237
To: cales 4646,237 (X
(continuem previous ae)...
As for the suggestins (yo can pck whih are minor" g>):
a) Folks withous needa way ithe killthe reize/moe keyoard
actvatio, or away ofcompletng itfrom he key
b) Progrmmers need way of dtermiing i an aplicaton isrunnin under
K-Windo gtstatcall giing adetermiistic esult oul sure be
nice. Or as I suggsted onemail, efinig a ":KW:"(or some uch)
r in Temcap. aybe ven a "KW=42: for eition 2, e.g.
kw = tgetnm("KW");
if (kw > 3) {..}
ned a stndard sooh.
c) Signalswhen windanged I woud lie to se codes to
_ss_dcon() and _ff) to enabe and disale senf a sinal to
a pocesswhen ito has ben chaged/rsized(defaut, no sl,
of cours). It woul have bee really nie (and eay) to havebeen able
ut upport forthese in m "sc" and"ispell" orts. d) A bigge mousecut/pase buffr we nice e) Then thee's thse F-kes...
Anyways, cheer, and keepup th goodwork.se!
Ken (hat sunurn ad goate acros the upper able i Chicgo...)
#: 15717 S9/809 (CCo)
30-Ju-92 2153:40 Sb: Data Bass
Fm: BILL JLF 7263,226
To: AlDoes anyoneknow of a ata Bse whih wil allow morn a thee (3) evel
so ata Mater frm Compterwar (theLevel2 verion of rofile)allows three evels of orts,oesnt allo furter sors on the list'. know his isprobaby an od s, new on orum
Thanks Bill elf
#: 15719 S12/OS9/68000 (OSK)
01-Jul-92 2:20:7
donet-oftwar for OS
Fm: Jim Sutmeier 0673,154
To: Robller 1450,432 (X)
Shucks, if thereare a lot f Fido nods, andUsenet noin you part f
the countr sugest yo openup a Used, rater tha a Fid feedI was a BBSoperatr from e984 unti the end o 1991 (<PlRap BBS),
and live in avery busktplacehere n Los Ageles Fido,Usent, StG
RCIS, plus few ore are repreented he
Back in the firste of yars o my BBS I rana CoBBSsystem then I
switche to PBBS util 1990, hen I swver to StG(the idea o
networking entic- littl did I relize hat I as nukng myown sytem).
During the first 3 yeas of opeI averagedapproximtely 10,00 callers per year, nd was thebusies RSDOS/O9/CoCo BB here in Ls Angeles. The
reason for my populaity was imple. This wafre the ays of networking, nd I hd a lotof RSOS andOS9 "gru's" dy caling in nd
"talking wich oter.
The idea of networing cae ontothe scee, as I recll, out 197
sometime. As etworkig becae moreand mre popuar, icd that my
average callrs per ear dwinled. So, i 1990, ed ooking up t StG in
the hot mabe I ould get mre callersback. (rong!) Peple wcal their StG and not y system toget tews and iformation.
In the last 2 yers of m BBS' operaion, I h00 callrs pe year -a
far cry from the 10,00 per yearwhenI firs starte.
So, I the pug on y BBS. If I ha had the oportunity in the pas years, to once again ofer smething niqueto the ommuniy, I amcert could have atractedsome usersback.
The point of ths ratng mesage (oo log -> srry, gus) is hat if ou
have oportuity to ffer omethig uniue to our commuity, thenI'd
est you go ith that,e than oing wth wha's alrher. Fro a
SysOp's pont of vie, the priarideation is tat you want our
investmet to bsy ad attrat calers. If you hasmething uniqe to
your area, you sand a beter chanc of gettingcalles, andkeepin them.
jim Sutemeier
There is 1ly
#: 15728 S12/OS9/68000(OSK)
01-Jul-92 4:2
Sb: #15719-fidonetsoftware fo OSK
Fm: RobertHeller71450,432
To: Jim Suteeie 706731754 (X
Jim:
I have nothing nst offerin something uique. Wihin the FioNet
world, mypresent sys rather uique - I un a BB on a Sride 40. Ths
is a 6800d system. The opeating systeP/M-68K lyerde on a
ti-User BIS" (a kindof tatcherrunnig unde multile copies ofa
single-user O/S). S software s UNXcess .0.2, hich ws writen fo
UNIX, but I hact for CPM-68K. I se a homegrown maier progra
(Wolf/68K) with a home-grow echomailhandler.
Te probem wit offerng a Uenet is cot of imorting Also
most of the peple who wind a Usent feedintersting an gia the Int conectionto th localcollees (UMAmherst, mith Collee,
Amherst Colleg, Hampsolleg, and ount Hlyoke olleg). One of he
main reasons the'tinthe wayof Useet out h the ack of UNIX systet ae not art oflege cmpus sytem. Veryusinesss
running UNIX hops an thosefew ar too sall an poor o handl muchd
their own EMail over ucp.
While mypresent ystem wors, it s limitd in was (notthe
last of which i har- th 'ole Strid is geting old and epair and
replat pats are hardt comethe hrd dis contoller ied rcen my system was own fr oo monhs, unil I maageocatea replcement machine () If I couldmove to OK, tulss o a problem
migrating to newwer ardware wuld be posble also mmore ffectve us of
the Strie as wel (ithas 10serial pors, but CP/M68K, dispte tuti-User BIS" is a sinle-user / inge-tas/S).
Robert
#: 15722 S1/General Interest
01-Jul-92 16
Sb: #15598-Thes Operting ystem
Fm: Lal172
To: Kevin Drling 6703,427 (X)
Theos, hmmmmm!!!!
I wonifDan ha aske aboutthis o.sys oer in the Reigion Foum.
d like Teos would b something hat wold run n G.O..-likecomputr.
(G.O.D. bein and arony which meas "Graphi Omniscint Device")
Lee
#:15762 S/Generest
03Jul-9 10:5:05
Sb: #15597-#Theos Oprating
Fm: Fred Carter 6646,3172
To: Dn Dalen70641,551 (X
H:
What is Teos? Frmessage I gther you ae using a ystem with thos Oeratin Syste on iheos s optimzed fr mult-user ata bae
application. Eachdata ores infomation abou the data tpe of eac
field of a record. (IT comman can be use on any ata fie)
Theo may sund lik a mythlogreek gd, but believ it is an
acronym for"THE Operaing System. Before tere was86, ther was
OASIS ("Onine Aplicaiofo Sysem" or omething which ran o a
Z-80. The systemsuppoted abose per Mz of sstem cock sped.
The Z80 sysems runnOSIS (Altosfor exampl) usually hd 256K of AM
and 40 to 400 MBd disk stoage. 10 y this wold have cst $2K.
The hard isks wee of size sing aSMD (torageModul Devie)
Irface Averae seek ime was 20-2 millisecons and trasfer rateswere 1/Sec. Troughthe useof ovelays, rogram could e arbitraily large The ommand lin interpretr is simliar o REXX and ws modelIB
mainframe (Systm/36?). he comman line interprter was refully oaded
script languae. Appicatios coul be witten n BASIC,and later C
Print Spooling is buil in and mltiple prnters nd prit frete.
Theos liXor OS-. Theos ht foundationsolidly n the MISnagement Iformationms) wold. Whil I haen't sed the'38sion
the Z-80 ad 808 versire roust andefficient.
Regards
Fred Carter (7666,3172)
There is 1 eply.
#: 15773 S1/Genera Interst
Jul-9 00:0:11
Sb: #1562-Theo Operatng Sysem
Fm: Kevin arling 6707
To: FredCarte 7664,3172 X)
Fred,
Was it Oasis or Oasys? I remmber the ltter... i was multuser and ad
automatcrd-locing lke OS-.
best - kev
#: 15726 S10/OS9/609 (CoCo) 01Jul-92 17:6:29
Sb: #15617-Smartwach Clock
Fm: Lee Veal 7172
To: randypischke75460205 (X
Randy,
saw part of yur exchang withKevin. I justuploaed SMAT.AR toDL10tll robablybe avalable tmorrow r when evr the sysps activate i Lee
#: 15729 S3/es
01-Jul-9 19:2:56
Sb: #CGX.L
Bet Schnider 7244,47
To: MarkGriffit
I found out that all isthe Verion 3 isue o CGFX. - I ned tha to sav
my image dik! So far,98% of thecod great o the MM/1! t alo
workseat eal fater! shouldhave m MANDL09K pogram out onthe
street voon (oce I get he new cgx.lion 3 updte). Theimages ar
breaktaking o the M/1! Iam sur Paulther will e intersted!See ya
Bert
P.S. Is Bret W. still in S.? I'vebeen tying toget hol of hm but
he doesn't anwerSee ya again! Brt
The1 Reply.
#: 15746 S3/Language
l-92 09:03:8
Sb: #1572-#CGFX.
Fm: Mark Gri07,41
Tot chneidr 7024,427 ()
Bert,
Yeah, Bret is still around, but he a prety lowprofilethes days.
don't knowwhat hs phon numbe is, ut he oes po in m timeto tim.
Good to heouhave somn coolfor th MM/1 Can't wat tit.
Mark
Ther 1 Repy.
#: 15789 S3/Lnguages
05-Ju 16:8:26
Sb: #15746-CGF.L
Fm: Scneider7024,427
Toar Griffth 7600,41 ()
I got ahold of him! He s still here ieU.S. andhas a sailig busines!
As soon a I get he newCGFX. libral have my ANDEL09K eady for Pal.
I have run theimage from stubiver Ibuilt o testit out o makeit
a totally uiendl progam, I eed th new CGibrary.
See ya!
Bert Seder
#: 15741 S12OS9/6800SK)
02Jul-92 02:1145
Sb: #C_Quesion
Fm: LARRYOLSON 7227,347
To: all
C guru ...
Would someone please poit out thee with th following supposedly smpleC progrm.
------------------------------------------
#include <stdio.h>
main()
{
int x; char *a[5];
for (x = 0; x <= 5;++x)
getsa[x]);
for (x = 0; <= 5; +x)
print("%s\[x]);
exit(0);
}
--------------------------------------------
This is n example out of the book Going From Basic To C. It is
supposed to get 5 characters from the keyboard and then print them, but
all I get from it is a crashed machine.
So far the other examples that I have tried, have worked, but for
some reason unknown to me this one doesn't work.
What simple thing am I overlooking ????
There are 2 Replies.
#: 15742 S12/OS9/68000 (OSK)
02-Jul-92 06:58:37
Sb: #15741-#C_Question
Fm: Pete Lyall 76703,4230
To: LARRY OLSON 72227,3467 (X)
Larry -
Your problem are the lines:
char *a[5];
.... AND
gets(a[x]);
If that's the way the book reads, you should shoot the author!
In the statement: char *a[5]
You're stating that 'a' is an array of pointers with 5 elements. These pointers
point at SOMETHING of type 'char' - but WHAT? You haven't allocated any space
for them to point at, nor have you initialized the pointers to point AT
anything. There's no magic in C.. you have to do all the dirtywork yourself
(grin).
This problem doesn't rear its ugly head until:
gets(a[x]);
Which says: get a string [terminated by a return] from the keyboard (STDIN),
and stuff it in the location pointed to by the pointer I'm giving you.... Well,
we already know that the pointer is crap, and we have no idea what it points
to, AND whatever it DOES point to will be clobbered.
This program could be made to work by changing the declaration of 'a' to: char
a[5][256], which states that 'a' is an array of 5 arrays of 256 characters.
This pre-allocates space to put the strings in, and also implicitly supplies
pointers to the 0th character of each 256 character array when you call it
a[0], a[1], etc. (in C, an array NAME by itself is the same as the pointer to
the 1st [0th] element of the array... i.e. 'a' is the same as &a[0], and a[4]
is the same a[4][0].
Goo luk!
Pete
Theres1 Repy.
#: 15S12/S9/6800 (OS)
03-ul-92 01:1249
S1542-#C_uestio
Fm: LARRY ON 72227,3
To: Pete Lyal 7670,4230 X)
Pete,
Sounds like I beter thrat book awy, or at lest pu it awy
until I kno somethng abot C andn spo mistaes likethat. e was
using that routine toshow hthe follngBasic outine ionvrted to C.
10 DIM5)
20 FOR x=0 TO 3 INPUT a$()
40 T x
50 FOR x=0 TO
6RIT a$(x
70 NEXT x
80 EN
Thanks Pete, Ill seewhat oher truble can get ito <g>
Larry
er is 1 Rply.
#: 15765 S12OS9/6800 (OS)
03-Jul92 1326:24
#1556-#C_uestio
Fm: Pete Lyll 7673,4230 To: LARRY OLSON 72227,34)
The problem her is tht Basicdoes atomati (dc)g alloationa
well as othvariables).You'reright ... oss th book Thatept ws at
such lemntary lvel that tis guound to hose ouup at the moe
complex levl.
*ABSOLUTE BEST* book I have eer seenhe C eophte (andthe oe thatok the ie forme afer buing ore than half dozen othes) was "Therimr PluThee Grou. Eading, ots ofexamplend a god
sense of hmor aswelll wort the 25 r soIW, the local ollege uses
it their C txtbook
There is Repl.
#: 15712/6800 (OSK)
04-Jul-9 03:22:1
Sb: #15765-C_Qion
Fm: LARRY OLSON 7227,3467
To: Pete Lyal 76703,423 (X)
Pete Thanks forthe tip onthe book(C Primer Pus), I'll pck it up.I've gota
dozenC books hee but none farry
#: 15752 S12/OS9/68000 (OSK)
02-Jul-92 23:57:55
Sb: #15741-#C_Question
Fm: Kevin Darling 76703,4227
To: LARRY OLSON 72227,3467 (X)
Larry - I'd have never come up with as elegant and simple a solution as Pete,
but I thought I'd add some thoughts. I know that you are also a 6809 rma
programmer, so another way to help learn C is to look at the compiler output
(eg: "cc test.c -ca" which will stop with a "test.a" source listing).
For example, the goofed up source they gave (shortened up here) was:
main()
{ int x;
char *a[5];
for (x = 0; x <= 5; ++x)
gets(a[x]);
}
Compiled with the -ca option, you get this (#comments are mine):
psect test_c,0,0,0,0,0
* main()
* {
ttl main
main:
pshs u
ldd #_1
lbsr _stkcheck
* int x;
* char *a[5];
* for (x = 0; x <= 5; ++x)
leas -12,s # make room on stack for int_x and 5 pointers (2+5*2)
clra
clrb
std 10,s # x=0
lbra _4 # enter "for" loop
* gets(a[x]);
_2
ldd 10,s # x
aslb # multiply * 2 as index into array ([x])
rola
leax 0,s # point to beginning of array
leax d,x # now point to a[x]
ldd 0,x # pick up a[x] <<< contains pointer to ?? nothing!
pshs d # push on stack as parameter for gets
lbsr gets # call gets function
leas 2,s # drop parameter
* }
_5
ldd 10,s # x = x+1
addd #1
std 10,s
_4
ldd 10,s # x
cmpd #5 # <= 5 ?
lble _2 # yes, loop
_3
leas 12,s # else exit
puls u,pc
_1 equ -82
endsect
So it was pretty easy to see that the parameter picked up and passed to
the gets function pointed to who-knows-what, yah? (cont'd in reply)
There are 3 Replies.
#: 15753 S12/OS9/68000 (OSK)
02-Jul-92 23:58:24
Sb: #15752-C_Question
Fm: Kevin Darling 76703,4227
To: Kevin Darling 76703,4227 (X)
So now we look at Pete's example (very slightly modified):
main() { int x;
char a[5][200];
for (x = 0; x <= 5; ++x)
gets(a[x]); }
psect test_c,0,0,0,0,0 * main() * {
ttl main main:
pshs u
ldd #_1
lbsr _stkcheck
* int x; * char a[5][200]; * * for (x = 0; x <= 5; ++x)
leas -1002,s # make room for int_x and 5*200 one-byte chars
clra
clrb
std 1000,s # x=0
lbra _4 # enter "for" loop
* gets(a[x]); _2
ldd 1000,s # x
pshs d
ldd #200 # size of each array element
lbsr ccmult # multiply stack param (x) * array_element_size
leax 0,s # point to beginning of array
leax d,x # point to a[x][0]
pshs x # push parameter for gets
lbsr gets # call gets function
leas 2,s * } _5
ldd 1000,s # x=x+1
addd #1
std 1000,s _4
ldd 1000,s # etc
cmpd #5
lble _2 _3
leas 1002,s
puls u,pc _1 equ -1072
endsect
Now, even tho we had to guess at the function of ccmult, it was still clear
that we were passing the address of an _allocated_ char subarray to the gets
function... and not just a pointer to hyperspace. Does this make sense?
The other thing that looking at -ca output does is to impress the fact that C
is basically an assembly macro language... and that *pointers are just
variables being used as extra "index registers". best - kevin
#: 15755 S12/OS9/68000 (OSK)
03-Jul-92 00:24:00
Sb: #15752-#C_Question
Fm: Pete Lyall 76703,4230
To: Kevin Darling 76703,4227 (X)
Elegant shmelegant... you spotted it, and in what I'd consider a denser jungle.
When are you coming over to C, anyhoo? It'll be C++ time soon....
Pete
There is 1 Reply.
#: 15760 S12/OS9/68000 (OSK)
03-Jul-92 07:13:52
Sb: #15755-#C_Question
Fm: Kevin Darling 76703,4227
To: Pete Lyall 76703,4230 (X)
Ha! No way would I have come up with allocating a two-dimension array like you
did, to make all the rest of his example work. At least, not quickly.
That's my problem. I can't quite think in C yet (I can read it better than
write it). It's still far easier for me to write utils in Basic09, too.
But I admit that I've started converting my window driver to C. Seems that I
have no choice for OS-9000... :-) If/when I ever finish, I might know C.
<sigh> I should've started learning in earnest back when you and Carl did.
kev
There is 1 Reply.
#: 15766 S12/OS9/68000 (OSK)
03-Jul-92 13:32:22
Sb: #15760-C_Question
Fm: Pete Lyall 76703,4230
To: Kevin Darling 76703,4227 (X)
Carl predated me by years, and was my mentor and father confessor when I got
deep into the quicksand. Best C advice? Assume that the compiler does nothing
FOR you... your analysis of C as a macro assembler couldn't be more accurate.
The beauty is that the #defines and functions allow you to move into a level of
abstraction that is truly close to high level language.
It's NEVER too late. Hell - it took me 3-4 years to break the mental block
against C (1983-1986).
Pete
#: 15757 S12/OS9/68000 (OSK)
03-Jul-92 01:36:03
Sb: #15752-#C_Question
Fm: LARRY OLSON 72227,3467
To: Kevin Darling 76703,4227 (X)
Keven,
That is what I need to start doing, looking at the assembly, and getting
familiar with how C compiles these little example routines.
Yes, I'm trying to tackle C again, no hard drive yet but I can set up a
large ram disk, which makes the compile times lots faster. Its only a problem
when the computer crashes, then it is a five minute boot up to load the ram
disk back up again.
Larry
There is 1 Reply.
#: 15761 S12/OS9/68000 (OSK)
03-Jul-92 07:17:45
Sb: #15757-#C_Question
Fm: Kevin Darling 76703,4227
To: LARRY OLSON 72227,3467 (X)
Larry,
If I'm not sure about what something I've written will do, I almost always
compile it to asm source first... a bad mistake will glare out at me and I can
avoid the usual crash/reboot C learning cycle :-)
I've been after someone to port one of those small C interpreters. Maybe even
make it interactive like Basic. Something like that would really cut down on
the C learning time for most people, I think. Quicker feedback.
kev
There is 1 Reply.
#: 15777 S12/OS9/68000 (OSK)
04-Jul-92 03:16:36
Sb: #15761-#C_Question
Fm: LARRY OLSON 72227,3467
To: Kevin Darling 76703,4227 (X)
Kevin,
I'm not real familiar withOSK assembly yet, so the mistakes wouldn't glare
out at me like 6809 assembly would. Its just going to take time and work to get
the hang of it.
While I have you here, I was wondering if there will be an SS.Tone like
syscall for K-Windows. Digital recording and playing is great but I would think
that sometimes you would want to have the computer generate some sound.
Larry
There is 1 Reply.
#: 15779 S12/OS9/68000 (OSK)
04-Jul-92 03:34:09
Sb: #15777-#C_Question
Fm: Kevin Darling 76703,4227
To: LARRY OLSON 72227,3467 (X)
Larry,
Oh. Oh! I don't know why I assumed you were compiling on the 6809 instead of
under OSK.
No SS.Tone thingie yet, altho I've done parts of it. A lot of features are
being worked on in parallel. Either because they're inter-related, or simply
because they're too boring to do all at once <big grin>.
There is 1 Reply.
#: 15784 S12/OS9/68000 (OSK)
04-Jul-92 14:50:25
Sb: #15779-C_Question
Fm: LARRY OLSON 72227,3467
To: Kevin Darling 76703,4227 (X)
Kevin,
Will it be just like SS.Tone, or will it have more capability ? The reason
I ask,thinking of porting this sound editor that I have been working on.
Larry
#: 15748 S14/misc/info/Soapbox
02-Jul-92 09:21:26
Sb: CoCo System For Sale
Fm: Lee Veal 74726,1752
To: All
Attention:
CoCo3 System For Sale!
Includes: CoCo3 128K
FD502 Controller
w/ 1 Disk Drive
CM-8 RGB Monitor
DMP-130 Printer
Deskmate 3
2 Game cartridges
2 joysticks
They want $300 for whole system package.
They do not want to break up the system.
The system is practically new, it was used
very sparingly.
If you're interested leave me an E-Mail message and I'll give you their phone
numbers.
------------------------------------------------------------------------
_ _ _____ _
_// ' ) / //
__/ _ _ ( / _ __. //
(_/\__ </_</_ \/ </_(_/|_</_
#: 15751 S12/OS9/68000 (OSK)
02-Jul-92 23:07:41
Sb: #Pointer help
Fm: Bob van der Poel 76510,2203
To: all
Can someone confirm that I'm doing this correctly? I'm trying to declare a
pointer to an array of ints. I have a index which I load dynamically, so I find
I have to do declare my pointer like this:
int (*index)[DIM2];
This lets index act the same as if static storage was allocated with:
int index[DIM1][DIM2];
I can now do something like index=malloc(sizeof(int)*DIM1*DIM2).
This appears to work, but seems to be highly un-intutitive! Is there no way I
can actually have [DIM1][DIM2] in the declaration, or at least [DIM1]? I just
get worried that a year from now when I change the index structure I'll screw
the pointer.
Also, I'm not too impressed by the way I have to calculate the size of the
array in the malloc(). But I don't see anyway around this.
There are 3 Replies.
#: 15754 S12/OS9/68000 (OSK)
03-Jul-92 00:20:57
Sb: #15751-Pointer help
Fm: Pete Lyall 76703,4230
To: Bob van der Poel 76510,2203 (X)
Bob -
If you're looking to allocate a dynamically sized array, then you pretty much
MUST use malloc() (or a variation).
Example:
Allocate an array of pointers to type int. The array will be 'num_required'
long:
num_required = 49; /* or whatever */
.....
int *array_ptr; /* pointer to a type of int */
array_ptr = malloc(num_required * (sizeof (int *)));
You now have an array of pointers to int that may be accessed either in the
form array_ptr[0...num_required-1] or array_ptr+0...num_required-1.
Pete
#: 15758 S12/OS9/68000 (OSK)
03-Jul-92 03:25:00
Sb: #15751-Pointer help
Fm: Bruce MacKenzie 71725,376
To: Bob van der Poel 76510,2203 (X)
Bob,
Yes, the way you've done the declaration is precisely the way it should be
done. The declaration becomes clearer when one thinks of a 2D array as 1D
arrays nested inside a 1D array. "int (*index)[DIM2]" declares index to be a
pointer to an array of integer arrays of size DIM2 in the same way that "int
*index" would declare index to be a pointer to an array of integers. In either
declaration the number of objects pointed to is irrelevant to the declaration,
only the size of the individual objects pointed to matters (the size of an
array of DIM2 integers in the first case or the size of a single integer in the
second case). In a program one may want to assign the pointer to arrays of
various lengths and indeed one can:
int (*index)[20],yes[5][20],no[10][20];
.
.
.
if(getchar()=='y')
index=yes;
else
index=no;
index[2][3] would evaluate to the appropriate element in either array. (Of
course index[6][1] would be out of bounds if index were pointing to the yes
array) You needn't worry about changing what you #define DIM1 and DIM2 to be.
As long as you've used the macros consistently in your program changing their
values should not cause any problems.
#: 15767 S12/OS9/68000 (OSK)
03-Jul-92 14:03:00
Sb: #15751-#Pointer help
Fm: Bruce MacKenzie 71725,376
To: Bob van der Poel 76510,2203 (X)
Bob,
Another thought: the data structure of your 2D array could be made more
explicit in your source if you use calloc() rather than malloc to set aside
memory for the array:
index = calloc( DIM1 , sizeof( int[DIM2] ))
This is functionally equivalent to what you have done with malloc, but here
calloc() explicitly sets aside memory for DIM1 arrays of DIM2 integers.
There is 1 Reply.
#: 15848 S12/OS9/68000 (OSK)
09-Jul-92 20:21:30
Sb: #15767-#Pointer help
Fm: Bob van der Poel 76510,2203
To: Bruce MacKenzie 71725,376 (X)
Thanks for the confirmation, Bruce. (And Pete and others...). Sometimes I start
to think that I'm really understanding C, and then there is yet another thing
to learn. Fun.
BTW, the book you keep quoting from sound like it belongs on my desk. Happen to
know a price and ordering place?
There are 2 Replies.
#: 15856 S12/OS9/68000 (OSK)
10-Jul-92 08:49:53
Sb: #15848-#Pointer help
Fm: Pete Lyall 76703,4230
To: Bob van der Poel 76510,2203 (X)
Bob -
Haven't got the book/ISBN nearby, but the cost is about $25. Definitely worth
it.
Another book which I have come to rely on heavily is the series by
Osborne/McGraw Hill ... in my case it's "C++ The Complete Reference". I believe
there's a C only version as well. Has both tutorial sections and reference
sections. Explanations are _good_, and there are usually examples. Just the
sort of thing for when you're sitting there saying "Now how does X work?" It's
about $35, and also worth every penny.
Pete
There is 1 Reply.
#: 15867 S12/OS9/68000 (OSK)
11-Jul-92 21:22:33
Sb: #15856-Pointer help
Fm: Bob van der Poel 76510,2203
To: Pete Lyall 76703,4230 (X)
Speaking of books... I have 'C, The complete Reference' by Schilt. Yes, it is
very good. Based on that I also ordered Schilt's 'Advanced C, 2nd ed.'. Sort of
a waste of $$ since most of it was already in 'Complete'.
Other books I use a lot are 'C, A reference Manual' by Harbison & Steele. And
did someone mention good old K&R in this discussion?
#: 15859 S12/OS9/68000 (OSK)
10-Jul-92 17:52:22
Sb: #15848-Pointer help
Fm: Bruce MacKenzie 71725,376
To: Bob van der Poel 76510,2203 (X)
Bob,
You're very welcome. If you're refering to Gehani, I take it you found
the tutorial. Your question inspired me to put a few thoughts together.
I picked up Gehani at Walden Books,or perhaps B. Daltons, several years
ago. It cost around $20. I'm by no means an authority on C texts. There are
many out there and I'm sure others might serve as well. All I have to compare
Gehani to is Purdum, which I bought back in 84 when I first got C for the COCO.
I can't recomend Purdum at all, I think his presentation is very unorganized
and sloppy. I also have THE C PROGRAMMERS HANDBOOK by Thom Hogan which is very
useful as a quick reference on questions such as "what the heck is the bitwise
exclusive or operator?" It is not and does not purport to be a primer on how
to program in C however.
#: 15764 S12/OS9/68000 (OSK)
03-Jul-92 12:03:34
Sb: #reply to mess # 15716
Fm: Keith H. March 70541,1413
To: 76703,4227 (X)
Friday July 3, 1992
Kevin;
I also go along with Bobs idea!
>Also, why not have the initial mode as an option (maybe set in
>/dd/sys/keyboard.env). >This file could also have other options in it (like
having the Fkeys generate >values, instead of being screen selectors).
How about using the <SCROLL LOCK> key (this key is not used, is it?) to forward
cycle the windows and maybe <CTRL>-<SCROLL LOCK> or <ALT>-<SCROLL LOCK> to go
backwards.
Keith
CIS:70541,1413 INTERNET:keith@khmarch.bowlgreen.oh.us
There is 1 Reply.
#: 15774 S12/OS9/68000 (OSK)
04-Jul-92 00:07:19
Sb: #15764-reply to mess # 15716
Fm: Kevin Darling 76703,4227
To: Keith H. March 70541,1413 (X)
Keith - of course SCROLL LOCK turns on/off its light (unless CTRL is down), so
to use it for flipping screens a person would want to cover up the light :)
I keep thinking that one key should wake up a background "master" process which
could have a menu for forking new shell windows, etc. Gotta play with the idea
some tho.
I go along with Bob and your idea of makingn the keybd programmable... just not
sure if it'll be in v42 ;)
thx! - kev
#: 15768 S12/OS9/68000 (OSK)
03-Jul-92 14:56:22
Sb: C code on the MM/1
Fm: Keith H. March 70541,1413
To: All
C guru needed...
Could someone show me how to take this code (RICK ADAMS UUCP Ver.AK.
The following c from dscriptc
#include <stdi.h> #inc <sgnal.inclue <sgsat.h>
ern int port extern car phon[80ern int ebuglv; exten inthook
struct sgbuf ot;
KPPED COE>
case k':
/* See pae B-12 in 8K appedixes anual*/
stat(0, prt, &opt);
pt.sgbaud =00; /*50 baud setstt(0, prt, &ot);
write (ort, \0", 1;
/* Switch o org. bau rate *
pt.sg_aud = 0; /* 400 ba setstat(0 port, &op f (deuglvl>= 2)
pritf("<BREAK");
reak; case'K':
getstaort, opt);
opt.sg_aud = 00;/* 50 aud /
setstt(0, prt, &op);
write port, \0", 1;
/* Sitch t org. aud ra optsg_baud = 1; /* 9600 aud */
settat(0,port, &pt);
if(debuglvl > 2)
pintf"<BREA>"); brea; MORE CODEGOES HEE <EOF
#: 15770 S10/OS9(CoC)
03-Ju-92 17:45:43
Sb: #15558-pinter
Fm: tom farrow 7271,543
To: Mzzi 7676,271 (X)
Thanks fte info Tom .
#: 15786 S12/6800 (OSK)
05-Jul-923:6
Sb: Lout text formater
Mrk Grifith 7070,41 To: All
ve Wegrt just ploaded akage caled "Lout"into L2. This iprbably he besttext frmatte you wileer nee for yu OSK sstem. t
outputs te mus beautifu postscript cd is ver easy touse. Thinkof it
as the UNIX trof, bu bette. Thepackagealso isfull spport or
generatingmath quatons, chart, and line rawing fr graphat
Postscript ormated dcdocs arw includedand are an xcellent xample of tat
this pecan d.
I would suggesteveryoe who wns anOSK mchine o dowload ths appication istall nd leat as soonpossile. Even i you dont havea
postscriptprintr, yu canualy get acess t one place. Perhaps ths
will spur meon to finish he port ofscipt that ike Haaland started. Till llow sendng lout's ostscritput diectly to a dot-matrix printer.
All-in-all this s a suerb pakage. robablythe best SK appliction I have seen y
Mark
#: 15788 S14/misc/info/Soapbo
05-Jul-2 14:9:25
Sb: No pace in libary
Fm: Bruc MacKenie 7175,376
To: sysop (X)
The library is full.
#: 15S3Languaes
07-Jl-92 1:49:0
Sb: #C++ forOS/9on 68020
Fm: Graham Ullrch/C.B6506,203
To:l
I'm trying to find any type ofC++ cmpilerfor OS9 whic prodces cde for
the 68amly (spcificaly the 8332). Topiler cn be arnt en
compiler whch prouces (likecfron), a DS or SPAd OS/9 cross-compilr, or20 O/9 base compler whih prduce0 cod.
T of te (tnuous) leade foundso far hav been o chec into NU C++ and ATT's cront. Unforunately mucess rate n finding ou anything ab these proucts is ear zro.
If you can hep out bvingme infomationabout, r telphone umbersfor
these grops, or if know aout soe other C+ produ OS/9, pease help
me out. I'm af just won't cut it for thi project
Thanks,
Graham
There are 2 Replies.
#: 15852 S3/Languags
09-Jul-92 23:0:40
Sb: #15804-C++ fo OS/9 n 6800
Fm: Bob almer 7646,2156
To: Graham h/C.B.,C 76506,203 (X)
I have not d in the dowload library here but eems to m that the compilers are in the DLs. If not ad if you hve access thy a the COCO
SIG OS( subsection on te DELPI servie and als Iold can be foundon
othrvices. GN has bot an excellent C copiler comlete with swtches
for 6800 and 68020 (alhough I cnnot say wha the code geneated wll do tke use f the full cmplement o added intruc onlythat it wil not
run on a 680the 68020 ws set). Thecompiler uss the sandar Microare
embler to ceate the machinecode but produes coe which uns quite a faster from a few benchmarks I hae done. he C++ is ae file but snce I
have not yet gotte aroundto learthe anguage I tae it on fath that th
thing works. Maybesoy. Right fter I get a e o just plain C, sy
in 2000. Bob. OOPS - ean ay - of couse - has bth a C (GCC and C++
compilr.
#: 15862 S3/Languages
11-Jul-92 05:59:52
Sb: #-#C++ for OS/9 on 6802
Fm: Adalbert Gubo 10042,161
To: Graam Ullrich/C.B.,CO 037 (X)
Hallo Graham,
Eltec in Germany horted the GU++ C Copileth GN Debuger
The Addrs: ELTC Eletroni
Galieli Gaieleoase 38
650MANZ Gerany
Bert
There is 1 Reply.
#: 1586S3/Lnguages
1ul-92 23:31:3
Sb: #15862-C++for OS9 on 8020Fm: Gaham lrich/C.B.CO 76506,037
To: Adalbet Guo 10002,1161
Bert,
Is there any way snd a mesage o ELTECthroughCompuerve?
nks fr your elp.
Graham
#: 15805 S12/OS9/68000 (OSK)
0l-92 1:37:25 Sb: #GNU GCCC comiler v.40
Fm: Graam Ullich/C.B650,2037
To: Jim Sutenmeir 70673,174 (X)
Jim,
I'm looking for a C++ compler wich prouces 802 coderunnig on the O-9
platform. ploaded NU GCC v1 in Feruary, ad from wha I can determine, ths compler ma do te trik for e. My dent envronment
is a DOS machne communcating a 6832 (6802 derivative compter vi
PC-Bridge. Do yo hav any ideethr GNU C++ wll work? An if it wil, how
good is he comildocs,librar, etc. Is t suport for th
compiler? Is there e-leel deugger? Wht A+ verion dos the
compilr supprt?
Sure, I'm aking alot ofquestios, bu otal of,84 bytempler is quie a heav package tooad ust for evluation ps.
Thanks for any infon you canpass alon.
Graham
There is 1 Reply.
#: 15808 S/OS9/8000 (OS)
-Jul-92 1:25:51
SJim Sutemeier 70673,1754
To: Graham Ullrich/C.B.,CO 76506,2037 (X)
Sorry, but I can't help you much as far as the C++ Compiler is concerned. I do
know it works on the 68070, and I hear that it works on the 68000, but the
68020 & derivatives, I know nothing about.
Wish I could suggest you get 1/2 the package, and try that, but the libraries
and stuff are scattered throughout the archives.
Sorry I can't help any more....
jim
There is 1 Reply.
#: 15831 S12/OS9/68000 (OSK)
08-Jul-92 22:36:52
Sb: #15808-#GNU GCC C compiler v1.40
Fm: Graham Ullrich/C.B.,CO 76506,2037
To: Jim Sutemeier 70673,1754 (X)
Jim,
What hardware and software platforms have you run (or heard about) the GCC
compiler on? Is this OS-9 on a 680x0 machine?
Maybe I'm really out of it, but I've never heard of the 68070. Is that the
latest Motorola chip in the 680x0 series, or was that a typo?
Thanks for the information!
Graham
There is 1 Reply.
#: 15845 S12/OS9/68000 (OSK)
09-Jul-92 15:11:20
Sb: #15831-GNU GCC C compiler v1.40
Fm: Jim Sutemeier 70673,1754
To: Graham Ullrich/C.B.,CO 76506,2037 (X)
The 68070 is a 68000 clone, Graham, and is completely compatible with 68000
code. The 68070 is produced by Signetics.
I've heard about the GCC Compiler running on 68070 and 68000 platforms, and
THI{NK I saw a note in Usenet that it was used on a 68030.
jim
#: 15806 S12/OS9/68000 (OSK)
07-Jul-92 11:37:33
Sb: #OS-9 C++ compiler
Fm: Graham Ullrich/C.B.,CO 76506,2037
To: Robert Heller 71450,3432 (X)
Robert,
I noticed in the description of your uploaded Home Librarian v1.0 that you used
C++ to develop the program. I'm looking for a quality (or just any) C++
compiler to create 68020 code for OS-9. Can you give me some additional
information about your development environment and the tools you used?
Thanks,
Graham
There is 1 Reply.
#: 15807 S12/OS9/68000 (OSK)
07-Jul-92 18:10:53
Sb: #15806-#OS-9 C++ compiler
Fm: Robert Heller 71450,3432
To: Graham Ullrich/C.B.,CO 76506,2037 (X)
I used the G++ compiler (downloaded from the InterNet). MicroEMacs 3.10
(haven't) snarfed 3.11 yet). There is at present no symbolic debugger
available for use with G++ under OS-9. I used Microware's srcdbg, mostly in
assembly level, and lots of printf's err <'s to cout.
I prepared the documentation using LaTeX - OSK TeX (Common TeX). Microware's
make using the -b option and explicit rules to handle g++.
Hardware is a Force CPU-30 (20mhz 68030/68882, 6U VME system).
Robert
There is 1 Reply.
#: 15830 S12/OS9/68000 (OSK)
08-Jul-92 22:36:46
Sb: #15807-#OS-9 C++ compiler
Fm: Graham Ullrich/C.B.,CO 76506,2037
To: Robert Heller 71450,3432 (X)
Robert,
What version of the GCC compiler did you use? Version 1.4 is in the Compuserve
OS-9 library, and there is apparently a version 2.2. The Free Software
Foundation told me that v1.4 is their current "stable" compiler release, and
v2.2 is their current "beta" release.
Thanks for the information.
Graham
There is 1 Reply.
#: 15847 S12/OS9/68000 (OSK)
09-Jul-92 18:24:04
Sb: #15830-OS-9 C++ compiler
Fm: Robert Heller 71450,3432
To: Graham Ullrich/C.B.,CO 76506,2037 (X)
gpp -v tells me I'm using g++ 1.39.1 (based on gcc 1.40).
I have not tried to create 68020 code (wanting to produce programs that will
run on lowwer end machines (i.e. plain 68000's)). My system is a 68030/68882
system. I *think* gcc will produce '020 code if told to, but defaults to
68000. I don't know about g++. My understanding of the differences in the
user-mode instruction sets between the 68000 and 68020 is that except for some
extended addressing modes and a full 32x32 bit multiple and divide, there is
not much difference between a 68020 and a 68000. The '030 only adds in an
on-chip MMU, which only effects super-mode code (i.e. kernel and SSM stuff).
*I* have not noticed much performance difference between programs compiled in
'020 mode vs. '000 mode (I have not done formal benchmarks, just gut feeling -
no noticable delays with '000 code).
Robert PS: I downloaded gcc and g++ from hermit.cs.wisc.edu (something like
that). RPH
#: 15812 S1/General Interest
08-Jul-92 00:50:57
Sb: #Smartwatch
Fm: randy pischke 75460,205
To: lee veal
Lee- I downloaded the SMART.AR file that you uploaded. Upon reading the docs I
noticed that the drivers are designed for the MPI, which I am not using. I want
to put the Smartwatch in my J&M controller as it has both 24 and 28 pin
sockets. Do you know if it will work? I only use RSDOS in the 24 pin socket but
am hoping that the clock can be read from the 28 pin socket even though it
isn't selected.
There is 1 Reply.
#: 15821 S1/General Interest
08-Jul-92 18:02:41
Sb: #15812-#Smartwatch
Fm: Lee Veal 74726,1752
To: randy pischke 75460,205 (X)
Randy,
First, the OS9 SmartWatch drivers will only be able to read from the switch
selected ROM socket. As I recall, the ROM switch essentially just switched
power from one ROM socket to the other. Therefoae, only one ROM socket can be
active at a time. The 24-pin RSDOS ROM can run from the 28-pin socket, and I
think you plug the RSDOS ROM in so that the first four pins are left empty.
Basically, it would look like this from the pin 1 side...
Notched )----------------------
pin#1-|-|-|-|-|-|-|-|-|-|-| <---- RS-DOS ROM
ends )--------------------------
1-|-|-|-|-|-|-|-|-|-|-|-|-| <---- SmartWatch (c)
--> )--------------------------
|-|-|-|-|-|-|-|-|-|-|-|-|-|
pin# 1 x <---- first four pins
(two on each side)
Also, I'd bet that as long as you don't have any other devices addressed (by
using a Y-cable or some sort of mini-bus in the J&M controller, for instance)
at the location where MPI's slot select byte is located, then the slot select
coding in the SW routines shouldn't bother anything.
On the other hand, if it does cause anomalous problems, then all you should
have to do is NOP the slot select coding in the routines. In SWCLOCK2, for
instance, the code starts at $01EB and looks like this:
Addr 0 1 2 3 4 5 6 7 8 9 A B C D E F 0 2 4 6 8 A C E
---- ---- ---- ---- ---- ---- ---- ---- ---- ----------------
0100 E034 30AE ....
.... ** **** ****
01E0 3401 1A50 B6FF 7FD6 9034 0686 11B7 FF7F 4..P6..V.4...7..
01F0 C4FC F7FF 9096 9185 0126 0CF6 FFA7 3406 D|w....F.&.v.'4.
If worse comes to worse, you could change the 8611B7FF7F to 1212121212, but
according to the guy that I talked to, you shouldn't have to resort to this.
The coding for selecting the MPI slot is exactly the same in all the various SW
routines (SWCLOCKn, GETCLKn, SWSETn), it's just in different places.
Lee
There is 1 Reply.
#: 15822 S1/General Interest
08-Jul-92 19:00:33
Sb: #15821-Smartwatch
Fm: randy pischke 75460,205
To: Lee Veal 74726,1752 (X)
Lee-
Thanks for the information. It really helps me to understand how things work.
You are correct that the 24 pin ROM need to have the top four pins of the 28
pin socket left open. I have a 28 pin ROM that was modified to work in a 24 pin
socket and it has the top 4 pins bent up and tied together.
Randy.
#: 15815 S1/General Interest
08-Jul-92 05:11:10
Sb: Delphi poll results
Fm: Ken Flanagan 75460,2514
To: Carl Kreider
Carl, I have uploaded the results of the poll from Delphi. They are in area
14. The file is called CARL.TXT.
#: 15825 S12/OS9/68000 (OSK)
08-Jul-92 20:33:27
Sb: #15503-wind38 ??
Fm: BRUCE MOORE 70075,143
To: Kevin Darling 76703,4227 (X)
Just got preliminary version of kwindows today. Have lots of questions since
no docs but the most important is :
How (or where) do I patch the keyboard driver to make the arrow keys work? I
want to use them for dynastar and a basic program we use to manage our
printshop
I want them to output the same codes as the coco keyboard 8, 9, 10, and 12 I
beleive.
I DO have the program running !
#: 15832 S10/OS9/6809 (CoCo)
08-Jul-92 22:42:54
Sb: #Shell+
Fm: Ian Hodgson 72177,1762
To: All
OK, I just came across a strange problem. After lazily putting it off for
years, I finally patched Shell+ 2.1 to turn on wildcards. Worked fine, except
when I went to use a memory script that I have been using for many months. The
script reads like this:
chd /r0
prompt Directory?
var.2
prompt File (no extension)?
var.0
tmode .1 -echo
prompt Keyword?
var.1
display d a
tmode .1 echo
crypt %2/%0.cr %1
rename crypt.out %0
It works fine with wildcards OFF, but with wildcards ON the first and third
prompts do not display (the second one does). Otherwise it seems to work fine.
I turned wildcards back OFF again and, once more, the script works fine. What?
This does not make much sense.
In case it matters, I don't use the provided modpatch script to make change,
but simply toggle the value of 04DC in Shell between 26 and 27 hex. Any
suggestions?
There is 1 Reply.
#: 15833 S10/OS9/6809 (CoCo)
08-Jul-92 22:49:13
Sb: #15832-#Shell+
Fm: Pete Lyall 76703,4230
To: Ian Hodgson 72177,1762 (X)
Ian -
Could it be the question marks???????????
Pete
There is 1 Reply.
#: 15834 S10/OS9/6809 (CoCo)
08-Jul-92 23:08:11
Sb: #15833-#Shell+
Fm: Ian Hodgson 72177,1762
To: Pete Lyall 76703,4230 (X)
Pete,
I was just coming back on to mention that. What the devil is wrong with using
the question marks at that point? Why does the effect differ? On the second
prompt, I get File (no extension)m t which seems odd. I realize that the ?'s
are single character wildcards, but can't see why they have the effect that
they do.
Ian
There are 2 Replies.
#: 15837 S10/OS9/6809 (CoCo)
09-Jul-92 06:39:42
Sb: #15834-Shell+
Fm: Bill Dickhaus 70325,523
To: Ian Hodgson 72177,1762 (X)
Ian,
It is the question marks. I remember this problem from many years ago, and I
think I finally gave up and removed the question marks from things like this.
Its been so long I can't remember if 2.1 with that patch allowed for
temporarily disabling the wild cards (something like a special character at the
beginning of the line). I do remember that the results were sometimes not what
was expected, like the example you gave.
Bill
#: 15840 S10/OS9/6809 (CoCo)
09-Jul-92 08:46:42
Sb: #15834-Shell+
Fm: Pete Lyall 76703,4230
To: Ian Hodgson 72177,1762 (X)
Well, I can't speak for SHELL+, but the unix shell would see that as a command
to run the prompt command with an argument of any filename that matches the
template 'Directory?' or whatever...
Try enclosing the question + text in quotes (single/double) and see what
happens.
Pete
#: 15861 S1/General Interest
11-Jul-92 02:49:42
Sb: #C Books
Fm: LARRY OLSON 72227,3467
To: Pete Lyall 76703,4230 (X)
Pete,
I picked up that book yesterday, and from the looks of it so far
I will be spending alot less time on here asking dumb questions. This
one is very informative and easy to follow.
I saw your mention of the book C The Complete Reference, which was
funny because I had seen that book and picked it up also.
The names have changed a little, C Primer Plus is now New C Primer Plus
and the other one is C The Complete Reference Second Edition.
For others that might be interested:
The Waite Group's
New C Primer Plus
ISBN 0-672-22687-1
by Mitchell Waite and Stephen Prata
$29.95 U.S. / $37.95 CAN.
published by SAMS
copyright 1990
This edition covers ANSI C, UNIX, Microsoft C and Turbo C
C The Complete Reference
Second Edition
ISBN 0-07-881538-X
by Herbert Schildt
$28.95
published by Osborn,McGraw-Hill
copyright 1987, 1990
This edition covers C++ and ANSI C
Thanks again for the tip on the book.
Larry
There is 1 Reply.
#: 15863 S1/General Interest
11-Jul-92 08:20:00
Sb: #15861-#C Books
Fm: Pete Lyall 76703,4230
To: LARRY OLSON 72227,3467 (X)
Thanks for the update on the book titles Larry. It looks like you'll be
spending your weekend reading!
Enjoy them - they're both excellent.
Pete
There is 1 Reply.
#: 15864 S1/General Interest
11-Jul-92 10:20:05
Sb: #15863-C Books
Fm: LARRY OLSON 72227,3467
To: Pete Lyall 76703,4230 (X)
Pete,
Yes, reading and tyeing <g>. I thought about ordering the disks that are
available for both books, but then entering all these examples by hand I think
will help it stick.
Larry
#: 15866 S15/Hot Topics
11-Jul-92 21:13:14
Sb: #OS9 Underground
Fm: Jim Sutemeier 70673,1754
To: ALL
I FINALLY had the opportunity to watch a video of the Atlanta CoCoFest last
April.
I thoroughly enjoyed the meeting that Frank, Ed and Paul had.
The person who taped the meeting of 'the big three' also taped the meeting that
Kevin Darling had.
Kevin said one thing there in the meeting room, and that is the purpose of this
message.
He was talking in reference to new magazines that come onto the marketplace
from time to time. He said (and I quote) "If you wait 3-6(-12) months to
subscribe to the new magazines, then YOU'VE KILLED THE MAGAZINE".
Well, we've got a new kid on the block - the OS9 Underground, that is just
starting to get off wobbly feet, and really produce some quality stuff.
Are we gonna let it die by not subscribing??
It's up to each of us not to let this happen to this magazine. It's only $18 a
year, so it's no back breaker on the price end.
Call 818:894-0012 to order your free copy of the magazine. If you like it,
then place your order.
jim
There is 1 Reply.
#: 15881 S15/Hot Topics
12-Jul-92 21:15:10
Sb: #15866-OS9 Underground
Fm: Bill Dickhaus 70325,523
To: Jim Sutemeier 70673,1754 (X)
Jim,
I did get a free copy already, and was impressed. You're right, we all need to
subscribe, and NOW! I'll be sending my order out first thing next week. Thanks
for the reminder.
Bill
#: 15873 S12/OS9/68000 (OSK)
12-Jul-92 14:42:22
Sb: tc70 Kwindows
Fm: BRUCE MOORE 70075,143
To: Kevin Darling
I have patched the keydrv to make the arrow keys work on my prelim ver of tc70
kwindows. I have also succesfully added fonts via the mm1 35 fonts file from
delphi. Even the gifshow file viewer works but.... colors are all wrong. The
colors for
the color command supplied are wrong.. looks like green and red are
interchanged.
also f9 and f10 circle thru the windows but in the same direction. Would be
nice
if the went forward, other backward.
Had a little trouble getting kwindows to work with dynastar but the answer came
from
KSCALES: check tmode and see that pag=26. I then realized my screens have 26
lines! Who nice.
How would the gifshow file and the color command colors be fixed?
looking forward to the new enhanced kwindows for tc70!
#: 15878 S12/OS9/68000 (OSK)
12-Jul-92 18:10:05
Sb: #printf problem
Fm: Bob van der Poel 76510,2203
To: all
Has anyone else noticed a problem with the printf() family? The following code
fragement works fine by itself, but in a large program it doesn't:
switch (fmt){
.....
case 'H': sprintf(buff,"%X",value);
break;
case 'h': sprintf(buff,"%x",value);
break;
....
The entire format loop works fine--expect when the %X format is used. In this
case a single 'x' is printed. However, %x, does work alright. I've put a bunch
of debug code (printf()s) in the real program and the printf() react the same
way. For some reason, uppercase hex doesn't work. However, when I just extract
the code out and stick it in a test program, all works alright. I've really
pulled my hair on this one--even checked the crc while the program is running.
No luck. I've cobbled a work-around for now by using %x and then converting the
string to uppercase if fmt=='H'.
Either there is a bug in sprintf(), or my program is cobblering something. Any
ideas?
There is 1 Reply.
#: 15886 S12/OS9/68000 (OSK)
13-Jul-92 08:49:05
Sb: #15878-#printf problem
Fm: Mark Griffith 76070,41
To: Bob van der Poel 76510,2203 (X)
Bob,
Why not try reversing the two sprintf lines...i.e., do the lower case 'h' first
and then the uppercase. If there is a pointer clobbering something, it should
make the 'x' statement not work then. This is what I expect is the problem (a
wild pointer).
Mark
There is 1 Reply.
#: 15897 S12/OS9/68000 (OSK)
13-Jul-92 23:35:17
Sb: #15886-printf problem
Fm: Bob van der Poel 76510,2203
To: Mark Griffith 76070,41 (X)
Thanks Mark. I already tried the obvious stuff like moving code around. No
help. I even used debug to monitor things and discovered that the call to
sprint() is being set up properly. Even checked to verify that the register
pointing to the format specifier (D1) actually pointed to the correct data. It
did. I think that a wild pointer might be the problem, but can't figure out
things. If the pointer is corrupting the program (including sprintf()) then the
crc of the program should change. It doesn't. So, I suppose it could be mucking
up a static buffer used by sprintf() but that is pretty hard to track down...
Be nice to have source for the MW library. Oh well, I'll probably find another
nasty bug and trace this to it!
For others reading--any suggestions are appreciated!
#: 15879 S12/OS9/68000 (OSK)
12-Jul-92 18:10:16
Sb: #SCF Buffer size
Fm: Bob van der Poel 76510,2203
To: all
Could someone refresh my tired gray cells? How de? one change the input &
output buffer sizes for the serial ports on the mm/1? I thought I'd do it
quickly (of course this was at 3am) via xmode. But I don't believe the size is
contained in the descriptor. Annoying thing is that there have been some
messages fly by in the past--and I choose to ignore them...
Thanks.
There is 1 Reply.
#: 15883 S12/OS9/68000 (OSK)
12-Jul-92 21:37:01
Sb: #15879-#SCF Buffer size
Fm: Bill Dickhaus 70325,523
To: Bob van der Poel 76510,2203 (X)
You have to use the moded utility (I keep forgetting its there!) and make sure
that you have the right moded.fields file in /DD/SYS. This only works on files,
though. Somebody needs to hack on xmode to do this real time....hint...hint :-)
Bill
There is 1 Reply.
#: 15896 S12/OS9/68000 (OSK)
13-Jul-92 23:35:06
Sb: #15883-SCF Buffer size
Fm: Bob van der Poel 76510,2203
To: Bill Dickhaus 70325,523 (X)
Bill, I tried moded and thought that I had the correct file. Of course, I
didn't. Works fine now that I have the right file! Thanks. (So, when are you
going to pos the new xmode <grin>.)
#: 15880 S10/OS9/6809 (CoCo)
12-Jul-92 19:51:12
Sb: #pcdos
Fm: Denise Tomlinson 71021,3274
To: bob santy
I downloaded a os9 file to my pc because I have only one modem I thought i
could transfer it to coco with your transfer program called pcdos. I forgot it
was in binary instead of ascii, and it also was an "arc" file. It won't unarc
on an os9 disk. Could I hook a null modem cable between the bit banger of the
coco and the com2 port of my pc and transfer the file? I have a os9 terminal
program and also one for the pc? What pins on the two computers would I use?
I am fairly adept at making things for the coco with a soldering iron!
Would this work? I believe the file as it sits in my pc harddrive is an exact
copy of the one here that I downloaded I evidently am loosing data with the
"pcdos" program because it's binary instead of ascii text. Thanks, Denise
There is 1 Reply.
#: 15882 S10/OS9/6809 (CoCo)
12-Jul-92 21:36:45
Sb: #15880-pcdos
Fm: Bill Dickhaus 70325,523
To: Denise Tomlinson 71021,3274
Denise,
For binary files, make sure to use the -raw option of pcdos, otherwise pcdos
assumes its an ascii file.
Check out the file SERIAL.TXT for some good explanations and examples of
hooking up different computers and equipment to the various serial ports of the
CoCo. I can't remember which library its in, but try this command in any of the
libraries:
bro all serial.txt
Bill
#: 15887 S1/General Interest
13-Jul-92 11:31:51
Sb: #14865-New AR Developments
Fm: Lee Veal 74726,1752
To: Carl Kreider 71076,76
These questions, as posed in the Delphi poll, on AR's enhancements received
several replies. However, not all persons interested AR enhancements subscribe
to the Delphi services. This is a response from a local BBS users here in the
Dallas, Tx area. The comments are his not mine.
Lee
-----------------------------------------------------
WHAT SHOULD THE DEFAULT COMPRESSION BE? Carl Kreider is thinking of updating
AR. He would like to know what the users want for the default compression
though. Do you want the default to remain at 11 bits so that it remaini
compatible with OS-9 Level I, or do you feel the default compression should be
12 bit so that binary files can be compressed. I believe he is planning on
adding the 12 bit code, but wants to know what you want the default compression
toggle to do. Also, if you leave a comment, please mention whether you would
like the attributes saved with the file, and any other features you would like
added, changed, or removed. The results will be given to Carl on CIS.
10-Jul-92 05:00pm Subject: Re: AR Developments...
My comments to Mr. Krieder:
I like the unsanctioned version of AR1.5b. It's flawless (so far). I like the
default to 12 bits, but I wouldn't be bothered by the 11 bit default if that
were the way it would go.
Automatically sensing if a compression was good or not (i.e. compress all
files, check to see if the result was larger, if so: rewrite) is 100% necessary
in my opinion. I have compressed MANY MANY binaries using AR1.5b with very few
not compressing. And even so, the ones that didn't compress well wene "stored"
without a noticably lengthy loss in time. Time during compression does not
matter half as much as time during extraction anyway!
ATTRIBUTES ARE 100% necessary!!!! Don't even think about not puating it
in...(please...)
Daniel Hauck
#: 15888 S1/General Interest
13-Jul-92 14:30:21
Sb: Programmer Wanted
Fm: Miguel Payet 70702,731
To: all
A company in Peru is looking for a programmer to accomplish the following job:
1. Conversion of OS-9 propietary format graphic files to industry-standard
PCX format.
2. Transfer of converted files from OS-9 CAD system to Novell NetWare file
server
3. Archiving and deletion of unneeded CAD files.
4. Scheduling and automatic operations of the above after normal business
hours.
If you are interested, please respond by email to 70702,731 for more
information.
Regards, Miguel
#: 15895 S15/Hot Topics
13-Jul-92 23:00:05
Sb: #6309???
Fm: DOUG 72667,1433
To: all
Hey all you gurus... I've been off the circuit for a while. What's with this
6309? Data Sheets available? Supply sources??? Tell me more.... Doug
72667,1433
There is 1 Reply.
#: 15902 S15/Hot Topics
14-Jul-92 00:16:21
Sb: #15895-6309???
Fm: Bill Dickhaus 70325,523
To: DOUG 72667,1433
Doug,
Check out 6309.TXT in LIB 1, which explains what the 6309 is all about.
There are some other related files, try the following command in any of the
data libraries:
bro all /key:6309
Bill
#: 15903 S12/OS9/68000 (OSK)
14-Jul-92 00:32:49
Sb: Atari? Windows?
Fm: Mark Sours 70372,1370
To: Kevin Darling
Kevin,
Are you going to port your windows routines to the Atari? If so
when can we expect it? Last I read you were, has that changed..
I got off the mainframes and onto sun sparcs and I hate to come
home to the windowless atari...
Later
#: 15904 S12/OS9/68000 (OSK)
14-Jul-92 02:48:03
Sb: #playm on MM/1
Fm: GLEN HATHAWAY 71446,166
To: all
Hi all... Can I use playm on my MM/1 with I/O board and 1 Meg? I've tried, but
get only garbage sound or no sound at all. I've seen the file with the
modifications, but I'm real hesitant about cutting anything on the board except
as a last resort. It's much easier to remove it than to put it back ya know...
There is 1 Reply.
#: 15910 S12/OS9/68000 (OSK)
15-Jul-92 01:22:56
Sb: #15904-playm on MM/1
Fm: GLEN HATHAWAY 71446,166
To: GLEN HATHAWAY 71446,166 (X)
Hi all... Never mind the message I'm replying to. After buying 2 more megs of
memory and installing it, everything works as advertised. Tomorrow night I'll
have a Fujitsu 105 Meg hard drive up and running - can't wait. Bought a
Logitech Mouseman - works fine (it's MicroSoft compatible, so use the .ms
drivers). My MM/1 is finally starting to act like a real computer!
Press <CR> !>