Re: [M100] TextSweeper2_1

[John R. Hogerhuis]

Thanks!

Played a round in CloudT.

— John.

Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 100

[John Gardner]

You're not going to find a supercap that'll

a)  Keep RAM alive as long as a healthy NiCd will,  and

2)  Fit inside the case.  Or inside your trunk,  probably...

But what you can do is

1)  Use Eneloop "Low Self-Discharge" AAs,  which if your RAM
 is healthy (not drawing much stand-by current)  will keep memory
 alive for many years,  fully charged.

b)  Use a 3 or 5F supercap,  which will keep healthy RAM alive for
 weeks;  plenty of time to recharge or replace your Eneloops.

Why?  Eneloops don't leak.  Supercaps don't leak.  NiCds do.



On 5/13/18, Jeffrey Birt  wrote:
> Update…
>
>
>
> It was the RAM module. After thinking about it after Fugu’s email the other
> day it occurred to me I had done a capture of the standard RAM bank select
> lines (and I happened to dave it) and after looking at it again it looked
> fine. This evening I pulled the standard RAM module out, split apart a 30
> pin DIP socket to make two 15 pin SIPs and plugged in of the option RAMs.
> AND…nothing. Sigh…
>
>
>
> Then I noticed I had not plugged the ROM back in after cleaning the flux
> from the board. So, the ROM was installed, and STRL-BRK done on power up
> and…It’s ALIVE! Bwa-ha-ha-ha! It’s ALIVE!
>
>
>
> I tried reflowing the original standard RAM module and it still did not
> work. I could ohm out each line to each individual RAM chip and maybe get
> lucky and find one open trace, but I would guess that a bad RAM chip is more
> likely. I’ll look into making some more RAM module or buying a few, for now
> I have 16K.
>
>
>
> As luck would have it the second M100 I bought from across the state arrived
> yesterday, I still have not opened it yet. It is supposed to work, got it
> from the original owner who seemed like a nice guy. A grand total of $61
> including shipping. Now I’ll put together an order for enough caps to finish
> recapping the first M100 and re-cap the 2nd one while I’m at it. I also need
> to try and calculate a super-cap size that will at least match the original
> NiCad battery.
>
>
>
> Thanks again everyone (especially Fugu) for your help.
>
>
>
> Jeff
>
>
>
>
>
> From: M100  On Behalf Of Fugu ME100
> Sent: Thursday, May 10, 2018 10:06 AM
> To: m...@bitchin100.com
> Subject: Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive
> Model 100
>
>
>
> The address could be stuck internally on the RAM so the address line would
> appear OK externally.  The fact the ROM runs correctly with the shared
> Address line would indicate the address lines are generally OK.  It could be
> floating on the module as you suggest,  look to see if there is any
> corrosion on the module and the pins to the module are in good condition.
> Perhaps try reflowing each of the module pins to make sure there are no dry
> joints?
>
>
>
> I am currently looking into producing some sort of test harness for the
> model T however the lack of socket for the 8085 makes it hard to add in a
> test fixture.  Even trying to tri-state the 8085 appears difficult as it
> does not tri-state the ALE, all the other lines are OK.  Another option
> would be to try and monitor what it does with something that plugs into the
> RAM socket.  That way at least there would be a trace showing the bus
> activity.   Being able to single step the 8085 might be another option with
> a known ROM in the socket.
>
>
>
>

Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 100

[Jeffrey Birt]

Update…

 

It was the RAM module. After thinking about it after Fugu’s email the other day 
it occurred to me I had done a capture of the standard RAM bank select lines 
(and I happened to dave it) and after looking at it again it looked fine. This 
evening I pulled the standard RAM module out, split apart a 30 pin DIP socket 
to make two 15 pin SIPs and plugged in of the option RAMs. AND…nothing. Sigh…

 

Then I noticed I had not plugged the ROM back in after cleaning the flux from 
the board. So, the ROM was installed, and STRL-BRK done on power up and…It’s 
ALIVE! Bwa-ha-ha-ha! It’s ALIVE! 

 

I tried reflowing the original standard RAM module and it still did not work. I 
could ohm out each line to each individual RAM chip and maybe get lucky and 
find one open trace, but I would guess that a bad RAM chip is more likely. I’ll 
look into making some more RAM module or buying a few, for now I have 16K.

 

