Bitchin100 DocGarden - User contributions [en]

LaddieCon

2024-04-30T23:10:12Z

Jhoger: /* LaddieAlpha */

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

LaddieAlpha is a "cross platform" build of LaddieCon file service that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop
* Maps/fixes up filenames so you can load/save TXT, HTM, etc. files as .DO files
* Supports 8.3 filename format for use with Model T CP/M
* It supports TCP connections [[Connecting NEWDOS to Wimodem232]]

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download LaddieAlpha]

<pre>
.\LaddieAlpha.EXE COM1 6 [[-ext=xxxx|-win32|-baud=xxxxx|-resp=sz|-req=len|-ver]]
</pre>

By default, -ext is set to 2 which is the extension length for the Model T. The only other value of use is 3, for CP/M support 8.3 support.

-baud is for setting the baud rate. Default is 19200

-resp and -req are an experimental feature for setting larger packet sizes to increase throughput. -resp sets the maximum # bytes LaddieAlpha will read in file-write request. -req is the maximum length of a file-read reply from LaddieAlpha. You probably don't need these settings. You would need a special client (special TS-DOS, etc.) for compatibility

-win32 makes LaddieAlpha use the Win32 serial API directly through .NET Interop, rather than the Serial framework API. Sometimes I use this to see if a problem is in the Serial framework object. You probably don't need this option.

-ver is to print the version block. This will crash on some systems if the assembly needs/hasn't been granted permission to access its file metadata.

Example for CP/M support:

<pre>
.\LaddieAlpha.EXE COM1 8 -ext=3
</pre>

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

If your executable has execute permissions for your user / group, you can usually leave out invoking Mono, the shell will do it for you.

<pre>
./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

LaddieCon

2024-04-30T23:05:28Z

Jhoger: /* LaddieAlpha */

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

LaddieAlpha is a "cross platform" build of LaddieCon file service that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop
* Maps/fixes up filenames so you can load/save TXT, HTM, etc. files as .DO files
* Supports 8.3 filename format for use with Model T CP/M
* It supports TCP connections [[Connecting NEWDOS to Wimodem232]]

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download LaddieAlpha]

<pre>
.\LaddieAlpha.EXE COM1 6 [[-ext=xxxx|-win32|-baud=xxxxx|-resp=sz|-req=len]]
</pre>

By default, -ext is set to 2 which is the extension length for the Model T. The only other value of use is 3, for CP/M support 8.3 support.

-baud is for setting the baud rate. Default is 19200

-resp and -req are an experimental feature for setting larger packet sizes to increase throughput. -resp sets the maximum # bytes LaddieAlpha will read in file-write request. -req is the maximum length of a file-read reply from LaddieAlpha. You probably don't need these settings. You would need a special client (special TS-DOS, etc.) for compatibility

-win32 makes LaddieAlpha use the Win32 serial API directly through .NET Interop, rather than the Serial framework API. Sometimes I use this to see if a problem is in the Serial framework object. You probably don't need this option.

Example for CP/M support:

<pre>
.\LaddieAlpha.EXE COM1 8 -ext=3
</pre>

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

If your executable has execute permissions for your user / group, you can usually leave out invoking Mono, the shell will do it for you.

<pre>
./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

LaddieCon

2024-04-30T23:02:44Z

Jhoger: /* LaddieAlpha */

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

LaddieAlpha is a "cross platform" build of LaddieCon file service that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop
* Maps/fixes up filenames so you can load/save TXT, HTM, etc. files as .DO files
* Supports 8.3 filename format for use with Model T CP/M
* It supports TCP connections [[Connecting NEWDOS to Wimodem232]]

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download LaddieAlpha]

<pre>
.\LaddieAlpha.EXE COM1 6 [[-ext=xxxx|-win32|-baud=xxxxx|-resp=sz|-req=len]]
</pre>

By default, -ext is set to 2 which is the extension length for the Model T. The only other value of use is 3, for CP/M support 8.3 support.

-baud is for setting the baud rate.

-resp and -req are an experimental feature for setting larger packet sizes to increase throughput. -resp sets the maximum # bytes LaddieAlpha will read in file-write request. -req is the maximum length of a file-read reply from LaddieAlpha. You probably don't need these settings. You would need a special client (special TS-DOS, etc.) for compatibility

Example for CP/M support:

<pre>
.\LaddieAlpha.EXE COM1 8 -ext=3
</pre>

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

If your executable has execute permissions for your user / group, you can usually leave out invoking Mono, the shell will do it for you.

<pre>
./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

LaddieCon

2024-04-30T23:01:42Z

Jhoger: /* LaddieAlpha */

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

LaddieAlpha is a "cross platform" build of LaddieCon file service that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop
* Maps/fixes up filenames so you can load/save TXT, HTM, etc. files as .DO files
* Supports 8.3 filename format for use with Model T CP/M
* It supports TCP connections [[Connecting NEWDOS to Wimodem232]]

<pre>
.\LaddieAlpha.EXE COM1 6 [[-ext=xxxx|-win32|-baud=xxxxx|-resp=sz|-req=len]]
</pre>

By default, -ext is set to 2 which is the extension length for the Model T. The only other value of use is 3, for CP/M support 8.3 support.

-baud is for setting the baud rate.

-resp and -req are an experimental feature for setting larger packet sizes to increase throughput. -resp sets the maximum # bytes LaddieAlpha will read in file-write request. -req is the maximum length of a file-read reply from LaddieAlpha. You probably don't need these settings. You would need a special client (special TS-DOS, etc.) for compatibility

Example for CP/M support:

<pre>
.\LaddieAlpha.EXE COM1 8 -ext=3
</pre>

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download and test LaddieAlpha]

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

If your executable has execute permissions for your user / group, you can usually leave out invoking Mono, the shell will do it for you.

<pre>
./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

LaddieCon

2024-04-30T23:00:51Z

Jhoger: /* LaddieAlpha */

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

LaddieAlpha is a "cross platform" build of LaddieCon file service that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop
* Maps/fixes up filenames so you can load/save TXT, HTM, etc. files as .DO files
* Supports 8.3 filename format for use with Model T CP/M
* It supports TCP connections [[Connecting NEWDOS to Wimodem232]]

.\LaddieAlpha.EXE COM1 6 [[-ext=xxxx|-win32|-baud=xxxxx|-resp=sz|-req=len]]

By default, -ext is set to 2 which is the extension length for the Model T. The only other value of use is 3, for CP/M support 8.3 support.

-baud is for setting the baud rate.

-resp and -req are an experimental feature for setting larger packet sizes to increase throughput. -resp sets the maximum # bytes LaddieAlpha will read in file-write request. -req is the maximum length of a file-read reply from LaddieAlpha. You probably don't need these settings. You would need a special client (special TS-DOS, etc.) for compatibility

Example for CP/M support:

.\LaddieAlpha.EXE COM1 8 -ext=3

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download and test LaddieAlpha]

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

If your executable has execute permissions for your user / group, you can usually leave out invoking Mono, the shell will do it for you.

<pre>
./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

LaddieCon

2024-04-30T22:46:25Z

Jhoger:

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

LaddieAlpha is a"cross platform" build of LaddieCon that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop
* Supports 8.3 filename format for use with Model T CP/M

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download and test LaddieAlpha]

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

Peeking the Option ROM From a BASIC Program

2022-12-22T19:42:30Z

Jhoger:

The question came up on Facebook as to whether you can read the contents of an Option ROM from BASIC. The short answer is not really, or at least, not without some work.

Why? The 8085 has a 65536 byte address space. That space is apportioned between ROM at the bottom and RAM at the top. The 32K Option ROM, when enabled, occupies the same address space as the 32K main ROM. When the Option ROM is running, the BASIC ROM isn’t, and vice versa,, because all their jumps, internal data references and interrupt handlers are located to execute in the same space: the lower 32,768 bytes of the 8085 CPU’s address space. The upper 32K of the address space is permanently devoted to the RAM.

OK, well, BASIC has an OUT I/O routine and BASIC has a PEEK routine. To switch to the option ROM, you OUT 1 to I/O register 224. To switch back you OUT 0 to I/O register 224. So knowing just enough to get ourselves in trouble, a naive approach to PEEKing the option ROM would be:
OUT 224,1:?PEEK(0): OUT224,0
to print the first byte of the Option ROM, and because I'm almost clever, I of course switch back to the Main ROM at the end of it like a good BASIC citizen.

Workey? No. No workey.

The problem is that the BASIC interpreter will abruptly disappear with OUT 224,1. Boom. Poof. Gone. So the BASIC interpreter loop that executes your BASIC program line by line, token by token, will never get to anything after the first OUT... it will instead lock-up or, perhaps, crash spectacularly.

Because of that, I don't think there's any way to PEEK the option ROM from pure BASIC. But rather than let that hurdle stop us, instead, we need to contrive some machine code with no ROM dependencies and embed it in our BASIC program. This code will run completely from RAM, which always stays mapped in, so our code can swap the standard ROM out and the Option ROM in without causing a crash.

So we’re writing a machine language (ML) subroutine. We can interface ML with BASIC. BASIC gives us a way to invoke a ML subroutine, the “CALL” function. We will design a routine we can CALL, passing along the address of the Option ROM location we want, and get back the byte value that is at that offset in the Option ROM.

How does CALL work? The CALL statement takes three parameters: a subroutine entry point, an 8-bit parameter, and a 16-bit parameter. The subroutine is called, and the parameters are passed in the A and HL registers, respectively. At the end of the subroutine, CALL’ed code must effectuate return to the BASIC interpreter, leaving the stack as it found it.

Clearly, we need to pass the address to PEEK. The 16-bit parameter could be good for that. We don’t have any use for an 8-bit input to our subroutine. But what about passing back the byte "PEEKed"? That's an "out" parameter. It sure would have been great if Microsoft had made CALL return a 8 or 16-bit value.

But it is not so, and the BASIC ROM is literally etched in stone for many of our machines.

Oh well. No point in crying into our cereal about it... we just need to put our thinking caps back on. What we can do instead is pass a parameter array of integers as our 16-bit value. That is, instead of passing one value, we pass a value that refers (a reference) to a modifiable object.

A single array reference can convey an arbitrary number of values and pointers. And since we're passing a reference to the array object, the variables at each index of the array can be modified by the ML routine, supporting "in" and "out" parameters.

<pre>
DIM P%(2)
' P%(0): return value
P%(1) = 1000 : ' Address in Option ROM to peek
</pre>

So assuming our subroutine is at address PK% (we’ll get to that later), an invocation of our subroutine to find out what’s at address 1000 of the Option ROM would look like:

<pre>
P%(1) = 1000: CALL PK%, 0,VARPTR(P%(0)): ?P%(0)
</pre>

So now that we know what we want the routine to do and how we will invoke it, let's code it.

For each line I will show the assembly instruction, as well as the hex and what I call Funny Hex for each instruction. Funny Hex is like hex but ABCDEF are represented by :;<=>? , for simplified conversion. Any character in Funny Hex, you can subtract 48 (ASCII encoding of zero) and it will give you a value between 0 and 15

First I need to resolve a level of indirection on the value of HL to load the “address” parameter into the HL register.

<pre>
; HL starts as the address of the integer parameter array
; Load HL with param[1] since it's the address to peek
XCHG ; $EB >;
INX D ; $13 13 ; uh oh, need a listable alternative
INX D ; $13 13 ; again
LHLI ; $ED >=
</pre>

That was my first cut at that... and it would work, but $13 is an unprintable ASCII control character (^S / DC3/ XOFF). We have an opportunity here to craft code that can be embedded directly into a BASIC string, execute in place, and have no LIST or EDIT issues. That makes for much shorter BASIC code, with no "poke loop" overhead and no need to run from ALT-LCD. To do that, we need all instructions (and operands!) we use to be ASCII 32 (printable space) or higher.

So to avoid problems we instead:

<pre>
PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
</pre>

<pre>
; we're going to set the 224 ($E0) register to 1 to switch in the option rom
XRA A ; $AF :?
INR A ; $3C 3<

; disable interrupts so the hardware won't interrupt us. I’m not sure if this is actually necessary, since Option ROMs have their own interrupt handlers.
DI ; $F3 ?3

; Switch in the option ROM
OUT 224 ; $D3 $E0 / =3 >0

; L <- option ROM byte referenced by HL
MOV L,M ; $6E 6>

; Switch back to the standard ROM (same I/O register as we used to enable, but with A=0 instead of A=1)
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0

; restore interrupts
EI ; $FB ?;

; load the peeked value into HL (high byte is always zero)
XRA A ; $AF :?
MOV H,A ; $67 67

; Address of parameter array (references the first parameter) is on stack, restore it
POP D ; $D1 =1

; pass the peeked value as the return value
SHLI ; $D9 =9

; return to the BASIC interpreter
RET ; $C9 <9
</pre>

The full assembly:

PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
XRA A ; $AF :?
INR A ; $3C 3<
DI ; $F3 ?3
OUT 224 ; $D3 $E0 / =3 >0
MOV L,M ; $6E 6>
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0
EI ; $FB ?;
XRA A ; $AF :?
MOV H,A ; $67 67
POP D ; $D1 =1
SHLI ; $D9 =9
RET ; $C9 <9

That works out to 20 bytes of machine code.

Here’s a 7-bit ASCII encoded BASIC program that modifies an embedded string to hold the subroutine. Run it once, and it will do the work of converting the Funny Hex into a safe binary string (note I had to split the Funny Hex string to avoid a Mediawiki crash).

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="####################"
110 S=">52323>;>=:?3<"+"?3=3>06>:?=3>0?;:?67=1=9<9#"
112 K=256%
120 A=VARPTR(S)+1:A=PEEK(A)+K*(PEEK(A+1)+K*(PEEK(A+1)>127)):T="":C=0
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127))
126 E=D
130 C=PEEK(A)-48:IFC=-13GOTO160:ELSEC=16*C+PEEK(A+1)-48:T=T+CHR$(C):A=A+2:POKEE,C:E=E+1:GOTO 130
160 REM
</pre>

Run it and LIST it, and line 105 will now look like this:

[[File:OptROMPeek.png]]

Very compact… although we used a POKE loop to produce it (to avoid having to type graphic characters), you don’t need to keep the POKEr. Think of it as bootstrap, or a stage rocket. So now you can remove lines 110, 120, 126, 130, retaining the execute in place string ML and the CALL address computation.

