| Name: | Asar v1.91 |
| Authors: | Alcaro, Check changelog for full list |
| Added: | |
| Version History: | View |
| Operating System: | Windows, Mac OS X, Linux |
| Platforms: | SNES |
| Games: | General |
| Source Available: | Yes |
| Featured: | Essential |
| Website: | Link |
| Description: | Asar is a Super Nintendo assembler based on xkas v0.06. It's the assembler used primarily on SMW Central. Asar's got a freespace finder, will ask for filenames if double clicked, can use parentheses and proper priority in math, can assemble SPC-700 and SuperFX codes, and has many, many other neat little features. The full list of features can be found in the manual. Some of the new features in Asar 1.90:
1.90 also deprecates a lot of features that will be removed in 2.0. For more details, check the changelog and the release announcement thread. For more details about new features, see the manual. Source code can be found on GitHub, where you can also contribute using issues and pull requests. |
| Tags: | assembler patcher |
| Comments: | 124 (jump to comments) |
| Rating: |
Download
583.09 KiB | 16,624 downloads
Comments (124)
So you have multiple options:
- Compile Asar yourself for OS X
- Find someone who has already compiled it for OS X and nicely ask them for a copy
- Just use the Windows version via wine
Just a minor bugfix release with virtually no user-facing changes, everything appears to work fine, tested the same way as 1.90.
Tested by applying all the patches in the site one by one and checking output almost-equivalence with previous asar version (total equivalence is impossible due to changes in the freespace finder algorithm).
ASAR asks for a patch and I type "[patchname].asm"
Next it asks for the ROM and I type "[romname].smc"
Am I missing a step?
Can you verify the file size of your ROM? It should be 1 MB or larger. If that's not the case, you're likely trying to use a corrupt rom.
A read at $00FFD5 failing is something I can only imagine happening if either you're not providing a ROM file, or you're providing an incorrect ROM file (smaller than 1 MB).
"retry.asm:23: error: (E5039): SNES address 00FFD5 in read function out of bounds. [if read1($00FFD5) == $23]
retry.asm:40: error: (E5039): SNES address 01E762 in read function out of bounds. [if read2($01E762) == $EAEA && read1($009EF0) != $00]
retry.asm:48: error: (E5039): SNES address 05DAA3 in read function out of bounds. [if read1($05DAA3) == $5C]
Errors were detected while assembling the patch. Assembling aborted. Your ROM has not been modified."
I could not find a solution in the user's manual.
Probably never. Next version is likely gonna be 1.91. Not ETA yet, though.
thanks to yoshifanatic for telling me this
Never mind, I removed the lorom version to work with SA-1 and it works now
thanks to yoshifanatic for telling me this
That's usually an issue with the file extension. Change to .smc instead of .sfc, if you haven't.
Is it possible.
You need a tool that runs Windows tools like CrossOver to make it work.
macs don't use .exe files
error: (E5016): File 'owcount.asm' wasn't found.
Errors were detected while assembling the patch. Assembling aborted. Your ROM has not been modified.
0034:fixme:ver:GetCurrentPackageId (0x33fe94 0x0): stub
What there's a trojan malware in asar? Omg I gotta tell everyone!But seriously, even if there was a trojan (I trust the community enough that I personally don't worry) you can actually modify a trojan to actually act as an automatic updater! Also fun fact: did you know that some antivirus software is actually a modified virus? Also, did you know that, in practicality, any installer file (apk, set up wizards, ect...) are, by definition, a trojan? So, a trojan "malware" might actually BE beneficial! Just thought I'd share this! I hope goombud sees this... Or anyone else that thinks this a virus, for that matter.
1 Azar te dice el nombre del parche lo insertas en Entre patch name
2 y luego te dice el ROM y listo no es complicado del todo
YAY!!! No virus message!YAY!!! No virus message!Can you help me with tutorial
>app says ver1.60
12/10
???
What's SA-1?
But yeah, an alternate way of doing the same thing would be
which is what I've been using so far. I assumed it was more common than !!.
Regardless, I edited it in the 1.27 version.
So yeah, not quite sure what to do about it in the future. I think randomdude proposed reintroduing the feature, but marking it as "deprecated" and making it throw a warning.
People are aware of this and an update will probably happen soon after this one is accepted.
For now, changing the if statement on line 203 of lzx.asm to
Label:
.Label:
+
-
would mean different things, depending on if they were used inside or outside of a macro. In my opinion not an ideal solution, either. With the current implementation, the syntax is clear and means just a single thing, no matter the context (of course ?Label can't be used outside of macros, anyways, so the context doesn't matter there, but Label and #Label do the same thing, no matter where they are used).
I think one reason for this mess is that the concept of macros in xkas/Asar is kinda shaky to begin with. I personally like to think of macros as a text replacement mechanism, kinda like in C preprocessors, and that's mostly how I treat them, though in xkas and Asar, they also have traits/behaviors that are more function-like. This makes everything regarding them a bit tricky to deal with. When working with them, though, I prefer to lean more towards the "text replacement" side, which also influenced my decision here. Letting labels "leak" outside of macros by default is more "text replacement"-like, while not letting them leak outside is more "function"-like.
But backwards compatibility says that's hard or impossible to fix.
?Label
?.Label
?+
?-
for labels that should be local to the macro they're in.
#Label
for labels that are global, but don't modify the label hierarchy. All other types of labels are supposed to leak outside of macros, that's by design.
I have tried 4 times and I just can`t get it to work. It says it can`t open the file.
EDIT: I`m just stupid, I forgot to type a bit of the patch name.
This bug has been complicating some of the stuff I've worked on recently, and it'd be nice if it was fixed.
should attach .baz to foo:, not ?bar:.
This also happens on +/- symbols too, as tested on GPS.
Possibly the most annoying bug I've experienced when using GPS and PIXI. Thank god uberasm tool's library does not use that, instead it uses filename_label:
Probably, I'm not sure.
Actually, judging by test.cpp being made for Windows and Linux simultaneously (backslashes, but also including sys/stat.h), someone dropping a libasar.so in the source directory, and the empty help.sfc, there's a fair chance it doesn't.
So at least it seems like I didn't break anything that was previously working.
New features:
NOTE: Based entirely on conversion tables I got from Ladida; don't know if these conversions are actually correct. Some features may not work as intended when using those mappers (such as freedata, for example), but I can't verify this.
Bug fixes:
Notes:
Also if a tools moderator sees this, can you please moderate this version? I don't want to submit version 1.50 before version 1.40 has been approved (or denied). Thanks!
I'm late (don't regularly check the comments here). What bug is it? Maybe report it here if it still exists and needs to be fixed?
The first sentence of its description should be removed.
Kamekku, don't mislead people like that.
Use Destroyer.
niiice.
I don't really see much uses for the new functions but readfile seems cool.
New features:
turns into
for example, whereas
turns into
Bug fixes:
Notes:
It is recommend to everyone update it to avoid further issues, specially if you're using an enhancement chip in your ROM hack.