wikiteam VS diskimageprocessor

WikiTeam is working on the archival, with the usual XML dumps and image dumps. You can follow updates and see how to help:

https://github.com/WikiTeam/wikiteam/issues/465#issuecomment...

https://wiki.archiveteam.org/index.php/Miraheze

Already before the announcement we had XML dumps for thousands of Miraheze wikis.

The thread linked has the information you need. Read me on the Github page for WikiTeam's dump generator.

ArchiveTeam WikiTeam has download tooling: https://github.com/WikiTeam/wikiteam

Hi all - I'm trying to archive a number of fandom pages. Upon checking out this subreddit, I've found a few ways of doing so, and am currently working with the WikiTeam python tool (https://github.com/WikiTeam/wikiteam)

Httrack is a good choice for having a local copy of the wiki you can browse personally, but note that if you ever have to back up a wiki in a formal suitable for migrating to another wiki site, something like ArchiveTeam's WikiTeam tool would be suitable. It also has a built-in tool to upload the resulting backup to archive.org, like how someone has done so with the MGQ wiki here.

I found ArchiveTeam's WikiTeam tool relatively easy to use. I just had to download the repository from github (from the Code: Download Zip in the top right), have Python installed, open a command prompt in the folder, copy-paste the commands from their front page, have it fail complaining about missing modules, look up the command to install Python modules, and install the modules it needs. Their tutorial has additional instructions for uploading the resulting archives to archive.org and for downloading lists of wikis.

If anyone has used this app please help me. I have followed the instruction in the readme.txt https://github.com/WikiTeam/wikiteam and I have the dumpgenerator.py but, when I run it with this commands:

Next, I web-searched for EO1. This appears to be a block-device image, also seems like it's mostly used in MS Windows world. I found this Python repository: https://github.com/CCA-Public/diskimageprocessor for dealing with images of that sort. See if it does you any good. But, like I wrote earlier, this is a block-device image format. So, there may not be any files there. In addition, this means that it doesn't contain any file-system implementation (you would have to provide your own to read the file-system data). By this I mean: since this is MS Windows, you could have NTFS or FAT or some other less known MS Windows-compatible file-system, and you would have to figure out which one it is and read the contents accordingly.