OK, here's a version of my TOS4 that:Rustynutt wrote: 29 Dec 2022 08:47 So you set Frank up with the TOS you integrated MAPROM (or fast RAM.prg) into a TOS binary, and he burned an EPROM, or flashed the DFB1?
...
I'd like to test your modification. If allowed, could I also request you edit the binary to set the Falcon control register bit setting for the Blitter to 1/2 (8MHz)?
...
Think you're able to correct the CRC AIRC.
1) Sets up an FRB (normal size, the 128 was just to prove a point);
2) Detects TT-RAM and declares it;
3) Skips the CRC check -- I don't correct it;
4) Blocks the Blitter and CPU from switching to 16MHz.
EDIT: since this is a DFB1 thread and this is custom for Rusty (it won't work in DFB1) I'll PM it instead.
This was simply a test to prove things then failed at 128k.So you've (well, Frank) been able to set the FRB at 128K, and successfully use the earlier version of HDDriver?
Uwe states the transfer size changes depending on various factors, so we couldn't simply guess it. Also the default he cited was 256MB, which is somewhat of a blocker to that approach! :lol:If increasing the FRB to 128K works under Frank's testing of file sizes, wouldn't it make sense to just set an FRB size to the maximum block sizes HDDriver uses for file transfers and just be done with it?
BW
