Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.apple2.programmer > #639 > unrolled thread

MPW IIGS package

Back to article view | Back to comp.sys.apple2.programmer

Contents

  MPW IIGS package retrogear <larrygr510@gmail.com> - 2013-02-16 06:20 -0800
    Re: MPW IIGS package D Finnigan <dog_cow@macgui.com> - 2013-02-17 22:32 +0000
      Re: MPW IIGS package retrogear <larrygr510@gmail.com> - 2013-02-17 16:01 -0800
        Re: MPW IIGS package Steven Hirsch <snhirsch@gmail.com> - 2013-02-17 21:07 -0500
          Re: MPW IIGS package retrogear <larrygr510@gmail.com> - 2013-02-17 20:26 -0800
            Re: MPW IIGS package Stavros Karatsoridis <skaratso@gmail.com> - 2013-02-19 12:10 -0800
              Re: MPW IIGS package D Finnigan <dog_cow@macgui.com> - 2013-02-19 20:57 +0000
                Re: MPW IIGS package retrogear <larrygr510@gmail.com> - 2013-02-19 14:54 -0800
                  Re: MPW IIGS package Steven Hirsch <snhirsch@gmail.com> - 2013-02-19 21:39 -0500
                Re: MPW IIGS package retrogear <larrygr510@gmail.com> - 2013-02-27 08:30 -0800

#639 — MPW IIGS package

I am so close to being able to compile the IIGS system sources with MPW IIGS. The code is all assembling until it looks for the tool called overlayIIGS which may have been in the original MPW IIGS package ? I am mainly doing this for historical purposes to see if it can still be accomplished. If anyone knows where this tool might exist please let me know. Reply here or gmail me at larrygr510. Whether we admit it or not most of what this group does is re-live a rich part of the history of computing. Thanks.

[toc] | [next] | [standalone]

#644

retrogear wrote:
> I am so close to being able to compile the IIGS system sources with MPW
> IIGS. The code is all assembling until it looks for the tool called
> overlayIIGS which may have been in the original MPW IIGS package ?

We've probably done the same searches and came up with the same results:
overlayiigs likely was an Apple-internal MPW tool. There is no mention of it
anywhere in the Apple II Usenet archives here at Mac GUI, nor any mention of
it on the Web according to Google. Nor did I find any remark about it in any
MPW documentation.

Probably the best way to proceed is to first figure out what exactly it did
by examining the make files and examining how it is used. I think it was
used to overlay parts of files to make a composite file, but I could be
wrong.

-- 
]DF$
Apple II Book: http://macgui.com/newa2guide/
Usenet: http://macgui.com/usenet/  <-- get posts by email!
Apple II Web & Blog hosting: http://a2hq.com/

[toc] | [prev] | [next] | [standalone]

#645

> We've probably done the same searches and came up with the same results:
> overlayiigs likely was an Apple-internal MPW tool. There is no mention of it 
> anywhere in the Apple II Usenet archives here at Mac GUI, nor any mention of
> it on the Web according to Google. Nor did I find any remark about it in any 
> MPW documentation. 
> Probably the best way to proceed is to first figure out what exactly it did
> by examining the make files and examining how it is used. I think it was 
> used to overlay parts of files to make a composite file, but I could be 
> wrong.
> 

the tool overlayiigs appears to be used as follows:

overlayiigs inputfile outputfile -a $6400
	
which places input file into output file at offset $6400. I suppose this could be done manually with a hex editor. Any utility come to mind that can do this?

Larry

[toc] | [prev] | [next] | [standalone]

#646

On 02/17/2013 07:01 PM, retrogear wrote:
>
>> We've probably done the same searches and came up with the same results:
>> overlayiigs likely was an Apple-internal MPW tool. There is no mention of
>> it anywhere in the Apple II Usenet archives here at Mac GUI, nor any
>> mention of it on the Web according to Google. Nor did I find any remark
>> about it in any MPW documentation. Probably the best way to proceed is to
>> first figure out what exactly it did by examining the make files and
>> examining how it is used. I think it was used to overlay parts of files
>> to make a composite file, but I could be wrong.
>>
>
> the tool overlayiigs appears to be used as follows:
>
> overlayiigs inputfile outputfile -a $6400  which places input file into
> output file at offset $6400. I suppose this could be done manually with a
> hex editor. Any utility come to mind that can do this?

