8bitfiles.net/archives

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

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / RTCMMSGS.SFX / 01rtcmaster < prev next >

Wrap

Text File | 1990-02-12 | 33.5 KB | 742 lines

Files 12603 and 12604.. have fun! ------------ Category 8, Topic 23 Message 47 Sat Jun 19, 1993 E.RAFANAN at 15:54 EDT I don't know if this was covered already, but... What's the difference between versions 2.01 and 2.02? Are the overlays compatible? Which of the (many) support files in the library are for 2.02? And finally, how come version 2.01 is the "free" version instead of 2.02? Thanks! ------------ Category 8, Topic 23 Message 48 Sat Jun 19, 1993 YLR.ROSE at 18:24 EDT ER.. 2.01 is the freebie this week, because 2.02 still has some minor bugs in it.. my error, I released it too soon. 2.01 works great as it is, use the companion file 11958 as mentioned in the description to use with it (has additional overlays). The Free File of the Week will be no more after 1 July, so we wanted to give you a couple of GREAT programs to grab.. then after the rate change.. downloading will be more economical than anywhere else. (G) Hugs ------------ Category 8, Topic 23 Message 49 Sat Jun 19, 1993 CBM-ED [e.g.bell] at 20:12 EDT ER: ER> What's the difference between versions 2.01 and 2.02? Are ER> the overlays compatible? Which of the (many) support files ER> in the library are for 2.02? And finally, how come version ER> 2.01 is the "free" version instead of 2.02? First, overlays from one version will never work on a different version. The reason is that these are all assembled each time and make calls on routines in the main program. I had to make a decision... I could not cram everything I envisioned in the limited RAM of the C128, so overlays were the way to go. There are simply too many things called to just use jump tables, which to me are a waste of memory, particularly when I like to make such extensive use of the routines in the main progam.. So when you upgrade versions, you are 'in for a penny, in for a pound.' As for the differences between the versions... First, there was a bug in version 2.01 affecting display only.... when you did a hotkey load of an overlay, the color for the current screen changed to white. It affected only the current screen, not all subsequent colors, but some found it annoying... that was fixed... New to 2.02 is a whole new hot menu for loading overlays which you can edit etc... makes loading any overlay basically a 2 key operation, for up to 20 overlays. I added the ability for function keys to call other function keys, including themselves, to a limit of 16 keys. Also made it possible to call control codes from function keys. I improved some of the buffer mark and scroll routines to work even better. I added the ability for you to set your screen color, user, main, system (status line), and menu (main window) messages. Mark and I have enhanced the autolog overlay and his script maker program to make it possible for us to store passwords in the dflt. file (and user id's too) so that we can soon upload tested, functioning scripts for you all.... in addition to creating your own. I added another drive setting, which means you can now set up a 'system' device from which your overlays, fkeys, and strings will always be loaded. It can be the same as your source/target, or completely different, thus up to 3 drives used by RTCM. I included the ability to set partition paths for better device support for CMD devices and the 1581. I hope to enhance this even more in the future. I introduced a new overlay, a file copier, that is not complete as I intend, but complete enough to use. It was mainly written to move files from REU to floppy, but it works with any unit. I also wrote a special boot program which will be the normal boot starting with version 2.03, that allows you to set some defaults so that you would be able to have your boot set the RTCM clock from your RamLink if you have a clock installed, answer the REU setup questions automatically, and load and execute an auto-logon script if you choose to do that. Logging on to GEnie can be as simple as typing: run "ez.boot" I changed some of the cmdr-f key definitions.... cmdr-f5 now gets you a system device directory and cmdr-f7 now toggles the floating device between all 3 devices. There were enhancements and changes made to all of the existing overlays also..... overall, 2.02 is the most radically changed version in quite awhile. The changes have come about mainly because of constant testing, staff brainstorming and testing, and users making suggestions or requests in the conferences. Rose is essentially correct about the reason it is not the free-download. It may be in the future. I can't say, cuz that is Rose's turf... hehe But whether it is or not, I can tell you for sure it will be continually upgraded as long as there is interest. I am working on a full-screen editor now, which will probably precipitate the release of 2.03, because there have been a few changes already in the main program that will not be made live until the next version. ------------ Category 8, Topic 23 Message 50 Thu Jul 01, 1993 CBM-ED [e.g.bell] at 20:27 EDT I have just uploaded 2.02 of RTCMaster, with all of the new overlays. There is a LOT different about this version from previous versions, and it has been in use for awhile and some bugs have cropped up. Most have been repaired. If you got one of the earlier versions of this version these files, except for the main program, are different. They are repaired and in some cases updated. There are several new features, particularly with the AutoLog and script functions. There is also a new boot program that automates much of the manual stuff during boot up. The documentation is also available to be released as soon as possible. Read it! ;) Bugs I know about right now that will wait until next version: The hot load of the overlays using the ALT key does not go to the system device, but to the source device. The copier overlay will NOT copy files into the REU. And this one, which no one has caught yet... the screen color settings do not get installed when you load a new 'dflt.' file. Anything else, please let me know. There are so many changes in this version, it is almost inevitable that things were missed. Thanks to those who have already reported the problems that have been repaired. Hope you enjoy this! ------------ Category 8, Topic 23 Message 51 Fri Jul 02, 1993 HOWIE-CBM at 06:22 EDT Ed, THANKS!! :) Howie ------------ Category 8, Topic 23 Message 52 Fri Jul 02, 1993 YLR.ROSE at 11:28 EDT RTCMaster 2.02 is now available for download... Files 12792 and 12783 are the ones that you need for supercomputing on Genie and elsewhere. Docs will be available later today. Hugs ------------ Category 8, Topic 23 Message 53 Fri Jul 02, 1993 YLR.ROSE at 11:29 EDT nearly forgot, file # 12793 is also available for you now, Mark's newest and greatest SCRIPTMAKER for version 2.02 of RTCMaster. :> ------------ Category 8, Topic 23 Message 54 Fri Jul 02, 1993 CBM-MARK at 21:52 EDT Ah-ha! Thanks Rose, that was a fast release! ;) A few words about Script Maker 2.0; First off I don't have the docs ready :( The sample script that comes with Script Maker 2.0 will log you on GEnie, buffer and save to disk any email, buffer and save to disk any new Commodore RT BB messages, buffer and save new Commodore RT Library files (#11 on the Library menu), and finally place you at the Commodore RTC, asking you to enter a room numer. Two things will have to be defined before you use this sample script. Run the DEFAULTS overlay in RTCM and enter your GEnie userid;password in USERID of the DEFAULT overlay. Also run Script Maker 2.0 and enter your GEnie phone number. If you don't want to further edit the script, press F1 to go to the Re-do/Save/List/Quit menu. Pressing the HELP key will toggle a small help screen listing all the autolog directives that can be entered in the RESPONSE strings. Both F1 and HELP are only active when there is a flashing cursor on screen. Have any questions or problems with Script Maker 2.0, just ask ;) Mark ------------ Category 8, Topic 23 Message 55 Fri Jul 02, 1993 CBM-MARK at 22:51 EDT Sorry everyone, had to remove Script Maker 2.0 from the library. A display bug slipped by me that messes with a script entry. Irritates me, so I'm sure it will irritate everyone else ;D A couple of other small bugs will be fixed too. Should have it back up for you all by Sunday. Sorry :( Mark ------------ Category 8, Topic 23 Message 56 Sat Jul 03, 1993 C128.JBEE at 02:34 EDT This newest version with the script maker is awesome :) ------------ Category 8, Topic 23 Message 57 Mon Jul 05, 1993 HOWIE-CBM at 23:54 EDT Could someone post a listing of all the files that I need for the latest RTCMaster? Thank you! Howie ------------ Category 8, Topic 23 Message 58 Tue Jul 06, 1993 CBM-MARK at 00:31 EDT Thank you JBEE! ;D Too bad that display problem forced me to take it down :( Will be uploading a fixed version in a few minutes ;) Mark ------------ Category 8, Topic 23 Message 59 Tue Jul 06, 1993 YLR.ROSE at 01:12 EDT Howie.. hoping that the LNM doesnt eat me alive.. I have had MONSTROUS problems lately :< with the exception of Marks RTCScriptmaker.. here they are.. : 12792,12783,12778,12779,12780 ------------ Category 8, Topic 23 Message 60 Sun Aug 15, 1993 R.KIRK7 [Dick] at 17:46 EDT I am just trying out RTCM 2.02 and am having a little trouble getting it to work. First of all- The last couple of paragraphs of the GET ME STARTED docs have to do with intering ones phone number etc. to modify the Autolog overlay. Everthing works as instructed until I go to save the changes. The docs state that the 'dflt.mysetup' file will be saved. I get a scr. prompt when I try to save. Just how do I modify and save the dflt.mysetup file? Also, do all the commands work as the docs indicate? Several don't for me. ------------ Category 8, Topic 23 Message 61 Sun Aug 15, 1993 YLR.ROSE at 18:12 EDT Dick.. when you make changes to the DFLT.MYSETUP file using the Default Overlay, you first have to SCRATCH the original file, then resave it as the same name. DO NOT leave RTCM before you resave this file! To save it, hit the help key, cursor over to LOAD/SAVE, down to PROFILE, then save the new format with MYSETUP (rtcm adds the prepend for you). Then your new changes will be saved. A fast way to load the default overlay is to hit the ALT key, then the letter which corresponds to the overlay that you want. Which commands dont work? Please be more specific.. it might only be that you are misreading the intention of the command. :> Hugs ------------ Category 8, Topic 23 Message 62 Sun Aug 15, 1993 CBM-ED [e.g.bell] at 18:22 EDT Dick: RK> First of all- The last couple of paragraphs of the GET ME RK> STARTED docs have to do with intering ones phone number etc. RK> to modify the Autolog overlay. Everthing works as instructed RK> until I go to save the changes. The docs state that the RK> 'dflt.mysetup' file will be saved. I get a scr. prompt when I RK> try to save. RK> Just how do I modify and save the dflt.mysetup file? Use the 'ovrl.defaults' file RK. It is included in the main package. To load it, press CMDR-O, then when you are prompted for the 'ovrl.' file, type in the word 'defaults'. If you have done things right, there will be a directory of 'ovrl.' files on the screen, one of which will be 'defaults'. When t this is loaded, press CTRL-M, and when asked, enter 'd' for the slot number. You will be at a pull-down menu from which you can make the edits you want. When you have made the edits, press ESCape at the pull-down menu, and it will ask if you want to install the changes. Enter 'y', and you'll be back at the main RTCM screen. From there, press CMDR-W, and select '3' at the next menu. Enter 's' to save when asked. You will see a directory of 'dflt' files on the disk. Select a name that is not used and type that in and press RETURN. If you want to use 'dflt.mysetup' you will either have to delete that file before you save the new one (I don't generally believe in assuming someone wants to use save w/replace) or do some name changes after you are done. To create/edit scripts you will need Mark Dulski's Script Maker 2.0 program. When you get ready to do that, you will love his program. It makes things very easy. RK> Also, do all the commands work as the docs indicate? Several RK> don't for me. It would have helped if you mentioned which ones you were having trouble with. It is always possible that something is not working as it should, or that the instructions were not as clear as they could be. Let me know where else I can be of assistance! egb ;) ------------ Category 8, Topic 23 Message 63 Sun Aug 15, 1993 C128.JBEE at 18:32 EDT I would suggest renaming the old file (C= Y for disk commands) r:dflt.mysetupold=dflt.mysetup so you always have a copy of the original default file on disk in case you need it if you totally bungle something, like screen colors. That way you can always reset the computer, rename the dflt files, and try again. I have set my default colors for text and screen to white before and this sure beat unSFX the files again. ------------ Category 8, Topic 23 Message 64 Sun Aug 22, 1993 CBM-ED [e.g.bell] at 09:34 EDT Rose: Here is what I've found wrt using RTCMaster with the RamLink and the REU in the back port. I have my switches set to enable/direct. The EZ.BOOT program was set io%=asc("r") (yes this installs RamDos), and when you run this configuration, the REU will be partition 1 (at least it was in my set up), the device number you set in the SYS command as usual, and the RamLInk will be device 16, or whatever you have it configured for, and seen as partition 2. This says to me that the REU will be blown off each time you boot, which works for what you do with it. I'll play a little more with it. I believe I had different results with it in enable/normal also. I'll let you know, but with this setup I know it works. If I understood it better perhaps I'd try something different. ------------ Category 8, Topic 23 Message 65 Sun Aug 22, 1993 CBM-ED [e.g.bell] at 09:54 EDT Rose: I have another report, and this is going to be my recommendation to anyone using RamLink and an REU. It seems to let RamLink do things the way I read in the manual... here it is. My switches are set for enable/normal. EZ.BOOT has io%=., which means it won't set up for answers to the RamDos/DMA question. However, this never even comes up with the switches set up like this. When you do this, the REU is seen as partition 1, at least on my setup cuz it was totally from scratch that I did this, and the RamLink is seen as partition 2. Both are accessed as drive 16, tho if you changed that in your config, it b will reflect that I guess. I had to format the REU partition with a long format [ n0:partition 1,p1 ] to be able to use it. I then used Cmdr-Q to set the target path to cp1 and the source path to cp2. You would use whatever partition numbers you wanted. The net effect... my source drive fkey shows the directory of RamLink and my target drive fkey shows the directory of the REU partition. This is the absolute best I can do for you, and you will have to configure as I just described. I'd have to play with it to tell you more, but I used EZ.BOOT, set as above, and everything loaded and dialed, etc. perfectly. Give it a try to see if you don't have the same results. Doug: Does this seem ok to you too? The EZ.BOOT program is just a little hack that uses the dynamic keyboard technique to answer the RamDos/DMA prompts if an REU is detected. However with the switches in enable/normal RTCM does not detect the REU and just accepts it as another partition. I can't imagine this being wrong because it matches exactly what I have read in the RL manual on what is supposed to happen with the REU. ------------ Category 8, Topic 23 Message 66 Sun Aug 22, 1993 YLR.ROSE at 10:22 EDT ok, Ed.. thats pretty much the way I had been using rtcm and the rl, in enable/normal, but everyone kept saying that was wrong, that I should be using enable/direct, and stop using ramdos, etc.. you see how frustrating that can be when I have no idea what folks are talking about.. ie: stop using ramdos.. I have rtcm setup now where it runs in enable/direct, and when autosave is on, it saves the buffer files to part#3, which is where I have rtcm, so I guess its working okay. Its just very intermittent with the dump to basic routine. Cam and I have found that if you run the program 'offline' and try to dump to basic, it dumps to monitor instead.. BUT, if you have been ONLINE for a while (like working in the rtc's), then it WILL dump to basic 9 times out of 10. Now, aint that strange. (G) Hugs Darlin ------------ Category 8, Topic 23 Message 67 Sun Aug 22, 1993 CBM-ED [e.g.bell] at 13:16 EDT Rose: YR> ok, Ed.. thats pretty much the way I had been using rtcm and YR> the rl, in enable/normal, but everyone kept saying that was YR> wrong, that I should be using enable/direct, and stop using YR> ramdos You shouldn't need RamDos at all using it the way I mentioned. If you set up the switches in enable/normal, RTCM never even 'sees' the REU and thus never presents the option of using RamDos. And don't worry about what everyone else says. That doesn't always make it right. I'll wait for verification on this, but I gave you the option to do it both ways, with direct and normal. With direct you need RamDos and with Normal you don't. I can't speak for what Dialogue uses or CS-DOS... or I can I guess. CS-DOS probably uses direct because Chris handled REU access with his own code. I only do that with DMA, which I don't recommend people use w/RTCM anyway. YR> Cam and I have found that if you run the program 'offline' and YR> try to dump to basic, it dumps to monitor instead.. BUT, if YR> you have been ONLINE for a while (like working in the rtc's), YR> then it WILL dump to basic 9 times out of 10 I think we may have found the problem and I'm going to try to patch the main program and upload it for you. I also expect to have another copy of SWIFT.OBJ for SwiftLink users soon, based also on what Doug has pointed up. Something occurred to me during the discussion that has almost surely caused most of the problems Mark has had, tho lord knows why it was only him and not me or JBEE? It *is* strange! I'll try to have all of this stuff up by Thursday evening at the latest. The main program patch will be the tricky one ------------ Category 8, Topic 23 Message 68 Sun Aug 22, 1993 R.KNOP1 [Rob Knop] at 16:48 EDT Rose, it's very simple really, and you can understand using an REU in a RAMLink with three simple rules. (1) The first partition you create in your RAMLink should have the same number of kilobytes as your REU has. (2) If you work with the switch in "NORMAL" mode, the REU acts exactly as if it were more SIMMs inside your RAMLink. The computer does not thing it has an REU installed. Feel free to use the first partition for whatever. (3) If you work with the switch in "DIRECT" mode, regardless of the setting of the enable/disable switch, the REU acts just like an REU. Also, you should avoid the first RAMLink partition created. There is nothing software specific about most any of these; all the business of trying to figure out what switch settings you need to use for different software can be determined by looking at (2) and (3) above and asking yourself if you want a 17xx REU with a given piece of software. Most people have figured out, however, that it's just as easy to pick one setting and stick with it. Either set your switch to DIRECT and leave it that way, giving yourself an REU; or, set your switch to NORMAL, and so far as the computer is concerned, you don't have an REU, and can make free use of the first RAMLink partition created. -Rob ------------ Category 8, Topic 23 Message 69 Sun Aug 22, 1993 YLR.ROSE at 20:09 EDT ok, explain this then.. if the reu in direct mode acts like an reu.. then HOW do I access it?????????????????????????? That seems to be the big convaluted thang here that you are trying to confuse me with! From everything I have read and been told, the REU =takes= the first partition of the ramlink.. just HOW do I access the reu without using the first partition?? that makes no logical sense, Rob. duhhhhh :> ------------ Category 8, Topic 23 Message 70 Sun Aug 22, 1993 A.TOLLE [Color64-Tony] at 22:51 EDT Rose, the way I understand it is that if you have a RamLink *and* an REU, then you must choose one option and then stick with it. You can choose to use the REU as part of the RamLink's RAM, or you can choose to use the REU all by itself. It would be impractical and difficult to attempt to force the RamLink to switch between these two methods. If you decide that you will never have to use the REU for anything except extra RamLink memory, then you should plug the REU in and while it is in the RamLink, configure all of the RamLink's partitions. After this, you should never unlpug the REU for any reason if you are going to use the RamLink. On the other hand, if you plan to use the REU with CS-DOS or RamDos, then you must *not* use the REU as part of the RamLink. In this case, you must configure all of your RamLink partitions *without* the REU plugged in, and never try to use the REU as memory on the RamLink. You *can*, however, use the REU *as* an REU while the RamLink is active. When you use the REU as extra memory on the RamLink, the REU is totally *transparent* to the computer. The computer could care less if the RamLink had all its own memory on SIMMs or if the RamLink was using the REU as memory, and the computer *can't* tell the difference in this case. The flipside to this is that if you use the REU as a seperate device, then the computer will see two totally different things, the RamLink and the REU. The RamLink will *not* try to use the REU, and he computer cannot force the RamLink to do so. The answer to your question is that the computer CAN'T access the REU when it is set up as a partition on the RamLink. You can use the REU one way or the other, but it is very difficult to have it both ways. ------------ Category 8, Topic 23 Message 71 Mon Aug 23, 1993 CMD-DOUG at 01:20 EDT Ed had a proper setup, and his messag is valid. Rob's message was also valid, though both leave a lot of gaping holes in how things work (expected, as Ed was trying to explain the use of one certain program, and Rob took the approach that generally setting aside the entire REU means you don't get into unexpected trouble). But in case you didn't see it, I left a dissertation of sorts back in Category 2 about RAMLink, REU's, programs and configuring it all. If you read and understand that synopsis, you'll have a lot better idea as to why what works when. :) ------------ Category 8, Topic 23 Message 72 Mon Aug 23, 1993 CBM-ED [e.g.bell] at 01:26 EDT Thanks Doug! That helps. I am going to have to go thru and digest all of this stuff. Every time I think I understand it I start to think about it and then I REAllY get confused! ------------ Category 8, Topic 23 Message 73 Mon Aug 23, 1993 R.KNOP1 [Rob Knop] at 02:54 EDT >ok, explain this then.. if the reu in direct mode acts like an eu.. >then HOW do I access it?????????????????????????? You access it... just like an REU. Any program that would use the REU plugged directly into the 128 will use it in EXACTLY the same manner when you have the RAMLink in DIRECT mode. >From everything I have read and been told, the REU =takes= the first >partitio of the ramlink.. just HOW do I access the reu without using >the first partition?? that makes no logical sense, Rob. duhhhhh :> This is hopefully alread a dead horse, but I'm gonna flog a little further here. Well, yes, when you access the REU, you are using the first partition. Now, I hate to say that, because I realize that it is only going to confue you. So, here is a better way to think about it: When you have the RAMLink in DIRECT mode, you can access the REU as an REU, but doing so will _corrupt_ the first partition of your RAMLink. Actually, to be more precise, you will corrupt any partition on the RAMLink which overlaps the memory in the REU which is used. But in the simple case where the first partition you create is the size of the REU, the previous paragraph is accurate. This is why I (and presumably some others) have set aside as the first partition created a partition the size of the REU, which I don't use to store valuable or permanent data- because that partition is always getting corrupted when I use my REU as an REU in Dialogue128, ZED, CSDOS, or whatever. (Also, for GEOS reasons, that first partition is a DACC partition.) Anthony: that business about configuring your RAMLink without the REU plugged in: when you do plug the REU in, which port do you plug it into? If you are plugging it into the "Pass-Thru Port," then perhaps things are OK, but I believe it is very unwise to plug and unplug an REU to and from the RAM port while the RAMLink has power. Unless you have a full 16 Meg of SIMMs and need to use every meg of that, it is a lot safer to configure your RAMLink with the REU in, configuring your first partition as a DACC the size of the REU, and to leave the switch in DIRECT mode. This is safer, and functionally equivalent to what it seems to me you are suggesting. >The answer to your question is that the computer CAN'T access the REU when >it is set up as a partition on the RamLink. You can use the REU one way or >the other, but it is very difficult to have it both ways. This statement, however, is incorrect. You can access the REu when it is set up as a partition on the RAMLink- that is what the DIRECT switch is for. It is just that doing so will corrupt the RAMLink partition stored in the REU, as I mentioned to Rose above. -Rob ------------ Category 8, Topic 23 Message 74 Mon Aug 23, 1993 YLR.ROSE at 08:50 EDT whew.. what a debate.. (G). Ok.. I have my first part# as a NATV 4096, which is the size of my REU, its in the RAMport, and everything is now working in enable/direct. The first partition is working just like I want it to.. I WANT it to be nuked each time, cause that is the area I use for downloading lib files, then I transfer them to hard disks, and then I zap em outa there. I dont want to have to scratch files all the time.. sometimes we are talking about 50 or more files, and if I had to download them to other partitions, it would take quite a while to do.. this way, I can nuke em real quick, and all is well with the world. I know it probably sounds weird to ya'll..but its working for me, so am not gonna fix what aint broke no more. (G).. Hugs, and thanks for all the advice. It does make a little more sense now. Just saying not to use RAMDOS is what had me all confused. :> ------------ Category 8, Topic 23 Message 75 Mon Aug 23, 1993 CMD-DOUG at 23:56 EDT My only question to Rose is, do you use that first partition in a normal manner outside of RTCM and CS-DOS? If you don't, I have two suggestions: Recreate you setup and make that area a DACC, and set its partition number to something other than 1 (or change your default partition from 1 to the partition most often used normally). You may want to perform this latter step even if you don't set up the DACC area, since this will keep you from landing in the corrupt area every time you turn on your RAMLink. And just one comment: Wiping out all the files in a partition isn't much harder than doing it in an REU - just takes a short DOS NEW: @"Nn",dv where: n = partition number dv = device number of RAMLink Have a nice day! :) ------------ Category 8, Topic 23 Message 76 Tue Aug 24, 1993 A.TOLLE [Color64-Tony] at 01:09 EDT Sorry about the mistake... You can find another apology in the aforementioned Topic... :) I didn't intend to cause more confusion :/ ------------ Category 8, Topic 23 Message 77 Tue Aug 24, 1993 R.KNOP1 [Rob Knop] at 02:36 EDT >and everything is now working in enable/direct. >I WANT it [The first partition] to be nuked each time, cause that is the >area I use for downloading lib files, then I transfer them to hard disks, >and then I zap em outa there. I dont want to have to scratch files Uh, Rose, I hate to say it, but.... if you are downloading to the first partition in the RAMLink, and you have an REU, you ought to be working in ENABLE/NORMAL. You will see this is what my "3 rules" I posted earlier would suggest. Unless you are using RAMDOS, in which case ENABLE/DIRECT is what you want. Were I to use the words you use, I would mean that I was NOT using RAMDOS, but I am not quite sure what you mean.... -Rob ------------ Category 8, Topic 23 Message 78 Tue Aug 24, 1993 YLR.ROSE at 09:33 EDT Doug.. I have the rl defaulting to partition 2, where I have Dialogue.. I had my rl in enable/normal, Rob, but then had to flip to enable/direct to use Geos and CSdos and TWS128.. so now I have rtcm and Dialogue working just fine in enable/direct, and everything is hunky dory for me. And the partition 1 (native) usually doesnt give me a problem until I go from one program to another, then its a simple matter of reNewing it real quick and I'm flying along again. If I go from non-term pgms back to Dialogue.. its all still there, and I nuke it anyway. (ie: when I d/l prgms from library, and then test them, then get back to Dialogue to get back on GEnie, etc). Ed, it aint broke no mo'e.. LOL. Hugs ------------ Category 8, Topic 23 Message 79 Tue Aug 24, 1993 CBM-ED [e.g.bell] at 18:02 EDT YR> Ed, it aint broke no mo'e.. LOL. Rose, if you are happy, so am I. If it works for you that is all that really counts, and if it goofs up, you can accept responsibility, so like I said, I'm happy! ------------ Category 8, Topic 23 Message 80 Wed Aug 25, 1993 CMD-DOUG at 02:02 EDT I tend to agree that, if Rose has it working at this point, she's probably better off NOT doing any further tweaking until she understands it all better and comes up with a need to do things decidely differently. :) ------------ Category 8, Topic 23 Message 81 Sun Sep 05, 1993 R.KIRK7 [Dick] at 13:28 EDT YLR.ROSE- Thanks for the RTCM file numbers.I take it they haven't been updated for V2.02 or are they still pertinent? I download the new files list every month and for some reason the 11052 file number wasn't included. My list went from 11050 to 11058. For some unkonown reason I can't get any of my or the included scripts to logon GENIE. They act like my ID number isn't being sent. When I check the get started instructions everything seems OK. Got any advice? Do I have to load any overlays before exicuting any scripts? Thanks in advance ------------ Category 8, Topic 23 Message 82 Sun Sep 05, 1993 CBM-ED [e.g.bell] at 13:52 EDT Dick: RK> Thanks for the RTCM file numbers.I take it they haven't been RK> updated for V2.02 or are they still pertinent? They have not been updated for 2.02. I will do that today. That is mostly my fault. Sorry. RK> For some unkonown reason I can't get any of my or the included RK> scripts to logon GENIE. They act like my ID number isn't RK> being sent. When I check the get started instructions RK> everything seems OK. Did you put your ID into the script or did you use the token to send your id/password? If the latter, did you use ovrl.defaults to put your id/password into the script. That would cause what you describe. RK> Do I have to load any overlays before exicuting any scripts? Only the AutoLog overlay, which is in there when you first boot up. The scripts are dialing ok, right? Let me know if any of this gets you farther along. ------------ Category 8, Topic 23 Message 83 Mon Sep 06, 1993 R.KIRK7 [Dick] at 19:17 EDT E.G.>Did you put your ID into the script or did you use the token to send your id/password? If the latter, did you use ovrl.defaults to put your id/password into the script. That would cause what you describe. I have just tried the scripts with the tokens to send my id/password. It doesn't get passed the U#= prompt. E.G.>The scripts are dialing ok, right? All scripts dial OK. I tried all kinds of script combinations today. I did get a couple of the ones that came with RTCM to work after putting the local GENIE phone number in. Therfore, it appears that at least my inputting my id/password into the ovrl.defaults file and use of the tokens is working OK. None of the ones I wrote which used the exact same codes as the "canned" ones would log on, however. Does the number of tries and amount of time have any factor in logging on. The one time I managed to log on with a modified "canned" script used a time of 60 seconds between tries. I couldn't get that to solve the log on problem with any other scripts, however. I have had no problem using a script I wrote from scratch to log on local