| Could Robot Odyssey be coaxed into a ProDOS port? [message #378036] |
Tue, 11 December 2018 15:59  |
Steve Nickolas
Messages: 2036
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
I don't think there's a chance of porting Robot Odyssey to ProDOS and
keeping it on 5.25" disks, but that's not what I've got in mind. See...I
want to have it hard drive installable. ;)
If it might be possible to identify some sort of pseudo filesystem or
something, I suppose a ProDOS port might be easier, but I foresee much
bankswitching because it's 64K...
-uso.
|
|
|
|
| Re: Could Robot Odyssey be coaxed into a ProDOS port? [message #378071 is a reply to message #378036] |
Tue, 11 December 2018 23:31  |
qkumba
Messages: 1584
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
2.0 is three sides large. It's not a good candidate to remain on floppies.
I agree that a hard disk installable version would be good.
It uses the ProDOS floppy driver, complete with $4x parameters.
You could always use ProRWTS in RWTS mode, which can support concatenated whole-disk images, if you can find a way to distinguish between the disks.
Then ProDOS is just the bootstrapper.
|
|
|
|
| Re: Could Robot Odyssey be coaxed into a ProDOS port? [message #378072 is a reply to message #378071] |
Wed, 12 December 2018 00:03 |
Steve Nickolas
Messages: 2036
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On Tue, 11 Dec 2018, qkumba wrote:
> 2.0 is three sides large. It's not a good candidate to remain on floppies.
> I agree that a hard disk installable version would be good.
> It uses the ProDOS floppy driver, complete with $4x parameters.
> You could always use ProRWTS in RWTS mode, which can support concatenated whole-disk images, if you can find a way to distinguish between the disks.
> Then ProDOS is just the bootstrapper.
>
1.x which I grew up on is 2 sides - but you have the same problem, how to
tell A from B?
-uso.
|
|
|
|
| Re: Could Robot Odyssey be coaxed into a ProDOS port? [message #378095 is a reply to message #378072] |
Wed, 12 December 2018 12:09 |
qkumba
Messages: 1584
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
Presumably there's an ID byte in one particular sector that it reads to verify. If you found the routine that checks that value, you could select a different image to read. That's how I got D-Generation to work. It's five full sides, and has a nice selector routine that I suppressed entirely.
Alternatively, it might be possible to extract chunks of data into files with unique names, and return them based on the first track and sector that is requested. That's how some of my ports work, and why the filenames are not always sequential.
|
|
|
|
|
|
Members
Search
Help
Register
Login
Home
