RHDN Forum Archive - Hex editor problem

RHDN Forum Archive

Romhacking

ROM Hacking Discussion

Hex editor problem

Pages: 1 [2]

Author

Topic: Hex editor problem (Read 1 times)

Tauwasser
Guest

Re: Hex editor problem

« Reply #15 on: March 21, 2010, 03:08:30 am »

Quote from: Nightcrawler on March 20, 2010, 01:13:35 pm

Something just not quite wired the same as everybody else in that head of yours. Tongue

I see that as a positive thing. If everybody was the same, that would be awful. Also, the same goes for a lot of other people working certain professions.

Quote from: Nightcrawler on March 20, 2010, 01:13:35 pm

For small bits of data or text, this can be done via your project build file and/or assembly file.

And I see how that can be helpful. Yet, I don't use any cross-assembler at all, because most of them don't work very well for game boy and require DOS and all that crap. So yeah, for SNES your fancy project files might be an option, for GB they aren't. Though at the moment I am looking into WLA-DX, which was seemingly updated semi-recently in 2008... But I doubt it will work with what I have in mind.
So one shouldn't bad-mouth thingy in general just because it may not be as useful for SNES hacking.

cYa,

Tauwasser

Karatorian
Guest

Re: Hex editor problem

« Reply #16 on: March 27, 2010, 11:27:37 pm »

Quote from: Tauwasser on March 21, 2010, 03:08:30 am

And I see how that can be helpful. Yet, I don't use any cross-assembler at all, because most of them don't work very well for game boy and require DOS and all that crap.

I find it hard to belive that there aren't any decent Z80 assemblers out there. Or does the Gameboy require more than just Z80? Furtheremore, what do you mean by "DOS and all that crap"? I assume you mean that they're command line tools.

I could be getting into holy war territory, but what's wrong with that? There is very little reason for an assembler (or compiler) to have a GUI. Command line programs can be used by sophisticated build systems, such as make, or called from a shell script (batch file to you DOS/Windows users), or invoked easily from a good editor or IDE. GUI programs are difficult or impossible to use in such situations. Even if a GUI is desired, it would be more useful as a front end, rather than built into the core program.

Tauwasser
Guest

Re: Hex editor problem

« Reply #17 on: March 28, 2010, 09:01:29 pm »

Quote from: Karatorian on March 27, 2010, 11:27:37 pm

I find it hard to belive that there aren't any decent Z80 assemblers out there. Or does the Gameboy require more than just Z80?

Nope, it uses its own flavor of Z80 -- often called z80-gb or somesuch.

Quote from: Karatorian on March 27, 2010, 11:27:37 pm

Furtheremore, what do you mean by "DOS and all that crap"? I assume you mean that they're command line tools.

You're wrong. With "DOS and all that crap" I mean Dos and all that crap. I'm not installing DOS 6.22 anytime soon to find out if a tool is worth my time when it barely even has mouse-support in its editor o.o

Quote from: Karatorian on March 27, 2010, 11:27:37 pm

I could be getting into holy war territory, but what's wrong with that? There is very little reason for an assembler (or compiler) to have a GUI. Command line programs can be used by sophisticated build systems, such as make, or called from a shell script (batch file to you DOS/Windows users), or invoked easily from a good editor or IDE. GUI programs are difficult or impossible to use in such situations. Even if a GUI is desired, it would be more useful as a front end, rather than built into the core program.

See above. I know what command line tools are, so back off.

cYa,

Tauwasser

Nightcrawler
Guest

Re: Hex editor problem

« Reply #18 on: March 29, 2010, 07:29:27 am »

Trying to pull this discussion away from the abyss of evil...

What's wrong with these tools out of curiosity?

KingMike
Guest

Re: Hex editor problem

« Reply #19 on: March 29, 2010, 08:48:29 pm »

Quote from: Tauwasser on March 21, 2010, 03:08:30 am

I am looking into WLA-DX, which was seemingly updated semi-recently in 2008... But I doubt it will work with what I have in mind.

I've WLA-DX to insert some stuff in a GB hack. Been awhile since I did something with it, but here's my example:

Assembly file header:

Code:

.ROMDMG ;set GB assembly mode?

.MEMORYMAP ;CPU memory map. Works fine since ROM is only mapped to 0-7FFF anyways
DEFAULTSLOT 0
SLOTSIZE $4000
SLOT 0 $0000
SLOT 1 $4000
SLOT 2 $8000
SLOT 3 $C000
.ENDME

.ROMBANKSIZE $4000
.ROMBANKS 8

.BACKGROUND "romfile.gb"

.bank 0 slot 0 ;select bank and slot

.org $xxxx ;been awhile, but I believe this sets the insertion address in the bank
.orga $xxxx ;sets CPU address
insert code here

DOS batch file:

Code:

wla-gb -o game.asm game.o
wlalink -r game.txt romfile.gb

where game.txt is a list of objects. Works for me to just have this

Code:

[objects]
game.o

Pages: 1 [2]