Jump to content
InsaneMultitasker

Horizon RAMdisk ROS and CFG

Recommended Posts

My SAMS is fully functional. AMSTEST4 verifies that it is there and everything is working correctly. All of the programs load and run fine and TurboForth finds it quite nicely. It has been my experience that Classic99 does NOT always mirror real TI gear. MESS seems to be more accurate as far as emulation is concerned.

Share this post


Link to post
Share on other sites

My SAMS is fully functional. AMSTEST4 verifies that it is there and everything is working correctly. All of the programs load and run fine and TurboForth finds it quite nicely. It has been my experience that Classic99 does NOT always mirror real TI gear. MESS seems to be more accurate as far as emulation is concerned.

Thanks. I am sure the problem is with the routine or some interpretation of how the SAMS card functions. I ran AMSTEST4 and noticed you had a hand in modifying the program. Does the original source exist? Maybe Brad's code only works with the smaller capacity AMS card.

Share this post


Link to post
Share on other sites

ah, I nearly forgot the FOUNDATION 128K: was undefinable, so I checked the the DSRs again:

 

 

 

 

post-41141-0-82732300-1438126293_thumb.jpgpost-41141-0-57444500-1438126328_thumb.jpgpost-41141-0-11997800-1438126337_thumb.jpg

Share this post


Link to post
Share on other sites

 

If the IDE is recognized as the SAMS, just because the CRU-address >1E00, the DSRs maybe are not read out from the cards ?

Maybe only the CRUs ?

But if Atrax´ card is running, and using >1E00, it should be shown in the ROSCFG832C.....

Maybe you can check the presence of the card (and the DSRs) once with Fred´s DU2K ?

...just to see whats happens.

Share this post


Link to post
Share on other sites

SAMS detect from Willsy

 

: SAMS? CR ." SAMS Memory card" $3000 @ 994a $3000 ! 255 $3000 >MAP $3000 @ 994A = IF ." not " THEN ." found " 0 $3000 >MAP $3000 ! ; SAMS? CR

 

That definition is flawed:

  1. The line is too long. It cannot be longer than 80 characters or the console reaches around you and taps the Enter key for you. :-o
  2. Even though the default in TF is for case insensitivity, ‘994a’ is not recognized as a hexadecimal number, even in HEX mode.
  3. Furthermore, if the current radix is 10 (likely), ‘994A’ must be preceded by a ‘$’.

The following should work for whatever radix is current:

: SAMS? CR ." SAMS Memory card " $3000 @ $994A $3000 ! $FF $3000 >MAP 
$3000 @  $994A  = IF ." not " THEN  ." found " 0 $3000 >MAP $3000 ! ;

[EDIT: Note the change from ‘255’ to ‘$FF’ to ensure radix insensitivity.]

 

...lee

Edited by Lee Stewart

Share this post


Link to post
Share on other sites

THIERY´s IDE:

 

I felt boring, so I digged it out, and set it from CRU >1F00 to >1E00 :)

so it was recognized as AMS/SAMS-Card (?) I think just by the address? hmmmm

So the DSRs seem not to be detected, or to misinterpreted...

 

IDE cards should not be placed at a high CRU :)

 

The SAMS detection over-rides any other card identification for CRU 0x1E00. I did this for testing purposes. The only time it will happen is if RAM is found in the DSR space. I am fairly certain Fred's DSR is supposed to lock the DSR as read-only for normal operation. Maybe the SAMS detection enables writes to the DSR. Interesting! The Brad Snyder method will not detect the IDE; however, since it writes to the mapper addresses, Fred's DSR might suffer.

 

Please reset your IDE to another CRU address :)

 

Edit: Foundation also will not work because of the AMS test code I redid. Consequences, consequences... Time for a break.

Edited by InsaneMultitasker
  • Like 1

Share this post


Link to post
Share on other sites

Old farts and packrats NEVER throw anything away. I have the source, I'll just have to find it.

 

I'm an old fart AND a packrat, but I can never find anything in the mess. You must be more organized than me. :)

Share this post


Link to post
Share on other sites

Lee,

 

That's how it is on my boot blocks. I just wrote it all out in a single line instead of trying to put it into a proper block format.

 

