MicroPicoDrive Popopo's version

[Popopo]

Thank you all,
All that info are very needed it

[Popopo]

New video.
First one of 2 audiovisual User Guide's

https://youtu.be/wyJjXfhqH4E

This part explain very basic concepts but that some users were asking about. One related with the last messages in this post (MDVs images versions and reasons of it).
Also explain how to program it (not so clear for people with +70 yo), and how to browse with new firmwares for it, prepare the microSD...etc.

Cheers

[Pr0f]

So confirming the workaround of adding a directory to list of files in a directory will allow the menu select logic to 'wrap around' and not hang.

Also - Dr Gusmans tool - if you create a small text file using any text editor, you can use the tool to create a Microdrive image - by adding your text file, then saving the result as an mdv image. This image works in Qemulator and allows programs to be added to the microdrive image from say a win image file. This means qdos information about the executable files remains intact. This also has the side affect of having populated the dataspace setting when the image is viewed again in the tool - result.

I will test the images this morning and confirm this has worked, but if it has worked - this is a big step forward for usability for this device.

Confirming - the PSION packages are now all working - so the above process seems to have resolved that issue.

[Martin_Head]

if that info is "only" in the doc of that emulator,
Does it mean that doesn't affect to others emulations or devices? (ie: vDrive, Oqtadrive, etc).

In addition to tofro's reply, QPC2 also supports the Qemulator executable file headers

[Popopo]

So confirming the workaround of adding a directory to list of files in a directory will allow the menu select logic to 'wrap around' and not hang.

Also - Dr Gusmans tool - if you create a small text file using any text editor, you can use the tool to create a Microdrive image - by adding your text file, then saving the result as an mdv image. This image works in Qemulator and allows programs to be added to the microdrive image from say a win image file. This means qdos information about the executable files remains intact. This also has the side affect of having populated the dataspace setting when the image is viewed again in the tool - result.

I will test the images this morning and confirm this has worked, but if it has worked - this is a big step forward for usability for this device.

Confirming - the PSION packages are now all working - so the above process seems to have resolved that issue.

You are awesome!!!
Thank for sharing it!
In addition to it, I have prepared a MDV image formatted in my repo. Its name is newcart.mdv.
Of course, after reading more detailed info that MDVs can vary its size (sectors) depending on the taste of who prepare it... it is not an universal solution. But for regular users that only want an standard MDV image to store, copy and so on, will make much easier its use.
I think... that for that matter Dr. Gusman created the MDP format, that solve all those problems that MDV has for "legacy" matter. I must read again the docs

In addition to tofro's reply, QPC2 also supports the Qemulator executable file headers

QPC2? what does it mean?
The MicroPicoDrive works with Qemulators files too, but sometimes. Now thanks to all your explanation I start to understand the roots of the problem.
I will try to document it for everyone and to make a tool (in Java) to manipulate those kind of things, or make it easy to do (similar than Dr. Gusman has done but multi-platform).

Thank you Martin

[Andrew]

QPC2? what does it mean?

https://www.kilgus.net/qpc/

[Derek_Stewart]

Hi

SMSQmulator also supports the Qemulator Header and the XTcc trailer.

Also look at sQLux that also supports all this header and trailer.

[Derek_Stewart]

Hi

Does the new version of the MicroPicoDrive still work with the original Cartridges by Dr Gusmans?

[Popopo]

Does the new version of the MicroPicoDrive still work with the original Cartridges by Dr Gusmans?

Hi Derek,
Good question, the answer is...
Yes,
Every version from my branch 1.4x works with the original project.
At any time you want to get the original behavior and system, just change the firmware.

Even the Bluetooth version that I am going to develop will work with the original one

[Derek_Stewart]

Does the new version of the MicroPicoDrive still work with the original Cartridges by Dr Gusmans?

Hi Derek,
Good question, the answer is...
Yes,
Every version from my branch 1.4x works with the original project.
At any time you want to get the original behavior and system, just change the firmware.

Even the Bluetooth version that I am going to develop will work with the original one

great, compatibility is an excellent feature.

Is the Bluetooth, updating the cartridge or can the QL access the Bluetooth interface?