As luck would have it the second M100 I bought from across the state arrived 
yesterday, I still have not opened it yet. It is supposed to work, got it from 
the original owner who seemed like a nice guy. A grand total of $61 including 
shipping. Now I’ll put together an order for enough caps to finish recapping 
the first M100 and re-cap the 2nd one while I’m at it. I also need to try and 
calculate a super-cap size that will at least match the original NiCad battery.

 

Thanks again everyone (especially Fugu) for your help.

 

Jeff

 

 

From: M100  On Behalf Of Fugu ME100
Sent: Thursday, May 10, 2018 10:06 AM
To: m...@bitchin100.com
Subject: Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 
100

 

The address could be stuck internally on the RAM so the address line would 
appear OK externally.  The fact the ROM runs correctly with the shared Address 
line would indicate the address lines are generally OK.  It could be floating 
on the module as you suggest,  look to see if there is any corrosion on the 
module and the pins to the module are in good condition.  Perhaps try reflowing 
each of the module pins to make sure there are no dry joints?

 

I am currently looking into producing some sort of test harness for the model T 
however the lack of socket for the 8085 makes it hard to add in a test fixture. 
 Even trying to tri-state the 8085 appears difficult as it does not tri-state 
the ALE, all the other lines are OK.  Another option would be to try and 
monitor what it does with something that plugs into the RAM socket.  That way 
at least there would be a trace showing the bus activity.   Being able to 
single step the 8085 might be another option with a known ROM in the socket.  

 

Re: [M100] TextSweeper2_1

[George Rimakis]

Hi John,

I use the paid app iZipPro on my iPhone to handle archives. It works fairly 
well. In either case I’ve attached the .BA for convenience.



TSWEEP.BA
Description: Binary data


~George

> On May 13, 2018, at 7:39 PM, John R. Hogerhuis  wrote:
> 
> A minor request, providing a straight .DO or BA instead of a zip makes it 
> easier to open in CloudT from my iPhone. As far as I know I can’t unzip a 
> file on the iPhone or transfer it into Google Drive in any obvious way.  
> 
> — John. 

Re: [M100] TextSweeper2_1

[John R. Hogerhuis]

A minor request, providing a straight .DO or BA instead of a zip makes it
easier to open in CloudT from my iPhone. As far as I know I can’t unzip a
file on the iPhone or transfer it into Google Drive in any obvious way.

— John.

[M100] TextSweeper2_1

[George Rimakis]

Hi all,

 

I’ve updated my game Text Sweeper(a minesweeper clone for the Model-T), to 
version to 2.1 For anyone that has played 2.0, here are the differences.

-Replaced custom cursor with standard cursor. Should be easier to see the 
cursor now on real hardware.

-Removed some unneeded lines of code, reducing tokenized file size from 4.3KB 
to around 3.3KB.

-Changed flag symbol to be Yen symbol.

-Changed mine symbol to asterisk.

 

http://www.georgerimakis.com/tsweep.html

 

Available at the above link. Please let me know your thoughts.

 

Best,

George



smime.p7s
Description: S/MIME cryptographic signature

Re: [M100] use of PRINT

[Kenneth Pettit]

Hi Steve.

I think I actually used this technique of auto string concatenation in one (or 
all) of my BASIC 10-Liners. Which reminds me, I never actually got the 
documentation done for 2 of those.  I should do that and post the other 2 games 
to personal libraries.

Ken

Sent from my iPhone

> On May 13, 2018, at 11:24 AM, Bill Marcum  wrote:
> 
> 
> 
>> On Sun, May 13, 2018, 12:51 PM Stephen Adolph  wrote:
>> I am reminded of the one line basic program activity.  sometimes BASIC can 
>> be so compact.
>> 
>> Here is a way to do a WHILE statement or and endless loop as part of a one 
>> line program
>> 
>> FOR I=1 to2:?i:I=I-1:ifinkey$="a"theni=i+1:nextelsenext
>> 
> 
> 
> You can also write FOR I =1 TO 2 STEP 0

Re: [M100] use of PRINT

[Bill Marcum]

On Sun, May 13, 2018, 12:51 PM Stephen Adolph  wrote:

> I am reminded of the one line basic program activity.  sometimes BASIC can
> be so compact.
>
> Here is a way to do a WHILE statement or and endless loop as part of a one
> line program
>
> FOR I=1 to2:?i:I=I-1:ifinkey$="a"theni=i+1:nextelsenext
>
>
You can also write FOR I =1 TO 2 STEP 0

