8bitfiles.net/archives

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

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / CMD.MISCMSGS.ARC / 00MISC.CMD.MSGS next >

Wrap

Text File | 2019-04-13 | 33.5 KB | 855 lines

************ Topic 9 Thu Oct 24, 1991 C128.JBEE [* Sysop *] at 04:56 EDT Sub: None of the above A place to post questions and whatever else that pops into your mind that does not fit into any of the other CMD topics already started. 150 message(s) total. ************ ------------ Category 12, Topic 9 Message 1 Thu Oct 31, 1991 C128.JBEE [* Sysop *] at 10:59 EST We had three good rolls of the dice and three lucky winners at the CMD conference the other night T.Adams 18 won 1st place but decided for an extension on his TC128 sub. L.Schonder won (25) 5.25 disks G.Correa won a free TC128 subscription It was a nice informal conference, one of many to come for Flagship$ users. ------------ Category 12, Topic 9 Message 2 Sat Dec 14, 1991 C128.JBEE [* Sysop *] at 00:00 EST FCOPY undocumented feature ... When you boot FCOPY from a partition it keeps the partition as the "target" partition when entering disk commands with the "at sign". True life example ... boot fcopy from partition #25 from HD set source from 1581 with a partition (using S) set target on HD partition #19 You see that you want to "new" partition #19 so you enter the disk commadn from the "at sign" command n:q,ijb It falls through to partition #25 and nukes your partition. Luckily for me I am pretty handy with a sector editor and I didn't loss any of my programs...could be tough on someone else. ------------ Category 12, Topic 9 Message 3 Sat Dec 14, 1991 CMD-DOUG at 23:40 EST Appendix A, page 6, under the heading "Send Disk Command (@)": "Important: disk commands do not follow the source or target path, but are instead sent to the current directory. Therefore, it is wise to make sure you are currently in the correct partition, sub-partition, or subdirectory before sending a command ntended for a certain area." I'd call that documented. It further goes on to state that you can use partition numbers and paths in the disk commands. That will assure you that they will go where intended. Problem is, most folks don't read this stuff until AFTER they have goofed. Only thing I can think of to make it clearer would be to add that "current directory means whatever directory you were in when FCOPY was loaded." So if you are in partition 1, and FCOPY is in partition 24, and you load it with ^24:FCOPY, then the current directory is still in partition 1. ------------ Category 12, Topic 9 Message 4 Sun Dec 15, 1991 HOWIE-CBM [H.HERMAN1] at 13:09 EST Yup! My Manual says the same thing. I gotta agree with Doug on this one. That's as documented a feature as you can document... No two ways about it!! Howie :) ------------ Category 12, Topic 9 Message 5 Sun Dec 15, 1991 C128.JBEE [* Sysop *] at 22:00 EST But, I changed the source/target after running FCOPY and even did directories of the source/destination disks and partitions. After setting the source/destination and then pressing "b" to view the target directory you would think now that I am viewing the target directory through FCOPY that the disk command would go there. I understand about being in the same partition I booted FCOPY from originally. But after setting to different paths and doing directories you would not think that sending a disk command to the B drive would instead go to the A drive and the original partition. Once you set the paths in FCOPY the channel commands should go to the respective drives and along the correct paths shouldn't it? ------------ Category 12, Topic 9 Message 6 Mon Dec 16, 1991 HOWIE-CBM [H.HERMAN1] at 22:25 EST JBEE, I quess one way to look at it is that FCOPY's use of SOURCE and DESTINATION are for _ITS_ use (in copying files) and have no affect on DOS. As you know, you can change and/or re-confirm the currect dir/part by issuing: CP5 and/or CD//telcom (or whatever) _FIRST_, then you'd know for sure any commands are going where intended. However, since this is all getting very technical, I may be missing the point... Howie ------------ Category 12, Topic 9 Message 7 Mon Dec 16, 1991 CMD-DOUG at 22:40 EST As Howie said, the SOURCE and TARGET partition and path info is strictly for FCOPY's own internal use for copying. Since there are two parameters (SOURCE and TARGET), and since FCOPY allows copying from one area of the drive to another, it would be necessary to check and change partitions and subdirectory paths internally each time the Send DOS Command function was activated. Doing so involves quite a bit of extra code, not only to make the moves, but also for possible errors in paths. And it complicates sending commands since now you must change all your path info to send a command to an area of the drive, or include the path info in your commnd string. We felt this would be more confusing than just requiring partition and path info at all times. ------------ Category 12, Topic 9 Message 8 Mon Dec 16, 1991 R.ALBRECHT3 at 23:57 PST Do you see the possibility of a CD ROM drive package available for the 64 or the 128 in the future? I have used these CDROM devices on the PC campatibles and I really like the information that is currently available for the PC'S. Could such a setup (CD ROM) work on the Commodore 8-bit line of computers? ------------ Category 12, Topic 9 Message 9 Sat Dec 28, 1991 C128.JBEE [* Sysop *] at 07:19 EST FORWARDED FROM CAT 12 - TOPIC 18 ------------ Category 12, Topic 18 Message 1 Thu Dec 26, 1991 S.CRAIK [Steve] at 20:50 PST Hi, I thought that this would be a better place inwhich to discuss the problems I've been having. I'd been talking about it in the post RAMLink TRicks & Tips. Since it isn't a TRick or Tip !!! Perhaps those messages & replies could be brought over here? AS I mentioned I found another RAMLinnk User that is having problems with his Expansion Port. (though, at the moment I haven't found out for sure that he has the HONG KONG assembled 128D from what he said it does seem very similar. I've replied to HIM (Pat Wood) ...a NOTE for you CMD just in case you get a call. Anyway, I was finding out many things that seemed to not be working as a 128D or 128 should. For one, if there was nothing in the Expan- sion slot that my 128D wouldn't let the BASIC 7.0 screen to appear That turns out to be that the port's connector's pins (bottom & top) were all touching. I replaced the connector with another. That problem is no more. I do get the BASIC 7.0 screen RAMLink still doesn't work in 128 mode correctly! I've taken my 'puter to a repair shop and it said that the 6526 chips U1 U4 were bad, we replace them but still the test ended BAD! Mind you all this time I'm still able to use my 128D with Aprospan ...a REU (1.5 meg) & a Swiftlink Cart connected to a USRobotic HST 14.4 beside the 1581 and Panasonic KX-P 1080 printer w/ Super G interface.. plus the 1084s monitor So it was suggested that I try it on other machines... Well I have, a flat type 128 that had Jiffy-Dos Kernal Rom (switch out) it worked. Then thinking it still had something to do with the "D" model... I tried it on one at the user group meeting that I attend. It turned out that it worked on that unit ...but I noticed that it was assembled in TAIWAN. Just recently, in the I talked with another person that had a TAIWAN made 128D and asked him what happens when he presses "F1" for the Jiffy-Dos Directory command. the 128. Though, not sure as I thought that they get swapped out, I thought ...for whats in the RAMLink. Anyway, my ROMs in U32 & U34 chips were made in 1986 CBM one has the last few digits xxxx23-02 & the other xxxx22-02. So are these any thing that is in your 128D? A curious thing that I've been hearing about is some sort of "EMI" thing. Not sure if thats the correct nomiclature. Any idea what that relates to? Well the solution still hasn't been found. But should this be happening this is the place to watch for INFO. As I don't want others to go through all the problems that I have. Thanks for listening! and hopefully a CURE will follow in the messages after this. Steve (S.CRAIK) ------------ Category 12, Topic 18 Message 2 Sat Dec 28, 1991 C128.JBEE [* Sysop *] at 07:06 EST I will be moving this topic elsewhere in the Category and deleting the original message. re:bad 6526s I think I explained this before somewhere else but... The teste is a good place to start when tracking down problems but it is not "foolproof" nor is it a replacement for a logic probe and DMM. I have a computer a customer sent me that got hit by lightening and wiped out both 6526s (they tested bad). Now with two good (and tested) 6526s in the C-128D the one at U1 stil shows bad on the tester but good on the board. I have tested almost everything on the mother board and it still shows U1 as bad and the 80 column screen still has glitches with a new wpower supply and a new VDC. Replacing chips is no guarantee the computer will be "right" if there is another logic chip, resistor, or capacitor that is bad. If you have replaced both 6526s because they were bad and they still show bad that means the computer was subjected to a surge that did more than damage the chips. I would also look at testing and replacing the power supply. Since this is a $80 item I suggest making sure it is bad and it is the only thing that will need to be replaced. Otherwise you will end up spending more in parts than a C128D costs used or in some cases new. ------------ ------------ Category 12, Topic 9 Message 10 Sat Dec 28, 1991 HOWIE-CBM at 11:11 EST Steve, I believe that if a SwiftLink is in the pass thru port, that in order for it to work properly, the setting for the NORMAL/DIECT switch is a factor. If you find that you have a prob running with it, you might try switching it to its other position. Howie ------------ Category 12, Topic 9 Message 11 Sun Jan 19, 1992 J.ROBBINS16 [JBUS] at 16:37 EST Hi:), just a little rumor I'd like to get some info on. I'd heard that CMD is no longer providing Gateway with the sale of RamLink or RamDrive, but instead will be providing a GEOS Configure file, for GEOS users. I'd like very much to get a copy of this Configure file, but I still can't seem to find it anyplace. ... Is this Geos Configure file just a rumor, or is there somplace I can get a copy? ------------ Category 12, Topic 9 Message 12 Sun Jan 19, 1992 PAUL-MB at 18:54 CST I heard about that too...and I believe it because I got it from the author of the Configure file! ------------ Category 12, Topic 9 Message 13 Thu Jan 23, 1992 JIM.COLLETTE at 19:20 EST Yep, I did write the Configure for that... I believe it will be available in the CMD library here on GEnie. Hopefully Doug will see this soon and post an official reply... Jim :) ------------ Category 12, Topic 9 Message 14 Fri Jan 24, 1992 J.ROBBINS16 [JBUS] at 00:52 EST Thanks guys, I was hoping this was for real. ------------ Category 12, Topic 9 Message 15 Sat Jan 25, 1992 L.SCHECTER [Shek] at 19:24 EST Perfect print is wunnerful! I would like to see a printer adaptation file and a printer driver for the Hewlett Packard Desk Jet 500 printer in PCL level3, Epson FX-80 and IBM Proprinter III emulations. I'd buy that! ------------ Category 12, Topic 9 Message 16 Sat Jan 25, 1992 C128.JBEE [* Sysop *] at 20:53 EST L.Schecter Since you mentioned the Deskjet 500 I would like to mention that the Pacific Page and Elefont cartridges now sell for $99 and buy using a plain old word processor you can bury font commands in your text. This allows you access to fonts and typefaces ranging from 6pt to 30pt! at 300 DPI! Graphics are another story ... though I have found printing graphics out from Geos and then running the paper through it again to place text around the graphics is a good way to make a master page suitable for photocopying. ------------ Category 12, Topic 9 Message 17 Tue Jan 28, 1992 CMD-DOUG at 05:17 EST Okay folks - the official word about the new GEOS patches for RAMLink and RAMDrive... Orders taken after January 1, 1992 were no longer supplied with a free copy option for gateWay, but when shipped included a new set of CONFIGURE files and utilities to allow using RAMLink and RAMDrive with the standard GEOS deskTop. The reasoning behind this is simple - many GEOS users found gateWay to be difficult to set up and learn, and we concur that gateWay is simply not for everybody. There are also some bugs in gateWay that we had hoped the author would have resolved by now, but we're still waiting for those fixes to materialize. By far, we felt it was better to create a method for those who do prefer the iconic interface of the deskTop to use RAMLink and RAMDrive, and to have an alternative for those who had problems with the bugs due to their particular configurations. For those of you who prefer gateWay's power, we have not given up it by any means - the bugs are still being worked out, and we'll make new versions available as soon as we feel satisfied that they truly resolve the known bugs. As for the new CONFIGURE files and utilities for using standard GEOS, these are now available for download in our private library here, complete with documentation. The method used to make RAMLink and RAMDrive usable under standard GEOS was actually discovered by Paul Bosacki while creating gateWay, and in fact, the basic routines employed came from gateWay itself. Since Paul has been extremely busy with his own business, as well as with working on improving gateWay, we employed the assistance of Jim Collette to implement the actual code required. Thanks to Jim, who has done a fine job by the way. The new CONFIGURE files will allow you to use parts of RAMLink or RAMDrive as a RAM 1541 or RAM 1571, and can also access 1581 partitions. Jim also created a partition switching utility so that access to multiple 1581 partitions is possible. This utility can also be used to copy files between partitions. Finally, Jim created new versions of RBOOT and 128 RBOOT, so that GEOS can be RAM rebooted, EVEN AFTER YOUR COMPUTER HAS BEEN TURNED OFF. In addition to these fine utilities by Jim, I have created a setup program which can automatically configure RAMLink or RAMDrive partitioning for use with GEOS - a feature I felt was really needed to help the less technical users. So, for anyone who wants this new system, it is now available in our private library as a single download 'RL/RD.GEOS.SFX'. If you don't have access to that area, and are a registered owner of RAMLink, RAMDrive, or a CMD HD for that matter, leave mail to me (CMD-DOUG). The patches are also available on disk direct from us for $10.00 fee. ------------ Category 12, Topic 9 Message 18 Tue Jan 28, 1992 A.KARANTZE [The Maverick] at 21:01 EST Doug, Good to hear about that. Ill pass on the info to some other people here who are using gateway and RAMLink... and I hope that you do get gateway sorted out... it does look like it can do the job. At any rate, I believe in CMD's ability. -> Antony karantze ------------ Category 12, Topic 9 Message 19 Thu Jan 30, 1992 D.BURR8 at 01:14 EST Heh, sounds like a reasonable solution to me. However... Silly me never remembered to register my RamLink. It is an EARLY model with the 1.30 RL-DOS Rom. No serial number visible anywhere on the RamLink. Do I need to open the case to find a serial number? If so, where do I find the number. Any advice would be appreciated since I really DO have to get this things registered and get access to the files/updates/etc...Thanks Dan ------------ Category 12, Topic 9 Message 20 Thu Jan 30, 1992 CMD-DOUG at 08:09 EST Early models (revision A) RAMLinks have no serial number - but they did have a registration card. Did you send that in? ------------ Category 12, Topic 9 Message 21 Thu Jan 30, 1992 D.BURR8 at 21:53 EST No, I haven't sent it in, sice it asks you to write down the serial #. Not having a number, I assumed I was just missing something. So I can simply send it the card, and it will be counted as valid? Dan ------------ Category 12, Topic 9 Message 22 Thu Jan 30, 1992 CMD-DOUG at 22:03 EST Yes - just send it in. You're obviously well past warranty, but at least you will be registered, so you can be notified of any updates, etc. ------------ Category 12, Topic 9 Message 23 Fri Feb 28, 1992 JMMCCUTCHEN at 18:42 EST Hello everyone, I was a diehard C64 user from when they first hit the shelves, for the last couple of years i've been using ibm compatibles (there just so cheap to upgrade!). I'm looking at my dusty old C64 and a seagate IDE hardrive....anyone know of a C64-IDE adapter?? Thats reasonably priced?? I kinda miss the old gal..she was so easy! ------------ Category 12, Topic 9 Message 24 Sat Feb 29, 1992 C128.JBEE [* Sysop *] at 00:41 EST I do not know of any IDE adapter. ------------ Category 12, Topic 9 Message 25 Tue Mar 03, 1992 D.MCLAUGHLI8 [Black Fire] at 01:29 EST How does one go about getting access to the CMD Private Library? I've sent mail to CMD-Doug, on a few occasions, but have got no response, and I can <J>oin library 19 yet! Help! Doug ------------ Category 12, Topic 9 Message 26 Tue Mar 03, 1992 HOWIE-CBM at 04:24 EST Doug, Hmmm... Generally you should be granted access in about a week. Include in the GEnie Mail request to Doug, info about the CMD equipment you have registered. I am pretty sure that I did not see your name included with the list of those recently given access to CMD's Library. Howie ------------ Category 12, Topic 9 Message 27 Tue Mar 03, 1992 CMD-DOUG at 20:19 EST It usually takes just a tad longer than a week, as I usually collect the names for a week, then take them in to the office to verify against product registration cards, then submit the approved list to the sysop here, and then they undoubtably have some overhead time in getting your name into the system for access. Your name has been approved and submitted, by the way, so your access should be available soon. ------------ Category 12, Topic 9 Message 28 Sat Mar 07, 1992 D.MCLAUGHLI8 [Black Fire] at 10:09 EST Thanks a lot! And thanks for the reply as well! Doug ------------ Category 12, Topic 9 Message 29 Fri Apr 03, 1992 J.ROBBINS16 [JBUS] at 04:02 EST I have a problem with geoMakeBoot, and before I send it back I'd like to know if it is me or the program.. I've sucessfully made aGeos 128 v2.0 back-up, but the Geos 64 v2.0 doesn't work. All I get is a screen full of colored square boxes and a locked computer Is there something different about the 64 version I should know about, or is it just possibly a bad file? I've tried it with both GEOS 64 v2.0 and GEOS 64 v2.0r (georam) and get the same results. ------------ Category 12, Topic 9 Message 30 Tue Apr 07, 1992 J.ROBBINS16 [JBUS] at 18:56 EDT Well, Thanks CMD...sent me a new complimentary disk in 3 days of my previous message. Now that's service! The new programs both work great. Please give my personal thanks to Mr. Christianson for the disk and his letter. :] ------------ Category 12, Topic 9 Message 31 Thu Apr 09, 1992 PAUL-MB at 11:09 EDT Here's an odd one I discovered last night with my RAMDrive & JiffyDOS. Normally, to start up Wizard, I type FAST <cr> @#11 <cr> @CP3 <cr> and SHIFT RUN/STOP. But I accidentally typoed FAST@ <cr>. Guess what? A reset! JiffyDOS reset on me twice when I did that. Third time it locked. So I tried PRINT@ <cr>. I got an odd number (something on the line of pi) and the drive status! I don't know if this is just an "undocumented bug" but it's there :) ~~~ Paul ~~~ ------------ Category 12, Topic 9 Message 32 Thu Apr 09, 1992 HOWIE-CBM at 19:16 EDT Paul, I suspect, but am not sure so someone else may have to confirm this, that what you saw is more an attribute of a design decision, rather than any bug. If the firmware of JiffyDos is set up to operate along the lines of something like Basic8 or CS/DOS, then JD is first looking for a command it can recognize and execute, and if not, then passes along the command to the Basic interpreter. FAST@ is nonsense to both, so weird things are likely to happen. Under nornal CBM dos, I suspect you'd get some sort of error message. Having JD on top of this may not always let this be the case, leaving the only option of having JD determine if the command is in fact a valid Basic one before passing it along. Adding this extra error checking routine could have been done, I suppose, but at the expense of overhead and extra execute time. If I was designing JD, I'd leave something like this out, since the extra time wouldn't be worth the trade-off of catching something like this. Others may not agree with the way I look at it though. One way to avoid something like this from happening again is to save the following file to your default RD partition and directory, and run *IT* each time you want to run Wizard: 10 fast:@#11:open15,11,15:print#15,"cp3":close15:dload"wizard",u8 If I misread your configuration, just change around device numbers in the above. Then if you decide this is sorta a nice way for things to get started, and you add more programs, and include a series of menus, so one keypress does a GOTO, to start up each, then you pretty much have a menu driven sys similiar to mine! :) Howie ------------ Category 12, Topic 9 Message 33 Thu Apr 09, 1992 PAUL-MB at 19:20 EDT Thanks, Howie :) I think it's about time I ran a program to boot Wizard...only been doing this for about 5 1/2 months or so :) ~~~ Paul ~~~ ------------ Category 12, Topic 9 Message 34 Fri Apr 10, 1992 C128.JBEE [* Sysop *] at 08:30 EDT the <at sign>F is a JiffyDos command ... ------------ Category 12, Topic 9 Message 35 Mon Apr 13, 1992 J.ROBBINS16 [JBUS] at 22:48 EDT I got brave and tried it, ... it just reads the error channel and ignores anything before it in my RamDrive. but the print@ puts it in a tizzy and locks the screen up for any command after it.. if it's placed after the@ sign it will try to print the file in memory to the printer... and crash.... nice try though, Paul must have had something still hanging around in memory to get the results he found... that mixed in with the @ command.. ------------ Category 12, Topic 9 Message 36 Tue Apr 28, 1992 MIKE.DUNCAN [ Mikey ] at 00:10 EDT CMDoug, Does CMD supply technical data for their products? Like service literature (schematics/parts list) for the HD and RL. If something goes wrong with them, I'd like to be able to repair them myself. RAMLink ======= Is upgrade data available for the RL? My RL has Rev.D on it, but I noticed that the paper that came with it said you were up to Rev.G or H. (I'd hafta look) BTW - Is the RAMCard upgradable to the RamCard_II configuration? Hard Drive ========== Could I just `swap' the 20mb drive that came in my HD with a 200mb drive? Which SCSI commands are supported by the HD, and which aren't? Is the HD actually GCR formatted? Have you released (or are you gonna) a ROM routine listing? ================= Just lookin' ahead => Mikey ------------ Category 12, Topic 9 Message 37 Thu Apr 30, 1992 CMD-DOUG at 05:58 EDT There are numerous options for upgrading RAMLink. Hardware upgrades of the units are expensive, so unless you really have a problem I would avoid that issue. Firmware upgrades can be made by purchasing the latest ROM Revision which costs $15.00 plus shipping. RAMCard itself cannot be upgraded to a RAMC ard II, but there is a trade-in policy which gives a $20.00 credit. We also supply other goodies with that type of exchange, such as the latest DOS and utilities or any other parts needed to operate with an RTC option installed (where required). As far as technical info, no, we've never compiled that for distribution, nor is it likely that we will. There have been so many mods and changes that just putting it together would be a monumental task, and there just are not that many who would benefit from that (not to mention the drain it would put on our internal resources which would slow down other projects which are planned or in-process). We also feel that such information SHOULD remain proprietary, as well as ROM code...we worked long and hard to design and debug these things, and it would be a shame to just give it away and make it easier for someone else to copy. There may be at some time in the future a release of certain information, such as the jump tables which are not supposed to change, and maybe some other location information if we can determine that it has remained stable over all revision levels (takes a heap of checking just to verify this). As for SCSI commands on the HD, the Send SCSI command (S-C) doesn't check what you send, so anything that the drive mechanism can accept will work. The routine just passes the command on to the SCSI device. As far as changing the drive mechanism, most any can be used, but we won't guarantee compatbility with anything other than those which we have tested ourselves. Best to ask about specific models when you are ready to make such a change. Also, watch the power consumption on the 12 VDC...max surge current should not exceed 2.5 A at 12 VDC. ------------ Category 12, Topic 9 Message 38 Fri May 08, 1992 MIKE.DUNCAN [ Mikey ] at 23:51 EDT CMDOUG, Thanks for the quick reply. >> ...so unless you really have a problem I would avoid that issue. Haven't noticed any problems with my RL so far. Sure hope I never do. But what I was hoping to get, was a detailed listing of what actual problems have been found, and what the specific fixes were. I guess I should have asked if I could find out what's the difference between the rev D that I have, and the latest rev. And if there was a parts list, guide, or something that I could use to make the mods. >> ...such information SHOULD remain proprietary... Only wanted to be able call some routines. That's all. Didn't want to be reinventing the wheel. I've got books for the 1541 & 1571 with the same type of information. Sorry, I didn't know it was that big of a deal. Now I know. Thanks Again - Keep those great CMD products comin'! ** ** *** *** **** ** ** ***** ** ** ** ******* ** ** ** ** **** ** ** ** * ** ** **** **** ** ** ** ** ** ** ** ** ** ** ** ** ** **** ** ** ***** ** ** ------------ Category 12, Topic 9 Message 39 Sat May 09, 1992 CMD-DOUG at 11:36 EDT That may be a hard list to come by...while I have much of the info, Mark has never given me any official documentation of the changes from Rev I to Rev 2A, or the changes in the RL-DOS from around 1.6 to 2.0. While I know he has such info, he has just never typed it up for entry into our own information library at CMD. I haven't pressed him to do so, as he has been overly busy with new projects, as have we all. Will mention it to him though, and once I have it I'll upload it. I avoid going straight from his notes, as they usually require interpretation :) ------------ Category 12, Topic 9 Message 40 Wed Aug 05, 1992 C128.JBEE [* Sysop *] at 22:26 EDT I have a programming problem and need an answer. How many relative files can you have open at one time on either a CMD HD or a Ramlink? I know you can't have more than one open on a 1581 (at least it doesn't work for me). I know I read about file limits somewhere and how to calculate them but I can't find a thing in the HD manual. ------------ Category 12, Topic 9 Message 41 Wed Aug 05, 1992 CBM-ED [e.g.bell] at 22:55 EDT The limits on the floppy drives have to do with the internal buffers that each filetype allocates within the drive. How many buffers do the HD/ RAMLinks have for internal DOS management? ------------ Category 12, Topic 9 Message 42 Fri Aug 07, 1992 CMD-DOUG at 00:01 EDT The number of job buffers available on CMD devices is dependent upon the partition type being used. When using emulation partitions, these devices have the same number of buffers as the drive type being emulated. That is 5 for 1541 and 1571, and 9 for 1581 (one of these is reserved for DOS). RAMLink and RAMDrive max out at 9, so this is the limit for CMD Native partitions on those devices. The HD, however, has 32 buffers available when using CMD Native partition types, which means you can have up to the full 10 files (of any type) allowed by the file table in the computer open at once. ------------ Category 12, Topic 9 Message 43 Fri Aug 07, 1992 C128.JBEE [* Sysop *] at 16:02 EDT The reason I am asking all this is I am converting my database program to run on the Ramlink and HD but I also want to make available the option to run it from a 1581 just in case someone's RL or HD goes down and they need to access data files from their backup disks. So running from a 1581 or a 1581 emulation partition I should be able to have open (2) relative files and (1) sequential file at the same time? Without corrupting data that is? ------------ Category 12, Topic 9 Message 44 Fri Aug 07, 1992 CBM-ED [e.g.bell] at 18:54 EDT Seems to me that a REL file takes up 3 internal data buffers and a SEQ takes 1, *if* memory serves. I don't think the 1581 has 7 internal buffers, does it. Of course, you don't have to keep the REL files open all the time to you. Actually, I jus checked the 1581 manual.... You can only open 1 REL file and 1 SEQ file and the command channel at a time. BTW, to find that info, I looked under error 70 in the back of the manual, which is the 'No Channel...' error. ;-( ------------ Category 12, Topic 9 Message 45 Sat Aug 08, 1992 C128.JBEE [* Sysop *] at 02:53 EDT Thank you Ed :) I just couldn't track down that the piece of information even though I read it somewhere. Shoot! I thought after 7:00 tonight ;) I could have two relative (3 buffers each) and 1 seq. file open (1 buffer) at the same time. I guess not! I am going to try the (2) relative files and (1) on the Ramlink and HD and see what happens. I have been assured it should work :) Though the 1581 emulations probably will not work. ------------ Category 12, Topic 9 Message 46 Sat Oct 24, 1992 R.KNOP1 [Rob Knop] at 14:43 EDT The drives are black so that reviewers have _something_ to criticize in them! :) (Besides the fact that the reviewer wanted one four years ago.) Naah, I prefer JBEE's answer. -Rob ------------ Category 12, Topic 9 Message 47 Sat Oct 24, 1992 PAUL-MB at 20:14 EDT And now's the time for people to spraypaint their computers jet black :) - Paul :) ------------ Category 12, Topic 9 Message 48 Sun Oct 25, 1992 J.ROBBINS16 [JBUS] at 05:32 EST JBEE already tried that once on a 128D... ;D ------------ Category 12, Topic 9 Message 49 Sun Oct 25, 1992 CMD-DOUG at 22:28 EST Actually, the drives are black because we don't have to worry about color clashing when we get drives with various bezel colors in. :) ...see there really was a reason behind it... ------------ Category 12, Topic 9 Message 50 Sun Oct 25, 1992 C128.JBEE [* Sysop *] at 23:29 EST J.R, yea I am getting a FD drive just so I have something that matches it -lol ------------ Category 12, Topic 9 Message 51 Mon Dec 28, 1992 C128.JBEE at 01:10 EST Here is a FCOPY suggestion: Have an option "n" that will let you rename files if a duplicate exists on the target disk or another option "c" that will append a "+" to the filename automatically and then copy the file. The "c" option would be handy when backing up a lot of files to a 4meg floppy, so you don't have to babysit the program. ------------ Category 12, Topic 9 Message 52 Thu Dec 31, 1992 F.OGLE [Color 64 BBS] at 04:12 EST Good idea - The SSv5 cartridge appends a character in front of duplicate filenames. Nice'n'easy for mass scratching of them. :) ------------ Category 12, Topic 9 Message 53 Thu Dec 31, 1992 GULLIBLE [Jon] at 15:01 EST SSv5 appends a CTRL-A to then end of duplicate filenames. You can still do a mass scratch with a 1581. ------------ Category 12, Topic 9 Message 54 Sun Feb 14, 1993 CMD-DOUG at 21:18 EST MCOPY Bug Report: This applies only to MCOPY versions 2.14 and 2.16. These versions appeared on FD UTILITIES and from 2/2/93 through 2/12/93 on HD/RL/RD UTILITIES. Conditions: Copying from HD 1571 partition to RL or RD 1571 partition. Description: RAMLink or RAMDrive 1571 partition becomes corrupted. Fix: None available as yet. New version of MCOPY with fix should be uploaded to the CMD Private Library sometime this week. I'll be sure to post a message when it is there. ~