On 2017-08-04, at 3:08 PM, [email protected] wrote: > Send M100 mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of M100 digest..." > > > Today's Topics: > > 1. Re: Gopher (Ray Lopez) > 2. DVI (Jan Vanden Bossche) > 3. 102 screwed up. (Ted MacGillivray) > 4. Re: 102 screwed up. (Josh Malone) > 5. Re: 102 screwed up. (John R. Hogerhuis) > 6. Re: 102 screwed up. (Stephen Adolph) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 3 Aug 2017 17:23:46 -0500 > From: Ray Lopez <[email protected]> > To: [email protected] > Subject: Re: [M100] Gopher > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > The world famous Kim Holviala! I guess I shouldn't be surprised to find > a fellow gopher enthusiast on the M100 list! :-) > > Kim Holviala is the creator of Gophernicus, probably the best gopher > server around. I am running my gopher site on Motsognir, another recent > gopher server, but am thinking about switching over to Gophernicus at > some point. > > Check out our respective gopher sites via proxy: > > Ray: http://ratthing.com:7780/ratthing.com/1/ > Kim: http://ratthing.com:7780/gophernicus.org/1/ > > RL > > > ------------------------------ > > Message: 2 > Date: Fri, 4 Aug 2017 18:17:17 +0000 (UTC) > From: Jan Vanden Bossche <[email protected]> > To: "[email protected]" <[email protected]> > Subject: [M100] DVI > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > [-I know I've asked this question before, but apparently, I can't see my own > postings from my yahoo mailbox to the list, don't know why, yet. Anyway, this > question is just as much a test as a genuine question.-] > Is there somewhere a description of how the DVI interface works, and what > signals (type & speed) come out (and where) of the Model T ? And how they > have to be interpreted ?Did you need to load any software on the T to make it > work, or was a simple screen 1,0 enough ? > Is there a general description of the workings of a DVI, somewhere ? > > I'm thinking about contacting a friend with electronics knowledge to > replicate a DVI with a Raspberry Pi as base. If only, the video output. > Greetings from the TyRannoSaurus > Jan-80 > #yiv0578448067 #yiv0578448067 -- P > {margin-top:0;margin-bottom:0;}#yiv0578448067 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.bitchin100.com/private.cgi/m100-bitchin100.com/attachments/20170804/a378bf84/attachment.html> > > ------------------------------ > > Message: 3 > Date: Fri, 4 Aug 2017 11:23:07 -0700 > From: Ted MacGillivray <[email protected]> > To: [email protected] > Cc: Ted MacGillivray <[email protected]> > Subject: [M100] 102 screwed up. > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > > Hi, > > I've had a 102 for about ten years, added a REX (version 1) and used it > mainly as a portable word processor. It recently screwed up while printing > out files stored on the Rex. Just stopped -- I forget what the message > was--it was meaningless to me. The 102 still works, sortof, does not > recognize the Rex, and CALL63012 doesn't call REXMGR.BA. TELCOM, ADDRSS and > SCHEDL have disppeared or don't work. I've tried reinstalling the Rex, but no > luck. > > Without additonal storage, my 102 is no longer useful as a WP, so my question > is : Is there anyone actually manning CLUB100? I'm not looking for > something-for-nothing, so is anyone available as a Professional who might be > able to help me? > > Thank you, > and Pleasedtomeetya, > Ted MacGillivray.
Hi Josh, John and Stephen' with many thanks for your replies: Basic seems to work in that I "Killed" a test file with it ---, but first I hard-started the 102 and got the usual menu, then Killed the text file to see if it deleted it. It did. Rexmgr.BA wasn't on the menu. I hard-booted again and then, in Basic, I Call(ed)63012, but nothing happened. I had removed the Rex and its balsa, cleaned the contacts and put it back, so I'm assuming the Rex had gone bad. Free memory reads 29565. I'm concerned that while TELCOM, SCHEDL and ADDRSS appear on the menu, trying to load them draws blanks --- i.e., I'll need to (somehow) reload DOS, so even if I can get a new Rex I won't have solved the problems. I'm more a technologist that a technician and though I started in computers back in '82 with CP/M etc, I'm not a programmer and am a bit out of my depth. Thank you, gentlemen, I'm grateful for your comments. Ted. > , With many thanks for your replies > Message: 4 > Date: Fri, 4 Aug 2017 14:48:41 -0400 > From: Josh Malone <[email protected]> > To: [email protected] > Subject: Re: [M100] 102 screwed up. > Message-ID: > <CAB==woojxoeu874bpusnmbe6pwgaoym6yqfedw3x39jee8t...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > does basic still work? > > How much free memory is reported? > > It sounds like you had some sort of not-completely-cold start. Have you > done a cold-start on it? > > On Fri, Aug 4, 2017 at 2:23 PM, Ted MacGillivray <[email protected]> wrote: > >> >> Hi, >> >> I've had a 102 for about ten years, added a REX (version 1) and used it >> mainly as a portable word processor. It recently screwed up while printing >> out files stored on the Rex. Just stopped -- I forget what the message >> was--it was meaningless to me. The 102 still works, sortof, does not >> recognize the Rex, and CALL63012 doesn't call REXMGR.BA. TELCOM, ADDRSS >> and SCHEDL have disppeared or don't work. I've tried reinstalling the Rex, >> but no luck. >> >> Without additonal storage, my 102 is no longer useful as a WP, so my >> question is : Is there anyone actually manning CLUB100? I'm not looking >> for something-for-nothing, so is anyone available as a Professional who >> might be able to help me? >> >> Thank you, >> and Pleasedtomeetya, >> Ted MacGillivray. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.bitchin100.com/private.cgi/m100-bitchin100.com/attachments/20170804/92fc1e6c/attachment-0001.htm> > > ------------------------------ > > Message: 5 > Date: Fri, 4 Aug 2017 11:50:55 -0700 > From: "John R. Hogerhuis" <[email protected]> > To: [email protected] > Subject: Re: [M100] 102 screwed up. > Message-ID: > <cacutkugjo_w2kqqheakkwbjvi1gkynmntqgwx6nukymwpdm...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Fri, Aug 4, 2017 at 11:23 AM, Ted MacGillivray <[email protected]> > wrote: > >> >> Hi, >> >> I've had a 102 for about ten years, added a REX (version 1) and used it >> mainly as a portable word processor. It recently screwed up while printing >> out files stored on the Rex. Just stopped -- I forget what the message >> was--it was meaningless to me. The 102 still works, sortof, does not >> recognize the Rex, and CALL63012 doesn't call REXMGR.BA. TELCOM, ADDRSS >> and SCHEDL have disppeared or don't work. I've tried reinstalling the Rex, >> but no luck. >> >> > It would help to know exactly what you attempted to do as far as > "reinstalling REX" > > First, it needs to make good contact with the pins in the Option ROM bay. > Second, you need to cold start and get REXMGR reinstalled. > > I'm guessing that REX is not making good contact to the pins. > > -- John. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.bitchin100.com/private.cgi/m100-bitchin100.com/attachments/20170804/8cd18206/attachment-0001.htm> > > ------------------------------ > > Message: 6 > Date: Fri, 4 Aug 2017 17:12:31 -0400 > From: Stephen Adolph <[email protected]> > To: [email protected] > Subject: Re: [M100] 102 screwed up. > Message-ID: > <CAMCMnV5G3wTcraoecsvS+ukUZHBYc4Y83t4kNoOZFv=mrvv...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > this sort of thing often indicates that the REX firmware (either the > software or the directory structure) is corrupted and needs to be > reloaded. an unfortunate side effect is that the directory structure > gets rewritten which in effect wipes out the stored data. > > There are some ways to recover your data however if it is really important. > > ..Steve > > > > On Fri, Aug 4, 2017 at 2:50 PM, John R. Hogerhuis <[email protected]> wrote: >> >> >> On Fri, Aug 4, 2017 at 11:23 AM, Ted MacGillivray <[email protected]> >> wrote: >>> >>> >>> Hi, >>> >>> I've had a 102 for about ten years, added a REX (version 1) and used it >>> mainly as a portable word processor. It recently screwed up while printing >>> out files stored on the Rex. Just stopped -- I forget what the message >>> was--it was meaningless to me. The 102 still works, sortof, does not >>> recognize the Rex, and CALL63012 doesn't call REXMGR.BA. TELCOM, ADDRSS and >>> SCHEDL have disppeared or don't work. I've tried reinstalling the Rex, but >>> no luck. >>> >> >> It would help to know exactly what you attempted to do as far as >> "reinstalling REX" >> >> First, it needs to make good contact with the pins in the Option ROM bay. >> Second, you need to cold start and get REXMGR reinstalled. >> >> I'm guessing that REX is not making good contact to the pins. >> >> -- John. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > M100 mailing list > [email protected] > http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com > > > ------------------------------ > > End of M100 Digest, Vol 80, Issue 4 > ***********************************