Re: [M100] use of PRINT

[Stephen Adolph]

I am reminded of the one line basic program activity.  sometimes BASIC can
be so compact.

Here is a way to do a WHILE statement or and endless loop as part of a one
line program

FOR I=1 to2:?i:I=I-1:ifinkey$="a"theni=i+1:nextelsenext



On Sun, May 13, 2018 at 12:02 PM, John R. Hogerhuis 
wrote:

>
> On Sun, May 13, 2018 at 7:08 AM Stephen Adolph 
> wrote:
>
>> I found this interesting bit of code.
>> here E=chr$(27).
>>
>> 10 PRINTE"pFile to Convert "E"q";
>>
>> I didn't know that basic automatically concatenates strings like this.  I
>> would have written this
>>
>> 10 PRINT E+"p"+"File to Convert"+E+"q";
>>
> Huh! I don’t remember ever seeing that, and I’ve typed in a lot of MS
> BASIC programs.
>
> — John.
>

Re: [M100] use of PRINT

[John R. Hogerhuis]

On Sun, May 13, 2018 at 7:08 AM Stephen Adolph  wrote:

> I found this interesting bit of code.
> here E=chr$(27).
>
> 10 PRINTE"pFile to Convert "E"q";
>
> I didn't know that basic automatically concatenates strings like this.  I
> would have written this
>
> 10 PRINT E+"p"+"File to Convert"+E+"q";
>
Huh! I don’t remember ever seeing that, and I’ve typed in a lot of MS BASIC
programs.

— John.

Re: [M100] use of PRINT

[Stephen Adolph]

I don't know, would have to research the manual a bit.
The other way is to  call POSIT, that is fast and simple to do.

On Sun, May 13, 2018 at 10:11 AM, George Rimakis  wrote:

> Hi Stephen,
>
>
>
> It’s funny you sent this, I was about to post. I’m trying to use the
> Escape Sequences to reposition the cursor to the location of Y,X.
>
>
>
> I’ve got
>
>
>
> Y=3
>
> X=14
>
> CR$=CHR$(27)+CHR$(89)
>
> PRINT CR$+CHR$(Y)+CHR$(X);
>
>
>
> I’ve already turned on the cursor earlier.
>
>
>
> Do I just have the wrong syntax? I also noticed that the strings to
> concatenate without use of + while testing this.
>
>
>
> ~Geore\ge
>
>
>
> *From: *M100  on behalf of Stephen
> Adolph 
> *Reply-To: *
> *Date: *Sunday, May 13, 2018 at 10:08 AM
> *To: *
> *Subject: *[M100] use of PRINT
>
>
>
> I found this interesting bit of code.
>
> here E=chr$(27).
>
>
> 10 PRINTE"pFile to Convert "E"q";
>
> I didn't know that basic automatically concatenates strings like this.  I
> would have written this
>
> 10 PRINT E+"p"+"File to Convert"+E+"q";
>

Re: [M100] use of PRINT

[George Rimakis]

Hi Stephen,

 

It’s funny you sent this, I was about to post. I’m trying to use the Escape 
Sequences to reposition the cursor to the location of Y,X.

 

I’ve got

 

Y=3

X=14

CR$=CHR$(27)+CHR$(89)

PRINT CR$+CHR$(Y)+CHR$(X);

 

I’ve already turned on the cursor earlier.

 

Do I just have the wrong syntax? I also noticed that the strings to concatenate 
without use of + while testing this.

 

~Geore\ge

 

From: M100  on behalf of Stephen Adolph 

Reply-To: 
Date: Sunday, May 13, 2018 at 10:08 AM
To: 
Subject: [M100] use of PRINT

 

I found this interesting bit of code.  

here E=chr$(27).


10 PRINTE"pFile to Convert "E"q";

I didn't know that basic automatically concatenates strings like this.  I would 
have written this

10 PRINT E+"p"+"File to Convert"+E+"q";



smime.p7s
Description: S/MIME cryptographic signature

[M100] use of PRINT

[Stephen Adolph]

I found this interesting bit of code.
here E=chr$(27).

10 PRINTE"pFile to Convert "E"q";

I didn't know that basic automatically concatenates strings like this.  I
would have written this

10 PRINT E+"p"+"File to Convert"+E+"q";