| |
Carrion
Registered: Feb 2009
Posts: 317 |
Exomizer problems on mac os?
Hi to all!
Do you guys encounter strange behaviour of exomizer on mac os (intel)?
I use this command:
./exomizer.exe sfx basic main.prg -s"lda #$01 sta $d021" -o test.prg
causes exomizer to stop with this message:
line 864, syntax error, unexpected STA
Parse failure.
this command:
./exomizer.exe sfx basic main.prg -x "lda #$01 sta $d021" -o test.prg
gives:
line 1290, syntax error, unexpected STA
Parse failure.
Both commands work OK on Windows.
Exomizer compiled on mac os without any warnings or errors. What do I do wrong? or is it mac os version issue?
TIA
[edit]
I get these messages with exo 3.0.2
3.1.1 stops as well but with:
line 1434, syntax error
Parse failure
[edit2]
It's the quotes.... XD
Thanks Trap! |
|
... 17 posts hidden. Click here to view all posts....
|
| |
Carrion
Registered: Feb 2009
Posts: 317 |
Quote: Problem solved, now for some off-topicness:
Why Exomizer in the first place? :)
One of my many pet peeves is needlessly slow decrunch, and Exomizer should only be used if you really need the size.
That basically only goes for cracks, where minimum size earns a flower pot.
(For 4K demos and the like, even slower crunchers exist, but for a good reason.)
There are many other crunchers for self-extracting executables with shorter load-to-run times, despite slightly higher block count.
@Krill
the size is key factor in my game. With my "coding skills" there was not much memory left. all three part (intro, main game, end) after unpacking the intro take 0801-ffff. levels inside the game are BB2 packed though. |
| |
Krill
Registered: Apr 2002
Posts: 2980 |
Quoting FranticWhat cruncher would be optimal (generally speaking) if total loading+decrunch time is the issue, and if a standard action replay cartridge is used to load the crunched program? Before settling on Exomizer for a given program, i'd recommend trying TinyCrunch V1.2 (extremely fast decrunch, but limited crunchiness) and https://github.com/bboxy/bitfire/tree/master/packer/zx0 (as crunchy as Exomizer on average, but a lot faster decrunch). |
| |
Krill
Registered: Apr 2002
Posts: 2980 |
Quoting Carrion@Krill
the size is key factor in my game. With my "coding skills" there was not much memory left. all three part (intro, main game, end) after unpacking the intro take 0801-ffff. levels inside the game are BB2 packed though. Ah, interesting! :)
Then you're always scratching the $0801-$d000 border even with Exomizer, i take it? (ZX0 might still be worth a try.)
When the game comes in three files (and 1541/71 compatibility is all you care for), perhaps try Transwarp on it. Gives you encryption of the end part for free, you only need to bury the key well. ;) (And of course this might delay the inevitable cracks by... anything within 5 to 50 hours? =D) |
| |
iAN CooG
Registered: May 2002
Posts: 3193 |
Interesting, I didn't know zx0 was now able to make c64 sfx programs. As of now I think it was only used for the loader in Vinyl Tribute #2 unless there are other demos where Bitbreaker isn't credited for the loader.
Can anyone build zx0.exe for win32/win64? I don't seem to have all tools required in the makefile from the bitfire 1.0 repo. |
| |
Krill
Registered: Apr 2002
Posts: 2980 |
Quoting iAN CooGInteresting, I didn't know zx0 was now able to make c64 sfx programs. As of now I think it was only used for the loader in Vinyl Tribute #2 unless there are other demos where Bitbreaker isn't credited for the loader.
Can anyone build zx0.exe for win32/win64? I don't seem to have all tools required in the makefile from the bitfire 1.0 repo. I've used the ZX0 SFX option for a game on the Transwarp showcase images.
But let's not confuse decrunch-loading ZX0-packed files with having an executable packed with ZX0. :)
That said, the SFX portion still needs a bit of love, Exomizer is more mature in that regard.
Anyways, the tools you need are standard *NIX tools like grep, sed and hexdump. These should also work in a Windows incarnation (from mingw et al.). |
| |
Claus_2015
Registered: Oct 2012
Posts: 53 |
Regarding the macOS issue: make sure to disable "Use smart quotes and dashes" in System Preferences -> Keyboard -> Text. Otherwise, macOS will happily convert your quotes in the shell to start and end quotes, which will confuse most commandline tools. |
| |
Carrion
Registered: Feb 2009
Posts: 317 |
@Claus
Yeah that's mega annoying. I disabled it already as it made using the Vice monitor impossible. ;) |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: @Claus
Yeah that's mega annoying. I disabled it already as it made using the Vice monitor impossible. ;)
same here, made me ditch the internal monitor and now always use an external. :D |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
Quoting KrillThat said, the SFX portion still needs a bit of love, Exomizer is more mature in that regard.
feature requests/suggestions welcome, so just let me know what i can improve :-) Meanwhile there's also salvador that outputs zx0 format, but crunches as good as the slow zx0 crunching, but as fast as with the quick mode. As i made some slight changes on the zx0-encoding to make it suit better for the 6502, i need to adopt/fork from the original though or think about a reencoder that also includes all the c64 features needed. |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
What is salvador? |
| Previous - 1 | 2 | 3 - Next |