IF this is being fed an object file, I have a feeling it may be doing segment 
relocation.  Maybe not as simple as a mechanical overlay.

[toc] | [prev] | [next] | [standalone]

#647

> IF this is being fed an object file, I have a feeling it may be doing segment  
> relocation.  Maybe not as simple as a mechanical overlay.

the linker and makebin are run before this step so they should be binary files. the hex editor would have to run from the Basilisk Mac OS or can be copied out to a Windows folder. Basilisk has the copy to Windows feature built in. I have all the binaries compiled for the GS firmware and their offsets mapped so if I can patch them together I might almost have a ROM 04 Mark Twain ???  

[toc] | [prev] | [next] | [standalone]

#648

On Feb 17, 11:26 pm, retrogear <larrygr...@gmail.com> wrote:
> > IF this is being fed an object file, I have a feeling it may be doing segment
> > relocation.  Maybe not as simple as a mechanical overlay.
>
> the linker and makebin are run before this step so they should be binary files. the hex editor would have to run from the Basilisk Mac OS or can be copied out to a Windows folder. Basilisk has the copy to Windows feature built in. I have all the binaries compiled for the GS firmware and their offsets mapped so if I can patch them together I might almost have a ROM 04 Mark Twain ???

Nope. You won't have a ROM 04.

The Mark Twain prototypes I've seen all have ROM 3 in them. The
project never got far enough for a new ROM to be written for the
machine. The source code is the source code for ROM 3.

[toc] | [prev] | [next] | [standalone]

#649

Stavros Karatsoridis wrote:
> 
> Nope. You won't have a ROM 04.
> 
> The Mark Twain prototypes I've seen all have ROM 3 in them. The
> project never got far enough for a new ROM to be written for the
> machine. The source code is the source code for ROM 3.
>

But with the copyright year changed to 1991 instead of 1989.

[toc] | [prev] | [next] | [standalone]

#650

On Tuesday, February 19, 2013 2:57:09 PM UTC-6, D Finnigan wrote:
> Stavros Karatsoridis wrote: > > Nope. You won't have a ROM 04. > > The Mark Twain prototypes I've seen all have ROM 3 in them. The > project never got far enough for a new ROM to be written for the > machine. The source code is the source code for ROM 3. > But with the copyright year changed to 1991 instead of 1989.

so much for wishful thinking. at least I can byte compare the result with the original ROM 03

[toc] | [prev] | [next] | [standalone]

#652

On 02/19/2013 05:54 PM, retrogear wrote:
> On Tuesday, February 19, 2013 2:57:09 PM UTC-6, D Finnigan wrote:

>> Stavros Karatsoridis wrote: > > Nope. You won't have a ROM 04. > > The
>> Mark Twain prototypes I've seen all have ROM 3 in them. The > project
>> never got far enough for a new ROM to be written for the > machine. The
>> source code is the source code for ROM 3. > But with the copyright year
>> changed to 1991 instead of 1989.

> so much for wishful thinking. at least I can byte compare the result with
> the original ROM 03

I still think it's very much worth doing, particularly if you can get it 
byte-accurate.

Steve

[toc] | [prev] | [next] | [standalone]

#667

On Tuesday, February 19, 2013 2:57:09 PM UTC-6, D Finnigan wrote:
> Stavros Karatsoridis wrote: > > Nope. You won't have a ROM 04. > > The Mark Twain prototypes I've seen all have ROM 3 in them. The > project never got far enough for a new ROM to be written for the > machine. The source code is the source code for ROM 3. > But with the copyright year changed to 1991 instead of 1989.

Apparently the changes by 1991 included tools added to the ROM 03 firmware which are not present in the ROM 03 binary I have. Was there newer releases of ROM 03 firmware in systems that were sold? I am wading through the source trying to decide what belongs and what got left out. The notes indicate the changes were made to incorporate System 6.0.1. I am having fun mapping out the firmware and putting it all together. I will share my findings eventually. If this is documented somewhere already, let me know.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.apple2.programmer

csiph-web