8bitfiles.net/archives

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

/ 8bitfiles.net/archives / archives.tar / archives / genie-commodore-file-library / Information / 02RTCMMS.SFX / 04rtcm.msgs

Wrap

Text File | 1990-02-12 | 30.8 KB | 729 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 121 Mon Jun 19, 1995 C128.JBEE at 15:42 EDT > CMD-DOUG > start every one of my DOS primitive subroutines with an LDA #0, STA $90. As far as I can tell, no. I will give it a shot with that instead, though I think at this point I will stick with the CLI if both give equal results. ------------ Category 8, Topic 18 Message 122 Mon Jun 19, 1995 C128.JBEE at 15:43 EDT > E.GBELL > I don't do anything -> erotic <- ... just standard access Oh sure, give me the old stock story why don't you! ;D ------------ Category 8, Topic 18 Message 123 Mon Jun 19, 1995 GEOS-TIM at 23:27 EDT Brenda, Just an interjection into the discussion....Congratulations you won the April Jim Brain Trivia for April...#17. BTW he will be in conference tomorrow night at 10 pm.. :) -Tim ------------ Category 8, Topic 18 Message 124 Wed Jun 21, 1995 B.GANN1 [Brenda] at 01:47 EDT GT>> Congratulations you won the April Jim Brain Trivia for April...#17. Thanks! Actually, I was a co-winner. The prize was a Toaster manual. Now all I need is the Toaster ;) (I have an Amiga 1200.) GT>> BTW he will be in conference tomorrow night at 10 pm.. :) -Tim Good conference :) Ed... Well, here we go again... I had just booted RTCM and used RTCM to post my replies with quoter. Pressed reset on the computer. (I know, we have ruled out RTCM, but thought I would include that info anyway.) Loaded TWS. Did not load a file. Typed for a while. When I tried to saved, TWS broke to the monitor with: pc: 7e0bb sc: 30 ac: 0c xr: 0c yr: 1x sr: f5 I typed x and return, the RUN. I tried to get a directory from TWS. It just said "Press Return" on blue screen like it does when you are trying to get a directory from a device that is not on the system. I noticed that the printer was off. I am starting to wonder if the problem is caused by leaving the printer off. I've only had this printer for a little while. Brenda ------------ Category 8, Topic 18 Message 125 Wed Jun 21, 1995 E.GBELL [e.g.bell] at 18:14 EDT Brenda: It seems you are consistently able to duplicate the problem. Try turning your printer on and leaving it on. If that is the problem, it is still not a problem that should exist... iow, there is nothing that should cause your system to BRK to the monitor (nothing that is not intended to do that, anyway). I still don't know what to think about that '7e0bb' tho. I don't think I've ever had anything BRK in that configuration. FWIW, your RESET will also reset all of the vectors in the 128, removing anything customized by a program like RTCM. I don't THINK that TWS uses a custom NMI handler... it might.... I still don't think a bRK to monitor is a valid response to anything tho. ------------ Category 8, Topic 18 Message 126 Thu Jun 22, 1995 E.GBELL [e.g.bell] at 06:08 EDT John: I got more info on FIDO about how you suggested to blank the screen. The explanations I got were excellent, and that what you suggest will prevent burn-in. I do have another question tho. Why bother disabling the attributes? If everything is black, it seems to me the attributes are not going to hurt anything. I only ask because when I finally get time to sit down and do this, I want to have to deal with as few bytes as possible. I won't have to do the BANK call either since the code call guarantees the proper registers and routines will be i context. ------------ Category 8, Topic 18 Message 127 Fri Jun 23, 1995 B.GANN1 [Brenda] at 02:35 EDT EB>> Brenda: It seems you are consistently able to duplicate the problem. Try turning your printer on and leaving it on. I finally got around to trying to duplicate the problem... Here is what happened. Had all equipment on except the printer. Typed. (note problem does not happen with LOAD). Save... break. Was saving as SEQ files. Tried PRG to see what would happen. Screen turned black. Run/stop-restore to get out. Turn on printer. Same results. Try to get a directory. Blue screen with "press return" as if no drive is there. Set drive to 10 (the HD). File saved. Reboot with printer on from start. Same results. Noticed in "Defaults/Misc" Text file device is set to 12! Extreme problem with getting device set properly and saved. FD error light would flash. No message that the write protect was on. Took write protect off. Still did not appear to save. Seemed to save, but when recalled the default list the device was still 12! Error light did not come on. A couple of times, the error channel read file not found (???). Solution #1: brks to monitor occur with TWS when the Text file device is set to a non-existant device. (Also note that TWS uses the wrong definitions of device and drive. A device is a number like 8 or 9. A drive is 0 or 1.) Soluntion #2: To get the Text file device to save, you MUST set the default from within TWS. It is not enough to just change it from the Customizer. I think I know why I did not see the problem before. I think I had the RL set to device #12. But I don't know why I would have saved the defaults that way. EB>> If that is the problem, it is still not a problem that should exist... iow, there is nothing that should cause your system to BRK to the monitor (nothing that is not intended to do that, anyway). Looks like its time to write to TWS' programmer :) BTW, I knew about the Customizer bug but couldn't remember what it was. EB>> I still don't know what to think about that '7e0bb' tho. I don't think I've ever had anything BRK in that configuration. Did the description of the problem help any? Brenda ------------ Category 8, Topic 18 Message 128 Fri Jun 23, 1995 H.HERMAN1 at 04:54 EDT Brenda, Is there any possibility that you might be using a Super Graphic Gold or other exotic printer interface which messes around with the serial bus? Howie ------------ Category 8, Topic 18 Message 129 Sat Jun 24, 1995 E.GBELL [e.g.bell] at 05:57 EDT Brenda: Considering the 'leg work' you have already done, I would think Eric Lee would be happy to take a look at the problem. You did all the hard work. If you DO write to him, I have a suggestion too... during searches, I suggest he change the cursor color when instances are found. I always have trouble visually locating the cursor when the scrolling stops. I never customized my TWS. I just change devices manually when I need to access a different one. What you describe really doesn't give ME any insight about why it is BRKing to that configuration. I suggest, again, that if you write to Eric Lee you ask him. If he is like me, you will probably get WAY more information than you want. ;) I will suggest one thing, tho you may have already tried it... after you tried the save of the defaults and the light flashed and it did not work, did you try sending a reset to the drive (uj or u; or u ever one works on your unit) and re-attempt the save. At any rate, nice piece of detective work! (Hey Mark... looks like you are FINALLY getting some help! haha ;) ------------ Category 8, Topic 18 Message 130 Sat Jun 24, 1995 C128.JBEE at 10:07 EDT Ed, The VDC, like most graphic chips, stores information about the screen it has to constantly redraw in RAM, not on the chip itself. Otherwise the chip would require thousands of bytes on the chip or thousands of registers. Both would be very expensive and not as flexible. The VDC in text mode has an area for character attributes. When you disable attributes you are disabling the use of the second set. This second set is what allows you to use two character sets at once for 512 characters, blinking, different colors for each character, etc. Setting the foreground/background colors only effect the next character to be displayed, the foreground changes which will be written to the attribute area. If you already have characters displayed in many different colors or operating outside the normal VDC routines, changing the background and foreground colors will do nothing, unless you disable attributes. Then the VDC will use the colors it finds in the registers globally since it thinks the attribute RAM no longer exists for it to use for enhanced displays. You could keep the attributes enabled and just change the 2,000 bytes (80x25) so the lower nibble matched the background color. Though saving the bytes before they are changed or restoring them from the defaults is messy ad probably takes much more code then the above solution. ------------ Category 8, Topic 18 Message 131 Tue Jul 04, 1995 E.BOURDON1 [C128-Eddie] at 22:01 EDT Here is a problem I've encountered with RTCM 3.01: If I load the program off my 1581 (after setting up the 'myboot' file) with nothing in the cartridge port,it loads fine. It also load fine with my RAMlink pluggd in, but not if I have the Swiftlink plugged in. And this includes if I unplug the RL and plug in the SL by itself or if I leave the SL plugged in the RL. I set up the 'myboot' file with these settings: SL at $de00, RAMlink with no RTC, font.cbm, dflt.mysetup, modem set at 14.4k, no autorun scrp. file. Here is what happens: It loads RTCM, get to the point where it is going to set the defaults ($de and 14.4 ) to the screen, it seems to do a reboot of the computer, but the RTCM screen stays, the start up message is displayed in the main window (the Commodore 128 BASIC screen), then it prints a '2' and a '5' right below the start up screen. This only happens when my Swiftlink is plugged in. If I remove the SL I can boot the program fine, I just can't use my modem then ;) Any clues as to the fix for this? Also, I have not physically changed the address of my SL, it is at it's default address. ------------ Category 8, Topic 18 Message 132 Wed Jul 05, 1995 C128.JBEE at 00:47 EDT Eddie, Do you have a modem or interface plugged into the user port in addition to the expansion port? ------------ Category 8, Topic 18 Message 133 Wed Jul 05, 1995 CBM-MARK at 00:53 EDT I didn't try removing my SL so all the farther I got with a bootup of V3.01 was just after the prompt for RAMDOS/DMA. Locked up the keyboard on me. JBEE, I've always ahd a modem plugged into the user port along with the SL in the cartridge port. Always worked fine before. ~~Mark~~ ------------ Category 8, Topic 18 Message 134 Wed Jul 05, 1995 E.BOURDON1 [C128-Eddie] at 01:05 EDT Jbee, I don't have anything in the userport. The only other drive I have hooked up (besides the RL) is a 1581 drive. I have only encountered this problem on the latest version. ------------ Category 8, Topic 18 Message 135 Wed Jul 05, 1995 CBM-MARK at 01:30 EDT Ed, some more on this ... I had been selecting RAMDOS and it was right after pressing RETURN that everything locked up. I just tried selecting DMA and had pretty much the same results as Eddie. The only difference being I had a '2' and '3' printed to the screen when it 'reset'. These numbers seem to coincide with the dynamic keyboard entry of the SL address and baud rate. I use the default of $de00 for the SL at 2400 baud. Eddie used $de00 also but a higher baud rate, hence his '5'. It was hard to tell, but I think I counted 5 files loaded after I selected DMA and 512k. If right, this would mean RTCMZK was loaded and pow! ~~Mark~~ ------------ Category 8, Topic 18 Message 136 Wed Jul 05, 1995 E.GBELL [e.g.bell] at 06:18 EDT Ok! I'll be checking into things the rest of this week. This version does have changes to both of the NMI handlers. I'm going to plug my SL and my REU in (not at the same time tho) and try to duplicate your results. With everyone having the problems, I am pretty sure I'll be able to duplicate them. Thanks for the quick responses! BTW, Eddie, other than this, when it did work for you, did it do better with your RL? That may be a premature question, but that is the problem I aggressively went after this time. I suspect the problems you are having now are something I've introduced that your setups (i.e. REU and SwiftLink) burp on that I did not use when testing. I'm going to do that now. Again, thanks for the quick response! ------------ Category 8, Topic 18 Message 137 Wed Jul 05, 1995 E.GBELL [e.g.bell] at 18:11 EDT Can I ask you both to do one thing in the meantime... try booting it without the REU. I was hoping that I had overwritten the interface page, tho your test w/DMA should have tested that Mark. I am pretty sure that the problem is with the SwiftLink module... I hope it is that I overstepped a memory boundary... My code is pretty well crammed in there. One way or the other, I expect to find it this weekend. Sure would like to know, tho, if I crushed the problem with the RamLink tho! ------------ Category 8, Topic 18 Message 138 Wed Jul 05, 1995 E.GBELL [e.g.bell] at 19:11 EDT the SL module seems to have gotten corrupted somehow. I reassembled it and am using it now. I didn't make any changes... just reassembled it. It broke for me too... go figure. Give it a try now... we can move on to the tests I'm REALLY trying to make. hehe ------------ Category 8, Topic 18 Message 139 Thu Jul 06, 1995 CBM-MARK at 00:37 EDT Ed I noticed you didn't include a boot prg for using the 1670. Oversight or isn't it needed anymore? ~~Mark~~ ------------ Category 8, Topic 18 Message 140 Thu Jul 06, 1995 CBM-MARK at 00:59 EDT Ed, you have partial success! I'm online with 3.01 right now. However, if I select RAMDOS, everthing locks up. Haven't had a break to the monitor since that first time, just locks up so I have to reset. Selecting DMA for the REU is what got me online. Can't unplug my REU because I've wired it together with the SL ;> This is the 2nd time I wished I hadn't done that. The lock up happens immediately after the RAMDOS selection. ~~Mark~~ ------------ 8 | ************ 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 141 Thu Jul 06, 1995 CBM-MARK at 01:11 EDT I hate to do this to you Ed but ther is another problem. The HELP key doesn't call up the help screen. just prints "help" to the screen. Also, none of the CMDR- hotkeys work. Least I couldn't find one. All they do is either send one of the fkeys (higher than #8), send a carriage return, or print some character. o ^ - above was what I got for C= W (an 'oh') ~~Mark~~ ------------ Category 8, Topic 18 Message 142 Thu Jul 06, 1995 E.GBELL [e.g.bell] at 06:04 EDT Ok! The cable went out last night so I had a few minutes. I walk from 3 to 5 miles after work and go to bed at 8:30 so I don't have a lot of time in the evenings *and don't feel much like doing anything with the time I have* so this will all have to wait until tomorrow night and the weekend. I'll try to duplicate everything you just described Mark... This is the kind of stuff I dread!!! go in to make some minor changes to the whole program and get bombed with a host of little stuff. arrrrggggghhhh! ------------ Category 8, Topic 18 Message 143 Thu Jul 06, 1995 E.GBELL [e.g.bell] at 18:11 EDT Ok, I think I found and fixed everything. There were two separate problems. The swiftlink thing was probably cause by the way I assembled this version. I think you'll find it works ok now and all the effects Mark experienced are gone. I was immediately able to duplicate them so I know they are fixed. The REU thing was a problem with the code changes made to 3.01... or more accurately, a problem with the install module not taking those changes into account. An address was called that used to be an equate but which became an external label with version 3.01. The net effect was that ramdos never got loaded which is why the BRK. That has been corrected with the intent of the changes to 3.01 preserved. I also tested this and was able to duplicate it, which is how I know it is fixed. Sorry and thanks for the quick reports. With a program this size, I'd never be able to test my work in a timely fashion with all the different possible configurations w/o the help provided. Again, thanks. The file fix is only about 3K. It is in the library now. ------------ Category 8, Topic 18 Message 144 Fri Jul 07, 1995 CBM-MARK at 00:28 EDT Nice work Ed! What I've tried so far has worked fine ;D Oh, ah, dumb question of mine about a 1670 boot. I forgot about BOOTSET :> ~~Mark~~ ------------ Category 8, Topic 18 Message 145 Fri Jul 07, 1995 E.GBELL [e.g.bell] at 05:12 EDT I forgot about BOOTSET too until last night... and then I forgot to tell you, but you remembered anyway. ;) I think that I nailed the troubles last night. I do like it when I locate a problem that is obviously the problem! ------------ Category 8, Topic 18 Message 146 Sat Jul 08, 1995 E.GBELL [e.g.bell] at 06:06 EDT Mark: Got the disk w/the files you had problems with. I tested it w/ 3.01 from the 1581 to the ramlink and the 1581 to the 1581 with my setup, meaning no SL and no REU. It worked fine both times. So I figured I'd try with the sL and REU so I popped in my Aprospand and tried again. Worked again just fine. Finally, I figured I'd try to duplicate your results with 3.00, which is the version you had the problem with, because there were some changes made to the 3.01 version. I tried it from the 1581 to the 1581 with a configuration like yours and it worked fine again. I archived 5 files maching the pattern '??soft*' in all of my tests. Do you still have a copy of the files which you can try with 3.01? I'll send the disk back. I'm sure it is not a problem with the disk cuz I used your disk, both as source and target. ------------ Category 8, Topic 18 Message 147 Sat Jul 08, 1995 CBM-MARK at 21:42 EDT Ed, don't bother sending the disk back. I just made a comment in email to you about ARCHIVER before I came over here ;) V3.01 doesn't give me any problems like V3.00 did. The files I have here still won't archive with V3.00 but *will* with V3.01. I originally had even gotten another copy of everything, thinking it may have been something about the download, but that wasn't the answer. Whatever the answer is, V3.01 works ;D ~~Mark~~ ------------ Category 8, Topic 18 Message 148 Sat Jul 08, 1995 E.GBELL [e.g.bell] at 22:07 EDT That is some good news. I was not too enthusiastic about poking around in that overlay. I have a rough understanding of some of the ARc stuff, but not deep. The fact that it was with disk stuff narrowed the scope. Now if I just hear the RL stuff is over1 ------------ Category 8, Topic 18 Message 149 Sun Jul 09, 1995 E.GBELL [e.g.bell] at 11:08 EDT Mark: I am uploading the set of files we have been working on. I had to make some changes to the DOS section of the code and also move the staging buffer back 2k.... the latter *may* have been unnecessary but I wanted to make sure on the basis of something I saw today. Whenever you can, drop the .3 file in my mailbox if it is ready. I'm anxious to see what you have. I included the .equ and equates files for 3.01 in case you don't have them yet. can't remember if I sent them. ------------ Category 8, Topic 18 Message 150 Mon Jul 10, 1995 CBM-MARK at 23:16 EDT Ed, you updated them again? I just got done putting the whole thing out in hard copy so I could look it over better! ;D Good thing I did. I noticed I set up two address tables that I didn't see you already had set up. Be easy enough to remove though. I'll send you what I have so far. It works pretty good if I do say so myself ;> ~~Mark~~ ------------ Category 8, Topic 18 Message 151 Mon Jul 10, 1995 CBM-MARK at 23:31 EDT Ed, just downloaded that file and noticed that some time during the download, the info "Bytes [#]:------" changed to Bytes [#0:------". The right bracket changed to a zero. Soon as the download was done and the proccess terminated, that zero changed back to a right bracket -[f] ------------ Category 8, Topic 18 Message 152 Tue Jul 11, 1995 E.GBELL [e.g.bell] at 05:59 EDT Mark: The bytes display onscreen during transfers, copies,etc. is wedged into the system interrupt. What you are describing SHOULD be impossible, but I guess something could have happened at JUST the right time to move the display over one byte. I trap for things going to the VDC at the start of the IRQ handler and exit if it is printing there at that time. However, that is just a display routine so it is not a big deal. The zero changed back at the end because it probably got repainted. the changes I made were minor. One was that if you load a file, that file now comes up in the prompt so that you can save it w/o having to retype it. I forget the other/s. Like I said tho, they were minor, and only involved SCRIPT.DOS. I changed .0 too to reflect the new date. But if you want to print the stuff out you can concentrate on the .DOS file. ------------ Category 8, Topic 18 Message 153 Tue Jul 11, 1995 E.GBELL [e.g.bell] at 18:05 EDT Mark: Nice work on the .3 files. One thing... the first character in my telephone number is missing. Otherwise, it printed everything I sent at. Looking forward to the verbose part... do you have stuff in mind. I kind of tnink you are going to find that as easy, if not easier than, what you already did.... more work but easier.... :) ------------ Category 8, Topic 18 Message 154 Tue Jul 11, 1995 CBM-MARK at 22:15 EDT Ed, the first charaxcter of youtr telephone number was missing? I wonder why because I used one of your scripts from the RTCM package. What I get for your phone number is "572-7320^" *IF* the compiled BASIC version of Script Maker is used to write a script and *IF* an AM start time is defined, this version of SM will mess up printing out the script. It's caused by a bug in the BASIC version. Found out it doesn't do AM times right. Oh, wait! You didn't by chance have a start time specified in your script that was in the format of HH:MM:SS (with the colons)? I realized the other day that a time format with the colons will mess things up in the print out. I have the recoding done on paper but haven't made the changs yet. I do have something in mind for the verbose part. Some of it on paper but that's as far as I've gotten so far. =As far as getting easier, the more I had worked on it, the easier it got. This part should go pretty good ;) ~~Mark~~ ------------ Category 8, Topic 18 Message 155 Wed Jul 12, 1995 C128.JBEE at 04:57 EDT According to the doc file, with the new ez.boot all I have to do is change line 20 to "u=10" and press return and it is automatically saved to disk. But the next time I load the file, U still equals 8. Plus, when the program is first run it still defaults to unit 8 for the overlays even when the first line is changed to unit 10. Is this the way it is suppose to run or did I misunderstand the newer docs? ------------ Category 8, Topic 18 Message 156 Wed Jul 12, 1995 E.GBELL [e.g.bell] at 06:15 EDT MD> first charaxcter of youtr telephone number was missing Yes, in every instance I tested, the first digit is not there... I get.... '72-7320^'. This is the only field affected... and no, I don't have any presently with the time set in the number. MD> *IF* the compiled BASIC version of Script Maker is used to MD> write a script and *IF* an AM start time is defined, this MD> version of SM will mess up printing out the script Don't understand this at all... what you mean, that is. MD> As far as getting easier, the more I had worked on it, the MD> easier it got That is the way it always works for me.... otherwise some of the big progs I've written would have gotten canned early on. The one I'm working on now is a collection of monster parts... very difficult. I'm kind of figuring it out/planning it as I go along. JB> with the new ez.boot all I have to do is change line 20 to JB> "u=10" and press return and it is automatically saved to disk. That has been the case going back as far as I can remember John. Line 20 starts out with the line number, obviously, followed by a 'REM' statement, a quotation mark, and several deletes. Then, when you list the line, it leaves only the executable onscreen. When you change this line, you are doing so in immediate mode only, not in program mode. Otherwise, it would not save the prog when you press RETURN. I went to this technique in both my bASIC and ML code years ago after getting tired of saving the current file to the wrong file on disk. This method totally protects against that. And you are right... the program line does not change. JB> when the program is first run it still defaults to unit 8 for JB> the overlays even when the first line is changed to unit 10 Yes. This has come up before. Guess I didn't explain it well enough. The device number in line 20 has nothing to do with anything but the boot program. It is only there for the reason mentioned in the previous paragraph. When RTCM boots, it will use whatever unit you boot from as the source drive. It does not save the source device anywhere for this reason. This is a protection against problems that would inevitably result if I saved a copy of the source drive. Even saving the system device causes me problems here if I boot RTCM with the RL unplugged. That is because device 16 is not present. It boots fine because of the way I use the source for boot operations instead of the system device. but if I try to access the default system device later, it burps because it is not there. Now, here is something that the new docs do explain about that number in line 20, in the BOOTSET section. If you run BOOTSET to create your custom boot program, line 20 will automatically be set to whatever your SOURCE device is set to at the time. Again, this is just a convenience feature that saves you the steps of typing in the commands to resave the file. Line 20 does not affect the settings in RTcm in any way. If it matches your settings, that is coincidence. Finally, if you want to force the boot to happen from a differnt drive, you *could* add a line that says 'POKE 186,<device number>'. RTCMaster will always load all of the system files from the drive specified in address 186, which is usually the drive from which you loaded the boot program. O, and I have high hopes that BOOTSET will make setup painless as it steps you through the process, asking about 10 or 15 questions, and creates a program called 'MY.BOOT' complete with all the adjustments you specified. It also modifies your 'dflt.mysetup' and any script you specify. And there is a new overlay on the way. ------------ Category 8, Topic 18 Message 157 Wed Jul 12, 1995 C128.JBEE at 12:18 EDT The screen blanker works fine now. The file copier does not break to ROM now, I have not tried the other overlays. Flow control does not work properly no matter what I set my modem to. When RTCM first boots and you answer "n" to running an overlay, why does RTCM access the disk drive? What does it load? ------------ Category 8, Topic 18 Message 158 Wed Jul 12, 1995 E.GBELL [e.g.bell] at 18:51 EDT John: JB> The screen blanker works fine now. I have my concerns about this, but if it works for you, good. I had it create a flashing row of pixels up the right side of my screen last week, but it only happened once so who knows. JB> file copier does not break to ROM now, I have not tried the JB> other overlays. That was one of the ones people mentioned. Ymodem was the other, but you never mentioned having that problem. JB> Flow control does not work properly no matter what I set my JB> modem to Can't explain this, but the only time flow control is EVER used is just before an auto-save... so if you are expecting it at other times, it is never going to meet your expectations. I know it works then because both Mark and I have verified that. I don't have a high speed modem and therefore can't claim to support them. Perhaps in the future I'll investigate rts/cts, but it is not high on my priority list. JB> When RTCM first boots and you answer "n" to running an JB> overlay, why does RTCM access the disk drive? What does it JB> load? I'd have to dig, but I *think* what that is is a drive initialization. The reason was that when I first instituted auto-executing scripts, it was found that if a script was not on the boot disk, the drive light was left flashing, which caused more questions than the drive init would and the drive init stopped the light from flashing. I have to check to see if there is anything else that RTCM does at that point. ------------ Category 8, Topic 18 Message 159 Wed Jul 12, 1995 CBM-MARK at 22:56 EDT Ed, for some time now I've been defining a source drive from within the boot program that is *not* the boot drive. I use my #8 drive to boot up RTCM but have my source defined as #9. Added just one line to EZ.BOOT that poke DRIVE with the source drive I want. Don't have aprintout of EZ.BOOT handy right now but I think I put that line in after the prompt for a script file. I'll check on that missing char from the phone number. Can't imagine waht happened. It was working ;> I noticed what John saw too about RTCM loading something after answering "n" to a script. Seems to be more than just a drive init. This wouldn't be where you're loading the PATH. file is it? ~~Mark~~ ------------ Category 8, Topic 18 Message 160 Wed Jul 12, 1995 C128.JBEE at 23:16 EDT With the older versions of the overlays none of them worked properly while accessing my RamLink. I just picked the file copier overlay because it was easier to document every small step. ------------ 8 |