Version 3.2a last revised on 06/14/2002. Any comments or suggestions please direct them to Vorlon001. I can be found at the DSSUNDERGROUND , Innermatrix, DSSReload, or DSSGroundzero DSS Sites.
Guide is maintained and hosted by The Vorlon Homeworld. Linking to this guide is
ok, however anyone interested in hosting this guide must first contact Vorlon001
READ, VERY IMPORTANT:
use, possession or importation of Test (Programmed/Pirate) Cards is Illegal in
the United States. If you are a U.S. resident, you are required by law to
subscribe and use of Test Cards of any kind is unlawful and subject to Criminal
and Civil penalties according to U.S. law. We do not condone use of Test Cards
to U.S. residents. You and you alone are SOLELY responsible for abiding by the
laws of your Country, State, Province or Territory. THE DSS UNDERGROUND, HITEC
SATELLITE, DSSTECH, and THE VORLON HOMEWORLD WILL NOT BE HELD RESPONSIBLE FOR
THE ACTIONS OF THE PEOPLE USING THIS DOCUMENT. This Guide is strictly for Canada
and EDUCATIONAL USE ONLY. Also the DSS Underground, Hitec
Satellite, DSS Tech, and The Vorlon Homeworld
does not and will not take any responsibility for what might happen to any card
using the following procedures. In other words, USE
THIS GUIDE AT YOUR OWN RISK.
So with that out of the way let us say that what we are trying to offer here is a basic and simple instruction that hopefully will make everything as easy for you as possible. We also want these instructions as safe as possible, meaning we want to try our best to avoid having your card become damaged. But remember nothing is absolutely foolproof and donít let anybody ever tell you differently. There is always a risk taken whenever you attempt to clean an HU card. But also at the same time if you follow certain precautions you can lower those risks and that is what we have tried to do with this guide. But sometimes people, when they run into an error or when they get confused about what they are doing, will guess or attempt to try things on their own resulting in creating possibly a more serious problem. If during any of the following instructions you should get any kind of error message or if you become confused and donít understand something stop immediately, make note of any on screen message(s) and then go to your favorite Forum Site and seek out advice. Usually there is always somebody online that will be more than glad to help you out. If you do need to seek out help again please be specific when posting your problem and also give as much detail as possible.
Part 1 will cover program configuration and it's use. 06/12/02 for ver.3.2a
Part 2 will cover the basic program, itself. 06/12/02 for ver. 3.2a
Part 3 will cover the .hex creator part of the program. 06/12/02 for 1.74 to 3.2a inclusive.
Part 4 will cover ExtremeHU Unlooping with ver. 3.2a. 06/14/02
Since ExtremeHU3.2a is based, primarily, on the UL4S Atmel code, we will start there. We will assume that you have a looped HU card and have selected the Medical Icon on the toolbar. You will be prompted to insert your card. If the card has a glitchable ATR, you will get the following prompt.
Clicking on yes will bring up a second warning screen.
At this point you can abort by hitting yes or continue by hitting no. You get one more warning!
Yes will continue or no will abort. Hitting Yes will bring up the UL4S settings screen. From this screen you can set your functions the same as if you use the settings feature of ExtremeHU.
If you have never unlooped before or have never set or checked the auto update custom box, you should probably select the Standard range from the range settings box pictured below. In the Standard and 3 Alternative ranges, you cannot change any of the settings in the range boxes. These can be manually changed in the Custom settings selections and can be saved for future use. You can set which custom setting you wish to have the program auto update if you check that box.
If you have tried the Standard range without results, go through the Alternative settings. One of those should work. Later, you can use the updated custom settings and get faster program results or you can manually enter settings that were suggested on one of the forums.
With your range setting selected, on the bottom of the screen, click on Start Unlooping and the process will begin. ExtremeHU3.2a will reset the loader, display the Atmel code, display the setting used, and start glitching for an ATR response. At any time, you can click on the Stop Glitching box to stop the process. Note that starting with version 3.2 of ExtremeHU, even the UL4S unlooping will FF the card before starting the unlooping process. This was done because it often makes it easier to unloop the card if it is FF'ed.
When an ATR is acquired, the program will attempt to load a bootstrap. Some form of ATR will be displayed. It may only be 00 (last byte of ATR) or it may consist of a few more digits. The number of attempts and elapsed time will be displayed.
The window below, shows a different ATR response but you are told you have one and the bootstrap will attempt to be loaded.
When the bootstrap loads, a window will pop up asking you to select your repair bin for repairing the card. Select the bin you wish to use and click on open.
The Message Window will then appear as below. It indicates that the bootstrap is active and will show you the progress as the card is being written to. DO NOT REMOVE A CARD WHILE THE BOOTSTRAP ACTIVE INDICATOR IS PRESENT.
When the process is complete, ExtremeHU will appear as below: The ATR will be shown, the time it took, and the settings used by the program. If your update check box was checked, the custom settings of the program will be updated.
This guide cannot provide you with all of the answers. The reason is because the Unlooping process is very loader dependent. Any successful settings will most often be useful, only on that specific loader. This is called TESTING!
While the UL4S Atmel code is probably best for the casual person to use for occasional unlooping, ExtremeHU also contains the ability to use the HUFF code introduced by Unatester. In many respects, if you know how to use it, this code can be used to advantage as it is often much faster in unlooping, especially if you are familiar with the settings that work best for your loader. If you have a HUFF Atmel inserted, the repair icon will bring up the following screen. (You get the same 3 warnings as UL4S if the card has an ATR).
The Huff selection screen has all of the settings that are available on a pull down. Also, all settings of the program can be edited and saved. I suggest that you make only one change in the settings to start with and that is to change Max DAC2 Start to E0. This often yields faster results. In the program, the Max DAC1 setting is set to 60. You will find that most loaders start catching an ATR at a higher value. When you find you loader point, change this value to the point that ATR's start catching. This may be something like 74, 84, 88, or even A0. Once set, the program will unloop faster.
Since I most often use setting (3), I will select this from the pull down box above. This will select this glitch. If this one works for you, you will probably find that 4, 7, 8, & 9 will also work well. If not, start with the default settings boxes on the right side of the HUFF settings screen. With glitch (3) selected, click on Start Unlooping and the Message window will appear as below. The Min dac1 that you should watch for is displayed as 74 below. Remember, the card will be FF'ed first.
As soon as an ATR catches the program will attempt to load a bootloader. As soon as the bootloader is activated, your bin selection screen will appear. Select your repair bin that you want to use.
The screen will indicate the bootloader has been loaded as below, just like in UL4S. The Progress bar will indicate the Eeprom write in progress. DO NOT REMOVE A CARD WHILE THE BOOTSTRAP ACTIVE INDICATOR IS PRESENT.
When the write is complete, the Message Window will appear as below. The successful settings will be shown. You can use these settings to alter the setup paramaters of the program for your loader.
When using HUFF, I can give you a few hints. ExtremeHU gives slightly different responses in the message window than the script version does. Because of this, watch the ATR: reading. If there is nothing there and it changes to FF, it is at this DAC point you are starting to get a response. The DAC1 setting can be set to this point.
If you set the DAC1 setting too close to the actual result..... as in the last screen shot above 82, the glitch may miss and not catch at all. You should always set this value a little lower than the actual result. In the above case I would use a range of 78 to 7C for the setting.
I would like to thank Unatester, no1b4me, Extreme, the usual greats ...... RAM9999, AOL6945, Clipgrp, and all the others, for their forum input on HU Unlooping and their help in making all of this work!
Copyright (c) 2002 by Vorlon001. All rights reserved.