ql vdrive in EU ?

[Popopo]

maybe a MicroPicoDrive, with a Pico-W, and have wifi conductivity.

Or am I dreaming...

Pico W, right now... is not a next future and to use it, need to add that feature to the core (firmware).
I don't know if someone is going to do it, but not me.

Instead of it. Next after sound module... I'll going to add wireless comms (file transfer) but will be ... a cartridge avoiding expensive solutions and keeping the invest done in a nowadays driver (main unit).
That way, everyone who may need a wireless use of the MDP, could mount/pay the add-on, and who doesn't, save time & money. That is my next milestone (after sound).

In other words... a new cartridge compatible with the driver unit, to load images from your phone or computer directly. No screen, no buttons, no mSD. Just a tiny cartridge.

[Popopo]

To get an overview of the available solutions for Microdrive emulation (for QL & Spectrum), this feature comparison may be of help.

Very nice comparative.
There are some solutions that I didn't know!!! Thank you.

Thanks for the link and to the author for it.

Table General: What does mean combined with H/W drives?

[xelalex]

Table General: What does mean combined with H/W drives?

This means whether a solution can be installed & work together with real Microdrive units.

[Popopo]

Table General: What does mean combined with H/W drives?

This means whether a solution can be installed & work together with real Microdrive units.

Ah nice.
MicroPicoDrive can.

[xelalex]

MicroPicoDrive can.

So for example when installing the main MicroPicoDrive PCB in slot 1, and putting a real Microdrive in slot 2, MPD would be mdv1 and the real drive mdv2, and they could both be fully used without conflicts? I guess this assignment would then be fixed and could not be changed via software, right? I'll edit the feature comparison after your confirmation.

[Popopo]

MicroPicoDrive can.

So for example when installing the main MicroPicoDrive PCB in slot 1, and putting a real Microdrive in slot 2, MPD would be mdv1 and the real drive mdv2, and they could both be fully used without conflicts? I guess this assignment would then be fixed and could not be changed via software, right? I'll edit the feature comparison after your confirmation.

QL system is a daisy chain. So that would not affect unless very weird circumstances.
In fact, that way is how many users use the MDPs, MDP in first place, and a MDV (original) in second place.
The inverse is not possible due to the shape of the board (As I have shown in installation and overview videos).

It has not conflicts till I have detected (I have not working MDV to full test), and users have told me beyond some issues about motor (most part of the times due to ULAs and not about MDPs).
At any case, as you have said, it is easily solved by software (because of course, there could be a bug that I didn't detect or the author).

I would love to make a full test bud again, sadly I have not real working MDVs.

[Derek_Stewart]

Hi

I would use a MDV emulator like Oqtadrive and a QL-SD, which would work with QIMSI.