Here are the steps I took to be able to browse using the new WiFiPi wireless network driver, and Miami DX.

Version 0.1: First version to document my experiences - still finding and fixing typos

Downloads:
Emu68Tools from 23 April: https://github.com/michalsc/Emu68-tools/releases/download/nightly/Emu68-tools-20240423-75ea45.zip
Emu68 release 1: https://github.com/michalsc/Emu68/releases
Prism2v2: https://aminet.net/driver/net/prism2v2.lha
MiamiDX (demo): https://aminet.net/comm/tcp/MiamiDx10cmain.lha and https://aminet.net/comm/tcp/MiamiDx10c-MUI.lha (I already had this up and running with a 3COM PCMCIA card)

The info for where to copy the files is based on Michal Schultz's post: https://www.patreon.com/posts/wi-fi-alpha-102261532

Set up the Wireless network driver
1: Unpack Emu68 tools
2: Copy file Emu68-WiFi/Devs/Networks/wifipi.device to DEVS:Networks
3: Copy the whole folder emu68/WiFi/Devs/Networks/Firmware to Devs: (so you end up with Devs:Firmware containing a series of txt, bin and clm_blob files) NOTE: I didn't have the Devs:Firmware folder to start with but some of you might)
4: Unpack Prism2v2.lha you can choose to run the installer or copy some files manually

IF MANUAL
5: Copy Wirelsssmanager to C:
6: Create a text file in Envarc:sys/ called wireless.prefs
7: Add the lines
network={
     ssid="<name of your wireless network>"
     psk="<your network passphrase>"
}
8: Save the file
9: Reboot

