Jump to content
Tursi

Classic99 Updates

Recommended Posts

14 hours ago, Tursi said:

Not sure if it will mean much to programmers

I don't know what the hell you're talking about yet I greatly appreciate your efforts in maintaining my favorite emulator. Thank You!

  • Like 4

Share this post


Link to post
Share on other sites

Is this related to the level II/Level III Disk Routines that caused some many problems in the early days of MDOS?

Share this post


Link to post
Share on other sites
10 hours ago, dhe said:

Is this related to the level II/Level III Disk Routines that caused some many problems in the early days of MDOS?

I can't tell you anything about MDOS. ;)

 

  • Like 2

Share this post


Link to post
Share on other sites

Classic99 399.037

 

This took substantially longer than I intended, but I reviewed and re-commented every single opcode to make sure I wasn't missing anything, in order to get memory accesses correct. I also updated every memory read function in order to gain tighter control of cycle counting with respect to the read-before-write cycles. To that end, 9 opcodes were updated (4 were mostly rewritten), although one of those was probably not wrong before I changed the memory system. ;) This even included jumping into the data book to verify a couple of memory accesses I had documented but hadn't coded, as they were unclear. So hopefully, this will be it. ;)

 

The overall effect, though, is generally going to be pretty small. From the user's standpoint, you won't see much difference - indeed the error was within the margin of error of the CPU clock. But for programmers, cycle counting should be more correct, particularly on the byte instructions which was where most of the work went. STCR was outright missing a dummy read I knew about, and XOP, B and BL were missing dummy reads I didn't know about but had documented anyway! ;)

 

Since I changed a fair bit, I ran a number of regression tests as well as reviewing the changes multiple times, so I think it's okay!

 

Anyway... usual places... http://harmlesslion.com/software/classic99

 

 

 

  • Like 17
  • Thanks 3

Share this post


Link to post
Share on other sites

Hi Tursi,

 

since classic99 399.032 I was'nt able to assemble a compiled XB program with the XBGDP internal assembler.

If I use the external Asm994a assembler all is working.

 

 

I used a simple "PRINT HELLO" program and in the version v399.030 all is fine:

TEST

 

image.png.561ae4c381088d018f4356440f30bcce.png

 

Since classic99 v399.032/033... if I will assemble this I get the following screen:

 

image.png.39b2f713bd76d5ec9a47f5c48fb6e280.png

 

 

 

Perhaps the cause lies in seniorfalcon's XBGDP program. However, this worked very well up to and including v30.

Share this post


Link to post
Share on other sites

I need a step-by-step to reproduce the issue, a screenshot isn't enough. Even then, I don't know the compiler, but at least it's a start.

 

However, here's the diff between 30 and 32:

https://github.com/tursilion/classic99/compare/9d40c8ab6f8ac5628ddd58c83c751079751de95c..c6f1e02e0deab7cf01b55f947c7a1d6a3800a4f4

 

I don't see anything obvious in there, but you are saying if you go back to v30, you can run this correctly?

 

Share this post


Link to post
Share on other sites
3 hours ago, Tursi said:

I need a step-by-step

Hi Tursi,

This is the .zip with the functional v399.030. I used.
 

_classic99_399-030.zip

 

The step by step is easy:

 

1. Run classic99 from the .zip. The cartridge is TI-Extended Basic and the DSK1=...\_classic99_399-030\ISABELLA6\

2. Select "2" for TI Extended Basic

    -> This will autoload the ISABELLA6 menu

3. Use Arrow down for Extended Basic + ENTER

4. >OLD DSK1.TEST + ENTER

5. >SAVE DSK1.TEST + ENTER   *** From now on you can only press ENTER when the program asks for an input!

6. >SAVE DSK1.TEST-M,MERGE press ENTER

7. >RUN "DSK1.LOAD" press ENTER
    -> the ISABELLA6 menu is on the screen

8. Select Compiler press ENTER
   -> The compiler asks for some files, you can always press ENTER (6 times) for the defaults.
   -> After the compiling the ISABELLA6 menu is in the screen again

9. Select Assembler press ENTER

   -> In classic99 later than v030 this step shows the destroyed screen and a terrible sound! 
   -> In classic99 v30 and earlier the assembler asks for some files, you can always press ENTER (5 times) for the defaults.
   -> The assembler is executing 

10.  Press ENTER if the assembly is finished and it shows 0000 ERRORS
   -> the ISABELLA6 menu is on the screen

11. Select LOADER press ENTER
   -> the loader asks for some file names, you can always press ENTER (4 times)

12. The compiles program is running and shows "HALLO"

 

I mapped the "ISABELLA6" folder in the actual classic99 v37 and got the described issue.

 

Share this post


Link to post
Share on other sites

Hi Tursi,

 

I changed the classic99.ini file from the functional v030 to my non functional v037 and now the process is working!

 

So it seems that my classic99.ini has been corrupted since v032.

 

Thanks for looking at my issue!

Here is my defective ini file, but you don't need to take any further action here.

classic99-corrupt.ini

 

EDIT: I changed the ini file back and the issue is there, so it was the ini file!

Edited by wolhess
Additional Info
  • Like 2

Share this post


Link to post
Share on other sites


 

42 minutes ago, wolhess said:

Hi Tursi,

 

I changed the classic99.ini file from the functional v030 to my non functional v037 and now the process is working!

 

So it seems that my classic99.ini has been corrupted since v032.

 

Thanks for looking at my issue!

Here is my defective ini file, but you don't need to take any further action here.

classic99-corrupt.ini 8.46 kB · 1 download

 

EDIT: I changed the ini file back and the issue is there, so it was the ini file!

 

As I can see, there are some small differences in the INI files.

Just a thought, maybe you set them back, one by one ?

(Not sure if I saw all the changes, but I think so)

 

FIAD_AllowNoHeaderAsDF128=1 (BEFORE IT WAS: 0)

FIAD_EnableLongFilenames=1 (0)

cputhrottle=0 (1)
systemthrottle=1 (0)

EnableF18A=0 (1)

ScreenScale=-1 (1)

 

Good luck

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

Thanks Wolfgang, I need to give that a try, the directions for using Isabella got me somewhat overwhelmed I can follow this and give it a try... Thanks!!

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...