-
Notifications
You must be signed in to change notification settings - Fork 28
ZX Spectrum Emulator not working #229
Comments
If you have installed from nuget package that version is obsolete, try to install the latest package from the releases section. |
Thanks @gusmanb for your reply. I have installed SpectNetIDE 2.0 (Preview 9) directly from Visual Studio by selecting the Extensions → Manage Extensions menu command and then clicking the online tab and typing “SpectNetIDE” in the search box. Is the software installed from there handled via the NuGet package manager? |
Hmmm, strange. Is the .rom file in the "Rom" folder of the project? Also, do you see any message in the SpectNetiDE Output pane? |
The rom file is in the rom folder. And I even tried with the 128K and +3 and the behaviour is always the same. I don't find the SpectNetiDE Output pane. Where is it located? |
I am experiencing a quite puzzling issue. I am on a Windows 10 Pro computer, having installed the Microsoft Visual Studio Community edition 2019 (version 16.11.8), from scratch, just for installing SpectNet IDE. I followed the instructions here https://dotneteer.github.io/spectnetide/getting-started/install-spectnetide-2 and I confirm that I selected for installation also the .Net desktop development. Finally I installed the SpectNet IDE itself following the same instructions. And everything seemed OK.
But it failed in the first tutorial "Tutorials v2 - Create a ZX Spectrum 48K Project". There, running the command ZX Spectrum IDE|ZX Spectrum Emulator, the emulator tool window has showed up. And then when I press 'play' in the emulator, the Spectrum ROM is not loaded, which means that I do not get the "© 1982 Sinclair Research Ltd" message nor can access to the BASIC. This means I cannot issue any BASIC command to it. I tried also invoking the emulator by right-clicking the mouse button on a .bas program and the same behaviour happens - the emulator window opens but it does not run the BASIC file. Can you help me to solve this issue?
The text was updated successfully, but these errors were encountered: