exxos's Atari, Amiga & retro forum

@frank.lukas I know. My point is that there is a mention of disabling blitter via NVDI, but nothing about hd driver. With patched tos 4.04 you will do nothing about hd driver.. I guess I have already patched tos in flash...

If blitter doesn't work with DFB1, it stands to reason that you shouldn't enable the blitter function in hd driver. But yes it probably *does* need to be documented somewhere.

@Steve It was configured long ago, so I didn't enabled it exclusively for installing DBF1X.. Is that hard to understand?

@nokturnal not sure what you're being so defensive about, I agreed with you, it should be documented and pointed out. But one should not be surprised that it doesn't work. It's good that you pointed it out for others to see.

frank.lukas wrote: 14 Jul 2023 07:19 DFB1 and Blitter do not work.

Use the patched TOS 4 from Badwolf with Fastram Support or EmuTOS ...

DFB1 and blitter work fine. But only within the restrictions of the blitter. Blitter can't address TT-RAM space so whenever somethign tries (whether it's HDDriver trying to blit into TT-RAM space or the VDI trying to blit from TT-RAM space), things will go wrong.

So yes, I'm afraid with any TT-RAM expansion HDDriver's blitter acceleration of IDE won't work. Booting to the desktop without NVDI (or alternative VDI) won't work either.

My patched TOS only declares TT-RAM, it doesn't solve the VDI or HDDriver blitter issues.

BW

HDDriver's "load into TT-RAM" probably won't work either as the Falcon DMA can't write to TT-RAM, unlike on the TT.

stephen_usher wrote: 14 Jul 2023 11:43 HDDriver's "load into TT-RAM" probably won't work either as the Falcon DMA can't write to TT-RAM, unlike on the TT.

The only DMA (blitter accelerated IDE aside) on the Falcon's hard disc side of things is for SCSI. Uwe has provided a fix for his SCSI<->TT-RAM transfers via the AB40Fix program, I believe.

Else I can't see why you couldn't load into TT-RAM. I'm not sure there's much benefit, mind. Of course, if you're running FASTRAM.PRG after the hard disc driver's been loaded it's a bit too late.

BW

The main advantage is that it doesn't take up valuable ST-RAM, but that's less of a problem on the Falcon as there's 14MB of that.

stephen_usher wrote: 14 Jul 2023 13:02 The main advantage is that it doesn't take up valuable ST-RAM, but that's less of a problem on the Falcon as there's 14MB of that.

Have you tried running a copy of HD Driver from the autofolder after alt ram had been installed?

Rustynutt wrote: 14 Jul 2023 21:22

stephen_usher wrote: 14 Jul 2023 13:02 The main advantage is that it doesn't take up valuable ST-RAM, but that's less of a problem on the Falcon as there's 14MB of that.

Have you tried running a copy of HD Driver from the autofolder after alt ram had been installed?

You'd have to boot from floppy to do that.