#: 14733 S3/Languages 31-Mar-92 02:14:38 Sb: #14699-#Help Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) Do you know the catalog number for the development package? There isn't anyone I know that has a CoCo for sale anymore. All my friends went to MSDOS a few years ago. There's only one other guy in my area that has a CoCo and he runs a BBS on his also. He's still using RSDOS though. There are 2 Replies. #: 14736 S3/Languages 31-Mar-92 03:01:21 Sb: #14733-#Help Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) George - Sorry.. no idea. Got any old (2 yrs) RS catalogs around? Pete There is 1 Reply. #: 14771 S3/Languages 03-Apr-92 10:56:13 Sb: #14736-#Help Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) Geezzz.. I don't know...I'll have to look.... I'm starting to have other problems now. I think my GIME chip has gone bad. The computer just locks up every now and then and starts printing those sparklies on the screen. I can't run my Burke & Burke File Repack System anymore. As soon as I type 'repack /h0' the program will load and the drive light will come on for a second and then nothing or the sparklies come back. Even multitasking seems to not work right sometimes. My Deskmate wordprocessor doesn't work right either when I try to copy blocks pf text. I figure, well it might be the GIME chip as I've heard that when they go bad, things like that happen. It most likely is as I have been running my CoCo for about 5 years nonstop now running a BBS. I've alreay had to replace a HD a couple of years ago. Where can I get updated GIME chip? Does Frank Hogg have them? Thanks... There is 1 Reply. #: 14777 S3/Languages 03-Apr-92 16:00:42 Sb: #14771-#Help Fm: Kevin Darling 76703,4227 To: George Hendrickson 71071,2003 (X) George - try cleaning the GIME chip contacts... or at least tapping on it. Same for the MPI connectors (if you have one). It's amazing how cruddy the metal gets, especially after some moist days. There is 1 Reply. #: 14783 S3/Languages 04-Apr-92 02:43:14 Sb: #14777-#Help Fm: George Hendrickson 71071,2003 To: Kevin Darling 76703,4227 (X) I cleaned all my connections with a Nintendo cleaning kit. Those suckers were filthy! Especially slot 4 on my multi-pak! I'm still using an old Radio Shack floppy drive controller. I would like a nice Disto controller if I can find one. To clean the GIME chip contacts, should I pull the chip out and clean them or will some type of cleaner work like a Zero residue spray? BTW, I still got the same results with 'repack' after I cleaned my connections. I hope cleaning the GIME chip connections will make it work... Thanks for the help... There is 1 Reply. #: 14784 S3/Languages 04-Apr-92 04:59:20 Sb: #14783-Help Fm: Kevin Darling 76703,4227 To: George Hendrickson 71071,2003 I usually just pop the GIME out, and then pop it back in again... seems to be enough to cure a lot of ills (too lazy to spray it off so far :). You might call CRC and see if they have any Disto controllers left. Tony was making a few more, and there was a false report on the nets that they were all gone. Actually, the CRC salespeople goofed and didn't catch on that there were going to be a few more made available. Same goes for 1-meg upgrades and the 4-in-1 boards, I think. luck!- kev #: 14741 S3/Languages 31-Mar-92 19:19:45 Sb: #14733-#Help Fm: Bill Dickhaus 70325,523 To: George Hendrickson 71071,2003 (X) According to the manual I got with the development system, the catalog # was 26-3032. From what I've heard over on Delphi, you might be able to find one, but it won't be easy. Bill There is 1 Reply. #: 14773 S3/Languages 03-Apr-92 11:01:27 Sb: #14741-Help Fm: George Hendrickson 71071,2003 To: Bill Dickhaus 70325,523 (X) Thanks. I'll check with my local Radio Shack this weekend and see if they can help me. #: 14734 S9/Utilities 31-Mar-92 02:18:56 Sb: #Help Fm: George Hendrickson 71071,2003 To: all Does anyone know of any software for OS9/MSDOS that will allow me to connect an MSDOS machine and a CoCo together through the RS232 port? MSDOS has WeakLink but its for 2 PC's, that I know of. I need something that will allow me to port my stuff from my CoCo to my 386. Any help would be appreciated...Thanks! There are 2 Replies. #: 14737 S9/Utilities 31-Mar-92 03:02:54 Sb: #14734-#Help Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) George - I always used a crossover cable (Null modem style) and a terminal package at each end... I typically used Kermit (and Procomm's Kermit) to effect the transfers. Pete There is 1 Reply. #: 14772 S9/Utilities 03-Apr-92 11:00:03 Sb: #14737-Help Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) I used RiBBS and Procomm+ at 9600 baud and I tried OSTerm and Procomm+ at 19200 baud. Now that was great! Talk about your speedy file transfers! However; using OSTerm, I had to issue the menu commands on the CoCo but the file transfers came thru on Procomm. I couldn't see the menu selections using Procomm. I need to have my modem initalize differently... #: 14750 S9/Utilities 01-Apr-92 16:56:49 Sb: #14734-#Help Fm: ole hansen 100016,3417 To: George Hendrickson 71071,2003 (X) If you need to read your OS-9 disks in your PC, there is a German company called DTR(Daten Technik Reicshke), that has made a utility for MSDOS called OS9MAX, that will allow you to read,write,format,dir,diskcopy OS-9 disks in your PC-drive. It will read almost any format. If you are interested I will look up the address/phone number. There is 1 Reply. #: 14774 S9/Utilities 03-Apr-92 11:03:17 Sb: #14750-Help Fm: George Hendrickson 71071,2003 To: ole hansen 100016,3417 Thanks! What's the number?? I wonder if they have a utility that will repack an OS9 HD? That would be impressive. #: 14735 S3/Languages 31-Mar-92 02:58:27 Sb: #14724-#getkey problem in C Fm: Pete Lyall 76703,4230 To: Robert A. Hengstebeck 76417,2751 (X) The problem seems to be that you're passing 'vlu' to getkey() by VALUE... that is, you're sending a clone of VLU, but not VLU itself. In order to do what you want, you weel need to pass a pointer to VLU, ala: getkey(&vlu) and then down in getkey() (note declaration of vlu): int getkey(vlu) int *vlu; { *vlu = inkey(); .... } Pete There is 1 Reply. #: 14747 S3/Languages 01-Apr-92 06:47:02 Sb: #14735-#getkey problem in C Fm: Robert A. Hengstebeck 76417,2751 To: Pete Lyall 76703,4230 (X) Pete, your way of returning the pointer to the entered value, turned out to be be the best approach to what I was trying to do. I changed the 'int getkey()' to a 'char getkey()' also, since I found that I could more easily handle the returned value than the clone. There is 1 Reply. #: 14748 S3/Languages 01-Apr-92 09:50:47 Sb: #14747-getkey problem in C Fm: Pete Lyall 76703,4230 To: Robert A. Hengstebeck 76417,2751 (X) Actually, 'C' (or really C++) is bending in your direction... In C++, you can pass variables by reference without using pointers: swap(a,b) ..... swap( int& a, int& b) { int temp; temp = a; a = b; b = temp; } There are a few nice things about this approach: 1) You no longer have to dereference pointers 2) It is more intuitive in the target function 3) Because you're not using pointers, you have no opportunity to walk on something else. I believe there's a GNU C++ for the OSK boxes... Pete #: 14746 S3/Languages 01-Apr-92 06:43:19 Sb: #14729-getkey problem in C Fm: Robert A. Hengstebeck 76417,2751 To: Bob van der Poel 76510,2203 (X) Thanks Bob, I like your 'while' loop better than the one that I had. But also see my message to Pete. #: 14738 S6/Applications 31-Mar-92 07:30:47 Sb: #14731-UMuse Query Fm: Ches Looney 73016,1336 To: Bill Dickhaus 70325,523 (X) Thanks, Bill. Patching shell+ is probably what I did, then, to cope with the malloc error. Perhaps Mike will show up soon and refresh my memory. Thanks for the response. Regards, Ches. #: 14739 S10/OS9/6809 (CoCo) 31-Mar-92 09:58:53 Sb: #more coco c programming Fm: Joseph Cheek 71431,3466 To: all Hello, C programmers! I have another question. Suppose I have an array of pointers to functions, such as the following: int func0(), func1(), func2(), func3(), etc...; int funcarr[] = { func0, func1, func2, func3, etc... }; and I know which function I want to execute by its subscript in the array: int whichfunc; whichfunc = 1; /* I want to execute func1() */ It seems to me, from what James Jones said earlier to me, that the proper statement would be: (*funcarr[whichfunc])(); Is this correct? Are all of my previous statements syntactically correct? Thank you for any replies. There is 1 Reply. #: 14740 S10/OS9/6809 (CoCo) 31-Mar-92 18:59:36 Sb: #14739-more coco c programming Fm: James Jones 76257,562 To: Joseph Cheek 71431,3466 (X) Be careful! It's int (*funcarr[])() = { func0, func1, func2, func3, /* etc. */ }; This is one of the more ghastly aspects of C, alas. #: 14742 S10/OS9/6809 (CoCo) 31-Mar-92 20:40:31 Sb: c on the coco Fm: Joseph Cheek 71431,3466 To: james jones/all Many thanks to James Jones for his help with my programming problems. It now works! Here's what I did: First of all, I declared my functions, as they were in a separate source file: int func0(), func1(), func2(), etc...; and then built my array: int (*funcarr[])() = { func0, func1, func2, etc... }; I decided to call dofunc by number, instead of by function address; here is my (short and simple) dofunc function! dofunc(funcnum) /* do the func */ char funcnum; { return((*funcarr[funcnum])()); } Thank you so much for your help, James! I appreciate it very much. It is cleaner, more manageable, and faster than using switch (as I did previously). #: 14743 S12/OS9/68000 (OSK) 31-Mar-92 21:37:35 Sb: Timing Help Fm: Bob van der Poel 76510,2203 To: all Has anyone done much work with timed sleeps? I think I've found a bug in the sleep command--when the high bit of the value is set (as per MW instructions) it does not time 1/256 seconds accurately. Look at the following test code: main() { register int t; /* this gives "exactly" 10 seconds delay */ system("date"); for(t=10;t;t--) tsleep(0x80000000 + 256); /* however, this gives only about 7 sec... */ system("date"); for(t=256;t;t--) tsleep(0x80000000 + 10); /* and this gives only about 1 second */ system("date"); for(t=2560;t;t--) tsleep(0x80000000 + 1); system("date"); } As the comments indicate, the smaller the duration, the greater the error. If anything, the loops with the short sleep values should give more than 10 seconds delay due to the loop overhead. Or am I doing this all wrong? Oh, I'm using OSK 2.4 on a mm/1. #: 14744 S10/OS9/6809 (CoCo) 31-Mar-92 22:20:59 Sb: #14706-Rogue under Multivue Fm: Bert Schneider 70244,427 To: Mike Guzzi 76576,2715 OK - anyway, I got ROGUE to work with the graphics mode and it does fine. I can't use Shell+ since I also run UMUSE3 from Multivue - you see I wrote some code in C to run the program in the background so I can call up UMUSE3 from Multivue. I don't need all the bells and whistles anyhow! I can type at least 70 wpm so I don't need fancy shell interfaces to help me!!! See ya! Bert Schneider #: 14745 S12/OS9/68000 (OSK) 01-Apr-92 01:36:53 Sb: #GNU C Compiler Fm: Mark Sours 70372,1370 To: 70673,1754 (X) Can anyone tell me if either of the new C compilers will work on a one meg Atari ST. Does anyone know of any OSK users that operate on Atari ST's. There are 2 Replies. #: 14753 S12/OS9/68000 (OSK) 02-Apr-92 01:10:10 Sb: #14745-#GNU C Compiler Fm: Tom Birt 76640,1205 To: Mark Sours 70372,1370 (X) Mark, I know of two other Atari OSK users besides you, K. Darling and myself. Their names are, Mel Smith and Farrell Kenimer (both OS9CN members). Tom Birt, OS9CN Editor P.S. Don't hesitate to join our rapidly expanding (and improving) group. There are 3 Replies. #: 14754 S12/OS9/68000 (OSK) 02-Apr-92 01:23:38 Sb: #14753-#GNU C Compiler Fm: Mark Sours 70372,1370 To: Tom Birt 76640,1205 (X) Thanks for the info on other St Oskers, how do I join your group? I used to have a CoCo with Level II and I went to the ST five years ago because it would run OSK. But the floor fell out and I have no idea where I can find OSK stuff for the ST. If the program is located in DL 12 will it run on my ST? I need a C compiler but I would hate to pay MW 600 bucks for just the C compiler. I saw the new C compiler on this service but I'd hate to DL it and find out it won't work on my system. Anyway any help will for the most part will be all the help I get.. There is 1 Reply. #: 14756 S12/OS9/68000 (OSK) 02-Apr-92 01:34:38 Sb: #14754-GNU C Compiler Fm: Tom Birt 76640,1205 To: Mark Sours 70372,1370 (X) Please leave your name, address and phone number here, I'll take care of the rest (on joining the OS9CN). There are alot of 'generic' OSK programs that will run on the STs, unfortunately there are too many MM/1 specific programs at this time. Graphics standards need to be established along the same lines as TERMCAP (for text screen handling), so incompatabilities don't _kill_ the blossoming OSK market. My advice to you on DLing the GNU set, is to wait for my (or someone elses) report on its performance. Tom Birt #: 14759 S12/OS9/68000 (OSK) 02-Apr-92 07:54:08 Sb: #14753-#GNU C Compiler Fm: Kevin Darling 76703,4227 To: Tom Birt 76640,1205 (X) Hi Tom... Bob Santy also runs Atari OS9; he developed his 6809 emulator on it. And there are a coupla Microware guys who run it, too. Anyone else out there? There is 1 Reply. #: 14778 S12/OS9/68000 (OSK) 03-Apr-92 20:25:15 Sb: #14759-#GNU C Compiler Fm: Tom Birt 76640,1205 To: Kevin Darling 76703,4227 (X) Hi Kevin (or do you prefer Kev?), it would be nice to assemble a list of machine types and the number of users (using OSK). Has anyone started such a list? Since this message is totally off subject, why not go for broke. :)* Have you ever made any revisions to your Atari windows since v19? Has anyone else expressed any interest in adding back key repeat? Since I got 'hooked' on CoCo3 windows, I'll never go back to any other type. Although I would like to peek at the G windows version originally developed on the 1040ST. Take care. Tom There is 1 Reply. #: 14782 S12/OS9/68000 (OSK) 04-Apr-92 01:50:52 Sb: #14778-#GNU C Compiler Fm: Kevin Darling 76703,4227 To: Tom Birt 76640,1205 (X) Hi Tom. Kevin or Kev is fine (whichever you have enough strength to type :). A lot of people enter their name and other info in the member directory of the forum. I'm not sure of the new way of getting to it, but "mem" used to do it. Then you can add information, or search by name or interest. Perhaps we should razz people into updating their entries? Yah, I did a fancier version of the ST windows, but then my mouse died and I couldn't check its operation out. Thx for reminder; I owe everyone some version of it. Lemme see what I can dig up. Keep after me! kev There is 1 Reply. #: 14793 S12/OS9/68000 (OSK) 04-Apr-92 21:34:37 Sb: #14782-GNU C Compiler Fm: Tom Birt 76640,1205 To: Kevin Darling 76703,4227 (X) I will definitely keep you aware of a need for a ST windows upgrade. Today I'm going to upgrade my 520ST, from 1M to 2M, then I'll try using the GNU set. BTW, have you heard of any domestic Atari OSK licensees? Tom P.S. The BOD of the OS9CN would like to know if you have the time to get involved in our activities. #: 14764 S12/OS9/68000 (OSK) 02-Apr-92 23:11:54 Sb: #14753-#GNU C Compiler Fm: Carl Kreider 71076,76 To: Tom Birt 76640,1205 (X) I am an Atari OSK user too. Probably one of the first around here. On another note, what does the OS9CN editor do? I joined several months ago and have heard nothing from your group. I did finally get a response to a message I emailed to John Wight but it didn't really clear anything up. Carl There are 2 Replies. #: 14767 S12/OS9/68000 (OSK) 03-Apr-92 02:57:12 Sb: #14764-GNU C Compiler Fm: Tom Birt 76640,1205 To: Carl Kreider 71076,76 (X) line noise is severe, systeem (CIS) going down in 3 minutes, will continue at a later time. Tom Carl, that's a good question. I am the 3rd editor this group has had, so far. Of the 3 newsletters that have been composed, one could have created them, likw so: OS9: merge file1 file2 file3 > new.newsletter. I intend to improve this method somewhat, by actuaGq,~?~?~?~?/exit #: 14779 S12/OS9/68000 (OSK) 03-Apr-92 21:06:13 Sb: #14764-#GNU C Compiler Fm: Tom Birt 76640,1205 To: Carl Kreider 71076,76 (X) Let me try to clear up any questions you may have about the OS9CN. As I tried to express last night (but line noise and system time prohibited) a true newsletter (NetNews) is in the works (hard copy, pending the BOD's approval), but an ASCII disk file should be available on your local regional librarians board. I will UL the April NetNews here, as soon as possible (pending its completion). The theme of this months newsletter is communications, meaning how can we best keep in touch through the most popular msg. bases. If you or someone you know would like to submit an article on the simplest methods for using (and finding) these networks, it would be very much appreciated. Since the name of this user group implies it's network nature, I think our first priority should be to show everyone interested in OS-9, how to make his/her connection to our services. Tom P.S. We now have representatives of the OS9CN on all major msg. networks. There is 1 Reply. #: 14810 S12/OS9/68000 (OSK) 05-Apr-92 20:54:17 Sb: #14779-GNU C Compiler Fm: Carl Kreider 71076,76 To: Tom Birt 76640,1205 Thanks for the reply. It does raise two questions of mine - how do I find the 'local regional librarians board' to look at the newsletter and, in addition to 'how to connect to your services', what are your services. You should also make it a priorty to give people who send in mail in response to your posted requests for membership some feedback so they don't think you are vapour like I did. #: 14755 S12/OS9/68000 (OSK) 02-Apr-92 01:24:04 Sb: #14745-GNU C Compiler Fm: Tom Birt 76640,1205 To: Mark Sours 70372,1370 (X) This msg. is to answer your first question (will GNU work on a 1M ST?). I believe it requires 4M. I have DLed the entire GNU set, but haven't tried it out. I have bought a 4M bare board upgrade ($39), but have only purchased 2M of DRAM (want to make sure it works first). I'll let you know about the upgrade and the GNU operation as soon as possible. Tom Birt #: 14749 S12/OS9/68000 (OSK) 01-Apr-92 14:00:47 Sb: #14636-MM/1 Video Pinout???? Fm: Kevin Darling 76703,4227 To: Keith H. March 70541,1413 (X) OUCH. Kevin Pease called me this morning to tell me that the video port file (which I got from somewhere :-) was laid out wrong. Here's the right one, I hope: (looking at the female port) 5 4 3 2 1 9 8 7 6 1 - n/c 2 - gnd 3 - R 4 - G 5 - B 6 - n/c 7 - n/c 8 - HS 9 - VS #: 14751 S9/Utilities 01-Apr-92 21:16:26 Sb: PC Anywhere w/OS-9 Fm: Lee Veal 74726,1752 To: All To: Any and All I'm looking for a program that runs under OS-9 that does what the remote PC in a "PC-Anywhere arrangement" does. As you may know, PC-Anywhere allows a host PC to accessed via a comm-link connected remote PC. The remote PC can be in the next room, the next county or the next country, as long as they are attached to each other through their respective COMM ports. The remote PC (once logged on) can to anything from the remote site that can be done from the local (host) site. A LAN is being installed here at work. My employer's PC is across the room, my CoCo (w/OS-9) is here on this side of the room, where all my "stuff" is. I think it'd be great if I could link up with the LAN-ed Po using PC-Anywhere running on the PC and an OS-9 counterpart running here on the CoCo3. I could then just open a window under my Level 2 system, start the OS-9 version of PC-Anywhere, log on to the PC (running the host part of PC-Anywhere), log on to the LAN, then do everything from where I've been doing it all anyway. Anything like a PC-Anywhere out there for Level 2? I just need the remote side to run on the OS-9 end. The host side (PC-Anywhere) would still be running on a PC. "PC-Anywhere" is just example of what I'm talking about. There are several such programs that run in the MiSery-DOS environs. A counterpart to just about any one of them would probably do. Thanks, Lee #: 14752 S1/General Interest 01-Apr-92 21:20:55 Sb: #New AR Developments Fm: Lee Veal 74726,1752 To: Wayne Day Wayne, Have you heard anything on the status of the new AR program that's being worked on by Carl K.? Just curious. There's a lot of guys over here in Dallas that are very much interested in the development of the new AR. In fact, they'd like to pass along suggested features, if possible. Lee There is 1 Reply. #: 14763 S1/General Interest 02-Apr-92 22:24:27 Sb: #14752-#New AR Developments Fm: Carl Kreider 71076,76 To: Lee Veal 74726,1752 (X) I'm not Wayne, but I do know the answer ;) I am waiting for the last of the infamous ar hackers to send me their changes to I can evaluate them for inclusion in the next version. You can feel free to email me your wish list and I promise it will get consideration too. Carl There are 2 Replies. #: 14776 S1/General Interest 03-Apr-92 11:30:30 Sb: #14763-New AR Developments Fm: Lee Veal 74726,1752 To: Carl Kreider 71076,76 (X) Thank you, Carl. That's what I wanted to hear. I'll make every effort to get our wish list to you in a timely and appropriate manner. Thanks again, Lee #: 14818 S1/General Interest 06-Apr-92 16:46:13 Sb: #14763-New AR Developments Fm: Lee Veal 74726,1752 To: Carl Kreider 71076,76 From: Daniel Haucke (through Lee Veal, CIS #74726,1752) To: Carl Krieder Subject: Upgrade/enhancement suggestions for AR 1.2 o Improved compression reflecting as good or better compression than the unsanctioned versions of AR. o Various compression formats to fit the various types of files available. (e.g. one format compresses text very wfll, where another compresses binaries pretty well.) o A MOUSE DRIVEN INTERFACE that we may use since the file exten- sion is only (.ar) two letters instead of three. (i.e. we can not use Multi-Vue.) o ASCII processing for files to be displayed to STDOUT via the -p option. This is to say that AR should filter out control characters and binary (mask high-order bit) data while send- ing the text out. If that option does not appeal to you, the parhaps an option for this while printing would me more appropriate such as "ar -pp [archive.ar] " ? o When files are compressed using AR 1.2, sometimes the result is actually LARGER than the original file. At times like that, it would make sense that some kind of compression logic be added to the program to test the last compression to see if the result is larger that the original file and if so, simply do not compress (store as-is) or use another compression method. ----------------------------- Lee #: 14757 S7/Telecommunications 02-Apr-92 06:30:35 Sb: #sterm at high bps Fm: James Jones 76257,562 To: Mark Griffith Gee...now that I have /t0 set for 19.2Kbps, sterm thinks I'm running at 1200 baud, and uses 512-byte packets for CIS B downloads. Since it's still doing sliding windows, it doesn't really matter on throughput, but just out of idle curiosity, how can I get sterm to get the right idea about baud rate? (This, of course, is under OSK on my MM/1.) There is 1 Reply. #: 14758 S7/Telecommunications 02-Apr-92 07:48:44 Sb: #14757-#sterm at high bps Fm: Mark Griffith 76070,41 To: James Jones 76257,562 (X) James, >can I get sterm to get the right idea about (19.2) baud rate? Sure, go into the io.h header file that sets up the baud rate table and change the 19.2 value from 16 to 15 and recompile. Either that or drop back to 9600 baud. Look for: #ifdef OSK {5, 7, 10, 12, 14, 16}; and change the 16 to 15. That's all folks!!! Mark There is 1 Reply. #: 14766 S7/Telecommunications 02-Apr-92 23:24:04 Sb: #14758-sterm at high bps Fm: James Jones 76257,562 To: Mark Griffith 76070,41 (X) Aha! "Use the source, Luke." Thanks! #: 14760 S12/OS9/68000 (OSK) 02-Apr-92 21:19:31 Sb: #more serial wierdness Fm: Steve Wegert 76703,4255 To: Carl Kreider 71076,76 (X) Carl (and Kev), I recently completed adding the remaining serial ports to my MM/1. I now have all five ports available. On the surface .... they all work. /t2,/t3 and /t4 have always functioned, so I tested /t0 and /t1 by swapping a terminal to each port, firing up a shell and issuing a few commands. But, when I try something a bit more intense I find I have more serial weridness. For instance, with a terminal on /t0 and a shell active, I fire up my com program with the following command: sterm -l /t3 As soon as I get any activity from sterm, the port is locked up. (other port still function). Attempting to kill the process on /t0 will lock up the entire machine. The same thing will happen if I use Kermit. Mark muttered somthing about interupts, so I grabbed a snapshot with the IRQS command: OS9 St. Louis MM/1 OS-9/68K V2.4 (max devs: 32, max irqs: 32) vector prior port addr data addr irq svc driver device ------- ----- --------- --------- --------- --------- ------ 28 (4) 1 $00e00291 $0017b710 $0000e252 sc68681 t4 28 (4) 1 $00e00281 $0016e520 $0000e252 sc68681 t3 28 (4) 2 $00e00000 $001ffdc0 $0001b912 scsi_mm1d 28 (4) 5 $00e00381 $001f5560 $0000d8d0 sc68901 t2 29 (5) 1 $009ffc41 $001f9814 $00014f94 keydrv 29 (5) 3 $009ffc00 $00000000 $0000c098 tk68901 29 (5) 5 $009ffc01 $001877a0 $0000d8d0 sc68901 t1 29 (5) 9 $009ffcc1 $001f2140 $00019c1c rb37c65 d0 29 (5) 255 $009ffc0d $001f2e10 $0000ce7c sc68070 t0 Immediately the 255 priority on /t0 strikes me as odd. (more in the reply) There are 2 Replies. #: 14761 S12/OS9/68000 (OSK) 02-Apr-92 21:20:41 Sb: #14760-more serial wierdness Fm: Steve Wegert 76703,4255 To: Steve Wegert 76703,4255 (X) Next, I start to compare the values found in the above table with those found by using moded on the various descriptors. What I find is that for all of the descriptors _except_ for /t0, values for vector, pirority and port address match. Moded reports a vector of 60, priority of 5 and an address of $80002011 on /t0. Further testing and playing uncovers another bit of weirdness. With a shell on /t1 (and showing up in the IRQS table), any request of the floppy will lock up the machine. Only a reboot will fix it. The same this _does not_ happen with /t2. (I'm guessing this would rule out the 901 driver causing this problem along with the my 'one-off' problem). Looking at the IRQS table, I notice that the port address for /t1 is one byte higher than the clock. I wonder if this is significant, given the gap between other devices is at least 10. Not knowing what the heck I'm talking about reduces me to just reporting what I see. I hope it's helpful. Ideas? Do I have an interupt problem or should I go looking elsewhere? Steve #: 14765 S12/OS9/68000 (OSK) 02-Apr-92 23:14:02 Sb: #14760-#more serial wierdness Fm: Carl Kreider 71076,76 To: Steve Wegert 76703,4255 (X) I have captured your message. I agree that t0 looks flakey (255 et. al.) so the best thing I can recommend is that you help Mark find time to mail me some boards so I can look into it ;) Carl There are 3 Replies. #: 14769 S12/OS9/68000 (OSK) 03-Apr-92 07:33:31 Sb: #14765-#more serial wierdness Fm: Steve Wegert 76703,4255 To: Carl Kreider 71076,76 (X) Consider it don, Carl! ---> Hey Mark! Bring that board in to the office today, We'll have Pat find a suitable box and ship it post haste! Steve There is 1 Reply. #: 14809 S12/OS9/68000 (OSK) 05-Apr-92 20:46:00 Sb: #14769-#more serial wierdness Fm: Carl Kreider 71076,76 To: Steve Wegert 76703,4255 (X) Steve, I spent a bit of time staring at your problem, and I think you may in fact have several. We know there is something wrong with the 901 driver because it gets in the 'one behind' mode. But your are right about t0 not looking right. The address is wrong and the priority is wrong. The address is actually that of the interrupt pending register B. It seems like something or someone has overwritten them. Since that register does deal with floppy and hard disk I/O, perhaps it isn't too surprising that floppy access can hang the system. Can Mark or anyone else duplicate those results? Carl There is 1 Reply. #: 14820 S12/OS9/68000 (OSK) 06-Apr-92 19:37:26 Sb: #14809-more serial wierdness Fm: Steve Wegert 76703,4255 To: Carl Kreider 71076,76 Carl, A message today from John W. confirms the lock up problem when accessing the floppy also occurs on his machine. Mark's following this thread and I hope will attempt to duplicate the problems as well. I'll pester him at the office tomorrow about it. BTW ... the CPU board left today via overnight delivery. You should have it in the morning. Steve #: 14781 S12/OS9/68000 (OSK) 03-Apr-92 22:25:37 Sb: #14765-#more serial wierdness Fm: Steve Wegert 76703,4255 To: Carl Kreider 71076,76 (X) By the way ... Mark passed along a copy of the new sc68681 driver for me to bash on (as long as I'm bashing! :-) ) What problem does it fix? Steve There is 1 Reply. #: 14811 S12/OS9/68000 (OSK) 05-Apr-92 20:56:36 Sb: #14781-more serial wierdness Fm: Carl Kreider 71076,76 To: Steve Wegert 76703,4255 (X) Pretty trivial in the usual case. Has to do with baud table selection not working right with certain baud combinations, like 9600 on one port and 19200 on the other or some such. #: 14802 S12/OS9/68000 (OSK) 05-Apr-92 10:20:46 Sb: #14765-#more serial wierdness Fm: Steve Wegert 76703,4255 To: Carl Kreider 71076,76 (X) Carl, Mark mentioned to me on Saturday he'd be sending off the cpu board to you on Monday. In the meantime, a little more testing on my part has yielded a bit more info that might be helpful as you desk test. I removed both the sc60870 and sc68901 updated drivers from my bootfile, replacing each with the distribution versions and got some interesting results. (appropriate descriptors were also replaced) Relative to the /t0 problems, there wasn't any significat change in performance. The port still locked up trying to run a telcom program and accessing /d0 with /t1 active locked up the machine. What was interesting was that /t0 no longer shows up in the IRQS display. Now onto slightly better news: The 'one-off' problem doesn't appear while using the older version of the 901 driver. However, the port locks up frequently enough to make it unusable in my application. (might be related to the smaller buffer sizes?) In any event, I wanted to pass along what symptoms I can duplicate. Perhaps it's helpful. Thanks for your efforts, Steve There are 2 Replies. #: 14806 S12/OS9/68000 (OSK) 05-Apr-92 14:47:23 Sb: #14802-#more serial wierdness Fm: John R. Wainwright 72517,676 To: Steve Wegert 76703,4255 (X) Hey Steve, Just thought I would drop a note in here to tell you that you are not alone with the serial wierdies. I noticed the 'one off' problem on both /t0 and /t1. I also can lock up every thing by trying to access any floppy drive when there is a shell running on /t1. My solution (after I got the tech manual and found out how to do it was to reconfigure the paddle board (I only have one) to use /t3 (unplugged /t1 and made a little cable). I figure I'll ignore /t1 until somebody smarter than me fixes it. For the (old) /t0 lockup problem (it gets hung up if it sees something at the wrong baud rate), I have a little program called 'guardian' that was uploaded to DELPHI by Randy Wilson. It watches for an error in the on-board 68070 serial port and resets it. Watching this thread with interest. John Wainwright There is 1 Reply. #: 14819 S12/OS9/68000 (OSK) 06-Apr-92 19:33:48 Sb: #14806-more serial wierdness Fm: Steve Wegert 76703,4255 To: John R. Wainwright 72517,676 John, Thanks for the confirmation of problems. It's good to know it's not just me. Steve #: 14813 S12/OS9/68000 (OSK) 05-Apr-92 22:01:06 Sb: #14802-more serial wierdness Fm: Carl Kreider 71076,76 To: Steve Wegert 76703,4255 (X) The problem with the old 901 driver locking up didn't have anything to do with buffer sizes. It sounds like the 'off by one' feature was introduced with the variable buffer sizes, though. #: 14762 S12/OS9/68000 (OSK) 02-Apr-92 21:26:40 Sb: #14618-#MM/1 help Fm: Steve Wegert 76703,4255 To: Bill Dickhaus 70325,523 (X) Bill, additional serial problems have shown up . Could I get you to review my latest posting here and see what if anything you might be able to duplicate on your end? Let's see ... you have /t1 and /t3 jes? Steve There is 1 Reply. #: 14775 S12/OS9/68000 (OSK) 03-Apr-92 11:27:09 Sb: #14762-#MM/1 help Fm: Bill Dickhaus 70325,523 To: Steve Wegert 76703,4255 (X) Steve, I haven't installed /T1 yet. I don't have /T3 yet. I have had similar problems with /T0 locking up, and I have tried to kill a process (in this case "rz") on /T0 which locked up the machine. I don't know enough about interrupts on the MM/1 to comment, but something does look a little funny. Bill There is 1 Reply. #: 14780 S12/OS9/68000 (OSK) 03-Apr-92 22:20:53 Sb: #14775-#MM/1 help Fm: Steve Wegert 76703,4255 To: Bill Dickhaus 70325,523 (X) So the output of an IRQS command shows a similar priority for you? I'd like to have it confirmed on another machine so I can rule out cockpit error. Tonight I went as far as booting up with my "no-windows-terminal-only" boot disk to rule out a windowing confict. Same results. Steve There are 2 Replies. #: 14785 S12/OS9/68000 (OSK) 04-Apr-92 05:08:46 Sb: #14780-#MM/1 help Fm: Mike Haaland 72300,1433 To: Steve Wegert 76703,4255 (X) Steve, Here's my IRQS output with 1 process on /t0, you right 255 priority. IMS MM/1 68070 Computer 2 Meg System OS-9/68K V2.4 (max devs: 32, max irqs: 32) vector prior port addr data addr irq svc driver device ------- ----- --------- --------- --------- --------- ------ 28 (4) 2 $00e00000 $001ffa60 $000234f6 scsi_mm1d 28 (4) 5 $00e00381 $001f5c30 $000180b0 msdrv 29 (5) 1 $009ffc41 $001f6264 $000175ac keydrv 29 (5) 3 $009ffc00 $00000000 $0000bec6 tk68901 29 (5) 9 $009ffcc1 $001f3870 $00021800 rb37c65 d0 29 (5) 255 $009ffc0d $001f5d60 $000185b4 sc68070 t0 57 (1) 2 $80004040 $001f3870 $000218ae rb37c65 d0 57 (1) 2 $80004040 $001ffa60 $00023500 scsi_mm1d 59 (3) 1 $80001001 $001f6264 $00017274 windio w1 (?) 59 (3) 5 $80002011 $001f5d60 $0001895e sc68070 t0 60 (4) 5 $80002011 $001f5d60 $0001894e sc68070 t0 62 (6) 2 $80004000 $001f6264 $00017ae4 snddrv - Mike - /ex There is 1 Reply. #: 14786 S12/OS9/68000 (OSK) 04-Apr-92 07:38:44 Sb: #14785-#MM/1 help Fm: Steve Wegert 76703,4255 To: Mike Haaland 72300,1433 (X) Thanks for the confirmation, Mike. Later today I'm gonna drop back to pre-update versions of both the sc68070 and sc68901 drivers and see if that doens't give me a temporary fix. I'll keep you posted. Steve There is 1 Reply. #: 14807 S12/OS9/68000 (OSK) 05-Apr-92 16:07:31 Sb: #14786-#MM/1 help Fm: Bob van der Poel 76510,2203 To: Steve Wegert 76703,4255 (X) If your are keeping track, my /t0 shows a prior of 255 too. Doesn't seem to cause any problems tho. Mind you, I don't have the other serial ports yet. Just /t0 and /ms.... There is 1 Reply. #: 14821 S12/OS9/68000 (OSK) 06-Apr-92 19:42:12 Sb: #14807-#MM/1 help Fm: Steve Wegert 76703,4255 To: Bob van der Poel 76510,2203 (X) Bob, If you could .... even though you don't have the paddle boards, you can attempt to duplicate some of these problems. For instance, load the sc68901 driver (if you don't already have it in memory), along with /t1. Start a shell on /t1 with a Shell -l <>>>/t1& Confirm it with the DEVS and IRQS command. Now ... attempt to access the floppy. Let me know what happens. Steve There is 1 Reply. #: 14825 S12/OS9/68000 (OSK) 06-Apr-92 21:23:49 Sb: #14821-#MM/1 help Fm: Bob van der Poel 76510,2203 To: Steve Wegert 76703,4255 (X) Steve, I talked to Paul today, and he promised that paddle board would be sent "right away"! When I get it I'll try this again, but without a /t1 board I get a real nice result when I try to access /t1--total system hangup. No keyboard, nothing. This happens if I just do an 'iniz /t1' or attempt to start up a shell. I don't think that this SHOULD be happening? BTW, any idea what the sc68681 driver is for? There is 1 Reply. #: 14826 S12/OS9/68000 (OSK) 06-Apr-92 21:34:53 Sb: #14825-MM/1 help Fm: Steve Wegert 76703,4255 To: Bob van der Poel 76510,2203 Bob, The sc68681 driver is for /t3 and /t4. I'm not too surprised at your lock up, the serial stuff seems to have a few problems that need to be worked out. When you did your test ... what was /t0 doing? Steve #: 14814 S12/OS9/68000 (OSK) 05-Apr-92 22:02:40 Sb: #14780-#MM/1 help Fm: Carl Kreider 71076,76 To: Steve Wegert 76703,4255 (X) Steve, Could you elaborate on 'same result'? Did /t0 still exhibit the wierdness? You are not booting with any mouse stuff are you? There is 1 Reply. #: 14822 S12/OS9/68000 (OSK) 06-Apr-92 19:52:10 Sb: #14814-MM/1 help Fm: Steve Wegert 76703,4255 To: Carl Kreider 71076,76 Carl, When I went back to the distrubiton drivers and descriptors, I wasn't using any mouse related stuff at all. I've had that commented out of my boot file until just recently. To clarify my 'same result' statement: With the older version of sc68070 and /t0 in use with a shell running on the terminal connected to /t0 (which appears to function fine), invoking sterm on the terminal (using /t3 for the modem port ___ i.e. sterm -l /t3) will lock up the port immediately upon sterm displaying it's opening screen. Attempting to kill the sterm process at the console (/term) will lock up the machine. Using kermit instead of sterm nets the same result. The only difference I noticed using the older version of /t0 and it's driver was no entry appeared in either DEVS or IRQS for /t0 even though it had been attached. Steve #: 14770 S12/OS9/68000 (OSK) 03-Apr-92 07:38:13 Sb: serial weirdness Fm: Steve Wegert 76703,4255 To: James Jones 76257,562 (X) JJ, Take a peek at my posting in 14760. Will you see if you can duplicate any of it on your set up? Does an IRQS show the same weirdness for you? Thanks! Steve #: 14787 S14/misc/info/Soapbox 04-Apr-92 07:39:31 Sb: #I Give Up Fm: Mark Griffith 76070,41 To: All Well..... It has now been two (2) years since the debut of the MM/1 at the Chicago Fest in April 1990. Since that time, none of the promised software packages have made it to the markit. Why? Everyone is still waiting on the window interface to be completed......the very same window interface that was demoed 2 years ago and oh so many promises made. Sigh. My friends, I have given up on this and this is my last public comment on this subject. If someone can get the window system out to the public, then maybe the MM/1 project can still be saved. Hey, a new cause for the whale watchers: Save The MM/1 !!! Mark There are 2 Replies. #: 14795 S14/misc/info/Soapbox 05-Apr-92 01:01:43 Sb: #14787-#I Give Up Fm: Mike Haaland 72300,1433 To: Mark Griffith 76070,41 (X) reply 14787 New Windio w/docs, c lib and c manual is in Pauls hands as we speak. ;-) - Mike - There is 1 Reply. #: 14800 S14/misc/info/Soapbox 05-Apr-92 10:13:04 Sb: #14795-I Give Up Fm: Steve Wegert 76703,4255 To: Mike Haaland 72300,1433 (X) Hot dog! Thanks for the update, Mike. Steve #: 14799 S14/misc/info/Soapbox 05-Apr-92 08:21:46 Sb: #14787-I Give Up Fm: Mark Griffith 76070,41 To: Mark Griffith 76070,41 (X) Mike, Finally! Thanks. MArk #: 14788 S10/OS9/6809 (CoCo) 04-Apr-92 14:54:49 Sb: #OS9 level 2/disk basic 2 Fm: paul Mooney 100015,134 To: All Help wanted, Is there any way I can boot OS9 level 2 from disk basic 2.0 - this version of basic doesn't recognise the DOS command? Thanks, Paul There is 1 Reply. #: 14796 S10/OS9/6809 (CoCo) 05-Apr-92 02:26:24 Sb: #14788-#OS9 level 2/disk basic 2 Fm: Wayne Day 76703,376 To: paul Mooney 100015,134 (X) Yeah... use one of the boostrap loaders. I BELIEVE there's a couple in the CoCo Library.. DOS.BAS or similar. Wayne There is 1 Reply. #: 14803 S10/OS9/6809 (CoCo) 05-Apr-92 11:11:36 Sb: #14796-#OS9 level 2/disk basic 2 Fm: Pete Lyall 76703,4230 To: Wayne Day 76703,376 (X) Wayne/Paul - Wasn't there also a simple 15 line program called "*.BAS" in the back of the manual that came distributed with os9? It was intended for folks with 1.0 disk ROMS. Pete There are 2 Replies. #: 14808 S10/OS9/6809 (CoCo) 05-Apr-92 19:31:54 Sb: #14803-OS9 level 2/disk basic 2 Fm: John L. Wilkerson Jr. 71140,77 To: Pete Lyall 76703,4230 (X) Look on the BACK of the BASIC09/CONFIG disk.... in RSDOS.... there is a program that will boot os9. You can either check drive speed or boot os9. I believe the program is called *. That will get you running. -- John #: 14816 S10/OS9/6809 (CoCo) 06-Apr-92 02:49:53 Sb: #14803-OS9 level 2/disk basic 2 Fm: Wayne Day 76703,376 To: Pete Lyall 76703,4230 (X) Yep, there was.... *.BAS. I think the one we've got is the same thing. Wayne #: 14789 S4/MIDI and Music 04-Apr-92 16:11:38 Sb: #14716-#Umuse3 Help Fm: Ches Looney 73016,1336 To: Larry J. Mohr 76120,1642 (X) Larry, perhaps you've noticed that I've been trying to find the answer to the malloc problem. It hit me a year or so ago and Mike gave me a fix. Unfortunately, in a misguided fit of cleaning up, I recently lost the fix and now I have the same problem again. It has to do with SHELL+. If you reboot with the original SHELL instead of SHELL+ as SHELL, I believe you will be able to run UmUse without problems. I have called Mike but so far no answer; perhaps he's out of town. More later. Ches. There is 1 Reply. #: 14797 S4/MIDI and Music 05-Apr-92 03:39:58 Sb: #14789-#Umuse3 Help Fm: Larry J. Mohr 76120,1642 To: Ches Looney 73016,1336 (X) l* Ches, Thanks for trying. I read the message thread a couple of days ago and decided to try some of the suggestions myself(I was too impatient to wait). Nothing seemed to work until I tried booting with the original Tandy Shell. Voila! Umuse was running perfect. Well I did not want to have to put up with the limitations of the old shell and I was unsure what I wanted to do until I realized that the only version of shell causing the problem was the one that Umuse3 ran from. I patched an original Tandy shell to the name Tshel and also patched the prompt to VDG and put it in my CMDS directory. Then I re-booted with my normal shell+ and begore Then I re-booted with my mormal shell+ and used the following sequence to run Ultimuse. tshell i=/vdg& then I go over to the VDG window and umuse3 and everything appears to work fine. I have been using this method for 2-3 days without problem. If you do find out a more elegant solution I would be happy to hear it, however, I am doing just fine now. P.S. Do you have version 4.7.5a -I thing the additions to it are fabulous. About the only thing I wished for that he has not already added is the coming APPEND function and a stand alone song player. Thanks again for the clues. Larry Mohr There is 1 Reply. #: 14798 S4/MIDI and Music 05-Apr-92 07:31:13 Sb: #14797-Umuse3 Help Fm: Ches Looney 73016,1336 To: Larry J. Mohr 76120,1642 Glad it is working! No, I have 4.7.0. Do you have a number or location for Second City since they moved. I haven't been in touch with Ed for a while and would like to upgrade. Regards, Ches. #: 14790 S7/Telecommunications 04-Apr-92 16:17:55 Sb: #Garble? Fm: Ches Looney 73016,1336 To: sysop (X) I've noticed a few times lately that what appears to be a message number appears in the body of a message. Is something happening inside CIS or have I somehow done something to cause the problem? Thanks for advice. Ches. There is 1 Reply. #: 14791 S7/Telecommunications 04-Apr-92 20:43:21 Sb: #14790-#Garble? Fm: Steve Wegert 76703,4255 To: Ches Looney 73016,1336 (X) That's a new one, Ches. I've not noticed anything at this end. What terminal software are you using to access the fourms? Does it only happen on in the OS9 forum or everywhere? Steve There is 1 Reply. #: 14794 S7/Telecommunications 04-Apr-92 23:25:30 Sb: #14791-#Garble? Fm: Ches Looney 73016,1336 To: Steve Wegert 76703,4255 (X) Since you sorta said it's me, I looked more carefully. What seems to be happening is that a line-feed is being lost at the end of the message so the RR #XXXXX (or whatever the syntax is) comes in over the last line. Dunno why the only thing that shows up is the number. Strange. Software is STERM; no logging occuring when # shows up. Doesn't happen all the time. Gotta be a timing problem of some sort, but 'tis interesting that it doesn't occur on anything but that last line. Ideas?? Ches. There is 1 Reply. #: 14801 S7/Telecommunications 05-Apr-92 10:18:13 Sb: #14794-Garble? Fm: Steve Wegert 76703,4255 To: Ches Looney 73016,1336 Who me (the master of cockpit error?) point the finger are _you_? Nahhhhhh! :-) Ches, I'd start looking at various parameters for conflicts. Start with CIS and GO DEFAULT. Look at your terminal defintions closely. Next, I'd take a peek at your serial ports with xmode. Anything there? I take it this is a recent development? What's new to your set up? Logging in at a diffferent BAUD rate? (CIS keeps different parms on each BAUD). THe more info you can share, the better off we'll be. Steve #: 14804 S12/OS9/68000 (OSK) 05-Apr-92 13:53:08 Sb: #MM/1 Tech Manual Fm: GLEN HATHAWAY 71446,166 To: all Hi all... Just received my copy of the 'MM/1 Technical Manual'. Anybody else got one yet? Are you as disappointed as I am? Seems kinda thin and vague considering that it costs $50.00. Instead of giving you information, it lists references of where to get the information. I guess I'll have to shell out more time and money to get this info, but I kinda thought it would be in the tech manual... There is 1 Reply. #: 14805 S12/OS9/68000 (OSK) 05-Apr-92 14:30:21 Sb: #14804-#MM/1 Tech Manual Fm: Steve Wegert 76703,4255 To: GLEN HATHAWAY 71446,166 (X) Glen, What information were you expecting in the tech manual that isn't there? I know Mark is planning a revision, so perhaps your input would be timely. Steve There is 1 Reply. #: 14812 S12/OS9/68000 (OSK) 05-Apr-92 21:48:08 Sb: #14805-#MM/1 Tech Manual Fm: GLEN HATHAWAY 71446,166 To: Steve Wegert 76703,4255 (X) Hi Steve... Specifically, I would like some information on getting at the guts of the VSC chip - how to program it, how to use the pixel accelerator functions, etc. All the (oops) "tech manual" tells us is that there is a chip called the VSC and that it controls the video output. Not much help there. All the information in there seems kinda like that. It mentions stuff, but doesn't go into any detail at all. I like to program in assembler and I like to sometimes 'cheat' and go directly to hardware without letting the OS handle it. Must be my coarse RSDOS upbringing, I guess... I thought a tech manual was supposed to explain in detail everything about the machine hardwarewise, rather than just brush over things... I'm not saying the manual is totally useless, but so far it hasn't enlightened me a hell of a lot.M (oops) Guess Signetics wouldn't let IMS reprint their spec sheets?? That seems kinda dumb, if they want to sell products... I don't know what the problem is, but I want more for my $50!!! There are 3 Replies. #: 14815 S12/OS9/68000 (OSK) 06-Apr-92 02:46:08 Sb: #14812-#MM/1 Tech Manual Fm: LARRY OLSON 72227,3467 To: GLEN HATHAWAY 71446,166 (X) Glen, If I may jump in, I too have the MM1 technical manual, and your right it didn't get very deep in the hardware. But there is a solution, and it only costs a phone call. If you call Phillips/Signetics, they will send you a load of stuff.. Just call and ask for data books/sheets on the following Hardware & Software manuals for SCC68070 Phillips # 9398-651-50011 SCC68070 User Manual 1990 Part 1 9398-650-40011 SCC68070 User Manual 1990 Part 2 Software oops- Part 1 should be Part 1 Hardware For the SCC66470 Video & systen Controller Phillips # 98-8066-470 SCC66470 Data Sheet The number I have for Signitics is (408)-991-2000 You will be suprised at what they will send you for free, the SCC66470 Data Sheet, is actually 60 pages of info on the vsc, while those user manuals are like some of the programming books you have probably paid quite a bit for. If you are also interested in the I^C stuff built into the 68070, then also ask for the.. I^C Peripherals for Microcontrollers Phillips # 98-8080-574 They will even send you a Master product catalog # 98-1000-000-05 without even asking. You will think its Christmas, when all the stuff shows up ;-) I hope this helps Larry Olson There is 1 Reply. #: 14829 S12/OS9/68000 (OSK) 06-Apr-92 22:28:45 Sb: #14815-MM/1 Tech Manual Fm: GLEN HATHAWAY 71446,166 To: LARRY OLSON 72227,3467 Hi Larry... That's exactly what I want! Thanks - I'll give Signetics a call tomorrow... #: 14817 S12/OS9/68000 (OSK) 06-Apr-92 06:46:31 Sb: #14812-MM/1 Tech Manual Fm: Mark Griffith 76070,41 To: GLEN HATHAWAY 71446,166 (X) Glen, >Specifically, I would like some information on getting at the >guts of the VSC chip - how to program it, how to use the pixel >accelerator functions, etc. All the (oops) "tech manual" tells >us is that there is a chip called the VSC and that it controls >the video output. If you care to call the numbers I give, or write to the addresses, you'll get SEVERAL BOOKS on just the VSC. Yes, all the information on the VSC covers three different books. And I mean books of over 100 pages each. It was not that Signetics didn't allow IMS to reprint them, it was just too much to be included in the tech manual. If I had re-written all of that or just re-printed it and included it in the manual, it would have driven the price up to well over $100. Would you think that was a bargan? What I did give was some specifics on the different devices where they apply to the MM/1. If you could have figured all this out on your own then you wouldn't have needed the tech manual. As it is, with the tech manual and the manufacturer docs, you have all you need to "cheat" when you didn't have that before. If you think the price should be lower, then talk to Paul Ward. If you want to complain about the contents some more, then I'm the one to talk with. Mark #: 14823 S12/OS9/68000 (OSK) 06-Apr-92 20:02:39 Sb: #14812-MM/1 Tech Manual Fm: Steve Wegert 76703,4255 To: GLEN HATHAWAY 71446,166 Glen, I see you have a couple of replies already telling you what suggestions I would have to offer. In fact, I really need to call Signetics myself and get the hardware info for my files. You'll be pleased with what you get for just a phone call. I tend to agree there needs to be a bit more info in the manual for the price it carries. In talking with Mark, he mentions that he had planned on including all the window stuff as well as addtional driver info but printing deadlines conflicted with developer deadlines and the manual had to move ahead without it. Paul Ward happened to call me today and I passed on your concerns about the manual. He's asked that I have you call him to discuss the situation. He's kicking around a few ideas about a manual update that I think you'd be interested in. Steve #: 14824 S12/OS9/68000 (OSK) 06-Apr-92 20:37:10 Sb: Your TC70 Fm: Frank Hogg of FHL 70310,317 To: Kevin Darling 76703,4227 Kev, So... Kev... Now that you've had your TC70 for awhile now... When can we expect to see the 'final' KWindows port done??? huh huh huh :) Frank #: 14827 S12/OS9/68000 (OSK) 06-Apr-92 21:43:37 Sb: 600 baud on /t0 Fm: Steve Wegert 76703,4255 To: All An unexpected feature of /t0 showed up over the weekend. It would appear that this port can not support 600 baud. You can xmode the descriptor to the appropriate value, but attempting any type of use of that port (just an iniz, for example) and a 240 error will result. Why a drive error happens, I'm not too sure, but happen it does. With my 5 serial ports in operation, I had plans on having my X10 controller hooked to /t0 (thus the 600 baud), a tube on /t1, a critter on /t2 and a couple of modems on /t3 and /t4. Looks as if I may have to swap the tube and X10. This bit of trivia wasn't in the manual that came with the computer, nor did I recall seeing it in the Tech manual. However, I'm told it's covered in the technical info from Signetics. Thought I'd pass this on to other MM/1 users ... and I'd expect a similar feature on a TC70's /term port. Steve Press !>