exxos blog - random goings on

[dad664npc]

All okay with blitter enabled too :)

[exxos]

All okay with blitter enabled too :)

:shrug: Don't get why it fails on other machines but yours then. Which MB do you have exactly ? Also your cleaning booting TOS206 and not using NVDI or anything ?

[exxos]

I installed anti-bomb to see if it would give any clues..

But bus error ?! bus error accessing what ?! the only way I could really see it ending up like that is with corruption on the address bus or something where its trying to access a invalid address :shrug:

IMG_1025.JPG

I'm going to call this fault, YABADAP , Yet Another Bloody Atari DMA Apocalypse!


EDIT:

This not much help either.

IMG_1026.JPG

[dad664npc]

All okay with blitter enabled too :)

:shrug: Don't get why it fails on other machines but yours then. Which MB do you have exactly ? Also your cleaning booting TOS206 and not using NVDI or anything ?

520 STe CA4003290 Motherboard
Clean booting TOS2.06 - no AUTO folder
Remember - this STe was causing me no-end of problems with the PICO HDC until I replaced the CPU with the HC part - it's now good as gold

[exxos]

520 STe CA4003290 Motherboard
Clean booting TOS2.06 - no AUTO folder
Remember - this STe was causing me no-end of problems with the PICO HDC until I replaced the CPU with the HC part - it's now good as gold

The HC CPU generally fixes problems with the -38 DMA. Though in my tests it made no odds on CPU or DMA version.

My only other thought is to install NVDI as it replaces a lot of the blitter stuff. Beyond that, i'm out of ideas.

[chronicthehedgehog]

:shrug: Don't get why it fails on other machines but yours then. Which MB do you have exactly ? Also your cleaning booting TOS206 and not using NVDI or anything ?

520 STe CA4003290 Motherboard
Clean booting TOS2.06 - no AUTO folder
Remember - this STe was causing me no-end of problems with the PICO HDC until I replaced the CPU with the HC part - it's now good as gold

Interesting. I was wondering how you got it to work with HD driver. I have the same mobo, stock CPU.

[exxos]

Sadly while NVDI was a lot faster in deleting files, it still failed :(

Does anyone know of any blitter functions NVDI doesn't replace ?

IMG_1027.JPG

I have been looking through the TOS sources to see if there is anything which could potentially be different between TOS1.62 and TOS2.06, but not really finding anything which is seemingly of any relevance. Most of the switches seem to be for above TOS104 or above TOS200.

Other than it being a pure fluke that some code sequences cause problems with the blitter and some don't, that would mean *every* ST out there would likely have this bug.

On that note, I give up.

:2k2:


EDIT:
Oddly its still deleting my test files when I ran FLDER999.PRG with NVDI. :WTF: Will see how it goes...

[rubber_jonnie]

Ok, couldn't post earlier as I was off at training, however just deleting the empty folders was fine.

It strikes me as some sort of resource issue and I'm wondering if it's something to do with path length? Almost like a memory leak of some sort.

I'm going to try something and see if it works and I'll report back.

[exxos]

It strikes me as some sort of resource issue and I'm wondering if it's something to do with path length? Almost like a memory leak of some sort.

I'm going to try something and see if it works and I'll report back.

Try the FOLDRXXX.PRG It seems to ahve helped with NVDI installed.

I am currently copying my files again to try without NVDI. But when I tried FOLDRXXX.PRG before it did not change anything. :stars:

[exxos]

So without NVDI and using FOLDR999.PRG it crashed again. I don't get it. Will rety NVDI again.

EDIT:

NVDI on its own - nope
FOLDR999.PRG on its own - nope

FOLDR999.PRG & NVDI - nope (even though it worked earlier!)

So yep, No idea what's going on!