Deployment: Are you using the hosted EaaSI service, or a local node?
EaaSI Version: This corresponds to the release branch/installer version used to deploy your instance. This information should be available in the Manage Node menu, if accessible
Browser: The name and version of the browser you are using to access the EaaSI UI, if applicable
Description: Please describe your issue in as much detail as possible, including name + ID of any relevant environments, software or content. You can also attach screenshots or relevant error report files.
I have imported a number of disk images from CHM’s software collection. Some are .iso files, others are .img files. No matter what they are, when I try to use them with various Mac OS base images, they always appear as .iso files or .img files in the virtual CD-ROM drive, rather than mounting as disks in the floppy or CD-ROM drives. This happened with System 7.01 (IIci) in Basilisk, System 7.5 in Basilisk, and Mac OS 8.5 in Sheepsaver and Mac OS 9 in Sheepsaver.
The only except was a .iso of Myth II Soulblighter, which Mac OS 8.5 correctly identified as a disk and tried to mount, but not Mac OS 9.
However Mac OS 8.5 could not recognize the file system on the disk (which it should have as it’s a Mac game, unless this was the Windows version. I think it’s actually a hybrid CD-ROM, so perhaps it correctly recognized the Windows half of the disk but not the Mac half?). It asked to initialize the disk, which it can’t because the image is read only, and it will keep asking this until the virtual disk is ejected.
I am also having similar issues with my imported Windows disks also showing up as raw .iso files in Windows 95 base environments.
I even tried to import some images as Content instead, but with the same results.
Perhaps this could be an issue with the disk images themselves? Are these images not compatible with EaaSI or with these emulators? What needs to be done to the images to make them work?
Are you able to reproduce the issue or did it happen once? What steps can you take to repeat the issue? What did you expect to occur and what was the actual outcome?
Happens with almost all the disk images I’ve imported, all the time.
These disks should mount as disks in the OS.
Urgency: If possible, please give an indication of how urgently the issue needs to be addressed - is there a timeline or deadline (e.g. upcoming demo, researcher request, etc.) that EaaSI support staff should be aware of?
Not really urgent, but definitely a blocking issue.