Re: [M100] Is this for real?

2018-02-13 Thread Doug Jackson 
Retro gear is just sometimes expensive.  $4k for an imsai 8080 isn't
unheard of.

On 14 Feb. 2018 2:37 pm, "Chris Fezzler"  wrote:

I found it fun to buy computers from when the industry was battling with
innovations and different form factors.  A lot of real innovative engineers
out there.

On ‎Tuesday‎, ‎February‎ ‎13‎, ‎2018‎ ‎09‎:‎34‎:‎16‎ ‎PM‎ ‎EST, Kevin
Becker  wrote:


“Retro” computing stuff seems to be going up in price lately. Even things
that didn’t seem very retro to me. Look at the prices for old 486/pentium
machines.  There are some wild ideas about the value of a generic beige x86
tower.

On Feb 13, 2018, at 9:22 PM, Chris Fezzler  wrote:

Fake to drive up prices?

On ‎Tuesday‎, ‎February‎ ‎13‎, ‎2018‎ ‎09‎:‎10‎:‎23‎ ‎PM‎ ‎EST, Kevin
Becker  wrote:


I was watching the TPDD2 and was disappointed when it went over $100
because one went for $60 or $70 a week ago.

It makes no sense they went so high. It looks like to two different buyers
too.

On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:

Check these two auctions that just ended...

Tandy-Portable-Disk-Drive-2


and

Tandy-102


How, why, WHAT??

Re: [M100] Is this for real?

2018-02-13 Thread Chris Fezzler 
 I found it fun to buy computers from when the industry was battling with 
innovations and different form factors.  A lot of real innovative engineers out 
there.

On ‎Tuesday‎, ‎February‎ ‎13‎, ‎2018‎ ‎09‎:‎34‎:‎16‎ ‎PM‎ ‎EST, Kevin 
Becker  wrote:  
 
 “Retro” computing stuff seems to be going up in price lately. Even things that 
didn’t seem very retro to me. Look at the prices for old 486/pentium machines.  
There are some wild ideas about the value of a generic beige x86 tower. 
On Feb 13, 2018, at 9:22 PM, Chris Fezzler  wrote:


 Fake to drive up prices?

On ‎Tuesday‎, ‎February‎ ‎13‎, ‎2018‎ ‎09‎:‎10‎:‎23‎ ‎PM‎ ‎EST, Kevin 
Becker  wrote:  
 
 I was watching the TPDD2 and was disappointed when it went over $100 because 
one went for $60 or $70 a week ago. 
It makes no sense they went so high. It looks like to two different buyers too. 
On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:


Check these two auctions that just ended...
Tandy-Portable-Disk-Drive-2

and
Tandy-102

How, why, WHAT??

Re: [M100] Is this for real?

2018-02-13 Thread Kevin Becker 
“Retro” computing stuff seems to be going up in price lately. Even things
that didn’t seem very retro to me. Look at the prices for old 486/pentium
machines.  There are some wild ideas about the value of a generic beige x86
tower.

On Feb 13, 2018, at 9:22 PM, Chris Fezzler  wrote:

Fake to drive up prices?

On ‎Tuesday‎, ‎February‎ ‎13‎, ‎2018‎ ‎09‎:‎10‎:‎23‎ ‎PM‎ ‎EST, Kevin
Becker  wrote:


I was watching the TPDD2 and was disappointed when it went over $100
because one went for $60 or $70 a week ago.

It makes no sense they went so high. It looks like to two different buyers
too.

On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:

Check these two auctions that just ended...

Tandy-Portable-Disk-Drive-2


and

Tandy-102


How, why, WHAT??

Re: [M100] Is this for real?

2018-02-13 Thread Chris Fezzler 
 Fake to drive up prices?

On ‎Tuesday‎, ‎February‎ ‎13‎, ‎2018‎ ‎09‎:‎10‎:‎23‎ ‎PM‎ ‎EST, Kevin 
Becker  wrote:  
 
 I was watching the TPDD2 and was disappointed when it went over $100 because 
one went for $60 or $70 a week ago. 
It makes no sense they went so high. It looks like to two different buyers too. 
On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:


Check these two auctions that just ended...
Tandy-Portable-Disk-Drive-2

and
Tandy-102

How, why, WHAT??

Re: [M100] Is this for real?

2018-02-13 Thread Chris Kmiec 
Yeah, there was a NIB TPDD2 few weeks back for $60 BIN. It got snached from
me literally as I was clicking to buy it...

These two crazy auctions though... Now the next 5 T102s listed will be $499
BIT, you just watch...

On Tue, Feb 13, 2018 at 8:10 PM, Kevin Becker  wrote:

> I was watching the TPDD2 and was disappointed when it went over $100
> because one went for $60 or $70 a week ago.
>
> It makes no sense they went so high. It looks like to two different buyers
> too.
>
> On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:
>
> Check these two auctions that just ended...
>
> Tandy-Portable-Disk-Drive-2
> 
>
> and
>
> Tandy-102
> 
>
> How, why, WHAT??
>
>

Re: [M100] Is this for real?

