Hi David, Is it possible for you to acquire a DIAL-A-ROM? Your capabilities would vastly improve with even just the default images that Jeff Birt loads into the DAR device since it already includes the latest SARDOS which includes the CIRCLE() routine. I think they cost about $16 USD plus shipping, but admittedly I don't know if Jeff ships internationally.
Gary On Sat, Oct 24, 2026 at 11:25 AM David Szasz <[email protected]> wrote: > Gary: > > I don't doubt your algorithm is much faster. I'd load your ROM if I had a > burner and appropriate chip. > > On closer examination I rewrote it to just be all integers in BASIC. It's > pretty fast under those circumstances. but still a "one-trick" pony. > > 10 CLS:XC%=120:YC%=63 > 20 READ X1%,Y1% > 30 FOR I%=1 TO 24 > 40 READ X2%,Y2% > 50 LINE (XC%+X1%,YC%+Y1%)-(XC%+X2%,YC%+Y2%) > 60 X1%=X2%:Y1%=Y2%:NEXT I% > 70 END > 100 DATA 63,0, 61,16, 55,31, 45,45, 32,55, 16,61, 0,63 > 110 DATA -16,61, -31,55, -45,45, -55,32, -61,16, -63,0 > 120 DATA -61,-16, -55,-31, -45,-45, -32,-55, -16,-61, 0,-63 > 130 DATA 16,-61, 31,-55, 45,-45, 55,-32, 61,-16, 63,0 > > This one would only run on a m200. But if you change lines 10, 30 and the > data you could probably draw anything on any Model-T. > Thanks -Dave > > On Sat, Oct 24, 2026 at 12:00 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/m100 >> 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. Anyone used Model 100 or 200 in MAME? (John R. Hogerhuis) >> 2. Re: Drawing The Largest Circle or Polygon on a Model-T Screen >> (Gary Weber) >> 3. Re: Drawing The Largest Circle or Polygon on a Model-T Screen >> (Gary Weber) >> 4. Re: Anyone used Model 100 or 200 in MAME? (B9) >> 5. Tandy 200 Restoration - need LCD ([email protected]) >> 6. Re: Anyone used Model 100 or 200 in MAME? (Douglas Quagliana) >> 7. Re: NEC 8201A Technical Reference manual (Mike Hyde) >> 8. Re: NEC 8201A Technical Reference manual (Mike Hyde) >> 9. NEC-PC8300 - TELCOM Stat (Georg K?ter) >> 10. Re: NEC-PC8300 - TELCOM Stat (Gary Weber) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 23 Oct 2026 13:13:13 -0700 >> From: "John R. Hogerhuis" <[email protected]> >> To: [email protected] >> Subject: [M100] Anyone used Model 100 or 200 in MAME? >> Message-ID: >> <CACutKUg7_1V2HTa0_WZ= >> [email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> Found out on Facebook that MAME emulator supports the Model 100 and 200... >> if I knew that before I forgot. Anyone used it? Any opinions on its >> debugging and scriptability versus VirtualT? >> >> -- John. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/3461e9e5/attachment-0001.htm >> > >> >> ------------------------------ >> >> Message: 2 >> Date: Fri, 23 Oct 2026 13:21:45 -0700 >> From: Gary Weber <[email protected]> >> To: [email protected] >> Cc: Model 100 Discussion <[email protected]> >> Subject: Re: [M100] Drawing The Largest Circle or Polygon on a Model-T >> Screen >> Message-ID: >> < >> caajazkoa7twwv9xnfhljdc849rpmsfx2ok-jx2_kfvydb99...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hi David, >> >> I'd be curious about your comparison to the speed of circle drawing with >> your BASIC routine compared to the CIRVLE(X,Y),R routine in the latest >> Sardos for the T200. :) >> >> Also wondering how your algorithm compares to the one I'm using iny >> routine, as it relates to how well it interprets curvature at the lower >> radius circles. >> >> If you want to play with a SARDOS option from for the 200 you can download >> it from the SARDOS download area. >> >> https://www.web8201.net/default.asp?content=/Files/body.asp%3Fname=SARDOS/TS-DOS%20(NEC/M100/T200)%26url=SARDOS_TSDOS >> >> Gary >> >> >> >> >> >> On Thu, Oct 22, 2026, 8:02?AM David Szasz <[email protected]> wrote: >> >> > Hi Again: >> > >> > Here is a subroutine to draw the largest polygon or "circle" on a m200 >> > screen: (This relates to the m100 discussion list on 10/16/26 >> regarding >> > a CIRCLE() command for the Model-T computers.) >> > >> > 10 'DRAW REG POLYGON OR "CIRCLE" >> > 20 CLS >> > 35 XC=120:YC=63 'SET SCREEN CTR >> > 40 R=63 'SET RADIUS IN PIXELS >> > 50 N=24 'SET NO. OF SIDES >> > 60 PI=4*ATN(1) 'SET SINGLE PRECISION PI >> > 70 DA=(2*PI)/N 'ANGLE STEP PER VERTEX >> > 90 X1=XC+R*COS(0):Y1=YC+R*SIN(0) 'CALC 1ST VERTEX >> > 110 X0=X1 'SAVE START POINT >> > 120 FOR I=1TON 'STEP >> > 130 A=I*DA >> > 140 X2=XC+R*COS(A):Y2=YC+R*SIN(A) >> > 160 LINE (X1,Y1)-(X2,Y2) >> > 170 X1=X2:Y1=Y2 >> > 180 NEXTI >> > 190 END >> > >> > I am a "novice" m100-BASIC programmer so you will forgive any violation >> of >> > your sensibilities. The code works well when drawing a figure with a low >> > number of corners or "vertices", like a triangle or petagon. But you >> will >> > see if you draw a polygon with a low radius value (like 10) with a high >> > number of sides (like 24) it starts to look like a piece of "popcorn". >> I >> > wrote it originally in GWBasic and there it takes on an elongated >> > appearance due to the aspect ratio of GWbasic for an early PC screen. >> Hence >> > the ability of the CIRCLE() command in GWBasic to change the aspect >> ratio >> > to make the circle look better. On the m200 I'm guessing that the pixels >> > are more square so it looks OK as is. >> > >> > 1.) In the real world (whatever that is?) I would add code to save the >> > coordinates of the vertices to an array. Then take the coordinates and >> draw >> > a polygon from that. It would take less code and save processing time. >> But >> > for just "playing" around this is OK. >> > >> > 2.) In books relating to the Model-T computers they always plot the >> > individual points of a circle, which looks better but takes an eternity >> to >> > draw. >> > >> > 3.) For the m100 screen size one will have to reduce the values of YC in >> > line 35 and R in line 40 accordingly. >> > >> > 4.) As expected, values exceeding screen size will cause an error. >> > >> > >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/2db6fa28/attachment-0002.htm >> > >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 23 Oct 2026 13:21:45 -0700 >> From: Gary Weber <[email protected]> >> To: [email protected] >> Cc: Model 100 Discussion <[email protected]> >> Subject: Re: [M100] Drawing The Largest Circle or Polygon on a Model-T >> Screen >> Message-ID: >> < >> caajazkoa7twwv9xnfhljdc849rpmsfx2ok-jx2_kfvydb99...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hi David, >> >> I'd be curious about your comparison to the speed of circle drawing with >> your BASIC routine compared to the CIRVLE(X,Y),R routine in the latest >> Sardos for the T200. :) >> >> Also wondering how your algorithm compares to the one I'm using iny >> routine, as it relates to how well it interprets curvature at the lower >> radius circles. >> >> If you want to play with a SARDOS option from for the 200 you can download >> it from the SARDOS download area. >> >> https://www.web8201.net/default.asp?content=/Files/body.asp%3Fname=SARDOS/TS-DOS%20(NEC/M100/T200)%26url=SARDOS_TSDOS >> >> Gary >> >> >> >> >> >> On Thu, Oct 22, 2026, 8:02?AM David Szasz <[email protected]> wrote: >> >> > Hi Again: >> > >> > Here is a subroutine to draw the largest polygon or "circle" on a m200 >> > screen: (This relates to the m100 discussion list on 10/16/26 >> regarding >> > a CIRCLE() command for the Model-T computers.) >> > >> > 10 'DRAW REG POLYGON OR "CIRCLE" >> > 20 CLS >> > 35 XC=120:YC=63 'SET SCREEN CTR >> > 40 R=63 'SET RADIUS IN PIXELS >> > 50 N=24 'SET NO. OF SIDES >> > 60 PI=4*ATN(1) 'SET SINGLE PRECISION PI >> > 70 DA=(2*PI)/N 'ANGLE STEP PER VERTEX >> > 90 X1=XC+R*COS(0):Y1=YC+R*SIN(0) 'CALC 1ST VERTEX >> > 110 X0=X1 'SAVE START POINT >> > 120 FOR I=1TON 'STEP >> > 130 A=I*DA >> > 140 X2=XC+R*COS(A):Y2=YC+R*SIN(A) >> > 160 LINE (X1,Y1)-(X2,Y2) >> > 170 X1=X2:Y1=Y2 >> > 180 NEXTI >> > 190 END >> > >> > I am a "novice" m100-BASIC programmer so you will forgive any violation >> of >> > your sensibilities. The code works well when drawing a figure with a low >> > number of corners or "vertices", like a triangle or petagon. But you >> will >> > see if you draw a polygon with a low radius value (like 10) with a high >> > number of sides (like 24) it starts to look like a piece of "popcorn". >> I >> > wrote it originally in GWBasic and there it takes on an elongated >> > appearance due to the aspect ratio of GWbasic for an early PC screen. >> Hence >> > the ability of the CIRCLE() command in GWBasic to change the aspect >> ratio >> > to make the circle look better. On the m200 I'm guessing that the pixels >> > are more square so it looks OK as is. >> > >> > 1.) In the real world (whatever that is?) I would add code to save the >> > coordinates of the vertices to an array. Then take the coordinates and >> draw >> > a polygon from that. It would take less code and save processing time. >> But >> > for just "playing" around this is OK. >> > >> > 2.) In books relating to the Model-T computers they always plot the >> > individual points of a circle, which looks better but takes an eternity >> to >> > draw. >> > >> > 3.) For the m100 screen size one will have to reduce the values of YC in >> > line 35 and R in line 40 accordingly. >> > >> > 4.) As expected, values exceeding screen size will cause an error. >> > >> > >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/2db6fa28/attachment-0003.htm >> > >> >> ------------------------------ >> >> Message: 4 >> Date: Fri, 23 Oct 2026 13:23:59 -0700 >> From: B9 <[email protected]> >> To: [email protected] >> Subject: Re: [M100] Anyone used Model 100 or 200 in MAME? >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> Yeah, I've used it. Debugging and scripting is not as good as Virtual T. >> It also cannot handle some ROMs. For example, the 8201A emulation doesn't >> do ROMs at all. >> >> On the upside, it emulates all the chips, so the timing is cycle precise. >> >> It also has the familiar MAME interface and command line options. >> (Presuming you've used MESS). >> >> I rarely use it because I can't just run it on any machine; it uses lots >> of CPU. (Also, why does it default to blurring the pixels? That doesn't >> even make sense for an LCD.) >> >> I did find a need for it a few months ago when I reported that Virtual T >> was running FOR loops slightly too fast. >> >> --Ben >> >> >> >> On October 23, 2026 1:13:13 PM PDT, "John R. Hogerhuis" <[email protected]> >> wrote: >> >Found out on Facebook that MAME emulator supports the Model 100 and >> 200... >> >if I knew that before I forgot. Anyone used it? Any opinions on its >> >debugging and scriptability versus VirtualT? >> > >> >-- John. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/1f3e66c0/attachment-0001.htm >> > >> >> ------------------------------ >> >> Message: 5 >> Date: Fri, 23 Oct 2026 22:27:55 +0000 (UTC) >> From: <[email protected]> >> To: "[email protected]" <[email protected]> >> Subject: [M100] Tandy 200 Restoration - need LCD >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> when using super cap how do you prevent overvoltage ~5.5v? As NiCad >> orig's age (dried out?) the internal resistance gets large and the terminal >> voltage rises as high as 7-8v resulting in IC damage!?? >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/4b5b08cd/attachment-0001.htm >> > >> >> ------------------------------ >> >> Message: 6 >> Date: Fri, 23 Oct 2026 17:54:10 -0500 >> From: Douglas Quagliana <[email protected]> >> To: [email protected] >> Subject: Re: [M100] Anyone used Model 100 or 200 in MAME? >> Message-ID: >> <CALaYSmkj_bXeJyryRdLE4UoDZOk7PT5p30xkzscH= >> [email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> Does the MAME version support audio input to the cassette interface? >> >> I have a project I am working on that is delayed because my 100 has a >> screen issue and the other emulators that I am aware of don't support the >> cassette port audio input. >> >> Regards, >> Douglas >> >> On Fri, Oct 23, 2026, 3:24?PM B9 <[email protected]> wrote: >> >> > Yeah, I've used it. Debugging and scripting is not as good as Virtual T. >> > It also cannot handle some ROMs. For example, the 8201A emulation >> doesn't >> > do ROMs at all. >> > >> > On the upside, it emulates all the chips, so the timing is cycle >> precise. >> > >> > It also has the familiar MAME interface and command line options. >> > (Presuming you've used MESS). >> > >> > I rarely use it because I can't just run it on any machine; it uses lots >> > of CPU. (Also, why does it default to blurring the pixels? That doesn't >> > even make sense for an LCD.) >> > >> > I did find a need for it a few months ago when I reported that Virtual T >> > was running FOR loops slightly too fast. >> > >> > --Ben >> > >> > >> > >> > On October 23, 2026 1:13:13 PM PDT, "John R. Hogerhuis" < >> [email protected]> >> > wrote: >> > >> >> Found out on Facebook that MAME emulator supports the Model 100 and >> >> 200... if I knew that before I forgot. Anyone used it? Any opinions on >> its >> >> debugging and scriptability versus VirtualT? >> >> >> >> -- John. >> >> >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/30bca5f4/attachment-0001.htm >> > >> >> ------------------------------ >> >> Message: 7 >> Date: Fri, 23 Oct 2026 20:12:36 -0500 >> From: Mike Hyde <[email protected]> >> To: [email protected] >> Cc: [email protected] >> Subject: Re: [M100] NEC 8201A Technical Reference manual >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> You are correct. I rotated, split the pages, combined the files and >> tried to clean it up a bit. The source is still the original files that >> were linked hear earlier in the thread. >> >> >> > On Oct 20, 2026, at 12:02?PM, Brian K. White <[email protected]> >> wrote: >> > >> > I apologize for criticizing, but this appears to be a blurry 40M >> version of these two sharp 5.7M and 3.4M files I found on my drive. I don't >> know where I got them, presumably archive.org <http://archive.org/> or >> web8201. >> > >> > >> https://drive.google.com/drive/folders/1yriOM60OrGU94kBm81UsGNcaNmDki5_C >> > >> > The 3.4M appears to be a made from the 5.7M. The both have the same >> created date in 2005, both say ABBYY FineReader, but the 3.4M also says >> modified 2017 and with Adobe Acrobat and is saved as PDF 1.6 while the 5.7M >> is 1.2. So someone reprocessed the 5.7M to get the 3.4M without losing >> anything as far as I can tell. They both look the same sharpness. >> > >> > It appears to have all the same dust speckles and random lines and >> scratches and the same major flaws on the pages John specifically pointed >> out like 77 and 79. >> > >> > Is that in the original and all copies will have it? >> > ... Yes I see Kurt's new scan has those same things too. >> > Some original fax or xerox from NEC must have had it. >> > >> > What does Kurt's new scan fix? >> > >> > Sorry Kurt I know how tedious it is to scan a book! >> > >> > -- >> > bkw >> > >> > On 10/20/26 01:47, Mike Hyde wrote: >> >> I tried cleaning it up a bit. >> >> nec8201_techref.pdf <https://drive.google.com/file/ >> d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing < >> https://drive.google.com/file/%20d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing >> >> >> >> drive.google.com <http://drive.google.com/> < >> https://drive.google.com/file/ >> d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing < >> https://drive.google.com/file/%20d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing >> >> >> >> drive_favicon_2026_32dp.png <https://drive.google.com/file/ >> d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing < >> https://drive.google.com/file/%20d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing >> >> >> >> < >> https://drive.google.com/file/d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view? >> usp=sharing < >> https://drive.google.com/file/d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?%20usp=sharing >> >> >> >>> On Oct 19, 2026, at 10:39?PM, Gary Weber <[email protected] <mailto: >> [email protected]>> wrote: >> >>> >> >>> Kurt's scan is in three parts: >> >>> >> >>> https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt1.pdf >> <https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt1.pdf>, >> >>> https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt2.pdf >> <https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt2.pdf>, >> >>> https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt3.pdf >> <https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt3.pdf> >> >>> >> >>> And yes these are getting uploaded to archive.org < >> http://archive.org/> <http://archive.org/ >, along with all of the other >> PDFs I have fro the various other manuals. >> >>> >> >>> Gary >> >>> >> >>> On Mon, Oct 19, 2026 at 7:44?PM B9 <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >> >>> >> >>> __ >> >>> I suggest uploading to archive.org <http://archive.org/> < >> http://archive.org/> as a start. >> >>> >> >>> --b9 >> >>> >> >>> >> >>> On October 19, 2026 6:54:45 PM PDT, Kurt McCullum >> >>> <[email protected] <mailto:[email protected]> <mailto: >> [email protected]>> wrote: >> >>> >> >>> I've just finished scanning the manual but it's just over 36 >> >>> megs in size. I need to figure out where to upload it, but >> >>> when I do I will send the links. >> >>> >> >>> Kurt >> >>> >> >>> On Sun, Oct 18, 2026, at 9:41 PM, John R. Hogerhuis wrote: >> >>>> I think it was Kurt McCullum that had a clean copy... >> >>>> >> >>>> I need the following pages from the NEC tech ref: >> >>>> >> >>>> Pg 77, 78, 79, 97, 99, 105, 177, 119, 191, 198, 210, 211, 228 >> >>>> >> >>>> What I am working on is a very accurate OCR with good >> >>>> formatting of the ASCII art and accurate content for all >> >>>> assembly listings, etc. I'm using gemma4:31b on a local rig >> >>>> to do the conversions to ASCII and ultimately .md. My current >> >>>> purpose is informing the AI as to low level access to file >> >>>> system etc for it to generate VirtualT socket tests for >> >>>> Gary's port of SuperROM. >> >>>> >> >>>> The AI is doing a much better ocr of the content than the >> >>>> PDF has. It is doing an excellent job. Even at ASCII art. >> >>>> Sometimes hallucinating portions of diagrams that aren't >> >>>> there, which is bizarre. And it keeps stopping and needing to >> >>>> be kicked to continue working. Even so it will save me a lot >> >>>> of time and we will all have a more tractable version of the >> >>>> content, ultimately. >> >>>> >> >>>> Thanks, >> >>>> >> >>>> -- John. >> >>> >> > >> > >> > -- >> > bkw >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/41a2fd55/attachment-0002.htm >> > >> >> ------------------------------ >> >> Message: 8 >> Date: Fri, 23 Oct 2026 20:12:36 -0500 >> From: Mike Hyde <[email protected]> >> To: [email protected] >> Cc: [email protected] >> Subject: Re: [M100] NEC 8201A Technical Reference manual >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> You are correct. I rotated, split the pages, combined the files and >> tried to clean it up a bit. The source is still the original files that >> were linked hear earlier in the thread. >> >> >> > On Oct 20, 2026, at 12:02?PM, Brian K. White <[email protected]> >> wrote: >> > >> > I apologize for criticizing, but this appears to be a blurry 40M >> version of these two sharp 5.7M and 3.4M files I found on my drive. I don't >> know where I got them, presumably archive.org <http://archive.org/> or >> web8201. >> > >> > >> https://drive.google.com/drive/folders/1yriOM60OrGU94kBm81UsGNcaNmDki5_C >> > >> > The 3.4M appears to be a made from the 5.7M. The both have the same >> created date in 2005, both say ABBYY FineReader, but the 3.4M also says >> modified 2017 and with Adobe Acrobat and is saved as PDF 1.6 while the 5.7M >> is 1.2. So someone reprocessed the 5.7M to get the 3.4M without losing >> anything as far as I can tell. They both look the same sharpness. >> > >> > It appears to have all the same dust speckles and random lines and >> scratches and the same major flaws on the pages John specifically pointed >> out like 77 and 79. >> > >> > Is that in the original and all copies will have it? >> > ... Yes I see Kurt's new scan has those same things too. >> > Some original fax or xerox from NEC must have had it. >> > >> > What does Kurt's new scan fix? >> > >> > Sorry Kurt I know how tedious it is to scan a book! >> > >> > -- >> > bkw >> > >> > On 10/20/26 01:47, Mike Hyde wrote: >> >> I tried cleaning it up a bit. >> >> nec8201_techref.pdf <https://drive.google.com/file/ >> d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing < >> https://drive.google.com/file/%20d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing >> >> >> >> drive.google.com <http://drive.google.com/> < >> https://drive.google.com/file/ >> d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing < >> https://drive.google.com/file/%20d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing >> >> >> >> drive_favicon_2026_32dp.png <https://drive.google.com/file/ >> d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing < >> https://drive.google.com/file/%20d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?usp=sharing >> >> >> >> < >> https://drive.google.com/file/d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view? >> usp=sharing < >> https://drive.google.com/file/d/1lrG5xFYHzFkpzP9aIkPClPZplgM7CVsL/view?%20usp=sharing >> >> >> >>> On Oct 19, 2026, at 10:39?PM, Gary Weber <[email protected] <mailto: >> [email protected]>> wrote: >> >>> >> >>> Kurt's scan is in three parts: >> >>> >> >>> https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt1.pdf >> <https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt1.pdf>, >> >>> https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt2.pdf >> <https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt2.pdf>, >> >>> https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt3.pdf >> <https://www.web8201.net/Files/LIBRARY_web8201/nec8201_techref_pt3.pdf> >> >>> >> >>> And yes these are getting uploaded to archive.org < >> http://archive.org/> <http://archive.org/ >, along with all of the other >> PDFs I have fro the various other manuals. >> >>> >> >>> Gary >> >>> >> >>> On Mon, Oct 19, 2026 at 7:44?PM B9 <[email protected] <mailto: >> [email protected]> <mailto:[email protected]>> wrote: >> >>> >> >>> __ >> >>> I suggest uploading to archive.org <http://archive.org/> < >> http://archive.org/> as a start. >> >>> >> >>> --b9 >> >>> >> >>> >> >>> On October 19, 2026 6:54:45 PM PDT, Kurt McCullum >> >>> <[email protected] <mailto:[email protected]> <mailto: >> [email protected]>> wrote: >> >>> >> >>> I've just finished scanning the manual but it's just over 36 >> >>> megs in size. I need to figure out where to upload it, but >> >>> when I do I will send the links. >> >>> >> >>> Kurt >> >>> >> >>> On Sun, Oct 18, 2026, at 9:41 PM, John R. Hogerhuis wrote: >> >>>> I think it was Kurt McCullum that had a clean copy... >> >>>> >> >>>> I need the following pages from the NEC tech ref: >> >>>> >> >>>> Pg 77, 78, 79, 97, 99, 105, 177, 119, 191, 198, 210, 211, 228 >> >>>> >> >>>> What I am working on is a very accurate OCR with good >> >>>> formatting of the ASCII art and accurate content for all >> >>>> assembly listings, etc. I'm using gemma4:31b on a local rig >> >>>> to do the conversions to ASCII and ultimately .md. My current >> >>>> purpose is informing the AI as to low level access to file >> >>>> system etc for it to generate VirtualT socket tests for >> >>>> Gary's port of SuperROM. >> >>>> >> >>>> The AI is doing a much better ocr of the content than the >> >>>> PDF has. It is doing an excellent job. Even at ASCII art. >> >>>> Sometimes hallucinating portions of diagrams that aren't >> >>>> there, which is bizarre. And it keeps stopping and needing to >> >>>> be kicked to continue working. Even so it will save me a lot >> >>>> of time and we will all have a more tractable version of the >> >>>> content, ultimately. >> >>>> >> >>>> Thanks, >> >>>> >> >>>> -- John. >> >>> >> > >> > >> > -- >> > bkw >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261023/41a2fd55/attachment-0003.htm >> > >> >> ------------------------------ >> >> Message: 9 >> Date: Sat, 24 Oct 2026 12:02:53 +0200 >> From: Georg K?ter <[email protected]> >> To: M100 Discussion Group <[email protected]> >> Subject: [M100] NEC-PC8300 - TELCOM Stat >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> Community, >> ? >> running NEC-P8300 in native mode I found something strange. Trying to set >> in TELCOM using F3 to COM parameter fails always >> with a beep, no matter which combination i.e. 9N81XN I choose. This >> happen on real hardware and in VirtualT too. >> ROM on real hardware is same as in VirtualT, I?ve tried also ROM-Dump I >> found on https://github.com/bkw777/m100_dev/tree/main/platforms/N83 >> without success. Also user manual doesn?t give any hint. >> Setting the COM parameter with a small BASIC program works fine and >> TELCOM use the paramater from this. >> ? >> 1 ?NEC-PC8300 - set COM parameter to 9N81XN >> 2 for i=62470 to 62475:readj,pokei,j:next:end >> 3 DATA 57,78,56,49,88,78 >> ? >> Has anybody from you seen this before? What I?m doing wrong? >> ? >> Regards >> Georg >> ? >> Vertraulichkeitsinformation: >> Diese Nachricht ist vertraulich. Die Informationen dieser Nachricht sind >> ausschlie?lich f?r die pers?nliche >> und vertrauliche Verwendung durch den/die oben genannten Empf?nger >> bestimmt. Wenn Sie kein beabsichtigter >> Empf?nger sind, bitte lesen, kopieren und verwenden Sie die Nachricht >> nicht. Machen Sie sie nicht anderen >> zug?nglich. Bitte informieren Sie uns umgehend ?ber den Zustellfehler und >> senden Sie die Originalnachricht >> per E-Mail an uns zur?ck. >> >> Confidentiality Notice: >> This message is confidential. The information contained in this message >> is intended only for the personal >> and confidential use of the recipient(s) named above. If you are not the >> intended recipient, please do not >> read, copy, or use it and do not disclose it to others. Please inform us >> immediately of the delivery error >> and return the original message to us via e-mail. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261024/ac915ea6/attachment-0001.htm >> > >> >> ------------------------------ >> >> Message: 10 >> Date: Sat, 24 Oct 2026 08:01:33 -0700 >> From: Gary Weber <[email protected]> >> To: [email protected] >> Subject: Re: [M100] NEC-PC8300 - TELCOM Stat >> Message-ID: >> <CAAJazkq+Azr= >> [email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> The NEC PC-8300 has support for the optional internal modem, and due to >> this, the STAT has extra parameters that have to be specified. >> >> Add "P1O" on the end of your setting. That is a P, then a 1, and then the >> letter O. >> >> Alternatively you can just keep the PC-8300 in 8201 mode and continue to >> use the old settings with an OUT 163,2 from BASIC. >> >> >> >> On Sat, Oct 24, 2026, 3:03 AM Georg K?ter < >> [email protected]> wrote: >> >> > Community, >> > >> > >> > >> > running NEC-P8300 in native mode I found something strange. Trying to >> set >> > in TELCOM using F3 to COM parameter fails always >> > >> > with a beep, no matter which combination i.e. 9N81XN I choose. This >> happen >> > on real hardware and in VirtualT too. >> > >> > ROM on real hardware is same as in VirtualT, I?ve tried also ROM-Dump I >> > found on https://github.com/bkw777/m100_dev/tree/main/platforms/N83 >> > >> > without success. Also user manual doesn?t give any hint. >> > >> > Setting the COM parameter with a small BASIC program works fine and >> TELCOM >> > use the paramater from this. >> > >> > >> > >> > 1 ?NEC-PC8300 - set COM parameter to 9N81XN >> > >> > 2 for i=62470 to 62475:readj,pokei,j:next:end >> > >> > 3 DATA 57,78,56,49,88,78 >> > >> > >> > >> > Has anybody from you seen this before? What I?m doing wrong? >> > >> > >> > >> > Regards >> > >> > Georg >> > >> > >> > >> > *Vertraulichkeitsinformation: *Diese Nachricht ist vertraulich. Die >> > Informationen dieser Nachricht sind ausschlie?lich f?r die pers?nliche >> > und vertrauliche Verwendung durch den/die oben genannten Empf?nger >> > bestimmt. Wenn Sie kein beabsichtigter >> > Empf?nger sind, bitte lesen, kopieren und verwenden Sie die Nachricht >> > nicht. Machen Sie sie nicht anderen >> > zug?nglich. Bitte informieren Sie uns umgehend ?ber den Zustellfehler >> und >> > senden Sie die Originalnachricht >> > per E-Mail an uns zur?ck. >> > >> > >> > *Confidentiality Notice: *This message is confidential. The information >> > contained in this message is intended only for the personal >> > and confidential use of the recipient(s) named above. If you are not the >> > intended recipient, please do not >> > read, copy, or use it and do not disclose it to others. Please inform us >> > immediately of the delivery error >> > and return the original message to us via e-mail. >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.bitchin100.com/private/m100/attachments/20261024/78136fb6/attachment-0001.htm >> > >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> M100 mailing list >> [email protected] >> http://lists.bitchin100.com/listinfo/m100 >> >> >> ------------------------------ >> >> End of M100 Digest, Vol 190, Issue 22 >> ************************************* >> >
