News

  Frontpage
  News archive
  News topics

Resources

  MSX Forum
  Articles
  Reviews
  Fair reports
  Photo shoots
  Fairs and meetings
  Polls
  Links
  Search

Software

Downloads
Webshop

MRC

  Who we are
  Join our team
  Donate
  Policies
  Contact us
  Link to Us
  Statistics

Search

Login

Lost your password?

Statistics

There are 37 guests and 1 MSX friend online

You are an anonymous user.

VRAM depackers for BitBuster and Pletter

Utilities - VRAM depackers for BitBuster and Pletter

Tuesday, February 19, 2008 - 21:14
Submitted by: Metalion
Topic: Utilities

Metalion just released VRAM depacker routines for BitBuster v1.2 and Pletter v0.5b, which work on all MSX models. These direct VRAM depacker routines are a first release, as they work only on VRAM addresses up to $3FFF. New releases working on all the VRAM space are planned to be released in the next few weeks. For further info, see this forum thread.

Relevant link: BitBuster v1.2 VRAM depacker (16Kb)
Relevant link: Pletter v0.5b VRAM depacker (16Kb)

By Google

By ARTRAG on February 19 2008, 22:55

great work well done!

By Yukio on February 19 2008, 23:47

It should be very nice ...

By Metalion on February 20 2008, 07:10

Thanks for your nice comments.

I must say that dvik pointed to me yesterday that the code needed to be lightly modified for MSX1 applications since the OUTs are too close from one another, which could cause VRAM data corruption. Those needed corrections will be added in the next releases.

By jltursan on February 20 2008, 10:38

Thanks anyway!, these modifications are easy to add as is.

Great work!

By Whizzy on February 20 2008, 12:12

Very nice. I may be going to use this

By SapphiRe on February 20 2008, 12:30

Very nice!

I guess it's also necessary to read bytes 6 an 7 on main ROM for a total compatibility with some weird MSX1 models.

By Metalion on February 22 2008, 16:58

I just uploaded the new sources, which include a slight modification to take into account the VDP timing issues. I added a NOP instruction where VDP timing might be critical. Fine tuning (adding or removing NOPs) will have to be done by the user, according to its needs. A readme.txt is added where everything is explained.

By ARTRAG on February 22 2008, 19:25

IMHO well nops between outs at 0x99 are never needed, but thanks for the great work!!

Recent news

MSX version of Coleco’s Tutankham

34th MSX Users Meeting in Barcelona

MSX VDP on a ZX Spectrum

Tir-Nan-Og translation

MSXart'08: 3rd entry: 25 Years later

Where in the world..

Bonami Retro Fair - photoshoot by Dioniso

MSX Error 51 videos

Nowind firmware 2.1

[ News archive ]

Latest forum posts

v9990 Transfer Speed - Update

Selling a large part of my MSX collection

Have the VDP limits been reached?

Basic interface

BCF disk images

MSX basic listing readable on pc.

MSX Basic games....

GPS Navigator for MSX: Possible?

[ View MSX forum ]

Poll

What will our scene be like in ten years?

Extremely active

Not even worth mentioning anymore

[ View results ]

Latest reactions

Tir-Nan-Og translation

MSX version of Coleco’s Tutankham

MRC Download Charts - September 2008

34th MSX Users Meeting in Barcelona

MSX VDP on a ZX Spectrum

MSX article in leading Spanish magazine

Bonami Retro Fair - photoshoot by Dioniso

Nowind firmware 2.1

MSX Error 51 videos

Affilates

Sponsored Links

(c) 1994 - 2008 MSX Resource Center Foundation. MSX is a trademark of MSX Licensing Corporation.