2018-02-13 Thread John R. Hogerhuis 
Could always be shill bidders. Or Bill G is getting into the hobby.

— John.

Re: [M100] Is this for real?

2018-02-13 Thread Josh Malone 
Same seller though. I call shenanigans.

On Feb 13, 2018 9:10 PM, "Kevin Becker"  wrote:

> I was watching the TPDD2 and was disappointed when it went over $100
> because one went for $60 or $70 a week ago.
>
> It makes no sense they went so high. It looks like to two different buyers
> too.
>
> On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:
>
> Check these two auctions that just ended...
>
> Tandy-Portable-Disk-Drive-2
> 
>
> and
>
> Tandy-102
> 
>
> How, why, WHAT??
>
>

Re: [M100] Is this for real?

2018-02-13 Thread Kevin Becker 
I was watching the TPDD2 and was disappointed when it went over $100
because one went for $60 or $70 a week ago.

It makes no sense they went so high. It looks like to two different buyers
too.

On Feb 13, 2018, at 9:05 PM, Chris Kmiec  wrote:

Check these two auctions that just ended...

Tandy-Portable-Disk-Drive-2


and

Tandy-102


How, why, WHAT??

[M100] Is this for real?

2018-02-13 Thread Chris Kmiec 
Check these two auctions that just ended...

Tandy-Portable-Disk-Drive-2


and

Tandy-102


How, why, WHAT??

Re: [M100] List of wanna haves

2018-02-13 Thread Lee Kelley 
The only reason I would really want a simple method for having an external
display port is to be able to connect to a projector for a presentation.
With the effect of showing that it can be done.

On Tuesday, February 13, 2018, John R. Hogerhuis  wrote:

>
> On Tue, Feb 13, 2018 at 11:02 AM Mike Stein  wrote:
>
>> I guess the thing that makes it relatively uninteresting for me is that
>> you'll have to be tethered to a display of some kind, which negates the
>> most attractive aspect of the ModelT, its portability; you might as well
>> just run VT on a laptop.
>>
>> m
>>
>
> Well might nice for dev on real hardware. But the only time I do that is
> when I’m testing serial port stuff so, yeah.
>
> Which I think is why when we’ve talked about this before the parallel port
> seems the better way. But then you need even more hardware.
>
> — John.
>
>>

-- 
*"I will never in my lifetime make a film that cannot be seen by the whole
family"*  Arther P. Jacobs

Re: [M100] List of wanna haves

2018-02-13 Thread John R. Hogerhuis 
On Tue, Feb 13, 2018 at 11:02 AM Mike Stein  wrote:

> I guess the thing that makes it relatively uninteresting for me is that
> you'll have to be tethered to a display of some kind, which negates the
> most attractive aspect of the ModelT, its portability; you might as well
> just run VT on a laptop.
>
> m
>

Well might nice for dev on real hardware. But the only time I do that is
when I’m testing serial port stuff so, yeah.

Which I think is why when we’ve talked about this before the parallel port
seems the better way. But then you need even more hardware.

— John.

>

Re: [M100] List of wanna haves

2018-02-13 Thread Mike Stein 
I guess the thing that makes it relatively uninteresting for me is that you'll 
have to be tethered to a display of some kind, which negates the most 
attractive aspect of the ModelT, its portability; you might as well just run VT 
on a laptop.

m
  - Original Message - 
  From: John R. Hogerhuis 
  To: m...@bitchin100.com 
  Sent: Tuesday, February 13, 2018 12:13 PM
  Subject: Re: [M100] List of wanna haves




  On Tue, Feb 13, 2018 at 7:26 AM Mike Stein  wrote:




And I haven't had an answer to what you want to do with it ;-)



I'm not aware of any software that uses the 80x25 screen mode, and 
redirecting the 8x40 display through the com port to a Pi or laptop etc. is 
trivial, so what makes this worth while (other than the challenge/fun) ?




  Definitely the more doable solution for non EE’s.


  Something like Coco drivewire but more portable. Pi with battery. 




  The serial connection is certainly faster than the built in display, at least 
for scrolling text. 


  Downside is you lose the port for other purposes (tpdd access) unless you 
packet multiplex. That would mean more software tricks on model t side. 


  — John.

Re: [M100] List of wanna haves

2018-02-13 Thread John R. Hogerhuis 
On Tue, Feb 13, 2018 at 7:26 AM Mike Stein  wrote:

>
> And I haven't had an answer to what you want to do with it ;-)
>
>
>
> I'm not aware of any software that uses the 80x25 screen mode, and
> redirecting the 8x40 display through the com port to a Pi or laptop etc. is
> trivial, so what makes this worth while (other than the challenge/fun) ?
>
>
Definitely the more doable solution for non EE’s.

Something like Coco drivewire but more portable. Pi with battery.


The serial connection is certainly faster than the built in display, at
least for scrolling text.

Downside is you lose the port for other purposes (tpdd access) unless you
packet multiplex. That would mean more software tricks on model t side.

— John.

Re: [M100] List of wanna haves

