Re: I have uploaded disk images of Magnetic Scrolls' "Corruption" to Asimov

[Hot Rod <hotrod.apple2@gmail.com>]

On Tuesday, September 4, 2012 9:24:48 PM UTC-5, Hot Rod wrote:
> On Tuesday, September 4, 2012 9:13:00 PM UTC-5, Hot Rod wrote:
> 
> > On Tuesday, September 4, 2012 3:37:33 PM UTC-5, Hot Rod wrote:
> 
> > 
> 
> > > On Tuesday, September 4, 2012 2:49:32 PM UTC-5, Hot Rod wrote:
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > On Tuesday, September 4, 2012 1:50:06 PM UTC-5, Hot Rod wrote:
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > On Monday, September 3, 2012 3:03:22 AM UTC-5, skylarking wrote:
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > > I got them a while ago and they aren't working, but someone may be able to hack them.
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > > Did you have foppies that worked, or only just these .dsk images?  Side A certainly has data on it, and does get to boot0, but on quick glance, it appears to be hanging in the $C65E datastrobe routine in ROM looking for address markers (at least in AppleWin).  That seems peculiar, given they're .dsk images (and not .nib).
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > Hmm, it looks like the boot loader is like an old EOA loader (IIRC), and the sectors in the .dsk image aren't in the order it's expecting.  It wants to load physical sector 7 into $900, but is getting a different sector instead ($B). Then it should load track $4, sector $1 into $A00, and that code seems to be on track $4, sector $E instead.
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > > So it looks like the sector ordering is mixed up.  Need to ponder what the correct mapping is...
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > Ok, so converting the image from ProDOS order to DOS order at least gets it to boot to the crack screen and load the rest of the regular boot... and then hang again in a datastrobe routine (now in an RWTS routine loaded into $2800-$2FFF though).  I wonder if the disk had mixed sector skewing?  Still looking...
> 
> > 
> 
> > 
> 
> > 
> 
> > Still not sure why it won't load the next boot section.  The code loads an RWTS from $2800-$2FFF, and then continues execution at $2F46.  All that does is to load from track $0, sector $9 through track $3, sector $F into $8000-$B6FF, and then jump to $8000 (with the X reg loaded with the slot number).  If I do that manually (via The Inspector), voila, Corruption finally starts.  But then it's unhappy about the volume number (wants a #$72).  Working around that, it then finally stops with an 'Internal error #3F5E00' (and to please record this number!).  Might be more RWTS trouble, don't know.
> 
> 
> 
> Aha!  By converting to a .2mg and putting a volume number of 114 ($72) on it, it now boots successfully on its own (and is now asking for disk 2).  I think I can untangle it from here (once I figure out the other volume numbers).

Hey, this thing has DHGR in it (I was thinking it was pure text).

Anyway, disk 2 is volume 115 and disk 3 is volume 116, and it now all seems to work.  Lots of disk swapping though - is there a way to configure it to use more than one drive?

I'll upload these fixed images to Asimov so more testing can be done.

]HR