Re: [M100] Programming languages for the Model 100?

2015-06-29 Thread John R. Hogerhuis
On Mon, Jun 29, 2015 at 9:13 AM, Mark Wickens  wrote:
> I have a package waiting for me in the hallway - it's either an NEC or a
> Tandy 200!
>
> Mark.
>
>

Wow already in Stage 3 of your model T addiction. Ecellent...

-- John.


Re: [M100] Programming languages for the Model 100?

2015-06-29 Thread Mark Wickens
I have a package waiting for me in the hallway - it's either an NEC or a 
Tandy 200!


Mark.

On 29/06/15 15:39, John R. Hogerhuis wrote:

MFORTH opt rom source is public so you could look at that.

http://www.strangegizmo.com/products/mforth/

Steve Adolph with REX/REXMGR is the one to most recently create an
Option ROM. You could ask him what he has as far as a Option ROM
template.

-- John.




Re: [M100] Programming languages for the Model 100?

2015-06-29 Thread John R. Hogerhuis
MFORTH opt rom source is public so you could look at that.

http://www.strangegizmo.com/products/mforth/

Steve Adolph with REX/REXMGR is the one to most recently create an
Option ROM. You could ask him what he has as far as a Option ROM
template.

-- John.


Re: [M100] Programming languages for the Model 100?

2015-06-17 Thread Mark Wickens

John

My plan is to create an OptionROM so any boiler plate code, guidelines, 
etc. would be most welcome.
I am still planning on exploring the SmallC route, but I've already 
started coding in assembler and am quite liking it :)

Certainly 8085 is a lot easier to get in your head than VAX Macro-32!

Regards, Mark.

On 11/06/15 18:57, John R. Hogerhuis wrote:

On Thu, Jun 11, 2015 at 10:04 AM, Kurt McCullum  wrote:

John,

Glad to hear it exists. The question I am trying to answer is about the
boilerplate. Looking through a few of the Traveling Software ROMs it would
appear that each one is slightly different. Is this because the interrupt
routines are different for various software used on the ROMs?

Kurt



Maybe, in part. Steve and I found bugs/inefficiencies in Mo's
routines. So we were fixing them.

So I'd say it's a few things:

a) Bugfixes/improvements over time
b) Different ROMs, different names.
c) Application specific hardware interrupt handling (software
interrupts / effectively "custom instructions")
b) ISTR there being some nooks and crannies where you could insert
code. So some variability may just be that they have application
specific code packed in between system critical stuff.

-- John.




Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread Mark Wickens
I can get SmallC running under Linux. This generates a SmallMAC (an 8085 
macro assembler) input source file. I have the source code for SmallMAC 
which is also written in C - I should be able to get that running under 
Linux also.


The remaining steps, as I see them, are as follows:

1. Post-process the object files that SmallMAC genarates into a format 
readable on a Tandy 102 (or at least burnable).
2. Provide enough c-library functions to interface with the hardware - 
screen, keyboard etc.

3. Provide a suitable C startup file.
4. Ideally programs would use suitable sections so that they can be 
split between ROM and RAM.


I have done all this in the past with a different compiler targeting a 
single board 68k computer.
Hopefully the memory overhead would be acceptable to leave enough space 
for reasonable sized programs.


I was wondering if you can call the ROM routines from an option ROM?

Regards, Mark.

On 11/06/15 19:27, Frederick Whitaker wrote:
The developer's wife stayed in touch with the list for a time after he 
died. If you can reach her, I don't know her email, she might be 
willing to sell copies. At the time we last obtained copies we were 
able to get them for $50 a pop, which was an excellent price.


RBASIC is still an excellent tool. Unless someone would like to 
develop a dedicated 8085 output "C" compiler. There are 8085 "C" 
compilers, but they have to be run under a "Z80" emulator.


Don't forget the excellent assembly compiler in VirtualT.

Frederick Whitaker


On 6/11/2015 10:52 AM, John R. Hogerhuis wrote:

I don't know. I bought a legit copy a few years back.

On Thursday, June 11, 2015, Mike Stein <mailto:mhs.st...@gmail.com>> wrote:


