Re: [M100] Connector Question
On 2/17/23 17:56, ho collo wrote: Looking at page 6-1 of the service manual for the Model 100 attempting to figure out the connector that goes from the AC jack to the main board. It has 3 pins to wires (orange, red, black). Does anyone know a replacement part # or the spacing so I can replace both the male and female connections? Thanks in advance. Ho. Sent from my iPhone I dont' think that is actually a removable connector. No male & female parts, just a single "wire-to-board" part that's soldered to the board. So you lose nothing by just soldering the wires directly. If you want to replace it with a removable connector, I think the space is a bit constrained for most 2.54mm 3-pin connectors. -- bkw
Re: [M100] One Tiny Battery Pack (Cryptronics, RAM+ expansion)
On 2/17/23 19:53, Fisher wrote: Meanwhile the whole contraption os giving me fits! Is there a tppd driver that it will play nice with? I can't manage it with a floppy drive or a Backpack. After I load up some files it forgets how to change banks. I suppose I need to be using Teeny or somesuch, just thought to ask here in the RAM+ users group. Sean Consult the manual http://www.club100.org/library/doc/tsdos.html And these pimers about binary apps on this platform: http://www.bitchin100.com/wiki/index.php?title=Loading_a_typical_CO_file http://www.bitchin100.com/wiki/index.php?title=Run-In-Place_CO All machine language programs conflict with each other on this platform. To switch back and forth between different machine language programs, you have to keep copies of them in ram in .CO file form, and re-load them into high memory to displace whatever the last other program you ran was. (multiplan is a little different in this case, where it's really a rom but also installs a ram component and effectively has the same problem.) Usually this means having a .CO file in the ram filesystem, and a small .BA file launcher which basically just does a clear statement and then runs the .CO For instance: http://www.club100.org/library/ups/diskon.do This uses up a lot of ram though, since it means you have effectively 2 copies of the program in ram, one in the form of the .CO file, and one in high memory which is the one that's actually executed. The copy in high memory gets clobbered every time any other machine language program runs. This is true for almost all machine language programs. There are exeptions but they are rare and fragile. *some* few machine language apps like TEENY and DSKMGR have special relocating installers that can edit all of the jumps and address pointers in a program at install-time, to install the app at some arbitrary offset address, so that two machine language apps can both coexist side by side in high memory at different address ranges. Then they can each have what's called a trigger file in the main menu that just jumps to the right address. But neither multiplan nor ts-dos has a relocatable installer like that that I know of. So, they just will always clobber each other. This is actually the norm for most machine language apps. TS-DOS has a special option to store the .CO file on the disk instead of in ram, and in ram you can have a much smaller TSLOAD.CO instead of the full DOS100.CO. TSLOAD is small and all it does is load DOS100.CO from the disk into high memory temporarily each time you want to run it, the same as what Ultimate ROM 2 does. I can't find a copy of tsload on-line anywhere unfortunately. I did find a copy for Model 200, but not for 100 or nec. The manual describes it, and I see Kurt asked about it on the list years ago, but that's it. For anyone interested, tsload.co for model 200 is here: http://www.club100.org/library/libpg.html Most of that stuff, including that particular copy of dos200.co is all just for Paul's X-OS which is a special alternative OS just for Model 200. But that copy of tsload.co is probably just the ordinary copy from travelling software for ts-dos on the 200. It doesn't do you any good on a 100. Anyway, unless someone can come up with a copy of TSLOAD.CO for 100, you simply really want TS-DOS in ROM, and since you also want to use Multiplan which is itself a rom, then you really want a REX# so you can switch between roms at will. Failing that, you need to keep a copy of DOS100.CO in ram, and launch it with a little basic launcher like the one I linked above. This will eat 10 to 12k of your ram but that's just the way it is with machine language apps on this platform. -- bkw
Re: [M100] Need a beta tester
Thanks, Gary! Not sure how that slipped past me. --b9 On Fri, Feb 17, 2023 at 1:46 AM Gary Weber wrote: > Actually I think this would be the conditional statement that you would > want: > > IF PEEK(A)=195 AND PEEK(A+5)=46 THEN AP=1 ELSE AP=0 > > That actually would identify if AP is in memory, with the JMP instruction > at the start and the '.' at the +5 offset right in the middle of the > version string. > > > On Wed, Feb 15, 2023 at 2:48 PM gary wrote: > >> I'm having trouble with understanding how the conditional in this >> statement would ever evaluate to true: >> >> IF PEEK(A)=195 AND PEEK(A)=46 THEN AP=1 ELSE AP=0 >> >> Did you mean PEEK(A+1)=46 ? >> >> Gary Weber >> www.web8201.com >> >> >> >> Original message >> From: B 9 >> Date: 2/13/23 11:51 PM (GMT-07:00) >> To: m...@bitchin100.com >> Subject: Re: [M100] Need a beta tester >> >> I am working on updating the ap_doc.do file with AsciiPixel image >>> encoding documentation, but it is a bit involved and is taking some time to >>> update. >>> >> >> Hey Ken, I know you're in the middle of updating the documentation, but I >> figured I might as well share the minor changes I made to ap_doc.do. Mainly >> I corrected the instructions for the Tandy 200, but I also fixed the mouse >> cursor ascii art, and added a section on how to detect if AsciiPixels is >> available. >> >> Here's the patch: >> >> --- ap_doc.txt~ 2023-02-13 21:14:40.395371132 -0800+++ ap_doc.txt >> 2023-02-13 22:22:58.771620379 -0800@@ -5,8 +5,8 @@ >> /_/ \_\___/\___|_|_||_| |_/_/\_\___|_|___/ >> >> - Version 1.0- Copyright 2015, Ken Pettit+ Version >> 1.0.1+ Copyright 2023, Ken Pettit >> All rights reserved. >> >> @@ -19,7 +19,7 @@ >> The library is distributed as a standard .CO file that can be loaded >> to the portable and installed using the LOADM BASIC instruction. Once >> installed, the library is accessed by making CALL instructions to the-base >> entry address (value depends on M100/T102 vs T200), passing in +base entry >> address (value is the same on M100/T102 and T200), passing in >> arguments in the A and HL registers to indicate the desired action. >> >> Services currently provided by AP include:@@ -44,12 +44,21 @@ >> 2. Enter basic and execute the "CLEAR" command to move HIMEM so >> there is room to load ASCPIX: >> -- Model 100/102:clear 256,58000-- Model 200: >> clear 256,58000+clear 256,58000 >> >> 3. Still from BASIC, load the CO: >> -loadm "ASCPIX"+- Model 100/102:loadm "ASCPIX"+ >>- Model 200:loadm "ASCPX2"DETECTING+=+To >> detect if ASCPIX has been loaded, use this code:++A=58000+IF >> PEEK(A)=195 AND PEEK(A)=46 THEN AP=1 ELSE AP=0 >> >> >> CALLING@@ -106,8 +115,8 @@ >> >>|\ |\ |\ >>| \ | \ | \- | \ |. \ >> |_.'- |__/ \\ \\+ |/^` |_.' >> | \+\\ \\|__/ >> >>Cursor 0 Cursor 1Cursor 2 >> >> Or, see the attached file. >> >> —b9 >> >>
Re: [M100] Option ROM - multiplan
I posted scans for the M100 version a week or so ago: Using Multiplan https://archive.org/details/trs-80-model-100-portable-computer-using-multiplan-26-3829 Reference Guide https://archive.org/details/trs-80-model-100-portable-computer-multiplan-reference-guide-26-3829 The originals are huge files so I made smaller file versions here too where I made sure the drawings still came out clear. A lot of the illustrations use only background color to highlight cells and table blocks, so I made sure those didn't get washed out. When you see a white square, it's really white in the original. http://tandy.wiki/MULTIPLAN -- bkw On 2/17/23 19:22, Joseph Colson III wrote: Is there a need for the Manual to Multiplan? I have the original Multiplan Reference and Using Multiplan Guides. I can scan them and provide the PDF’s if needed. Joe -- bkw
Re: [M100] One Tiny Battery Pack (Cryptronics, RAM+ expansion)
Meanwhile the whole contraption os giving me fits! Is there a tppd driver that it will play nice with? I can't manage it with a floppy drive or a Backpack. After I load up some files it forgets how to change banks. I suppose I need to be using Teeny or somesuch, just thought to ask here in the RAM+ users group. Sean
[M100] Option ROM - multiplan
Is there a need for the Manual to Multiplan? I have the original Multiplan Reference and Using Multiplan Guides.I can scan them and provide the PDF's if needed. Joe
[M100] Connector Question
Looking at page 6-1 of the service manual for the Model 100 attempting to figure out the connector that goes from the AC jack to the main board. It has 3 pins to wires (orange, red, black). Does anyone know a replacement part # or the spacing so I can replace both the male and female connections? Thanks in advance. Ho. Sent from my iPhone
Re: [M100] Some M100 SIG files
Mike -- I've done all required adjustments that I could identify and I've done some spot checking; it all appears to be fixed up now. Give it a try for the files you were interested in. Gary On Fri, Feb 17, 2023 at 2:42 PM Mike Stein wrote: > Good guess; as a matter of fact there are other files with an extension > made up of the contributor's initials and a digit. > > On Fri, Feb 17, 2023 at 3:20 PM Brian K. White > wrote: > >> On 2/17/23 13:51, Gary Weber wrote: >> > Hi Mike, >> > >> > I'm not sure what those extensions represent either, >> >> .pw1 is probably for Phil Wheeler >> >> and .des is probably description based on the contents >> >> IE, not intended to indicate file types >> There's a fair amount of that scattered through the m100sig >> >> -- >> bkw >> >>
Re: [M100] - Backpack
It might not be that straightforward; the printer port is partially shared with the keyboard. On Fri, Feb 17, 2023 at 10:58 AM Alex ... wrote: > Wire a R2R DAC to the printer port and have the M100 play music Covox > style. 😃 > > On Wed, Feb 15, 2023, 14:21 Fisher wrote: > >> All it needs in its next version is an 8mm stereo jack, an mp3 player and >> some jukebox software for the laptop! >> Too much to wish for? No matter, it’s already a great piece of kit. :-) >> >> Sean >> >> >> On Feb 14, 2023, at 8:08 PM, < >> bir...@soigeneris.com> wrote: >> >> The Backpack was designed by a friend of mine who wishes to remain >> private. He sent me one and I thought it was great and encouraged him to >> make more offering my help. My only part of the design was the case. >> >> Jeff Birt >> >> *From:* M100 *On Behalf Of * >> grima...@gmail.com >> *Sent:* Tuesday, February 14, 2023 1:15 PM >> *To:* Model 100 Discussion >> *Subject:* [M100] - Backpack >> >> Just received my Backpack from Soigeneris. All I have to say, is that I >> really like the design of it all. It’s relatively compact, it matches the >> design of the M100, and it runs on a single AA cell. >> >> I immediately plugged it in, and got it to work. Pretty much zero >> configuration needed. I’ve already got REX installed so I was able to load >> up TS-DOS and be off to the races. >> >> Shout out to Soigeneris and to whomever designed and built this device! >> >> Best, >> George >> >> >>
Re: [M100] Some M100 SIG files
Good guess; as a matter of fact there are other files with an extension made up of the contributor's initials and a digit. On Fri, Feb 17, 2023 at 3:20 PM Brian K. White wrote: > On 2/17/23 13:51, Gary Weber wrote: > > Hi Mike, > > > > I'm not sure what those extensions represent either, > > .pw1 is probably for Phil Wheeler > > and .des is probably description based on the contents > > IE, not intended to indicate file types > There's a fair amount of that scattered through the m100sig > > -- > bkw > >
Re: [M100] Some M100 SIG files
How did I not know about this... Thanks, Brian! On Fri, Feb 17, 2023 at 3:19 PM Brian K. White wrote: > > > https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LFUTL.INF > > > https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LF.CMD > > > https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LFUTL.PW1 > > > https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LFUTL.DES > > > On 2/17/23 13:30, Mike Stein wrote: > > Hi Gary, > > > > I'm trying to download a couple of files from the M100 SIG repository > > but it looks like it won't allow downloading any files with a > > non-standard extension and I don't quite understand the explanation and > > instructions I get instead. > > > > Can you help? > > > > The files are in LIB07: > > LFUTIL.PW1 > > LFUTIL.DES > > > > What are those extensions anyway? > > > > TIA, > > > > m > > -- > bkw > >
Re: [M100] Some M100 SIG files
I'm just going to do this in the file system: find . -type f -name '[^.]*.*' | sed 's|.*\.||' | sort -u And make sure every extension listed is an allowed downloadable file type. On Fri, Feb 17, 2023 at 1:20 PM Brian K. White wrote: > On 2/17/23 13:51, Gary Weber wrote: > > Hi Mike, > > > > I'm not sure what those extensions represent either, > > .pw1 is probably for Phil Wheeler > > and .des is probably description based on the contents > > IE, not intended to indicate file types > There's a fair amount of that scattered through the m100sig > > -- > bkw > >
Re: [M100] SPAM-LOW: Recap and new battery
I had no issues replacing either the battery or the caps. Everything flowed fine. Must be living right. Sent from my iPhone > On Feb 16, 2023, at 07:02, bir...@soigeneris.com wrote: > > I would recommend not trying to use a desoldering tool directly. They did > not use thermal reliefs on the pads going into ground/VCC pours which makes > it difficult to heat up properly. Use the soldering iron to heat one leg and > push the top of that cap to the opposite side. Then do the same for the other > leg. It will take 3-4 repetitions, but you can 'walk' the cap out this way. > Now you have full access to the pads top and bottom to remove the solder. > > If the solder is really corroded, you will need to carefully scrape the > crusty stuff off before you can heat it enough to remove the part. The > tin/lead oxides that form from corrosion have a much higher melting > temperature, so they have to be physically removed. > > I have used a small heat gun, one I use for heat shrink tubing (not for > component removal), to preheat a difficult PCB to 100C or so. This can help > but don't go crazy, keep the temp low. > > Go to YouTube, search for "Hey Birt!", my channel, and from the channel page > search for M100 or Model 100 and you will find a lot of videos where I show > this process. > > Jeff Birt > > -Original Message- > From: M100 On Behalf Of ho collo > Sent: Wednesday, February 15, 2023 7:41 PM > To: m100@lists.bitchin100.com > Subject: SPAM-LOW: [M100] Recap and new battery > > I picked up a Model 100 from the flea market for $10 and was shocked it > actually worked. Waiting on a new battery from MO, but did get my caps in > today. I’ve been told the caps may be difficult to remove. Has anyone tried > using a heat gun on a low setting prior to attempting? Did it work out for > you? > > Ho. > > Sent from my iPhone > > >
Re: [M100] Some M100 SIG files
On 2/17/23 13:51, Gary Weber wrote: Hi Mike, I'm not sure what those extensions represent either, .pw1 is probably for Phil Wheeler and .des is probably description based on the contents IE, not intended to indicate file types There's a fair amount of that scattered through the m100sig -- bkw
Re: [M100] Some M100 SIG files
https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LFUTL.INF https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LF.CMD https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LFUTL.PW1 https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-07-UTILITIES/LFUTL.DES On 2/17/23 13:30, Mike Stein wrote: Hi Gary, I'm trying to download a couple of files from the M100 SIG repository but it looks like it won't allow downloading any files with a non-standard extension and I don't quite understand the explanation and instructions I get instead. Can you help? The files are in LIB07: LFUTIL.PW1 LFUTIL.DES What are those extensions anyway? TIA, m -- bkw
Re: [M100] Some M100 SIG files
looking at the files, .DES is a description file, flat ascii, and .pw1 is basic in asciiwillardSent from my Galaxy Tab® A null
Re: [M100] Some M100 SIG files
Thanks very much!!! m On Fri, Feb 17, 2023 at 1:51 PM Gary Weber wrote: > Hi Mike, > > I'm not sure what those extensions represent either, but I can say that I > definitely missed adding them to the approved "MIME" types list on the > website back-end, thus preventing download in this case. Ugh! Sorry > about that. > > I'll go through the entire library with a script that will spit out all > file extensions that I can use to compare against the MIME type > configuration as it stands now so I can add the missing ones. > > Gary > > On Fri, Feb 17, 2023 at 11:30 AM Mike Stein wrote: > >> Hi Gary, >> >> I'm trying to download a couple of files from the M100 SIG repository but >> it looks like it won't allow downloading any files with a non-standard >> extension and I don't quite understand the explanation and instructions I >> get instead. >> >> Can you help? >> >> The files are in LIB07: >> LFUTIL.PW1 >> LFUTIL.DES >> >> What are those extensions anyway? >> >> TIA, >> >> m >> >
Re: [M100] Some M100 SIG files
Hi Mike, I'm not sure what those extensions represent either, but I can say that I definitely missed adding them to the approved "MIME" types list on the website back-end, thus preventing download in this case. Ugh! Sorry about that. I'll go through the entire library with a script that will spit out all file extensions that I can use to compare against the MIME type configuration as it stands now so I can add the missing ones. Gary On Fri, Feb 17, 2023 at 11:30 AM Mike Stein wrote: > Hi Gary, > > I'm trying to download a couple of files from the M100 SIG repository but > it looks like it won't allow downloading any files with a non-standard > extension and I don't quite understand the explanation and instructions I > get instead. > > Can you help? > > The files are in LIB07: > LFUTIL.PW1 > LFUTIL.DES > > What are those extensions anyway? > > TIA, > > m >
Re: [M100] Burning a 27C256 EPROM
I have one of those XGecu T48 programmers. It works on some other EEPROMs. Haven't tried it on 27C256 yet. On Wed, Feb 15, 2023, 18:06 Brian K. White wrote: > TL-966, any version. I like both my old TL-866A and newer TL-866II+ > because they are supported by the open source "minipro" util. But the > maker no longer sells those and you have to get them from ebay or amazon > or aliexpress. > > The current models T48 and T56 are apparently fine too, you are just > limited to using their windows app to run it, which does work in wine so > it's actually still usable from linux (this much I do know directly > because it's the same for the II+). > So depending on what you care about, a CS will be the cheapest if you > can find one. It's the same as the A but without an ICSP heater for > in-circuit jtag programming of some chips. It is perfect for DIP eproms. > The A version adds the icsp header, and the II+ version has new guts > inside and is like the A but newer and supports more chips. > > You will also need a uv eraser. There's a generic $15 blue platic one > you can get anywhere. It's fine. > > https://www.ebay.com/itm/255956579505 > https://www.ebay.com/itm/363143496160 > > If you don't care about being able to use the open source software, you > can get either of the current models from their official store. The > website looks sketchy but autoelectric.cn is the real site and links > from there go to their official ebay and aliexpress shops. > > You don't really need to get one of the kits with 50 different adapters > just for working on these old machines that have all DIP parts. You can > always get them later if you decide you need them. A used TL-866CS will > be the cheapest since it's both an old model now and lacks the ICSP port > so most people want the A or II+ versions. But the age doesn't matter > at all. The minipro software supports it and can handle every chip > you're likely to encounter in 80's machines, and really you're probably > only ever even going to care about exactly one chip, 27C256. > > > > On 2/15/23 16:46, Joseph Colson III wrote: > > While surfing the private files on the Club100 site the file below > > caught my eye as I have a booster pack and would like to update the > > System ROM. My question for the group is how much do the programmers > > cost? What inexpensive programmer would you suggest? Is it difficult > > to program? Any links to software or documentation would be helpful. > > > > As Always Thanks for your help, > > > > Joe > > > > ( BP1ROM_Fixed.bin ) > > > > This is the Booster Pak v1.23 "BP1" main system ROM image which includes > > the multi-page file display bug fix. With the original ROM, if you have > > more than two pages of files to display, you would only ever be able to > > see the second page of files when pressing shift-down. The third page of > > files or beyond was inaccessible due to a limitation in Traveling > > Software's TPDD client. Well, with this replacement BP1 system ROM > > image, the limitation is gone! The bug fix was originally made available > > in Ken Pettit's release of the TS-DOS 4.10 option ROM. This fix has been > > extended to all RAM versions of TS-DOS, as well as the SARDOS option > > ROM. And now, it is available for the "Disk" client that is in your > > Booster Pak's system ROM. Just burn this image to a standard 27C256 > > EPROM and replace your Booster Pak's "BP1" chip which would be all the > > way on the bottom-right side of your Booster Pak's sockets. > > > > -- > bkw > >
[M100] Some M100 SIG files
Hi Gary, I'm trying to download a couple of files from the M100 SIG repository but it looks like it won't allow downloading any files with a non-standard extension and I don't quite understand the explanation and instructions I get instead. Can you help? The files are in LIB07: LFUTIL.PW1 LFUTIL.DES What are those extensions anyway? TIA, m
Re: [M100] - Backpack
Wire a R2R DAC to the printer port and have the M100 play music Covox style. 😃 On Wed, Feb 15, 2023, 14:21 Fisher wrote: > All it needs in its next version is an 8mm stereo jack, an mp3 player and > some jukebox software for the laptop! > Too much to wish for? No matter, it’s already a great piece of kit. :-) > > Sean > > > On Feb 14, 2023, at 8:08 PM, < > bir...@soigeneris.com> wrote: > > The Backpack was designed by a friend of mine who wishes to remain > private. He sent me one and I thought it was great and encouraged him to > make more offering my help. My only part of the design was the case. > > Jeff Birt > > *From:* M100 *On Behalf Of * > grima...@gmail.com > *Sent:* Tuesday, February 14, 2023 1:15 PM > *To:* Model 100 Discussion > *Subject:* [M100] - Backpack > > Just received my Backpack from Soigeneris. All I have to say, is that I > really like the design of it all. It’s relatively compact, it matches the > design of the M100, and it runs on a single AA cell. > > I immediately plugged it in, and got it to work. Pretty much zero > configuration needed. I’ve already got REX installed so I was able to load > up TS-DOS and be off to the races. > > Shout out to Soigeneris and to whomever designed and built this device! > > Best, > George > > >
[M100] Need a beta tester
Actually I think this would be the conditional statement that you would want: IF PEEK(A)=195 AND PEEK(A+5)=46 THEN AP=1 ELSE AP=0 That actually would identify if AP is in memory, with the JMP instruction at the start and the '.' at the +5 offset right in the middle of the version string. On Wed, Feb 15, 2023 at 2:48 PM gary wrote: > I'm having trouble with understanding how the conditional in this > statement would ever evaluate to true: > > IF PEEK(A)=195 AND PEEK(A)=46 THEN AP=1 ELSE AP=0 > > Did you mean PEEK(A+1)=46 ? > > Gary Weber > www.web8201.com > > > > Original message > From: B 9 > Date: 2/13/23 11:51 PM (GMT-07:00) > To: m...@bitchin100.com > Subject: Re: [M100] Need a beta tester > > I am working on updating the ap_doc.do file with AsciiPixel image >> encoding documentation, but it is a bit involved and is taking some time to >> update. >> > > Hey Ken, I know you're in the middle of updating the documentation, but I > figured I might as well share the minor changes I made to ap_doc.do. Mainly > I corrected the instructions for the Tandy 200, but I also fixed the mouse > cursor ascii art, and added a section on how to detect if AsciiPixels is > available. > > Here's the patch: > > --- ap_doc.txt~ 2023-02-13 21:14:40.395371132 -0800+++ ap_doc.txt > 2023-02-13 22:22:58.771620379 -0800@@ -5,8 +5,8 @@ > /_/ \_\___/\___|_|_||_| |_/_/\_\___|_|___/ > > - Version 1.0- Copyright 2015, Ken Pettit+ Version > 1.0.1+ Copyright 2023, Ken Pettit > All rights reserved. > > @@ -19,7 +19,7 @@ > The library is distributed as a standard .CO file that can be loaded > to the portable and installed using the LOADM BASIC instruction. Once > installed, the library is accessed by making CALL instructions to the-base > entry address (value depends on M100/T102 vs T200), passing in +base entry > address (value is the same on M100/T102 and T200), passing in > arguments in the A and HL registers to indicate the desired action. > > Services currently provided by AP include:@@ -44,12 +44,21 @@ > 2. Enter basic and execute the "CLEAR" command to move HIMEM so > there is room to load ASCPIX: > -- Model 100/102:clear 256,58000-- Model 200: > clear 256,58000+clear 256,58000 > > 3. Still from BASIC, load the CO: > -loadm "ASCPIX"+- Model 100/102:loadm "ASCPIX"+ > - Model 200:loadm "ASCPX2"DETECTING+=+To detect > if ASCPIX has been loaded, use this code:++A=58000+IF > PEEK(A)=195 AND PEEK(A)=46 THEN AP=1 ELSE AP=0 > > > CALLING@@ -106,8 +115,8 @@ > >|\ |\ |\ >| \ | \ | \- | \ |. \ > |_.'- |__/ \\ \\+ |/^` |_.' >| \+\\ \\|__/ > >Cursor 0 Cursor 1Cursor 2 > > Or, see the attached file. > > —b9 > >
