[offer] Wordstar 3.01 for CP/M (5.25, SCP)
Unfortunately the disk has bad sectors and I don't know if this impacts the files as I don't have a CP/M system to test it.
I included a scan of the manual.
https://mega.nz/file/eHAmBbCY#E0VkXCktoePDDakmmqAxqaTcGOqatC1gTL1g_u3OU6E
I included a scan of the manual.
https://mega.nz/file/eHAmBbCY#E0VkXCktoePDDakmmqAxqaTcGOqatC1gTL1g_u3OU6E
Comments
Unfortunately I don't know about CP/M.
What is the physical condition of the disk? Scratched? Warped? Dirty? Visibly perfect? Did you clean it before reading it?
At least looking at the multiple dumps, it did not seem to get worse.
callmejack, is there anything at all with this that indicates what manufacturer's system this is intended for? (I know, often they don't label it)
https://mega.nz/file/zPJDjAAb#CIqRxqy3rT7FjDrbt8Pg4589nGsTqr2z0qB7YcCjFSc
I tried to read it with 22disk but with no success (tried all 98 tracks formats)
Looking through the data, I don't see any clue what system it is for.
diskdef ws300 seclen 256 tracks 160 sectrk 16 blocksize 2048 maxdir 128 boottrk 3 skew 1 os 2.2 end
Just for my knowledge, how did you manage to find those parameters?
Thanks for information of it.
Yes, there is no bad track.
Educated guesses. The seclen, tracks and sectrk parameters are determined by the disk geometry. In the raw image it is easy to find the start and end of the directory, which gives us boottrk and maxdir. The directory also tells us how many blocks are allocated to each file, allowing a guess at blocksize (trial and error would work, too). The sector skew is almost always 1 for 5.25" disks.
Just searching by those parameters, I don't see anything known out there that matches exactly. Could have been something totally custom.
It could well be that this version is generic and runs on many systems.
Back then it was fairly common, and often required, for users to go directly to their local vendor, who would have a machine that would copy between formats. So if a title was not released specifically for a specific system model or implementation, the vendor would just convert the format. I'm thinking that is likely what happened here.