-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ZX Spectrum Opus Discovery disk config #330
Comments
Names maybe would be better as |
I know there is Opus1 and Opus2 hardware, we can expect it to work alike. zx.opus.sd and zx.opus.dd sound great. |
Hi. Does this work yet please, or does it need code changes to be implemented? Thanks. |
You only need the profile in your diskdefs.cfg |
Thanks. That's sorted it. I tried to add an opd.py file as well, but it didn't pick that up. |
@mitchelln , it now works for you? I think the diskdefs on linux is src/greaseweazle/data/diskdefs.cfg I editted the initial comment to be more readable. |
How do I use this without an opd.py file? gw.exe complains that it doesn't recognise the OPD input file I am trying to write to a physical disk. I added the config entries to diskdefs.cfg and the -h option reports zx.opus.ss and zx.opus.dd among the supported formats now. |
Rename *.opd file to *.img and try again. |
That worked and using the single sided format, delivers something on to disk that gives a readable directory entry on Opus but it doesn't lead to a loadable program (Wrong File Type error). Are the gaps certain to be correct for a stock Opus with a single-sided single density drive? When I copy the OPD file content from my GoTek secondary drive to my stock primary drive to the same physical disk in Opus itself, it does work. |
Gaps don't really need to be specified. Try removing them all from your diskdefs. |
Also interleave should be 13 and cskew should be 13 also. So be sure to fix interleave and specify cskew. And then see how you get on. |
If that doesn't work, only then additionally try gap3=12 |
still no, including with interleave = 13 and cskew =13. The Disk index "CAT 1's" on Opus / ZX Spectrum, but no files load. "m Wrong file type, 0:1" |
Opus 2 is simply an Opus Discovery 1 with the 2nd drive slot populated. |
I don't know then I'm afraid. I assume the OPD is known good? It sounds more like a filesystem error than a sector/track level issue. |
Yeah, all the OPD I'm using are the original 180K format and mount + load fine in an actual Opus via the GoTek, including copying them to physical disk (in the ZX Spectrum / Opus) and then running from the physical disk. Only factor I haven't been able to exclude yet is the floppy drive I'm using for the Greaseweazle based imaging. It runs pretty much error-free on the greaseweazle but that's still a drive verifying it's own sectors - if it's out of whack a bit it's not going to produce something the Opus can read. Many thanks for the help with the attempts so far! |
The reason I played with the gaps was to keep it within the maximum tracksize. Are you using a 40 track drive or a 80 track with double steps? You can try to create a scp and look at it with hxc-> track analyzer. I used this to write: If you like I can try to reproduce it on my side. |
Greaseweazle will automatically mess with all gaps (except gap2) to fit sectors in. Of course if you do know the correct gap values from a real disk, that is best of all. |
Trying to use an 80-track drive. |
Success!! Command: Config file in use (relevant section): disk zx.opus.dd |
Using same command options and the settings from gnulnulf's original post at the top of this thread in diskdefs.cfg, and using a different OPD image, I made another succesfully readable opus phsyical disk (used blank media to start, so not an accidental residue from an earlier attempt). |
Update: one one of the disks I imaged with gnulnulf's settngs, some games loaded and others (higher numbered tracks) did not. I now imaged it again using the settings recommended by Keirf without the gap3=12 and that rewritten disk (from same image) now works fine for all programs on the image. `disk zx.opus.ss disk zx.opus.dd |
The img file is normally called "OPD".
The single sided drive: 40T/18S(0-17)/256ss -> 180k
The double sided drive: 80T/18S(0-17)/256ss -> 720k
I'm not sure if I got the gaps right.
Main difference from other formats is the usage of sector 0.
My addition to the diskdefs.cfg config is:
The text was updated successfully, but these errors were encountered: