Skip to content
This repository was archived by the owner on Oct 14, 2023. It is now read-only.

Commit 89c5fa1

Browse files
committed
updated to v1.03
1 parent 62375bc commit 89c5fa1

File tree

2 files changed

+254
-155
lines changed

2 files changed

+254
-155
lines changed

README.md

Lines changed: 29 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,40 @@
1-
# isx2gb v1.02
1+
# isx2gb v1.03
22

3-
Command line utility to convert Intelligent Systems eXecutable files into Game Boy ROM format. This is my personal replacement for abISX v1.02 by Anaerob. It has following features:
3+
Command line utility to convert Intelligent Systems eXecutable files into Game Boy ROM format and more. This is my personal replacement for abISX v1.02 by Anaerob. It has following improvements:
44

55
- code / data overflow in bank 0 is allowed, excess bytes are moved to bank 1 without any fuss.
6-
- you're not forced to ORG your code/data if you don't need to, just GROUP it in appropriate banks.
7-
- you can ORG your code in RAM or SRAM (why not?) and use `-r` option to save it to file for further processing. This might be appreciated by ROM hackers while generating series of patches.
8-
- to create symbolic file use CAPSOFF/SMALL with PUBALL directives in your source(s).
6+
- you're not forced to ORG your code / data if you don't need to, just GROUP it in appropriate banks.
7+
- you can ORG your code to RAM or SRAM (why not?) and save it to file(s) for further processing. This might be appreciated by clever coders or when size does matter.
8+
- you can patch Game Boy ROM on the fly exploiting ISX file as [IPS](http://justsolve.archiveteam.org/wiki/IPS_(binary_patch_format)) replacement. All the code / data will be applied to proper offsets.
9+
- creating symbolic file is easy, just use CAPSOFF/SMALL with PUBALL directives in your source(s).
910
- ROM checksums are fixed automagically providing that there's a valid logo in header section.
10-
- ROM map is more readable.
11+
- more readable ROM map.
1112

12-
### Options :
13+
### Options :
1314
```
14-
-f switch ROM filling pattern to 0xFF
15-
-p round up ROM size to the next highest power of 2
16-
-r save isx records separately
15+
⚠ there were changes from 1.02 to 1.03
16+
17+
-d dump isx records into binary file(s)
18+
-f switch ROM filling pattern from 0x00 to 0xFF
19+
-p patch supplied ROM file with ISX records
20+
-r round up ROM size to the next highest power of 2
1721
-s create symbolic file for debugger
1822
```
1923

24+
### Examples :
25+
```
26+
isx2gb -d code.isx
27+
```
28+
This will save all ORG sections into separate binary files, no ROM file is created. If you're into 128B/256B/1K/etc. coding, try to place your code in WRAM and compress such output for better result.
29+
```
30+
isx2gb -p patch.isx romfile.gbc
31+
```
32+
Patch `romfile.gbc` with code / data from `patch.isx` which basically works like `.ips` patching you're most likely familiar with. Take a look at my [Macross 7 english translation](https://github.com/gitendo/bm7j) for a proof of concept.
33+
```
34+
isx2gb -f -r -s game.isx
35+
```
36+
Create ROM file which will have free space filled with 0xFF instead of 0x00 (default). Round it to proper size, just like commercial stuff and produce symbolic file to be used with debugger ie. [BGB](http://bgb.bircd.org/).
37+
2038
### Important :
2139
Let me know if you see similar message:
2240
```
@@ -26,8 +44,7 @@ Currently only record types 0x01, 0x13, 0x14, 0x20, 0x21, 0x22 are supported and
2644

2745
### To do :
2846
- improve rom padding option
29-
- clean up code / comments
3047
- test it thoroughly
3148

3249
### Bugs :
33-
I've fixed every one I found. Let me know if there's any more.
50+
Let me know if there's any.

0 commit comments

Comments
 (0)