TurboPascal99 Questions

[lucien2]

That's problably the same problem I just described in this post: http://www.atariage.com/forums/topic/185137-bricks-demo/page__st__50?do=findComment&comment=2609401.

 

I tried to run WURM from the demos, it has the same problem and it was not compiled with my patched compiler.

 

I had to add BEGIN to your code to compile it (error 28).

 

PROGRAM T1;
BEGIN
 WRITELN(9900);
END.

[+retroclouds]

duh, yeah that was a typo there.

 

I created a disk image that runs from DSK1 and that also has RUNLIB on there.

So were you able to do a full-cycle on the TI-99/4A or was it in classic99 ?

 

BTW I did manage to load/compile/assemble/link your version of the BRICKS demo using classic99. Very nice!

Edited October 1, 2012 by retroclouds

[lucien2]

I just tried the full cycle with the hardware, it works.

 

The generated EA5 program runs even after a cold start. That was not the case with classic99 and MESS (it does not load RUNLIB).

[+Vorticon]

I just tried the full cycle with the hardware, it works.

 

The generated EA5 program runs even after a cold start. That was not the case with classic99 and MESS (it does not load RUNLIB).

 

So can I assume that you have succeeded in patching TP99 so it works without errors? This is so great! Can I upload your files to the Development Resources TP99 section and replace the old files?

[lucien2]

Sure. I hope there's not a typo in the code I typed from Retroclouds's screenshots.

You can double-check it, it's from >FDC0 to >FEE0.

[+retroclouds]

So can I assume that you have succeeded in patching TP99 so it works without errors? This is so great! Can I upload your files to the Development Resources TP99 section and replace the old files?

 

If done I can then also add it to the 'Programming Languages' section in the Development Resources thread.

Guess we could do a zip file for emulation and a disk image for the CF7+ for using on the TI-99/4A

[+Vorticon]

While this works perfectly fine in Classic 99, I can confirm that it unfortunately does not on real hardware... All I get is a blank blue screen, but the computer does not lock up. Same with the WURM program. What's on the real hardware that is not being correctly emulated by Classic99 that could account for this?

For reference, my hardware setup is a stock console with F18A, 32K, IDE card, RS232 with HDX and 2 DSSD drives. Pretty mundane stuff by the standards of the day. As retroclouds mentioned above, could this be related to the F18A?

Edited April 6, 2013 by Vorticon

[lucien2]

Here's my hardware list used to run it without problem: stock console and nanopeb.

[+Vorticon]

Here's my hardware list used to run it without problem: stock console and nanopeb.

So I repeated the process using only my console with F18A and the CF7+, and I got the same problem. Therefore, since the only difference between your setup and mine is the F18A, I can only deduce that the problem lies with that. Matt, any thoughts on this?

[lucien2]

Just to be sure that it's not the same problem that Tursi described here, I edited WURN to always load RUNLIB without checking the RAM contents (I replaced JEQ >FFD0 with >0000).

 

If you can run the edited WURM, then it's the same problem.

WURM.zip

[+Vorticon]

Nope, same issue again, so I suspect it's a video issue since all I get is a blank screen...

[Tursi]

Just to butt in here -- you're making sure that the file "RUNLIB" is available on DSK1, right?

 

[+Vorticon]

Just to butt in here -- you're making sure that the file "RUNLIB" is available on DSK1, right?

Yes

[+Vorticon]

By the way, why is the compiler not creating object tagged code files from source? I thought the original TP99 did that so there was no need to separately assemble the code prior to linking...

[lucien2]

In the RTF file translated by apersson850, it's written:

The source program is syntactically checked, then converted to machine language converted and saved to file.

 

Not clear, but assembly source could also be described as machine language.

 

There is also a file in german "KURZANL" for Kurzanleitung (Short description).

 

Ablauf: Programm mit Editor eingeben

------- Danach abspeichern (SA Filename)

Dann compilieren (CO Filename)

Assembler laden (ist mit auf der Diskette!)

Das compilierte File assemblieren

Das assemblierte File linken

 

It's written that you must load the assembler from the floppy and assemble the compiled files.