Trubo Oberon (Announce)
> > Version 07-07 didn't seem to like native DOS (FD or MS 7), but
> > DOSBox-X was fine.
>
> I swear 07-12 (TOC.EXE) is giving me "Invalid Opcode" under FreeDOS,
> but it seems fine under MS-DOS 8. I tried running EMS Magic (TSR), but that
> didn't help ("not enough memory").
I tested Trubo Oberon under some environments.
Windows 98: Error message: "Not enough memory" (but MEM shows about 545Kb free)
standalone MS-DOS 7.1 (with HimemX+JEMM386): computer hangs
FreeDOS, kernel 2044 (with HimemX+JEMM385): it WORKS.
However I don't like how the compilation process is invoked.
Why "TOC CALENDAR.MOD" does not brew the CALENDAR.EXE? In place of that only some CALENDAR.OM is created.
But if that has some good reason, why it is not enough to just write something like "TOC /L CALENDAR.MOD"?
Why the hell I have to write "TOC /Entry=Run CALENDAR.MOD?"
How shall I know that the valid entry point is just Procedure Run?
It is not guarranted at all.
So i in theory I have to inspect every MOD file and have to analyze it and find some procedure which looks as a entrypoint.
It seems to be quite awful for me.
---
DOS-u-akbar!
Complete thread:
- Trubo Oberon - rr, 08.07.2026, 21:24 (Announce)
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- Trubo Oberon - Rugxulo, 15.07.2026, 03:18
- Trubo Oberon - Rugxulo, 16.07.2026, 20:54
- Trubo Oberon - Rugxulo, 20.07.2026, 07:54
- Trubo Oberon - Laaca, 21.07.2026, 23:05
- Trubo Oberon - Rugxulo, 23.07.2026, 07:15
- Trubo Oberon - Laaca, 23.07.2026, 18:57
- Trubo Oberon - Rugxulo, 24.07.2026, 21:34
- Trubo Oberon - Rugxulo, 27.07.2026, 07:52
- Trubo Oberon - Rugxulo, 24.07.2026, 21:34
- Trubo Oberon - Rugxulo, 04.08.2026, 13:16
- Trubo Oberon - Rugxulo, 31.08.2026, 09:49
- Trubo Oberon - Laaca, 23.07.2026, 18:57
- Trubo Oberon - Rugxulo, 23.07.2026, 07:15
- Trubo Oberon - Laaca, 21.07.2026, 23:05
- Trubo Oberon - Rugxulo, 15.07.2026, 03:18
Mix view