Oric Explorer is a .Net GUI application running on Windows, macOS and Linux for exploring collections of Oric media, primarily tape and floppy disk images of various formats. Features include viewing text and binary data, pictures, code with syntax highlighting pertaining to software designed for the different models of Oric 8-bit computers: Oric 1, Atmos, and Telestrat.
I have transferred my 3" Jasmin floppy With my Gotek drive with FF and HxC, I can open and use with Clock signal in HFE or converted to DSK with the HxC converter tool. But I can't open with OricExplorer.
Do you know this issue ?
Regards
I created a basic program (33 lines of code) as a text file in windows notepad and then used Oric Explorer V2.35 to import it as a ".tap" file. After this was completed, I loaded said tap file into Oricutron to test it. The program appeared to execute correctly in Oricutron and then returned to the curser in the default text mode as desired. However, when I then "listed" the program (to check/modify it further) the listing displayed extra lines of unexpected additional "random" characters at the end. If the program was modified using "EDIT" to remove the extra unwanted characters, the text editor/Oric would crash and needed a system RESET. As this is appears to be some sort of data corruption and very unusual, I manually typed the very same program directly into the Oricutron application and then into a real Oric. Both worked correctly without any errors whatsoever when the program was executed/re-listed or edited.
My feeling is that there is some sort of data corruption at the point where the basic program (as text) is imported from the text file and then translated into the tap file. My request is that this feature is checked/investigated further.
I have attached the original text file that I used, to hopefully help identify the issue. Circles.txt
The original ReadMe.md has instructions for running the software and configuring a development environment on Windows platforms.
It would be nice to add instructions to run the software in macOS and Linux with Mono, and how to set up a development environment based on MonoDevelop.
Ideally these new instructions should be added to the original ReadMe.md file.