#: 3549 S9/Utilities 17-May-90 00:32:36 Sb: #Level Two windows? Fm: Wendell Benedetti 72766,2605 To: Kevin Darling Kevin, Did you ever write a "window" driver for Standard OS-9 Level Two? Wendell There is 1 Reply. #: 3559 S9/Utilities 17-May-90 17:39:13 Sb: #3549-Level Two windows? Fm: Kevin Darling (UG Pres) 76703,4227 To: Wendell Benedetti 72766,2605 (X) You mean for terminals? Nope. But there was/is a company selling virtual terminal screen software. I hear it works okay. Anybody remember the name? #: 3598 S9/Utilities 19-May-90 12:52:45 Sb: #3559-#Level Two windows? Fm: James Jones 76257,562 To: Kevin Darling (UG Pres) 76703,4227 (X) I don't recall the name, but I'm sure that one can find an ad for it in any *68 Micro Journal* of the past couple or three years. There is 1 Reply. #: 3614 S9/Utilities 20-May-90 00:59:03 Sb: #3598-#Level Two windows? Fm: Wendell Benedetti 72766,2605 To: James Jones 76257,562 (X) James (&Kevin) I found it: Virtual Terminal by South East Media - for Standard and Coco OS-9. Thanks. Wendell P.S. (Kevin: so it's Dammed Yankees now? (grin)) There is 1 Reply. #: 3619 S9/Utilities 20-May-90 04:34:53 Sb: #3614-Level Two windows? Fm: James Jones 76257,562 To: Wendell Benedetti 72766,2605 (X) Re Southern vocabulary: my understanding is that it's always been one word: damnyankee. (I may not have the spelling right, though.) #: 3667 S9/Utilities 22-May-90 03:37:54 Sb: #Help with Shar Fm: Kevin Darling (UG Pres) 76703,4227 To: all Help. I downloaded the Shar util, compiled it, and tried to run it on a file with "shar -u unsit.shz". Zippo. Or at worst, wrote a char on the screen. Has anyone used this yet? The ident of my compile is: Header for: shar Module size: $266A #9834 Module CRC: $C4E9D6 (Good) Hdr parity: $64 Exec. off: $001B #27 Data Size: $18B2 #6322 Edition: $02 #2 Ty/La At/Rv: $11 $81 Prog mod, 6809 obj, re-en Thanks! There is 1 Reply. #: 3676 S9/Utilities 22-May-90 11:09:31 Sb: #3667-#Help with Shar Fm: Pete Lyall 76703,4230 To: Kevin Darling (UG Pres) 76703,4227 (X) Kevin -0 A 'shar' is just an ascii file... it's a SHELL ARCHIVE that contains both the script and data files to unpack itself. If you had a Unix bourne shell, you'd just unpack it by doing a: /bin/sh The .shz suffix makes me wonder.... there IS no standard suffix for a SHAR file. Also, the 'z' is usually tacked onto something that's been 'compress'ed. Try uncompressing it first (use a compress -d), and then see if it's ASCII. Then try the SHAR tool. Pete P.S. The UNSHAR I have occasionally crashes... dunno if they're the same. There are 2 Replies. #: 3701 S9/Utilities 22-May-90 17:40:32 Sb: #3676-Help with Shar Fm: Kevin Darling (UG Pres) 76703,4227 To: Pete Lyall 76703,4230 (X) Pete - thx. I'm trying to undo a file called UNSIT.SHZ from the new uploads section of UNIXFORUM. I'd love to see such a Mac Stuffit file unstuffer available under OS9 (which is what this is supposed to be source for). I'll try compress first. Thx! #: 3705 S9/Utilities 22-May-90 18:04:53 Sb: #3676-#Help with Shar Fm: Kevin Darling (UG Pres) 76703,4227 To: Pete Lyall 76703,4230 (X) Pete - ummm, where do I find the Compress util? Can't seem to find one for us. - kev There is 1 Reply. #: 3710 S9/Utilities 22-May-90 19:40:31 Sb: #3705-Help with Shar Fm: Pete Lyall 76703,4230 To: Kevin Darling (UG Pres) 76703,4227 Kev - Mebbe I'm the only one that has it, although I thought it was here as well. I'll upload it if it's not here.... Pete P.S. Our (os9/6809) compress will only handle 12bit compression... typical unix compression is done at 16 bit... were you aware of that? #: 3714 S9/Utilities 22-May-90 22:37:34 Sb: #3710-#Help with Shar Fm: Kevin Darling (UG Pres) 76703,4227 To: Pete Lyall 76703,4230 (X) Nope, I'm pretty ignorant of unix tools. I wonder if Simmy's done the 16-bit compression thingie for OSK? Thanks - if you get a chance to post the compress, that'd be great! There is 1 Reply. #: 3730 S9/Utilities 23-May-90 00:33:10 Sb: #3714-#Help with Shar Fm: Pete Lyall 76703,4230 To: Kevin Darling (UG Pres) 76703,4227 (X) Kev - Simmy ported our version from a 16 bit unix PD compress, so I'm sure he does have it... I'll try to remember to post it. Pete There is 1 Reply. #: 3755 S9/Utilities 23-May-90 21:44:17 Sb: #3730-#Help with Shar Fm: Kevin Darling (UG Pres) 76703,4227 To: Pete Lyall 76703,4230 (X) Pete - the compress worked fine! Much thanks. Now trying to get the source (of the file I got) to compile is a whole other deal... . thx again! kev There is 1 Reply. #: 3762 S9/Utilities 23-May-90 22:43:21 Sb: #3755-#Help with Shar Fm: Pete Lyall 76703,4230 To: Kevin Darling (UG Pres) 76703,4227 (X) Walll ... ahl be. I wonder if our new weirdo modems did any neato-beanie compression of their own, or if I just time warped while uploading. Either/both is possible.... Pete There is 1 Reply. #: 3770 S9/Utilities 24-May-90 06:04:09 Sb: #3762-#Help with Shar Fm: James Jones 76257,562 To: Pete Lyall 76703,4230 (X) Could be--you have MNP Level 5 or greater? (I think that's where they start compressing behind your computer's back.) There is 1 Reply. #: 3776 S9/Utilities 24-May-90 10:07:46 Sb: #3770-Help with Shar Fm: Pete Lyall 76703,4230 To: James Jones 76257,562 (X) JJ - Mebbe, but what's weird is that Kermit (C-Kermit) typically displays a period '.' every 4 packets (approx 4 * 94 bytes), and I was moving a file that was 37K+... I only saw about 5 periods.. Oh well, whatever the case it appears to have worked (?).. Pete #: 3787 S9/Utilities 24-May-90 20:53:13 Sb: Shell+ compatibility Fm: J SILLIMAN 72355,1207 To: All I have run into a major compatibilty problem with shell+ and FIle System repack. It seems that the two really do not get along. I did a backup and defrag a month ago and ended up having to reformat and recover my data because repack totally fraged my 20 meg drive. I started at 32% frag and ended at 64 or so frag. If anyone knows if there is a known compatibilty problem, please tell me, other wise I will notify the author some way or another thanx #: 3823 S9/Utilities 26-May-90 08:42:02 Sb: #3787-Shell+ compatibility Fm: Steve Wegert 76703,4255 To: J SILLIMAN 72355,1207 J, Why are you so sure there's a problem with Shell+ and your repak utility? About the only problems I've run into with Shell+ is in the wildcard stuff. Things can get real hairy if the utility you're running has it own wildcard routines. Best bet is to diable shell+'s wildcards and let the utlitiy cope as written. If you have more info, I'm sure we'd be interested in hearing .... Steve #: 3833 S9/Utilities 26-May-90 12:26:39 Sb: Play.ar / Studio Works Fm: TONY CAPPELLINI 76370,2104 To: ALL Does anyone out there know if the Studio Wworks sound files are compatible with the os9 play utility ? If so is there a way I can transfer files back and forth from os9 to rsdos ? I have a few SW files I would like to upload for eveyones use. Come to think of it, I haven't uploaded ANY files before. Where do I go to do that ?? TC #: 3904 S9/Utilities 28-May-90 20:55:52 Sb: #3823-Shell+ compatibility Fm: J SILLIMAN 72355,1207 To: Steve Wegert 76703,4255 (X) Repack does nothing with command line file functions, it is moving files, sector by sector around, and puting them in consecutive sectors. I am not positive that it is Shell+ doing it, but that was the only change that I had made. I was simply looking for some others that might have run into the same sort of problems thanx for the ideas though #: 4140 S9/Utilities 06-Jun-90 21:07:14 Sb: #Project Management Fm: tom farrow 72701,543 To: James Jones 76257,562 (X) Thankyou James but I really do not have the time or the inclination to get into that type of programming yet I am fairly new to os9. Could there be a way of getting MacProject II from the MacIntosh to the CoCo3? There is 1 Reply. #: 4142 S9/Utilities 06-Jun-90 22:10:33 Sb: #4140-Project Management Fm: James Jones 76257,562 To: tom farrow 72701,543 You'd have to talk to the folks who own MacProject II, or persuade a programmer to do something similar for the CoCo. (Now, Paul Ward et al. are working on porting, or having someone port, applications to OS-9/68K for the MM/1, and I'd be surprised if a scheduling/project management package hadn't crossed his mind, though of course you'd have to ask him whether anything is being done. The only association I have with the folks making the MM/1 is that I've already sent off my deposit on ordering one when they finally officially come out.) #: 4150 S9/Utilities 07-Jun-90 22:36:09 Sb: HDBACKUP upload Fm: Mark Griffith 76070,41 To: All All.... I have uploaded a new version of HDBACKUP in DL9. This one fixes a bug where the directory created on the backup disk had the correct attributes, but not the correct user ID number. Mark #: 4272 S9/Utilities 11-Jun-90 21:24:14 Sb: #4142-#Project Management Fm: tom farrow 72701,543 To: James Jones 76257,562 (X) I may seem somewhat out of touch but your reference to the MM/1 is unknown to me is this like the Tomcat or am I off track completely? There is 1 Reply. #: 4289 S9/Utilities 12-Jun-90 06:44:33 Sb: #4272-#Project Management Fm: James Jones 76257,562 To: tom farrow 72701,543 (X) The MM/1 is a 68070-based computer that Kenneth-Leigh Enterprises (actually, IMS, but I don't remember what that stands for :-) is working on (and that should be out in a month or two, I hope). The best thing I could do is refer you to DL15, where some descriptive material and press releases have been uploaded. (I have no association with KLE or IMS, other than having my deposit on an MM/1 sent off.) There is 1 Reply. #: 4318 S9/Utilities 12-Jun-90 17:39:57 Sb: #4289-Project Management Fm: Bill Dickhaus 70325,523 To: James Jones 76257,562 (X) IMS=Interactive Media Systems #: 4280 S9/Utilities 12-Jun-90 00:47:49 Sb: #VIEW.AR Fm: TONY CAPPELLINI 76370,2104 To: Jim Peasely Jim I have a full 512K. But you know you can still run out of system meemory, while still having tons of user memory. Thats what looks like is happening now. No I didn't use the special script initially, but will try it this time. 10 q TC There is 1 Reply. #: 4358 S9/Utilities 14-Jun-90 01:22:50 Sb: #4280-VIEW.AR Fm: Jim Peasley 72726,1153 To: TONY CAPPELLINI 76370,2104 ~ Tony; If you still have problems after merging gfx2, syscall, and inkey, let me know. What's in your bootlist? And do you have a bunch of stuff merged in with Shell? There's gotta be an easy explanation for your out of memory problem. I've got View, TSed, and 3 windows going right now, and have 8K left. ...Jim #: 4404 S9/Utilities 16-Jun-90 11:27:33 Sb: New Touch Utility Fm: Ken Drexler 75126,3427 To: All I have just uploaded a version of a touch command to DL 9. The program allows one or more files to be touched with the current date or any date selected by the user. The command accepts wildcards (* or ?). It is written in c. Ken Drexler, 75126,3427 #: 4431 S9/Utilities 17-Jun-90 08:17:54 Sb: RBF Fm: Mark Griffith 76070,41 To: Ken, 75126,3427 Ken, I noticed in the docs for your new touch utility you mentioned something about a bug in RBF. I don't understand your reasoning behind this. If a user does not have write permissions to a file, then they would not be able to write to it, and therefore not have the ability to change the file date. Can you explain further? Mark #: 4463 S9/Utilities 18-Jun-90 01:35:22 Sb: #4431-RBF Fm: Ken Drexler 75126,3427 To: Mark Griffith 76070,41 (X) Mark, I am now running one of my systems at my law office. Most of the files have the attributes set for both the owner and public read and write. On some of the files the modification date is important for backup purposes. I began to notice that the modification dates got out of sync and eventually figured out it was when the user who did not own the file updated it. (At the office, neither my secretary or I run as super user.) I checked this out on my system here and confirmed that an update by a person with write permission only updates the file date if the person is also the owner. The version of RBF I run is $10 with a CRC of $C199E8. It is circa 1983 and purchased from Smoke Signal Broadcasting. For further information you might ask Carl Kreider. He has a revised version of RBF which he did and gave me a copy of years ago. It does not reflect the bug described above. Hope this helps. Ken #: 4670 S9/Utilities 26-Jun-90 22:21:45 Sb: #Copy Fm: Paul Hanke 73467,403 To: Anyone Is there a disk file copy utility with wildcards? -ph- There are 3 Replies. #: 4688 S9/Utilities 27-Jun-90 14:50:06 Sb: #4670-Copy Fm: Pete Lyall 76703,4230 To: Paul Hanke 73467,403 (X) Paul - Carl Kreider's 'cp' is based on the Unix copy command, and should either be in DL9 or the UGLIB DL (5).. Pete #: 4696 S9/Utilities 27-Jun-90 19:30:37 Sb: #4670-Copy Fm: Ed Gresick 76576,3312 To: Paul Hanke 73467,403 (X) Hi Paul! Contact D. P. Johnson. He sells a utility pak which gives that kind of capability and more. His address D. P. Johnson 7655 S.W. Cedarcrest St Portland, OR 97223 503-244-8152 Ed #: 4782 S9/Utilities 30-Jun-90 17:30:37 Sb: #4670-Copy Fm: Lee Veal 74726,1752 To: Paul Hanke 73467,403 (X) There's a file called MCOPY.AR in DL10 that does wildcard copying. Lee #: 5167 S9/Utilities 13-Jul-90 21:40:49 Sb: #BURKE&BURKE + PBJ CC-BUS Fm: RODGER ALEXANDER 75366,556 To: ALL IS THERE ANYONE USING A BURKE AND BURKE HD INTERFACE WITH THE PBJ CC-BUS (6 SLOT MULTIPAK)? THE SLOT SELECT ADDRESS IS DIFFERENT FROM THE RAD SHAK MULTIPAK AND EVEN CHRIS BURKE HAS NOT BEEN ABLE TO HELP ME OUT YET WITH THIS ONE. WOULD APPRECIATE ANY INFORMATION, PATCH, ETC. TO HELP GET THE COCO-3 AND THE MULTIPAK TOGETHER WITH A HARD DRIVE. (FITS PERFECTLY INTO A TANDY 1000 CASE.) There is 1 Reply. #: 5177 S9/Utilities 14-Jul-90 01:01:23 Sb: #5167-BURKE&BURKE + PBJ CC-BUS Fm: Kevin Darling (UG Pres) 76703,4227 To: RODGER ALEXANDER 75366,556 (X) Check CCBUSP.TXT in Lib 10, Rodger... see if that helps. - kev #: 5186 S9/Utilities 14-Jul-90 11:25:55 Sb: #Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: all I am new to OS9 and need some information on reading OS9 directorys. I am getting ready to write a utility for my OS9 BBS (George's Dewdrop Inn) and need to know the formula for converting information taken from reading the directory into a 'dir e' type thing. There is a program called DSORT.B09 in the dloads that reads the directory and sorts it from opening a dir path. When looking at the varibles (printing them) I see alot of 'garbage' characters. My question is, How do I convert each record into something readable? The program sets up the records using 'TYPE' and the LSN varibles. Any help would be appreciated. Thanks George There is 1 Reply. #: 5187 S9/Utilities 14-Jul-90 11:53:31 Sb: #5186-#Reading OS9 Directorys Fm: Zack Sessions 76407,1524 To: George Hendrickson 71071,2003 (X) If you can read C, download my sdir.ar from the Utilities lib. Zack There is 1 Reply. #: 5220 S9/Utilities 15-Jul-90 04:23:38 Sb: #5187-#Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Zack Sessions 76407,1524 (X) I can't read C yet but I do have sdir in my CMDS directory! Pretty nice! Now if I could do that in Basic09.... ..without pipes... t Nope, can't read C but I do have 'sdir' in my CMDS dir! <, There is 1 Reply. #: 5222 S9/Utilities 15-Jul-90 09:48:22 Sb: #5220-Reading OS9 Directorys Fm: Zack Sessions 76407,1524 To: George Hendrickson 71071,2003 I only use a pipe to determine the "full path name" of the current directory or the execution directory. And everything that sdir does can be done in BASIC09. Zack #: 5267 S9/Utilities 16-Jul-90 20:32:55 Sb: #5167-BURKE&BURKE + PBJ CC-BUS Fm: DENNIS SKALA 73177,2365 To: RODGER ALEXANDER 75366,556 I wouldn't recommend using the B&B interface with the PBJ CCBus. It was the death of mine, and the reason I finally broke down and bought an MPI. First problem is that you need to add the 12 volt DC circuit to the CCBus (or power the HD interface card with a separate 12 VDC). Then because the CCBus doesn't switch the SCS and CTS lines separately, you must use a floppy controller which is fully decoded to $FF4x, so that it doesn't conflict with the B&B interface, which is at $FF5x. This means no Tandy floppy controller, as well as many others. Or --- you could fully decode the offending floppy controller. I did that, and it's fairly easy. I don't recall having to patch any software for the sake of the hard disk interface itself (of course to use the CCBus with OS9, a few system patches were required for other stuff). When I put the whole thing together, it worked for about 15 minutes and blew out the average size wall transformer. I found the absolutely biggest one of the proper voltage, rigged a plug to it, and gave it a try. It held out, but ran super hot too. I used this setup for a while until I noticed that the power supply on the CCBus board was running so hot that it melted the plastic cover. The standard PC hard disk interfaces are apparently quite power hungry At that point I gave up and got the MPI. A *LOT* more reliable (if physically more inconvenient). Give a yell if you need more specific information. ***** Dennis ***** #: 5281 S9/Utilities 17-Jul-90 02:08:50 Sb: #5222-#Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Zack Sessions 76407,1524 (X) Could you give me the formula for translating directory information into something readable? It would save me a headache.... It sure is different than good ol' RSDOS dirs! I'm still in the learning mode for this baby! I just resently conceived how basic09 disk I/O works in setting up files. I'm used to the old 'FIELD' command from BASIC. It certainly has opened new doors for me! I have some great ideas brewin'! Thanks for the help. There is 1 Reply. #: 5284 S9/Utilities 17-Jul-90 04:31:02 Sb: #5281-#Reading OS9 Directorys Fm: Kevin Darling (UG Pres) 76703,4227 To: George Hendrickson 71071,2003 (X) George - yah, someone should do a tutorial on the dir layout. It's really quite simple. The technical manual (RBF) section has the details, but it takes some snooping around on a disk to put two and two together. Do you have the dEd disk editor downloaded? That tool will be very helpful in checking out the disk setup... a must-have program. Once familiar with it, a tutorial will be easier to follow. It usually only takes about 20 minutes to teach someone over the phone to fix and follow his os9 dir structure, in my experience. I'll look into writing something up (if someone doesn't beat me to it - please! grin). Kev There is 1 Reply. #: 5315 S9/Utilities 18-Jul-90 11:20:55 Sb: #5284-#Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Kevin Darling (UG Pres) 76703,4227 (X) Yeah, I have the dEd program. That can be very useful. What we need is tutorial on reading directorys as opening a file, getting the information and converting it into something readable like a 'dir e' would do in Basic09. That is the only thing holding me back at this moment from writing a badly needed utility. I work alot of hours so I don't get to devote the time that I would like to to figure out how to get that information. The best I get to is to read the manual while working. Now that's fun! If I could just get a little push in the right direction, I could really get started on a few things. The manual tells what certain things do by using syscall, but it doesn't tell you how to convert the information into something readable. We need a book called "Inside Basic09" real bad! ...Anybody wanna write it?{ If I didn't have to work so much..... There are 2 Replies. #: 5321 S9/Utilities 18-Jul-90 15:52:13 Sb: #5315-Reading OS9 Directorys Fm: Kevin Darling (UG Pres) 76703,4227 To: George Hendrickson 71071,2003 How about a different (and possibly easier to answer in a msg) slant on this... would a basic program which opened the current dir and printed a "dir e" style output give you enough of a jumpstart? I'd bet that several people here could whip one out.... a specific request tends to find responses. ? #: 5323 S9/Utilities 18-Jul-90 17:17:04 Sb: #5315-Reading OS9 Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 George - Piece'o'cake... Just open the directory as you would any file, and instead of just READ, open it for READ + DIR modes. Then, read it in 32 byte chunks. The chunks are broken down: filename[29] LSN_of_FD[3] If the 1st byte of filename is 0, then the file has been deleted. Also, filenames may be less than 29 characters. The last character always has the high-bit (i.e. 'A' + $80 = $C1) set. The LSN is the absolute sector number where that file's File Descriptor Sector (FD) is stored. In the FD sector is all the information about file owner, dates, attributes, size, and physical mapping on the disk. Best bet is to read the technical manual on the RBF file manager to get detailed breakdown on this. BTW - what's the utility? It's hard to imagine a flavor of directory based utility that hasn't already been written for OS9. Pete #: 5373 S9/Utilities 20-Jul-90 03:26:18 Sb: #5321-Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Kevin Darling (UG Pres) 76703,4227 (X) BINGO! I believe that hit the nail on the head! The program that I intend to write (when I get the time) will have the option of passing what directory that the user would like a certain file in. (ex: makefile /h0/bbs) Is there any special things I should know about that other than using the 'PARAM' command? I've got that down... Thanks for the help....... #: 5374 S9/Utilities 20-Jul-90 03:34:17 Sb: #5323-#Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) Thanks for the info! I'll toss that up in the air and see where it lands. The utility that I plan to write will be a 'desc.bbs' file editor for RiBBS v2.0. I haven't found one anywhere. Actually a person could use a wordprocesser to create the file but I want a program dedicated to that file. It can be a pain to add, delete, purge etc... filenames from it by going thru it one filename at a time. The utility will be able to allow the sysop to make a list of filenames to purge and then delete then instantiously. My idea is sort of a screen editor type program. The only problem I was having was the reading the directory thing. There is 1 Reply. #: 5378 S9/Utilities 20-Jul-90 09:59:00 Sb: #5374-Reading OS9 Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 George - Okay... there are plenty of tools (and styles) that have been comitted to the directory listing concept. Just wanted to make sure you weren't reinventing the wheel. Pete #: 5466 S9/Utilities 22-Jul-90 15:33:29 Sb: #5378-Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 Naw, just writing a utility that will help maintain my dload file. I could have had it done by now if I didn't have to work 6 days a week! Geezz...I need a break....I wanted to ask you about the LSN number. The LSN points to the sector that has the info that I'm looking for correct? Ddo I use syscall to get the information by passing the register number for a certain thing? ex: attributes.... #: 5479 S9/Utilities 23-Jul-90 08:41:56 Sb: #5466-#Reading OS9 Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) Right - the FD sector has all the info ABOUT the file (owner, size, dates, attributes). Best approach has been found to open two paths. One to the directory you're reading, and one to the whole RAW disk (i.e. /DD@). This way, when you read the LSN # from the directory, you can seek to the LSN * 256 on the RAW disk path and get right to the file's info. This is much faster than opening each file and doing an SS.FD getstat on it. Pete] There is 1 Reply. #: 5483 S9/Utilities 23-Jul-90 12:15:51 Sb: #5479-Reading OS9 Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) Oh I see..thanks for the help. I'll get right on it. Than I hope to make this program a good one. #: 5507 S9/Utilities 24-Jul-90 12:32:01 Sb: #Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) I've been working on my utility and got it to read the directory and print the filenames and the LSN numbers. I set it up to read the directory using TYPE. Here is how I did it. 'TYPE direntry=name:STRING[29]; lsn0,lsn1,lsn2:BYTE' When I tell it to print each filename, after resetting the last character of the filename, and print the LSN's 0-2, this is what it looks like. e.g. FILENAME LSN0=0 LSN1=119 LSN2=203 Which one of those do I use to 'SEEK' to the filenames FD sector and get my info? Do I have to multiply the lsn's together to get that sector number? And if so, what's the formula? (I'm getting closer! This is fun!) OS9 has opened all new doors to me...amazing stuff! There is 1 Reply. #: 5508 S9/Utilities 24-Jul-90 13:58:47 Sb: #5507-Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 George - Yep - you're on the trail.... here's the scoop: The LSN is a 3 byte number. Basically, the breakdown is - MSB * 256 * 256 + NSB * 256 + LSB ======================== LSN # In C, there are functions for taking these three bytes and making a LONG INTEGER out of them (and back). Under B09, you may have to use a type REAL, since the result is greater than +/- 32767. Pete #: 5542 S9/Utilities 25-Jul-90 11:07:53 Sb: #5508-#Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) All right! I knew that 256 had something to do with it but wasn't sure what the formula was. Thanks alot for the help. There is 1 Reply. #: 5543 S9/Utilities 25-Jul-90 15:01:13 Sb: #5542-Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) De nada, George. Let us know how it comes out. Pete #: 5615 S9/Utilities 27-Jul-90 11:59:15 Sb: #Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) I thought I'd show you what I've come up with so far. I've been having trouble with 'seeking' the sector were the FD is stored. As before, I have the dirpath set up like this: TYPE direntry=name:string[29]; lsn0,lsn1,lsn2:BYTE DIM direc:direntry This worked fine for reading just the filenames. I set up a second path like this to get the rest of the info: TYPE dirsec=fdatt:BYTE; fdown:INTEGER; y,m,d,h,mn,fdlink:BYTE;fdsiz1, fdsiz2:INTEGER; y1,m1,d1:BYTE;fdseg:STRING[240] DIM dirnfo:dirsec What is happening is, it will read the directory, determine where the sector is by converting the varibles lsn0,lsn1,lsn2 in the sector number using this formula: sector=((direc.lsn0*256)*256)+(direc.lsn1*256)+direc.lsn2 then 'seeking' the second path to the sector, getting to that path 'dirnfo' and printing the results. (e.g. dirnfo.fdatt, dirnfo.fdown etc..) But after a couple of records, I get an error 203. Do I have the sector formula right? I tried 'seeking' the sector x 256 but that gave me an error 203 right away. I also tried seeking to (direc.lsn1*256) also and got the same results. There is 1 Reply. #: 5616 S9/Utilities 27-Jul-90 12:55:56 Sb: #5615-Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 A couple of questions: a) Is 'sector' declared as a REAL? b) The second path... how did you open it? It should have been something like OPEN /DD@, READ (not being a B09'er...) c) Is the information you DO get valid? d) Error 203 is 'Illegal Mode'... usually should occur at time of OPEN. If you're processing multiple directories, you still only need to open /DD@ one time. e) Are you closing the DIRECTORY after finsihing with it, and before moving on to another one? Pete #: 5692 S9/Utilities 29-Jul-90 20:44:49 Sb: #Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) Here's a little info to show you what I've done so far. I couldn't put the whole program here because the maximum lines are 51 so...I'll give as much info as possible. I took a few things out so that it would fit. PROCEDURE readdir 0000 DIM dirname:STRING[80] 000C TYPE direntry=name:STRING[29]; lsn0,lsn1,lsn2:BYTE 002A DIM direc:direntry 0033 TYPE dirsec=fdatt:BYTE; fdown:INTEGER; y,m,d,h,mn,fdlink:BYTE ; fdsiz1,fdsiz2:INTEGER; y1,m1,d1:BYTE; fdseg:STRING[240] 0081 DIM dirnfo:dirsec 008A DIM dirpath,dirpath1,k:BYTE 0099 DIM nam:STRING[29] 00A5 DIM sect,s0,s1,s2,c0,c1,c2:REAL 00C4 DIM counter:INTEGER 00CB PRINT CHR$(12) 00D0 GOSUB 999 00D4 counter=0 00DB INPUT "Read which directory? ",dirname 00F9 dirname:=TRIM$(dirname) 0102 IF dirname="" THEN END 010F ENDIF 0111 (* 0114 (* Open directory 0125 (* 0128 OPEN #dirpath,dirname:READ+DIR 0134 OPEN #dirpath1,"/dd":READ+DIR 0142 WHILE NOT(EOF(#dirpath)) DO 014D counter=counter+1 0158 GET #dirpath,direc 0162 GOSUB 1000 0166 GOSUB 2000 016A SEEK #dirpath1,s1 0174 GET #dirpath1,dirnfo 017E IF k=0 THEN 10 0190 (* Was printing information to screen here *) 039E ENDWHILE 03A2 1000 (* Reset last byte on filename and return. Line 999 reset var. 04EF 2000 (* Determine FD sector 0508 c0=ASC(CHR$(direc.lsn0)) 0516 c1=ASC(CHR$(direc.lsn1)) 0524 c2=ASC(CHR$(direc.lsn2)) 0532 s0=c0*256*256 0544 s1=c1*256 0551 s2=c2 0559 sect=s0+s1+s2 0569 RETURN There is 1 Reply. #: 5709 S9/Utilities 30-Jul-90 07:42:33 Sb: #5692-#Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) George - Your problem is one of the 4 possible things I'd suggested... Instead of opening /DD@ for READ, you're opening /DD for READ+DIR. The difference is monumental. OPening /DD for DIR+READ simply opens the ROOT directory for reading. OPening /DD@ for READ opens the whole DISK so that you may read it sector by sector (including the LSN0, bitmaps, and everything else). That appears to be the major problem here (still pre-coffee here, so I haven't digested all of the rest). Pete There is 1 Reply. #: 5724 S9/Utilities 31-Jul-90 13:42:59 Sb: #5709-#Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) What's the syntax for opening '/DD@'? Is it just a simple OPEN #path, "/DD@":READ? There are 2 Replies. #: 5726 S9/Utilities 31-Jul-90 16:06:33 Sb: #5724-Reading Directorys Fm: Zack Sessions 76407,1524 To: George Hendrickson 71071,2003 (X) yes #: 5732 S9/Utilities 31-Jul-90 18:55:52 Sb: #5724-#Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) Yep - pretty much that simple. Pete There is 1 Reply. #: 5761 S9/Utilities 01-Aug-90 16:44:33 Sb: #5732-#Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) Dah...I sometimes can't see the trees for the forest. Ever have that problem? Thanks. I'll try that out. There is 1 Reply. #: 5766 S9/Utilities 01-Aug-90 21:41:29 Sb: #5761-Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 George - The "forest for the trees" syndrome is all too familiar to most of us. You are in good company. How's it working, by the way? Pete #: 5776 S9/Utilities 02-Aug-90 04:02:00 Sb: #5766-#Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) I DID IT!!!! I got it to read correctly and I can see what it is doing now. I'll finish writing this little demo for everyone to look at. It will read a directory and show it in a 'dir e' type listing. I should have it done pretty soon. I feel like I'm coming down the other side of the mountain! (whew!) I'll leave you a message when I upload it. Thanks for the help! George There is 1 Reply. #: 5777 S9/Utilities 02-Aug-90 08:50:27 Sb: #5776-#Reading Directorys Fm: Pete Lyall 76703,4230 To: George Hendrickson 71071,2003 (X) George - Good deal! Glad we were able to lend a hand. Pete There is 1 Reply. #: 5832 S9/Utilities 04-Aug-90 13:25:48 Sb: #5777-Reading Directorys Fm: George Hendrickson 71071,2003 To: Pete Lyall 76703,4230 (X) I've got it all together. I'll upload it now. The filename will be readdir.pak or something like that. #: 5871 S9/Utilities 05-Aug-90 11:55:27 Sb: Revised Touch Fm: Ken Drexler 75126,3427 To: all I have just uploaded a revised version of my touch command to Lib 9 (Utilities). Unlike the version uploaded a month or so ago, if the file to be touched is not found, one is created. This conforms its behavior more closely to the touch command on OSK. Sorry I did not think of this when I originally wrote touch.c, but I invariably touch existing files. Ken #: 5920 S9/Utilities 07-Aug-90 20:03:06 Sb: #go? Fm: Zack Sessions 76407,1524 To: Pete Lyall Pete, I'm trying to find a copy of your GO utility. Is it here on CIS? Thanks, Zack There is 1 Reply. #: 5928 S9/Utilities 07-Aug-90 23:37:23 Sb: #5920-go? Fm: Pete Lyall 76703,4230 To: Zack Sessions 76407,1524 (X) Zack - I modified it, but it wasn't mine... I believe it came from the UGLIB, which still has a number of really neat tools that most folks haven't checked out. I *think* Bill Dickhaus might have also whacked on it, so check with him as well - or possibly Mark. In any case, Mike Ward can extract it from the UGLIB archives and upload it for you, if you need it. Pete #: 6134 S9/Utilities 14-Aug-90 20:55:50 Sb: #PAK utilities Fm: STEPHEN WALLACE 73720,2420 To: sysop (X) Where do I find info on how to unpak *.pak files? Where do I find a utility to unpak *.pak files?/exit There is 1 Reply. #: 6135 S9/Utilities 14-Aug-90 21:53:42 Sb: #6134-PAK utilities Fm: Pete Lyall 76703,4230 To: STEPHEN WALLACE 73720,2420 (X) Stephen - Check in DL9 or DL10 for PAK*.* .... Pete #: 6191 S9/Utilities 18-Aug-90 11:41:04 Sb: #hdbackup modification Fm: Ken Drexler 75126,3427 To: Mark Griffith, 76071,41 Mark, Last weekend, I spent ten hours using your hdbackup to backup hard disk. It is a slick program. The fact that the files remain individually readable is a great advantage. I did run into one small hitch. At one of the "Insert next disk" prompts, I bounced the return key. Of course, meant that when the current disk was full, the program skipped through the next swap disks prompt without stopping. Although I was able to continue the backup using ^S to stop the program and a second terminal to build the needed directories on the new disk, I decided to modify the code to eliminate the problem. Actually I made two changes. Both are in swap_disk(). One deals with the double RETURN problem which I had. The other gives the user the option of running a shell command at each disk swap prompt. This latter change allows the user to format disks, for example. I have tested my changes and think they may be useful to others. The changed code in swap_disk is in the following message. It replaces your code up to "if (flag == FULL)". If it looks useful, you are free to include in a future upgrade of hdbackup. Ken There is 1 Reply. #: 6207 S9/Utilities 19-Aug-90 08:05:19 Sb: #6191-hdbackup modification Fm: Mark Griffith 76070,41 To: Ken Drexler 75126,3427 Ken Thanks for the nice comments. I'm glad you like it. And thanks for the code....I'll look it over. Mark #: 6192 S9/Utilities 18-Aug-90 11:42:10 Sb: hdbackup modification Fm: Ken Drexler 75126,3427 To: 76071,41 swap_disk() /* modified to allow commands and cleanout stdin */ { int i; int c; /* KD */ BEEP BEEP BEEP do /* Start KD */ { printf("\nInsert next disk and press ENTER to continue\n"); printf("or type command line:\n"); fgets( tempstr, sizeof(tempstr), stdin ); /* get input */ sleep( 1 ); /* wait for bounce if any */ for( i = 0; i < 10; i++ ) /* clean out input stream */ if( _gs_rdy(fileno( stdin )) > 0 ) c = getchar; if( *tempstr != '\x0d' ) system( tempstr ); /* ignore errors */ } while( *tempstr != '\x0d' ); /* end KD */ gets(tempstr); */ #: 6470 S9/Utilities 02-Sep-90 20:20:47 Sb: #extension Fm: Stanley L. Goldsberry 72060,2720 To: [F] All I understand most of the extensions. such as asm, bin, txt,b09 but what is significant about the PAK extension is there a tutorial on this Also I need the IPATCH utility mentioned in the CC3DISK to complete the cc3disk patch do you know what library it is in I can't seem to find it in DL9 signed stan goldsberry 72060,2720 There are 2 Replies. #: 6471 S9/Utilities 02-Sep-90 21:25:45 Sb: #6470-extension Fm: Mike Ward 76703,2013 To: Stanley L. Goldsberry 72060,2720 (X) Stanley, PAK is just another file compression program. See PAK.BIN in Lib 10. It's pretty self documenting if you invoke it with no arguments. I took the liberty of forwarding your message to "All" so that one of the other folks could help with the Ipatch question. #: 6472 S9/Utilities 02-Sep-90 23:16:30 Sb: #6470-extension Fm: JOHN R. WAINWRIGHT 72517,676 To: Stanley L. Goldsberry 72060,2720 (X) Hi Stanley, Probably, the reason you can't find "IPATCH" is because it is contained in an archive called "PATCH.AR" in DL-10 - pretty sneaky, heh? I see Mike Ward already answered your other question. Anyway, go to DL-10 and download "patch.ar". JohnW #: 6628 S9/Utilities 09-Sep-90 14:57:39 Sb: #GO.ASM Fm: Zack Sessions 76407,1524 To: Pete Lyall 76703,4230 (X) Pete, I'm having a bit of a problem with go. In the doc file you state the way to invoke a command macro to enter: go . You go on to describe the and the which I assume are the previously mentioned. You state that the arguments must be pathnames. This is confirmed upon inspection of the source reveals you parse the command line with a F$PNAM system call. This forces the arguments to comply with OS9 pathname convention. My situation is that I want to call up a procedure file from cron using a go script nut use as the arguments. It is a procedure file will calls my pager. My pager requires a numerical code to display. You now say, well you have the source, fix it yourself! Well, I've tried that, too. But simply trying to compile it with LI ASM, I get an error, "Can't open /d0/defs/os9defs". The program source refers to /dd/defs/os9defs. ASM itself does not contain the character string /d0. Any idea why ASM is requiring this defs file to be in /d0/defs when both the source and ASM do not refer to /d0? Thanks, Zack There are 2 Replies. #: 6632 S9/Utilities 09-Sep-90 17:02:10 Sb: #6628-#GO.ASM Fm: James Jones 76257,562 To: Zack Sessions 76407,1524 (X) Hmmm. What does the file /dd/defs/os9defs contain? There are 2 Replies. #: 6637 S9/Utilities 09-Sep-90 19:58:31 Sb: #6632-GO.ASM Fm: Zack Sessions 76407,1524 To: James Jones 76257,562 (X) It is the defs file which came off of a LI disk. It does not reference /d0, either. Zack #: 6640 S9/Utilities 09-Sep-90 22:20:36 Sb: #6632-GO.ASM Fm: Zack Sessions 76407,1524 To: James Jones 76257,562 (X) The problem was /dd/defs/Defsfile which contained references to four /dd/defs , whoops, /d0/defs files. Thanks for the idea, Zack #: 6650 S9/Utilities 10-Sep-90 11:56:25 Sb: #6628-#GO.ASM Fm: Pete Lyall 76703,4230 To: Zack Sessions 76407,1524 (X) Zack - Are there any other USE directives? Also, does the defs file itself have a reference to a /d0 pathname? Pete P.S. GO isn't mine... I did a bit of fixing, but it originated in the UGLIB. Quite a goldmine in there really. Had I written it, I would have allowed non pathname arguments, etc. May rewrite it in C when the MM/1 arrives. There is 1 Reply. #: 6653 S9/Utilities 10-Sep-90 17:17:40 Sb: #6650-GO.ASM Fm: Zack Sessions 76407,1524 To: Pete Lyall 76703,4230 Found the defs problem, see an earlier message in the thread to JJ. Decided not to fix the asm program but to do a C re-write myself. It is 80% done. Zack #: 6721 S9/Utilities 16-Sep-90 01:07:51 Sb: New TREE Fm: Greg Morse 72746,3451 To: all I have just uploaded NTREE (new tree) pgm to dl9. doing "NTREE /DD ! GREP pattern" will serve as a poor man's whereis. #: 7436 S9/Utilities 16-Oct-90 19:02:42 Sb: #Rssave Fm: KEVIN JOHNSON 76475,1106 To: Zack C. Sessions 76407,1524 (X) I appreciate what you have done with rssave.ar, but why can't the device names be passed as parameters. Also why assume that RSDOS is located in There is 1 Reply. #: 7451 S9/Utilities 16-Oct-90 22:15:20 Sb: #7436-Rssave Fm: Zack Sessions 76407,1524 To: KEVIN JOHNSON 76475,1106 Some of your message got cut off. I figured only one device would ever be specified, that being the device which has the RSDOS disk in it. I mention in the docs that this characterstring constant was located in only one place and how to patch it for something other than /d0. Was that not enough? Zack #: 7437 S9/Utilities 16-Oct-90 19:08:23 Sb: #Cron Fm: KEVIN JOHNSON 76475,1106 To: Mark Griffith 76070,41 I have found cron only. There is 1 Reply. #: 7445 S9/Utilities 16-Oct-90 20:55:31 Sb: #7437-Cron Fm: Pete Lyall 76703,4230 To: KEVIN JOHNSON 76475,1106 Kevin - GO was in the UGLIB database (DL5). If not there presently, ask Mike Ward (76703,2013) to pull it from the archives for you. Another tool you may like is 'dispatch.ar' in DL9. Enjoy... Pete #: 7640 S9/Utilities 21-Oct-90 21:29:08 Sb: #7451-#Rssave Fm: KEVIN JOHNSON 76475,1106 To: Zack Sessions 76407,1524 (X) Mainly, I didn't see way you would assume RSDOS to be located in /dd/cmds. There is 1 Reply. #: 7642 S9/Utilities 21-Oct-90 21:55:28 Sb: #7640-#Rssave Fm: Zack Sessions 76407,1524 To: KEVIN JOHNSON 76475,1106 (X) Where else would it be? There is 1 Reply. #: 7833 S9/Utilities 28-Oct-90 10:35:19 Sb: #7642-#Rssave Fm: KEVIN JOHNSON 76475,1106 To: Zack Sessions 76407,1524 (X) Anywhere a user choose to place it. There is 1 Reply. #: 7882 S9/Utilities 28-Oct-90 22:32:09 Sb: #7833-Rssave Fm: Zack Sessions 76407,1524 To: KEVIN JOHNSON 76475,1106 why not your current CMDS directory. that is where you usually load it from. #: 8121 S9/Utilities 11-Nov-90 16:01:19 Sb: #Cron help Fm: Ken Drexler 75126,3427 To: Ted Miller 76545,457 (X) Ted, Sorry so see you had problems with my ramdisk running on a CoCo. Since seeing your message, I have tried ramdisk on my machine with cron and had no difficulty. I wonder if it is in the CoCo's implementation of F$MapBlk or F$ClrBlk or in you version of cron. I the cron I have is by Pete Lyall and is downloaded from here. It is edition 5 and has a size of $38D and a crc of $A6D46E. It recognizes in turn /r0 and /dd. It also looks for /nl or /nul to dump its i/o to/from. If you could provide more information, I could try and run down why ramdisk did not work on your CoCo with cron. (Did you have /nl or /nil in memory?) Ken Drexler 75126,3427 There is 1 Reply. #: 8207 S9/Utilities 15-Nov-90 22:04:39 Sb: #8121-#Cron help Fm: Ted Miller 76545,457 To: Ken Drexler 75126,3427 (X) Thanks for responding to my message concerning cron and your ramdisk driver. Your message prompted me to start experimenting again and I've come up with the following observations. When I start cron (i.e. cron -l&), and before cron errors out, if I try to access the ramdisk I get an error 241 (sector error). When cron errors out,after a minute has passed, I can access the ramdisk again with no problem. The cronerrs file reports "cannot open /r0/sys/crontab". If I try to start cron without forking (i.e. cron), and then press the Break key to end the process, the ramdisk is permanantly scrambled. All I get is error 241 when the ramdisk is accessed. I have to deiniz the ramdisk and then iniz again in order to use the ramdisk once more. BTW I have the same version of cron that you have and I have no problem with cron when using Kevin Darlings ramdisk. Here is another strange anomaly that I have noticed when using your ramdisk. Recently I have been working on learning 'C'. To this end I use a simple interface program called devsys that enables one to set the compiler options,run the compiler and call an editor at the press of a key. I use a version of 'cc' written by Pete Lyall that uses a ramdisk for all its files. Ordinarily this combination works very well with your ramdisk. However I have two boot disks, the only difference being that one has Vdgint installed and the other one doesn't. When I boot with Vdgint installed I have problems with the above setup. When 'devsys' calls 'cc' to compile my source code it errors out with error 213 (non existing segment). However if I switch to another window and call 'cc' manually the file compiles with no problems. Please note that the existence of Vgdint in the boot has no bearing with cron not working I couldn't even hazard a guess to what is going on. Right now the advantage of the ease of calling and removing your ramdisk outwieghs the above problems and I thank you for supplying it. Ted Miller There is 1 Reply. #: 8273 S9/Utilities 17-Nov-90 11:17:36 Sb: #8207-Cron help Fm: Ken Drexler 75126,3427 To: Ted Miller 76545,457 (X) Ted, Thanks for the message. I will have to scratch my head a while to see if I can figure out what is going (or not going) on. I think from you description, I can eliminate cron as a suspect. Beyond that I need some think time. I will get back to you. Ken #: 8150 S9/Utilities 12-Nov-90 18:36:36 Sb: #7882-#Rssave Fm: KEVIN JOHNSON 76475,1106 To: Zack Sessions 76407,1524 (X) No, it is where YOU might usually load it from! Where I load it from is MY choice. Sorry to be so buggy, but I think you're ignoring the OS9 concept. There is 1 Reply. #: 8175 S9/Utilities 13-Nov-90 16:01:35 Sb: #8150-Rssave Fm: Zack Sessions 76407,1524 To: KEVIN JOHNSON 76475,1106 (X) I simply do a "load RSDos", just EXACTLY like dsave does a "load copy". That way it gets loaded from your current execution directory which is wherever you have done a CHX to. Isn't that the "OS9 concept"? The intention was to make a utility command similar to dsave which used RSDos instead od copy. Which RSSave does very well. You are the only person who has made such a comment about this utility. You are also the first person to accuse me of "ignoring the OS9 concept". I don't think I am since the RSSave command works JUST LIKE the standard OS9 dsave command. Zack #: 8250 S9/Utilities 16-Nov-90 17:53:05 Sb: #HELP.... Fm: MICHAEL ROSEN 73340,2756 To: ALL I'M NEW AT OS-9 AND I'M WONDERING WHAT/HOW CAN I DOWNLOAD A PROGRAM FOR OS-9 AND CONVERT IT TO OS-9. I'VE TRIED USING A PROGRAM THAT MAKES A RS-DOS DISK READABLE BYU OS-9 BUT I CANNOT LOAD IT,EITHER UNDER SHELL OR BASIC09... I'M USING MIKEYTERM RIGHT NOW AT 2400 BAUD AND IT DOES WHAT IT'S SUPPOSED TO ANYHOW... WELL I HOPE I FIGURE THIS OUT SOON. THANKS... MICHAEL ROSEN <73340,2756> There is 1 Reply. #: 8253 S9/Utilities 16-Nov-90 20:03:49 Sb: #8250-HELP.... Fm: Kevin Darling (UG Pres) 76703,4227 To: MICHAEL ROSEN 73340,2756 (X) Hi Michael - you're probably pretty close... does a "dir /d1" (or wherever) of the disk you tried to make readable, show any files? If so, then you're in good shape. Now copy the files over to a *real* OS9 disk.... where you can do more operations on them (the rsdos->os9 disk thingie doesn't really make it a full os9 disk, so you must get the files onto a real os9 disk). From there, we'll have to give a little more help, I suspect... which will depend upon which files you downloaded. Some files are archived (compressed) and need Ar (AR09.BIN in lib 9) to break out, some are ready-to-go (you'll have to do "attr filename e pe" on those to make them loadable; and some may be text files etc... just as with any computer downloads. Let us know which files, and we'll get you rolling quickly as possible. best - kev #: 8338 S9/Utilities 19-Nov-90 17:52:28 Sb: HELP.... Fm: MICHAEL ROSEN 73340,2756 To: KEVIN DARLING THANK YOU VERY MUCH FOR THE HELP KEVIN.. I WILL TRY ALL OF THAT AS I LOG OFF AND REBOOT OS-9. ANSWERING YOUR QUESTION ON MY SYSTEM, I HAVE A 128K COCO 3,2 TEAC DSDD DRIVES, A MPI, DMP 130A PRINTER, RS-232 PAK, ORCHESTRA 90, X-PAD, PLUG-N-POWER CONTROLLER (OLD & NEW STYLE),AND 2 64K COCO 2'S.... I ALSO HAVE AN UNPOPULATED 512K BOARD,BUT I'M NOT SURE WHAT MEMORY CHIPS TO USE OR IT WOULD BE INSTALLED.. I'M USING A COMPUTER PERIPHERALS VIVA 24 MODEM (2400 BAUD) WELL THATS MY TOYS I GUESS I'LL PLAY WITH MY OS-9 FOR A WHILE AND TRY TO GET THE HANG OF IT.... MAYBE A FEW OF US CAN GET TOGETHER ONE EVENING AND CHAT ON CONFERENCE FOR A FEW... THANKS AGAIN, MICHAEL ROSEN 73340,2756 #: 8406 S9/Utilities 25-Nov-90 11:56:58 Sb: #spell package Fm: Ken Drexler 75126,3427 To: Bob van der Poel, 76510,2203 (X) Bob, I have been using your improved spell checker in my law office. It is a great inprovement on Eric Williams original. After getting used to the old checker, its is a flash! Recently I tried to add words to the dictionary and ran into a problem with dicmerge. When it ran it correctly merged the two files until file2 ran out. At that point the program as written stopped copying words from file1 to the output file. The result is that the output file ends after the last word of file2. The problem seemed to be in the exit conditions on the while loop. In order to fix this, I revised the while contidion to depend only on the lack of eof on file1 and add a flag which is set when there is an eof on file2. Once the flag is set, all of file1 will be copied to the output. I have uploaded the revised dicmerge.c and asked sysop to forward it to you for your use or posting. It is not a perfect solution because it depends on file2 running out first. I could not think of a way to have it handle eof on either file easily. Ken Drexler There are 2 Replies. #: 8407 S9/Utilities 25-Nov-90 12:18:13 Sb: #8406-spell package Fm: Steve Wegert 76703,4255 To: Ken Drexler 75126,3427 (X) Ken, I've forwarded a copy of the code to Bob and await his word. Thanks for the effort! Steve #: 8433 S9/Utilities 26-Nov-90 20:51:33 Sb: #8406-#spell package Fm: Bob van der Poel 76510,2203 To: Ken Drexler 75126,3427 (X) Ken, I've sent you an update via email. Hopefully this works and you can post it for the rest of the gang. There is 1 Reply. #: 8443 S9/Utilities 27-Nov-90 10:42:22 Sb: #8433-spell package Fm: Ken Drexler 75126,3427 To: Bob van der Poel 76510,2203 Bob Thanks for the update I will grab it and give it a try. Ken #: 8436 S9/Utilities 26-Nov-90 23:17:15 Sb: #new OS-9/6809 uploads Fm: Bruce Isted (UG VP) 76625,2273 To: All Hi all, I've finally uploaded some of the stuff that's been hanging around in a half finished state. More to come shortly, but for the moment, check out LIB 10 for SMOUSE.AR, and improved serial mouse patch set for CC3IO. Also includes a version for regular color joystick/mouse users, and all patches incorporate Kevin Darling's idea to enable IRQs during keyboard scan. This improves IRQ response to the mouse and also to other serial devices. In LIB 9 look for CHOPTHRD.AR (large message thread file stripper/chopper), INPUTS.AR (Line Input and Stripped Line Input subroutines for Basic09), and SLOWIO.AR (slow I/O filter utility) if you're interested in those sorts of things. Updates to my ELIMSW.AR package and a new WDDISK.AR package are coming soon. The ELIMSW.AR file will include a new 6551 ACIA driver that works much like my DACIA driver for the 6552 dual ACIA. Should provide reliable operation at 9600 baud when used with the new SMOUSE.AR's CC3IO patches. Bruce There is 1 Reply. #: 8441 S9/Utilities 27-Nov-90 08:31:46 Sb: #8436-new OS-9/6809 uploads Fm: Pete Lyall 76703,4230 To: Bruce Isted (UG VP) 76625,2273 Bruce - There's been a fellow with a HD formattin problem chatting w/me. Does your (any?) S/W support cluster sizes > 1? He has a 230 MB hard drive, and can't seem to locate a formatter to handle the size... Pete #: 8446 S9/Utilities 28-Nov-90 15:19:58 Sb: Formatter Fm: Frank Russell 74020,1135 To: all I am looking for a new format comand that will handle multiple clusters I recently picked up a 230mb RLL HD and can oly format 120 ANY SUGGESTIONS??? Thanks Frank