Quote:

Aurora, whaz yer prob? I can't even name one asm that will add xtra data @ files.

You're kidding, right?
What's the name of assembler again, we were just talking about?

Oh, and try this on a couple of assemblers:

    org $0100
    nop
    org $80FF
    nop

and watch the result. I expect a binary file of 2 bytes: 00 00. Not a 32k file full of zeros, but that's exactly what you get with quite a few assemblers!

Quote:

stupid asian guitars.. bleh. long life gibson and ibanez indeed!

I wouldn't know, can't play the guitar for a bit (Google was my friend)
I remember Hohner, though. was my very first musical instrument: a recorder ("blokfluit" )

Quote:

love to work with the Bios, and the only problem I have with WBASS is that its programs/files cannot exceed 4kb (which is really small). But I just have a whole big bunch of small files.... (almost as if each routine has a different file haha) Still there is always a good thing about small files.

Ah, you got the initial setup.
You can adjust the STARTING pointer for your source, just put'm slightly above your BASIC space (starting somewhere on #8200 for example) That means you can't use a BASIC listing anymour (or atleast no big ones) but you'll be having more than 16k of source data (if you count $c000-$d000 and don't assemble in that space)

here's how I have set up my WBAars environment:

Basic: BUUUUUZZ (read:NO BASIC) harf harf.
WB-source: #8000-#D1FF
assembling ALWAYS to page 0,1 or 2.
him-mem for the kernel: #d200-d4FF (somewhere)

Quote:

Quote: Aurora, whaz yer prob? I can't even name one asm that will add xtra data @ files. You're kidding, right? What's the name of assembler again, we were just talking about? Oh, and try this on a couple of assemblers: org $0100 nop org $80FF nop and watch the result. I expect a binary file of 2 bytes: 00 00. Not a 32k file full of zeros, but that's exactly what you get with quite a few assemblers!

yeah, so? the ASSEMBLER did NOT add any extra data dude. It's just that you are stupid enought to TELL the assembler to SAVE data from #100 to #8100.

NEXT!

Quote:

You can adjust the STARTING pointer for your source, just put'm slightly above your BASIC space (starting somewhere on #8200 for example)

YIPPIE ~!~
I didnt know that was possible !~!
Which brings me to my next question (can you see it comming??)

Quote:

adjust the STARTING pointer for your source

How???

org address?

oh no

this time it's set /b address
and with set /e address you can specify the top address for your source

Thaz the one. The start/end addresses are stored somewhere. If ya got the original BW loader it even is included in the basic source (IIRC!) change it there, save and have it set all of the time. (something like that... it's been yeeears)

it says

endaddress buffer: $DA87
thats E

But
B
is for Bin numbers: %

there is no setting for the beginning address

anyway,
I guess that when I set endaddress to $E000 or something, that this will give me more space,
right???

then it's set /s address

quite rusty after not using WB-Ass2 anymore after... about 7 years or so.

is:

set /s $4000 a good idea???

iirc that's where the assembler itself is stored. You can't really change the end-address of the buffer either, since that's where the stack is. WB-ASS2 just has that problem, it doesn't allow for big sources. That's why I suggested you change to a cross-assembler such as sjasm or tniasm...

It's been a long time since I used wbass2, but I can't remember ever having much trouble with source size. And I found sources (in wbass2 tokenised format) up to 20kb in my old stuff. Which was already too much for practical purposes. That was a demo source that included everything from intro, main and end parts to replayers for both fm-pac and music-module in a single file.

Still, nothing easier than cross assemblers though. So much easier to combine everything you need into a single project.

That's because a 20kB source can hardly be considered big. If the file is 20kB in WB format, it's prolly around 40kB in ASCII format, 50kB tops. If you're gonna be making a game like Space Manbow, you'll prolly end up coding anywhere between 100 - 250kB's of source, depending on your coding style. BombaMan, or so I'm told, is something in the order of 1MB source data. While it could be *possible* to make a project of that size in WB-ASS2, it's hardly worth the effort. It would involve lots of DLOADs and PAGEing. Anyhoo, switch to a cross-assembler. There's nothing better than assembling a 250kB source in less than half a second...

Quote:

Quote: Oh, and try this on a couple of assemblers: org $0100 nop org $80FF nop and watch the result. I expect a binary file of 2 bytes: 00 00. Not a 32k file full of zeros, but that's exactly what you get with quite a few assemblers! yeah, so? the ASSEMBLER did NOT add any extra data dude.

It did: 32k of it.

Quote:

It's just that you are stupid enought to TELL the assembler to SAVE data from #100 to #8100.

Nope. I told the assembler to use a different location counter for the second NOP. That'ssomething completely different. If I want to assembler to spill 32k of zero's I'd code something like:

    org $0100
    ds 32*1024
    nop

Having multiple ORGs in one source, without having the assembler fill up the 'holes' is very convenient for writing e.g hooks and other pieces of relocatable code.

Quote:

It's been a long time since I used wbass2, but I can't remember ever having much trouble with source size. And I found sources (in wbass2 tokenised format) up to 20kb in my old stuff.

\that is strange,
because by then I will get the message:
out of memory