Jump to content
IGNORED

130XE Reverse Option Key for Basic


Diskwiz

Recommended Posts

If that's where you would do any other 16K XL OS

then I don't see why not, I don't have one so I

just don't know that part about it.

But it's a legit XL/XE OS all day long.

 

For emulator use it's not the best at least for

Win800 because there they like to use the patched

areas used here for their patches so sometimes

goofy things can start to happen.

 

Does it need to be in a different form for U1MB?

Edited by 1050
Link to comment
Share on other sites

  • 2 months later...

What does this version do?

 

Reviewing the past posts, here's the changes:

- XL base OS ROM (Self test does not test XE extended memory)

- Hias' hispeed patch

- Reverse Option for BASIC

- Fast Math pack patch

- Updated checksums so OS startup-check passes

 

This is pretty perfect - only minor update would be to make these changes using the latest XE OS ROM instead for the updated self-test to include extended XE memory test. I'll see if I can find /confirm a Rev D ROM that does this, maybe someone would be willing to patch that one with the above as well.

  • Like 2
Link to comment
Share on other sites

Yes, and it's broken. A bug in the code makes it test

two banks of the four original XE banks twice instead

of a genuine four bank test. Can only test those four

banks if it were fixed without writing new code.

 

Other problems exist where if you wanted to use the

code in an emulator you will find that the emulator

is also overlaying it's patch code into the areas

that this 'new' code was stuffed into and you'll

wind up with issues to say the least.

 

So I could post a fixed version, but I can't find the

message containing the fix, just spent hours looking

and I fear it was posted so long ago that the search

engine will not dig it up. Is it worth it for broken

code? I really don't think so. I used to until I

knew about the broken part.

  • Like 1
Link to comment
Share on other sites

Oh yuck! Yeah definitely not worth it. Again, it would have been interesting really only for acedemic reasons. I didn't even know about the additional RAM test until recently anyhow. There's so many better ways to test memory anyways. And from reading another recent thread about the XEGS ROM, since the keyboard table moved, some games like missile command will fail to read the keyboard if they don't go through proper vectors...

 

Overall very quickly declining interest in this idea. Thanks for trying to find the fixed version though. The best fixed version would be without the intentionally slowed down code in the memory test routines in the first place. :P

Edited by Nezgar
Link to comment
Share on other sites

So I could post a fixed version, but I can't find themessage containing the fix, just spent hours lookingand I fear it was posted so long ago that the searchengine will not dig it up.

I don't recall anyone posting a fixed ROM, but there are pointers for fixing it yourself.

 

Is it worth it for broken code? I really don't think so. I used to until I knew about the broken part.

The Self Test changes are not the only ones introduced in the XE OS rev. 3. They also fixed a bug in SIO that occasionally caused the "nine minute hang" when accessing a printer.

 

And from reading another recent thread about the XEGS ROM, since the keyboard table moved, some games like missile command will fail to read the keyboard if they don't go through proper vectors...

This issue is common to all XL/XE OS revisions, the XE and XEGS are not different from the XLs in this regard. Edited by Kr0tki
  • Like 3
Link to comment
Share on other sites

  • 6 months later...

Quite possibly yes, but the XEGS in my experience

had a mindset all it's own too. It would get 'latched'

into flaky behavior and do what it wanted in other

words. Not exactly sure what is going on there but

it might come back to the unusually high failure

rate of OS eproms on the XEGS. When that is borderline

then there is no telling where the real issue is.

 

Try to use 200ns speed eproms for burning the XEGS OS

and see if that isn't the reason first. Just a

suggestion, it does work better in other machines

when this can be done - but the XEGS isn't my go to

machine and I have no results to speak from.

  • Like 1
Link to comment
Share on other sites

There is also a capacitor that holds the memory like that, I forget which ATM but you can search it out. Does wonders for not losing type in code during slight power issues, but sucks when you just want to bop in and out and around when searching for or testing whatever it is your flitting to and from.

  • Like 1
Link to comment
Share on other sites

My theory is that the extended hang time for memory

on the 4464 equipped devices is the better silicon

used in those. Just keeps the memory cells at their

proper level of charge very much longer. And no work

around exists that I know of. So Mathy asked if there

was a software solution when I was writing MyRD code.

So I put in a keypress combo that will 'bomb' the

box and force a coldstart no matter what.

 

To do this fastest one does a RUN AT E477 and then

press SHIFT + 1 when the RUN AT screen goes away. It

will reboot twice, with the second one being the wipe

out bombed coldstart deal.

 

Since those times some of the newer toys also have a

software solution built into them and I would think

they are the better way to deal with this issue. Not

sure my method is foolproof since it must boot DOS

again in order to run the MyRD autorun.sys file too.

But it was the only stick I had so I used it. Just

for grins you might try it out?

http://www.mathyvannisselroy.nl/mydos.htm

  • Like 1
Link to comment
Share on other sites

Oh how I (not fondly) remember the days of hammering on the reset button on my 320XE for 30 seconds straight to try to get it to cold start to save my ramdisk with something valuable still on it after reset-proof crash.... eventually It would trigger a cold start if you hammered it fast enough!

  • Like 2
Link to comment
Share on other sites

Oh how I (not fondly) remember the days of hammering on the reset button on my 320XE for 30 seconds straight to try to get it to cold start to save my ramdisk with something valuable still on it after reset-proof crash.... eventually It would trigger a cold start if you hammered it fast enough!

omg I still do this!

Link to comment
Share on other sites

  • 2 weeks later...

Anyone update this with the Rev D OS to test for 128k?

See earlier in the thread. Rev. C added testing of the extended 64K in the 130XE, but due to a bug with the PIA bits used, it actually only tests 2 of the 4 banks. So, there's actually not much value in C or D vs B, as you're better off testing extended memory with a program written to do that. Especially if you have installed more than 128K.

Link to comment
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.
Note: Your post will require moderator approval before it will be visible.

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