Hello @tim.mifsud! There are a number of different questions to troubleshoot here, but I’m sure we can collectively help. It would probably be helpful to consider each media type separately - 3.5 floppy, CD-ROM/ISO, and Zip. And with each, it is indeed best to confirm, if we can, that the imaging process was complete and successful before getting into the EaaS import and mounting process, so that we are confident the issue is somewhere in EaaS or the environment configuration and not the disk images themselves.
First the CD-ROMs - have you tried to make ISO files from them with all three of the imaging programs mentioned? Most emulators do not support, for example, BIN/CUE files or E01 files or most of the other formats that those imaging programs sometimes offer for optical media. Sometimes a raw (BIN) file can work just by changing/renaming the extension to “.iso”. If you have been making ISOs already - do they mount correctly on their own in Windows 10?
Just in terms of other options, in addition to the programs you mention, I know many people have had success with IsoBuster for imaging optical media. So perhaps it is also worth a shot. And I highly recommend @aschweik’s report for NYU a few years back for a thorough rundown on all the different types and layouts of optical media out there and possible problems with imaging, e.g. multi-session or Audio CDs. I don’t know if it will be relevant here, but I’ve always found it a very useful resource for potential oddities.
For floppies, I’ll quickly plug the FluxEngine project, which is a much cheaper and more open alternative to the Kryoflux. However that still involves finding the legacy hardware (and the need to convert raw flux data into disk images that can actually be used in emulation, which is a whole other side of things), so that’s just an aside - a USB 3.5" floppy drive should in theory be fine to get that data. But the formatting of the floppy might make a difference? Do you know if these floppies were originally intended for Windows or Mac machines? Can they just mount directly in Windows 10 via the USB floppy drive? What type of image and settings are you using in WinImage or FTK Imager to try to capture them?
Zips are also interesting, I have never worked with them directly so I am actually not sure whether in emulation they can be treated as “Floppies” or if they have to be treated more like a generic block storage device, like a hard drive or thumb drive. That would affect how to properly import and mount them in EaaS. I’ll follow up on that point but I hope/wonder if anyone else in this forum may have more direct experience with imaging Zips. And again, exactly which program and settings have you been trying to make images from them?
Lastly, in general I am unfortunately most familiar with Linux imaging programs that can be used to create raw disk images for block storage devices like floppies, disk drives, thumb drives (and I assume, Zip): dd, ddrescue, Guymager. (There’s also @johanvanderknijff’s diskimgr program that creates a simple interface for the command-line programs dd and ddrescue, which I find very handy) However I am not sure whether any of these can be run directly in Windows 10 using, for instance, the Windows Subsystem for Linux. There may very well just be Windows ports or versions of those programs that would be helpful here. I’ll investigate this as well. (@ecochrane works more in Windows than I do - perhaps he has ideas)