exxos's Atari, Amiga & retro forum

HigashiJun wrote: 17 Feb 2025 08:44 @rubber_jonnie

Nice progress since the beginning of this journey.

Well done !

As promised, here are my settings for ADF disks:


1.JPG


2.JPG


Just tried to write Workbench32.adf and it went smooth as usual.

My GW is the last revision one (4.1) and the 3.5" FDD is a Y-E DATA 702D-6238D/D33253 (720 KB, 1.2 MB and 1.44 MB).

Hope this helps you.

;)

Yes, it's been an odd journey but getting there. I still have some instabilities with the A500 8MB/IDE not starting properly, I think it is socket related so I will swap that out soon too. Could be the PSU but voltages all seem good at power up so I don't really want to recap the PSU just yet.

Thanks, I'll take a look and see if I can make it work :)

I don't usually use FluxMyFluffyFloppy, but I did install it recently so these settings will help. I have an Greaseweazel F7 Lightning, the firmware was updated the last time I used it, so it's pretty recent. I have a selection of drives I can try with.

I'll let you know how I get on when I've had a chance to test.

I also decided last night that I was going to use the Boo Bip 27C400 emulator instead of a normal ROM. That way I can have 4 ROMs installed and switch between them with a keypress. Currently I have KS3.1, 2.0 and 1.3 installed as that seems to give good compatibility all round.

@rubber_jonnie

Good.

Let me know your results.

I do have and use GreaseweazleGUI too, but my preference goes to FMFF.

(I will check my A3000 network settings tomorrow).

HigashiJun wrote: 17 Feb 2025 09:55 @rubber_jonnie

Good.

Let me know your results.

I do have and use GreaseweazleGUI too, but my preference goes to FMFF.

(I will check my A3000 network settings tomorrow).

Thanks. I found AcornSSL and dropped it where its supposed to be, !FTPc now fails with a different error, I expect the module is the wrong one for 3.1, though I got it from the hard disk 4 image on ROOLS.

It's very odd that Sunfish/Moonfish both broke too but they may be easier to fix.

Finally got round to dropping FlashFloppy onto my New Gotek. Tested and working great on the Amiga, but I think I need to break out my 3D printer again as I've not used it in an age and I need to print an adapter for the A500.

The USB A to USB A is definitely the easiest method for flashing these days.

I may order another Gotek as it's about time I did the same for the A1200. Got an OLED display ordered for the new Gotek too.

Good progress!

JP2 allocates 1MB chip instead of 0.5MB Chip, so it also allocates the slow ram.
But then Agnus and Gary have to fight about that 0.5MB ram on the trapdoor expansion..,
that is why you use the disable jumper on the memory expansion to tell Gary he has lost the fight.

Kickstart 3.2.2 would probably be better for the workbench, but 3.1 will work fine.

I do not know if the IDE controller has the MaxTransfer bug that the A600/1200 has, probably not as it has a different setup..
(If you find that your HDD becomes corrupt then you can try to open up HDToolBox, then on the change file system page, you should see a string gadget containing the max transfer value. change it to 0x0001FE00)

Maximilian wrote: 17 Feb 2025 14:40 Good progress!

JP2 allocates 1MB chip instead of 0.5MB Chip, so it also allocates the slow ram.
But then Agnus and Gary have to fight about that 0.5MB ram on the trapdoor expansion..,
that is why you use the disable jumper on the memory expansion to tell Gary he has lost the fight.

Kickstart 3.2.2 would probably be better for the workbench, but 3.1 will work fine.

I do not know if the IDE controller has the MaxTransfer bug that the A600/1200 has, probably not as it has a different setup..
(If you find that your HDD becomes corrupt then you can try to open up HDToolBox, then on the change file system page, you should see a string gadget containing the max transfer value. change it to 0x0001FE00)

The Max Transfer setting is changed to that during the partitioning process so all good :)

For the record the max transfer restriction is not required for this controller. It was only necessary due to a bug in scsi.device for Gayle IDE controllers which this controller doesn't use

alexh wrote: 17 Feb 2025 17:43 For the record the max transfer restriction is not required for this controller. It was only necessary due to a bug in scsi.device for Gayle IDE controllers which this controller doesn't use

I wonder why the documents for prepping the drive say to set it then? Odd as these are from the git repository for this controller.

rubber_jonnie wrote: 17 Feb 2025 17:50 I wonder why the documents for prepping the drive say to set it then? Odd as these are from the git repository for this controller.

Reading https://github.com/jbilander/SF500 (same firmware) tells me that it should be set.
In any way, it should be safe to set and the performance hit should be small.

Maximilian wrote: 18 Feb 2025 03:36

rubber_jonnie wrote: 17 Feb 2025 17:50 I wonder why the documents for prepping the drive say to set it then? Odd as these are from the git repository for this controller.

Reading https://github.com/jbilander/SF500 (same firmware) tells me that it should be set.
In any way, it should be safe to set and the performance hit should be small.

Well that is how it's set, so we'll see how it goes. I have a couple of larger CF cards coming so hopefully one will work and I can try to get WHDLoad installed on both the A500 and the A1200, they've been in the dark too long :)