Is RBASIC still available?
m

- Original Message -
*From:* John R. Hogerhuis

*To:* Model 100 Discussion

*Sent:* Thursday, June 11, 2015 9:03 AM
    *Subject:* Re: [M100] Programming languages for the Model 100?

Not really. Assembly is your best bet hands down.

But there is RBASIC a basic compiler and MFORTH.

-- John. 







Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread Frederick Whitaker
The developer's wife stayed in touch with the list for a time after he 
died. If you can reach her, I don't know her email, she might be willing 
to sell copies. At the time we last obtained copies we were able to get 
them for $50 a pop, which was an excellent price.


RBASIC is still an excellent tool. Unless someone would like to develop 
a dedicated 8085 output "C" compiler. There are 8085 "C" compilers, but 
they have to be run under a "Z80" emulator.


Don't forget the excellent assembly compiler in VirtualT.

Frederick Whitaker


On 6/11/2015 10:52 AM, John R. Hogerhuis wrote:

I don't know. I bought a legit copy a few years back.

On Thursday, June 11, 2015, Mike Stein <mailto:mhs.st...@gmail.com>> wrote:


Is RBASIC still available?
m

- Original Message -
*From:* John R. Hogerhuis

*To:* Model 100 Discussion

*Sent:* Thursday, June 11, 2015 9:03 AM
    *Subject:* Re: [M100] Programming languages for the Model 100?

Not really. Assembly is your best bet hands down.

But there is RBASIC a basic compiler and MFORTH.

-- John. 





Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread John R. Hogerhuis
On Thu, Jun 11, 2015 at 10:04 AM, Kurt McCullum  wrote:
> John,
>
> Glad to hear it exists. The question I am trying to answer is about the
> boilerplate. Looking through a few of the Traveling Software ROMs it would
> appear that each one is slightly different. Is this because the interrupt
> routines are different for various software used on the ROMs?
>
> Kurt
>
>

Maybe, in part. Steve and I found bugs/inefficiencies in Mo's
routines. So we were fixing them.

So I'd say it's a few things:

a) Bugfixes/improvements over time
b) Different ROMs, different names.
c) Application specific hardware interrupt handling (software
interrupts / effectively "custom instructions")
b) ISTR there being some nooks and crannies where you could insert
code. So some variability may just be that they have application
specific code packed in between system critical stuff.

-- John.


Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread Stephen Adolph
I think the techniques are the same, but the actual routines will differ.
The improved boiler plate John and I did is just an example.
Steve

On Thursday, June 11, 2015, Kurt McCullum  wrote:
> John,
> Glad to hear it exists. The question I am trying to answer is about the
boilerplate. Looking through a few of the Traveling Software ROMs it would
appear that each one is slightly different. Is this because the interrupt
routines are different for various software used on the ROMs?
> Kurt
>
>
>
> On Thursday, June 11, 2015 9:03 AM, John R. Hogerhuis 
wrote:
>
>
> On Thu, Jun 11, 2015 at 8:36 AM, Kurt McCullum 
wrote:
>> Does this book still exist?
>>
>> "The Secrets of the Option ROM Revealed" by Mo Budlong
>>
>
> It exists at my house. Mo also wrote RBASIC.
>
> The main takeaway though is the boilerplate assembly code which you
> base an OptROM on, switching, and calls in/out of optrom to the main
> ROM. The boilerplate code inlcudes the ROM portion of interrupt
> handlers that need to be present since when the OptROM is switched in
> since interrupts can happen any time. It also includes the
> "installation" code.
>
> Steve and I worked a bit on the "shell" and maybe the call code. If
> anyone wants to write their own OptROM I think we can get you some
> code.
>
> -- John.
>
>
>


Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread Kurt McCullum
John,
Glad to hear it exists. The question I am trying to answer is about the 
boilerplate. Looking through a few of the Traveling Software ROMs it would 
appear that each one is slightly different. Is this because the interrupt 
routines are different for various software used on the ROMs?
Kurt
 


 On Thursday, June 11, 2015 9:03 AM, John R. Hogerhuis  
