Problem running SAMS TI-Nopoly on console

[twoodland]

Good day everyone. I need your help! What am I doing wrong?

Goal: To play TI-Nopoly on real iron.

Issue: Loading EA5 "ABOOT" on Classic 99 loads menu option E "TI-Nopoly". Loading the same file from the TI Console does not load option E.

Hypothesis: The AEMS boot script is not finding the SAMS memory.

CFG: TI-99/4A console w/Speech Synth, PEB (FlexCable Interface, TI32K, TIRS232, TIPI-PEB, SAMS 1024K, TIDisk Controller)

Attachments:

Files in Directory:

Classic 99 Screen Shot 1:

Classic 99 Screen Shot 2:

Real Iron Screen Shot 1:

Real Iron Screen Shot 2:

[Asmusr]

Have you tried if other SAMS software is working? Dungeons of Asgard, for instance.

DOA.dsk

[twoodland]

Have you tried if other SAMS software is working? Dungeons of Asgard, for instance.

 

Asmusr,

 

Yes. I typically run RXB's "In The Dark" game:

 

 

And just tried "Dungeons Of Asgard". Thank you so much!!!

 

[+adamantyr]

Does DOA use ABOOT, or it's own custom loader?

[Asmusr]

Does DOA use ABOOT, or it's own custom loader?

 

It's a custom loader.

[RXB]

Does DOA use ABOOT, or it's own custom loader?

ABOOT is a good menu program but I do not know if anyone fixed the issue of the address it starts in a XB cart or RXB or SXB as it ignores the Random Number Generator and non standard start of cart.

 

FW had the same issue why every XB game ran from FW always used the same exact random numbers., you never got random results ever.

 

Also it did not initialize all of XB variables or clear all of them, thus a very small number of XB programs crahsed, specially in RXB as it used odd address that

 

was not supposed to be the starting point of XB GPL code.

 

GROM ADDRESS >633B is the start address supposed to be used in any XB cart. If I remember (I could be wrong) ABOOT and FW and MENU were using >63D3

Edited May 2, 2019 by RXB

[Tursi]

I have to note I don't know very much about the ABOOT and the AEMSSYS boot script - but did you try looking at the latter to see if there is any hard-coded paths that don't apply to your machine?

[atrax27407]

It is probably an error in AEMSSYS not pointing to the correct pathname. Give us a look at your AEMSSYS file.

[twoodland]

Success! Thanks to all of you for your help! It ended up being a simple issue that I had overlooked. If you look at my files screenshot. The AEMSSYS script file has the Attibute of "Classic". I converted this file to TIFILES and it loaded on the console. I feel embarrassed, but am very thankful for your input.

[twoodland]

It is probably an error in AEMSSYS not pointing to the correct pathname. Give us a look at your AEMSSYS file.

atrax27407 FYI here is the contents of the AEMSSYS file. Last night I noticed that it had the attribute of "Classic" so I converted it to TIFILES format using Ti99Dir and it the console was able to read the file

 

*

* AEMS Boot Script

*

RAM 1024

*

SW99

MENU DSK1.TIN_A,'TI-Nopoly'

*

......................

[Tursi]

Success! Thanks to all of you for your help! It ended up being a simple issue that I had overlooked. If you look at my files screenshot. The AEMSSYS script file has the Attibute of "Classic". I converted this file to TIFILES and it loaded on the console. I feel embarrassed, but am very thankful for your input.

Grr, I asked Fred not to do that... it's not a Classic99 file, it's a corrupted file header.

 

Oh well, glad you found the issue!!