8bitfiles.net/archives

home *** CD-ROM | disk | FTP | other *** search

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / SUPERBASE.SFX / superbase.msgs

Wrap

Text File | 1990-02-12 | 35.1 KB | 866 lines

rea 12 1-40 nor ************ Topic 12 Sat Oct 23, 1993 MRABOY (Forwarded) Sub: Superbase 3.01 KEEP US GOING!!!! 80 message(s) total. ************ ------------ Category 3, Topic 1 Message 1 Sat Oct 23, 1993 MRABOY (Forwarded) Doug, thanks to CMD I finally got SB vs.3.01 on a 3.5 inch disk. I have been trying to get this for a year. Now I need to get multiplan 128 on a 3.5 inch disk. It seems that I am the only person using this program, but it is still the best spreadsheet. I've tried them all. Maybe CMD can find a way or maybe CMD can write a program for its sophisticated hardware called CMD 1 2 3 . Anyway just dreaming. Thanks, Mike :) ------------ Category 3, Topic 12 Message 2 Sat Oct 23, 1993 H.HERMAN1 (Forwarded) ha! I don't know how long the topic police will allow this one to hang around so I'll add my 2 cents to the *wish list*, and it is for all 3 Pocket programs: Writer3, Filer2 and Planner2 to be on one 1581 disk that has NO COPY PROTECTION! Yea! That is what I want!!! Howie ------------ Category 3, Topic 12 Message 3 Sat Oct 23, 1993 THE.OUTLAW (Forwarded) I'd like to see that myself :> ------------ Category 3, Topic 12 Message 4 Sun Oct 24, 1993 MIKE.DUNCAN (Forwarded) Speaking of Superbase - I have the 128 version installed on a 1541 partition on my CMD HD. When I MCOPY'd it over - I got a read error, but it seems to work okay. The backup had an error too. Is this supposed to be copy protected? BTW. How do you guys have Superbase setup? Anybody? Mike D. ------------ Category 3, Topic 12 Message 5 Sun Oct 24, 1993 CMD-DOUG (Forwarded) It isn't unusual to get the error and still have it work. There were some 'hard' errors on the Superbase master disks that were not removed, even though the routines that check for them were. The current master disks are now clean, though, so anyone who gets a new one at this point won't see such error messages when copying. ------------ Category 3, Topic 12 Message 6 Mon Oct 25, 1993 C128.JBEE (Forwarded) With the new SB master disks, can you just file copy the needed programs to your 1581 subdirectory or do you have to MCOPY it? ------------ Category 3, Topic 12 Message 7 Mon Oct 25, 1993 CMD-DOUG (Forwarded) We got rid of the errors, JBEE, but we didn't rewrite the whole program! SB still uses block-reads to pull program itself into memory (and decripts the encrypted data within them as they are loaded, I might add...), so an MCOPY is still the only way. ------------ Category 3, Topic 12 Message 8 Mon Nov 15, 1993 R.NEAZER [Reub] (Forwarded) I am using Superbase 128 v3.01 Trying to create a display screen with a Header and output data. I am using the 'display' command to send the header to the screen and the 'output' command for the data. The problem is that the output command seems to clear the screen, erasing the header. Can anyone guide me in the right direction??. Thanks Reub....... ------------ Category 3, Topic 12 Message 9 Mon Nov 15, 1993 CMD-DOUG (Forwarded) Reub, Show the exact way you have display used in your program... that might help. There are a few different ways of using it - and it may simply be the way you are using it that is causing the problem. ------------ Category 3, Topic 12 Message 10 Tue Nov 16, 1993 R.NEAZER [Reub] (Forwarded) Hi Doug, Thanks for the response. My program looks like the following: display 'Last name'; 'First name' output all [lastname][firstname] There are a couple of more fields, but basically this is what it look like. The display creates the header but then the output clears the screen, erasing the header and putting the data on the screen.. Reub......... ------------ Category 3, Topic 12 Message 11 Tue Jan 25, 1994 R.SMITH32 (Forwarded) I just got an HD100/170 and currently use Superbase and a 1581 set to device 9 for data. Could you please tell me how to set up the HD so I can transfer my data to the HD. I've just done an inventory of our bookstore and would like to get this going right away. Thanks for all your help. Later R.SMITH32 ------------ Category 3, Topic 12 Message 12 Tue Jan 25, 1994 CMD-DOUG (Forwarded) Depends on what kind of partition you intend to use for the data, and if you plan to use a Native type, the size of the partition would also effect the answer. If you let me know those details, I'll be able to respond. ------------ Category 3, Topi 12 Message 13 Wed Jan 26, 1994 C128.JBEE (Forwarded) Here is how I use Superbase on the hard drive. First off, set your HD to device #8 so you do not have to worry about swapping the device numbers all the time. Second, create a 12800 blk, or bigger, native mode partition. Then run the 1581sub program on that partition and create a 1581 partition emulation. Next, file copy all the Superbase files over to that subdirectory. I have a tamed copy of SB, you might have to use bcopy? Then copy your file format to the partition. With the HD as #8 and the 1581 as #9, boot SB from the harddrive. Once booted, create a file from your file format (copied from your data disk) and create a new database into which you can import data. This means also creating a new "file". Now the tricky part, use the DATABASE command to close that database once it is created. Then do a directory. NOW - press swap 9 so the 1581 becomes #8 and the HD #9 Now, issue the DATABASE command, open the database on the 1581 and then use FILE to open the file. Now type EXPORT ALL TO "9:yourfile". Once SB has exported all the files to your HD into the 1581 sub, I suggest closing the 1581 database. Quit SB. Then reset the computer with the switch. Now, run SB from the 1581 sub (in the large native mode partition) on the HD. Once you are up and running within your empty database type IMPORT"8:yourfile". Done :) Now, when you do backups, you can either export to the 1581 EXPORT ALL TO "9:yourfile" or EXPORT ALL TO "8:yourfile" on the HD. If you do daily backups and your data is important, here is what I suggest. Do a daily export of all records to the 1581 as long as it is big enough. I usually do mind to a FD-4000 and it only takes about 1 hour for a very big file. Once you get so you have (30) full exports on 1581s (stored offsite of course!) start using ARC (since it is faster than LHA) to compress the oldest disks and then reuse them for a new export. That way, you do not use a large number of disks, but always have an emergency backup you can do pronto from the 30 day backups and always have the compressed files (be sure to arc128/v them) if by chance you ever corrupted a file and did not know about it. ------------ Category 3, Topic 12 Message 14 Wed Jan 26, 1994 R.SMITH32 (Forwarded) Jbee, would it change anything to know that I'm running on a C64 and booting Superbase from a 1541 and then switching to the 1581 as my data drive via the start.p program? Thanks again ------------ Category 3, Topic 12 Message 15 Wed Jan 26, 1994 R.SMITH32 (Forwarded) I just had a thought. My Superbase disk has a utility program that recovers databases. Could I use that to transfer my data from 1581 to HD since I've done it before from 1581 to 1581 or should I still use the import/export thing? Thanks again! ------------ Category 3, Topic 12 Message 16 Wed Jan 26, 1994 C128.JBEE (Forwarded) No, I assumed you were booting from a 1541/71. I do not think there is much difference (or any at all) between SB64 or SB128. The only thing I should have added is to turn the 1541 off when you have the HD as device #8 AFTER you have copied the files to the CMD HD, you can use FTTP to set it as device #10 while doing the file copying. I had the exact same setup (128, 1571, 1581, CMD 20) and that is how I moved all my SB files over. I always leave the 1571 off now and only use software (except for games) that works with the HD. ------------ Category 3, Topic 12 Message 17 Wed Jan 26, 1994 C128.JBEE (Forwarded) Well, maybe that utility would work okay, I have never tried it. I know the way I described works. Would not hurt to give either a shot. BTW: NEVER use duplicate keys - I found out the "strong suggestion" in the book should be "never" ------------ Category 3, Topic 12 Message 18 Thu Jan 27, 1994 R.SMITH32 (Forwarded) OK, the part I'm still a little fuzzy on is 'copy your file format to the partition' and 'create a file from your file format (copied from your data disk)'. Is there a file on my data disk that I need to physically copy over to the partition or do I just create a new file with the same fields? BTW I tried the recover utility and it didn't work. Thanks alot! ------------ Category 3, Topic 12 Message 19 Thu Feb 03, 1994 R.SMITH32 (Forwarded) I can't even get Superbase to boot from the HD yet. I copied the files over using FCOPY and the 2 block SEQ file from my data disk of the file definitions to the 1581 subdirectory but Superbase just reset when I tried to boot. I don't mind booting from the 1541 I just want to get my data to the HD Please help! Thank you for your patience. ------------ Category 3, Topic 12 Message 20 Thu Feb 03, 1994 R.SMITH32 (Forwarded) Eureka! I found an easy way to set up Superbase data on the HD. 1. Create a native mode partition on the HD of 12800 blocks 2. Run 1581sub on that partition. 3. Open that subdirectory and use the Utility program on your Program disk to recreate a data base. My data was on 1581 so I set my 1581 as device 8 and the HD as device 9. As long as you've opened the 1581 subdirectory you can copy everything right over;database definitions, file formats, everything. The Utility program handles it all. My next task is to learn to set up a boot disk on the HD. I think I'll set up a 1541 partition, MCOPY the boot disk to it and use the Start.p program to open up the right subdirectory. Time to look at the HD manual. Later ------------ Category 3, Topic 12 Message 21 Fri Feb 04, 1994 C128.JBEE (Forwarded) Darn! Did I forget to tell you to open the subdirectory? :P No reason to suffer with a 1541 subdirectory and have to change partitions and such. Superbase (v3.01) will run just fine from the 1581 partition. ------------ Category 3, Topic 12 Message 22 Fri Feb 04, 1994 R.SMITH32 (Forwarded) OK, here's where I'm stuck. I have my boot disk in a 1541 partition. I have my data in a 1581 subdirection in a Native mode partition. I can boot from floppy and access my data by switching to the right subdirectory before I boot and telling Superbase where the data is with the start program. But I can't boot from the HD and tell Superbase where the data is because I can't send disk commands from within Superbase. I can't use the FPPS mode because the data is in a subdirectory. Does ANYONE know a way to do it? Thanks ------------ Category 3, Topic 12 Message 23 Fri Feb 04, 1994 CMD-DOUG (Forwarded) You CAN send disk commands from within Superbase. Try Maintain Other. ------------ Category 3, Topic 12 Message 24 Sat Feb 05, 1994 R.SMITH32 (Forwarded) I saw that but the manual stated that only certain commands could be sent. I'll try to send the CP and CD commnands and see what happens. ------------ Category 3, Topic 12 Message 25 Sat Feb 05, 1994 R.SMITH32 (Forwarded) JBEE, I'd love to try your idea but I can't get my Superbase program files over to the 1581 sub. FileCopy didn't work. Mcopy is only for 1541 partitions. And Bcopy is only for CMD devices. How else can I get my program files to the 1581sub? Thanks ------------ Category 3, Topic 12 Message 26 Sat Feb 05, 1994 R.SMITH32 (Forwarded) Well, I finally got it! Thank you for all of your suggestions. Here's how. First my boot disk was Mcopied to a 1541 partition. Next my data was copied to a 1581 subpartition with the Utility program (copied from 1581). Then I modified my start.p program to send the CD command and placed it in the parent directory of the 1581 sub. After booting Superbase I used the FPPS mode to select the data partition's parent directory and the start.p program changed to the 1581 sub. It is now blindingly fast especially with my TurboMaster CPU. Thank again for all your help. Later ------------ Category 3, Topic 12 Message 27 Sat Feb 05, 1994 CMD-DOUG (Forwarded) Why not put a CP command in your start.p program as well? Then you could skip using FPPS. ------------ Category 3, Topic 12 Message 28 Sun Feb 06, 1994 R.SMITH32 (Forwarded) Because if i mess with the start.p program on my boot disk, it won't boot anymore. The modified start.p has to be on the data disk. Believe me, I've tried. So now when I'm prompted to insert my data disk after bootup I then change to the parent directory of the 1581 sub where I can put a modified start.p. ------------ Category 3, Topic 12 Message 29 Sat Feb 12, 1994 J.KARN (Forwarded) To RSmith32. Actually you can alter the start.p program on your Superbase boot disk if your really feel up to. I've done a similar thing to my Superscript boot disk sot that the default printdriver file is a customized file for my Star SD-10 with all the macros built in (e.g. ESC p to change drive partitions). Thing is, you gotta do it with a track and sector editor like Disk Doctor or Peek-A-Byte 128. As you know, any attempt to delete the old start.p program and replace it with a modified version just overwrites the damn copy protection scheme. Also the modified start.p program will have to be on a portion of the disk where there are no copy protection errors. Obviously, you only attempt this on a backup copy of the boot disk. J.Karn ------------ Category 3, Topic 12 Message 30 Sun Mar 13, 1994 D.SNYDER8 (Forwarded) To J.KARN Please describe in detail how you modified the superscript and superbase disks to allow the defaults files to be modified on the 'boot' disks. I use my 1581 for data but have to use an intermediate 'defaults disk' to get it to go to the 1581. I would LOVE to modify my disks to be able to change disks automatically. And I'll bet that there are many more who would enjoy the info too. ------------ Category 3, Topic 12 Message 31 Tue Apr 05, 1994 J.KARN (Forwarded) In a previous post I mentioned using a disk editor to modify my Superscript boot disk so it would load a customized print driver on booting. I've been asked for more details on how this was done. There's not a lot to it--probably easier to do than to describe. I'll try to make this brief, but clear. On loading, Superscript presents a menu with several options. Pressing RETURN with the boot disk in the drive loads the default print driver on the boot disk which is a CBM 801 driver. What I did was edit the disk so a customized driver for my SD-10 with a number of added macros was loaded instead. This requires the use of a disk editor such as Kevin Hisel's Disk Doctor. On BACKUP COPY of the Superscript boot, use the disk editor to examine track 18 sector 1. This is the directory track and the default print driver is called DEFAULT (or possibly DEFAULTS, can't remember at the moment). The first of the 3 bytes preceding the file name designates the file type, the next 2 the track & sector where the file begins. Since I was planning to overwrite the EPSON driver with my customized SD-10 driver, I modified the track & sector bytes preceding DEFAULT(S) to point to the EPSON driver instead (T=19 S=0). Just cursor down to the track and sector bytes for EPSON in the directory track to get the values. I then used the JUMP function of the disk editor to go to the start of the EPSON file and used the JUMP function to follow all the file links, making a list of all the tracks and sectors as I went. I then toggled the disk editor to a second drive in which I had my Superscript work disk with the customized DEFAULT print driver. Again going to the directory track, I went to the track & sector pointers for the DEFAULT(S) file and used the JUMP fuction to follow the file links, making a parallel list of the links, so that I wound up with something like the following: Orig DEFAULT Custom DEFAULT T S T S 19 0 Start 17 0 19 10 17 6 19 1 17 12 19 11 17 18 -- -- etc. -- -- -- -- etc. -- -- 19 15 17 4 (19) ( 6) 17 10 (19) (16) End 17 16 The original DEFAULT print driver was shorter my customized driver (ending at track 19 sector 15) so the additional tracks & sector in parentheses had to be added. At this point you have a couple of options: You can use the disk editor to make a hard copy printout of every track and sector in the custom DEFAULTS file and then use the editor to alter every byte in the boot disk DEFAULTS file. This is conceptually simple, but painfully tedious. Fortunately, I have a copy of Slaymaker's Peek-A-Byte 128, an editor which allows you to read the contents of a track & sector into a buffer and then write the buffer back to any track and sector on the disk. The procedure then was to go to the start of the custom driver file on the work disk (Track 17 Sector 0) and read the contents to the buffer. Next, the first 2 bytes of the track and sector in the buffer (which point to the next link in the file) had to be edited to point to the appropriate track and sector on the boot disk to which they would be written. E.g. they were changed from the original values of 17 & 6 to 19 & 10. Then the editor is toggled back to drive containing the Superscript boot disk and Track 19 and Sector 0 are selected (start of the EPSON file which is to be overwritten). The WRITE function of Peek-A-Byte was then used to write the buffer contents to Track 19 Sector 0 of the boot disk. This process is repeated for each track and sector of the custom print driver file, always remembering to alter the first 2 bytes of each track & sector to point to the appropriate track and sector on the boot disk. Note: the first 2 byte of the last sector, which signify the end of the file are left unaltered. At this point it would probably be a good idea to go back to the directory track of the boot disk and use the JUMP function to follow the links of your new DEFAULTS file, just to see if you got everything right. That's about all there is to it. Note that you could use a similar procedure to put a modified START.P file on a Superbase boot disk. As with Superscript, any attempt to replace files on the Superbase boot disk with a normal save will corrupt the protection scheme and prevent the program from loading. J.Karn ------------ Category 3, Topic 12 Message 32 Wed Apr 06, 1994 N.PHI [Toto] (Forwarded) Ummm, I bought a new copy of SuperBase 128 3.01 (on 1581 disk) from CMD some months ago. I knew that Superbase once had a copy-protection scheme, but I'd like to know how much of that scheme has made the transition to 3.5" disk... That is, if I wanted to make modifications like the one described just previously, how difficult would it be? ------------ Category 3, Topic 12 Message 33 Thu Apr 07, 1994 F.OGLE [Color BBS] (Forwarded) If you wanted to do what J.KARN just posted, there would be a difference, since the 1581's directory listing is on track 40 (not 18 like the 1541 & 1571). ------------ Category 3, Topic 12 Message 34 Thu Apr 07, 1994 CMD-DOUG (Forwarded) There is no copy-protection on the 3.01 versions, but the program loader still loads individual encryped blocks from the disks... it simply doesn't do it's old error checking for copy protection. ------------ Category 3, Topic 12 Message 35 Mon May 23, 1994 W.OVE (Forwarded) I boot superbase 3.01 from a 1571, but I cann't for the life of me get the program to create a database on the 1581 as device 9. I keep getting a no channel error when I type 'database"mine",9,0. Suggestions would be appreciated. As of yet it seems that 3.01 does nothing that was not done by 2.07. The manuals are identical. Are there any improved features to the program. thank you W. Ove ------------ Category 3, Topic 12 Message 36 Mon May 23, 1994 C128.JBEE (Forwarded) Try database "9:yourfile" ------------ Category 3, Topic 12 Message 37 Tue May 24, 1994 W.OVE (Forwarded) ZI have tried "9:yourfile" it does not work. I get a no chanel error. ------------ Category 3, Topic 12 Message 38 Tue May 24, 1994 CBM-ED [e.g.bell] (Forwarded) How many files do you have open when you get this error... include the error channel in this count. I don't use this software, so if what I'm asking makes no sense, that is the reason. A no channel error is usually caused by having too many channels open for the drive. I believe this is related to the number of buffers available in the disk drive. Thing is, this may have absolutely nothing to do with your syntax or drive specifiers, if you see what I mean. ------------ Category 3, Topic 12 Message 39 Tue May 24, 1994 B.GANN1 (Forwarded) It sounds like there is something wrong with your 1581. I am assuming that you are starting with a blank, formatted disk, and are typing: database"mine",9 and then you immediately get a "no channel" error. The reason I am asking as many people don't realize certain things about Superbase. For example, copying the capitalized database file to the new disk will not work. You must do a full disk copy, not a file copy. If the disk formats are not compatible, you must EXPORT the data and then IMPORT it into the new database. (JBEE: I haven't tried database"9:mine", but I wouldn't think it would work as this is not the purpose of the device designator feature.) What controller chip do you have in your 81? There should be a program online to test it for you. It seems I remember someone having the same problem on Q-Link... after a while, the drive finally went out. Try a different 1581 and see if the same thing happens. Changes in V3.0... this is what my slip says... Devices 8 and 9 supported for the EXPORT, IMPORT, or FIND commands. (When it says 8 and 9, it means 8 and 9. Dual digit device designators are not handled properly.) An example would be EXPORT"9:mydata" You should be using a database on device 8 before giving this command. This command would take the records from device 8 and put them in an EXPORT file on device 9. Since 8 and 9 are now supported, you can now no longer access drive 1 of a dual drive unit. New 128 version of the Utility program. It is the same, but works in 128 mode and does not require the use of the DOS command for the 1571. Expanded system requirements: Because of the extreme amount of reprogramming required for the changes, Superbase requires nearly the full 64k of the bottom memory partition of the 128. 1581 compatibility added. (The above paraphrased, etc from my revisions slip.) Brenda *s ------------ Category 3, Topic 12 Message 40 Wed May 25, 1994 W.OVE (Forwarded) I have no existing datbase on a 1581. I load Superbase. when I type "9:mydata" it will create a database called "9:mydata on drive 8. When I type database"mydata",9 it responds by saying database doesn't exist "create it?" If I say yes it responds with the no chanel error. I have been using this 1581 for many years and have never had any trouble with it at all. I have tried to to write memo files to the 1581 and the light comes on on the 1581, but the file is written to drive 8 the 1571. I first ordered superbase on 1581 format disk, but it won't load on the 1581 as drive 9. I had to flip the switch to make it drive 8, that was inconvient on the 128d and so I exchanged it for the 1571 format. The 1581 format disk however did access databases on the 1571. And it also accessed the training data base on the program disk so I am not sure that anything would be wrong with my 1581. I have used Superbase for many years and it has proved adequit for my needs, but my database and associated programs fill up an entire 1571 and I was looking for the additional space on the 1581. Thank you for your assistsance ------------ 3 | ************ Topic 12 Sat Oct 23, 1993 MRABOY (Forwarded) Sub: Superbase 3.01 KEEP US GOING!!!! 80 message(s) total. ************ ------------ Category 3, Topic 12 Message 41 Wed May 25, 1994 C128.JBEE (Forwarded) My setup, 128, CMD HD, FD-4000 (device #9). I booted Superbase, created the databases on device #9, and then got errors whenever I tried to access it. Solution: database"newdb",9 exit Superbase copy the file format to #9 Reset the C-128 Run Superbase, once the main menu is showing database "newdb",9 file"newfile",9 then import data. ------------ Category 3, Topic 12 Message 42 Thu May 26, 1994 B.GANN1 (Forwarded) He can try that, but it doesn't sound like he is getting as far as #1. Now for what I wrote offline... The reason database"9:mydata" is not working is that it is not a valid command. (Jbee does not know what he is talking about :> ) The reason the light comes on on the 1581 when you try to write a memo file, but it goes to the 1571 is that it is not a valid command. The ONLY valid uses for the drive designator are IMOPORT, FIND, and EXPORT. database"mydata",9 is correct. Like I said, someone on Q-Link had this same problem. After a long time with no results, the drive gave out. That's the only thing I can tell you at this point. Try another 1581. That will rule out whether it is the drive or not. My 1581 has never given me a no channel error. Superbase is VERY finicky... it could be your 1581 is borderline, and works with everything. But Superbase is picking up something the other programs aren't. Word of advice... put device # switches in the 128D and use the 81 as drive 8 :) re: "The 1581 format disk however did access databases on the 1571." I'm not sure I know what you mean. re:And it also accessed the training data base on the program disk so I am not sure that anything would be wrong with my 1581. As long as you are SURE you are using v3.0 or v3.01 you should be fine. Brenda ------------ Category 3, Topic 12 Message 43 Fri May 27, 1994 B.GANN1 (Forwarded) Well, JBEE had to delete my last post due to percieved (c) Q-Link. I'm NOT going to try to paraphase it here, as he suggested. It took me all night to find the posts on old disks. Sorry... I'm not in a very good mood. Brenda ------------ Category 3, Topic 12 Message 44 Fri May 27, 1994 C128.JBEE (Forwarded) Sorry, but 172 lines from Q-link, posted with both their dates and message numbers is clearly violating their copyright and had to be deleted. ------------ Category 3, Topic 12 Message 45 Sun May 29, 1994 W.OVE (Forwarded) Actually I think I may have figured this thing out. Mr. Bell was wondering about the channels open. One of the anomally in my 128d is that I must issue the close command twice to close a file on the 1571. ie "open15,8,15,"command":close15:close15" if I do not close the disk file twice the file is not closed. Perhaps something similar is occurring at the start of superbase, when booted from the 1571. It does not occur with the 1581, because it closes file properly. Would I be correct in assuming that it might be a drive ROM on the 1571? If I were to purchase Jiffy DOS, would it correct that problem if indeed it is a Drive rom problem. thank you W.Ove ------------ Category 3, Topic 12 Message 46 Sun May 29, 1994 CBM-ED [e.g.bell] (Forwarded) Bill: WO> must issue the close command twice to close a file on the 1571. WO> ie "open15,8,15,"command":close15:close15" if I do not close WO> the disk file twice the file is not closed That is kind of weird! But doesn't SuperBase open and close its files transparent to you as user? That is, you don't have to issue the actual open and close do you? I thought it was the 1581 you were having problems with, but if it is the 1571, and your 1571 is doing what you describe, it does sound like a possibility. As I originally said, the no channel error is due to the limit on the number of 'channels' that can be open to a unit at one time. While the computer can have up to 10 files open at once, a single drive cannot handle this number (unless one of the CMD units can). I believe this limit is due to the limited number of ram buffers in the drives. When you get a no channel error, it is usually because there are not enough of these available to the drive to open the specified file. I can't answer your question about JD... maybe no one here can w/o looking at the unit cuz there is more than one ROM in your drives. If there is a problem, maybe it isn't in the ROM that JD replaces. Of course I'm no tech and quickly get lost on hardware stuff. The channel errors, however, I understand a little bit. :) ------------ Category 3, Topic 12 Message 47 Mon May 30, 1994 J.KARN (Forwarded) Couple more observations on use of device 9 with SUPERBASE 3.01. As B.Gann has pointed out, the proper way to access a SB database on device 9 is with the SB command: database"dbname",9. If that doesn't work, then I'm afraid the disk drive is probably dying (or exhibiting some of the 1581 quirks that have been thoroughly discussed on this BBS in the hardware section. You can also access databases on device 9 with run"9:start", if you have put a start.p program on the disk containing a line such as the ffg: 10 database"dbname",9:file"filename". I've also found that you can access a database on device 10 with database"dbname",10; however, commands like run(or load)"10:start" don't work. The run"dn:start" is a SUPERBASE command which is only supported (in vers. 3.0 & up) for devices 8 & 9. I presume the database"dbname",10 works because it "falls through" to CBM DOS. I've found that all of the above work using 1571, 1581, SFD 1001, FD 2000, and CMD HD-85 drives. What I haven't figured out how to do is read the disk directory of device 9 or 10 (under SUPERBASE) if the disk doesn't have a SB database on it. At least not in an elegant way (I haven't tried to fool it by accessing a database on device 9 and then swapping disks). If anyone has figured out how to do this cleanly, I'd appreciate hearing about it. J.Karn ------------ Category 3, Topic 12 Message 48 Mon May 30, 1994 B.GANN1 (Forwarded) Sorry, I shouldn't have said that only FIND, IMPORT, and EXPORT work with device designators... that is what the slip says. JB> Sorry, but 172 lines from Q-link, posted with both their dates and message JB> numbers is clearly violating their copyright and had to be deleted. Sorry. Not going to debate (c) here. The Q-Link info was several years old, and is no longer on Q. In brief, it chronicalled a user with the very same symptoms. About 6 months later (?), his drive finally totally died. Bill... you should not have to be issuing a close command twice. Some commands do not like to be on the same line as the open statement. There is something wrong with your drive. Try another 1581. Ed... you do not need to open and close files yourself on SB. You do issue a "file" command though. J.KARN... What I haven't figured out how to do is read the disk directory of device 9 or 10 (under SUPERBASE) if the disk doesn't have a SB database on it. Nope, sorry. The reason you can't do a "10:file" I explained above. Brenda ------------ Category 3, Topic 12 Message 49 Wed Jun 01, 1994 H.HERMAN1 (Forwarded) >..... One of the anomally in my 128d is that I must issue >the close command twice to close a file on the 1571. ie >"open15,8,15,"command":close15:close15" ... I discovered this very same quirk some time ago. Not sure exactly how I stumbled on it, but since it works, I've been using it ever since. Besides, an unneeded CLOSE doesn't seem to be a fatal BASIC error. Or, maybe I am bunching up too many things on the same line as Brenda says... Howie ------------ Category 3, Topic 12 Message 50 Wed Jun 01, 1994 W.OVE (Forwarded) So if close is needed twice to close a file. Then is Superbase uses similar commands to close down one drive and open another, then isn't it possible that the reason for the no channel error is that there is still an extra channel open on the 1571 and the system has more files open than it can handle. Further playing has shown that I can load programs, memos and help from the 1581; but no database access. ------------ Category 3, Topic 12 Message 51 Wed Jun 01, 1994 CBM-ED [e.g.bell] (Forwarded) Bill: WO> isn't it possible that the reason for the no channel error is WO> that there is still an extra channel open on the 1571 and the WO> system has more files open than it can handle. I can't dispute what you and Howie have found out about a double close being required,tho I can't imagine it being caused by too many commands on one line for this reason. I do something very much faster all the time in ML.... namely closing multiple channels to a drive. And also, remember that in BASIC or any other high level language or applicatioin, the language or application is going to add to the time it takes to perform the operation. But as I have been saying all along, the no channel error is caused when a unit cannot allocate enough buffers in the drive for the operation requested. This is a predictable number based on the type of file being open... I believe relative files are the biggest hogs of buffers... also why your computer can open as many as 10 files, but not on the same unit, unless some of the CMD devices allow that. WO> I can load programs, memos and help from the 1581; but no WO> database access. And if the database access is via relative files, the evidence seems to be :ppiling up that what you and Howie have noted may be the reason you get the no channel errors. Perhaps something is not getting closed. And I believe that a command channel is needed to set relative file pointers tho I could be wrong about that. If that is the case, perhaps you are getting into a situation where something is attempting to open a 2nd command channel. ------------ 3 |