wrote:
   

 On Thu, Jun 11, 2015 at 8:36 AM, Kurt McCullum  wrote:
> Does this book still exist?
>
> "The Secrets of the Option ROM Revealed" by Mo Budlong
>

It exists at my house. Mo also wrote RBASIC.

The main takeaway though is the boilerplate assembly code which you
base an OptROM on, switching, and calls in/out of optrom to the main
ROM. The boilerplate code inlcudes the ROM portion of interrupt
handlers that need to be present since when the OptROM is switched in
since interrupts can happen any time. It also includes the
"installation" code.

Steve and I worked a bit on the "shell" and maybe the call code. If
anyone wants to write their own OptROM I think we can get you some
code.

-- John.


   

Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread John R. Hogerhuis
On Thu, Jun 11, 2015 at 8:36 AM, Kurt McCullum  wrote:
> Does this book still exist?
>
> "The Secrets of the Option ROM Revealed" by Mo Budlong
>

It exists at my house. Mo also wrote RBASIC.

The main takeaway though is the boilerplate assembly code which you
base an OptROM on, switching, and calls in/out of optrom to the main
ROM. The boilerplate code inlcudes the ROM portion of interrupt
handlers that need to be present since when the OptROM is switched in
since interrupts can happen any time. It also includes the
"installation" code.

Steve and I worked a bit on the "shell" and maybe the call code. If
anyone wants to write their own OptROM I think we can get you some
code.

-- John.


Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread Kurt McCullum
Does this book still exist?

"The Secrets of the Option ROM Revealed" by Mo Budlong 


 On Thursday, June 11, 2015 7:52 AM, John R. Hogerhuis  
wrote:
   

 I don't know. I bought a legit copy a few years back. 

On Thursday, June 11, 2015, Mike Stein  wrote:

Is RBASIC still available? m
 - Original Message -  From: John R. Hogerhuis  To: Model 100 
Discussion  Sent: Thursday, June 11, 2015 9:03 AM Subject: Re: [M100] 
Programming languages for the Model 100? 
Not really. Assembly is your best bet hands down.  
 But there is RBASIC a basic compiler and MFORTH.  
-- John.  



  

Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread John R. Hogerhuis
I don't know. I bought a legit copy a few years back.

On Thursday, June 11, 2015, Mike Stein  wrote:

>  Is RBASIC still available?
>
> m
>
> - Original Message -
> *From:* John R. Hogerhuis
> 
> *To:* Model 100 Discussion
> 
> *Sent:* Thursday, June 11, 2015 9:03 AM
> *Subject:* Re: [M100] Programming languages for the Model 100?
>
> Not really. Assembly is your best bet hands down.
>
> But there is RBASIC a basic compiler and MFORTH.
>
> -- John.
>
>


Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread Mike Stein
Is RBASIC still available?

m
  - Original Message - 
  From: John R. Hogerhuis 
  To: Model 100 Discussion 
  Sent: Thursday, June 11, 2015 9:03 AM
  Subject: Re: [M100] Programming languages for the Model 100?


  Not really. Assembly is your best bet hands down. 


  But there is RBASIC a basic compiler and MFORTH. 


  -- John.  

Re: [M100] Programming languages for the Model 100?

2015-06-11 Thread John R. Hogerhuis
Not really. Assembly is your best bet hands down.

But there is RBASIC a basic compiler and MFORTH.

-- John.


[M100] Programming languages for the Model 100?

2015-06-11 Thread Mark Wickens

Can I trouble the list with a question regarding programming?

What are the options for programming the Model 100 other than BASIC and 
machine code, if any?


My Retrochallenge 2015/07 entry this year will centre around creating a 
custom ROM for my Model 102 and I know I'll make more progress on the 
software if I can code it in language like C. I have been investigating 
the options for generic 8080/8085 code generation with a view to 
customizing the output to target the Model 100 architecture. At the 
moment the most convenient solution looks like it will be a custom 
target for the SmallC compiler, but there are other options which are 
generally CP/M based.


Thanks for the help, Mark.