Jump to content
IGNORED

New (alt) BIOS for Ultimate 1MB/Incognito


Recommended Posts

Loader was tested with numen.xex so hard to say what could be wrong. Does the HDD pass RWCRC test? New loader is not forgiving of dropped reads. It issues a multi-sector read of the cluster size and may burst the entire buffer into RAM. I'll add a slow option with retry and DRQ checks later.

Link to comment
Share on other sites

Loader was tested with numen.xex so hard to say what could be wrong. Does the HDD pass RWCRC test? New loader is not forgiving of dropped reads. It issues a multi-sector read of the cluster size and may burst the entire buffer into RAM. I'll add a slow option with retry and DRQ checks later.

Hi Jon, it does not seems to be anything related to the card inside of side2. Just tried to run my games from sio2sd and none of them can be loaded too. These were fine yesterday. Should I try to repeat some of parts of the flashing process just for the case something went wrong during that process?

 

post-34165-0-31536700-1450978262_thumb.jpg

Link to comment
Share on other sites

Hi Jon, it does not seems to be anything related to the card inside of side2. Just tried to run my games from sio2sd and none of them can be loaded too. These were fine yesterday. Should I try to repeat some of parts of the flashing process just for the case something went wrong during that process?

As long as you updated all three components (main BIOS, PBI BIOS and loader) there should be no problem. Flashes cannot be corrupted since they are verified, unless original file was somehow corrupt.

 

whats new in that rom?

Read the release notes for the latest Ultimate BIOS/Loader. This loader for SIDE is identical to that one.

Link to comment
Share on other sites

Hi Jon, it does not seems to be anything related to the card inside of side2. Just tried to run my games from sio2sd and none of them can be loaded too. These were fine yesterday. Should I try to repeat some of parts of the flashing process just for the case something went wrong during that process?

 

attachicon.gifpic.JPG

Sio2SD load xex problem vanished after switching off and on the machine. Sorry, this was misleading.

 

The problem with side2 loader and launching xex files is still here. These always freeze. I was trying to put side2 cartridge into unmoded 130xe and had the same problem. Then I flashed back the side2 with previous firmware and used it again in unmoded 130xe...then xex files loaded just fine. As you mentioned Jon, looks like new loader seems less forgiving to possible errors on cards inserted.

Edited by jk40001
Link to comment
Share on other sites

Sio2SD load xex problem vanished after switching off and on the machine. Sorry, this was misleading.

 

The problem with side2 loader and launching xex files is still here. These always freeze. I was trying to put side2 cartridge into unmoded 130xe and had the same problem. Then I flashed back the side2 with previous firmware and used it again in unmoded 130xe...then xex files loaded just fine. As you mentioned Jon, looks like new loader seems less forgiving to possible errors on cards inserted.

 

I'm wondering if this sensitivity to problems with the card is what caused my issues during the flash. In the past I thought my CF card was written off, but I managed to breath new life in to it through a low-level reformat under Linux. After that it read, wrote and checked out fine. However... It makes me think.

Link to comment
Share on other sites

Unless the HDD passed an RWCRC test, I'd be dubious about flashing firmware from it. The PBI BIOS contains the exact same double/missed read detection as found in the IDE Plus 2.0 BIOS, but by its very nature even that heavily unrolled code will not catch an equal number of dropped and repeated bytes on an unstable interface. Use of the original loader is therefore recommended in such cases.

Link to comment
Share on other sites

It should work just fine.

 

Out of interest, what brand of CF cards are exhibiting issues?

 

I have only got the one CF card - which is that one Lotharek sold me; a 4GB "SanDisk" consumer brand. To be totally honest I cannot say if this absolutely was the problem, but from what you have said it sounds possible. Whatever the case I have never seen that 'SystemError' message come up before.

Link to comment
Share on other sites

If you have an SIO2XXX device on which to host flash ROMs, it should be simple to eliminate the brand of CF card as the cause of mangled BIOS ROMs. Uflash exploding mid-flash suggests some rather disastrous stability issues, however. The software was tested here on half a dozen PAL Ataris using SIDE2 and Sandisk CF cards.

  • Like 1
Link to comment
Share on other sites

If you have an SIO2XXX device on which to host flash ROMs, it should be simple to eliminate the brand of CF card as the cause of mangled BIOS ROMs. Uflash exploding mid-flash suggests some rather disastrous stability issues, however. The software was tested here on half a dozen PAL Ataris using SIDE2 and Sandisk CF cards.

 

You are probably right; I have not had an easy time getting any of my 3 decrepit 800XL's to run at all. Initially, way back at the beginning of my adventures in hardware modding I could not get the SIDELoader to recognize the CF card contents. That seemed to be a PHI2 issue which a new 74F08 chip appeared to cure. However, it is possible the machine as a whole is not up to the demands of the new software where other, more robust systems can cope. One of the chaps mentioned it was a phenomena that some 800XL's for whatever reason have bad PHI2 propagation and cannot be modded. Perhaps that is why it flashed in the past but failed when using the new BIOS's and Loader.

Link to comment
Share on other sites

So that's many, many, many? Right: I'll look into it anyway. Anything which doesn't run, if posted here, will be checked out. Note that the thread charting development of the original loader ran for a long time, and since the new loader is not based on the old loader in any way shape or form (being an original, ground-up rewrite) and has only been out for a couple of weeks, it's not going to be "mature" for a while yet.

Link to comment
Share on other sites

sorry, but thats developmnent reality

 

testing.. testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..
and then release

Link to comment
Share on other sites

sorry, but thats developmnent reality

 

testing.. testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..testing..

and then release

Edited and my comment to w1k deleted only because it is Christmas Edited by jk40001
Link to comment
Share on other sites

You should have left it: as a confirmed Bah Humbug, I would have enjoyed reading it. If his bug reports were delivered in a less abrasive, belligerent and vague manner I wouldn't have to ignore them going forward. In the meantime, I downloaded and tested the mentioned demos and as far as I can tell they appear to work fine. Regarding those which don't, or perhaps display screen corruption, etc, this is usually the result of the game or demo failing to initialise RAM. I tested a couple of demos during development which crashed if the screen editor was opened prior to loading simply because the display list area wasn't completely filled with $00. This is pretty shabby coding but doesn't usually get caught with software tested primarily with the emulator's XEX loader. Of course we can do our best to make the loader work around such issues (hence the as yet unimplemented "Open Editor" option), but I'm not going to accept the failings of lazily written software as criticisms of the loader.

 

I'm really appreciative of the people who wish to help and who acknowledge that I can't personally sit here and test every XEX in existence. The hope is that people will try the loader and come back with some sensible feedback to help me correct faults and make improvements. Otherwise - Candle's loader being perfectly functional - I can quite happily abandon it and leave the thing languishing in an unfinished state, since there are plenty of other things vying for my attention. ;)

Edited by flashjazzcat
  • Like 2
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...