Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!udel!princeton!phoenix!gallaher
From: gallaher@phoenix.Princeton.EDU (William Christopher Gallaher)
Newsgroups: comp.sys.apple2
Subject: Re: Makebin problems...
Message-ID: <5265@idunno.Princeton.EDU>
Date: 12 Jan 91 20:05:57 GMT
References: <91009.135020AABENSON@MTUS5.BITNET> <14829@smoke.brl.mil>
Sender: news@idunno.Princeton.EDU
Organization: Princeton University, Princeton, New Jersey
Lines: 27

In article <14829@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>In article <91009.135020AABENSON@MTUS5.BITNET> AABENSON@MTUS5.BITNET writes:
>>Hi everyone.  I just ordered my Orca/M upgrade, but I haven't received it
>>yet.  Anyway, I would like to use "makebin" to make a binary file to be
>>used under ProDOS 8.  Unfortunately, this version of ORCA generates OMF 2.0
>>files, instead of OMF 1.0, which makebin supports.
>
>I think the latest APW MAKEBIN supports OMF 2.0, and possibly the current
>ORCA/M upgrade does (I haven't tried it yet).

Although I don't have the newest MAKEBIN yet, I have found a patch to
let Makebin recognize 2.0 files, as long as they don't use compressed
relocation records or Expressload headers.  I have ZapLink version
1.2.2, and Makebin is 1.1.  With a little disassembly of MAKEBIN,
I found that it would recognize the 2.0 files with the following change:

Change byte $0528 (offset) from $01 to $02

As long as you link with the "-X" and "-C" flags (disabling the creation
of an ExpressLoad header and creation of compressed records), the new
"MAKEBIN2" (as I call it) utility will recognize the OMF 2.0 files that
ZapLink creates.

Enjoy!

Scott Blackman
blackman@phoenix (IGNORE posting address ... using a friend's account)