8bitfiles.net/archives

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

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / RTCMMSGS02.SFX / 04rtcmmsgs next >

Wrap

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

----------- Category 8, Topic 18 Message 121 Sun Oct 01, 1995 R.KIRK7 [Dick] at 21:19 EDT E.G. OK I did a C=L to load a file which filled the buffer. I did a CTRL O to stash it to bank 0. I did a C=K to clear the buffer. I did a CTRL I and selected bank 0. I did a C=V to view the buffer. I used CTRL B to page through the buffer. I was able to view the total contents however when it got to the end it just kept going over agin from the beginning. For some reason it is in a continuous loop and will never end. See if this works for you! ------------ Category 8, Topic 18 Message 123 Mon Oct 02, 1995 E.GBELL [e.g.bell] at 05:38 EDT RK: The buffer viewer in 3.01, and from now on, cycles over instead of ending... iow, when you reach the end, RTCMaster prints a line like this: -------------------------------------------------------------------------- and then starts again at the top of the buffer. If you are scrolling up, it prints that line and starts again at the bottom. This is just a convenience feature that I find kind of useful. That is what you are running into. As for the C=V and ^V.... C=V has always been the key used to view the buffer. With 3.00, I believe, I introduced a scrollback buffer, which is a 48K buffer totally separate from your main buffer. This buffer is on all the time, whether you have your buffer on or not. Note that the only way you would have this is if you have a 64K VDC. Those with 16K VDC don't have this feature. Note also that when you mark a buffer you are going to be shown less buffer.... so if you mark the last 20 or 30 lines of a buffer, it is going to 'loop' over and over again because of what I mentioned above. As for the page size I mentioned, that is set in defaults.... it is a setting that allows you to set the size of your buffer for autosave. For DMA, you should leave it at the max setting which is 254 I believe. If you want RTCMaster to autosave your buffers to disk in smaller files, you would set this smaller. It has nothing to do with the size selection you mentioned. That only tells RTCMaster how many banks are available in your REU. The page setting tells it how much data to buffer before autosaving. But since DMA saves a whole buffer no matter what, it would make no sense to set a buffer setting less than maximum. That would result in a huge waste of your REU memory. I'm glad you figured out what the problem was. I'd have been stumped trying to find that one. ;) BTW, the new version, 3.02, has some further enhancements to the scrollback buffer... it correctly strips out the deletes now... AND the characters that were deleted.... If you know the problem you will know what I'm talking about... if you don't it isn't important. O, and about the boot program... are you using it on YOUR copy of EZ.BOOT or the new one uploaded with OVRL.BOOTSET. This is critical. The BOOTSET overlay absolutely requires that you use the EZ.BOOT created especially for use with it. One way or the other, I'll see that you get the new version when it is ready... I tested it again when you pointed this out so I know it works. ; ) egb ------------ Category 8, Topic 18 Message 124 Mon Oct 02, 1995 CBM-MARK at 22:37 EDT Ed, I'm having problems with getting 3.02 to operate correctly. Maybe a bad archive? It verified Ok at this end. What happens is that during boot up and after LOBLOCK is loaded you get a message atthe top of the screen saying "loading". Well, nothing is loading. It should be the modem init string being sent but that's not shown on screen. Sorry, forgot to look at the modem to see if the init string is in fact being sent but just not showing on the screen. Just thought of that now :/ The other problems are, right after the boot up is complete the buffer shows it contains 64768 blocks. It should be empty on initial start up. Viewing it I see lots of garbage, the modem init string, the word "autolog" and some other words that are related to RTCM. All repeating over and over. You *are* able to clear the buffer. The last thing is, touch the RUN/STOP key (no RESTORE) and the whole thing crashes to a black screen with a block cursor. RUN/STOP-RESTORE does *not* recover from the crash. Only resetting the computer gets you out of it. I quit testing here. ~~Mark~~ ------------ Category 8, Topic 18 Message 125 Tue Oct 03, 1995 E.BOURDON1 [C128-Eddie] at 00:35 EDT Ed, I am also having trouble with 3.02. I have had it crash on me 3 times within 10 minutes. Each time I was in the RTC. I didn't get a chance to write down what the monitor broke to the first 2 times, but the last time I got this: 00202 be 00 01 de 52 Also, I am having trouble using the scripts. I have redone all my scripts with the ovrl.Scriptmaker, but the problem still persists, and I have not had this problem with 3.01. It dial the number fine, I get the connect message, it prints the 'hhhhh' to the screen, then the music starts playing, and the script hangs at that point. I have to hit run/stop and enter the rest manually. I am booting off a Ramlink, and have set up my boot file with the bootmaker overlay. RTCM 3.01 worked almost flawless for me, with the exception of some trouble with Datamover. Any ideas? ------------ Category 8, Topic 18 Message 126 Tue Oct 03, 1995 E.GBELL [e.g.bell] at 06:04 EDT Eddie and Mark: I'll have to check what I uploaded. Until then I can't explain any of this.... I use 3.02 exclusively, booting from the RamLink, and tested almost exclusively with SwiftLink, but I've also used my user port modem... and am now as a matter of fact. I'll be looking into this but not til Thursday... I have classes tonight and tomorrow night. ed btw, Eddie, just for testing purposes, try disabling the music... see if that makes a difference. ------------ Category 8, Topic 18 Message 127 Tue Oct 03, 1995 E.BOURDON1 [C128-Eddie] at 20:55 EDT Ed, When I had setup the myboot file, I also have the 'allow music to burst forth' set to no in my dflt.mysetup. I am assuming this is the music you are talking about. ------------ Category 8, Topic 18 Message 128 Wed Oct 04, 1995 E.GBELL [e.g.bell] at 05:30 EDT Yes, that is what I was talking about. I'm reasonably sure all of these problems are setup problems.... that is, there is a setup that is causing problems and I never see it because my setup is not like that... which is why I always ask that the files be tested before release. ;) The address you gave does shed some light on things. If it is in the $02xx range, it *could* be the 'install.obj' file that is trash. I kind of think I use that address as a temporary code buffer during the 'sniff' routine. I have another class tonight, but tomorrow night, I'm going to dissolve the archives here and try them out on my system. With the hours I've been working (and going to school) I just did not have time to dissolve them before sending them because there are so many files. Now I'll have to. If it works here, I'll try making a bundle of the absolutely necessary files and upload that and work from there. egb ------------ Category 8, Topic 18 Message 129 Wed Oct 04, 1995 CBM-MARK at 21:03 EDT Ed, I have my music turned OFF in my defaults, same as Eddie, and AUTOLOG turns it on after a CONNECT when it shouldn't. Eddie, try pressing the RUN/STOP key to get the music to stop. Only press it once though. A second press may cause the script to abort. ------------ Category 8, Topic 18 Message 130 Wed Oct 04, 1995 E.BOURDON1 [C128-Eddie] at 21:13 EDT Ed, That is what we are here for, to test them for you. If they all work fine for everybody, then there is no need for you to spend all that extra time on the files. I was hoping that it was just something that I had done wrong, and that 3.01 had worked so well I couldn't wait to try 3.02. ------------ Category 8, Topic 18 Message 131 Wed Oct 04, 1995 E.BOURDON1 [C128-Eddie] at 23:31 EDT Mark, That is what happend to me. I have the music set to off, then I am forced to hit run/stop to stop it. The script then doesn't continue, nor is it aborted. I am forced to then hit run/stop to abort the script and continue manually. ------------ Category 8, Topic 18 Message 132 Thu Oct 05, 1995 E.GBELL [e.g.bell] at 07:04 EDT I thought of something that I had forgotten to mention earlier... Are you using a Swiftlink Eddie? I honestly don't remember... if you are, you have to recreate your boot program. Use BOOTSET to do this as it will automate the whole process. This version of RTCM no longer looks for (or even has) the file 'SWIFT.OBJ'. The new version is called 'SWIFTRTS.OBJ'. This file is the NMI driver for the SwiftLink. There are some other things in there too, but mainly the engine. If you are still trying to load SWIFT.OBJ and it is not there, it would explain the crashes I believe. I have been using 3.02 for over a week now without problems, but with the new stuff in RTCM, this kind of thing always seems to happen to me. Another thing, if you are using a high speed modem, that you will want to do is to go into defaults and set your flow control method and the limit before control is asserted. Using BOOTSET will also automate these selections. If you are using a user port modem, I have more detective work to do, although I never touched those routines, and I did test them before uploading the program too. Note that if you are using a user port modem, the flow control stuff won't really apply to you as that driver does not look for it or assert it. ******** Also ********* I found a bug in 3.0# that you might never have found. It is not a serious one, but.... If you load a buffer and then do a search for a string and select one of the located occurrences and view from that point AND THEN LOAD ANOTHER BUFFER, when you exit the buffer viewer, RTCM window management gets confused and the cursor goes behind the main screen status line. RUN/STOP/RESTORE will fix that. You would have to restore your buffer if you wanted that data. The fix is in for the next release. And as an aside, version 3.02 now maintains your buffer when you hit RUN/STOP/RESTORE so that is different too. Dunno why I didn't think of that when I put in the trap for those keys! Mark: As for the music not being turned off I can't explain that. That flag is in the dflt.##### file. Nothing anywhere in the program changes it (except for ovrl.defaults) so I would have to suspect it is set in your dflts. file somehow. I'll get the address for you. You can load the file and check that address to see if it is 0. I believe the only two settings are 0 and 128. ed ------------ Category 8, Topic 18 Message 133 Thu Oct 05, 1995 E.BOURDON1 [C128-Eddie] at 16:35 EDT Ed, I am using a swiftlink with a 14.4k modem. I did create a new boot program with the bootset overlay. I answered all the questions and all seemed to have worked fine, until I tried it out online. When I set up my modem stuff, I set the baud rate to 2400. I no longer have access to a 9600 node, so I decided to leave it at 2400. I also re-did my dflt.mysetup file incase there was anything that was switched between 3.01 and 3.02. ------------ Category 8, Topic 18 Message 134 Thu Oct 05, 1995 CBM-BANDIT at 22:59 EDT Ed, I logged on with 3.02, but did it manually just to check things out... will go thru the BOOTSET routine tomorrow. By any chance is there a way to disable the screen blank routine? To me, I find it irritating. I find that if I leave the keyboard long enough and don't want to turn off the computer, I will turn off the monitor. (I leave my computer on all the time) :) ------------ Category 8, Topic 18 Message 135 Fri Oct 06, 1995 E.GBELL [e.g.bell] at 05:32 EDT Cam: Set the timer to 128. That will disable it. Eddie: I'll reply to you later... I did some testing of what I uploaded last night on my user port and it worked ok... except for one thing, the xon/xoff, which I'll explain tonight. ------------ Category 8, Topic 18 Message 136 Fri Oct 06, 1995 CBM-BANDIT at 07:04 EDT I did set it to 128, but the screen still went blank after awhile :/ I'll try again later along with the other goodies. :) ------------ Category 8, Topic 18 Message 137 Fri Oct 06, 1995 CBM-BANDIT at 20:57 EDT Ed, I played around with 3.02 some today and this is what I have so far: - Bootset: Not recognizing the DFLT.MYSETUP file - No problems with the Autolog (no music) except that the script to mail and BB didn't quite function properly.. It logged me on and took me straight to the BB and bypassed the mail. (I didn't have any mail at the time) Logged me off, but didn't terminate the script. Also noticed when setting up the drives, I couldn't set the target device the same as the system and source device. Was this meant to be? -Screenblanker: Seems to be disbled at the moment with the "128" command set. Oh, I'm running 3.02 from the Hard Drive, partition 34. ------------ Category 8, Topic 18 Message 138 Sat Oct 07, 1995 E.GBELL [e.g.bell] at 10:29 EDT Cam: CS> - Bootset: Not recognizing the DFLT.MYSETUP file Not sure what you mean here? Do you mean it does not come up in the directory listing? Bootset modifies this file, but does not actually read it. It just loads the one you pick and adds some settings to it that you provide through the prompts. Maybe I just don't understand what you mean. CS> script to mail and BB didn't quite function properly.. CS> It logged me on and took me straight to the BB and bypassed CS> the mail. (I didn't have any mail at the time) Logged me off Ok, which script are you using? Do you logon through sprintnet? If so, that script is just supposed to go directly to the bb, read the messages, and then say 'bye'... but it does one more thing... at the '@' prompt for sprintnet, it sends the 'hangup' command. Could this be the one you are using. It sure sounds like it. CS> when setting up the drives, I couldn't set the target device CS> the same as the system and source device. Was this meant to be No, and I'm going to go check this right now... hold on a sec... Ok, cam, I just tried what you described and here is my status line display... 01:17:07:A:C:010520:B::H:**::A:16:16:16:S:F:$***.** basically, I could not duplicate this problem. Could you give me a step by step? bTW, I don't know if you noticed, but based on what you mentioned a few months ago, I added support for partitions up to 254. So you should be able to access partition 34 now with no problem... rememeber version 3.01 could not go higher than 31. CS> Screenblanker: Seems to be disbled at the moment with the "128" Yes, it really has to. I did not understand why you had problems with this... again, this was implemented specifically at the request of you and I think sherry. bTW, I also added the chime when the greeter is off, and a way to toggle that, tho I can't remember the command right now... maybe c=5. and you can use c=z to check the current status of the function at any time... it says 'chime on/off' I believe. I *thought* I had fixed a problem that Bill Onufryk and RKIRK had mentioned with missed prompts following an autosave, but as I have been pondering the fix I mentioned, I am starting to think the 'fix' I put in won't do the trick. with all of the problems you are all having, I am kind of inclined to do another run of 3.02 to put in the fixes for this stuff.... and then to release the program piecemeal until we have all the troubles tracked down. Until then, obviously, don't release the program generally. bTW, Cam, are you using a high-speed modem? If you are using sprintnet, I can probably assume that. If so, how are things wrt losing chars? I am pretty confident I have things working well in this version... just wish I could explain all these problems. egb ------------ Category 8, Topic 18 Message 139 Sat Oct 07, 1995 E.GBELL [e.g.bell] at 10:34 EDT Eddie: I'm going to reassemble the program and send a copy of just the essential files. could you tell me what your setup is tho? as far as the settings you picked in bootset.... particularly: flow control type, break type, flow control limit (200-900), etc. also, do you have your alarm set on in the RTC when you crash? IOW, is the alarm going off to reveal your $$$ in the status line. I didn't do anything with that.... just grasping for clues. ------------ Category 8, Topic 18 Message 140 Sat Oct 07, 1995 CBM-BANDIT at 13:48 EDT Ed, CS> - Bootset: Not recognizing the DFLT.MYSETUP file EBG> Not sure what you mean here? Do you mean it does not come up in the directory listing? Bootset modifies this file, but does not actually read it. It just loads the one you pick and adds some settings to it that you provide through the prompts. Maybe I just don't understand what you mean. Ok, What I meant was, BOOTSET didn't bring up the DFLT.* file even tho it it the very 1st file in the directory. What BOOTSET saw was the directory header: hd 3d and used this as the "image mysetup" file and saved it to my HD. CS> script to mail and BB didn't quite function properly.. CS> It logged me on and took me straight to the BB and bypassed CS> the mail. (I didn't have any mail at the time) Logged me off EGB> Ok, which script are you using? Do you logon through sprintnet?Ifso, that script is just supposed to go directly to the bb, read the messages, and then say 'bye'... but it does one more thing... at the '@' prompt for sprintnet, it sends the 'hangup' command. Could this be the one you are using. It sure sounds like it. You have 3 scripts in the archives, I chose to use the scrp.mailbb. I didn't need the one for d/loading and I figured the one labled SCRP.SPRINTNET3 was for Sprint Net Access (Which I have but don't use). I have a Local GEnie node here and use that rather than go thru the excess hassles of Sprint. CS> when setting up the drives, I couldn't set the target device CS> the same as the system and source device. Was this meant to be EGB> No, and I'm going to go check this right now... hold on a sec... Ok, cam, I just tried what you described and here is my status line display... 01:17:07:A:C:010520:B::H:**::A:16:16:16:S:F:$***.** basically, I could not duplicate this problem. Could you give me a step by step? bTW, I don't know if you noticed, but based on what you mentioned a few months ago, I added support for partitions up to 254. So you should be able to access partition 34 now with no problem... rememeber version 3.01 could not go higher than 31. Where this problem occured was in the defaults overlay. I thought perhaps if I went thru this and set up my preferences 1st, BOOTSET would recognise the DFLT.* file. Wrong. System Setup - OK on both counts: 12,34 Target Setup - Dive Unit 12 Partition - This is where it hung up - I put in 34 and pressed return, I got the blinking curser in frpnt of the 4: []4 as in it wouldn't accept 34 again. Just went thru this again while typing on this machine, The Target setup was fighting me with using anything over 31 for the partition, but will accept anything from 30 and under. Same for the Alternate and now System partitions. :/ CS> Screenblanker: Seems to be disbled at the moment with the "128" EGB> Yes, it really has to. I did not understand why you had problems with this... again, this was implemented specifically at the request of you and I think sherry. Nope wasn't me, perhaps Sherry, but it's a moot point, it's there. :) As long as I can disable it, I can live with it. :) EGB> bTW, I also added the chime when the greeter is off, and a way to toggle that, tho I can't remember the command right now... maybe c=5. and you can use c=z to check the current status of the function at any time... it says 'chime on/off' I believe. Now this is something I really wanted!! :) I don't use the greeters much anymore, as my duties are more behind the scenes in the Library now and don't do much in the way of hosting. EGB> I *thought* I had fixed a problem that Bill Onufryk and RKIRK had mentioned with missed prompts following an autosave, but as I have been pondering the fix I mentioned, I am starting to think the 'fix' I put in won't do the trick. with all of the problems you are all having, I am kind of inclined to do another run of 3.02 to put in the fixes for this stuff.... and then to release the program piecemeal until we have all the troubles tracked down. Until then, obviously, don't release the program generally. I'll have to visit some place that is really busy to test the auto-save feature. This is one item I never had a problem with. In fact, I used 3.01 during the CMD conference last week, but it wasn't long enough to fill the buffer one time. EGB> bTW, Cam, are you using a high-speed modem? If you are using sprintnet, I can probably assume that. If so, how are things wrt losing chars? I have a SupraFax 9600, but the only nodes available (locally) are 2400, including the SprintNet Node. I do use the 800/9600 GEnie Line when I need to d/load files for testing. EGB> I am pretty confident I have things working well in this version... just wish I could explain all these problems. Seems kinda odd, the problems Mark and Eddie have, I don't. FWIW, this is what my system consists of: 128D w/o JiffyDos - Internal drive, 1571 (unit 8) 5MB RamLink, JiffyDos On, w/RTC - Unit 16 Switches set to Enable\Normal for Swiftlink in Pass-Thru port 512k REU in RAM Port (rarely used because of Switch settings) 1581 - Unit 9 (currently turned off) 1571 - Unit 10 (external - currently turned off) 85MB CMD HD - Unit 12 (No paralel cable attached to RL) Star Printer - Unit 4 SupraFax 9600 Modem I did have problems at one time with mice and joystickes hooked up - Currently I have a 1351 mouse in port 1 and a joystick in port 2. That covers my system. The differences in systems shouldn't cause problems what so ever, but then for some reason my system stopped letting me make .SFX files with CS-DOS and theirs does, go figure! ------------ Category 8, Topic 18 Message 141 Sat Oct 07, 1995 E.GBELL [e.g.bell] at 19:01 EDT cam: the fact that it happened in the defaults overlay was the key to finding the problem. Those routines are separate from the main program... the settings are the same ones, but the routines are different. That problem entering the devices is fixed now. Thanks! I just reassembled 3.02.... I don't have an editor so forgive the lack of quotes... what is your 'dflt.' file called. You refer to it in your message as 'image mysetup'.... was this a typo or do you have your file named that? The routines in rtcm that look for the dflt. files (and the fkey., strg., and ovrl. files) look for that prefix specifically. If bootset did not find any files, it should have aborted the operation. If your file is called 'dflt.mysetup' and bootset did not find it, that is something I'll have to figure out. If it is not named with a 'dflt.' prefix, that is something I can't fix. If it is called that, could you try it on one of your 1571s or 1581... just to see if there is something about the HD that rtcm does not handle properly. the routines to do the directory selection stuff have not changed for quite awhile. The device numbers were changed this time and that change did not ripple completely thru the defaults overlay... which is what caused the other problem... o, and see if it brings up a list of the 'dflt.' files on your drive. There is one other possibility.... if the partition was incorrect (since you could not set it for the system), rtcm would not see those files because it could not get to the partition where they are. That is also a very good suspect. I will be uploading a smaller package of 3.02 later tonight or early tomorrow... it will only be the main files, the autolog, defaults, bootset, and scriptmaker overlays. I want to get everyone at least working before I spend a lot of time doing the overlays again... they don't need the amount of changing the previous release did so all I have to do is reassemble them.... Mark: I have another suggestion.... are you using the '9600' boot I uploaded. If I uploaded that, it was a mistake... it is set to auto- answer the sl baud prompt with a 6, which is for 14.4 I believe... I tried it today w/my 2400 and it would not communicate with the modem either, so it might also be an explanation. boy I hate these kind of complete overhauls... Once I get all these wrinkles ironed out, I think you will find 3.02 is the best version yet. (hope so, tho I'm starting to wonder if I am dealing with some kind of '.02' jinx... :) ------------ Category 8, Topic 18 Message 142 Sat Oct 07, 1995 CBM-MARK at 20:12 EDT Ed, the boot file I'm using is EZ.BOOT that came with the .sfx's you uploaded for the staff. The only change I made to EZ.BOOT was to have RAMDOS as the default selection. ------------ Category 8, Topic 18 Message 143 Sat Oct 07, 1995 CBM-MARK at 21:16 EDT Ed, to recap what the problems I have with 3.02: At the point during boot up where the modem init commands are normally printed to the screen and sent to the modem, *neither* one happens. I'm unable to access the modem in any manner what so ever. Pressing the RUN/STOP key will cause RTCM to crash to a black screen and flashing cursor. RUN/STOP-RESTORE will *not* recover from this, only a computer reset works. I made sure I was using the EZ.BOOT file that came with the V3.02 upload, I was. Also made sure it was set for using my swiftlink at 2400 baud. Yes here too ;) I even ran BOOTSET and set up a new boot file. No better luck with RTCM accessing my modem through the swiftlink. Ok, now the *good* news : I'm on right now with V3.02! Pressing the RUN/STOP key does *not* cause ^-=-^. / o \ / / (@_@/-'` Horsin' Around Again??? RTCM to crash now. See that? ^^^ I had just pressed it and it sent my function key (F16) just like it was suppose to, with the text in the user window following. So how did I get RTCM to dial now, you ask? ;> I'm *not* using my modem through the swiftlink. I'm using my user port modem! Seems to me this points to a problem with the SWIFTRTS.OBJ file though how the pressing of the RUN/STOP key causes RTCM to crash is connected I don't know :/ OH, don't recall if you mentioned, but did you fix BOOTSET so that it writes "ASC" instead of "82" (think it's "82") for the ramdos, dma selection? ~~Mark~~ ------------ Category 8, Topic 18 Message 144 Sat Oct 07, 1995 CBM-MARK at 22:10 EDT OK! I got a script to dial out and connect without the music interfering. I ran the defaults overlay *again* and checked my music setting *again* ;> Same as always, the music was set to OFF. The only thing I did different this time was to save my dflt.mysetup using the C=W menu instead of through the defaults overlay. Why this would make a difference I don't know, but that was the only change that was done in the way I did things. Eddie, try that. Defining your music to OFF but save the dflt. file using the C=W menu. See if it works for you too. Course there is always the possibility I did something else but overlooked it ;> ~~Mark~~ ------------ Category 8, Topic 18 Message 145 Sat Oct 07, 1995 E.BOURDON1 [C128-Eddie] at 22:19 EDT Mark, I will give that a try. Hopefully it will work. :) Ed, I *BELIEVE* I had the flow control set to xon/off. I have the break set to the default and I used the flow control limit that you suggested ( 800 I believe). I don't have the alarm on..I will logon with RTCM and write down all the problems/defaults I have. ------------ Category 8, Topic 18 Message 146 Sat Oct 07, 1995 E.GBELL [e.g.bell] at 23:16 EDT Mark: MD> points to a problem with the SWIFTRTS.OBJ file though how the MD> pressing of the RUN/STOP key causes RTCM to crash I'm not sure about the sequence of events, but I can see how something could happen based on the run/stop key..... tho it should only happen in conjunction with the restore key. The NMI handler checks the sl as a first step.... if it is not the cart, it checks the stop key.... the assumption is that the only other thing that could cause an NMI is the restore key, and if the run\stop key is also pressed it goes thru the 'failsafe' routine..... doesn't explain the crash, but the fact that your problems disappear with the other modem hookup does point a convincing finger. MD> writes "ASC" instead of "82" (think it's "82") for the ramdos No, but then, the aSc should not be necessary if the correct code is in place. 82 is the aScII code for 'r', right?.. which you would want the variable to be set for for Ramdos. It would be 68 for dma, which is ascii for 'd'. I did test mine and it worked, but I guess I'll take another look. I only ever put the ASC in the line to make it clear what was going on for anyone who wanted to change it (until bootset) MD> without the music interfering. I ran the defaults overlay MD> *again* and checked my music setting *again* ;> Same as MD> always, the music was set to OFF Ok, when you say the music is interfering, do you mean it plays when it should not? Makes the script fail? I have it off for my GEnie scripts now but on for my DLG script.... they all work ok for me... that is what drives me NUTS! Still I think I've seen signs of what you've seen earlier on... matter of fact, I found a bug that had slipped by for a long time precisely because everyone else using sl apparently has it shut off... I was calling the routine directly in many of the overlays. that is ok for the user port routines because they are the default code assembled with the main program. the sl routines are assembled as a whole separate program using 'equ.rtcmaster' for the externals... But as you might guess, the music routine is in a different place. I have a jump address for it that I should have been using but forgot to. I never got burned cuz I use the user port and no one else did cuz you all have the music off... I found it and fixed it just as you are describing... it locked up after connecting. took a little while to figure it out too. %) MD> save my dflt.mysetup using the C=W menu instead of through the MD> defaults overlay I'll check the save routine tonight... I did some work on that part of the program I believe to make a dflt. file you loaded in defaults come up as the default file name if you save it. wonder if I trashed something! I went into autolog tonight to make sure the flag was tested properly. It is. Eddie: EB> I *BELIEVE* I had the flow control set to xon/off The version I uploaded has a bug in the xon/xoff routines. I tested the flag improperly in the autosave routine.... it never gets sent when the autosave starts.... I found and fixed it, but your setting, at least in the autosave, will not work. I would suggest also that you use the rts. Tho if you are happy, leave it alone. :) I'm going to check the defaults save routine right now. Thanks for all the feedback! ------------ Category 8, Topic 18 Message 147 Sun Oct 08, 1995 CBM-BANDIT at 00:06 EDT Commodore RoundTable Category 8, Topic 18 Message 141 Sat Oct 07, 1995 E.GBELL [e.g.bell] at 19:01 EDT Cool! glad to see the partition selection fixed :) EGB> what is your 'dflt.' file called. You refer to it in your message as 'image mysetup'.... was this a typo or do you have your file named that? I have the original DFLT.MYSETUP file as the *very* first file in partition 34 (RTCM 3.02). When I used BOOTSET, Bootset didn't "see" it. The *ONLY* thing BOOTSET saw was the partition header " HD 3D" and that is what BOOTSET wrote as my "Image (DFLT.MYSETUP) file". So now I have a file called "HD 3D" in my partition. EGB> The routines in rtcm that look for the dflt. files (and the fkey., strg., and ovrl. files) look for that prefix specifically. If bootset did not find any files, it should have aborted the operation. Ok, it did NOT abort the operation, as noted above, it only saw the partition header and took THAT to be my DFLT.MYSETUP file. EGB> If your file is called 'dflt.mysetup' and bootset did not find it, that is something I'll have to figure out. If it is not named with a 'dflt.' prefix, that is something I can't fix. If it is called that, could you try it on one of your 1571s or 1581... just to see if there is something about the HD that rtcm does not handle properly. the routines to do the directory selection stuff have not changed for quite awhile. Ok, done.. BTW, my HD partition is a 1581. I copied the files over to the 1581 drive and went thru the BOOTSET program. It did read the DFLT.* file. So I assume there is something about the directory of the HD? EGB> The device numbers were changed this time and that change did not ripple completely thru the defaults overlay... which is what caused the other problem... o, and see if it brings up a list