2018-02-13 Thread Brian White 
You did recieve a very thorough answer. That it won't work, and why not,
and what it would take to make it work. All that will happen is BASIC will
jump to a particular address, which jumps to the FC error.

-- 
bkw

On Feb 13, 2018 8:53 AM, "VANDEN BOSSCHE JAN" 
wrote:



I have asked the Raspberry Pi community to help me with the construction of
a DVI-like video-output device. I made the assumption that the DVI was only
a terminal. Both from the response here, as there, I understand now that
this combination is far more 'intimate' than I presumed.



https://www.raspberrypi.org/forums/viewtopic.php?p=1271713#p1271713



I hope that the response given in the above thread helps and incites
people, with far better and more knowledge of the processes and controllers
involved, to pick up on this project and propose the parameters for a
video-interface.



As far as I understand, the driver loaded from the DVI re-maps the video
controller of the M100 towards the one in the DVI, where new tekst and
graphics are generated. The 4K memory in the schematics is obviously the
video-RAM, where 40x16 text (640 bytes) and 240x128 points  (3840 bytes)
reside. I suppose text and graphics do not reside in different memory
locations. (because it doesn't fit...)



Anyway, contrary to what I thought before, we will probably need to
activate the SCREEN 1, 1 directive with software on the M100 itself. But
that software does not need to be as big as the original driver, because no
disk-routines are necessary.



I'm sorry if I sound presumptuous, and I apologise if I impose on people's
limited time, but I think this is a project worth pursuing.



(And I still didn't get an answer about the experiment I proposed, below.)

Greetings from the TyRannoSaurus
Jan-80 "
@ work( @ @ )
--.ooo--(_)--ooo.---

*From:* VANDEN BOSSCHE JAN
*Sent:* vrijdag 9 februari 2018 09:47
*To:* 'm...@bitchin100.com'
*Subject:* RE: [M100] List of wanna haves



.. .. (As I'm accessing this list from 2 different locations,

.. .. and my yahoo-postings aren't always visible to everyone,

.. .. I have repeated the question I send below)



I'm sadly enough not that technical, so I can't draw the same conclusion
from the link below. Can't that be confirmed from the ROM BASIC
dis-assembly too? Without a DVI connected and drivers loaded, what does
SCREEN 1,1 do ?



Anyway, even if it is wrong: would it take a lot of effort to re-write only
the display output portion of the DVI-drivers? That way, development could
start on a software solution for the video-output via the system bus. I had
thought of using the GPIO-pins of a Raspberry Pi for that. As the R.Pi can
also emulate a TPDD, you'd have a virtual DVI replacement, there.

Greetings from the TyRannoSaurus
Jan-80 "

@ work( @ @ )
--.ooo--(_)--ooo.---

*From:* M100 [mailto:m100-boun...@lists.bitchin100.com
] *On Behalf Of *Brian White

*Sent:* vrijdag 9 februari 2018 01:59
*To:* m...@bitchin100.com
*Subject:* Re: [M100] List of wanna haves



That won't work. I don't remember where I read this, but I read that the
system rom has calls for certain functions but they are just stubs. The rom
only contains the stub of a call that says "open CRT: for writing" which
just says go to some address and do whatever that address says. Normally
that address just points to the address for the built-in routine to return
the FC? error. But if dvi dos is installed then that address contains the
address of the routine in dvi dos to actually do something.

Aha, here's where I read it. Start on page 257
https://archive.org/details/InsideTheTrs80Model100

I can try it when I get home but we already know.

-- 

bkw







*From:* Jan Vanden Bossche [mailto:jan80...@yahoo.com ]

> how would you use it?



To have a bigger screen to work on, when not on the move. Imagine, a
17-inch old VGA monitor with 40 x 24 characters! HUGE!



I have a question, for anybody having a DVI:

Could you try the following: is it possible to operate a Model T hooked up
to a DVI, with the DVI ready to accept input and disk commands, but the
Model T without the driver software? I would think this is possible when
you boot up both machines, establish the connection, and then, while
connected, reset the Model so that it is no longer aware of it's
'companion'. At that moment, enter BASIC and type SCREEN 1,1. That would
send all BASIC output to the DVI, right? Does it ? (thàt's the question)



The above experiment would show if it's at all possible to run a
monitor-only part of a DVI, without loading software on the Model T to do
so. I hope, that the simple command SCREEN 1,1 does send some
screen-positioning code through the bus towards the DVI, even without the
drivers loaded on the Model T.  If it does, some clever programming on the
receiving side could just give us the DVI/video-only device we seek.



Greetings from the TyRannoSaurus
Jan-80


-

Re: [M100] List of wanna haves

2018-02-13 Thread Mike Stein 

  - Original Message - 
  From: VANDEN BOSSCHE JAN 
  To: m...@bitchin100.com 
  Sent: Tuesday, February 13, 2018 8:53 AM
  Subject: Re: [M100] List of wanna haves


   

  I have asked the Raspberry Pi community to help me with the construction of a 
DVI-like video-output device. I made the assumption that the DVI was only a 
terminal. Both from the response here, as there, I understand now that this 
combination is far more 'intimate' than I presumed.  

   

  https://www.raspberrypi.org/forums/viewtopic.php?p=1271713#p1271713

   

  I hope that the response given in the above thread helps and incites people, 
with far better and more knowledge of the processes and controllers involved, 
to pick up on this project and propose the parameters for a video-interface.

   

  As far as I understand, the driver loaded from the DVI re-maps the video 
controller of the M100 towards the one in the DVI, where new tekst and graphics 
are generated. The 4K memory in the schematics is obviously the video-RAM, 
where 40x16 text (640 bytes) and 240x128 points  (3840 bytes) reside. I suppose 
text and graphics do not reside in different memory locations. (because it 
doesn't fit...) 

   

  Anyway, contrary to what I thought before, we will probably need to activate 
the SCREEN 1, 1 directive with software on the M100 itself. But that software 
does not need to be as big as the original driver, because no disk-routines are 
necessary.

   

  I'm sorry if I sound presumptuous, and I apologise if I impose on people's 
limited time, but I think this is a project worth pursuing.

   

  (And I still didn't get an answer about the experiment I proposed, below.)

  Greetings from the TyRannoSaurus
  Jan-80 "
  @ work( @ @ )
  --.ooo--(_)--ooo.---

  From: VANDEN BOSSCHE JAN 
  Sent: vrijdag 9 februari 2018 09:47
  To: 'm...@bitchin100.com'
  Subject: RE: [M100] List of wanna haves

   

  .. .. (As I'm accessing this list from 2 different locations, 

  .. .. and my yahoo-postings aren't always visible to everyone, 

  .. .. I have repeated the question I send below)

   

  I'm sadly enough not that technical, so I can't draw the same conclusion from 
the link below. Can't that be confirmed from the ROM BASIC dis-assembly too? 
Without a DVI connected and drivers loaded, what does SCREEN 1,1 do ?

   

  Anyway, even if it is wrong: would it take a lot of effort to re-write only 
the display output portion of the DVI-drivers? That way, development could 
start on a software solution for the video-output via the system bus. I had 
thought of using the GPIO-pins of a Raspberry Pi for that. As the R.Pi can also 
emulate a TPDD, you'd have a virtual DVI replacement, there.

  Greetings from the TyRannoSaurus
  Jan-80 "
  @ work( @ @ )
  --.ooo--(_)--ooo.---

  From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Brian White
  Sent: vrijdag 9 februari 2018 01:59
  To: m...@bitchin100.com
  Subject: Re: [M100] List of wanna haves

   

  That won't work. I don't remember where I read this, but I read that the 
system rom has calls for certain functions but they are just stubs. The rom 
only contains the stub of a call that says "open CRT: for writing" which just 
says go to some address and do whatever that address says. Normally that 
address just points to the address for the built-in routine to return the FC? 
error. But if dvi dos is installed then that address contains the address of 
the routine in dvi dos to actually do something.

  Aha, here's where I read it. Start on page 257
  https://archive.org/details/InsideTheTrs80Model100

  I can try it when I get home but we already know.

  -- 

  bkw

   

   

   

  From: Jan Vanden Bossche [mailto:jan80...@yahoo.com] 

  > how would you use it?

   

  To have a bigger screen to work on, when not on the move. Imagine, a 17-inch 
old VGA monitor with 40 x 24 characters! HUGE!

   

  I have a question, for anybody having a DVI:

  Could you try the following: is it possible to operate a Model T hooked up to 
a DVI, with the DVI ready to accept input and disk commands, but the Model T 
without the driver software? I would think this is possible when you boot up 
both machines, establish the connection, and then, while connected, reset the 
Model so that it is no longer aware of it's 'companion'. At that moment, enter 
BASIC and type SCREEN 1,1. That would send all BASIC output to the DVI, right? 
Does it ? (thàt's the question)

   

  The above experiment would show if it's at all possible to run a monitor-only 
part of a DVI, without loading software on the Model T to do so. I hope, that 
the simple command SCREEN 1,1 does send some screen-positioning code through 
the bus towards the DVI, even without the drivers loaded on the Model T.  If it 
does, some clever programming on the receiving side could just give us the 
DVI/video-only device we seek.

   

  Greetin

Re: [M100] List of wanna haves

2018-02-13 Thread Mike Stein 
Playing devil's advocate...:



>...(And I still didn't get an answer about the experiment I proposed, below.)



And I haven't had an answer to what you want to do with it ;-)



I'm not aware of any software that uses the 80x25 screen mode, and redirecting 
the 8x40 display through the com port to a Pi or laptop etc. is trivial, so 
what makes this worth while (other than the challenge/fun) ?



m

  - Original Message - 
  From: VANDEN BOSSCHE JAN 
  To: m...@bitchin100.com 
  Sent: Tuesday, February 13, 2018 8:53 AM
  Subject: Re: [M100] List of wanna haves


   

  I have asked the Raspberry Pi community to help me with the construction of a 
DVI-like video-output device. I made the assumption that the DVI was only a 
terminal. Both from the response here, as there, I understand now that this 
combination is far more 'intimate' than I presumed.  

   

  https://www.raspberrypi.org/forums/viewtopic.php?p=1271713#p1271713

   

  I hope that the response given in the above thread helps and incites people, 
with far better and more knowledge of the processes and controllers involved, 
to pick up on this project and propose the parameters for a video-interface.

   

  As far as I understand, the driver loaded from the DVI re-maps the video 
controller of the M100 towards the one in the DVI, where new tekst and graphics 
are generated. The 4K memory in the schematics is obviously the video-RAM, 
where 40x16 text (640 bytes) and 240x128 points  (3840 bytes) reside. I suppose 
text and graphics do not reside in different memory locations. (because it 
doesn't fit...) 

   

  Anyway, contrary to what I thought before, we will probably need to activate 
the SCREEN 1, 1 directive with software on the M100 itself. But that software 
does not need to be as big as the original driver, because no disk-routines are 
necessary.

   

  I'm sorry if I sound presumptuous, and I apologise if I impose on people's 
limited time, but I think this is a project worth pursuing.

   

  (And I still didn't get an answer about the experiment I proposed, below.)

  Greetings from the TyRannoSaurus
  Jan-80 "
  @ work( @ @ )
  --.ooo--(_)--ooo.---

  From: VANDEN BOSSCHE JAN 
  Sent: vrijdag 9 februari 2018 09:47
  To: 'm...@bitchin100.com'
  Subject: RE: [M100] List of wanna haves

   

  .. .. (As I'm accessing this list from 2 different locations, 

  .. .. and my yahoo-postings aren't always visible to everyone, 

  .. .. I have repeated the question I send below)

   

  I'm sadly enough not that technical, so I can't draw the same conclusion from 
the link below. Can't that be confirmed from the ROM BASIC dis-assembly too? 
Without a DVI connected and drivers loaded, what does SCREEN 1,1 do ?

   

  Anyway, even if it is wrong: would it take a lot of effort to re-write only 
the display output portion of the DVI-drivers? That way, development could 
start on a software solution for the video-output via the system bus. I had 
thought of using the GPIO-pins of a Raspberry Pi for that. As the R.Pi can also 
emulate a TPDD, you'd have a virtual DVI replacement, there.

  Greetings from the TyRannoSaurus
  Jan-80 "
  @ work( @ @ )
  --.ooo--(_)--ooo.---

  From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Brian White
  Sent: vrijdag 9 februari 2018 01:59
  To: m...@bitchin100.com
  Subject: Re: [M100] List of wanna haves

   

  That won't work. I don't remember where I read this, but I read that the 
system rom has calls for certain functions but they are just stubs. The rom 
only contains the stub of a call that says "open CRT: for writing" which just 
says go to some address and do whatever that address says. Normally that 
address just points to the address for the built-in routine to return the FC? 
error. But if dvi dos is installed then that address contains the address of 
the routine in dvi dos to actually do something.

  Aha, here's where I read it. Start on page 257
  https://archive.org/details/InsideTheTrs80Model100

  I can try it when I get home but we already know.

  -- 

  bkw

   

   

   

  From: Jan Vanden Bossche [mailto:jan80...@yahoo.com] 

  > how would you use it?

   

  To have a bigger screen to work on, when not on the move. Imagine, a 17-inch 
old VGA monitor with 40 x 24 characters! HUGE!

   

  I have a question, for anybody having a DVI:

  Could you try the following: is it possible to operate a Model T hooked up to 
a DVI, with the DVI ready to accept input and disk commands, but the Model T 
without the driver software? I would think this is possible when you boot up 
both machines, establish the connection, and then, while connected, reset the 
Model so that it is no longer aware of it's 'companion'. At that moment, enter 
BASIC and type SCREEN 1,1. That would send all BASIC output to the DVI, right? 
Does it ? (thàt's the question)

   

  The above experiment would show if i

Re: [M100] List of wanna haves

2018-02-13 Thread Kevin Becker 
If you search the list archives for "TDock" it seems like there has already
been a lot of work done toward a similar solution.

On Tue, Feb 13, 2018 at 8:53 AM, VANDEN BOSSCHE JAN <
jan.vandenboss...@vivaqua.be> wrote:

>
>
> I have asked the Raspberry Pi community to help me with the construction
> of a DVI-like video-output device. I made the assumption that the DVI was
> only a terminal. Both from the response here, as there, I understand now
> that this combination is far more 'intimate' than I presumed.
>
>
>
> https://www.raspberrypi.org/forums/viewtopic.php?p=1271713#p1271713
>
>
>
> I hope that the response given in the above thread helps and incites
> people, with far better and more knowledge of the processes and controllers
> involved, to pick up on this project and propose the parameters for a
> video-interface.
>
>
>
> As far as I understand, the driver loaded from the DVI re-maps the video
> controller of the M100 towards the one in the DVI, where new tekst and
> graphics are generated. The 4K memory in the schematics is obviously the
> video-RAM, where 40x16 text (640 bytes) and 240x128 points  (3840 bytes)
> reside. I suppose text and graphics do not reside in different memory
> locations. (because it doesn't fit...)
>
>
>
> Anyway, contrary to what I thought before, we will probably need to
> activate the SCREEN 1, 1 directive with software on the M100 itself. But
> that software does not need to be as big as the original driver, because no
> disk-routines are necessary.
>
>
>
> I'm sorry if I sound presumptuous, and I apologise if I impose on people's
> limited time, but I think this is a project worth pursuing.
>
>
>
> (And I still didn't get an answer about the experiment I proposed, below.)
>
> Greetings from the TyRannoSaurus
> Jan-80 "
> @ work( @ @ )
> --.ooo--(_)--ooo.---
>
> *From:* VANDEN BOSSCHE JAN
> *Sent:* vrijdag 9 februari 2018 09:47
> *To:* 'm...@bitchin100.com'
> *Subject:* RE: [M100] List of wanna haves
>
>
>
> .. .. (As I'm accessing this list from 2 different locations,
>
> .. .. and my yahoo-postings aren't always visible to everyone,
>
> .. .. I have repeated the question I send below)
>
>
>
> I'm sadly enough not that technical, so I can't draw the same conclusion
> from the link below. Can't that be confirmed from the ROM BASIC
> dis-assembly too? Without a DVI connected and drivers loaded, what does
> SCREEN 1,1 do ?
>
>
>
> Anyway, even if it is wrong: would it take a lot of effort to re-write
> only the display output portion of the DVI-drivers? That way, development
> could start on a software solution for the video-output via the system bus.
> I had thought of using the GPIO-pins of a Raspberry Pi for that. As the
> R.Pi can also emulate a TPDD, you'd have a virtual DVI replacement, there.
>
> Greetings from the TyRannoSaurus
> Jan-80 "
> @ work( @ @ )
> --.ooo--(_)--ooo.---
>
> *From:* M100 [mailto:m100-boun...@lists.bitchin100.com
> ] *On Behalf Of *Brian White
> *Sent:* vrijdag 9 februari 2018 01:59
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] List of wanna haves
>
>
>
> That won't work. I don't remember where I read this, but I read that the
> system rom has calls for certain functions but they are just stubs. The rom
> only contains the stub of a call that says "open CRT: for writing" which
> just says go to some address and do whatever that address says. Normally
> that address just points to the address for the built-in routine to return
> the FC? error. But if dvi dos is installed then that address contains the
> address of the routine in dvi dos to actually do something.
>
> Aha, here's where I read it. Start on page 257
> https://archive.org/details/InsideTheTrs80Model100
>
> I can try it when I get home but we already know.
>
> --
>
> bkw
>
>
>
>
>
>
>
> *From:* Jan Vanden Bossche [mailto:jan80...@yahoo.com ]
>
>
> > how would you use it?
>
>
>
> To have a bigger screen to work on, when not on the move. Imagine, a
> 17-inch old VGA monitor with 40 x 24 characters! HUGE!
>
>
>
> I have a question, for anybody having a DVI:
>
> Could you try the following: is it possible to operate a Model T hooked up
> to a DVI, with the DVI ready to accept input and disk commands, but the
> Model T without the driver software? I would think this is possible when
> you boot up both machines, establish the connection, and then, while
> connected, reset the Model so that it is no longer aware of it's
> 'companion'. At that moment, enter BASIC and type SCREEN 1,1. That would
> send all BASIC output to the DVI, right? Does it ? (thàt's the question)
>
>
>
> The above experiment would show if it's at all possible to run a
> monitor-only part of a DVI, without loading software on the Model T to do
> so. I hope, that the simple command SCREEN 1,1 does send some
> screen-positioning code through the bus towards the DVI, even without the
> drivers loaded on the Model T.  If it does, som

Re: [M100] List of wanna haves

2018-02-13 Thread Lee Kelley 
Here is an article on the Mikrokolor which I don't think ever quite made it
to market.

http://www.trs-80.org/mikrokolor/

On Tue, Feb 13, 2018 at 7:53 AM, VANDEN BOSSCHE JAN <
jan.vandenboss...@vivaqua.be> wrote:

>
>
> I have asked the Raspberry Pi community to help me with the construction
> of a DVI-like video-output device. I made the assumption that the DVI was
> only a terminal. Both from the response here, as there, I understand now
> that this combination is far more 'intimate' than I presumed.
>
>
>
> https://www.raspberrypi.org/forums/viewtopic.php?p=1271713#p1271713
>
>
>
> I hope that the response given in the above thread helps and incites
> people, with far better and more knowledge of the processes and controllers
> involved, to pick up on this project and propose the parameters for a
> video-interface.
>
>
>
> As far as I understand, the driver loaded from the DVI re-maps the video
> controller of the M100 towards the one in the DVI, where new tekst and
> graphics are generated. The 4K memory in the schematics is obviously the
> video-RAM, where 40x16 text (640 bytes) and 240x128 points  (3840 bytes)
> reside. I suppose text and graphics do not reside in different memory
> locations. (because it doesn't fit...)
>
>
>
> Anyway, contrary to what I thought before, we will probably need to
> activate the SCREEN 1, 1 directive with software on the M100 itself. But
> that software does not need to be as big as the original driver, because no
> disk-routines are necessary.
>
>
>
> I'm sorry if I sound presumptuous, and I apologise if I impose on people's
> limited time, but I think this is a project worth pursuing.
>
>
>
> (And I still didn't get an answer about the experiment I proposed, below.)
>
> Greetings from the TyRannoSaurus
> Jan-80 "
> @ work( @ @ )
> --.ooo--(_)--ooo.---
>
> *From:* VANDEN BOSSCHE JAN
> *Sent:* vrijdag 9 februari 2018 09:47
> *To:* 'm...@bitchin100.com'
> *Subject:* RE: [M100] List of wanna haves
>
>
>
> .. .. (As I'm accessing this list from 2 different locations,
>
> .. .. and my yahoo-postings aren't always visible to everyone,
>
> .. .. I have repeated the question I send below)
>
>
>
> I'm sadly enough not that technical, so I can't draw the same conclusion
> from the link below. Can't that be confirmed from the ROM BASIC
> dis-assembly too? Without a DVI connected and drivers loaded, what does
> SCREEN 1,1 do ?
>
>
>
> Anyway, even if it is wrong: would it take a lot of effort to re-write
> only the display output portion of the DVI-drivers? That way, development
> could start on a software solution for the video-output via the system bus.
> I had thought of using the GPIO-pins of a Raspberry Pi for that. As the
> R.Pi can also emulate a TPDD, you'd have a virtual DVI replacement, there.
>
> Greetings from the TyRannoSaurus
> Jan-80 "
> @ work( @ @ )
> --.ooo--(_)--ooo.---
>
> *From:* M100 [mailto:m100-boun...@lists.bitchin100.com
> ] *On Behalf Of *Brian White
> *Sent:* vrijdag 9 februari 2018 01:59
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] List of wanna haves
>
>
>
> That won't work. I don't remember where I read this, but I read that the
> system rom has calls for certain functions but they are just stubs. The rom
> only contains the stub of a call that says "open CRT: for writing" which
> just says go to some address and do whatever that address says. Normally
> that address just points to the address for the built-in routine to return
> the FC? error. But if dvi dos is installed then that address contains the
> address of the routine in dvi dos to actually do something.
>
> Aha, here's where I read it. Start on page 257
> https://archive.org/details/InsideTheTrs80Model100
>
> I can try it when I get home but we already know.
>
> --
>
> bkw
>
>
>
>
>
>
>
> *From:* Jan Vanden Bossche [mailto:jan80...@yahoo.com ]
>
>
> > how would you use it?
>
>
>
> To have a bigger screen to work on, when not on the move. Imagine, a
> 17-inch old VGA monitor with 40 x 24 characters! HUGE!
>
>
>
> I have a question, for anybody having a DVI:
>
> Could you try the following: is it possible to operate a Model T hooked up
> to a DVI, with the DVI ready to accept input and disk commands, but the
> Model T without the driver software? I would think this is possible when
> you boot up both machines, establish the connection, and then, while
> connected, reset the Model so that it is no longer aware of it's
> 'companion'. At that moment, enter BASIC and type SCREEN 1,1. That would
> send all BASIC output to the DVI, right? Does it ? (thàt's the question)
>
>
>
> The above experiment would show if it's at all possible to run a
> monitor-only part of a DVI, without loading software on the Model T to do
> so. I hope, that the simple command SCREEN 1,1 does send some
> screen-positioning code through the bus towards the DVI, even without the
> drivers loaded on the Model T.  If it does, some cle

Re: [M100] VirtualT patch (for Ken Pettit really)

2018-02-13 Thread Bert Put 


On 02/12/2018 12:13 PM, Ken Pettit wrote:
> � This is a bit of work though, especially since I have to
> convert the source tree from CVS to git (sourceforge.net no longer
> accepts commits to the cvs repository).
> 
> Ken
> 

Hi Ken,

I'm wrestling with that decision here as well.  I have a whole slew of
CVS repos with many years of history in them (not in SF).  Perhaps SF
will do the conversion for you via their web interface?  The git book
points to a couple of command-line utilities but it is unclear how
successful the transfer of commit history, tags, etc. will be.

You ay just have to take the latest stable version, convert that branch
only and then move forward from there.

Regards,Bert

Re: [M100] List of wanna haves

2018-02-13 Thread VANDEN BOSSCHE JAN 

I have asked the Raspberry Pi community to help me with the construction of a 
DVI-like video-output device. I made the assumption that the DVI was only a 
terminal. Both from the response here, as there, I understand now that this 
combination is far more 'intimate' than I presumed.

https://www.raspberrypi.org/forums/viewtopic.php?p=1271713#p1271713

I hope that the response given in the above thread helps and incites people, 
with far better and more knowledge of the processes and controllers involved, 
to pick up on this project and propose the parameters for a video-interface.

As far as I understand, the driver loaded from the DVI re-maps the video 
controller of the M100 towards the one in the DVI, where new tekst and graphics 
are generated. The 4K memory in the schematics is obviously the video-RAM, 
where 40x16 text (640 bytes) and 240x128 points  (3840 bytes) reside. I suppose 
text and graphics do not reside in different memory locations. (because it 
doesn't fit...)

Anyway, contrary to what I thought before, we will probably need to activate 
the SCREEN 1, 1 directive with software on the M100 itself. But that software 
does not need to be as big as the original driver, because no disk-routines are 
necessary.

I'm sorry if I sound presumptuous, and I apologise if I impose on people's 
limited time, but I think this is a project worth pursuing.

(And I still didn't get an answer about the experiment I proposed, below.)
Greetings from the TyRannoSaurus
Jan-80 "
@ work( @ @ )
--.ooo--(_)--ooo.---
From: VANDEN BOSSCHE JAN
Sent: vrijdag 9 februari 2018 09:47
To: 'm...@bitchin100.com'
Subject: RE: [M100] List of wanna haves

.. .. (As I'm accessing this list from 2 different locations,
.. .. and my yahoo-postings aren't always visible to everyone,
.. .. I have repeated the question I send below)

I'm sadly enough not that technical, so I can't draw the same conclusion from 
the link below. Can't that be confirmed from the ROM BASIC dis-assembly too? 
Without a DVI connected and drivers loaded, what does SCREEN 1,1 do ?

Anyway, even if it is wrong: would it take a lot of effort to re-write only the 
display output portion of the DVI-drivers? That way, development could start on 
a software solution for the video-output via the system bus. I had thought of 
using the GPIO-pins of a Raspberry Pi for that. As the R.Pi can also emulate a 
TPDD, you'd have a virtual DVI replacement, there.
Greetings from the TyRannoSaurus
Jan-80 "
@ work( @ @ )
--.ooo--(_)--ooo.---
From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Brian White
Sent: vrijdag 9 februari 2018 01:59
To: m...@bitchin100.com
Subject: Re: [M100] List of wanna haves

That won't work. I don't remember where I read this, but I read that the system 
rom has calls for certain functions but they are just stubs. The rom only 
contains the stub of a call that says "open CRT: for writing" which just says 
go to some address and do whatever that address says. Normally that address 
just points to the address for the built-in routine to return the FC? error. 
But if dvi dos is installed then that address contains the address of the 
routine in dvi dos to actually do something.
Aha, here's where I read it. Start on page 257
https://archive.org/details/InsideTheTrs80Model100
I can try it when I get home but we already know.

--
bkw



From: Jan Vanden Bossche [mailto:jan80...@yahoo.com]
> how would you use it?

To have a bigger screen to work on, when not on the move. Imagine, a 17-inch 
old VGA monitor with 40 x 24 characters! HUGE!

I have a question, for anybody having a DVI:
Could you try the following: is it possible to operate a Model T hooked up to a 
DVI, with the DVI ready to accept input and disk commands, but the Model T 
without the driver software? I would think this is possible when you boot up 
both machines, establish the connection, and then, while connected, reset the 
Model so that it is no longer aware of it's 'companion'. At that moment, enter 
BASIC and type SCREEN 1,1. That would send all BASIC output to the DVI, right? 
Does it ? (thàt's the question)

The above experiment would show if it's at all possible to run a monitor-only 
part of a DVI, without loading software on the Model T to do so. I hope, that 
the simple command SCREEN 1,1 does send some screen-positioning code through 
the bus towards the DVI, even without the drivers loaded on the Model T.  If it 
does, some clever programming on the receiving side could just give us the 
DVI/video-only device we seek.

Greetings from the TyRannoSaurus
Jan-80


From: Mike Stein mailto:mhs.st...@gmail.com>>
To: m...@bitchin100.com
Sent: Thursday, 8 February 2018, 3:49
Subject: Re: [M100] List of wanna haves

Just curious: how would you use it?

m

- Original Message -
From: "Randy Kindig" m

Re: [M100] quick electronics question about AC adaptor port on M100

2018-02-13 Thread Brian White 
Yes the center pin is negative. Same is true for most of the related
accessories like the tape drives ctr-41, ctr-80, ccr-81, ccr-82, ccr-83,
the tpdd & tpdd2 disk drives, trp-100 printer, etc. They all take 6vdc,
center negative, same 5.5x2.1mm barrel plug.

-- 
bkw

On Feb 12, 2018 3:02 PM, "megarat"  wrote:

> Greetings again, folks.  Thanks for the feedback you gave me about digital
> audio recorders, it was very helpful.  I hope you don't mind another
> hopefully quick question.
>
> Some time ago I built an off-board power supply that could power my M100
> with 4 D-cell batteries by connecting them to the AC adaptor port.  (An
> idea suggested on this list.)  I had never actually tested it, and in
> hindsight, I'm not sure if I got the polarity correct when I wired the
> battery pack to the barrel connector.
>
> According to one of my documents, the official Tandy AC adaptor is listed
> as "center-negative" or "center-minus".  Does this mean that the terminal
> in the middle of the barrel should be wired to the negative wire on the
> battery pack?
>
> And to further indulge my curiosity, what would happen if I tried to use
> such a D-cell-based power supply if the polarity were reversed?
>
> Thanks again,
> CAM
>