CBBS(R) 4.0.3a 06/12/89 20:53:02 Y/N: want CBBS "1st time user" info?^U ?^U ?^U ?n;ward;christensen;odraw;;fullc;piss Logging name to disk... You are caller 206305; next msg =41940; 463 active msgs. Prev. call 06/11/89 @ 23:39, next msg was 41935 Recording logon for next time. Use FULL? to check assignments ?^U ?xxxxx "Mine" command checking for msgs TO you, ^K to abort. >Function:?dir c:log;dir c:killed;dir summary;type-30 log,ward c;or;*;short LOG. 13 KILLED. 102 SUMMARY. 30 06/11/89,23:39:13,206278,9,WARD CHRISTENSEN,,4 06/12/89,00:57:58,206279,1,DANNY VAISRUB,,1 06/12/89,01:10:41,206280,3,DAVID RECKLES,ARLINGTON HIEGHTS,15 06/12/89,02:43:56,206281,2,ERIC BOHLMAN,,1 06/12/89,02:52:02,206282,2,JIM MORAVEC,,3 06/12/89,03:33:25,206283,2,JERRY OLSEN,, E#41935,20 06/12/89,05:34:47,206284,2,PETE JONES,,2 06/12/89,05:50:52,206285,1,DAVID SUGAR,,8 06/12/89,06:53:41,206286,2,DENNIS STAHL,,7 06/12/89,07:26:01,206287,1,JOEL WHITE,Oakbrook Terr. IL,6 06/12/89,08:46:58,206288,1,GARY MCCOY,,1 06/12/89,09:58:53,206289,1,ANDY SHAPIRO,, ]>> got Flash<< E#41936, E#41937,18 06/12/89,10:42:58,206290,1,ROBERT SMITH,8X~, >Help: S?,14 ]ROBERT SMITH, 06/12/89,11:18:55,206291,2,MARTY LINGG,,1 06/12/89,12:27:38,206292,1,TC SCHUSTER,WINNETKA, 06/12/89,12:41:58,206293,1,DOUGLAS ATLAS,Lincolnshire/ IL,20 06/12/89,13:07:55,206294,1,FAISAL FAROOQI,SKOKIE/IL,4 06/12/89,13:19:58,206295,1,ALLEN GOLLUB,Oak Brook/ IL,4 06/12/89,13:45:38,206296,1,COLIN SCHROEDER,,10 06/12/89,14:12:01,206297,1,JOHN MUNDT,,4 06/12/89,14:40:22,206298,2,STEVE COOK,,1 06/12/89,14:48:49,206299,1,MARK SHELL,Knoxville/ TN, E#41938,14 06/12/89,16:29:03,206300,2,JAMES SCHMIDT,,3 06/12/89,16:43:33,206301,9,MIKE ANDREWS,,8 06/12/89,17:51:30,206302,2,JOSEPH SKOM,, E#41939,4 06/12/89,19:51:26,20603,2,ALLEN PETLOCK,,3 06/12/89,20:08:05,206304,2,SCOTT PAKIN,,14 06/12/89,20:53:06,206305,9,WARD CHRISTENSEN,, 41935 06/12/89 JERRY OLSEN => JIM JOYCE: "R/BOOT-UP PROBLEM" 41936 06/12/89 ANDY SHAPIRO => WARD CHRISTENSEN: "R/EXPERIENCE W/SUN?" 41937 06/12/89 ANDY SHAPIRO => WARD: "YER LAPTOP" 41938 06/12/89 MARK SHELL => WARD CHRISTENSEN: "XMODEM PROTOCOL" 41939 06/12/89 JOSEPH SKOM => ALL: "NEED HELP WITH MIDI" - End of summary - Retrieving flagged msgs: C skips, K aborts. Msg 41935 is 20 line(s) on 06/12/89 from JERRY OLSEN to JIM JOYCE re: R/BOOT-UP PROBLEM You've received quite some replies! . I had a similar problem early on when attempting to upgrade my DOS. My immediate reaction was the same as yours: Copying the two "hidden" files and COMMAND.COM onto C:. But this can royally muck things up. Problem is, the hidden files must be the FIRST two files placed on the HD or they'll never be found. At this point, there's a good chance your friend will have to back up all files, then erase all files on the HD, and finally copy them back in EXACTLY the right order (IO.SYS before MSDOS.SYS if your friend is running MS-DOS, else the equivalent files). It's best to use the SYS command to do this to ensure all is automatically done corretly.If THAT doesn't solve it, it could be a drive (or controller or cable) problem. I've also had a HD which just became too slow to boot in a sufficiently timely way, so the operating system considered it "unavailable" at boot time, but available a few seconds later-which would yield the same symptoms. Finally, I've had a cable which was just loose enough to result in the same thing. So, if SYSing (you might as well reformat before that with the procedures others have outlined for safe measure in case something became trashed, and to eliminate more variables), then I'd suggest swapping one item at a time-cable, HD, and controller board-to see which is the source of the problem. (Of course, ensure all swapped parts are compatible with each other!) Good luck. Msg 41936 is 16 line(s) on 06/12/89 from ANDY SHAPIRO to WARD CHRISTENSEN re: R/EXPERIENCE W/SUN? Thanks for the info. Actually, an IBM person gave me some literature about a new Micropolis drive that runs 1.2 GBytes! Anyway, the problem with the RT that we looked at was that, as I recall now, you had to partition the UNIX file system into 'minidisks,' so the largest single file you could have could not exceed a minidisk in size - and since the largest stcck drive was 320M, that wasn't big enough (complain, complain). Anyway, I probably won't contack Randy, since I'm only going to be in Chicago for another 10 days (actually leave on the 28th, but I'm spending a week in Utah first). . I also wanted to thank you for all the help and entertainment over the years. I first logged onto CBBS more than five years ago, so I have some feeling for the critter. I've got a great deal of good advice over the years. I hope that you manage to keep this board functioning for a loooong time.! Msg 41937 is 08 line(s) on 06/12/89 from ANDY SHAPIRO to WARD re: YER LAPTOP Try VDE as a text editor. Limits you to 64K or so files, but it's small and fast. For text handling, there's always ROFF4. Both of these programs started out in CP/M, but MS-DOS versions are available. I'd never heard of the hardram, but it sounds like a real good idea. I use a little CP/M laptop (Epson Geneva) and it's slow, but with TINY CP/M programs. loading is quick. I use a version of VDE that's around 11K, no text formatter, though, as I don't output to a printer from the laptop. Check out VDE anyway - great little editor! Msg 41938 is 04 line(s) on 06/12/89 from MARK SHELL t WARD CHRISTENSEN re: XMODEM PROTOCOL I need a discription of the XMODEM protocol so that I can use it in a data acquisition system that I am working on. Is the protocol public domain? Does such a description exist? Please call me (Mark Shell) at 1-800-635-2699 or leave a message. Thanks! Msg 41939 is 09 line(s) on 06/12/89 from JOSEPH SKOM to ALL re: NEED HELP WITH MIDI I recently purchased a MIDIator interface for my PS/2 and Rolland S-10 Synth. I encountered a problem when sending multiple sequencer tracks to the S-10 during playback of a song. The problem is that some notes cut others off. I ran the Midi Monitor program and traced the problem to the fact that the S-10 sends an "all-notes-off" command whenever all the notes are released. Apparently, the sequencer records this command and sends it back to the synth; this causes all notes to be turned off at that instant, regardless of what "track" they came from. Is there any way to defeat the sending of the "all-notes-off" code? dup. chars. >Function:? >Function:? >Function:? >Function:?# Next caller 206306; next msg =41940; 463 active msgs. *=41935 (hi msg last call) #1=41935 #2=41936 #3=41937 #4=41938 #5=41939 >Function:?