Now to try it… add some test code:

<pre>
170 DIMP%(2)
180 P%(1)=3
190 CALL D,0,VARPTR(P%(0))
200 PRINTP%(0)
</pre>

This code declares a parameter array, sets the Option ROM address to peek to 3, and does the CALL. The PEEK’d value is returned in P%(0).

The full BASIC sample code:

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="####################"
110 S=">52323>;>=:?3<"+"?3=3>06>:?=3>0?;:?67=1=9<9#":K=256%
120 A=VARPTR(S)+1:A=PEEK(A)+K*(PEEK(A+1)+K*(PEEK(A+1)>127)):T="":C=0
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127)):E=D
130 C=PEEK(A)-48:IFC=-13GOTO160:ELSEC=16*C+PEEK(A+1)-48:T=T+CHR$(C):A=A+2:POKEE,C:E=E+1:GOTO 130
160 REM
170 DIMP%(2)
180 P%(1)=3
190 CALLD,0,VARPTR(P%(0))
200 PRINTP%(0)
</pre>

And the made code in Unicode, I guess:

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="å##ëí¯<óÓàn¯Óàû¯gÑÙÉ"
112 K=256%
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127))
160 REM
170 DIMP%(2)
180 P%(1)=3
190 CALLD,0,VARPTR(P%(0))
200 PRINTP%(0)
</pre>

Note that this code does seem to paste right into CloudT, CLOAD and run. There (to Unicode) and Back Again.

Other possible approaches would be to copy a whole 16-bit word from the Option ROM rather than just a byte at a time. Or even better, you could pass a source offset, a buffer address and size to copy from the Option ROM in one fell swoop. Or maybe you want the output already in hex, ready to display or dump out the serial port. I leave these enhancements as an exercise for the reader.

Also you may want to try building safe ML strings by hand. It’s possible! You will want to make a table for yourself of all the instruction opcodes, including a cheat sheet of how to type graphical characters. You can have a look at the [[8085_Reference]] for the full instruction set.

Peeking the Option ROM From a BASIC Program

2022-12-22T08:24:46Z

Jhoger:

The question came up on Facebook as to whether you can read the contents of an Option ROM from BASIC. The short answer is not really, or at least, not without some work.

Why? The 8085 has a 65536 byte address space. That space is apportioned between ROM at the bottom and RAM at the top. The 32K Option ROM, when enabled, occupies the same address space as the 32K main ROM. When the Option ROM is running, the BASIC ROM isn’t, and vice versa,, because they all their jumps, internal data references and interrupt handlers are located to execute in the same space: the lower 32,768 bytes of the 8085 CPU’s address space. The upper 32K of the address space is permanently devoted to the RAM.

OK, well, BASIC has an OUT I/O routine and BASIC has a PEEK routine. To switch to the option ROM, you OUT 1 to I/O register 224. To switch back you OUT 0 to I/O register 224. So knowing just enough to get ourselves in trouble, a naive approach to PEEKing the option ROM would be:
OUT 224,1:?PEEK(0): OUT224,0
to print the first byte of the Option ROM, and because I'm almost clever, I of course switch back to the Main ROM at the end of it like a good BASIC citizen.

Workey? No. No workey.

The problem is that the BASIC interpreter will abruptly disappear with OUT 224,1. Boom. Poof. Gone. So the BASIC interpreter loop that executes your BASIC program line by line, token by token, will never get to anything after the first OUT... it will instead lock-up or, perhaps, crash spectacularly.

Because of that, I don't think there's any way to PEEK the option ROM from pure BASIC. But rather than let that hurdle stop us, instead, we need to contrive some machine code with no ROM dependencies and embed it in our BASIC program. This code will run completely from RAM, which always runs from the same place, so it can swap the standard ROM out and the Option ROM in without causing a crash.

So we’re writing a machine language (ML) subroutine. We can interface ML with BASIC. BASIC gives us a way to invoke a ML subroutine, the “CALL” function. We will design a routine we can CALL, passing along the address of the Option ROM location we want, and get back the byte value that is at that offset in the Option ROM.

How does CALL work? The CALL statement takes three parameters: a subroutine entry point, an 8-bit parameter, and a 16-bit parameter. The subroutine is called, and the parameters are passed in the A and HL registers, respectively. At the end of the subroutine, CALL’ed code must effectuate return to the BASIC interpreter, leaving the stack as it found it!.

Clearly, we need to pass the address to PEEK. The 16-bit parameter could be good for that. We don’t have any use for an 8-bit input to our subroutine. But what about passing back the byte "PEEKed"? That's an "out" parameter. It sure would have been great if Microsoft had made CALL return a 8 or 16-bit value.

But it is not so, and the BASIC ROM is literally etched in stone for many of our machines.

Oh well. No point in crying into our cereal about it... we just need to put our thinking cap back on. What we can do instead is pass a parameter array of integers as our 16-bit value. That is, instead of passing one value, we pass a value that refers (a reference) to a modifiable object.

A single array reference can convey an arbitrary number of values and pointers. And since we're passing a reference to the array object, the variables at each index of the array can be modified by the ML routine.

<pre>
DIM P%(2)
' P%(0): return value
P%(1) = 1000 : ' Address in Option ROM to peek
</pre>

So assuming our subroutine is at address PK% (we’ll get to that later), an invocation of our subroutine to find out what’s at address 1000 of the Option ROM would look like:

<pre>
P%(1) = 1000: CALL PK%, VARPTR(P%(0)): ?P%(0)
</pre>

So now that we know what we want the routine to do, and how we will invoke it, let's code it.

For each line I will show the assembly instruction, as well as the hex and what I call Funny Hex for each instruction. Funny Hex is like hex but ABCDEF are represented by :;<=>? , for simplified conversion. Any character in Funny Hex, you can subtract 48 (ASCII encoding of zero) and it will give you a value between 0 and 15

First I need to get resolve a level of indirection on the value of HL to load the “address” parameter into the HL register.

<pre>
; HL starts as the address of the integer parameter array, in C-speak, &param[0]
; Load HL with param[1] since it's the address to peek
XCHG ; $EB >;
INX D ; $13 13 ; uh oh, need a listable alternative
INX D ; $13 13 ; again
LHLI ; $ED >=
</pre>

That was my first cut at that... and it would work, but $13 is an unprintable ASCII control character (^S / DC3/ XOFF). We have an opportunity here to craft code that can be embedded directly into a BASIC string, execute in place, and have no LIST or EDIT issues. That makes for much shorter BASIC code, with no "poke loop" overhead and no need to run from ALT-LCD. To do that, we need all instructions (and operands!) we use to be 32 (printable space) or higher.

So to avoid problems we instead:

<pre>
PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
</pre>

<pre>
; we're going to set the 224 ($E0) register to 1 to switch in the option rom
XRA A ; $AF :?
INR A ; $3C 3<

; disable interrupts so the hardware won't interrupt us. I’m not sure if this is actually necessary, since Option ROMs have their own interrupt handlers.
DI ; $F3 ?3

; Switch in the option ROM
OUT 224 ; $D3 $E0 / =3 >0

; L <- option ROM byte referenced by HL
MOV L,M ; $6E 6>

; Switch back to the standard ROM (same I/O register as we used to enable, but with A=0 instead of A=1)
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0

; restore interrupts
EI ; $FB ?;

; load the peeked value into HL (high byte is always zero)
XRA A ; $AF :?
MOV H,A ; $67 67

; Address of parameter array (references the first parameter) is on stack, restore it
POP D ; $D1 =1

; pass the peeked value as the return value
SHLI ; $D9 =9

; return to the BASIC interpreter
RET ; $C9 <9
</pre>

The full assembly:

PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
XRA A ; $AF :?
INR A ; $3C 3<
DI ; $F3 ?3
OUT 224 ; $D3 $E0 / =3 >0
MOV L,M ; $6E 6>
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0
EI ; $FB ?;
XRA A ; $AF :?
MOV H,A ; $67 67
POP D ; $D1 =1
SHLI ; $D9 =9
RET ; $C9 <9

That works out to 20 bytes of machine code.

Here’s a 7-bit ASCII encoded BASIC program that modifies an embedded string to hold the subroutine. Run it once, and it will do the work of converting the Funny Hex into a safe binary string (note I had to split the Funny Hex string to avoid a Mediawiki crash).

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="####################"
110 S=">52323>;>=:?3<"+"?3=3>06>:?=3>0?;:?67=1=9<9#"
112 K=256%
120 A=VARPTR(S)+1:A=PEEK(A)+K*(PEEK(A+1)+K*(PEEK(A+1)>127)):T="":C=0
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127))
126 E=D
130 C=PEEK(A)-48:IFC=-13GOTO160:ELSEC=16*C+PEEK(A+1)-48:T=T+CHR$(C):A=A+2:POKEE,C:E=E+1:GOTO 130
160 REM
</pre>

Run it and LIST it, and line 105 will now look like this:

[[File:OptROMPeek.png]]

Very compact… although we used a POKE loop to produce it (to avoid having to type graphic characters), you don’t need to keep the POKEr. Think of it as bootstrap, or a stage rocket. So now you can remove lines 110, 120, 126, 130, retaining the execute in place string ML and the CALL address computation.

Now to try it… add some test code:

<pre>
170 DIMP%(2)
180 P%(1)=3
190 CALL D,0,VARPTR(P%(0))
200 PRINTP%(0)
</pre>

This code declares a parameter array, sets the Option ROM address to peek to 3, and does the CALL. The PEEK’d value is returned in P%(0).

The full BASIC sample code:

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="####################"
110 S=">52323>;>=:?3<"+"?3=3>06>:?=3>0?;:?67=1=9<9#":K=256%
120 A=VARPTR(S)+1:A=PEEK(A)+K*(PEEK(A+1)+K*(PEEK(A+1)>127)):T="":C=0
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127)):E=D
130 C=PEEK(A)-48:IFC=-13GOTO160:ELSEC=16*C+PEEK(A+1)-48:T=T+CHR$(C):A=A+2:POKEE,C:E=E+1:GOTO 130
160 REM
170 DIMP%(2)
180 P%(1)=3
190 CALLD,0,VARPTR(P%(0))
200 PRINTP%(0)
</pre>

And the made code in Unicode, I guess:

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="å##ëí¯<óÓàn¯Óàû¯gÑÙÉ"
112 K=256%
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127))
160 REM
170 DIMP%(2)
180 P%(1)=3
190 CALLD,0,VARPTR(P%(0))
200 PRINTP%(0)
</pre>

Note that this code does seem to paste right into CloudT, CLOAD and run. There (to Unicode) and Back Again.

Other possible approaches would be to copy a whole 16-bit word from the Option ROM rather than just a byte at a time. Or even better, you could pass an source offset, a buffer address and size to copy from the Option ROM in one fell swoop. Or maybe you want the output already in hex, ready to display or dump out the serial port. I leave these enhancements as an exercise for the reader.

Also you may want to try building safe ML strings by hand. It’s possible! You will want to make a table for yourself of all the instruction opcodes, including a cheat sheet of how to type graphical characters. You can have a look at the [[8085_Reference]] for the full instruction set.

Peeking the Option ROM From a BASIC Program

2022-12-22T08:21:24Z

Jhoger:

The question came up on Facebook as to whether you can read the contents of an Option ROM from BASIC. The short answer is not really, or at least, not without some work.

Why? The 8085 has a 65536 byte address space. That space is apportioned between ROM at the bottom and RAM at the top. The 32K Option ROM, when enabled, occupies the same address space as the 32K main ROM. When the Option ROM is running, the BASIC ROM isn’t, and vice versa,, because they all their jumps, internal data references and interrupt handlers are located to execute in the same space: the lower 32,768 bytes of the 8085 CPU’s address space. The upper 32K of the address space is permanently devoted to the RAM.

OK, well, BASIC has an OUT I/O routine and BASIC has a PEEK routine. To switch to the option ROM, you OUT 1 to I/O register 224. To switch back you OUT 0 to I/O register 224. So knowing just enough to get ourselves in trouble, a naive approach to PEEKing the option ROM would be:
OUT 224,1:?PEEK(0): OUT224,0
to print the first byte of the Option ROM, and because I'm almost clever, I of course switch back to the Main ROM at the end of it like a good BASIC citizen.

Workey? No. No workey.

The problem is that the BASIC interpreter will abruptly disappear with OUT 224,1. Boom. Poof. Gone. So the BASIC interpreter loop that executes your BASIC program line by line, token by token, will never get to anything after the first OUT... it will instead lock-up or, perhaps, crash spectacularly.

Because of that, I don't think there's any way to PEEK the option ROM from pure BASIC. But rather than let that hurdle stop us, instead, we need to contrive some machine code with no ROM dependencies and embed it in our BASIC program. This code will run completely from RAM, which always runs from the same place, so it can swap the standard ROM out and the Option ROM in without causing a crash.

So we’re writing a machine language (ML) subroutine. We can interface ML with BASIC. BASIC gives us a way to invoke a ML subroutine, the “CALL” function. We will design a routine we can CALL, passing along the address of the Option ROM location we want, and get back the byte value that is at that offset in the Option ROM.

How does CALL work? The CALL statement takes three parameters: a subroutine entry point, an 8-bit parameter, and a 16-bit parameter. The subroutine is called, and the parameters are passed in the A and HL registers, respectively. At the end of the subroutine, CALL’ed code must effectuate return to the BASIC interpreter, leaving the stack as it found it!.

Clearly, we need to pass the address to PEEK. The 16-bit parameter could be good for that. We don’t have any use for an 8-bit input to our subroutine. But what about passing back the byte "PEEKed"? That's an "out" parameter. It sure would have been great if Microsoft had made CALL return a 8 or 16-bit value.

But it is not so, and the BASIC ROM is literally etched in stone for many of our machines.

Oh well. No point in crying into our cereal about it... we just need to put our thinking cap back on. What we can do instead is pass a parameter array of integers as our 16-bit value. That is, instead of passing one value, we pass a value that refers (a reference) to a modifiable object.

A single array reference can convey an arbitrary number of values and pointers. And since we're passing a reference to the array object, the variables at each index of the array can be modified by the ML routine.

