« Reply #1 on: May 13, 2019, 04:53:05 AM »
I hear in OS3.1.4 that the max transfer bug should now be gone correct?
Addressing the above (I knew I should have saved the link!), and you may not believe this, but the Max Transfer bug is STILL THERE! I am quoting from ThoR's own post, I think on EAB, stating you must still set MaxTransfer to 1FE00. I'm not kidding either. It would be nice if a biggie blunder like that were made public across the major Amiga forums. Maybe Thomas will see this and weigh in on the post where he admits that the MT bug never got fixed in 3.1.4's current release. It's late or I would go search for the post - been looking but I can't find it now.
In the mean time, try setting to 1FE00. Can't guarantee it will help but it's worth a try I suppose. Also, maybe Thomas will provide some pointers as you're using OS3.1.4.
« Last Edit: May 13, 2019, 04:54:42 AM by giZmo350 »
Logged
A500: 2MB Chip, 8MB Fast, IndiECS, MiniMegi, IDE4ZorroII on Z-500, KS1.3/KS3.1, WB3.1&BWB
A2000HD: 2MB Chip, 128MB Fast, P5:Blizz 2060@50MHz, PCD-50B/4GBCF, XSurf100, RapidRoad, IndiECS, Matze RTG, MiniMegi, CD-RW, SunRize AD516, WB3.9
A1200: 2MB Chip, 64MB Fast, 4GBCF, GVP Typhoon 030 @40MHz w/FPU, Subway USB, EasyNet Ethernet, Indi AGA MKI, FastATA MK-IV, Internal Slim CD/DVD-RW, WB3.5
Surfing The Web With AMIGA Is Fun Again!