IF USING THE INSTALLER:
5: Use expert mode
6: Choose 'No' when asked to install firmware for the Hermes chipset
7: Choose 'Yes' to set wireless preferences
8: Enter you wireless network name and password when prompted
9a: Choose whether or not to start WirelessManager automatically (it's up to you - see 'Observations' at the end)
9b: Finish the install and reboot

What's the difference between the two?
The process using the installer creates an encrypted version of the wireless password and uses that instead of the open text version. Handy if you don't want your password saved in plain text on your Amiga.
My personal experience is that I couldn't connect after setting up the wireless.prefs file manually, I would just get a timeout. Users Lemaru and Shaytam on the PiStorm discord assured me it should work without the encrypted PSK, so I uncommented the plain text line and commented out the encrypted line, rebooted and it then worked. The timeout was probably not related to the setup method I used (I have an old house with thick brick internal walls and Wifi can sometimes drop).

STARTING THE NETWORK
10: If you chose to use the installer and start automatically, and all being well, the wifipi.device should have been initialised on reboot.
11: If you have chosen the manual route open up a Shell and enter 'Wirelessmanager wifipi.device' - after a few seconds you hopefully get confirmation that you are associated with a MAC address, key negotiation is completed and CTRL-EVENT-Connected ie you're connected to the access point.

Configuring MiamiDX (Note I already use MiamiDX with a PCMCIA card and copied the original settings)
12: If not already done, install MiamiDX
13: Run and open up Hardware > New
14: Give it a name e.g. WiFiPi
15: Type of driver should default to SANA-II driver (if not change it to that)
16: In Driver enter DEVS:Networks/wifipi.device
17: Open SANA-II parameters
18: Choose 'Query Device' - the settings should auto-complete.
19: Choose OK to close the SANA-II parameters screen and again to close the Hardware Definition Screen
20: Choose Interfaces from the MiamiDX menu
21: Choose 'New'
22: My settings are:
 - Name: eth1
 - Alias: WiFiPi
 - Type: Ethernet
 - Hardware: (whatever you called the interface in step 14)
 - Priority: 10
 - IP type: Static
 - IP Address: something relevant to my network
 - Netmask Type: Static
 - Netmask: 255.255.255.0 (pretty common)
 - Gateway Type: static
 - Gateway: ip address of my router
 - Multicasts: disabled
 - Multicast pri: 0
 - Control panel: ticked
 - GUI default: unticked
 I don't have any Auto-connect/disconnect settings or Manual routes/aliases
TCP/IP settings:
 - Use ICMP: ticked
 - Fake IP: unticked
 - Get dynamic hostame, priority: 0
 - Get dynamic DNS servers: Ignore
 - Preferred offline state: Suspended
 - Get time: unticked
 - DHCP Enable: Ticked
 - Send hostname in request: Ticked
 - Host Name: Something you want to identify your Amiga on if looking in your router interface
23: OK to close the Interface TCP/IP Settings Window and again to close the Interface Definition Window
24: Right-click and choose 'Save' from the Settings menu

Now to test:
25: In MiamiDX, and the Interfaces section, select your newly created Interface and select 'Online'

Observations:
I Use Tinymeter and as soon as I run wirelessmanager the CPU drops to around 30%-33% free, so I'm going to continue to run this manually for now, only when I want to go online.
If you make any changes to the wireless.prefs file reboot for them to take effect.

Before making this video, please watch (this section) as you'll get an idea of the issue....

Amiga 4000: Is the Fastlane Z3 the best home for a BlueSCSIv2 Upgrade?

When I filmed that, I had to post process it A LOT to increase its brightness to acceptable levels for this video. I had assumed that the issue was to do with the RGB to SCART cable (unlikely) or that my trusty SAMSUNG LED with SCART was on its way out (more likely).

However, today, I tested this by plugging in my A500, and the video looks bright and clear, as I remember it. So, A4000 has a problem  .

Calling on the ancient wisdom of the Amiga collective. Would anyone know what this is a symptom of?

My guess, if I were someone else, would be that capacitors were going down the swaney, and providing too low voltage. However, I had this machine re-capped just last year. So its very unlikely this is the issue. However, the recap was because of some leakage in the video area, however, I was lucky in that it seemed to be early days. I have cleaned that area, so Im surprised if its on-going corrosion.

Anyway, over to you guys. Wondering if Christ Edwards lurks here, as I would assume he might recognise the issue...

Thanks for confirming and the updates on your progress. From your other replies you've clearly got much more electronics knowledge than me, so just a few more questions for clarification, to try and help diagnosis.

At the end of your original post you wrote  this happens even with the floppy unplugged, so is the Panasonic drive your floppy drive or your hard drive?

You wrote that you tried without accelerator, have you also tested with just floppy drive and no hard drive, no accelerator?

What are the ratings of the power supplies you've used? Are they all official Amiga PSUs or do you have something more powerful? (I was recently given 5 PSUs and the specified outputs vary, even for units with the same part number.)

About half a year ago I started repairing a badly battery damaged A2000 which had some memory issues. After a looong time of letting the project settle I finally got somewhere in the repair. The problem was a almost rotted trace for _UDS, just outside the area which I cleaned. It was still good enough to sometimes work but bad enough to not do so reliably. Also broken was the Even CIA and probably some ram chips (I just replaced all because I started being frustrated lol). I Fixed those issues and now Diagrom boots up without any memory errors and the memory test and the CIA tests succeed.

Now however I'm faced with another Problem:
Although diagrom boots I can only use it with the serial terminal. Nothing is ever displayed on the screen except for some flashing green bars at startup and then some random colors as the rom is "forcing stuff to run in fastmem if avaible".
Running any graphic tests also yields nothing but a slightly differently color-filled screen, except in "test raster" where I get some purple-green lines across the screen. I've verified that the color value output from Denise is actually what the display shows (so eliminated the Vidiot as a possible fault) and tested the monitor with my working a500.

And another issue I noticed is that the audio tests are non functional. They do play a tone but it is interrupted (sounds just like morse code). No idea if the two faults are related though.

I'm once again out of ideas for what to try as I've swapped around All chips between another A500 and the A2000 and none make any kind of a difference. Has anybody maybe seen this issue before?

Hi,

Simple answer is “Yes”, have had this even on a Rev 1D1 mainboard. The answer maybe that the top RF shielding is needed. Or the drive motor has become too noisy on the drive.
Is the drive by chance a Panasonic one?

Actually yes it is a newer panasonic drive.  This is an Escom Amiga made in France.  I've suspected it could actually be the floppy drive drawing too much current on motor start.  Its not a shielding problem, its the 5V rail dipping and the monitor loses sync, I can see it on my scope.  It happens even with all shielding installed.  I've tried different power supplies so its not the supply.  I've tried a different video cable.  This is a bare bones mainboard no accelerator.