home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsc!cbfsb!att-out!rutgers!cbmvax!fred
- From: fred@cbmvax.commodore.com (Fred Bowen)
- Newsgroups: comp.sys.cbm
- Subject: Re: ROM call woes
- Message-ID: <34865@cbmvax.commodore.com>
- Date: 3 Sep 92 13:31:07 GMT
- References: <1992Sep1.135948.1@kosmos.wcc.govt.nz>
- Reply-To: fred@cbmvax.commodore.com (Fred Bowen)
- Organization: Commodore, West Chester, PA
- Lines: 36
-
- Article <1992Sep1.135948.1@kosmos.wcc.govt.nz> asks:
- >Are their any programming guru's out there?
- >
- >I have a C64 ML program which I am converting to run on a 128.
- >There are a number of calls to the 64 ROM area which I'm having trouble
- >finding equivalents for on the 128. Most of these involve string
- >handling, which all my 128 books seem to skimp over.
- >
- >The addresses in the 64 are:
- >B475 ;reserve string
- >B6A3 ;free string
- >AD9E ;eval expression
- >B79E ;get parameter
- >
- >And a few others I think I have sourced okay. Any help would be really
- >appreciated - many thanks.
-
- $B475 (C64) $8688 (C128) Strini
- $B6A3 $877E FreStr
- $AD9E $AF96 FrmEvl
- $B79E $87F4 GetByt
-
- I have not played with these is quite a while, so I can't guarantee that
- the register and MMU setups are exactly the same. Keep in mind that some
- lower level BASIC routines expect a specific RAM bank to be in context
- already, and some will change the RAM bank. Also, strings are stored in a
- slightly different way (C128 has backpointers for better garbage collection),
- but if you stick to using ROM routines for everything you'll have no problem.
- --
-
- --
- Fred Bowen uucp: {uunet|rutgers|pyramid}!cbmvax!fred
- domain: fred@cbmvax.commodore.com
- tele: 215 431-9100
-
- Commodore Electronics, Ltd., 1200 Wilson Drive, West Chester, PA, 19380
-