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
UI Build: cb82b3d4b399d1ff155748bf4c0d743a062cd655
on Windows 10
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.
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?
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?
I downloaded and followed the instructions to install EaaSI_Demo_Lite on Windows 10. This seemed successful, and I have the familiar Legacy Interface.
Following the Special Considerations for Mac/Apple Environments, I then tried to install MacOS9 using the Generic Sheepshaver Template.
I used my own newworld86.rom image, and a MacOS9.raw image in the Import Environment workflow.
The gears spin, and then complete. But instead of a working emulator, I get a page that reads something like “The Emulator has stopped.”
Any tips for more success?