<pre>
DIM P%(2)
' P%(0): return value
P%(1) = 1000 : ' Address in Option ROM to peek
</pre>

So assuming our subroutine is at address PK% (we’ll get to that later), an invocation of our subroutine to find out what’s at address 1000 of the Option ROM would look like:

<pre>
P%(1) = 1000: CALL PK%, VARPTR(P%(0)): ?P%(0)
</pre>

So now that we know what we want the routine to do, and how we will invoke it, let's code it.

For each line I will show the assembly instruction, as well as the hex and what I call Funny Hex for each instruction. Funny Hex is like hex but ABCDEF are represented by :;<=>? , for simplified conversion. Any character in Funny Hex, you can subtract 48 (ASCII encoding of zero) and it will give you a value between 0 and 15

First I need to get resolve a level of indirection on the value of HL to load the “address” parameter into the HL register.

<pre>
; HL starts as the address of the integer parameter array, in C-speak, &param[0]
; Load HL with param[1] since it's the address to peek
XCHG ; $EB >;
INX D ; $13 13 ; uh oh, need a listable alternative
INX D ; $13 13 ; again
LHLI ; $ED >=
</pre>

That was my first cut at that... and it would work, but $13 is an unprintable ASCII control character (^S / DC3/ XOFF). We have an opportunity here to craft code that can be embedded directly into a BASIC string, execute in place, and have no LIST or EDIT issues. That makes for much shorter BASIC code, with no "poke loop" overhead and no need to run from ALT-LCD. To do that, we need all instructions (and operands!) we use to be 32 (printable space) or higher.

So to avoid problems we instead:

<pre>
PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
</pre>

<pre>
; we're going to set the 224 ($E0) register to 1 to switch in the option rom
XRA A ; $AF :?
INR A ; $3C 3<

; disable interrupts so the hardware won't interrupt us. I’m not sure if this is actually necessary, since Option ROMs have their own interrupt handlers.
DI ; $F3 ?3

; Switch in the option ROM
OUT 224 ; $D3 $E0 / =3 >0

; L <- option ROM byte referenced by HL
MOV L,M ; $6E 6>

; Switch back to the standard ROM (same I/O register as we used to enable, but with A=0 instead of A=1)
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0

; restore interrupts
EI ; $FB ?;

; load the peeked value into HL (high byte is always zero)
XRA A ; $AF :?
MOV H,A ; $67 67

; Address of parameter array (references the first parameter) is on stack, restore it
POP D ; $D1 =1

; pass the peeked value as the return value
SHLI ; $D9 =9

; return to the BASIC interpreter
RET ; $C9 <9
</pre>

The full assembly:

PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
XRA A ; $AF :?
INR A ; $3C 3<
DI ; $F3 ?3
OUT 224 ; $D3 $E0 / =3 >0
MOV L,M ; $6E 6>
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0
EI ; $FB ?;
XRA A ; $AF :?
MOV H,A ; $67 67
POP D ; $D1 =1
SHLI ; $D9 =9
RET ; $C9 <9

That works out to 20 bytes of machine code.

Here’s a 7-bit ASCII encoded BASIC program that modifies an embedded string to hold the subroutine. Run it once, and it will do the work of converting the Funny Hex into a safe binary string (note I had to split the Funny Hex string to avoid a Mediawiki crash).

<pre>
100 DEFINT A-K:DEFSTR S-Z
105 U="####################"
110 S=">52323>;>=:?3<"+"?3=3>06>:?=3>0?;:?67=1=9<9#"
112 K=256%
120 A=VARPTR(S)+1:A=PEEK(A)+K*(PEEK(A+1)+K*(PEEK(A+1)>127)):T="":C=0
125 D=VARPTR(U)+1:D=PEEK(D)+K*(PEEK(D+1)+K*(PEEK(D+1)>127))
126 E=D
130 C=PEEK(A)-48:IFC=-13GOTO160:ELSEC=16*C+PEEK(A+1)-48:T=T+CHR$(C):A=A+2:POKEE,C:E=E+1:GOTO 130
160 REM
</pre>

Peeking the Option ROM From a BASIC Program

2022-12-22T08:05:52Z

Jhoger: Created page with "The question came up on Facebook as to whether you can read the contents of an Option ROM from BASIC. The short answer is not really, or at least, not without some work. Why?..."

The question came up on Facebook as to whether you can read the contents of an Option ROM from BASIC. The short answer is not really, or at least, not without some work.

Why? The 8085 has a 65536 byte address space. That space is apportioned between ROM at the bottom and RAM at the top. The 32K Option ROM, when enabled, occupies the same address space as the 32K main ROM. When the Option ROM is running, the BASIC ROM isn’t, and vice versa,, because they all their jumps, internal data references and interrupt handlers are located to execute in the same space: the lower 32,768 bytes of the 8085 CPU’s address space. The upper 32K of the address space is permanently devoted to the RAM.

OK, well, BASIC has an OUT I/O routine and BASIC has a PEEK routine. To switch to the option ROM, you OUT 1 to I/O register 224. To switch back you OUT 0 to I/O register 224. So knowing just enough to get ourselves in trouble, a naive approach to PEEKing the option ROM would be:
OUT 224,1:?PEEK(0): OUT224,0
to print the first byte of the Option ROM, and because I'm almost clever, I of course switch back to the Main ROM at the end of it like a good BASIC citizen.

Workey? No. No workey.

The problem is that the BASIC interpreter will abruptly disappear with OUT 224,1. Boom. Poof. Gone. So the BASIC interpreter loop that executes your BASIC program line by line, token by token, will never get to anything after the first OUT... it will instead lock-up or, perhaps, crash spectacularly.

Because of that, I don't think there's any way to PEEK the option ROM from pure BASIC. But rather than let that hurdle stop us, instead, we need to contrive some machine code with no ROM dependencies and embed it in our BASIC program. This code will run completely from RAM, which always runs from the same place, so it can swap the standard ROM out and the Option ROM in without causing a crash.

So we’re writing a machine language (ML) subroutine. We can interface ML with BASIC. BASIC gives us a way to invoke a ML subroutine, the “CALL” function. We will design a routine we can CALL, passing along the address of the Option ROM location we want, and get back the byte value that is at that offset in the Option ROM.

How does CALL work? The CALL statement takes three parameters: a subroutine entry point, an 8-bit parameter, and a 16-bit parameter. The subroutine is called, and the parameters are passed in the A and HL registers, respectively. At the end of the subroutine, CALL’ed code must effectuate return to the BASIC interpreter, leaving the stack as it found it!.

Clearly, we need to pass the address to PEEK. The 16-bit parameter could be good for that. We don’t have any use for an 8-bit input to our subroutine. But what about passing back the byte "PEEKed"? That's an "out" parameter. It sure would have been great if Microsoft had made CALL return a 8 or 16-bit value.

But it is not so, and the BASIC ROM is literally etched in stone for many of our machines.

Oh well. No point in crying into our cereal about it... we just need to put our thinking cap back on. What we can do instead is pass a parameter array of integers as our 16-bit value. That is, instead of passing one value, we pass a value that refers (a reference) to a modifiable object.

A single array reference can convey an arbitrary number of values and pointers. And since we're passing a reference to the array object, the variables at each index of the array can be modified by the ML routine.

<pre>
DIM P%(2)
' P%(0): return value
P%(1) = 1000 : ' Address in Option ROM to peek
</pre>

So assuming our subroutine is at address PK% (we’ll get to that later), an invocation of our subroutine to find out what’s at address 1000 of the Option ROM would look like:

<pre>
P%(1) = 1000: CALL PK%, VARPTR(P%(0)): ?P%(0)
</pre>

So now that we know what we want the routine to do, and how we will invoke it, let's code it.

For each line I will show the assembly instruction, as well as the hex and what I call Funny Hex for each instruction. Funny Hex is like hex but ABCDEF are represented by :;<=>? , for simplified conversion. Any character in Funny Hex, you can subtract 48 (ASCII encoding of zero) and it will give you a value between 0 and 15

First I need to get resolve a level of indirection on the value of HL to load the “address” parameter into the HL register.

<pre>
; HL starts as the address of the integer parameter array, in C-speak, &param[0]
; Load HL with param[1] since it's the address to peek
XCHG ; $EB >;
INX D ; $13 13 ; uh oh, need a listable alternative
INX D ; $13 13 ; again
LHLI ; $ED >=
</pre>

That was my first cut at that... and it would work, but $13 is an unprintable ASCII control character (^S / DC3/ XOFF). We have an opportunity here to craft code that can be embedded directly into a BASIC string, execute in place, and have no LIST or EDIT issues. That makes for much shorter BASIC code, with no "poke loop" overhead and no need to run from ALT-LCD. To do that, we need all instructions (and operands!) we use to be 32 (printable space) or higher.

So to avoid problems we instead:

<pre>
PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
</pre>

<pre>
; we're going to set the 224 ($E0) register to 1 to switch in the option rom
XRA A ; $AF :?
INR A ; $3C 3<

; disable interrupts so the hardware won't interrupt us. I’m not sure if this is actually necessary, since Option ROMs have their own interrupt handlers.
DI ; $F3 ?3

; Switch in the option ROM
OUT 224 ; $D3 $E0 / =3 >0

; L <- option ROM byte referenced by HL
MOV L,M ; $6E 6>

; Switch back to the standard ROM (same I/O register as we used to enable, but with A=0 instead of A=1)
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0

; restore interrupts
EI ; $FB ?;

; load the peeked value into HL (high byte is always zero)
XRA A ; $AF :?
MOV H,A ; $67 67

; Address of parameter array (references the first parameter) is on stack, restore it
POP D ; $D1 =1

; pass the peeked value as the return value
SHLI ; $D9 =9

; return to the BASIC interpreter
RET ; $C9 <9
</pre>

The full assembly:

PUSH H ; $E5 >5
INX H ; $23 23
INX H ; $23 23
XCHG ; $EB >;
LHLI ; $ED >=
XRA A ; $AF :?
INR A ; $3C 3<
DI ; $F3 ?3
OUT 224 ; $D3 $E0 / =3 >0
MOV L,M ; $6E 6>
XRA A ; $AF :?
OUT 224 ; $D3 $E0 / =3 >0
EI ; $FB ?;
XRA A ; $AF :?
MOV H,A ; $67 67
POP D ; $D1 =1
SHLI ; $D9 =9
RET ; $C9 <9

That works out to 20 bytes of machine code.

Here’s a 7-bit ASCII encoded BASIC program that modifies an embedded string to hold the subroutine. Run it once, and it will do the work of converting the Funny Hex into a safe binary string.

File:OptROMPeek.png

2022-12-22T08:02:25Z

Jhoger: ML Program to PEEK the Option ROM

ML Program to PEEK the Option ROM

NEC 8508A

2020-06-27T03:29:26Z

Jhoger: Jhoger moved page NEC 8508A to NEC 8508A RAM/ROM Cartridge

#REDIRECT [[NEC 8508A RAM/ROM Cartridge]]

NEC 8508A RAM/ROM Cartridge

2020-06-27T03:29:26Z

Jhoger: Jhoger moved page NEC 8508A to NEC 8508A RAM/ROM Cartridge

ROM/RAM Cartridge for NEC 8500

Can be powered by coin cell or adapter.

[[File:NEC_8508A_ROM_Slots.jpeg|500px]]

[[File:Nec8508a_battery_port.jpg|500px]]

NEC 8508A RAM/ROM Cartridge

2020-06-27T03:29:08Z

Jhoger:

ROM/RAM Cartridge for NEC 8500

Can be powered by coin cell or adapter.

[[File:NEC_8508A_ROM_Slots.jpeg|500px]]

[[File:Nec8508a_battery_port.jpg|500px]]

File:Nec8508a battery port.jpg

2020-06-27T03:27:31Z

Jhoger: Picture of battery port area of NEC 8508a RAM/ROM cartridge

Picture of battery port area of NEC 8508a RAM/ROM cartridge

NEC 8508A RAM/ROM Cartridge

2020-06-27T03:26:18Z

Jhoger:

ROM/RAM Cartridge for NEC 8500

Can be powered by coin cell or adapter.

[[File:NEC_8508A_ROM_Slots.jpeg|500px]]

File:NEC 8508A ROM Slots.jpeg

2020-06-27T03:24:02Z

Jhoger: Picture of rom slots in NEC 8508A ROM/RAM cartridge

Picture of rom slots in NEC 8508A ROM/RAM cartridge

NEC 8508A RAM/ROM Cartridge

2020-06-27T03:23:25Z

Jhoger: Created page with "ROM/RAM Cartridge for NEC 8500 Can be powered by coin cell or adapter. File:NEC_8508A_ROM_Slots.jpeg"

ROM/RAM Cartridge for NEC 8500

Can be powered by coin cell or adapter.

[[File:NEC_8508A_ROM_Slots.jpeg]]

Connecting NEWDOS to Wimodem232

2020-03-29T08:17:36Z

Jhoger: /* Overview */

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

