8bitfiles.net/archives

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

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / 00RTCMMS.SFX / 00rtcm.msgs next >

Wrap

Text File | 1990-02-12 | 44.0 KB | 983 lines

************ Topic 18 Thu Feb 11, 1993 CBM-MARK (Forwarded) Sub: RTC Master -> Looking for help! A place to ask for help with RTC Master. 181 message(s) total. ************ ------------ Category 8, Topic 18 Message 1 Sat Apr 22, 1995 L.VICTORY [LURCH] at 17:01 EDT Thanks, Everyone; I have just received Version 2.04 and with scriptmaker I realized that I didn't have the 'HHHH' in my script as I thought and as Mr. Bell said. Everythings working like a charm so far :). Now, to configure my 'Greeter' See ya'll later, Lurch ------------ Category 8, Topic 18 Message 2 Sat Apr 22, 1995 E.GBELL [e.g.bell] at 18:49 EDT That is good new Lurch.... and I have some more... :) First, I got that font thing tracked down and fixed. And this gets even better. This change required that the bood programs be reworked, and actually made smaller as more functions were moved to machine language. The fact is that I could have always made it 100% ML like BellTerm but didn't because I figured some of the things were more easily configured if I let users twiddle their BASIc portion. Anyway, during an earlier boot program change, I made a colossal blunder in my code that has probably caused some of the crashes that have come up that I couldn't explain before. Anyone who uses 2.04 can see the mistake. It is in the boot program in the first place the dflt.mysetup file is loaded. The line right before that sets the load address. This address is peeked from memory and was done that way to give me the freedom to move that address if I wanted without worrying about complications with the bASIc portion. However, it always relied on rtcm.obj being loaded first. But when I moved that block of code earlier in the program, I didn't do the load so who knows where that was loading that file. duhhhhhhhhhhhhhhhhh! the new boot fixes that and anyone with the old version should try REMming those lines out and resaving their boot. If nothing bad happens that is good. Course, if it ain't broke, don't fix it I guess... and 3.00 is getting close to ready! I reworked ArcAngel Mark... added an ENABLE call somewhere there was none. course it wasn't there in 2.04 either. I'm hopeful that this will fix your problem tho. I also did the documentation for the Archiver, XArchiver, and ArcAngel overlays, TagThief, and redid FingerTip documentation too. And I added the RTCM update document in the archive as well. The TWS source files are in the package for anyone interested in editing the docs. Just send me a copy of the changed file. Mark: I believe this covers everything you have found. Let me know what you find with ArcAngel. I am really pretty sure this one will work for you... as sure as I can be anyway. For those of you using 2.04, I'm really anxious for you to get 3.00 so you can start using the Archiver overlay. It is VERY convenient, especially for the time I save not having to load different programs to create them. Just FYI, I have another overlay I'm starting that you should find somewhat useful, and another two I am considering. off to upload the updates.... :) ------------ Category 8, Topic 18 Message 3 Sat Apr 22, 1995 CBM-MARK at 21:22 EDT Nice work on tracking down those problems Ed! Don't have anything more about my Arcangel problems, except that I did select #1, xmodem from GEnie. Hopefully the new version does the trick for me. It could very well be my Swiftlink. I've had more problems not being able to run RTCM than anyone. Always seems to be that ENABLE routine that has to be added specially for my system :/ I just remembered something. When I first got my Swiftlink (used) I tried out a CP/M term program. Worked just fine. The thing is though, I didn't know you were suppose to switch the Swiftlink over to IRQ! It's not *suppose* to work like that with CP/M I was told by someone. ~~Mark~~ ------------ Category 8, Topic 18 Message 4 Sat Apr 22, 1995 E.GBELL [e.g.bell] at 21:56 EDT Well, you are right.... from what I understand cP/M requires the IRQ to be used instead of the NMI. George Hug says that that is the way god intended it to be done... w/the IRQ. He has said that from the time the SwiftLink came out. As a matter of fact, that is what I did do, add a call to ENABLE after a disk write. That call is in all of my stuff more times than I would have put it by myself... I have always had to be mindful of your system when I do the coding. :) and the RamLink has me thinking the same way about the DISABLE call. Now I just wait to hear how it worked for you. ------------ Category 8, Topic 18 Message 5 Sun Apr 23, 1995 CBM-MARK at 23:18 EDT Ed, now it gets confusing :/ I downloaded the latest fixes and replaced the old files with the new on my RTCM (boot, boot.1670,ovrl.arcangel,etc) disk. I tried once again to get Arcangel to download that v3.00 archive that it wouldn't do for me before. It worked!! Sure, good news, but wait... I stayed online and loaded the previous version of Arcangel and tried another download at that V3.00 archive. Now this time it works!?! I wish I had payed attention to how many timeouts and blocks retransmitted GEnie said I had, but I didn't. Before when RTCM would abort on Arcangel, Genie would come back with at least 7 blks retransmitted. Would Arcangel be more susceptable to line noise than ovrl.ymodem? Ok, that's a wild swing in the dark ;> That's the only update I've had time to check. Will get to the other stuff soon as I can. Oh, the font installs ok now ;D ~~Mark~~ ------------ Category 8, Topic 18 Message 6 Mon Apr 24, 1995 CBM-MARK at 00:37 EDT Ed, well things got worse. Last night was when I did my tests with Arcangel. For the heck of it I just did it again. No good :( Same as the earlier versions. Now what? :/ *s *l *l ------------ Category 8, Topic 18 Message 7 Mon Apr 24, 1995 G.NOGGLE [Greg] at 01:07 EDT just to add to confusion I was using rtcm v3 tonight hosting with the following setup omnitonix interface supra moe,reu usng dma mode install in a RL and it locked up on me. I used the archiver overlay before going online if that matters,this after modifying the defaults. ------------ Category 8, Topic 18 Message 8 Mon Apr 24, 1995 E.GBELL [e.g.bell] at 06:17 EDT Mark: I dunno... guess I'll have to go back in and look again. I just wish it wouldn't have worked at all. Then it would have maybe made more sense. :( MD> Would Arcangel be more susceptable to line noise than MD> ovrl.ymodem I don't think so, BUT, since it is not only downloading but also dissolving it is more susceptible to timeouts... tho at only 2k that should not be a problem. Have you by any chance tried decreasing the block size from 8 to 4 or 2 or some lesser number? greg: GN> omnitonix interface supra moe,reu usng dma mode install in a RL GN> and it locked up on me That is not good! Don't s'pose you can tell me what was happening at the time.... i.e. were you in the middle of an auto-save? Was the lockup an actual lockup.... that is, did things lock up incl. keyboard or ??????? Were you using the alarm? I don't know that all of the above matters... I'm just looking for clues on where to look. Your setup is strikingly similar to mine except that I don't use my REU regularly, and when I do, I usually use it under RAMDOS. The other thing is that I'm not on as long as you all are... I have never had a lockup, but I wonder if that is why.... tho I do frequently leave my computer online and buffering data on FIDO... and it is nothing unusual to get 7 or 8 240+ block buffers with me not at the keyboard. BTW, did you try pressing RUN/STOP RESTORE. That was added as a 'Panic Button' awhile ago. I would like to know more about your lockup tho.... if it is an actual lockup where nothing responds or more what Cam was describing the other night. I have been thinking maybe I'll do an overlay to take a snapshot of different registers for my testing.... something that would save it and restore things. That may be the route I go if we can't deduce this.... of course, that would require a live keyboard. ------------ Category 8, Topic 18 Message 9 Mon Apr 24, 1995 G.NOGGLE [Greg] at 20:06 EDT Buffer was on using with autosave enabled,the autosave was to RL The alarm was also on. Greeeters where also enabled. Yes I I tried the run stop key Something else that was weird,when first on I had a bunch of vertical lines across my screen but I did c= 3 key and restored the screen. I thought that might have come from I was just beboping with overlays checking the archiver. If it makes any difference I just got done using 2.o4 dissolve 3.0. I was running it out of RL with RL swapped to drive 8. Nothing I was typing showed through on the screen either. Hope this gives you some more information. ------------ Category 8, Topic 18 Message 10 Mon Apr 24, 1995 G.NOGGLE [Greg] at 20:14 EDT excuse me,the autosave was directed to the REU,device 13 unless I used the wrong device number for it an that caused the problem during the autosave. But I don't think thats it becaause when I try to do a device that doesn't exist it tells me so. ------------ Category 8, Topic 18 Message 11 Mon Apr 24, 1995 CBM-MARK at 21:48 EDT Ed, next time I'll try reducing Arcangel down to 4 blocks, then 2 if that doesn't work. I don't understand why it works only sometimes. The last 3-4 tests were all done as exactly the same circumstances as I possibly could. Just different days which makes me think I could be line noise or something, related. Btw, on the downloading status screen of Arcangel the Target Drive info doesn't show correctly. I was using drive #8 and it said drive #9. Normally I use drive #9 but changed it within Arcangel's overlay menu to my #8. Might want to check that 'path' displays the right info also if drives are changed. Ed, in the first edition of V3.00 I would occasionally experiance a crash also. Usually happend after a file save from buffer or after downloading. I traced this down to a flakey REU of mine. I had it set up for RAMDOS but was *not* using it to save to during those crashes. Always a reg disk drive. REU was just plugged in sitting there unused. RUN-STOP/RESTORE almost always gave me control back. Unplugging the REU or telling RTCM to use DMA solved the problem of crashes. Don't know if all this would in any way be related to Greg. ~~Mark~~ ------------ Category 8, Topic 18 Message 12 Tue Apr 25, 1995 E.GBELL [e.g.bell] at 06:02 EDT Mark: I am not sure exactly what to look at now.... It would be so much easier if it never worked at all.... MD> different days which makes me think I could be line noise or MD> something I don't think I'll blame line noise... you say you are getting timeouts, a protocol related problem..... the two of you (GEnie and you) are not communicating in a timely manner. If it were line noise you would be seeing CRC errors. MD> using drive #8 and it said drive #9 I'll look at that. I can see where that could happen. The label for 'drive' and 'ddrive' are very close. :) Is this consistent? MD> traced this down to a flakey REU of mine. I had it set up for MD> RAMDOS but was *not* using it to save to during those crashes I don't think it is the same as for Greg. Greg was using DMA and doesn'T use a SwiftLink... tho that may not be the problem either. GN> Something else that was weird,when first on I had a bunch of GN> vertical lines across my screen but I did c= 3 key and GN> restored the screen Greg: When RTCM 3.00 first starts up, your screen will be goofy because it is testing for the 64K VDC. Do you have 16 or 64K? I am curious because someone with 16K told me he had a problem and his system is a 16K system. I don't have one anymore to test it so this could prove helpful. I'm also not sure why you used c=3 or why it worked unless it was just that the 128 finished its tests at the same time as you pressed those keys. c=3 is just a toggle into a 'non-chat' type mode where your cursor is in the main window and what you type is sent immediately to the other system. It is a toggle, so doing it again moves you back to the user window. Obviously, none of the overlays should cause you any problems. Just one thing I wanted to point out tho... GN> autosave was directed to the REU,devic 13 unless I used the GN> wrong device number for it and that caused the problem during GN> the autosave Can I take it that the problem occurred at an auto-save, which I kind of suspected originally? If so, then perhaps this sheds some light on the problem. The device 13 setting is ONLY for RamDos operation. There is no device setting necessary for DMA saves.... the REU is not really a device (in the normal sense) in DMA saves. Kind of the same thing for the RamLink and DMA saves. If I read this right, you were directing your auto-save to a non-existent device. I'm not sure if this would do what you experienced or not. I'll have to give this a try. One reason I'm not sure is that I kind of think I remember that the DMA setting is automatically detected by the autosave routine and supercedes the target device. I just don't remember. :( Will have to check at first chance. Thanks for the complete report. I will definitely check and get back to you. ------------ Category 8, Topic 18 Message 13 Tue Apr 25, 1995 CBM-MARK at 08:57 EDT Ed, I'm pretty sure that the Target drive display is consistantly wrong ;> I thought I noticed it before but I was thinking it was on the overlay menu screen not the downloading status screen. Finally did see where it was. Ok, I just loaded the overlay and gave it another shot. Seems my memory was wrong as to when it happens. I said after using the overlay menu to change the Target device that Target drive info would be wrong, didn't I. No, that's not when or how to see it for yourself. Gotta quit playing with these programs when I should be in bed ;> Anyway, use C= U to make the Target drive change. Then use press 'd', then C= 0 (on the keypad- but you knew that ;) You should see it don't match up with what the Target has been changed to. This making sense? I should be in bed now ;D ~~Mark~~ ------------ Category 8, Topic 18 Message 14 Wed Apr 26, 1995 D.SMITH123 at 00:25 EDT Help! I can't get RTCM128 @2400 baud to logon GENIE. The manu al is hard to understand. Take me thru step by step. The manu al also says -scriptmaker.sfx & scriptmaker are on disk, not mine. Please I've been trying to get 2400 baud since December! ------------ Category 8, Topic 18 Message 15 Wed Apr 26, 1995 E.GBELL [e.g.bell] at 19:11 EDT DS: I have been sick all day so I'm going to postpone a detailed reply until tomorrow. Could you fill me in on what you have done alread in terms of setup of your boot program? Are you using the SwiftLink? what part of the manual is giving you problems? Mark: I'll try to duplicate your results. With your description, it should be easy to do. Thanks! ------------ Category 8, Topic 18 Message 16 Thu Apr 27, 1995 E.GBELL [e.g.bell] at 06:14 EDT Mark: I know now why you are seeing that discrepancy between drive number displays, and this should be a display only problem. Version 3.00 changed the way the overlays operate. It used to be that you had to use ^m to bring up the slot selection prompt, then enter a slot, then IF there was something in that slot it would get executed. If not you were notified and you exited. That changed with version 3.00. Now, when you load an overlay, you go immediately to the menu for that overlay. You will never see the slot selection menu. In most cases, I removed the hotkey entry by simply pointing all of the addresses in the overlay table to point to 'SLOTMENU'. Apparently I never made the change in ARCANGEL. If you try a hotkey entry into most of the other overlays, you will just go to the overlay menu. I did the above to take more control over the execution process. Before, it was possible to enter an overlay from an old version of RTCM and it would lock up. The code to notify you of that was always in place but it relied on two routines to do the screen notification and return, namely MSG.SYSTEM and EDSROOM. Starting with RTCM 3.00, these two routines have JMP entries that allow overlays of any version to notify you that they can't run under the version being used and exit properly. However, to assure that this trap worked, I had to limit points of entry to the overlay. I never use the hot keys and suspect a lot of others don't either. That said, here is the explanation for your display discrepancy. The display is updated at SLOTMENU, which is the point of selection for all overlay operations. What you did bypassed this meaning that whatever was last in there is displayed. I can correct this one of two ways. I can either redo the tables in the overlays that I changed to give them back their hotkey entrances... and I'd also have to move the display update routine back into the DIAGNOSE routine... or just make the fix to the ARCANGEL slot table. That is the fastest, easiest way to go. Do you think the hot keys are worth it? I didn't and so kind of quietly removed that feature from most of the overlays. Just missed ARCANGEL, and perhaps some of the others as well. The exception I think I did allow was the ^_ (or ^f) in Datamover that executes that overlay.... anyway, what do you think. Either way is not a BIG change... just one is bigger than the other. ------------ Category 8, Topic 18 Message 17 Thu Apr 27, 1995 CBM-MARK at 08:36 EDT Ed, the only overlay hot keys I have used regularly are to execute Datamover and download or upload in Ymodem. Pretty much all the rest I used the overlay menu to make my selections. With mention of the fact the overlays all enter their menu when loaded reminded me I have a small complaint ;> I sure wish that when using the Ymodem overlay it would return to RTCM's main screen after the fie transfering is done instead of the overlay menu ;) Oh, yeah, we were talking about Arcangel. ;D Slot 'd' is a hotkey entry to the overlay if I'm not mistaken. Not sure if the other slots are, but I would leave at least slot 'd'. But with consistancy in mind it would probably be better to do one or the other with *all* the overlays. Either make all the slots in all the overlay as hotkey entries or none at all. With thinking like that, I say, hotkeys. Gives the usser a choice how they want to use the overlays ;D ~~Mark~~ ------------ Category 8, Topic 18 Message 18 Thu Apr 27, 1995 E.GBELL [e.g.bell] at 18:24 ED Mark: MD> wish that when using the Ymodem overlay it would return to MD> RTCM's main screen after the file transfering is done instead MD> of the overlay Actually, I agree with you. I changed things for consistency. I felt that in most cases it was better to have one exit to the main program than to have all routines exit there afterward. I was running into situations where I had to reenter the overlay multiple times... but the Ymodem is a valid point. I have had similar feelings about its exit... it will be changed. MD> I say, hotkeys. Gives the usser a choice Ok! That will cause another delay, but not a major one I don't think. I'll get in there this week and change the tables gain. Due to the way the new overlay calling code is written, you will still not see the slot selection prompt anymore tho.... the hot keys will be the only way to activate a particular slot. All other slots point at SLOTMENU, which I feel is a better idea than telling the user that there is no code at a slot position. It is not possible, I don't think, to allow all slots to be accessed via hotkeys... many of them need setup prior to being called.... I'll look at them on a case-by-case basis. Any other suggestions while I'm going in then? ------------ Category 8, Topic 18 Message 19 Thu Apr 27, 1995 E.GBELL [e.g.bell] at 18:54 EDT DS: I am feeling better now so lets have a go at solving the problem.... As for ScriptMaker, I can't speak to that, but we should be able to get you online at 2400 without them in the meantime.... How much have you been able to get done? We can do that a step at a time..... First lets set up your GEnie ID and password.... 1] Press the ALT key... you will see a menu come up with different overlay names.... press the letter next to 'defaults'. It is probably 'd', but if not, select the one it is. This will load the defaults overlay. 2] Press CTRL-M, which brings up the slot selection menu. It says something like 'Select Slot [A-M]'..... you want to select slot 'd', which lets you set your defaults. This will bring up a menu bar that looks like this.... Profile Serial Modem Other Security Use the right cursor to move the light bar over the Security heading and when you get it there, press cURSOR down to pull down the Security menu. It will look like this.... Profile Serial Modem Other Security Encryption Key Password User ID Use your cursor down key to move te new light bar over 'Password' and then press RETURN. This will bring up a new screen that asks you to enter your password. Enter your GEnie password and press RETURN. You will then be asked for your user ID. Enter your GEnie User Id and press RETURN. This is important for the rest of your setup of your logon script files. 3] Press ESCape to exit the defaults overlay. You will be asked if you want to install the new settings. Just press RETURN with the cursor over the 'y'. This will send you back to the main RTCMaster screen. 4] Press C=w, which will bring up another menu. Depending on what version of RTCMaster you are using, selection 3 will either read 'dflt.' or Profile. They are both the same thing. Select 3 at this menu. When you are asked if you want to load or save, type 's' and press RETURN. When you are asked for a name, enter 'mysetup'. The 'dflt.' prefix is automatically added. This will save your defaults file to your system disk. (It *might* be a good idea to scratch 'dflt.mysetup' before you try saving the new copy... I don't remember if this is a save with replace type or not.... better yet, rename it before you save the new copy) All of the above steps get you ready to set up your boot program and use the scripts we have included with the program. Are you with me so far. :) Now lets get the pertinent things in the boot program set up.... There are only 2 or 3 places in Ez.BOOT that you have to make changes to get started.... Consider... 140 dcd=.:poke 56833,.:poke 56834,170:rem check swiftlink Note that it is possible line numbers are differet. The code you have to change will be the same. If you have a swiftlink, the above line will not need to be changed. If you have a Supra or other Hayes compatible modem, it probably won't need changed either. If your modem keeps thinking it is already online when you aren't, change 'dcd=.' in the above line to 'dcd=16' and try again... 250 df=peek(4895)*256+peek(4894):rem dflt. file load address 255 f$="dflt.mysetup":bload(f$),p(df),u(dv) The above two lines should be removed from the boot program. They appear deleted. 290 if peek(56834)<>170 then begin 295 : io$="2400":io%=-10*(io$="2400")-8*(io$="1200")-6*(io$="300") 300 : open2,2,2,chr$(io%)+chr$(0):poke 186,dv 305 bend Note the above lines carefully if you are not using a SwiftLink. The 'io$="2400" sets your baudrate if you are not using SwiftLink. This is a departure from many other programs, and even earlier programs of mine. I have taken it to be fact that a person uses the same modem every time and should only have to make this selection once.... make it here and yyou won't have to see the selection again. 380 io$="scrp.mailbb"+chr$(.):rem *must* end w/chr$(.) The above line specifies the logon script that will automatically execute after the number is dialed. You don't have to make any changes here, by the way. That is all you have to do to adjust your boot... there are more things that can be adjusted, but the above is all you HAVE to set up to run RTCMaster. The last thing you need to do is set up the logon script to dial the right number.... Save the boot program by typing (on a blank line) LIST 20. Move the cursor up to the line that is listed and change the 'u=11' to 'u=' whatever drive you want the file to be saved to and then press RETURN. Your custom boot will be saved to that drive. Finally.... Press the ALT key again, and at the menu, press 'a' to load the AutoLog overlay. Press cTRL-M to bring up the slot selection prompt again, then press 'l' to 'L'oad a script. You'll get a list of scripts (scrp.#####) on the disk. Type 'mailbb' at the prompt. This script will load and begin to execute. Press STOP to abort it. You will be back at the main RTCMaster menu. Press CTRL-M again, and select slot 'm' to modify this script. Go through all of the prompts.... just press RETURN to leave all settings the same EXCEPT for the phone number. Change this to the number you use to call GEnie. Press RETURN through all the rest of the prompts. When done, save this back to disk when prompted to do so... save it as the same name..... 'mailbb'. the 'scrp.' prefix is added automatically. Now to log on, all you have to do is type CTRL-M to bring up the slot selection menu and select 'e' to execute. It should dial in and log you on at 2400 baud. And from now on, every time you run your EZ.BOOT program it will automatically dial GEnie and auto-log you on. Let me know how you make out w/all of the above. If the instructions here are easier to follow, I'll see about getting them included with the manual, tho I know I've got a file or two outlining this stuff... ------------ Category 8, Topic 18 Message 20 Fri Apr 28, 1995 D.SMITH123 at 01:06 EDT I'm going to read what you wrote in the previous msg tommorow and I'll let you know if I could follow your inst. Thanks in advance ------------ Category 8, Topic 18 Message 21 Fri Apr 28, 1995 CBM-MARK at 08:14 EDT Ed, off hand I can't think of any changes I'd like to see other than those already mentioned ;) ------------ Category 8, Topic 18 Message 22 Fri Apr 28, 1995 C128.JBEE at 14:46 EDT D.SMITH123 is using a minimodem C24 by aprotek with RTCM V2.04. ------------ Category 8, Topic 18 Message 23 Fri Apr 28, 1995 E.GBELL [e.g.bell] at 18:17 EDT John: It is feast or famine with that modem and RTCM... :( However I think that 3.00 addresses one of the problems, namely the init string that Nate identified... and which DSMITH23 might need to consider as well. Might have to manually add that init string in the meantime... to make sure carrier is recognized properly... Mark: I've been kind of brainstorming and I've come up with a painless way to put the hot keys back in w/o any changes or difficult coding... I'm going to use dynamic keyboarding.... I'll grab the hot key, pop it into the keyboard buffer, then enter the slot menu with it like that... net effect is that you enter the overlay and press the desired function key as though you were actually there... I've already tested it and it works. Hard part is putting it in all of the overlays... That necessitated another change IMO... which I'm implementing at the same time.... namely an indicator for the menus to identify the hotkey items... from here on, items in an overlay menu that appear in REVERSE field (just the menu letters) will be hot key items. That way you can quickly tell what are hot keys and what are not. Non-hot-key entries simply take you to the slot menu.... more work than I really wanted to do but it will solve several situations cleanly without taking anything away from any of rTCM's functions and doesn't add a LOT of code... just have to reassemble all of the overlays. I was wrong about having removed the hot keys from all of the overlays... quite a few of them still had them in there... just the new ones that did not... btw, I'll fix the Ymodem thing you wanted to see replaced too. :) ------------ Category 8, Topic 18 Message 24 Sat Apr 29, 1995 C128.JBEE at 18:00 EDT When you are using the autolog overlay and are not watching the screen and believe you have the editor overlay active it is very easy to send your password and id by pressing CONTROL M - E. Maybe to execute scripts the letter X should be choosen instead? ------------ Category 8, Topic 18 Message 25 Sat Apr 29, 1995 E.GBELL [e.g.bell] at 19:49 EDT I'll take your word for that... I'm not sure how that happens, but I know it must or you wouldn't have mentioned it.... just for my curiosity, how are you set up that that happens? I have my password and ID in the 'dflt' files and the scripts have only tokens, which is how I can share them in the releases. X is not available in the way you mention.... the slots only go up to 'u'... Perhaps it would be better to choose a different letter for the Editor overlay, but there are going to be more than the editor and autolog using 'e'.... hmmmmmm! ------------ Category 8, Topic 18 Message 26 Sun Apr 30, 1995 CBM-MARK at 08:48 EDT Ed, I can see how it's possible to have your id/password sent by mistake. Don't forget that there is a flag in a script that is used if the script is executed while online. The CASE that is flagged will send the RESPONSE string if executed online and if that happens to be the tokens for your id/password... well they get sent :( About the overlay hotkeys, if you're gonna make some of the slots hotkeys wouldn't it be just as easy to make *all* the used slots hotkeys. Not sure how you are programming this but is the dynamic keyboard thing a separate routine you JMP or JSR to? If so, either the entry is a valid slot or it isn't. If not, then just dislpay the overlay menu as if no hotkey was used. Course, with my limited programming ability I may be suggesting more work than warrented ;> ------------ Category 8, Topic 18 Message 27 Sun Apr 30, 1995 E.GBELL [e.g.bell] at 13:56 EDT Mark: The changes are all in place already.... including the reverse menu selections... and in some cases I felt that hotkey entries were not warranted... In others, like in the copier overlay where an upper case B is also a menu option, there was no way to make that a hotkey. In most cases tho, all options are hotkeys... the games are the only exception... didn't change them at all... I'm working on a boot maker overlay right now that will create an ez.boot program for the user who just has to run the overlay and answer the prompts... not quite to the testing/debugging phase of it tho... I'm kind of hopeful it will ease installation.... ------------ Category 8, Topic 18 Message 28 Mon May 01, 1995 E.GBELL [e.g.bell] at 06:05 EDT That explains that Mark. I can be very shortsighted when it comes to things that people can do differently than what I do. That is why it is so helpful that others can test stuff. JOhn: I'll see where else I can put that menu selection... perhaps that function should not be a hot key at all? It wouldn't hurt me not having it because I rarely use hot keys.... data mover is the only one I do use because I remember it. :) I did an overlay yesterday to automate the setup of RTCM. It asks you pertinent questions about your setup and preferences (font, dflt.####, music file, REU, SwiftLink, etc.) assuming nothing, testing for the presence of nothing, then creates a boot program called 'MY.BOOT' which you load and run. After the boot program is created, it asks some questions it needs for the 'dflt.' file (GEnie user id and password and tone/pulse dial), then saves that. It uses the 'dflt' file you specified for the boot program. Then it asks for the phone number you use to dial GEnie for that script, and modifies the script specified in the boot program... modifies that and saves it. The overlay is complete... just needs some tweaking... when I run it the init string is grunged.... can't figure out why just yet, but that is what is in the works right now. I'd like to ease the setup of RTCM for at least new users. ------------ Category 8, Topic 18 Message 29 Mon May 01, 1995 D.SMITH123 at 23:18 EDT To EGBell Reference your instructions. I got farther than I have before but when I go to "e" execute the progam says that I'm already on line"! I'm not a programmer , in case you couldn't tell I was able to follow your directions but as I say above I still can't get online ------------ Category 8, Topic 18 Message 30 Mon May 01, 1995 E.GBELL [e.g.bell] (Forwarded) Hmmmm! Well Eddie.... I don't think it has anything to do with the clock, but take the 'rl%=16' or whatever you have it set to out of your boot. That will disable that. I keep my copy on the ramlink and boot off of it every day multiple times. There must be something different between what you hve set up and what I have set up. That is what I have to find out.... Brenda... could you try to disable that test as well by changing whatever you have RL% set to to RL% = 0 (or rl% = .) so the clock does not get involved. I do a LOT of loading of files because of developing.... dropping to the monitor is never a problem unless the code I'm working on has a bug in it or i put a brk in my code. Is this ALWAYS when accessing the RL, and again, what bank and address is the BRK to? If we know that, then perhaps Doug can shed some light on what is going on at that location. Eddie.... once is too many times when it comes to BRKing to the monitor. What all else are you running or do you have installed? An REU? RAMDOS? cartridges, SwiftLink? AproSpand? The next time it happens, make a note of what is on your screen so I can start tracking this thing down... I'm particularly interested in what you were doing at the time and what the address is where the program dropped to the monitor. Thanks! ------------ Category 8, Topic 18 Message 31 Tue May 02, 1995 E.BOURDON1 [C128-Eddie] at 01:06 EDT All I have on my system is the RL, Swiftlink and a 1581. I'll make a note of the info next time it happens. ------------ Category 8, Topic 18 Message 32 Mon May 01, 1995 B.GANN1 [Brenda] (Forwarded) Uh oh... when I tried to download from GEnie with RTCM to the RL, it dropped to the monitor. Does that mean I need the timing jumper? There are HD and RL versions of The Write Stuff. So that is probably why my 1581 version is not working on RL from a Native subdirectory. Why doesn't the RL version support the time and date stamp? Brenda ------------ Category 8, Topic 18 Message 33 Mon May 01, 1995 E.GBELL [e.g.bell] (Forwarded) Brenda: BG> download from GEnie with RTCM to the RL, it dropped to the BG> monitor I have a few questions to ask about it.... I'm not sure where topic overlap is in this so I'm going to consider this a grey area. - What protocol - what File - what is your RTCM setup - how much room in your partition/directory Anything else you can provide... Also, to what address did it drop and into which bank? The bank number is the first number in the address reported on the screen... for example: effd4 would, in the context of my question, be bank 14. It is not bank 14 in actuality, but I'll understand what you mean. The BRKs I have encountered were always to bank 8, which RTCM never uses. The RamLink seems extremely sensitive to enabled NMIs so I have been extremely careful for quite awhile about disabling them. Was before too... just moreso since I started working with this piece of hardware. I don't think that the jumper is the problem if your RL works in all other situations. I had a custom chipset in my 128 when I got the RL and had to remove that. It would not work at all until I put the original 128 chips back in... kind of a bummer cuz the chips repaired all the 128 bugs known at the time. I have gone to lengths every time something like this crops up to find out why, where I can, and do something to prevent it in the future, so when it happens if you can remember all of the specifics it helps. I regularly download to the RamLink and never have any problems at all, so there is something different about your setup from mine. Anything you can provide can help not oly Doug, but me as well. Thanks! :) ------------ Category 8, Topic 18 Message 34 Mon May 01, 1995 E.BOURDON1 [C128-Eddie] (Forwarded) Re Brenda's problem. I have also had trouble with RTCM when used on a RL, but at first it worked fine. I thought that it might have been corrupted, so I re copied it to the RL, still, the same problem persisted. It usually loads fine, but will sometimes drop to the monitor when it attempts to 'find' a auto-logon file. If I try to load anything from the RL (overlays, dflt. files, ect..) it usually drops to the monitor. I have the RL set as drive 8 while all of this is happening. I tried loading RTCM from the RL again, only this time I used drive #9, a 1581, as the system disk (after booting off the RL) and it loaded all the overlay, dflt, ect, fine. Any ideas? This is RTCM v3.00. It doesn't drop to monitor all the time, but more than I like. The RL works fine with all my other programs, so I'm sure it's not the RL One more thing (this might be it) the RL doesn't have the RTC on it. ------------ Category 8, Topic 18 Message 35 Tue May 02, 1995 E.GBELL [e.g.bell] at 05:54 EDT DS> when I go to "e" execute the progam says that I'm already on DS> line"! This is telling you that your carrier mask is set incorrectly. The line you want to change is: 105 dcd=.:poke 56833,.:poke 56834,170:rem check swiftlink The line number may be different in your boot program, but the code will look as it does above. Try changing the line above as follows: dcd=16:poke 56833,.:poke 56834,170:rem check swiftlink I didn't put in the line number. Make that the same as it is in your boot program. But note the 'dcd=16'. That will change your carrier mask for the opposite of what it is now. What kind of modem do you have, btw? ------------ Category 8, Topic 18 Message 36 Tue May 02, 1995 C128.JBEE at 23:18 EDT I was never able to get RTCMV2.02 or 2.04 to work with "my" Ramlink no matter what I did. I was the only one on staff that had the problems. I checked my RamLink, clips, tested my hardware, swapped PLAs, CIAs, etc. to no avail. I know customers have been using it with no problems on RamLinks. It looks like whatever the problem was with the code has been eliminated with V3.0, though it still needs extensive testing before I can say for sure. ------------ Category 8, Topic 18 Message 37 Wed May 03, 1995 E.GBELL [e.g.bell] at 06:22 EDT I don't know what I changed that would have had any effect like that. I have always used standard hi-level dos calls with the exception of overlays that access 2 drives at the same time. In those cases I use lower level DOS calls, but still nothing the RamLink doesn't support, and I use them with the RamLink I have all the time. It would help if I had memory maps or programming examples of use of the RamLink. There are some in the manual, but very few.... and no ML examples. There is at least one error code missing from the manual (error 39) which burned me, and some commands are documented that don't work as listed from what I read on FIDO, though this is just a transposition error in the manual. There is nothing that I have been able to find on NMIs or IRQs or how to finesse them when wedging but CMD does not seem to be as generous with programming information as Commodore was (in their manual). Kind of a shame too, given Doug's call for us part-of-the-problem type programmers to get into the push-the- envelope frame of mind. Something like the Commodore 128 Programmers Reference Guide would be much more help than 'doesn't handle errors properly' type stuff. I have had minimal problems with the RamLink and RTCM.... and given the way I use it (for development) I would think I'm more prone to them than everyone else. I'll keep working with things. If this was 5 years ago I might have given some thought to creating such a memory map, if it is even possible. It seems I have read somewhere that Commodore did provide special information to Jim Butterfield early on, and the logic I read makes a lot of sense. People like Jim were instrumental in helping others move along in their learning curve. If this is true, it was a great investment on the part of Commodore. Anyone who has problems of this nature, please let me know. There is obviously something I'm missing... or something I don't know. If you crash to monitor, note the address of the BRK and ESPECIALLY, the 'bank', which is the first number in the address listed. The address will be the first set of characters in the BRK message, a 5 character code.... something like this: 8c002 This will tell you where in ram (2 byteslater) you 'broke' and to which bank. The first character, 8 in the example, tells you what memory configuration you were in when the BRK happened. RTCM normall woudld show an 'e'. Depending on what you were doing, you could also see a '0', '1', or 'f'. If it is RamLink code executing when the BRK happened, you will see an '8'. A program will not BRK to a configuration it was not placed in... period. RTCMaster NEVER puts an 8 in the memory management unit... EVER. That is a ROM configuration putting external code into memory from $8000 to $c000. RTCMaster would NEVER do that... never have to. It is easier for a programmer to tweak code to navigate this than it would be to change ROM code. But it is hard to do anything flying relatively blind. ------------ Category 8, Topic 18 Message 38 Wed May 03, 1995 D.SMITH123 at 21:26 EDT EG.BELL I did the dcd=16 now when I 'e' I get M625;1 M625;1 then 'TIMEOUT! CASE#4 1 ?' 'TIMEOUT when I 'h' I get +++ath when I 'k' keyboard dial doesn't work when I 'c' says Currently Online! I have a Aprotek minimodem-C24 btw & Thanks 4 trying. /Doug ------------ Category 8, Topic 18 Message 39 Wed May 03, 1995 E.BOURDON1 [C128-Eddie] at 22:28 EDT Ed, Here is one of my results from breaking into the monitor: 89f23 ------------ Category 8, Topic 18 Message 40 Thu May 04, 1995 N.ONEIL [Nate] at 00:50 EDT D.SMITH123 I had a similar problem using Aprotek C24 with RTCM. Adding the following to EZ.boot took care of it for me. 4 DV=PEEK(186) 5 FAST:OPEN2,2,3,CHR$(10)+CHR$(0) 6 GET#2,A$ 7 PRINT#2,"AT#C1" 8 SLEEP5 DAN T. analyzed the problem and suggested the added BASIC lines. However, I had to add line 4 to his line 5-8 and modify line 45 as follows 45 BLOAD(F$),U(DV),B0,P24576:RESTORE 450:Z=. PEEKing 186 assigns to DV the # of the device from which your loading RTCM. That # is used to BLOAD from in line 45. 186 holds the # of the last device accessed. That device would be device 2 which is oopened in line 5. But dv saves the original device #. Hope this helps. Nate BTW. DAN T.'s analysis is at CAT8 TOP18 MSG 6 (enter REA 18 cat=8 6) to read it. ------------ 8 |