a few Dos versions exists, I need one compatible for Windows 32bit or 64bit, Mainly for NES hacking
I tried looking at Google, But it only looks up DOS stuff!
I am using XVI32, But in order to put it in ASM properly via Text, need to use it via a BIN2DB or BIN2BYTE converter or something, as long it is not under DOS!
When I had this same problem for GNU assembler back when I was in the GBA scene, I made bin2s, part of
the GBFS distribution. You could take it, change the source to produce 6502 instead of ARM assembly, and recompile it with Visual C++ Express or MinGW. It should be a doddle if you know C.
EDIT: wrong language
tepples wrote:
When I had this same problem for GNU assembler back when I was in the GBA scene, I made bin2s, part of
the GBFS distribution. You could take it, change the source to produce 6502 instead of ARM assembly, and recompile it with Visual C++ Express or MinGW. It should be a doddle if you know C.
Thanks, I may look at that to see if I can get any of it to work on my VC++ 2008. (I have both 6.0 and 2008. and pretty soon 2010 if I can afford it a few to several years more.)
NOTE: Edited to the extremes of the other post
why don't you just .incbin the binary file?
Disch wrote:
why don't you just .incbin the binary file?
True, If you want it harder for anyone to edit source code, not just me, Anybody.
That is okay for CHR and such, But raw data, Not so realiable to edit via an Hex editor manually. But it's a preference.
if the amount of bin data is so big that you need to tool to generate a bunch of declarations then I don't really think anyone would want to edit that data manually...
I don't know what data is in question though...
I generally incbin anything that's big enough and tedious to write and can be generated with a program (i.e sine table).
I write a tool for any time consuming operation that can be automized... and they're DOS tools.......
Did you find a converter? I think all the ones I use like that are command-line apps. They should still work in windows though, I'd think.
Myself, the main times that I'll use .byte instead of .incbin anymore is if I'm including constants (and constant expressions) into it. I just find hex editing a single file a lot easier than scrolling through the source and then having to manually count out each byte to know precisely which offset you're editing.
Memblers wrote:
Did you find a converter? I think all the ones I use like that are command-line apps. They should still work in windows though, I'd think.
Myself, the main times that I'll use .byte instead of .incbin anymore is if I'm including constants (and constant expressions) into it. I just find hex editing a single file a lot easier than scrolling through the source and then having to manually count out each byte to know precisely which offset you're editing.
Not under 64 or 32-bit, If I was to switch back and forth from and to DOSBox: It's annoying! And Dosbox's Drive capabilities really suck in a way I wish I had my old DOS back!
I wish I had a better, more accurate emu besides DOSBox, in which the speed is inaccurate. And whenever I use a 32bit app built for DOS in there, It'd crash
The reason is: Palettes and maybe Metatiles
True, DOS apps don't work on 64-bit Windows without DOSBox. But I haven't compiled a DOS app since about 2001, when I switched from DJGPP+Allegro to MinGW+Allegro. Command-line apps compiled with MinGW or VC++ are intended for the Win32 toolkit of Windows 2000 and Windows XP, and I don't see what keeps them from running under WOW64 on 64-bit Windows.
I just made a quick one
byte to asm.
It's made in C#, .net 2.0. It will work on any windows platform that contain .net 2.0 or higher. Since you said you're using a 64 bit machine, I assume you mean Vista/Win7, that should not be an issue.
You can define the prefix (.DB/.BYTE whatever), the number of byte per row (nesasm limitation). You can output to the screen or a file.
Didn't test it much but it should do the job. It's a quickly made soft, nothing special. Maybe it will help other people, who knows.
Since there was no reply to this thread if the quick tool I made was useful or not, I guess I won't make any of them in the future.
Banshaku wrote:
Since there was no reply to this thread if the quick tool I made was useful or not, I guess I won't make any of them in the future.
i hate when that happens... one never get used to leechers
I made a Binary to .db converter a long time ago, because TASM doesn't have incbin. Anyone want it?
comegordas wrote:
i hate when that happens... one never get used to leechers
It depends who ask in the first place. If the main requester who mentioned that no such tool existed or doesn't work or dosbox suck could have just said "it's what I was looking for, thanks!" or "No, it doesn't do the job, maybe if it could that... " etc then at the least then I don't see my time as wasted.
I just felt like helping, even thought I don't have much time these days. Just a quick venting I guess.
edit:
@dwedit:
The file still exist. I didn't delete it. I didn't say that I'm removing the file because of the current events.
Hmm, I suspect this is a dead thread, but I did create a quick-and-dirty C program literally 2 days ago that converts the NES's 2BPP chr binary format into DB assembly data that can be fed into the ASM6 assembler for the NES flawlessly. If this is the kind of program you need, I can supply it for you I just need to check to make sure I didn't tie anything to my computers local environment variables real quick. Oh, and I wrote it on my 64 bit vista and windows 7 machines, so you should be covered. I can post the program if anyone will have use for it. I didn't check, but I think ASM6 only accepts graphics data in DB format, so thats what I made it for...
Ack! I forgot! Many thanks for the converter, I really appreciate the help.
I am going to school, So later!