[http://www.club100.org/memfiles/index.php?&direction=0&order=&directory=Ken%20Pettit/NewDos/VER5.05 NEWDOS 5.05]

== Steps ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

Note that you don't HAVE to do this. But, say you need to inject a TPDD client like TEENY. To do that without running a Telnet server on my PC, I used Putty to Telnet to the Wimodem232, to the Model T at 600 baud. Then anything I paste into the Putty session is received by the Model T. In one case I used the Download function in TELCOM to capture TEENYX.DO into a file, which I then loaded into BASIC. But to do that, I needed to be at 600 baud and I needed to know the IP address of the Wimodem232.

If you don't care to connect TO the Wimodem, and already have your TPDD client loaded, you can skip to step 5.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

== Quick Launch ==

Here's a small launcher program to make connection easier. This avoids having to go into TELCOM and remember any commands.
Remember though, it expects the WiModem232 to already be in 19200bps mode.

<pre>
Type in the following, using your listener's IP and port:

10 OPEN"COM:98N1E"FOROUTPUTAS1:PRINT#1,"
ATDT 192.168.1.85:8085":CLOSE1:CALL63013
,2,2:MENU

SAVE"DIAL"
</pre>

Then when you want to connect to the TCP listener and launch TS-DOS, just put the widebar cursor over DIAL.BA and hit ENTER

Connecting NEWDOS to Wimodem232

2020-03-29T05:45:03Z

Jhoger:

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

== Steps ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

Note that you don't HAVE to do this. But, say you need to inject a TPDD client like TEENY. To do that without running a Telnet server on my PC, I used Putty to Telnet to the Wimodem232, to the Model T at 600 baud. Then anything I paste into the Putty session is received by the Model T. In one case I used the Download function in TELCOM to capture TEENYX.DO into a file, which I then loaded into BASIC. But to do that, I needed to be at 600 baud and I needed to know the IP address of the Wimodem232.

If you don't care to connect TO the Wimodem, and already have your TPDD client loaded, you can skip to step 5.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

== Quick Launch ==

Here's a small launcher program to make connection easier. This avoids having to go into TELCOM and remember any commands.
Remember though, it expects the WiModem232 to already be in 19200bps mode.

<pre>
Type in the following, using your listener's IP and port:

10 OPEN"COM:98N1E"FOROUTPUTAS1:PRINT#1,"
ATDT 192.168.1.85:8085":CLOSE1:CALL63013
,2,2:MENU

SAVE"DIAL"
</pre>

Then when you want to connect to the TCP listener and launch TS-DOS, just put the widebar cursor over DIAL.BA and hit ENTER

Connecting NEWDOS to Wimodem232

2020-03-29T05:40:12Z

Jhoger:

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

== Steps ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

Note that you don't HAVE to do this. But, say you need to inject a TPDD client like TEENY. To do that without running a Telnet server on my PC, I used Putty to Telnet to the Wimodem232, to the Model T at 600 baud. Then anything I paste into the Putty session is received by the Model T. In one case I used the Download function in TELCOM to capture TEENYX.DO into a file, which I then loaded into BASIC. But to do that, I needed to be at 600 baud and I needed to know the IP address of the Wimodem232.

If you don't care to connect TO the Wimodem, and already have your TPDD client loaded, you can skip to step 5.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

== Quick Launch ==

Here's a small launcher program to make connection easier.

<pre>
Type in the following, using your listener's IP and port:

10 OPEN"COM:98N1E"FOROUTPUTAS1:PRINT#1,"
ATDT 192.168.1.85:8085":CLOSE1:CALL63013
,2,2:MENU

SAVE"DIAL"
</pre>

Then when you want to connect to the TCP listener and launch TS-DOS, just put the widebar cursor over DIAL.BA and hit ENTER

Connecting NEWDOS to Wimodem232

2020-03-29T02:21:53Z

Jhoger: /* Steps */

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

== Steps ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

Note that you don't HAVE to do this. But, say you need to inject a TPDD client like TEENY. To do that without running a Telnet server on my PC, I used Putty to Telnet to the Wimodem232, to the Model T at 600 baud. Then anything I paste into the Putty session is received by the Model T. In one case I used the Download function in TELCOM to capture TEENYX.DO into a file, which I then loaded into BASIC. But to do that, I needed to be at 600 baud and I needed to know the IP address of the Wimodem232.

If you don't care to connect TO the Wimodem, and already have your TPDD client loaded, you can skip to step 5.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

Connecting NEWDOS to Wimodem232

2020-03-29T02:21:38Z

Jhoger: /* Steps */

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

== Steps ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

Note that you don't HAVE to do this. But, say you need to inject a TPDD client like TEENY. To do that without running a Telnet server on my PC, I used Putty to Telnet to the Wimodem232, to the Model T at 600 baud. Then anything I paste into the Putty session is received by the Model T. In one case I used the Download function in TELCOM to capture TEENYX.DO into a file, which I then loaded into BASIC. But to do that, I needed to be at 600 baud and I needed to know the IP address of the Wimodem232.

If you don't care to connect TO the Wimodem, and already gave your TPDD client loaded, you can skip to step 5.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

Connecting NEWDOS to Wimodem232

2020-03-29T02:20:17Z

Jhoger: /* Preparation */

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

== Steps ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

Note that you don't HAVE to do this. But, say you need to inject a TPDD client like TEENY. To do that without running a Telnet server on my PC, I used Putty to Telnet to the Wimodem232, to the Model T at 600 baud. Then anything I paste into the Putty session is received by the Model T. In one case I used the Download function in TELCOM to capture TEENYX.DO into a file, which I then loaded into BASIC. But to do that, I needed to be at 600 baud and I needed to know the IP address of the Wimodem232.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

Connecting NEWDOS to Wimodem232

2020-03-29T01:30:10Z

Jhoger: Created page with " == Overview == There are various RS232 to Wifi dongles around now. They allow you to establish a TCP connection to a PC from your Model T serial port. LaddieAlpha offers a ..."

== Overview ==

There are various RS232 to Wifi dongles around now.
They allow you to establish a TCP connection to a PC from your Model T serial port.

LaddieAlpha offers a TCP listening mode to support direct connections. But any TPDD emulator, or a real TPDD can work if you
have enough software to rig it up.

This article describes how to connect NEWDOS -> Wimodem232 -> LaddieAlpha in TCP mode.

== Preparation ==

1. Update firmware on Wimodem232. Be aware that the Wimodem232 may switch baud rates, generally to 300 baud after this and you need to change baud rates in TELCOM to match.

2. Up the baud on Wimodm232 to 600 baud. This is the fastest baud TELCOM can interact with Wimodem and not lose characters.

<pre>
AT<ENTER>
OK
AT*B600
OK
</pre>

3. Re-enter TELCOM at 600 baud

<pre>
Stat 48N1D
Term
AT
OK
</pre>

4. Determine your IP address

<pre>
ATI
...
IP:192.168.1.66
...
</pre>

Note down your IP address.

5. Switch baud to 19200bps for TPDD mode

<pre>
AT*B19200
OK
</pre>

6. Re-enter TELCOM at 19200bps

<pre>
F8 (Bye)
Disconnect? Y
Stat 98N1D
Term
AT
OK
</pre>

7. Launch LaddieAlpha.EXE

With a command prompt open, and from whatever directory you have a copy of LaddieAlpha, run it in tcp listener mode

<pre>
.\LaddieAlpha.EXE tcp://*:8085
</pre>

This means, listen on all IP addresses at port 8085.
You can pick any unprivileged port, you can give a specific IP address.
Note: network security best practices and configuring your firewall is out of scope for this article. Depending on your operating system, you will need to ALLOW the inbound TCP connection on port 8085. Otherwise you will simply find the Wimodem232 is unable to connect.

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
</pre>

8. Find the IP address of your PC

On Windows, use ipconfig, Linux, ifconfig, etc.

In my case it was 192.168.1.85

9. Dial LaddieAlpha

<pre>
ATDT 192.168.1.85:8085
CONNECT
</pre>

<pre>
C:\projects\modelt\laddiealpha > .\LaddieAlpha.EXE tcp://*:8085
================================================================================
LaddieAlpha Tandy Portable Disk Drive Emulator (Speaker To Machines, Inc.)
Built : 3/28/2020 2:08:10 PM
File Version : 2.1.0.0
Version : 2.1.0.0
Copyright : Copyright c Speaker To Machines, Inc. 2014
Working Dir : C:\projects\modelt\laddiealpha
================================================================================
Configure listener
Waiting for TCP connection...
Connected
</pre>

10. Launch NEWDOS in appropriate delay mode:

<pre>
BASIC
CALL 63012,2,2
F4 (Disk)
</pre>

Note that I sometimes have issues where this gets stuck.
Generally to fix I exit NEWDOS, go into TELCOM, Stat 98N1D, Term, F8-Bye, and re-launch NEWDOS with CALL 63012,2,2 and this resolves the handshake issue.

Note Note: to run NEWDOS in delay mode, you have to use the CALL every time. Launching from TS-DOS entry on the menu will start with no delay, and it won't work!

There is information in Ken's documentation on how to change the TS-DOS launcher to incorporate the delay.

TPDD Base Protocol

2019-12-12T23:17:41Z

Jhoger: /* General Reference */

== General Reference ==

Note that this information was taken from Compuserve archives. Some stuff has been fixed. The best way to understand the protocol is to look at existing code like LaddieAlpha or DLPlus.

If you have changes please suggest or make them.

<UL>
<LI>Disks are single sided 3.5 inch standard disks</LI>
<LI>PDD1 - 40 tracks 2 sectors 1280 bytes/sector (100K/disk)</LI>
<LI>PDD2 - 80 tracks 2 sectors 1280 bytes/sector (200K/disk treated as two banks of 100k
each)</LI>
<LI>Maximum file size = 64k. </LI>
<LI>Maximum number of directory entries (files) is 40 for PDD1 and 80 for PDD2.</LI>
<LI>File names are maximum 24 characters (padded with trailing blanks) although Tandy always
used 6 for filename and 2 for filetype, with period seperator (i.e. XXXXXX.TT)</LI>
<LI>All communications with drive are at 19,200 bps. PDD1 has dip switches so this can drop
to 9600bps. PDD2 is auto sensing down to 1200bps (??? - can anyone confirm this?).</LI>
</UL>

== Command Format ==

All commands are in a request/return format (half-duplex)

General request format:

<BLOCKQUOTE>
<TT>preamble type length data checksum</TT>
</BLOCKQUOTE>

General return format:

<BLOCKQUOTE>
<TT>type length data checksum</TT>
</BLOCKQUOTE>

== Command Type ==

(all values are in HEX)

{| WIDTH="100%" BORDER="1"
!  command
!  request
!  return
|-
|  directory ref
|  00
|  11 12
|-
|  open file
|  01
|  12
|-
|  close file
|  02
|  12
|-
|  read file
|  03
|  10 12
|-
|  write file
|  04
|  12
|-
|  delete file
|  05
|  12
|-
|  format disk
|  06 *
|  12
|-
|  drive status
|  07 *
|  12
|-
|  drive condition
|  0C *
|  15
|-
|   rename file
|  0D
|  12
|}

* PDD2 treats the disk as two banks of 100k each. All commands except these two must
specify the bank number as part of the request. The above commands reference BANK 0. To
reference BANK 1 you must add 40 HEX to these values (bit 6 = bank number). E.G. 'open
file' becomes 41 for BANK 1.

== Request Command details ==

=== Type 00 - Directory Reference ===

<PRE> 2 1 1 24 1 1 1 bytes
+----+--+--+--------------+----------+------------+------+
|5a5a|00|1a| filename |attribute |search form |chksum|
+----+--+--+--------------+----------+------------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 00h*
* length - length of data 1ah (26 decimal)
* filename - padded with blanks
* attribute - specify 'F' (not used normally)
* search form

<BLOCKQUOTE>
* 00h - reference file for open or delete
* 01h - request first directory block
* 02h - request next directory block
* 03h - request previous directory block
* 04h - end directory reference
</BLOCKQUOTE>

checksum - see below for calculating

=== Type 01 - Open file ===

<PRE> 2 1 1 1 1 bytes
+----+--+--+------+------+
|5a5a|01|01| mode |chksum|
+----+--+--+------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 01h
* length - length of data 01h (1 decimal)
* mode -

<BLOCKQUOTE>
* 01h - open new file for WRITE
* 02h - open existing file for APPEND
* 03h - open existing file for READ
</BLOCKQUOTE>

checksum - see below for calculating

=== Type 02 - Close file ===

<PRE> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|02|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 02h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 03 - Read file ===

<pre> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|03|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 03h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 04 - Write file ===

<PRE> 2 1 1 1-128 1 bytes
+----+--+---+------+------+
|5a5a|04|01-|data |chksum|
| | | 80| | |
+----+--+---+------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 04
* length - length of data 01h-80h (actual length of data)
* checksum - see below for calculating

=== Type 05 - Delete file ===

<PRE> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|05|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 05h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 06 - Format Disk ===

<PRE> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|06|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 06h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 07 - Drive Status ===
<PRE>
2 1 1 1 bytes<
+----+--+--+------+
|5a5a|07|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 07h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 0C - Drive Condition ===
<PRE>
2 1 1 1 bytes
+----+--+--+------+
|5a5a|0C|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 0Ch
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 0D - Rename file ===
<PRE>
2 1 1 24 1 1 bytes<
+----+--+--+-------+------+------+
|5a5a|0D|19|newname|attrib|chksum|
+----+--+--+-------+------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 0D
* length - length of data 19h (25 decimal)
* newname - new name for the file
* attribute- not used (specify 'F')
* checksum - see below for calculating

== Return Command Details ==
=== Type 10 - Read file Return ===
<PRE>
1 1 0-128 1 bytes
+--+---+----------+-----+
|10|00-| file data|cksum|
| | 80| |cksum|
+--+---+----------+-----+</PRE>

* return - type 10
* length - length of data 00h-80h (0-128 decimal)<UL><LI>if length is equal to 80h there may be more data - you must issue another read command</LI><LI>if length is less than 80h then this is last block</LI></UL>
* file data - data read from file
* checksum - see below for calculating

=== Type 11 - Directory reference return ===
<PRE>
1 1 24 1 2 1 1 bytes
+--+--+--------+------+----+----+-----+
|11|1c|filename|attrib|size|free|cksum|
+--+--+--------+------+----+----+-----+</PRE>

* return - type 11h
* length - length of data 1Ch (28 decimal)
* filename - file name - if no name specied is 00H. If at end of directory is 00H.
* attribute - not used
* size - size of file, big endian format
* free - number of free sectors (multiply by 1280 for bytes)
* checksum - see below for calculating

=== Type 12 - Normal Return ===
<PRE> 1 1 1 1 bytes
+--+--+-----+-----+
|12|01|error|cksum|
+--+--+-----+-----+</PRE>

* return - type 12h
* length - length of data 01h
* error code-

{| WIDTH="100%" BORDER="1"
|  00 - normal (no error)
|  10 - file does not exist
|  11 - file exists
|-
|  30 - no filename
|  31 - dir search error
|  35 - bank error
|-
|  36 - parameter error
|  37 - open format mismatch
|  3f - end of file
|-
|  40 - no start mark
|  41 - crc check error in ID
|  42 - sector length error
|-
|  44 - format verify error
|  46 - format interruption
|  47 - erase offset error
|-
|  49 - crc check error in data
|  4a - sector number error
|  4b - read data timeout
|-
|  4d - sector number error
|  50 - disk write protect
|  5e - un-initilized disk
|-
|  60 - directory full
|  61 - disk full
|  6e - file too long
|-
|  70 - no disk
|  71 - disk change error
|  
|}

* checksum - see below for calculating

=== Type 15 - Drive Condition Return ===
<PRE>
1 1 1 1 bytes
+--+--+---------+-----+
|15|01|condition|cksum|
+--+--+---------+-----+</PRE>

* return - type 15h
* length - length of data 01h
* condition- bit values

<PRE> 7 6 5 4 3 2 1 0 bit
+-+-+-+-+-+-+-+-+
MSB |0|0|0|0|x|x|x|x| LSB
+-+-+-+-+-+-+-+-+
| | | |
| | | +--power (0=normal 1=low)
| | +----write protect (0=not prot 1=prot)
| +------disk out (0=disk in 1=disk out)
+--------disk change status (0=not changed 1=changed)</PRE>
* checksum - see below for calculating

<H2>Sequence of Events</H2>
{| WIDTH="100%"
|  Get directory
| req 00 search form 01 
req 00 search form 02 (repeat as needed)
|-
|  Write file
| req 00 search form 00 
req 01 mode 01 or 02 
req 04 (repeat as needed) 
req 02
|-
|  Read file
| req 00 search form 00 
req 01 mode 03 
req 03 (repeat as needed) 
req 02
|-
|  Rename file
| req 00 search form 00 
req 0d
|-
|  Delete file
|  req 00 search form 00 
req 05
|}<HR>

<H2>Calculating Checksum</H2>The check sum is "the one's complement of the least significant byte of the number
of bytes from the block format through the data block". Most people (me included)
don't understand what that involves if you have to calculate it. Fortunately I found an
example of how to do this and so I'm passing it on to you.Checksum=(sum-of-bytes MOD 256) XOR 255where bytes = the bytes including the Request Type, Length and all Data fields
(but not including the preamble).<HR><H2>Using this Information</H2>A lot of the above commands can be set up in advance since there is no variable part to
calculate. Some commands must have the length and checksum calculate as the data is built
but the others don't. Here's how I set up some of the commands in my program:

<pre>
Close$ = "ZZ"+Chr$(2)+Chr$(0)+Chr$(253)
Dir1$ = "ZZ"+Chr$(0)+Chr$(26)+Space$(24)+"F"+Chr$(1)+Chr$(158)
Dir2$ = "ZZ"+Chr$(0)+Chr$(26)+Space$(24)+"F"+Chr$(2)+Chr$(157)
Status$ = "ZZ"+Chr$(7)+Chr$(0)+Chr$(248)+Chr$(13)
Format$ = "ZZ"+Chr$(6)+Chr$(0)+Chr$(249)+Chr$(13)
Erase$ = "ZZ"+Chr$(5)+Chr$(0)+Chr$(250)
Seek$(1) = "ZZ"+Chr$(1)+Chr$(1)+Chr$(1)+Chr$(252)
Seek$(2) = "ZZ"+Chr$(1)+Chr$(1)+Chr$(2)+Chr$(251)
Seek$(3) = "ZZ"+Chr$(1)+Chr$(1)+Chr$(3)+Chr$(250)
</pre>

The above commands can be sent directly without any calculating to speed up your
program. 

[[Category:Model T Developer Reference]]

TPDD Base Protocol

2019-12-12T23:17:05Z

Jhoger:

== General Reference ==

Note that this information was taken from Compuserve archives. Some stuff has been fixed.

If you have changes please suggest or make them.

<UL>
<LI>Disks are single sided 3.5 inch standard disks</LI>
<LI>PDD1 - 40 tracks 2 sectors 1280 bytes/sector (100K/disk)</LI>
<LI>PDD2 - 80 tracks 2 sectors 1280 bytes/sector (200K/disk treated as two banks of 100k
each)</LI>
<LI>Maximum file size = 64k. </LI>
<LI>Maximum number of directory entries (files) is 40 for PDD1 and 80 for PDD2.</LI>
<LI>File names are maximum 24 characters (padded with trailing blanks) although Tandy always
used 6 for filename and 2 for filetype, with period seperator (i.e. XXXXXX.TT)</LI>
<LI>All communications with drive are at 19,200 bps. PDD1 has dip switches so this can drop
to 9600bps. PDD2 is auto sensing down to 1200bps (??? - can anyone confirm this?).</LI>
</UL>

== Command Format ==

All commands are in a request/return format (half-duplex)

General request format:

<BLOCKQUOTE>
<TT>preamble type length data checksum</TT>
</BLOCKQUOTE>

General return format:

<BLOCKQUOTE>
<TT>type length data checksum</TT>
</BLOCKQUOTE>

== Command Type ==

(all values are in HEX)

{| WIDTH="100%" BORDER="1"
!  command
!  request
!  return
|-
|  directory ref
|  00
|  11 12
|-
|  open file
|  01
|  12
|-
|  close file
|  02
|  12
|-
|  read file
|  03
|  10 12
|-
|  write file
|  04
|  12
|-
|  delete file
|  05
|  12
|-
|  format disk
|  06 *
|  12
|-
|  drive status
|  07 *
|  12
|-
|  drive condition
|  0C *
|  15
|-
|   rename file
|  0D
|  12
|}

* PDD2 treats the disk as two banks of 100k each. All commands except these two must
specify the bank number as part of the request. The above commands reference BANK 0. To
reference BANK 1 you must add 40 HEX to these values (bit 6 = bank number). E.G. 'open
file' becomes 41 for BANK 1.

== Request Command details ==

=== Type 00 - Directory Reference ===

<PRE> 2 1 1 24 1 1 1 bytes
+----+--+--+--------------+----------+------------+------+
|5a5a|00|1a| filename |attribute |search form |chksum|
+----+--+--+--------------+----------+------------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 00h*
* length - length of data 1ah (26 decimal)
* filename - padded with blanks
* attribute - specify 'F' (not used normally)
* search form

<BLOCKQUOTE>
* 00h - reference file for open or delete
* 01h - request first directory block
* 02h - request next directory block
* 03h - request previous directory block
* 04h - end directory reference
</BLOCKQUOTE>

checksum - see below for calculating

=== Type 01 - Open file ===

<PRE> 2 1 1 1 1 bytes
+----+--+--+------+------+
|5a5a|01|01| mode |chksum|
+----+--+--+------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 01h
* length - length of data 01h (1 decimal)
* mode -

<BLOCKQUOTE>
* 01h - open new file for WRITE
* 02h - open existing file for APPEND
* 03h - open existing file for READ
</BLOCKQUOTE>

checksum - see below for calculating

=== Type 02 - Close file ===

<PRE> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|02|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 02h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 03 - Read file ===

<pre> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|03|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 03h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 04 - Write file ===

<PRE> 2 1 1 1-128 1 bytes
+----+--+---+------+------+
|5a5a|04|01-|data |chksum|
| | | 80| | |
+----+--+---+------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 04
* length - length of data 01h-80h (actual length of data)
* checksum - see below for calculating

=== Type 05 - Delete file ===

<PRE> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|05|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 05h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 06 - Format Disk ===

<PRE> 2 1 1 1 bytes
+----+--+--+------+
|5a5a|06|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 06h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 07 - Drive Status ===
<PRE>
2 1 1 1 bytes<
+----+--+--+------+
|5a5a|07|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 07h
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 0C - Drive Condition ===
<PRE>
2 1 1 1 bytes
+----+--+--+------+
|5a5a|0C|00|chksum|
+----+--+--+------+</PRE>

* Preamble - always 'ZZ'
* request - type 0Ch
* length - length of data 00h (no data field)
* checksum - see below for calculating

=== Type 0D - Rename file ===
<PRE>
2 1 1 24 1 1 bytes<
+----+--+--+-------+------+------+
|5a5a|0D|19|newname|attrib|chksum|
+----+--+--+-------+------+------+</PRE>

* Preamble - always 'ZZ'
* request - type 0D
* length - length of data 19h (25 decimal)
* newname - new name for the file
* attribute- not used (specify 'F')
* checksum - see below for calculating

== Return Command Details ==
=== Type 10 - Read file Return ===
<PRE>
1 1 0-128 1 bytes
+--+---+----------+-----+
|10|00-| file data|cksum|
| | 80| |cksum|
+--+---+----------+-----+</PRE>

* return - type 10
* length - length of data 00h-80h (0-128 decimal)<UL><LI>if length is equal to 80h there may be more data - you must issue another read command</LI><LI>if length is less than 80h then this is last block</LI></UL>
* file data - data read from file
* checksum - see below for calculating

=== Type 11 - Directory reference return ===
<PRE>
1 1 24 1 2 1 1 bytes
+--+--+--------+------+----+----+-----+
|11|1c|filename|attrib|size|free|cksum|
+--+--+--------+------+----+----+-----+</PRE>

* return - type 11h
* length - length of data 1Ch (28 decimal)
* filename - file name - if no name specied is 00H. If at end of directory is 00H.
* attribute - not used
* size - size of file, big endian format
* free - number of free sectors (multiply by 1280 for bytes)
* checksum - see below for calculating

=== Type 12 - Normal Return ===
<PRE> 1 1 1 1 bytes
+--+--+-----+-----+
|12|01|error|cksum|
+--+--+-----+-----+</PRE>

* return - type 12h
* length - length of data 01h
* error code-

{| WIDTH="100%" BORDER="1"
|  00 - normal (no error)
|  10 - file does not exist
|  11 - file exists
|-
|  30 - no filename
|  31 - dir search error
|  35 - bank error
|-
|  36 - parameter error
|  37 - open format mismatch
|  3f - end of file
|-
|  40 - no start mark
|  41 - crc check error in ID
|  42 - sector length error
|-
|  44 - format verify error
|  46 - format interruption
|  47 - erase offset error
|-
|  49 - crc check error in data
|  4a - sector number error
|  4b - read data timeout
|-
|  4d - sector number error
|  50 - disk write protect
|  5e - un-initilized disk
|-
|  60 - directory full
|  61 - disk full
|  6e - file too long
|-
|  70 - no disk
|  71 - disk change error
|  
|}

* checksum - see below for calculating

=== Type 15 - Drive Condition Return ===
<PRE>
1 1 1 1 bytes
+--+--+---------+-----+
|15|01|condition|cksum|
+--+--+---------+-----+</PRE>

* return - type 15h
* length - length of data 01h
* condition- bit values

<PRE> 7 6 5 4 3 2 1 0 bit
+-+-+-+-+-+-+-+-+
MSB |0|0|0|0|x|x|x|x| LSB
+-+-+-+-+-+-+-+-+
| | | |
| | | +--power (0=normal 1=low)
| | +----write protect (0=not prot 1=prot)
| +------disk out (0=disk in 1=disk out)
+--------disk change status (0=not changed 1=changed)</PRE>
* checksum - see below for calculating

<H2>Sequence of Events</H2>
{| WIDTH="100%"
|  Get directory
| req 00 search form 01 
req 00 search form 02 (repeat as needed)
|-
|  Write file
| req 00 search form 00 
req 01 mode 01 or 02 
req 04 (repeat as needed) 
req 02
|-
|  Read file
| req 00 search form 00 
req 01 mode 03 
req 03 (repeat as needed) 
req 02
|-
|  Rename file
| req 00 search form 00 
req 0d
|-
|  Delete file
|  req 00 search form 00 
req 05
|}<HR>

<H2>Calculating Checksum</H2>The check sum is "the one's complement of the least significant byte of the number
of bytes from the block format through the data block". Most people (me included)
don't understand what that involves if you have to calculate it. Fortunately I found an
example of how to do this and so I'm passing it on to you.Checksum=(sum-of-bytes MOD 256) XOR 255where bytes = the bytes including the Request Type, Length and all Data fields
(but not including the preamble).<HR><H2>Using this Information</H2>A lot of the above commands can be set up in advance since there is no variable part to
calculate. Some commands must have the length and checksum calculate as the data is built
but the others don't. Here's how I set up some of the commands in my program:

<pre>
Close$ = "ZZ"+Chr$(2)+Chr$(0)+Chr$(253)
Dir1$ = "ZZ"+Chr$(0)+Chr$(26)+Space$(24)+"F"+Chr$(1)+Chr$(158)
Dir2$ = "ZZ"+Chr$(0)+Chr$(26)+Space$(24)+"F"+Chr$(2)+Chr$(157)
Status$ = "ZZ"+Chr$(7)+Chr$(0)+Chr$(248)+Chr$(13)
Format$ = "ZZ"+Chr$(6)+Chr$(0)+Chr$(249)+Chr$(13)
Erase$ = "ZZ"+Chr$(5)+Chr$(0)+Chr$(250)
Seek$(1) = "ZZ"+Chr$(1)+Chr$(1)+Chr$(1)+Chr$(252)
Seek$(2) = "ZZ"+Chr$(1)+Chr$(1)+Chr$(2)+Chr$(251)
Seek$(3) = "ZZ"+Chr$(1)+Chr$(1)+Chr$(3)+Chr$(250)
</pre>

The above commands can be sent directly without any calculating to speed up your
program. 

[[Category:Model T Developer Reference]]

LaddieCon

2019-05-01T05:18:13Z

Jhoger: Removed protection from "LaddieCon"

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

More info to come. This is a new "cross platform" build of LaddieCon that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

Advantages of LaddieAlpha over LaddieCon:

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop

The only disadvantage of LaddieAlpha is that it won't run on Windows 98 (that is, the .NET version it requires was never ported by Microsoft to Windows 98).

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download and test LaddieAlpha]

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

