@Agent - I was thinking of using one large box for the region from the lowest point to the bottom of the screen, and then using the lines for the top. I think, like you said, it would still be too slow. For one thing, and you can correct me if I'm wrong, the interpreter would still be outputting 800 lines, and it doesn't matter how long the lines are--- it would still run just as slow.
@Peter X - Thanks for the lock/unlock tip--- I'll try that when I get home tonight

I have zero experience using those types of commands (get pixels pointer, etc.) because the manual is so scarce with information about them. I'll let you know what happens.
@the winch - Sorry about being a bit vague--- my terrain is truly 800 pixels wide. The only scrolling my game does is on the Y-axis when a player fires a shot. The terrain will be destructable and deformable. By building an image into a memblock, do you mean one large landscape image? My goal is to use random landscapes ala Scorched--- right now it builds the landscape randomly using a cosine wave.

--[
Gang Wars of New Canada]-- TGC Compo Game --