Amiga ISO Collection

home *** CD-ROM | disk | FTP | other *** search

/ Amiga ISO Collection / AmigaDemoCD2.iso / ASCII / TEXTE / SCENE / HPA / HACKING / HowToRipII.doc.pp / HowToRipII.doc

Wrap

Text File | 1994-11-28 | 32.3 KB | 614 lines

MODULE RIPPING FOR PROFESSIONALS II - WRITTEN BY DIGIT/DMX THIS FILE IS COPYRIGHTED BY DIMESION X COPYRIGHT ©1993/94/95 DMX YOU ARE ADVISED TO READ THE NOTICES BEFORE THE ACTUAL DOCUMENTATION __________________________________________________________________________ __________________________________________________________________________ INTRODUCTION ~~~~~~~~~~~~ Well I once wrote a quick document on how to rip modules using various methods but they were only looking for mainly Tracker modules. In this document I will hope to cover all aspects of module ripping so even the un-experienced among you will become semi-pro`s! I will not be giving or telling any information that I would like to keep to myself because there are just somethings that are too good to tell about! REPRODUCTION NOTICE! ~~~~~~~~~~~~~~~~~~~~ The following information can be re-used as long as the wording is not like mine in any way and that only this information can be spread by either word of mouth or by this text file. This text file must remain in it`s whole form and entirety. Broadcasting of this document by radio or television is prohibited in any country of the world, this also includes HAM radio transfers, CB`s. The spreading of this document can be done by either post or by modem transfers ONLY! HEALTH WARNING ~~~~~~~~~~~~~~ I am in no-way responsible for the loss or destruction of any data that you may encounter by following or using the information provided in the document. You will be doing it at your own risk. Any breech of copyright by following a method(s) in this document is entirly your own risk, I do not condone or encourage users to break or breech any copyright law(s). Variations of this may depend upon the country you are in and their own laws on copyright. __________________________________________________________________________ __________________________________________________________________________ PART ONE - DESCRIPTION OF VARIOUS RIPPERS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To rip a module you need some tools, I mean what is a plummer or electrician without any tools? Useless? There are many rippers available in either the PD libraries or commercial software. My best advice is to get rippers that are PD - why? Well because they are mainly written by scene freaks who know what you the hacker wants, okay that`s not really fair to say that not all module ripper coders are doing illegal things but they generally know what you would like to rip and the best ways to go about such tasks. To choose a decent ripper can be very daunting especially if you are just starting out. There are thousands of rippers, some are single rippers which only search for particular formats or there are the multi rippers! These are the best tools because not every one can be sure of what format the module they are going to rip is in especially when you are not an owner of an Action Replay (like myself!). The best rippers to look out for are the multi rippers. The main ones that I use are "The Exotic Ripper" and "Multi-Ripper", the greater the version number the better the rippers of these rippers are. Of course I have the latest but you cannot always be sure that these rippers can detect the module you are looking for but don`t worry about this at the moment as we will be leading astray. The reasons why I use two rippers and not one is because each ripper can do slightly different things. For example Multi-Ripper can search for crunched information in memory which is a very exellent tool for non-DOS disks while poor old Exotic cannot! I will be mainly using these two rippers when describing any ripping so I advise you to lay your hands on these but if you can`t then don`t dispare because there may be various commands in your ripper that do the function that I may be discribing. If you are a lucky owner of an Action Replay then you may have an advantage over the less fortunate, but for those that have not don`t despair because I have`nt got one and you can just follow me! Theres really nothing special about the Action Replay`s ripping function and it`s vertually shit anyway because it can hardly detect a module if you told it where it exactly is! It`s deaf, blind and dumb! The real advantage of an Action Replay is that you can access the memory directly into a running program without having to reset and so you are able to save the memory to disk to be sure of a better rip! NOTICE ~~~~~~ You are advised to read any and all documentation about your own tool to understand and help you if you suddenly become stuck or you come across a problem. Even better I would print the documentation out to be on the safe side, just incase you forgot or something! __________________________________________________________________________ __________________________________________________________________________ PART TWO - INFORMATION! ~~~~~~~~~~~~~~~~~~~~~~~ "Information", with out it we are virtually gonners thats why it`s best to understand about the disk format, it`s producers and it`s protection! To understand what I mean the following information should tell you. FORMAT - No it`s not the `Format', `Format', it`s the `Disk Format' or in better terminology the disk structure. It`s no good diving in the middle of ripping without knowing the fogist about your disk because the module may just be located on a bog standard DOS disk. So what would be the point of hacking into the program, disassembling the disk just to find sod all? There are two type`s of disk formats: `DOS' and `Non-DOS' Dos disks can be viewed by typing `DIR' on your Workbench disk, this will list all the files on the disk. You never know you might find the file `MOD.???' or `SOMEBODYS MODULE!' so all the ripping is`nt necessary just load the file up into the module player! Non-DOS disks cannot be viewed by using DIR because not only is the checksum on the root block (sector 880 or track 40) abnormal but the file headers will be non-existant and files can be spread far and wide so recovery of the files is very hard indeed - but not impossible! There are some good books that can tell you more about these disks if you want to know more about the format of a disk. The Amiga-DOS manual may give some information about them but I`m not sure?! PRODUCERS - Some producers re-use the same stuff over and over again, ie the same type of modules in their productions. If you research some producers or you have gathered information up over the years you may notice that it never changes so you know what module format you are looking for. Be-sure though because you never know when they might suddenly decide to change, I cannot promise everything! PROTECTION - It`s no good checking a disk if it`s protected because the information on either DOS or Non-DOS will be hidden from prying eyes like yourself so that they cannot duplicate the software or information. Of course we all know about hackers (do we?) so you may be fortunate to get a hacked copy that allows you to read the information on the disk. Action Replays can just ignore the protection and just load the software and save the memory to a disk then search, simple as that! If you cannot do either ways you could always hack it to pieces! Hint try disassembling the bootlock and then the first one or two tracks of information before the software loads to learn about the protection routine! __________________________________________________________________________ __________________________________________________________________________ PART THREE - GETTING YOUR HANDS DIRTY! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ METHOD 1 ~~~~~~~~ Once you have found out what the disk is like you should really start to think about ripping the module(s) from the disk. The best method and the one I always like to use where possible is to save all the programs information onto disk, ie using the Action Replay. Okay I know I have said I don`t have one but there are some tools that act like an Action Replay. Because I am the owner of an A1200 I am able to take advantage of the A1200 Action Replay (Version IV) which was made by Blackhawk. It`s a fairly good tool because it is more user friendly but some of the best functions tend not to work or not 100%, I suppose that`s the price you have to pay though! The other tool that can be used is Memwatch. This is a fairly unknown program because a lot of guys I know that collect tools such as this did not know about it until I sent them it. It`s a fairly good tool and works 100% on my A1200 but the lack of functions can get fairly anoying. But it`s main function is the ability to view your memory, disassemble/assemble, save, load, etc. You may have noticed that these two tools are all files and are not hardware add-ons so sometimes these tools might not get into the program because they will be destroyed on boot-up! There are some ways on how to get around this but they will be told later on in this file. One method though is to link up two Amiga`s where ever possible. There are some programs that have been produced to actually look at it`s linked brother`s memory and so you are able to save it to disk. This is a good method but the hardware and software really need to be bought because it give`s a good description on the perfect setup in the documentation. Another reason is making the hardware is not an easy task. All the decent hackers out there should already have a setup like this (Nomad, Blackhawk, Phil Duncan etc. etc.?) so if you know them why not pop around to their house? (Hi Charly!). Well the actual ripping process is very easy indeed with this method, only if the module is a known one but if it is not then you will have to disassemble the play routine or if possible get the play routine. The disassembling side will be covered later on in this file so try not to worry to much about it. If you have problems using this method try some of the ones below because you may or may not be doing it right or the actual program could be causing some kind of fault with the module so that you cannot detect. I have not come across this yet but I have been told it has been done and is possible! Okay lets get on with the ripping. Once the program has loaded and the music that you want to rip is playing enter the Action Replay or whatever method of tool you are using to access the memory, hopefully your tool will tell you how to access this in it`s documentation! Memory is a funny thing to beginners because they do not understand it that`s why I may say some stupid things from now on which may seem funny to the more experienced users among you, so just ingore it! Before you actually save the memory you are best to have a formatted disk on hand so if you have not then hopefully your tool should carry a 'Format' function (not the disk structure!) so format one, if not reset and get one. If you are lucky in two cases you may have a hard drive and your tool may take advantage of it so use that if possible to save the memory to. Now we will really begin work. It`s best to seperate the memory especially if you have a memory upgrade of more than half a meg so that you have more than one meg. You should know that you should only really save the first one meg of memory to a normal disk so if you have four meg or more you should have four blank disks or do this in four steps? Your choice, I just find it easier to work out in one meg chunks. It`s best that you know where the module lies because if you save some memory, lets say from address $0 to $80000 when you come to search the memory for a module it may be found at something like $70000 and may end at $90000. So when you come to search you will find the module, mainly the pattern data but half if not all the samples will be missing but this depends upon the module format. If this happens then save the memory where you found the module and then where it ends, if you don`t know that just save a meg of the memory. If your not sure what kind of format you should save the memory in especially if you are using an Action Replay then it`s the SM command or just data format. You do not want to be saving in 'DC.B', 'ASCII' or any shit of that sort, try to use your head but if your having trouble with that then read the documentation on the tool! Once the memory has been saved load your ripper in, as usual load it low so that you can load your saved file. While I remember to tell you have you made any allowances for the size of the ripper? If you have one meg and saved it all then how do you expect to load the saved file and the ripper into your RAM at the same time? Duh! Okay set the ripper to search at the address where the file was loaded to where it ends, now hunt. If your lucky it will be there if not then that`s one of the best chances of finding it gone! METHOD TWO ~~~~~~~~~~ Now we start with one of the easiest methods ever. Once the music has loaded up in the program reset and then load up your ripper. Once the ripper has loaded just hunt through memory and if the program does not make a hard reset you should be able to find the module. One warning when using this method. Be sure that you do not write over the module when loading up the ripper because some tricky coders save the module very low in memory so that they have a higher chance of being destroyed on boot up or during a reset! Just a hint I think I will add here, it`s nothing new and it`s fairly uncommon practic by lots of rippers but it really tends to work! Once the program with the music has loaded if possible try to make the machine crash eg. by removing the disk while loading but make sure the music is playing so you know it is`nt terminated when it access the disk. When the guru meditation comes up just click it away, load your ripper, hunt and if by chance it will be found - did it? METHOD THREE ~~~~~~~~~~~~ You might not be able to rip the module by using the two methods above so you might be lucky enough to hold a disk that can be ripped using this method. Load your ripper up, if you are short of memory load it low down in your RAM but not too low as to crash your machine about $20000 to $30000 so that you will be able to load the whole of the disk with the module on into memory. Well load the disk into RAM but do not write it over the ripper, try to leave a minimum of 100 bytes between the ripper and the disk load so that any of the rippers data is`nt accidentally destroyed because of bad allocation. Some rippers tell you where they are in RAM upon boot up but you do not know if the programmer is right or not - do you? Again have you made allowances for your ripper? You can`t load a whole disk and your ripper in half or one meg machines at the same time so you may have to read the disk in different portions. Once that is done just search through the memory where the disk was loaded into RAM, hopefully it should be there but....... METHOD FOUR ~~~~~~~~~~~ The fourth method is the most hardest and very hard to explain to the beginner. I will not be going into any grate detail because it could and would take me weeks to write out everything. So what is this so-called method four? Well most of you may already know but for those people that don't it's called "Disassembling", yep it's the opposite from "Assemble" and yes it does require knowledge of 68*** programming. I will not be going through any particular concept of disassembling but I will hopefully give you the main idea or 'gag' as to how to go about it. Before we begin though I really recommended that those guys who do not know how to code not to continue reading this method because you will not be able to implement it properly. For this method you will need some tools for disassembling, if you have the Action Replay you could do it that way but you will not be able to actually save it to disk as disassembled code so you would have to write it all out and then pump it all back into your assembler and edit it where necessary. The other tool for disassembling that I recommend is ReSource because it is a >VERY< powerful and easily the best disassembler I have ever laid my hands on. So if you have £100 lying about buy it! If you don't have either of the two you will have to find some P.D. or cheap commercial disassembler. I know of tools that disassemble but I don't know of any P.D. or cheap disassemblers that save the code to disk so you will have to look around - sorry! So where do we begin? Well if you have been doing your homework you could do it roughly two places - disassembling that is! So lets begin the two ways, simple and short! Oh yes while I remember for all you smart arses out there, there are other ways of doing it like this but these are the two best ways I think of getting a module this way. 1) The long way as I like to think it, but sometimes it is necessary to do it this way as you will shortly see. Firstly you will have to begin at the boot block to discover where all the data is being loaded from the tracks. ReSource will load the bootblock and disassemble it if you wish or you could use your Action Replay by loading in the bootblock and then disassembling the memory from where the track was loaded. The other way is to actually run the bootblock and then enter AR and disassemble it. Once that is done you should discover from this information where the data is being loaded so you are advised to load this data up ie read the tracks into memory. Note that if the data is crunched you will need to decrunch it either with a decruncher or with the actual crunch header. There are some decrunchers that will read tracks and if they know the decrunch header they will decrunch it, or else you will have to read the whole of the load data into RAM, save it to disk, load your decruncher then load the saved file. When thats done disassemble the loaded data, if it is a big file then you ReSource guys are going to need PLENTY of memory. Well if this file does not load other tracks from the disk ie. the module you are looking for then you are okay but if not you will have to look through all the code and follow it through until you find out what tracks, etc. So what are we looking for then? You are looking for an unknown module right? So you should be looking for data of that sort, this is where it can get very time consuming........! When you have found it you should save the replayer code to disk and then load up your assembler. Most assemblers will not like a lot of code so if your not a good coder like myself (he, he!) you will have to let someone else edit the bits you cannot do. This also takes time. All that is left now is to use this information to either hunt for the module or use it to play the module so it usually needs a bit of faffing about to get it going. Sometimes you may end up with the replayer code right infront of the actual module data so you should be careful what you are disassembling as you do not want to be mucking about figuring out what the fucks going on only to later find it's the module! 2) The second method needs an Action Replay or the soft kicking version etc. What is envolved with this method is like the one above except that all you have to do is run the program until the module is playing, enter your Action Replay. Once that is done you can save the memory to disk and then disassemble it or you can search for the module itself along with the play routine, and disassemble it on the spot then save the module to disk or save them all and the disassemble it with ReSource? _________________________________________________________________________ _________________________________________________________________________ WHAT DO I DO IF I WANT PROTRACKER FORMAT? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ So you have got a module from a music disk, game etc. using one of the above methods, right? And you would like (if possible) to translate the ripped tunes format back into Tracker so that you can load it up into ProTracker, SoundTracker etc. Before we begin I must say to you that it is impossible to do a straight translation with lots of module formats back into Tracker, so for these you would have to take the samples and reconstruct the module itself totally. But for the modules that can ........ Lets take into account what kind of module it is, ProRunner, HanniTracker, Kris, GP Tracker, Deep Tracker, Silents Tracker etc. but what ever kind of module that can be converted it was an original Tracker - "Spin Off", ie. it was originally a Tracker module but it has been converted to another format to help protect it from being ripped. All Tracker spin-offs can be reconverted back to ProTracker format with or without a lot of hassle. However or which ever way you wish to convert it is up to you. There are a few tools knocking about that will convert various module formats back to Tracker again and I recommend you use these because you would have to edit the actual code which converted it in the first place to reconstruct it back into Tracker. This is not my main subject, I mainly rely on various tools unless it is REALLY necessary. Tools that you should look out for to convert various formats are Perverter, Wizard Tool, Silents Converter, Hanni-Con and various other converters. If you notice two of the mentioned converters only convert that particular format while the first two convert various module types. Again these are the best tools to get unless necessary because you might not know the module format you have got to convert unless you have ripped it yourself and then you should know what format it is in! There is not much more I can say to you in this department but my best advice is to go and search out in the battle field for various tools, there are at least two more other kinds of multi-format converters like Perverter but I have forgotten their names. As usual the best places to look for these are on one of the NET's or through the modem scene. Most P.D. Boards sysops should be glad to help you find what you want. And for all those that can't ...... what's the point in converting them? If you have DeliTracker or EagleTracker and nearly two megs of play - routines to use (just about every format in exsistance) then there really is no need to convert them unless you are really desperate - is there?! _________________________________________________________________________ _________________________________________________________________________ HINTS AND TIPS (IF YOU REALLY NEED THEM..!) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1) How to get into a program with softkicking software instead of the hardware version ie. the Action Replay keeps on getting killed when the main program is booted up. Sometimes you can get around this by switching part of your memory off, ie one meg. Now load your tool up into the memory you have just switched off. If it does not try to detect the memory before it writes to it it should install itself okay. Now run your program and if it does not kill resident programs ie. tools that use the coolcapture (most programs use it just like virus's do) but detects for resident programs in RAM it should not detect it because your RAM with the tool in is switched off (supposedly). 2) Try this other tip for softkicking tools, try to use Fake Fast Mem, Degrader etc. to kid programs and make sure your tool is allocated in this area, it ocassionally works. If all else fails why not buy some hardware. 3) A lot of programs automatically detect for an Action Replay call ie. when you enter it so that it crashes or runs another sub program and locks it out. To get around this use two computers and link them up, as I have stated earlier in this document. Boot the game, demo or whatever from one machine and use a tool on the other machine to save the other computers memory. This is a good method which a lot of good hackers tend to use (if you wanted to know ........?). 4) If you are just starting out ripping try not to go for the harder rips that are too complicated. Go for things that you all ready know about ie. modules that somebody has already ripped because they should give you details on what they did, especially the format. Try to go for ProRunner and other Tracker spin-offs first. Don't jump into the deep end because you will never get the module as quickly as you would if you built up gradually over a period of time. Don't go trying to rip TFMX modules straight away ........ FOOOOOOOOLLLLLLLL! 5) If you are a coder and you discover a new module player routine which you have disassembled then why not try to write a program that detects these formats for future ripping. Also you could edit the replayer to run with DeliTracker, EagleTracker or your own specific module player as this will all save time and effort in future. Over a period of time you never know, you might get a very good collection of formats that you could use to write a ripper, module player ..... who knows? 6) Even if you run out of modules to rip go back to them again and try to rip them a different way because you never know when you may have to use a different method than the one you genrally use. 7) If you are writing a demo, game etc why not try to take the points above in hand to write your own replayer so that it would be harder to rip (it's more fun for me....!). But remember nothing is impossible to rip even encrypte modules, self verifying mods, and modules that randomly change on each boot up, remember as long as you have a replayer you will always be able to rip it no matter how you try to protect the code ie. checksums etc. .......! So don't be peed off when you see your module a day or so after the programs release. 8) You will definatly come across a problem some time or another so why not ask for help (hello Lee!) as it happens to everyone sometime or another and watch what the person does and how they go about doing it. Lots of guys try to rip modules they can't and if they cannot they rip other people off and claim it for themselves, but that's another story. We all know about these people and what do people call them LA**** ....? _________________________________________________________________________ _________________________________________________________________________ THE END PART (CRY, CRY) ~~~~~~~~~~~~~~~~~~~~~~~ Thankyou for taking an interest in this file, it was fairly quickly done so spelling and grammer may be a lot to desire but I have not spell checked it or anything, I think my English is good enough - to read? (no comments!) Well this is the update of the first version of this ripping document. Again the spelling and grammer may be a lot to desire but I have done my best by correcting the obvious mistakes and sentence structures. As it's getting late (later!) there is more chance for me to make some mistaeds! When I'm bored one night I may do some thorough spell and grammer checking myself or I might give it a good run through with a Text Editor. If you did find it enjoyable then why not contact the author of this file by sending in any modules, DeliTracker players, ripper updates (Exotic!), money (sterling), just letters of thanx, swapping, Dance & Hardcore, VHS videos, etc, etc, etc......... I'm also very interested in people that would like to critisise this file I'm not saying I am the best module ripper because I know I am not and some of the points above may not be as strongly and cleanly understood as you would like but this is just for general interest. I do it when I am bored or when I set myself a challenge or just when I like a module. All this information was gathered over a period of time and experience. So I would like to thank all the guys that have helped me out in the past with software, hardware, comments, ideas etc. You all know who you are because you are my closest friends, no more said then. _________________________________________________________________________ _________________________________________________________________________ AND AGAIN, AND AGAIN ........ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I am in no-way responsible for any damages software, hardware orientated when following or implimenting one or more of the above methods. I do not condone that you could do them 100% first time, how long it takes you depends on yourself. I am in no-way condoning or encouraging piracy or theft of a product when following a method above. What you do is your own interest I am in no-way responsible for YOUR OWN actions, there are TITS and there are DICKS your either one or both of them (we all are sometime). So if you think this is a ridiculous file that is encouraging piracy (TIM) then your daft, if guys can legally write and distribute books that show you how to make and design your own bombs, rockets etc. then your a fool. Why encourage terrorists? PLEASE READ THE BEGINNING OF THE FILE FOR FULL COPYRIGHT, SPREADING, AND THE USE OF THIS FILE, ETC. _________________________________________________________________________ _________________________________________________________________________ HELLO'S GREETS ETC, ETC, TYPE THING ....... ! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I would just like to say some Hi-Ho`s to all my mates:- R-9/DMX, PAZZA/LSD, JINX/NBA, QUACKERS/DMX, AMMO/SLP, ABH/SR, NEXUS, SAREK, WIDDY, JADE, QUEST, MARK, SPECTRE, MIXMASTER, ODDJOB, NOMAD/FLT, FLYGARIC/EXODUS, CYLON/DMX, NEOTRONIC/DMX, SLIDER, HAWK, YVES, SPY, LUARENT, ELIZABETH, DAVE, LAZZER/PSX, RATTIE, ELRIC, DENZIL/LSD, MJM/FLT, ARNAR, PHIL '94/95!, SARACEN/BANANA DEZIGN, COLOURBIRD/RAZOR 1911, SPLATT/FLT, HAWKEYE/KEFRENS, FIREFLY/DMX, KEVIN, FACET/SPACEBALLS, HOLLYWOOD, CHAZYB/CBD, ZADD/DMX! AND A SPECIAL THANKS TO KRUSHER! FOR ALL HIS TIME AND EFFORT WITH ME ON HIS BOARD - MOSTLY HARMLESS. THANKS MATE! AND TO THESE COOL DUDES - ONLY! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PHIL'94 - Thanks a lot mate for all the help with my coding (snigger), I hope you read the file all the way through so that when you come to coding another brilliant game you can protect your modules better from MR PIRATE! Keep up the worlds best letters! MIXMASTER - Thanx for the calls, the video, your time etc, etc. I'm glad the DJ'ing is still going well and I'm looking forward to your arrival at my place next Sunday (PARTY-TIME!) No more said .......... DENZIL - It's nice to know you trust me! Thanx for that large send, you held the record for one day! Sad is'nt it because the next day I got a jiffy with twice more! Good going though! Oh yeah I put as much as you did on the jiffy with at least another 50p so I would sort MR POSTMAN! LAZZER - Love the sends, that code was great but it must have been leaked pretty well and I was pretty stunned when I saw those mighty giants work fully assembled and executable. I'm still in shhhhhhhoooooockkkkkkk! I took a stroll through some of the routines - WHAT?! EEEEEEKKKKKKK! NEOTRONIC - Still no hope with the CD's? Short of money was what he said but I suspect he believes you as much as you believe him! He's not showing it but I know him, now wheres my wallet gone? ..... QUACKERS - Money, money, money! It's time you forgot about all that shit and got yourself sorted out with some proper coding! Sod the £1000 get back into the scene and lets see some of those long over due promised effects! CYLON - Long and over due, eh? (sounds more like my library books!). Well as you have seen I'm still coding DOS tools, not so well! Hey we all start everywhere, er somewhere! I'll shortly be starting a little intro and the effects & piccies for Retina Burn II look er, you will see GREAT! MASTER BATES - Hardware, what hardware? CD's Hmmmm? Maybe sometime but not with my budget as it's slightly a little slim! CHAZYB - My first scene buddy! I'm glad things are slightly cooking in CyberDreams these days, it's about time you got recognised so I hope it all goes well for you in the future of CyberDreams! It's also nice to see you are moving up in the world by taking some paddles in other areas - GOOD LUCK MATE! _________________________________________________________________________ _________________________________________________________________________ AUTHORS ADDRESS SO WRITE! ~~~~~~~~~~~~~~~~~~~~~~~~~ DIGIT/DMX - 2 BIDEFORD AVE, BLACKPOOL, LANCS, FY3 8PU, ENGLAND. OR LEAVE ME MAIL ON - MOSTLY HARMLESS / DIMENSION X *** +44(0) 705 614824 *** COOL RATIOS, COOL FILES, COOL SYSOPS, FRIENDLY SERVICE, BRILLIANT. HOW? - BECAUSE IT's 100% AMIGA - SIMPLE & TRUE!