MicroPicoDrive Popopo's version

[Popopo]

Hi,

Use MDI by Martin Head, in an emulator to create QLAY MDV images, available from QL Homepage.

I supply MDI with the Q68 and use it myself.

Also works on NEXT QL Core, better than their attempts at the emulated MDV approach.

Thanks Derek
It looks interesting

[Derek_Stewart]

Hi,
New user guide for using MDTool (Dr.Gusman's version).

It shows how to import a ZIP and convert it into a MDV image
https://youtu.be/AZIg0KIsFko

Hi,

Excellent video and great development.

Will try it out on my MicroPicoDrive.

[Popopo]

Hi,

Excellent video and great development.

Will try it out on my MicroPicoDrive.

Thank you Derek,
I hope it will be useful for you. The MDTool has more functionalities, but I didn't have the time to dig deeper into them.

[Derek_Stewart]

Hi

in thecOqradrivd system, it has the ability to mount a zip file in a MDV slot, coukd this be done in the MicroPicoDrive?

[Popopo]

Hi

in thecOqradrivd system, it has the ability to mount a zip file in a MDV slot, coukd this be done in the MicroPicoDrive?

Maybe, it could if some memory available (and I think yes, but need to check zip libraries for rp2040)
But I prefer to focus on what left in my roadmap (bluetooth cartridge and sound emulator) before to attack that.

[Derek_Stewart]

Hi

I think you are correct, on reflection, I think the mounting a zip file as a MDV drive makes little sense. As most MDV files have a maximum of 100Kb.

Better to attach more storage via Qubide QLSD or QIMSI

[Popopo]

Better to attach more storage via Qubide QLSD or QIMSI

That is the next I want to try.
Already doing some studies and checking about a development board to implement mass storage system.

Just by now my priority one is easy thing for mass user type.
Then more complicated things for average users.

Sometimes we lose the grip thinking about things for average users, forgetting the most kind of people. People without enough acknowledge about platforms and so on, that want to get into the ecosystem.
To try, and if they enjoy it, go some steps ahead and continue learning and trying things on platforms.

That is why I document as easy as I am able to and give enough (more than enough) information in a way everyone could understand and use.
If only I understand the things I do, it is due I didn't do it enough good.

[Derek_Stewart]

Okay Dokey...

Not good for people who read the manuals.

[Popopo]

Okay Dokey...

Not good for people who read the manuals.

Not good for you. That's it.
Write the manuals by yourself. People like me that we don't know how to read or are too lazy to read are not worthy of your great comments.

[NormanDunbar]

Not good for you. That's it.
Write the manuals by yourself. People like me that we don't know how to read or are too lazy to read are not worthy of your great comments.

[Moderator hat on]
Calm down, that's enough bickering. There has been too much of that on the forum recently.

We all need to remember that the written word does not convey body language and/on intonation etc, so it is easy to be unintentionally wound up over something written, that wouldn't be a problem if spoken.

Derek's comment is one I was going to add myself. While you tube is sometimes good at explaining stuff, not everyone has access to fast nternet access. For example, me! A manual is easily downloaded and used, you tube doesn't let downloads happen unless you pay a premium monthly fee.

So, having your stuff only on you tube is why it's bad for people who read, or can only read, manuals. It also, during a recent thread on the MDV sound board, why I never followed up your you tube videos! I couldn't, my Internet access is total crap. I'm currently on mobile broadband I an area with crap coverage. If I'm lucky, I get 0.5 megabits download.

So, Derek's comment was perfectly valid, your response was not acceptable. Let's all keep a calm head here, otherwise the ban hammer might be brought out of its packaging!

[Moderatorhat off]

Cheers,
Norm.