bravogaq.blogg.se

Improving amiga os 3.9
Improving amiga os 3.9









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.

improving amiga os 3.9

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.

improving amiga os 3.9

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. 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).

improving amiga os 3.9

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.











    Improving amiga os 3.9