Briel Computers support forum

garryj wrote:I guess two places, due to the forum's two link limit ...

Propeller Terminal ANSI/VT100 Escape Sequence Summary
Altair 8800micro v5.0 Addendum

A zip that has the above docs plus Jeff Trantor's excellent QuickReference, in pdf format:

Does anyone know of a way of getting a £ symbol to show up! The terminal emulates what was available in the day, which was 7-bit US ASCII. The U.S. keyboard shift-3 "#" character, ASCII code 35 (decimal) is used to represent the British sterling pound currency symbol. You may or may not k...

Sounds good Garry -- I've had good luck running C# CLR stuff on Linux using Mono so if you want some testing on that let me know. Will do. Although I'm comfortable with Linux, I do spend most of my development time in the Windows environment. I'm aware of Mono, but that's about it. I see in their F...

Garry, this post inspired me to write a converter to go from DSK to CPM format so you can read using cpmtools. See https://github.com/wd5gnr/diskcvt I'll try to update it soon so it could go back the other way but out of time for now. If anyone uses this, let me know it is working for you as it is ...

18 02 30 EA 65 ED 65 EE 85 E9 A2 04 B5 E9 95 EA CA 10 F9 38 E9 99 B0 E8 A5 EB 29 = 0FE8 My bad. I re-read the spec, and the record is indeed the entire line. The 24 bytes I called the record make up part of the "Battleship" program data. The 27 byte sequence within the square brackets is ...

The checksum is computed by adding one byte (two hex digits) at a time. That's why the example paired the nibbles up.

Just to be clear on the checksum, my mention of big-endian meant how to interpret the checksum in the dump printing, and not how it may be stored in memory. With 27 data bytes, you'll never overflow a 16-bit result. When I add the 27 data bytes in my example I get the 0FE8 checksum result.

My understanding of the spec still isn't right. . The record/data definitions are a bit confusing. Using the third line in your "Battleship" dump, the format breaks down like this: ; [18 02 30 <EA 65 ED 65 EE 85 E9 A2 04 B5 E9 95 EA CA 10 F9 38 E9 99 B0 E8 A5 EB 29>] 0FE8 The 24 bytes wit...

Is there a specification for the paper tape dump? Yep: The paper tape LOAD and DUMP routines store and retrieve data in a specific format designed to insure error free recovery. Each byte of data to be stored is converted to two half bytes. The half bytes (whose possible values are 0 to FHEX) are t...

you just can't use Control+Alt+F1 which is strange because it shows the same prompt and seems to work but it doesn't pace with the BASIC interpreter. Hi Al, long time, no read <g>. It looks like I left Ctrl-Alt-F1 undocumented, other than some comments in the Terminal code. It's a text file transfe...

I've tried it, but there doesn't appear to be a diskdefs parameter that tells it the 128 byte CP/M sector is at a 3 byte offset within the 137 byte physical sector of the 88-DCDD disk system. The source is available, but I've never had the time to see what it might take to tweak it to work with the ...

Sorry if this has been answered before - Is there a way to unpack files from a .DSK image in windows? TIA Not that I know of. The original Altair 88-DCDD disk controller that is emulated pre-dated CP/M and used a physical sector size of 137 bytes instead of the 128 byte (and multiples thereof) sect...

tranter wrote:Garry: Did you get a chance to dig up the sources for the TUTILS?

Not yet, but I think I'll be able to free up some time, hopefully this week. I apologize for the delay, but things have been quite hectic this last month or so.

The T* utilities (TREAD, TWRITE, etc.) also don't seem to have source code available for them. I know they are written in C - I'd be interested in getting the source code and possibly modifying it to add new features. I used the BDS C package for the "T" utilities. There is a small librar...

If you've upgraded to v5.2 of the terminal and you are using CP/M 2.2 with a BIOS version prior to v1.1 , the TUTILS.DSK image that's in the v5.2 update .zip file won't be readable, as it has the disk sector skew that's used by CP/M 3 and CP/M 2.2 BIOS v1.1 and newer. To upgrade your CP/M 2.2 BIOS t...