MSX-O-Mizer v1.4

Página 1/2
| 2

Por hitchhikr

Rookie (23)

imagem de hitchhikr

08-05-2008, 14:50

Instead of monopolizing the headlines i'd rather post it here.

v1.4:
- The depackers of this new version are 5 bytes shorter.

pagesperso-orange.fr/franck.charlet/MSX-O-Mizer.zip

Entrar ou registrar-se para comentar

Por wolf_

Ambassador_ (10135)

imagem de wolf_

08-05-2008, 15:31

Good idea, just like the 1chipMSX updates thread, a continuous development thread would be the best if you expect updates every few days.. kinda like SymbOS as well.

Por Metalbrain

Expert (67)

imagem de Metalbrain

08-05-2008, 18:14

; 396 bytes which must be aligned on 8 bits boundary

If I understood the changes you've made, the new buffer size isn't really 396, but 256+104 = 360, and you can cut back that number to 256+72= 328 if you replace the +52 by +36 and +104 by +72.

Por hitchhikr

Rookie (23)

imagem de hitchhikr

08-05-2008, 18:35

Absolutely, i forgot to modify that.

Por ARTRAG

Enlighted (6978)

imagem de ARTRAG

09-05-2008, 00:34

Well, it works even in this way, and gives me 111 spare bytes for the 2K competition
to be invested in
1) MC bullets
2) collisions of bullets with robots
3) robot explosion
4) game goal management

Wink

Por hitchhikr

Rookie (23)

imagem de hitchhikr

09-05-2008, 12:20

v1.5 released:

- 2 bytes removed from the executable files (1 byte from the generic depackers).

So this game can now be packed into 2048 bytes which makes it a real 2k game ;).

Por hitchhikr

Rookie (23)

imagem de hitchhikr

09-05-2008, 16:12

v1.5b:

- Fixed a bug which could occur under certain circumstances during depacking.

Por hitchhikr

Rookie (23)

imagem de hitchhikr

10-05-2008, 16:16

v1.5d:

- Added a depacker for ROM based software.
- The packer will display a warning if the source and destination addresses would overlap
during the decrunching process (it may work fine nevertheless).

Por ARTRAG

Enlighted (6978)

imagem de ARTRAG

11-05-2008, 08:19

Great!! It will be usefull also for masxdev!!
Why the other code was'nt good for the rom?
I see tha the offsettable is also defined as EQU at 0E000h+328
What should be passed in BC exactly?

Por hitchhikr

Rookie (23)

imagem de hitchhikr

11-05-2008, 11:09

The input datas are modified by the depacker.
The offset table have to be passed in bc, i fixed the archive.

Por hitchhikr

Rookie (23)

imagem de hitchhikr

12-05-2008, 19:57

v1.5f released, i noticed a nasty bug with the first byte which wasn't pre-calculated right in some cases.

Página 1/2
| 2