NOTE: On OSX, If you get an error about libMonoPosixHelper.dylib, mono may be finding the wrong shared library.

You need to edit the file /opt/local/etc/mono/config and change the relevant line as follows:

<pre>
<dllmap dll="MonoPosixHelper" target="/opt/local/lib/libMonoPosixHelper.dylib"/>

</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

CloudT Web Emulator

2019-03-04T00:47:48Z

Jhoger:

[[File:CloudT.png]]

CloudT is the "instant gratification" Model 100 emulator written completely in JavaScript.

To use it just enter the following link into any browser:

[https://bitchin100.com/CloudT https://bitchin100.com/CloudT]

It is not the best emulator (VirtualT is the best), but it is the only emulator that will run on an iPhone or iPad, the only emulator you can sneak onto any new smart device you may want to buy while you're device shopping at the store. It's the only emulator you can use on PCs you're not allowed to install software to, say at the library or internet cafe.

If you want a quick fix of Model T goodness, it's a good URL to remember.

Its features are:

* Loads instantly in your browser
* Can be saved with an icon on your device home screen as a full screen "web app" on both iOS and Android devices
* Once you load the first time, runs "Offline" (no internet connection required)
* It remembers your in-memory files from the last time you used it
* Runs on mobile devices including iPhones
* Compatible with the BASIC "SOUND" command
* Can load files to/from local drive
* Can load files to/from Google Drive
* Files pulled into the emulator show up on a "virtual tape" at the bottom of the screen. You process them (or create them) using the usual cassette commands (CLOAD, CSAVE, etc)
* Option ROMs are available from a drop down list

== Virtual Tape ==

CloudT creates a special "virtual tape" as a bridge between your CloudT and your PC file system, or web storage. Files on the Virtual Tape are shown at the bottom of the screen if you scroll down. If nothing is on the Virtual Tape you won't see anything there.

When you CSAVE a file on a real Model 100, it is turned into a series of digital packets, which are encoded as an audio signal you can capture on a cassette tape.

But when you CSAVE in CloudT, the digital packets are captured by the emulator and converted into in-memory files in a Virtual Tape at the bottom of your screen.

This sounds complicated but once you get used to the concept, it is easy to understand.

The Virtual Tape is a "queue." Files are served "first in, first out". The idea is similar to when you line up at the grocery store or bank. The first person in the line is the first person served. The next person into the line enters at the end of the line and their business will be addressed after every person that entered the line before them.

Conceptually, like a line at the bank, although you enter the queue at the end, all the action happens at the front.

New files CSAVEd to the Virtual Tape get staged (in programmer jargon, "enqueued") at the end of the tape.

If you CLOAD from the Virtual Tape, it will serve staged files from the front of the list, and the file you CLOAD will be removed from the list.

Once a file is in the Virtual Tape, you can click icons on the screen to download it directly to your computer, or save it to the cloud (Google Drive).

[[File:Virtual Tape.png]]

== Staging a File from the Clipboard ==

There is a text field below the keyboard. You can paste into this field and click the button "Add Plain Text"

This will create a .DO file in the Virtual Tape.

== Adding a File from Club100 ==

Say you're at http://club100.org/library/libgam.html

You want to load the game CHESS.100

Hover your mouse over the CHESS.100 link. Right click and choose "Copy Link Address"

Go to your tab containing CloudT.

Click Add URL.

Click on the field.

Hit Ctrl-V to paste the link.

Click OK.

Look at the end of the screen, you'll see ALIENS.BA in the Virtual Tape area.

== Adding a File from Google Drive ==

Feature implemented, need documentation

== Accessing the Virtual Tape Queue ==

Feature implemented, need documentation

== Saving a File to Your Hard Drive ==

Feature implemented, need documentaton

CloudT Web Emulator

2019-03-04T00:39:46Z

Jhoger: /* Virtual Tape */

[[File:CloudT.png]]

CloudT is the "instant gratification" Model 100 emulator written completely in JavaScript.

To use it just enter the following link into any browser:

[https://bitchin100.com/CloudT https://bitchin100.com/CloudT]

It is not the best emulator (VirtualT is the best), but it is the only emulator that will run on an iPhone or iPad, the only emulator you can sneak onto any new smart device you may want to buy while you're device shopping at the store. It's the only emulator you can use on PCs you're not allowed to install software to, say at the library or internet cafe.

If you want a quick fix of Model T goodness, it's a good URL to remember.

Its features are:

* Loads instantly in your browser
* Once you load the first time, runs "Offline" (no internet connection required)
* It remembers your in-memory files from the last time you used it
* Runs on mobile devices including iPhones
* Compatible with the BASIC "SOUND" command
* Can load files to/from local drive
* Can load files to/from Google Drive
* Files pulled into the emulator show up on a "virtual tape" at the bottom of the screen. You process them (or create them) using the usual cassette commands (CLOAD, CSAVE, etc)
* Option ROMs are available from a drop down list

== Virtual Tape ==

CloudT creates a special "virtual tape" as a bridge between your CloudT and your PC file system, or web storage. Files on the Virtual Tape are shown at the bottom of the screen if you scroll down. If nothing is on the Virtual Tape you won't see anything there.

When you CSAVE a file on a real Model 100, it is turned into a series of digital packets, which are encoded as an audio signal you can capture on a cassette tape.

But when you CSAVE in CloudT, the digital packets are captured by the emulator and converted into in-memory files in a Virtual Tape at the bottom of your screen.

This sounds complicated but once you get used to the concept, it is easy to understand.

The Virtual Tape is a "queue." Files are served "first in, first out". The idea is similar to when you line up at the grocery store or bank. The first person in the line is the first person served. The next person into the line enters at the end of the line and their business will be addressed after every person that entered the line before them.

Conceptually, like a line at the bank, although you enter the queue at the end, all the action happens at the front.

New files CSAVEd to the Virtual Tape get staged (in programmer jargon, "enqueued") at the end of the tape.

If you CLOAD from the Virtual Tape, it will serve staged files from the front of the list, and the file you CLOAD will be removed from the list.

Once a file is in the Virtual Tape, you can click icons on the screen to download it directly to your computer, or save it to the cloud (Google Drive).

[[File:Virtual Tape.png]]

== Staging a File from the Clipboard ==

There is a text field below the keyboard. You can paste into this field and click the button "Add Plain Text"

This will create a .DO file in the Virtual Tape.

== Adding a File from Club100 ==

Say you're at http://club100.org/library/libgam.html

You want to load the game CHESS.100

Hover your mouse over the CHESS.100 link. Right click and choose "Copy Link Address"

Go to your tab containing CloudT.

Click Add URL.

Click on the field.

Hit Ctrl-V to paste the link.

Click OK.

Look at the end of the screen, you'll see ALIENS.BA in the Virtual Tape area.

== Adding a File from Google Drive ==

Feature implemented, need documentation

== Accessing the Virtual Tape Queue ==

Feature implemented, need documentation

== Saving a File to Your Hard Drive ==

Feature implemented, need documentaton

CloudT Web Emulator

2019-03-04T00:36:21Z

Jhoger:

[[File:CloudT.png]]

CloudT is the "instant gratification" Model 100 emulator written completely in JavaScript.

To use it just enter the following link into any browser:

[https://bitchin100.com/CloudT https://bitchin100.com/CloudT]

It is not the best emulator (VirtualT is the best), but it is the only emulator that will run on an iPhone or iPad, the only emulator you can sneak onto any new smart device you may want to buy while you're device shopping at the store. It's the only emulator you can use on PCs you're not allowed to install software to, say at the library or internet cafe.

If you want a quick fix of Model T goodness, it's a good URL to remember.

Its features are:

* Loads instantly in your browser
* Once you load the first time, runs "Offline" (no internet connection required)
* It remembers your in-memory files from the last time you used it
* Runs on mobile devices including iPhones
* Compatible with the BASIC "SOUND" command
* Can load files to/from local drive
* Can load files to/from Google Drive
* Files pulled into the emulator show up on a "virtual tape" at the bottom of the screen. You process them (or create them) using the usual cassette commands (CLOAD, CSAVE, etc)
* Option ROMs are available from a drop down list

== Virtual Tape ==

CloudT creates a special "virtual tape" as a bridge between your CloudT and your PC file system, or web storage. Files on the Virtual Tape are shown at the bottom of the screen if you scroll down. If nothing is on the Virtual Tape you won't see anything there.

When you CSAVE a file on a real Model 100, it would is turned into a series of digital packets, which are encoded as an audio signal you can capture on a cassette tape.

But when you CSAVE in CloudT, the file digital packets are captured by the emulator and converted into in-memory files in a Virtual Tape list at the bottom of your screen.

This sounds complicated but once you get used to the concept, it is easy to understand.

The Virtual Tape is a "queue." Files are served "first in, first out". The idea is similar to when you line up a the grocery store or bank. The first person in the line is the first person served. The next person into the line enters at the end of the line and will be addressed after every person that entered the line before them.

Conceptually, like a line at the bank, although you enter the queue at the end, all the action happens at the front.

New files CSAVEd to the Virtual Tape get staged (in programmer jargon, "enqueued") at the end of the tape.

If you CLOAD from the Virtual Tape, it will serve staged files from the front of the list, and the file you CLOAD will be removed from the list.

Once a file is in the Virtual Tape, you can click icons on the screen to download it directly to your computer, or save it to the cloud (Google Drive).

[[File:Virtual Tape.png]]

== Staging a File from the Clipboard ==

There is a text field below the keyboard. You can paste into this field and click the button "Add Plain Text"

This will create a .DO file in the Virtual Tape.

== Adding a File from Club100 ==

Say you're at http://club100.org/library/libgam.html

You want to load the game CHESS.100

Hover your mouse over the CHESS.100 link. Right click and choose "Copy Link Address"

Go to your tab containing CloudT.

Click Add URL.

Click on the field.

Hit Ctrl-V to paste the link.

Click OK.

Look at the end of the screen, you'll see ALIENS.BA in the Virtual Tape area.

== Adding a File from Google Drive ==

Feature implemented, need documentation

== Accessing the Virtual Tape Queue ==

Feature implemented, need documentation

== Saving a File to Your Hard Drive ==

Feature implemented, need documentaton

CloudT Web Emulator

2019-03-04T00:20:07Z

Jhoger: Created page with "File:CloudT.png CloudT is the "instant gratification" Model 100 emulator written completely in JavaScript. It is not the best emulator (VirtualT is the best), but it is ..."

[[File:CloudT.png]]

CloudT is the "instant gratification" Model 100 emulator written completely in JavaScript.

It is not the best emulator (VirtualT is the best), but it is the only emulator that will run on an iPhone or iPad, the only emulator you can sneak onto any new smart device you may want to buy while you're device shopping at the store. It's the only emulator you can use on PCs you're not allowed to install software to, say at the library or internet cafe.

If you want a quick fix of Model T goodness, it's a good URL to remember.

Its features are:

* Loads instantly in your browser
* Once you load the first time, runs "Offline"
* Runs on mobile devices including iPhones
* Compatible with the BASIC "SOUND" command
* Can load files to/from local drive
* Can load files to/from Google Drive
* Files pulled into the emulator show up on a "virtual tape" at the bottom of the screen. You process them (or create them) using the usual cassette commands (CLOAD, CSAVE, etc)
* Option ROMs are available from a drop down list

== Virtual Tape ==

CloudT creates a special "virtual tape" as a bridge between your CloudT and your PC file system, or web storage. Files on the Virtual Tape are shown at the bottom of the screen if you scroll down. If nothing is on the Virtual Tape you won't see anything there.

When you CSAVE a file on a real Model 100, it would is turned into a series of digital packets, which are encoded as an audio signal you can capture on a cassette tape.

But when you CSAVE in CloudT, the file digital packets are captured by the emulator and converted into in-memory files in a Virtual Tape list at the bottom of your screen.

This sounds complicated but once you get used to the concept, it is easy to understand.

The Virtual Tape is a "queue." Files are served "first in, first out". The idea is similar to when you line up a the grocery store or bank. The first person in the line is the first person served. The next person into the line enters at the end of the line and will be addressed after every person that entered the line before them.

Conceptually, like a line at the bank, although you enter the queue at the end, all the action happens at the front.

New files CSAVEd to the Virtual Tape show up (in programmer jargon, "enqueued") at the end of the tape.

If you CLOAD from the Virtual Tape, it will serve files from the front of the list, and the file you CLOAD will be removed from the list.

Once a file is in the Virtual Tape, you can click icons on the screen to download it directly to your computer, or save it to the cloud (Google Drive).

[[File:Virtual Tape.png]]

== Adding a File from the Clipboard ==

== Adding a File from Club100 ==

== Adding a File from Google Drive ==

== Accessing the Virtual Tape Queue ==

== Saving a File to Your Hard Drive ==

==

File:CloudT.png

2019-03-04T00:19:08Z

Jhoger: Main screen of CloudT

Main screen of CloudT

File:Virtual Tape.png

2019-03-04T00:15:39Z

Jhoger: Explication on CloudT's virtual tape feature

Explication on CloudT's virtual tape feature

Bitchin100 DocGarden

2019-02-26T23:14:18Z

Jhoger:

Bitchin100 DocGarden is the site for enthusiasts to share documentation, notes, reviews and links to other projects and software related to [[True Portable Definition|True Portable Laptops]].

== [[Model T DocGarden|Model T]] ==

These pages are dedicated to [[Model T DocGarden|TRS-80 Model 100]], workalikes (Kyocera, NEC, Olivetti) and the Tandy 200

<div style="background-color:lightyellow;padding:1em;border-style:solid;font-siz
e:105%">
Club 100 Mailing List
The Official Club100 Mailing List is hosted here!
Go to the [http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com User Page] and subscribe to the list.
To send email to the list, just send it to m100@lists.bitchin100.com
</div>

== Other Interesting Machines ==

* [[Tandy WP-2 DocGarden|Tandy WP-2]]

* [[Cambridge Z88 DocGarden|Cambridge Z88]]

* [[Amstrad NC-100/200 DocGarden|Amstrad NC-100/200]]

* [[Epson PX-8 Geneva DocGarden|Epson PX-8 Geneva]]

* [[NEC 8500, Starlet]]

== 16, 32 or 64-bit bus Machines ==

Please contribute documentation on any machines you feel fit the [[True Portable Definition|TPD]].

Bitchin100 DocGarden

2019-02-26T23:13:54Z

Jhoger:

Bitchin100 DocGarden is the site for enthusiasts to share documentation, notes, reviews and links to other projects and software related to [[True Portable Definition|True Portable Laptops]].

== [[Model T DocGarden|Model T]] ==

These pages are dedicated to [[Model T DocGarden|TRS-80 Model 100]], workalikes (Kyocera, NEC, Olivetti) and the Tandy 200

<div style="background-color:lightyellow;padding:1em;border-style:solid;font-siz
e:105%">
IMPORTANT ANNOUNCEMENT
The Official Club100 Mailing List is hosted here!
Go to the [http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com User Page] and subscribe to the list.
To send email to the list, just send it to m100@lists.bitchin100.com
</div>

== Other Interesting Machines ==

* [[Tandy WP-2 DocGarden|Tandy WP-2]]

* [[Cambridge Z88 DocGarden|Cambridge Z88]]

* [[Amstrad NC-100/200 DocGarden|Amstrad NC-100/200]]

* [[Epson PX-8 Geneva DocGarden|Epson PX-8 Geneva]]

* [[NEC 8500, Starlet]]

== 16, 32 or 64-bit bus Machines ==

Please contribute documentation on any machines you feel fit the [[True Portable Definition|TPD]].

Model 100 Screen Escapes

2019-02-18T02:38:09Z

Jhoger:

{| class="wikitable"
|+Nonprinting characters
!Name
!Hex
!Description
!Notes
|-
|BELL
|0x07
|Beep tone
|None
|-
|BACKSPACE
|0x08
|Backspace
|None
|-
|HRZTAB
|0x09
|Horizontal tab: move to next tab position
|None
|-
|LF
|0x0A
|Linefeed
|None
|-
|VERTTAB
|0x0B
|Vertical tab: home cursor to (Row, Column) = (1,1)
|None
|-
|FF
|0x0C
|Form feed
|None
|-
|CR
|0x0D
|Carriage return
|None
|-
|ESC
|0x1B
|Start of escape sequence
|None
|}

{| class="wikitable"
|+Screen Escapes: Precede with 0x1B / CHR$(27)
!Name
!Hex
!Char
!Description
!Notes
|-
|CURUP
|0x41
|A
|Move cursor up one row unless already at edge
|None
|-
|CURDWN
|0x42
|B
|Move cursor down one row unless already at edge
|None
|-
|CURRIGHT
|0x43
|C
|Move cursor right one column unless already at edge
|None
|-
|CURLEFT
|0x44
|D
|Move cursor left one column unless already at edge
|None
|-
|CLRSCR
|0x45
|E
|Clears screen, homes cursor. Escaped synonym for 0x0C.
|None
|-
|HOME
|0x46
|H
|Home the cursor. Sets cursor to (Row, Column) = (1,1)
|None
|-
|ERAEOS
|0x4A
|J
|Erase from cursor to end of screen
|None
|-
|ERAEOL
|0x4B
|K
|Erase from cursor to end of line
|None
|-
|INSLIN
|0x4C
|L
|Insert a blank line on LCD at current cursor
|None
|-
|DELLIN
|0x4D
|M
|Delete line on LCD at current cursor
|None
|-
|CURON
|0x50
|P
|Turn on cursor
|None
|-
|CUROFF
|0x51
|Q
|Turn off cursor
|None
|-
|SETSYS
|0x54
|T
|Set system line (lock LCD row 8)
|None
|-
|RSTSYS
|0x55
|U
|Reset system line (unlock LCD row 8)
|None
|-
|LOCK
|0x56
|V
|Lock LCD display (no scrolling)
|None
|-
|UNLOCK
|0x57
|W
|Unlock LCD display (allow scrolling)
|None
|-
|REDRAW
|0x58
|X
|Redraw the screen
|None
|-
|CURPOS
|0x59 [0-based row + 32] [0-based col + 32]
|Y
|Position cursor at (Row, Column)
|None
|-
|CLRSC2
|0x6A
|j
|Clears screen, homes cursor. Another escaped synonym for 0x0C.
|None
|-
|ERSLIN
|0x6C
|l (lowercase-L)
|Erase entire line containing cursor.
|None
|-
|ENTREV
|0x70
|p
|Turn on reverse character mode
|None
|-
|EXTREV
|0x71
|q
|Turn off reverse character mode
|None
|}

Model 100 Screen Escapes

2019-02-18T02:35:43Z

Jhoger:

{| class="wikitable"
|+Nonprinting characters
!Name
!Hex
!Description
!Notes
|-
|BELL
|0x07
|Beep tone
|None
|-
|BACKSPACE
|0x08
|Backspace
|None
|-
|HRZTAB
|0x09
|Horizontal tab: move to next tab position
|None
|-
|LF
|0x0A
|Linefeed
|None
|-
|VERTTAB
|0x0B
|Vertical tab: home cursor to (Row, Column) = (1,1)
|None
|-
|FF
|0x0C
|Form feed
|None
|-
|CR
|0x0D
|Carriage return
|None
|-
|ESC
|0x1B
|Start of escape sequence
|None
|}

{| class="wikitable"
|+Screen Escapes: Precede with 0x1A / CHR$(27)
!Name
!Hex
!Char
!Description
!Notes
|-
|CURUP
|0x41
|A
|Move cursor up one row unless already at edge
|None
|-
|CURDWN
|0x42
|B
|Move cursor down one row unless already at edge
|None
|-
|CURRIGHT
|0x43
|C
|Move cursor right one column unless already at edge
|None
|-
|CURLEFT
|0x44
|D
|Move cursor left one column unless already at edge
|None
|-
|CLRSCR
|0x45
|E
|Clears screen, homes cursor. Escaped synonym for 0x0C.
|None
|-
|HOME
|0x46
|H
|Home the cursor. Sets cursor to (Row, Column) = (1,1)
|None
|-
|ERAEOS
|0x4A
|J
|Erase from cursor to end of screen
|None
|-
|ERAEOL
|0x4B
|K
|Erase from cursor to end of line
|None
|-
|INSLIN
|0x4C
|L
|Insert a blank line on LCD at current cursor
|None
|-
|DELLIN
|0x4D
|M
|Delete line on LCD at current cursor
|None
|-
|CURON
|0x50
|P
|Turn on cursor
|None
|-
|CUROFF
|0x51
|Q
|Turn off cursor
|None
|-
|SETSYS
|0x54
|T
|Set system line (lock LCD row 8)
|None
|-
|RSTSYS
|0x55
|U
|Reset system line (unlock LCD row 8)
|None
|-
|LOCK
|0x56
|V
|Lock LCD display (no scrolling)
|None
|-
|UNLOCK
|0x57
|W
|Unlock LCD display (allow scrolling)
|None
|-
|REDRAW
|0x58
|X
|Redraw the screen
|None
|-
|CURPOS
|0x59 [0-based row + 32] [0-based col + 32]
|Y
|Position cursor at (Row, Column)
|None
|-
|CLRSC2
|0x6A
|j
|Clears screen, homes cursor. Another escaped synonym for 0x0C.
|None
|-
|ERSLIN
|0x6C
|l (lowercase-L)
|Erase entire line containing cursor.
|None
|-
|ENTREV
|0x70
|p
|Turn on reverse character mode
|None
|-
|EXTREV
|0x71
|q
|Turn off reverse character mode
|None
|}

Model 100 Screen Escapes

2019-02-18T02:30:53Z

Jhoger: Change TBD to Notes

{| class="wikitable"
|+Nonprinting characters
!Name
!Hex
!Description
!Notes
|-
|BELL
|0x07
|Beep tone
|None
|-
|BACKSPACE
|0x08
|Backspace
|None
|-
|HRZTAB
|0x09
|Horizontal tab: move to next tab position
|None
|-
|LF
|0x0A
|Linefeed
|None
|-
|VERTTAB
|0x0B
|Vertical tab: home cursor to (Row, Column) = (1,1)
|None
|-
|FF
|0x0C
|Form feed
|None
|-
|CR
|0x0D
|Carriage return
|None
|-
|ESC
|0x1B
|Start of escape sequence
|None
|}

{| class="wikitable"
|+Screen Escapes: Precede with 0x1A / CHR$(27)
!Name
!Hex
!Char
!Description
!Notes
|-
|CURUP
|0x41
|A
|Move cursor up one row unless already at edge
|None
|-
|CURDWN
|0x42
|B
|Move cursor down one row unless already at edge
|None
|-
|CURRIGHT
|0x43
|C
|Move cursor right one column unless already at edge
|None
|-
|CURLEFT
|0x44
|D
|Move cursor left one column unless already at edge
|None
|-
|CLRSCR
|0x45
|E
|Clears screen, homes cursor. Escaped synonym for 0x0C.
|None
|-
|HOME
|0x46
|H
|Home the cursor. Sets cursor to (Row, Column) = (1,1)
|None
|-
|ERAEOS
|0x4A
|J
|Erase from cursor to end of screen
|None
|-
|ERAEOL
|0x4B
|K
|Erase from cursor to end of line
|None
|-
|INSLIN
|0x4C
|L
|Insert a blank line on LCD at current cursor (what if in middle of line?)
|None
|-
|DELLIN
|0x4D
|M
|Delete line on LCD at current cursor (what if in middle of line?)
|None
|-
|CURON
|0x50
|P
|Turn on cursor
|None
|-
|CUROFF
|0x51
|Q
|Turn off cursor
|None
|-
|SETSYS
|0x54
|T
|Set system line (lock LCD row 8)
|None
|-
|RSTSYS
|0x55
|U
|Reset system line (unlock LCD row 8)
|None
|-
|LOCK
|0x56
|V
|Lock LCD display (no scrolling)
|None
|-
|UNLOCK
|0x57
|W
|Unlock LCD display (allow scrolling)
|None
|-
|REDRAW
|0x58
|X
|Redraw the screen
|None
|-
|CURPOS
|0x59 [0-based row + 32] [0-based col + 32]
|Y
|Position cursor at (Row, Column)
|None
|-
|CLRSC2
|0x6A
|j
|Clears screen, homes cursor. Another escaped synonym for 0x0C.
|None
|-
|ERSLIN
|0x6C
|l (lowercase-L)
|Erase entire line containing cursor.
|None
|-
|ENTREV
|0x70
|p
|Turn on reverse character mode
|None
|-
|EXTREV
|0x71
|q
|Turn off reverse character mode
|None
|}

Model 100 Screen Escapes

2019-02-18T01:43:39Z

Jhoger: Created page with "{| class="wikitable" |+Nonprinting characters !Name !Hex !Description !TBD |- |BELL |0x07 |Beep tone |None |- |BACKSPACE |0x08 |Backspace |None |- |HRZTAB |0x09 |Horizontal ta..."

{| class="wikitable"
|+Nonprinting characters
!Name
!Hex
!Description
!TBD
|-
|BELL
|0x07
|Beep tone
|None
|-
|BACKSPACE
|0x08
|Backspace
|None
|-
|HRZTAB
|0x09
|Horizontal tab: move to next tab position
|None
|-
|LF
|0x0A
|Linefeed
|None
|-
|VERTTAB
|0x0B
|Vertical tab: home cursor to (Row, Column) = (1,1)
|None
|-
|FF
|0x0C
|Form feed
|None
|-
|CR
|0x0D
|Carriage return
|None
|-
|ESC
|0x1B
|Start of escape sequence
|None
|}

{| class="wikitable"
|+Screen Escapes: Precede with 0x1A / CHR$(27)
!Name
!Hex
!Char
!Description
!TBD
|-
|CURUP
|0x41
|A
|Move cursor up one row unless already at edge
|None
|-
|CURDWN
|0x42
|B
|Move cursor down one row unless already at edge
|None
|-
|CURRIGHT
|0x43
|C
|Move cursor right one column unless already at edge
|None
|-
|CURLEFT
|0x44
|D
|Move cursor left one column unless already at edge
|None
|-
|CLRSCR
|0x45
|E
|Clears screen, homes cursor. Escaped synonym for 0x0C.
|None
|-
|HOME
|0x46
|H
|Home the cursor. Sets cursor to (Row, Column) = (1,1)
|None
|-
|ERAEOS
|0x4A
|J
|Erase from cursor to end of screen
|None
|-
|ERAEOL
|0x4B
|K
|Erase from cursor to end of line
|None
|-
|INSLIN
|0x4C
|L
|Insert a blank line on LCD at current cursor (what if in middle of line?)
|None
|-
|DELLIN
|0x4D
|M
|Delete line on LCD at current cursor (what if in middle of line?)
|None
|-
|CURON
|0x50
|P
|Turn on cursor
|None
|-
|CUROFF
|0x51
|Q
|Turn off cursor
|None
|-
|SETSYS
|0x54
|T
|Set system line (lock LCD row 8)
|None
|-
|RSTSYS
|0x55
|U
|Reset system line (unlock LCD row 8)
|None
|-
|LOCK
|0x56
|V
|Lock LCD display (no scrolling)
|None
|-
|UNLOCK
|0x57
|W
|Unlock LCD display (allow scrolling)
|None
|-
|REDRAW
|0x58
|X
|Redraw the screen
|None
|-
|CURPOS
|0x59 [0-based row + 32] [0-based col + 32]
|Y
|Position cursor at (Row, Column)
|None
|-
|CLRSC2
|0x6A
|j
|Clears screen, homes cursor. Another escaped synonym for 0x0C.
|None
|-
|ERSLIN
|0x6C
|l (lowercase-L)
|Erase entire line containing cursor.
|None
|-
|ENTREV
|0x70
|p
|Turn on reverse character mode
|None
|-
|EXTREV
|0x71
|q
|Turn off reverse character mode
|None
|}

M100 CP/M

2017-09-12T16:09:57Z

Jhoger: Created page with "Placeholder for M100 CP/M content"

Placeholder for M100 CP/M content

TPDD Design Notes

2016-11-30T06:50:39Z

Jhoger: /* Update: Work Completed! */

The initial purpose is to document an effort to reverse engineer the TPDD and TPDD-2, in order to get a better understanding of the protocols that they support.

== Major silicon components ==

According to the schematics of the TPDD and TPDD-2, the major components of interest are:

<UL>
<LI>HD6301: CPU (a 6800 derivative with 128 bytes of onboard RAM, 4K of onboard ROM and a UART). Datasheet: [[Media:Hd6301.pdf‎]]</LI>
<LI>uPD449G (TPDD) / HM6117 (TPPD-2): RAM</LI>
<LI>uPD65002: CMOS Gate Array</LI>
</UL>

== Initial Thoughts ==

The idea for dumping the ROM of the TPDD came from the IPL boot code of the TPDD (need to check that this is the same for TPDD-2):

10 OPEN "COM:88N1DNN" FOR OUTPUT AS #1
20 PRINT #1, "S10985157C00AD7EF08B3AS901FE"
30 LOAD "COM:88N1ENN", R

It was noted that line 20 is [http://en.wikipedia.org/wiki/S-record S Record format], and breaks down as:

S1 09 8515 7C 00 AD 7E F0 8B 3A
S9 01 FE

which translates to "starting at address 8515, load the bytes 7C 00 AD 7E F0 8B", then terminate. Note that the termination record ("S9") is shorter than normal as it is missing the address component (possibly legal, but unusual).

The BASIC program then loads a program from the serial port (in this case, attached TPDD).

Given that we know the CPU type of the TPDD, disassembling those bytes gives:

8515 INC $00AD
8518 JMP F08B

These locations match up with what is known from the datasheet of the HD6301 (internal RAM maps from $0080 to $00FF, internal ROM maps from $F000 to $FFFF).

The question is, what else could we do with that line 20? Could we possibly coerce the TPDD into spilling its ROM contents over the serial port?

Current thoughts on plans of attack are:

<UL>
<LI>Seeing how much wiggle room there is in the boot code space (i.e. how much extra can we upload?)</LI>
<LI>How the uploaded boot code interacts with the boot sequence
<UL><LI>at what point does the uploaded code get executed? Are we patching a known location that the ROM calls? (is location 8515 magical?)?</LI>
<LI>(partly related to above) what triggers the execution? On receipt of the S9 record?</LI>
<LI>what is the significance of address $00AD?</LI>
</UL>
</UL>

== Update: Work Completed! ==

[[:file:PDD Reverse Engineering.zip|PDD Reverse Engineering]]

From Darren Clark:

Hello all,
I see on the Wiki that someone was working on trying to dump the ROM on the PDD, but that page was last updated in 2009. Well I took the challenge and wrote this little program to try it.

I've also posted the S-REC too so anybody can try it. In order to get the S-REC to work do the following:

# Switch your PDD to 9600 BUAD, the switches on the bottom need to be set to ON.
# Connect your PDD to a PC and connect with Hyper Terminal or another terminal program.
# Settings are 9600-8-n-1, no flow control. Set the line delay and character delay to 20mS, otherwise we're pushing data to the CPU too fast and will get a blinking light.
# Paste each line of the S-REC into the terminal program, but do not include the CR/LF (i.e. only highlight the text).
# If the Low Battery light starts blinking, start over because something bad happened (like accidently included a CR/LF).
# When the last line is pasted "S901FE", this triggers the program running in the ROM to jump to address 0x8515 and execute the program
# The ROM (F000-FFFF) is now dumped to the terminal program in the following format:
<pre>
F000:0F 8E 87 FF 86 FC 97 00
F008:86 34 97 02 86 FF 97 04
F010:97 05 86 A0 B7 40 00 F6
F018:40 01 C4 F0 37 54 54 54
F020:54 CE FF B7 3A A6 00 97
F028:80 B7 40 01 86 10 97 01
F030:86 0C 97 10 86 0A 97 11
F038:CE 00 81 CC 00 7F BD F9
F040:AD 72 FF 86 C6 64 BD F9
F048:BC BD F4 51 33 C1 D0 24
</pre>

Darren Clark.

[[Category:Model T Developer Reference]]

TPDD Design Notes

2016-11-30T06:45:20Z

Jhoger:

File:PDD Reverse Engineering.zip

2016-11-30T06:42:02Z

Jhoger: ROM dump of Tandy Portable Disk Drive

ROM dump of Tandy Portable Disk Drive

Template:Extension DPL

2014-11-16T01:12:53Z

Jhoger: Template:Extension DPL

<noinclude>This page was automatically created. It serves as an anchor page for all '''[[Special:WhatLinksHere/Template:Extension_DPL|invocations]]''' of [http://mediawiki.org/wiki/Extension:DynamicPageList Extension:DynamicPageList (DPL)].</noinclude>

Recovering an Unresponsive Laptop

2013-09-25T21:48:18Z

Jhoger: /* Clear the RAM File System */

Every once in a while, someone comes to the TRS-80 Model 100 mailing
list asking how to recover a laptop they bought off ebay that is
unresponsive to the power button.

== Clear the RAM File System ==

Although the Model T laptops use standard AA batteries, understand that there is an internal battery soldered to the motherboard that maintains power to the RAM even when the main batteries are dead or removed.

Often with units that have sat unused for awhile these problems occur:

* the nicad is drained
* the RAM is in some random state
* the contrast knob is in some random state

You need to resolve all three, but you need to do it in the right
order. Almost always you can recover a Model T without resorting to
more serious troubleshooting.

# Leave the laptop plugged in to the wallcube overnight with Memory Power switch on, and the power off. I don't think it matters whether you use good AA's or the wallcube at this point.
# Let the unit sit with the Memory Power button off and no plug or other cables connected or batteries in the battery compartment for about 15 minutes in order to clear the RAM.
# Turn the memory power switch back on, reinstall the AA batteries and/or connect the power cable
# With the power-button ON, hold down Ctrl-shift-break simultaneously, and hit reset button to clear the RAM

Now fiddle with the contrast knob. Hopefully you will see the normal Model 100 main menu.

== Check the Display ==

In rarer cases, the problem is a bad display, or problematic (internal) display connection. If the "clear RAM" steps above do not resolve the issues, the display is the next thing to check.

To diagnose this problem,
# Perform cold-boot (CTRL-BREAK-Reset)
# Hit the Enter key
# Type "beep" (without quotes) and hit Enter again
The machine will make a beep sound if it is actually working (meaning it has a bad LCD or bad LCD connection). Your recourse at this stage is to find a replacement display. Club100 or another community member may be able to help you.

If it doesn't work you could have multiple problems, including a bad display, bad keyboard, or a problem with the mainboard.

== Otherwise ==

If none of the steps above lead you to a resolution, then more serious troubleshooting begins. Head over to the Model 100 mailing list (you can subscribe at [http://club100.org/list.html Model 100 Mailing List] )

[[Category:Model T Hardware Hacking]]

Recovering an Unresponsive Laptop

2013-09-25T21:45:37Z

Jhoger: /* Clear the RAM File System */

Every once in a while, someone comes to the TRS-80 Model 100 mailing
list asking how to recover a laptop they bought off ebay that is
unresponsive to the power button.

== Clear the RAM File System ==

Although the Model T laptops use standard AA batteries, understand that there is an internal battery soldered to the motherboard that maintains power to the RAM even when the main batteries are dead or removed.

Often with units that have sat unused for awhile these problems occur:

* the nicad is drained
* the RAM is in some random state
* the contrast knob is in some random state

You need to resolve all three, but you need to do it in the right
order. Almost always you can recover a Model T without resorting to
more serious troubleshooting.

# Leave the laptop plugged in to the wallcube overnight with Memory Power switch on, and the power off. I don't think it matters whether you use good AA's or the wallcube at this point.
# Let the unit sit with the Memory Power button off and no plug or other cables connected or batteries in the battery compartment for about 15 minutes in order to clear the RAM.
# Turn the memory power switch back on
# With the power-button ON, hold down Ctrl-shift-break simultaneously, and hit reset button to clear the RAM

Now fiddle with the contrast knob. Hopefully you will see the normal Model 100 main menu.

== Check the Display ==

In rarer cases, the problem is a bad display, or problematic (internal) display connection. If the "clear RAM" steps above do not resolve the issues, the display is the next thing to check.

To diagnose this problem,
# Perform cold-boot (CTRL-BREAK-Reset)
# Hit the Enter key
# Type "beep" (without quotes) and hit Enter again
The machine will make a beep sound if it is actually working (meaning it has a bad LCD or bad LCD connection). Your recourse at this stage is to find a replacement display. Club100 or another community member may be able to help you.

If it doesn't work you could have multiple problems, including a bad display, bad keyboard, or a problem with the mainboard.

== Otherwise ==

If none of the steps above lead you to a resolution, then more serious troubleshooting begins. Head over to the Model 100 mailing list (you can subscribe at [http://club100.org/list.html Model 100 Mailing List] )

[[Category:Model T Hardware Hacking]]

LaddieCon

2012-10-19T00:40:49Z

Jhoger: /* LaddieAlpha */

== What is LaddieCon ==

LaddieCon is a Model 100 disk drive emulator written for Microsoft .NET. However it does depend on
the Win32 API for access to the serial port. So it is completely portable to any Microsoft operating
system running .NET ;-) . This is for historical reasons only... when LaddieCon was written, there was no
serial port API in .NET. If you need a TPDD emulator for a POSIX system, you should be using [[DLPlus]] or LaddieAlpha.

Note that LaddieCon does NOT support TS-DOS directory extensions, but LaddieAlpha does.

To run LaddieCon, you need to have installed the .NET Framework redistributable from Microsoft.
Most likely if your system is up-to-date on patches this is already done.

== Download LaddieCon ==

[http://bitchin100.com/files/windows/LaddieCon.exe Download LaddieCon]

== Running LaddieCon ==

On your laptop, you must be running a TPDD client. TPDD clients include TS-DOS, TEENY, POWR-DOS, FLOPPY.CO or the WP-2 Disk mode.

REX Manager is also a TPDD client, though it is limited to transferring 32K image files rather than individual .DO and .CO files.

For the physical connection, you need a "null modem" wired serial cable to connect to a serial port on your Windows PC. You need to know which numbered COM port you are using on the PC side.

LADDIECON.EXE runs on a Windows computer, on top of the .Net Framework. To start it,

Click Start -> Run -> cmd.exe

Assuming LADDIECON.EXE is saved at c:\tools\laddiecon.exe

<code><pre>
For the M100/T102/T200:

c:\tools\laddiecon.exe com1 6

For the WP-2:

c:\tools\laddiecon.exe com1 8
</pre></code>

Here I put 'com1.' For your setup, the number may well be different.

If you are using a Tandy WP-2 word processor, make sure to change the '6' to an '8'. This is important because the WP-2 uses an 8.2 style (8 characters for the base name, 2 characters for extension) filename, while the Model 10x and 200 use a 6.2 style filename. If you don't set this properly, you will get weird behavior.

When you press ENTER, laddiecon should run until you hit CTRL-C. It won't appear to "do anything." It is completely "remote controlled" by your disk client on the Model T laptop.

== LaddieCon and Vista ==

LaddieCon is reported to work with Vista. However, you must run '''laddiecon.exe''' in "Administrator Mode." Also, your USB adapter must have a driver that is compatible with Vista.

To enable "Run As Administrator:"

# Find your '''laddiecon.exe''' executable with Windows Explorer.
# Right click on '''laddiecon.exe'''
# Select Properties->Compatibility Tab
# Check the 'Run as Administrator' option.

Note: if anyone knows a more fine-grained way to permit '''laddiecon.exe''' to access
the COM port without using Administrator Mode, please note it here.

If you're looking for a USB->serial adapter known to work with Vista, the following have been tested:

* '''USBGEAR U232-P9AP'''

Also, Chris Fezzler reports this device as working:

<code><pre>
Gigaware 6-Ft. USB-A to Serial Cable
SKU Model:26-949
Driver Date 6/25/2007
Driver Version 3.1.0.0
Provider: Prolific Technologies
Purchased at Radio Shack
</pre></code>

Please add any other adapters you verify work with Vista and LaddieCon.

The following devices are known not to work with Vista:

* Belkin USB-to-Serial cable '''Model F5U109'''. Despite having Vista driver, was unsuccessful in getting it to work.

== LaddieAlpha ==

More info to come. This is a new "cross platform" build of LaddieCon that works on both .NET and mono. So you can run the same LaddieCon on Windows, Linux and Mac boxes!

Advantages of LaddieAlpha over LaddieCon:

* Runs cross-platform
* Implements TS-DOS/Desklink directory extensions
* Maps/fixes up extensions presented to TS-DOS so .DO's misnamed .BA don't crash your laptop

The only disadvantage of LaddieAlpha is that it won't run on Windows 98 (that is, the .NET version it requires was never ported by Microsoft to Windows 98).

[http://bitchin100.com/files/linux/LaddieAlpha.EXE Download and test LaddieAlpha]

Example Linux invocation for use with a Model 100/102/200:

<pre>
mono ./LaddieAlpha.EXE /dev/ttyUSB0 6
</pre>

NOTE: On OSX, If you get an error about libMonoPosixHelper.dylib, mono may be finding the wrong shared library.

You need to edit the file /opt/local/etc/mono/config and change the relevant line as follows:

<pre>
<dllmap dll="MonoPosixHelper" target="/opt/local/lib/libMonoPosixHelper.dylib"/>

</pre>

== Reliable Text-Only Transfers ==

If you are only transferring text files, Hyperterminal is known to be a reliable way to transfer files even at 19200 using XON/XOFF protocol. Note that saving and loading text files via the TEXT application is much faster than TELCOM, because TEXT does not scroll the text to the screen as it captures.

See [[Text File Transfer using Hyperterminal]] for details instructions on getting Hyperterminal working.

[[Category:TPDD Service]] [[Category:File Transfer]]

Setting up RN42 Bluetooth on Linux

2012-09-05T18:31:13Z

Jhoger:

<pre>
Open a terminal prompt
jhoger@hegemon:~$ hcitool scan
Scanning ...
00:06:66:43:02:81 RN42-0281

Get the "Channel" using the sdptool program:

jhoger@hegemon:~$ sdptool records 00:06:66:43:02:81
Service Name: SPP
Service RecHandle: 0x10000
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

jhoger@hegemon:~$

Edit /etc/bluetooth/rfcomm.conf

#
# RFCOMM configuration file.
#

rfcomm0 {
# Automatically bind the device at startup
bind no;

# Bluetooth address of the device
device 00:06:66:43:02:81;

# RFCOMM channel for the connection
channel 1;

# Description of the connection
comment "Model T Bluetooth";
}

jhoger@hegemon:~$ rfcomm bind rfcomm0

jhoger@hegemon:~$ minicom -b 38400 -D /dev/rfcomm0

Light should come on red, and you should be able to communicate with the BT radio via HTERM.

Or, you can run with LaddieAlpha:
Use HTERM to set the baud rate to 19200bps:
$$$
su,19200
---

mono LaddieAlpha.exe /dev/rfcomm0 6
</pre>

Setting up RN42 Bluetooth on Linux

2012-09-05T18:28:28Z

Jhoger: