You can use
[CODE]
..
[/CODE]
tags to preserve the formatting.
I think I've reconstructed what you posted; a shame not to see it in its full glory.
Incidentally, it was
:D
which became the smilely face.
Code:
+-----------------------------------------------+
| |
| Date:00/00/00 Time:00:00:00 |
| |
| Boot volume:DiskDISK |
| Kernel: TRS-OS 7.0.0 |
| Serial #172839465 |
| |
| Auto command: n |
| SYSGEN: n |
| BREAK enabled: y |
| |
| 1. <NORMAL> Start OS normally. |
| 2. <UPDATE> Run system updates. |
| 3. <SAFE> Prompt sysgen auto debug etc. |
| 4. <BIOS> Edit volume tables etc. |
| 5. <RTC> Management tables for VOLUMES |
| 6. <POST> Run self tests. |
| 7. <DEBUG> Start debugger. |
| 8. |
| 9. |
| |
+-----------------------------------------------+
Function desired? 1
Starting-background-multitasking.
Executing_initialization_chain....finished.
IPL complete.
Auto_command:>_
No_AUTO_command
TRSDOS Ready
Hey, thanks for the fix and yes it looks great.
I want in future to make a load format module of this project available to those wanting to try it out on an eZ80.
One reason eZ80 & Z180 is so attractive is that as a programmer, I know what peripherals and their addresses are on every platform. SBCs based on Z80 can have serial ports, counters etc but each platform will be different from another unless some standard is followed.
This means when I get a Z180 version running it will actually run on a model 4 with Z180 accelerator card.
However, before I can proceed with allowing others to run this, I must come up with a policy to honor everybody copyrights.
If anyone ever looked at LOWCORE you would notice some very intense code for handling TRS80 file system. It is something that evolved over the years into a very tight solid piece of software.
I have reached out a couple of times to copyright holder(s) for permission to reuse some old code and how to properly handle this. I never received any reply leading me to believe there is no interest.
I do not feel right unless some proper notice is worked up and explored. There are ways around this as most anyone wanting to run this project already has a copy of TRSDOS containing this code.
In a telephonic conversation with Bill @ LSI one time (about 1986) he told me any future versions should replace current directory system with perhaps a multi-level directory.
I have given some thoughts to this but not made a decision yet. If current file system were to be disjointed from this OS and replaced with another it would finally fulfill come of Randy Cooks visions.
BTW...outside of memdisk there are almost no applications that use bank memory on a TRS80, some but I can only think of a couple. Memdisk is a great use of banks.
I stated in past I read somewhere on web someone was saying just ignore TRSDOS API and call things directly in memory. This is worst TRS80 advice I have read on web yet. This is a disaster under TRSDOS for several reasons.....code portability is least of your worries.
In THE SOURCE you will see OS code make calls to OS subroutines but that is different. Until you understand why and what differences are, you better steer clear of any advice like this. Far far away ;-)
Model 3 is different and not really related to this project. It is true that a lot of code in TRSDOS 6 API was code brought over from LDOS 5.x (I wasnt there but Timm Mann website makes a statement like this, and he was there ;-)
There is no reason to think if Tandy would have built a model 5 that there would have been backwards compatibility with models 1 or even 3.
Same source is used to produce TRSDOS for 2, 12 & 16 so it's fairly compatible.
Also, I read one time that Randy Cook would intentionally change locations and addresses of subroutines and functions to intentionally keep developers from calling routines directly but rather encouraged use of a API to access system functions.
If anyone were to study 6.2 vs 6.3 you will find some things moved.