You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
DO NOT USE MOBILE / CGNAT DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!

DFBX1 Issues

Discussion and support for the DSTB1 & DFB1 boosters by BadWolf..
User avatar
exxos
Site Admin
Site Admin
Posts: 27530
Joined: Wed Aug 16, 2017 11:19 pm
Location: UK
Contact:

Re: DFBX1 Issues

Post by exxos »

charon030 wrote: Wed Dec 03, 2025 7:30 am I'm pleased to let you know that this firmware resolves the issue for me! I didn't observe any more freezes during boot with Flash/50 MHz CPU/NetUSBee connected to ROM-Port. I've tried like 10 times or so.
Great stuff :thumbup:
I don't have any bus pull-ups at hand, so I can't test this at the moment.
No rush anyway.
Another issue is that the XBOOT graphics are corrupted with the patched TOS version in the Flash (to detect TT-RAM). It seems that XBOOT is using the VDI functions of TOS for that, making use of the Blitter. Thus I can't have a faster HDDriver (running from TT-RAM) and error-free XBOOT at the same time. Same issue existed for SuperVidel (as I found in some other thread on Atari-Forum I think). But a solution could be to launch NVDI even before XBOOT.
@Badwolf did the patched TOS. I'd assume it's behavior wouldn't change much over original 404.
User avatar
Badwolf
Site sponsor
Site sponsor
Posts: 2992
Joined: Tue Nov 19, 2019 12:09 pm

Re: DFBX1 Issues

Post by Badwolf »

exxos wrote: Wed Dec 03, 2025 5:18 pm
Another issue is that the XBOOT graphics are corrupted with the patched TOS version in the Flash (to detect TT-RAM). It seems that XBOOT is using the VDI functions of TOS for that, making use of the Blitter. Thus I can't have a faster HDDriver (running from TT-RAM) and error-free XBOOT at the same time. Same issue existed for SuperVidel (as I found in some other thread on Atari-Forum I think). But a solution could be to launch NVDI even before XBOOT.
@Badwolf did the patched TOS. I'd assume it's behavior wouldn't change much over original 404.
I've not tried patched TOS and XBOOT but I suspect you're right. VDI calls from TT-RAM would cause problems.

How about setting your PRGFLAGS on XBOOT to ST-RAM only?

The blitter isn't a problem per se, it's just that the VDI a) doesn't know not to try to use it when working with TT-RAM and b) doesn't have an alternative anyway. After all, the Initial Atari logo is hardware blitted to the screen but it comes from ROM and goes into ST-RAM. No harm no foul.

BW
DFB1 Open source 50MHz 030 and TT-RAM accelerator for the Falcon
Smalliermouse ST-optimised USB mouse adapter based on SmallyMouse2
FrontBench The Frontier: Elite 2 intro as a benchmark
charon030
Posts: 18
Joined: Thu Nov 27, 2025 8:09 am

Re: DFBX1 Issues

Post by charon030 »

Badwolf wrote: Thu Dec 04, 2025 11:17 am How about setting your PRGFLAGS on XBOOT to ST-RAM only?
Actually, that worked! I first tried to move NVDI before XBOOT in the Auto folder, but that didn't help. So I assume that usage of the blitter is part of the XBOOT code. But running XBOOT from ST-RAM does the trick, having the icons stored in ST-RAM where the blitter can find them.

Cheers!
Post Reply

Return to “DSTB1 & DFB1 booster by BadWolf”