You said it did not work. What I posted works in Classic99 with SAMS enabled/disabled.

 

...lee

Share this post


Link to post
Share on other sites

Lee,

 

You are correct (as usual) I forgot the "$" in front of 994A. It is too long to enter in command mode. It appears as several lines in my boot blocks.

Share this post


Link to post
Share on other sites

Tim,

 

Check you inbox for the AMSTEST4 source.

I implemented Bruce's check, although I don't see how it can be considered a test. It isn't doing anything different to the 16 registers than what I did originally with one.

 

Anyway, here it is. CRU 0x1E00 may display two devices as I wanted to allow both detection routines to operate. Let's see what happens.

 

CFG832d is on the disk.

ROSCFG832C-3.dsk

  • Like 1

Share this post


Link to post
Share on other sites

OK - this is what happened. The latest version correctly finds and identifies the SAMS card as "AMS/SUPER AMS" at >1E00. You have struck again!

Edited by atrax27407

Share this post


Link to post
Share on other sites

However, another bug has crept in. Instead of a reasonable return when pressing FCTN-= and allowing MENU to re-boot. I get a colorful screwed up screen. Almost there! All that needs to be done is make sure we use a BLWP @0000 for a re-set.

Edited by atrax27407

Share this post


Link to post
Share on other sites

However, another bug has crept in. Instead of a reasonable return when pressing FCTN-= and allowing MENU to re-boot. I get a colorful screwed up screen. Almost there! All that needs to be done is make sure we use a BLWP @0000 for a re-set.

 

 

I will have to inspect the TEST routine. There may be some trick that need to be performed after the testing. If the FCTN-= worked in the previous "C" version, then it may be simple to track down. I have no idea why this routine works... I may need to find my SAMS card this weekend or it will bug me! Thanks Atrax.

Share this post


Link to post
Share on other sites

I am so confident that you will succeed quickly that I have moved some small programs from DSK4 to DSK5 to make space for the slightly larger CFG832x when it is finished. I also altered my RAMdisk backups accrodingly.

Share this post


Link to post
Share on other sites

I implemented Bruce's check, although I don't see how it can be considered a test. It isn't doing anything different to the 16 registers than what I did originally with one.

 

Anyway, here it is. CRU 0x1E00 may display two devices as I wanted to allow both detection routines to operate. Let's see what happens.

 

CFG832d is on the disk.

 

I tried the CFG832D on the disk and it successfully detected my Super AMS card!

 

post-35187-0-57057800-1438201384_thumb.jpg

Edited by Cschneider
  • Like 1

Share this post


Link to post
Share on other sites

 

I tried the CFG832D on the disk and it successfully detected my Super AMS card!

Whew. Now... like Atrax, did you get a colorful screwed up screen when you hit FCTN-= ? If not, what cartridge are you using?

Share this post


Link to post
Share on other sites

Whew. Now... like Atrax, did you get a colorful screwed up screen when you hit FCTN-= ? If not, what cartridge are you using?

 

No colorful screen when I hit quit. I tested it with both Editor Assembler Cart and XB 2.7 Suite cart.

Share this post


Link to post
Share on other sites

OK - I tried running CFG832D from "Rum Program File" in MENU. the F'WEB loaders, REA 2015, and got exactly the same results upon quitting. A colorful wierd screen. All of a sudden, for unfathomable reasons, it has finally decided to "play well" with my system. I have no idea why or what the initial problem was with its exit but it is working fine now. Gremlins?

Share this post


Link to post
Share on other sites

OK - I tried running CFG832D from "Rum Program File" in MENU. the F'WEB loaders, REA 2015, and got exactly the same results upon quitting. A colorful wierd screen. All of a sudden, for unfathomable reasons, it has finally decided to "play well" with my system. I have no idea why or what the initial problem was with its exit but it is working fine now. Gremlins?

 

Sounds like SPIKE was at it again.

Share this post


Link to post
Share on other sites

 

Sounds like SPIKE was at it again.

 

It's a vdp register problem, or maybe not clearing the status byte before quitting.

 

Should be an easy fix.

 

Gazoo

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...