CHRs 2

<body topmargin=0 leftmargin=0 marginheight=0 marginwidth=0> <table cellpadding=0 cellspacing=0 border=0><tr> <td valign="top" height=95 BGCOLOR="#CC99CC" TEXT="#080000" background="006265f1ezuady.png"> <div> <FONT SIZE="5" COLOR="#000000" FACE="Times New Roman" ><B>Final Fantasy Chronicles News</B></FONT><B>  </B><B> </B><B>|   </B><A HREF="index.htm" TARGET="_top" TITLE="Final Fantasy Chronicles News"><U><B>home</B></U></A></div> <div> <A HREF="id33.htm" TARGET="_top" TITLE="ChocoboMonkeys Art"><U>ChocoboMonkey's Art</U></A>   |   <A HREF="id34.htm" TARGET="_top" TITLE="ChocoboMonkeys Tile Creation"><U>ChocoboMonkey's Tile Creation</U></A>   |   <A HREF="id35.htm" TARGET="_top" TITLE="CHRs"><U>CHRs</U></A>   |   <A HREF="id36.htm" TARGET="_top" TITLE="CR2s"><U>CR2's</U></A>   |   <B>CHRs 2</B>   |   <A HREF="id38.htm" TARGET="_top" TITLE="Learning to Draw"><U>Learning to Draw</U></A>   |   <A HREF="id39.htm" TARGET="_top" TITLE="Thesis on Tile Art"><U>Thesis on Tile Art</U></A>   |   <A HREF="id40.htm" TARGET="_top" TITLE="Tile Making with Photoshop 5"><U>Tile Making with Photoshop 5</U></A>   |   <A HREF="id41.htm" TARGET="_top" TITLE="V2 Tutorial"><U>V2 Tutorial</U></A>   |   <A HREF="id42.htm" TARGET="_top" TITLE="Collision Detection"><U>Collision Detection</U></A>   |   <A HREF="id43.htm" TARGET="_top" TITLE="DMA"><U>DMA</U></A>   |   <A HREF="id44.htm" TARGET="_top" TITLE="Working with Bits"><U>Working with Bits</U></A>   |   <A HREF="id45.htm" TARGET="_top" TITLE="Item DAT Files"><U>Item & DAT Files</U></A>   |   <A HREF="id46.htm" TARGET="_top" TITLE="Menu Making"><U>Menu Making</U></A>   |   <A HREF="id47.htm" TARGET="_top" TITLE="Reading From Files"><U>Reading From Files</U></A>   |   <A HREF="id48.htm" TARGET="_top" TITLE="Savegames"><U>Savegames</U></A>   |   <A HREF="id49.htm" TARGET="_top" TITLE="Entity Talking"><U>Entity Talking</U></A>   |   <A HREF="id57.htm" TARGET="_top" TITLE="Mordred Tutorial 1"><U>Mordred Tutorial 1</U></A>   |   <A HREF="id58.htm" TARGET="_top" TITLE="Mordred Tutorial 2"><U>Mordred Tutorial 2</U></A>   |   <A HREF="id59.htm" TARGET="_top" TITLE="Mordred Tutorial 3"><U>Mordred Tutorial 3</U></A>   |   <A HREF="id63.htm" TARGET="_top" TITLE="Hicolor Fades"><U>Hicolor Fades</U></A>   |   <A HREF="id65.htm" TARGET="_top" TITLE="Tiny Tutorial on Multidimentional Arrays"><U>Tiny Tutorial on Multidimentional Arrays</U></A>   |   <A HREF="id67.htm" TARGET="_top" TITLE="V2.7 B10 Python Commands"><U>V2.7 B10 Python Commands</U></A>   |   <A HREF="id80.htm" TARGET="_top" TITLE="Overkills Tutorial 1"><U>Overkill's Tutorial 1</U></A>   |   <A HREF="id81.htm" TARGET="_top" TITLE="Overkills Tutorial 2"><U>Overkill's Tutorial 2</U></A></div> <div> </div> </td> </tr><tr> <td valign="top" height=385 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <A HREF="id12.htm" TARGET="_top" TITLE="Tutorials"><U>Tutorials</U></A>   |    <FONT SIZE="1" COLOR="#0000BF" FACE="Arial" ><A HREF="index.htm" TARGET="_top" TITLE="Final Fantasy Chronicles News"><U> home</U></A></FONT></div> <div> <A HREF="id33.htm" TARGET="_top" TITLE="ChocoboMonkeys Art"><U>ChocoboMonkey's Art</U></A>   |   <A HREF="id34.htm" TARGET="_top" TITLE="ChocoboMonkeys Tile Creation"><U>ChocoboMonkey's Tile Creation</U></A>   |   <A HREF="id35.htm" TARGET="_top" TITLE="CHRs"><U>CHRs</U></A>   |   <A HREF="id36.htm" TARGET="_top" TITLE="CR2s"><U>CR2's</U></A>   |   <B>CHRs 2</B>   |   <A HREF="id38.htm" TARGET="_top" TITLE="Learning to Draw"><U>Learning to Draw</U></A>   |   <A HREF="id39.htm" TARGET="_top" TITLE="Thesis on Tile Art"><U>Thesis on Tile Art</U></A>   |   <A HREF="id40.htm" TARGET="_top" TITLE="Tile Making with Photoshop 5"><U>Tile Making with Photoshop 5</U></A>   |   <A HREF="id41.htm" TARGET="_top" TITLE="V2 Tutorial"><U>V2 Tutorial</U></A>   |   <A HREF="id42.htm" TARGET="_top" TITLE="Collision Detection"><U>Collision Detection</U></A>   |   <A HREF="id43.htm" TARGET="_top" TITLE="DMA"><U>DMA</U></A>   |   <A HREF="id44.htm" TARGET="_top" TITLE="Working with Bits"><U>Working with Bits</U></A>   |   <A HREF="id45.htm" TARGET="_top" TITLE="Item DAT Files"><U>Item & DAT Files</U></A>   |   <A HREF="id46.htm" TARGET="_top" TITLE="Menu Making"><U>Menu Making</U></A>   |   <A HREF="id47.htm" TARGET="_top" TITLE="Reading From Files"><U>Reading From Files</U></A>   |   <A HREF="id48.htm" TARGET="_top" TITLE="Savegames"><U>Savegames</U></A>   |   <A HREF="id49.htm" TARGET="_top" TITLE="Entity Talking"><U>Entity Talking</U></A>   |   <A HREF="id57.htm" TARGET="_top" TITLE="Mordred Tutorial 1"><U>Mordred Tutorial 1</U></A>   |   <A HREF="id58.htm" TARGET="_top" TITLE="Mordred Tutorial 2"><U>Mordred Tutorial 2</U></A>   |   <A HREF="id59.htm" TARGET="_top" TITLE="Mordred Tutorial 3"><U>Mordred Tutorial 3</U></A>   |   <A HREF="id63.htm" TARGET="_top" TITLE="Hicolor Fades"><U>Hicolor Fades</U></A>   |   <A HREF="id65.htm" TARGET="_top" TITLE="Tiny Tutorial on Multidimentional Arrays"><U>Tiny Tutorial on Multidimentional Arrays</U></A>   |   <A HREF="id67.htm" TARGET="_top" TITLE="V2.7 B10 Python Commands"><U>V2.7 B10 Python Commands</U></A>   |   <A HREF="id80.htm" TARGET="_top" TITLE="Overkills Tutorial 1"><U>Overkill's Tutorial 1</U></A>   |   <A HREF="id81.htm" TARGET="_top" TITLE="Overkills Tutorial 2"><U>Overkill's Tutorial 2</U></A></div> <div> CHRs 2</div> <div> <B><U>What's a .chr?</U></B></div> <div> A .chr file (I hope you know this already) is a character file that contains the graphics for one character. Like, char.chr (which comes with ACE) contains the graphics for each and every frame of the tutorial character.</div> <div> Verge 1 .chr files are all the same (as far as I know)- 30 frames, 5 frames per row, 16x32 pixels per frame. Of course, you don't have to fill up each frame- all the extra (black) parts of the frame are transparent in the game.</div> <div> In Verge 2, you can make your .chr file however the hell you want. I'm going to go into a bit more detail as we continue.</div> <bR> <div> <B><U>Proggies</U></B></div> <div> <I>-pack-in stuff:</I> .chr programs that come with Verge 2</div> <div> <I>Chrmak</I>- The Character Maker. This generates a V2 .chr file from a properly formatted .pcx file of your character. For instance, if I was to take kain.pcx (a pcx file ripped shamelessly from Final Fantasy 4) and use chrmak, it would give me a very useable V2 .chr file. But, how do you use it?</div> <div> Okay, chrmak uses a .mak file type, which my copy of Visual C++ recognizes as a C++ makefile. Since I'm just a beginning super-newbie programmer, I didn't even know these existed. Oh well- this just means that if you have Visual Studio on your comp, you'll either have to change the file type or open these things manually.</div> <div> Anyway, a make file can be created and edited in any text editor (I use notepad, but if you like DOS you can use DOS Edit). The file tells chrmak how many frames your .chr will have, how big the frames are, what are your idle frames, and defines the movement scripts. There's also something called Hot Spots, which has to do with the size and such of your character. I don't fully understand it- maybe I'm just really stupid, but the readme that comes with it confuses me in this area. If anybody out there understands this and can write a tutorial for the average dummy, send it my way! For now, I'll just use the default values that the readme suggests.</div> <div> PCX format- if you make your own PCX from scratch, you will want to lay it on a solid black background, with each frame seperated by a one-pixel-thick border. Just open any .pcx character file and you'll see for yourself. But, don't forget to make each frame the same dimension. :)</div> <div> Here's an example make file:</div> <div> <B>//cecil.mak, makefile for cecil.chr</B></div> <div> <B>//Check this out- you can put comments in just like a vc file!</B></div> <div> <B>pcx_name=cecil; //The first line tells chrmak the name of the pcx file, and the second lists the chr_name=cecil; //name of the output file, that is the .chr file that will be created.</B></div> <div> <B>frame_w=16; //This is the width and height of each individual frame, in pixels.</B></div> <div> <B>frame_h=32; //16x32 is the standard V1 size, and you'll probably want to keep it this way.</B></div> <div> <B>hot_x=0; //here's that hotspot thing. Don't worry about this for right now.</B></div> <div> <B>hot_y=16;</B></div> <div> <B>hot_w=16;</B></div> <div> <B>hot_h=16;</B></div> <div> <B>per_row=5; //This tells chrmak how many frames are in each row, </B></div> <div> <B>total_frames=30; //And how many frames there are total.</B></div> <div> <B>lidle=10; //This says what frame number is shown when your dude is standing still, facing left.</B></div> <div> <B>ridle=15; //Ditto, but facing right.</B></div> <div> <B>uidle=5; //facing up</B></div> <div> <B>didle=0; //facing down</B></div> <div> <B>lscript=F10W10F11W10F12W10F11W10F10W10F13W10F14W10F13W10;</B></div> <div> <B>rscript=F15W10F16W10F17W10F16W10F15W10F18W10F19W10F18W10;</B></div> <div> <B>uscript=F5W10F6W10F7W10F6W10F5W10F8W10F9W10F8W10;</B></div> <div> <B>dscript=F0W10F1W10F2W10F1W10F0W10F3W10F4W10F3W10;</B></div> <div> <B>//these are all movement scripts. They'll be explained later.</B></div> <div> Note- I'm pretty sure you can put these things into whatever order you like, but I'm too lazy to check it out myself. Why don't you? :)</div> <div> Notice how, in the pcx_name and chr_name commands, no extension is neccessary. I dunno if it will give you an error or not, if you add one in. Next comes the dimensions (16x32 in this case). If you want some sort of gigantic entity, like 32x64, you can if you really want something that huge.</div> <div> Hotspots- like I said above, I don't understand it myself. Until I have one for you, just try and deciphr the chrmak readme.</div> <div> Actually making the .chr is very easy now. Go to DOS prompt, and type:</div> <div> chrmak cecil.mak</div> <div> After a few seconds, cecil.chr will be created from cecil.pcx, and you will be able to use him in your games! Do not forget that you have to include the path of the file if it's not in the same directory as chrmak. Go to DOS tips if you need some help.</div> <div> You want to do this yourself? Here is the cecil.pcx file to get started. Create the makefile (copy-paste if you so desire) but make sure you understand it all. Wasn't that easy? I thought so.</div> <div> Compared to Verge 1, this is much more complicated but certainly MUCH more powerful. Trust the FAQ, it tells the truth.</div> <div> <I>Chrconv-</I> This is a relief- after digesting that long chrmak tutorial, you can now relax. Chrconv is the simplest damn program in Verge (except maybe Verge.exe itself :)).</div> <div> Chrconv stands for Character Converter, and it converts character over from Verge 1 format to Verge 2 format. All you do is double click chrconv, and it'll prompt you for a .chr name. Enter <I>leo.chr</I>.</div> <div> And it will do it, almost instantaneously. Wasn't that easy? Leo.chr, btw, is a ripped FF6 sprite that I got in V1 format..</div> <bR> <div>  <A NAME="movement_scripts"><IMG BORDER="0" SRC="1x1.gif" HEIGHT="1" ALIGN="bottom" WIDTH="1" HSPACE="0" VSPACE="0" ></A><B><U>Movement Scripts</U></B></div> <div> Ah, they're not that hard.</div> <div> First of all, there's two types of scripts. One that's used in a .mak file to define a character's movement frames, and one that's used to actually move the character around. First, we'll look at the first type. Consider the following lines of code, from cecil.mak:</div> <div> <B>lscript=F10W10F11W10F12W10F11W10F10W10F13W10F14W10F13W10;</B></div> <div> <B>rscript=F15W10F16W10F17W10F16W10F15W10F18W10F19W10F18W10;</B></div> <div> <B>uscript=F5W10F6W10F7W10F6W10F5W10F8W10F9W10F8W10;</B></div> <div> <B>dscript=F0W10F1W10F2W10F1W10F0W10F3W10F4W10F3W10;</B></div> <div> Ugh. That's some pretty nasty crap. Let's look at 'dscript' first, simply because the numbers are smaller.</div> <div> In this type of script, the 'F' stands for 'Frame'. This is just what frame to show, not very difficult to understand here. The 'W' is 'wait', in number of ticks (100ths of a second). Therefore, W50 waits 50 ticks before going to the next frame, or a half second. You get the picture. Now, the 'dscript' thingy means 'down script', which is simply what direction this script refers to. I hope this isn't too hard to digest.</div> <div> The other type of script is the one that actually moves your little dude around. Consider the following:</div> <div> <B>entitymove(1,"R5U5L5D5W10F0W25F2W25F1W25F3Z25");</B></div> <div> Here's what this does. The entitymove function is used in map-based vc code (more on that in the map-based.vc section). The first number refers to what entity index to use, and the stuff in the quotatios is the script itself.</div> <div> And, here's how the script itself goes. 'R' just means move right X amount of spaces, in this case 5. L steps left, U steps up, etc. 'F', in this case, means 'face' rather that 'frame'. If you put F0, or face 0, you'll face direction 0, which is down. F1 is up, F2 is left, and F3 is right. 'W' just the same as before- wait the given number of ticks (hundredths of a second). 'Z' means to jump to a frame- in most cases, 25 is some sort of special frame, like surprise, or a death frame, or whatever- it's different for every chr.</div> <div> Now, if you have an entity with index 1, set to leo.chr, then that entity will walk the above script. More on implementing scripts will be in the map-stuff.vc section, and even a little bit in the MapEd section. Yeah, they're that important.</div> <bR> <div> <B><U>Newfangled .chr Editors</U></B></div> <div> <I>Winace beta-</I> Daniel Moquin's WinACE, the Windows version of ACE (real brainbuster there) will be an excellet .chr editor- once it's finished. For now, it can't load .chr's yet, just bmp's- but fear not, once that and movement scripting is enabled, this one will rock. Why? It's a Windows program.</div> <div> Oh, and the original DOS program, ACE, is V1 only- V2 .chr's will look real screwy. So, don't mess with it, unless you want to use Verge 1 for some reason.</div> <div> <I>V2 CHR Graphical Editor-</I> For now, I guess we'll have to use Brad Smith's excellent V2 CHR Editor :). No offense dude, but I'm switching to WinACE once it's finished :).</div> <div> This is <I>really</I> easy to use. You can probably learn it by playing with it for 5 minutes or reading the docs, whichever you like. Or you can read on.</div> <div> In order to load the chr, you gotta have it in the <I>same</I> directory as v2chr.exe.. Copy... oh... Leo.chr, the famous General Leo ripped from FF6 to your v2chredit folder and run v2chr.exe. You'll have the entire right half of the side basically empty, and the entire left side covered in menu choices like Save, Load, Close, etc. The first thing you want to do is load a chr- click load, and click on Leo.chr. Not too hard, I hope.</div> <div> Now, Leo appears in the editor. If you want to draw, you can click on the little colors in the bottom-left and have at it. But for now, let's look at Leo. First you'll notice the frame starting at you- frame 0, which is pretty much <I>always</I> the down-facing idle frame. Somewhere near the upper-left is an animation preview- click on it to change the view around, so you can see your dude in motion. Looks a little weird, eh? Yeah, it does. Leo seems to drag his feet around as he walks- all ripped FF6 chrs do, to my knowledge. We'll fix that in a minute.</div> <div> The left and right arrows around the button that says 'script' will shift through the frames one-by-one. Notice how frame 1 and 2 are identical, as well as 3 and 4. That's what's causing the drag. The default movement scripts (as I stated above) is 0-1-2-1-0-3-4-3. That means that when Leo walks, he'll go 0-1-2-1; now, 1 and 2 are the same frame, so it'll kind of drag along the ground. Right? Let's fix this.</div> <div> Now, click on that 'script' button. In the new window, click the left and right arrows to change to the four different views and their corresponding movement scripts. The proper script for a FF6 rip is 0-1-0-3-0-2-0-4, with a wait of 13 ticks between each page. For other views, you'll add five, ten, or fifteen to each value. For instance, when facing up, the idle frame is 5. So, you'll add 5 to each frame of the script for the correct 'up' script. Cool, huh?</div> <div> Once you've done that tedious work for all the views, you'll notice that Leo is suddenly walking smoothly. However, from the left and right views, he kind of looks like he has a limp- but don't worry, it looks normal in the game, and no other FF6 rips (as far as I know) look like this. Now, close the scripting window.</div> <div> See that number in the bottom-right corner? That's the zoom level. Right click it to go down (smaller) and left click it to go up (bigger). This is useful for coloring your dude- but, to be honest, I wouldn't recommend it. This program doesn't have either an undo button or a 'pick' button, so if you merely want to alter an existing chr, it is very difficult to find the proper colors. Okay, now save it (please don't make me explain this) and quit.</div> <div> Now, if you view leo.chr in the game, he'll look much more normal. No foot drag syndrome, no limp. If you need to know just <I>how</I> to view him, go to the map-stuff.vc section for some help.</div> <bR> <div>  <A NAME="making_ff3_style__chr_s__by_shadow64"><IMG BORDER="0" SRC="1x1.gif" HEIGHT="1" ALIGN="bottom" WIDTH="1" HSPACE="0" VSPACE="0" ></A><B><U>Making FF3-style .chr's: By Shadow64</U></B></div> <div> <B>************************************************************</B></div> <div> <B>Here is Shadow64's patented(?) way of doing FF style 3X4 chrs.</B></div> <bR> <div> <B>here is what the setup should be like</B></div> <bR> <div> <B>down frames 0 1 2</B></div> <div> <B>up frames 3 4 5</B></div> <div> <B>left frames 6 7 8</B></div> <div> <B>right frames 9 10 11</B></div> <div> <B>other 12 13 14</B></div> <div> <B>and so on..</B></div> <bR> <div> <B>here is what each should look like</B></div> <bR> <div> <B>down frames:</B></div> <bR> <div> <B>0 - chr is looking at the player in his/her stand still position</B></div> <div> <B>1 - chr is walking forward, his/her left foot (right foot to you) is out</B></div> <div> <B>2 - chr is walking forward, his/her right foot (left foot to you) is out</B></div> <bR> <div> <B>up frames:</B></div> <bR> <div> <B>3 - chr is looking in the opposite direction of the player in his/her stand still position</B></div> <div> <B>4 - chr is walking away, his/her right foot (both to you and him/her) is toward you</B></div> <div> <B>5 - chr is walking away, his/her left foot (both to you and him/her) is toward you</B></div> <bR> <div> <B>left frames:</B></div> <bR> <div> <B>6 - chr is looking to YOUR left in his/her stand still position</B></div> <div> <B>7 - chr is walking left, the foot that is farther away is out in front, the other is in back</B></div> <div> <B>8 - chr is walking left, the foot that is closer to you is out in front, the other is in back</B></div> <bR> <div> <B>right frames:</B></div> <bR> <div> <B>9 - chr is looking to YOUR right in his/her stand still position</B></div> <div> <B>10 - chr is walking right, the foot that is farther away is out in front, the other is in back</B></div> <div> <B>11 - chr is walking right, the foot that is closer to you is out in front, the other is in back</B></div> <bR> <bR> <div> <B>here is the default mak file.</B></div> <bR> <div> <B>pcx_name=default;</B></div> <div> <B>chr_name=default;</B></div> <div> <B>frame_w=16; /* this is the width of each frame, change it if needed */</B></div> <div> <B>frame_h=32; /* this is the height of each frame, change it if needed */</B></div> <div> <B>hot_x=0; /* the same goes for the hot spots */</B></div> <div> <B>hot_y=16;</B></div> <div> <B>hot_w=16;</B></div> <div> <B>hot_h=16;</B></div> <div> <B>per_row=3;</B></div> <div> <B>total_frames=12;</B></div> <div> <B>lidle=6;</B></div> <div> <B>ridle=9;</B></div> <div> <B>uidle=3;</B></div> <div> <B>didle=0;</B></div> <div> <B>lscript=F6W20F7W20F6W20F8W20; /* to speed up/slow down the animation decrease/increase the number after each W */</B></div> <div> <B>rscript=F9W20F10W20F9W20F11W20;</B></div> <div> <B>uscript=F3W20F4W20F3W20F5W20;</B></div> <div> <B>dscript=F0W20F1W20F0W20F2W20;</B></div> <bR> <bR> <div> <B>----------------------------------------------------------</B></div> <div> <B>That is all, just follow these rules, if you have any problems ask me, Shadow64</B></div> <bR> <div> <A HREF="mailto:shadow64@geocities.com" TARGET="_top" TITLE="mailto:shadow64@geocities.com"><U><B><U>shadow64@geocities.com</U></B></U></A></div> <div> <B>******************************************************</B></div> <bR> <div>  <A NAME="hot_spots_in__chr_s__by_jenria"><IMG BORDER="0" SRC="1x1.gif" HEIGHT="1" ALIGN="bottom" WIDTH="1" HSPACE="0" VSPACE="0" ></A><B><U>Hot Spots in .chr's: By Jenria</U></B></div> <div> <B>******************************************************</B></div> <div> <B>The trick, I believe, is to remember you're dealing with a two-dimensional world. We use pretty graphics to fool our eyes into seeing three dimensions, but really it's just a bunch of tiles lying flat along a map layer. It's like drawing a picture on a table. Your characters exist *above* the table, not in it. </B></div> <div> <B>Imagine your character is a flat sheet of paper that's 16x32 (the default size) with your character drawn on it. You want to to move that piece of paper along a flat surface, the map, or table. Let's say you want to move it to the center of the table, (0,0). You can only use one finger to move the paper, and at the end of the move, your finger will be over (0,0). The question is: where do you place the finger on the paper? Do you put your finger in the center, or move it via a corner?</B></div> <div> <B>The "hotspot" is where you place your finger while moving the paper. If the hotspot's in the head of your character, that's where Verge will move it. The *head* of your character will be over (0,0), because that's where you'll move your finger. If the hotspot's near the feet, then the *feet* of your character will be over (0,0). The default spot I believe is the left center edge of the character (That's (0,16) on the character picture, NOT the map!).</B></div> <div> <B>The obsctruction zone's a little harder to explain. You got to remember again that everything's two-dimensional. The simplest way to say it is the obstrustion zone should cover anywhere on your character picture where your character's SUPPOSED TO BE TOUCH THE GROUND. Your head does not touch the ground, so don't obstruct it. Your torso does not touch the ground, so don't obtruct it. You feet *do* touch the ground, so obstruct that area of the picture.</B></div> <div> <B>This is useful, because if you have a character that walks, all you have to do is obstruct the feet portion of its picture. However, if you have a character that's crawling, there's a lot more ground area to cover (Your hands touch the ground when you crawl) than someone standing straight up.</B></div> <div> <B>Well, I hope that helps some, and that I'm not wrong.</B></div> <div> <B>~</B><FONT SIZE="3" COLOR="#0000FF" FACE="Arial Narrow" ><A HREF="mailto:jenria@yahoo.com" TARGET="_top" TITLE="mailto:jenria@yahoo.com"><U><B><U>Jenria</U></B></U></A></FONT><B>, wannabe programmer.</B></div> <div> <B>*****************************************************</B></div> <bR> </td> </tr></table></body>