Not only does it lower by a little bit the CPU usage, it significantly increases the transfer rate and the overall system feels faster. OK, on to the results! As you can see enabling TLSFMem under AmigaOS 3.9 makes a huge difference. If you don’t know what TLSFMem is you can find information about it on Chris Hodges’ site here. TLSFMem is designed for AmigaOS 3.x only. In addition, two tests were performed on each ethernet card with TLSFMem enabled.
#Amiga os 3.9 usb 3 install#
Stock AmigaOS 4.1 Classic install using DHCP.ĪmigaOS 3.9 BB4 with MAPROM feature of Cyberstorm PPC enabled. The included Genesis command line ftp client was very slow for some reason under AmigaOS 3.9.ĪmigaOS 3.9 is using Genesis 68020 version In AmigaOS 3.9 the AmiFTP client was fastest. Under AmigaOS 4.1 it was the included command line ftp program. I used the fastest client I could for each test. There was a normally a higher “peak” transfer rate, but since that was not sustained, I recorded the more realistic number at the end of the transfer.
![amiga os 3.9 usb 3 amiga os 3.9 usb 3](https://cdn.substack.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F0a9e1907-d7d0-4c16-9e45-564389a9fcb0_1280x720.png)
The transfer rate at the end of the transfer was recorded for each test. Three different files were used – a 10MB file, a 40MB file, and a 102MB file. Sapphire Radeon 9250 256MB PCI graphics cardĭual Boot AmigaOS 3.9 and AmigaOS 4.1 Classic Installedįor each test a large file was ftp’ed from a local ftp server into the Amiga 4000T’s RAM disk. Realtek 8139 based PCI network card 100Mbit Realtek 8029 based PCI network card 10Mbit Phase 5 Cyberstorm PPC with 233MHz 604e and 50MHz 68060ĭeneb Zorro III USB Controller – PIO mode in AmigaOS 4.1, DMA mode in AmigaOS 3.9ĭ-Link DUB-E100 100Mbit USB Ethernet Adapter Mdbenson what is you status with your Rev F today and have you tried with OS3.I did some testing on the available Ethernet adapters for AmigaOS 4.1 and compared them against AmigaOS 3.9. Should it work as DF1: with real floppy drive being before the cable twist and HxC after the cable twist.Ģ) If I leave ID1B OFF, ID2B OFF, ID3B OFF is HxC set as one drive only?ģ) If I want to use it as DF1: should I set ID1A OFF, ID2A OFF, ID3A OFF and ID1B ON instead?Ĥ) If I want to use it inside external floppy drive case should I set is as ID2A ON and ID3B ON assuming those would mean DF2: and DF3:ĥ) Amiga 2000/30 models can understand a maximum of 2 internal floppy drives (DF0: and DF1:), so is setting HxC inside external floppy case and use it as DF2: and DF3: the only option to use real floppy drives DF0: and DF1: with them? So now I have a bunch of questions:ġ) If I set ID1A ON and ID0B OFF, ID1B OFF, ID2B OFF, ID3B OFF. I tried to put real floppy drive as DF0: and HxC Floppy Drive Emulator Rev F as DF1: but it shows "DF1:?" when I try to a Workbench disk. I have not tried with installed OS3.1, OS3.9 or OS4.1 Classic yet so I could comment troubles of mdbenson and before I even try, I would like to hear you (both) comment if it is possible to use HxC Floppy Drive Emulator Rev F with real floppy drive connected to the same cable? It reads Workbench 1.3, 2.0 or 3.1 disk with no problems and once loaded, finds any of those as second disk (DF1:) with default DIP settings of ID0A and ID1B. I have Amiga 4000 and HxC Floppy Drive Emulator Rev F with firmware v 1.8.2.40.
![amiga os 3.9 usb 3 amiga os 3.9 usb 3](http://www.haage-partner.de/amiga/aos39/graphics/aos39_screen_2.jpg)
If you want I can try it in my A1200 at the weekend? Again, I have not tested with anything other than a Amiga 4000 so I can't say if it's a problem with Amigas, or even just the AGA chipset. It seems to be getting 'out of step' somehow and failing to access different tracks correctly, but in nearly all cases (except formatting and mounting disks) the errors are recoverable and a 'Retry' and it carries on.
![amiga os 3.9 usb 3 amiga os 3.9 usb 3](https://albums-music.uk/images/3/9/los-bribones-amiga--vivir-sin-ti.jpg)
Even when successfully reading it makes sounds like it is struggling to access some blocks, head-scrubbing across the 'disk' and then carrying on reading.Booting from the valid WB3.1 disk had a read error at block 239 or there about, on a second attempt at block 1694 (076/080 S:0), a third time at block 1565 (070/080 S:0).First at 16%, cylinder 12, then the second time at 37%, third time at 28%. Formatting an unreadable 'Empty' HFE file via Workbench has lead to it failing.It will not mount one of the 'empty' disk images.It still will not mount a valid, bootable Workbench 3.1 disk.I don't know if it's JUST on Amiga 4000 or if it happens on other computers too. I re-flashed 1.7.2.0 to the HxC, then re-flashed 1.6.0.0 and confirmed that it definitely is the 1.6.0.0 firmware that causes the weird screen issue. I have looked at this again this evening to just confirm my work.