Written by GauchoDude
v1.3
10-30-2001

Thanks goes out to the entire #dsstech team, especially Extreme, Mex, and Digibluh for their
untiring patience and outstanding knowledge.

Also to RAM9999, and AOL9645 for their datastream & USW/DSW analysis. Where would we be without you ?

And to the entire rest of the #dsstech team and Operators, (Too many shout-outs here, folks !)
for supporting this hobby and giving me a place to hang.

A very special thanks to HUmorless, for assisting me in editing this document throughout
it's creation !!!!

HU USW0600 / DSW6 Workarounds and FAQ
=====================================

Table Of Contents
*****************

1.0 Background
2.0 Recommendations
3.0 Required Software and Installation
4.0 Card Cleaning
5.0 Activation Scripts
6.0 Public 3m's
7.0 General FAQ

1.0 Background
--------------

This document will briefly outline the current USW/DSW status on HU cards, provide recommendations, list the required software, and act as a General FAQ.

This is not meant to be an exhaustive, detailed analysis, but a general FAQ-type document.
For additional details, please consult the forums at http://chat.hitecsat.com.

Recently, there have been numerous updates on HU cards as follows:

USW Updates
+++++++++++

The USW has been incremented from 01 to 0600. Within those updates, there are 2 notable updates.
Please note that these USW updates do not appear to be complete.

- Clone Marking: A method for determining if a card is a "clone", and marking it as such for future
Hashing or Looping has been introduced by the current USW updates. Presently, the clone detection code does not cause hashing or looping. It appears to be incomplete, but can be completed any time by further updates.

Cloning is defined as a card that's EEPROM (CAM/ZKT, Keys etc.) are not the same as originally came on the card. This can generally be determined by comparing the CAM ID printed on the card with the CAM ID in the EEPROM. Use either an ISO programmer in WinExplorer 4.6, in P3 mode, by hitting the camera icon, and comparing the CAM ID in decimal, to the card number printed on the back of the card, or, in Extreme HU 1.71, by doing a Card, Check Card Info, and comparing the CAM ID listed there to the card number printed on the back of the card.

If they don't match, it's a clone, and you should restore the original backup bin. If for whatever reason you do not have an original backup bin, your card is being marked, and is now an easy target for a Hash or Loop.

On other areas of the card, identifying a clone is more difficult, but symptoms of a cloned card are:

- Inability of card to take USW updates - assuming this card will take updates
See Section 7.0 - General FAQ
- Longer than normal time to read when using known, functioning hardware

* Note !!!! We recommend restoring the original backup bin whenever possible due to the apparent
ASIC clone detection capabilities!!!

- Complex Hashing Algorithm

The current USW's contain a table that can be invoked at any time using the dynamic packet capabilities of the HU card, and, essentially, can check all non-card specific areas in the EEPROM, simply by delivering a new DSW package and/or a new CMD82 packet.

*Note !! This means if you are blocking CMD90 packets, you will get hashed, as both the DSW updates (CMD81) and the CMD82 packets are delivered via the CMD90 packets.

At present, the Hash routine checks for:

* Current DSW to be at 6
* USW to be at 0600
* Altered bytes in the 393Dh-3F47, 2711h-2ACDh, 3159h-3939h, 393Dh-3F47h ranges of EEPROM
(Updated 10-30-01)
If you don't have the updates, and/or your card has modified data in the above region(s), you will get
hashed, and one of the following will appear on your screen:

* "Please Stand By" on some or all channels - constant or periodic
* "Card Expired Please Insert a Valid Access Card"
* Blackness on channels other than the previews

- Updating your card to Current USW's

There is no safe method to load the USW's in a program. You MUST let the receiver do it.
For your USW to increment on an HU card the following conditions must ALL be met:

* At least 1 card in your 256-card group MUST be subbed
* Your USW Counter must not be corrupt
* Your USW Data/code must not be corrupt
* Your USW 12-byte key must not be corrupt

If any or all of these conditions are not met, NO USW updates will register on that card.

* Note !! There IS a method for forcing the USW updates, and it is not really recommended, but I included here for informational purposes. Please check the Section 7.0, General FAQ

- Currently, for the USW's to increment from 0000 or 0001 to 0600, the card must be put in the
receiver on channel 100 for about 2 hours.

DSW Updates
***********

- The current DSW update is 6, and with it, this initialized the current hashing. For your card to accept
the DSW updates, it can be at any DSW prior to 6 (including 0) and put in the receiver, without write
protection.

If your card does not have DSW6 on it, just clean it, and put in receiver and it will take it in a few
minutes.

- Ensure CMD90 blocking is OFF. This can be set in Extreme HU 1.71 - Card, Utilities, CMD90 Blocking, Turn OFF

2.0 Recommendations
------------------

Due to the complex Hash routines and Clone markings, #dsstech has the following recommendations for
testing with HU cards at present:

- No Cloning

As stated above, the current USW's "mark" clones, so, it is recommended that you do not use a clone at this time. If you were cloning, we recommend you restore your virgin bin by using Extreme HU 1.71. To do this, you must have a backup bin somewhere on your PC from a previous read and save.

There are some instances where that is not possible, such as, you never made a backup bin and you
cloned, the card came to you cloned, the card's CAM and/or ZKT have become corrupt and you receive
the "Call ext. 745" message and have no backup bin, the card is not in a card group that is receiving USW updates.

In each of these circumstances, you may need to clone to get the card working. It is the only way at this
point. It is not recommended, but this is the only cure.

* Note !!! Please note that a cloned card, for whatever reason, is subject to Hashing and/or looping. Please consider this a friendly warning.

- Use Activation Scripts WITHOUT Tier Wipe Blocking

Install an activation script WITHOUT tier wipe blocking. These are the safest, but require the most
maintenance and the use of a good HU loader due to frequent tier wipes. Tier wipes will "wipe" the tiers off a card within hours to days, resulting in frequent "Call Ext. 722" messages. This can be prevented by using tier wipe blocking (corrupting group keys), but is NOT recommended. An activation script without tier wipe blocking and current tiers will be much more immune to ECM's (hashing/looping).

One thing to remember, Tier Wipe Blocking (corrupt group keys) was a target on Black Sunday for H cards.
Please consider this a friendly warning.

* Note !!! A good HU loader is one that "pops" 90% of cards in the first 5 glitches. A loader that
consistently requires 20-30 glitches to "pop" a card is subject to corrupting the 4th byte
of the ATR, and/or looping your card with an ATR 00 or FF.

Please, use your own judgment here, as there is no public HU unlooping at this time.

Currently supported / working activation scripts are ExtrmeAct1.5 and NewEraAct1.0.
The installation and use of these is outlined in Section 5 - Activation Scripts

If, as recommended, you install these script without tier wipe blocking, your tiers will fall off quickly, and
you will lose channels and receive a "Call Ext. 722" message, within hours or days.

This is normal; it is part of the Tier update packets from the data stream. If your card is NOT subscribed to
the tiers you installed in the activation script, then the tier dates will revert back to Jan 1992.
This can be checked in Extreme HU 1.71 by performing a Card, Read Card, then a View, Tier Data. Check the
dates, any dates for any given tiers, that are not post the current date, will get the "Call Ext 722" nag on the
channels within that tier.

This requires refreshing tiers, from within the activation software; this is why we recommend a good loader,
as you will be glitching into the card often to refresh tiers

* Note !!! Although some Activation scripts have a Tier Wipe blocking option that will prevent the normal
tier update process from functioning, thusly allowing the installed tiers to work until its
expiration date is reached (BTW you can only set the Tier Expiry dates about 60 days out), it is
NOT recommended ! This was a major target on Black Sunday for the H cards.
Please consider this a friendly warning.

3.0 Required Software and Installation
--------------------------------------

- Extreme HU 1.71 / ExtremeActv1.5

The path of least resistance to getting Extreme HU 1.71 functioning correctly is as follows:

1. Download and install VBRUN60.EXE - this is available from Microsoft's web page
and most download / search engine sites, just type vbrun60.exe in the search screen, then download,
install it and reboot.

2. Download and install Extreme HU 1.60 Full from www.hitecsat.com/dssfiles2.htm, reboot

3. Download and install Extreme HU 1.70 from www.hitecsat.com/dssfiles2.htm; this is required because
it contains ExtremeActv1.5

4. Download and install Extreme HU 1.71 from www.hitecsat.com/dssfiles2.htm - this is the most recent
version of Extreme HU that fixes a problem with the new clean routine so that it properly handles all cards
regardless of USW, up to, and including, 0600 and some additional bugs. This version also adds a new
capability, called PPV Only card, that is available in the Card pull down menu.

- NewEraAct1.0

Download this from from www.hitecsat.com/dssfiles2.htm. This is a WinExplorer script, and it requires
WinExplorer4.6 fully functioning, see below.

- WinExplorer 4.6

Ok, seems as if a lot of people are having problems with this one. Here is the minimum you need to get this
working. Your mileage may vary. There are a lot of posts on the forums to get WinExp4.6 to work on certain
OS'es, and this FAQ does not address every situation.

1. Download and install WinExplorer 4.6 from www.hitecsat.com/dssfiles2.htm

2. Install the appropriate MS script controls for your operating system. The current version is 5.6 and can be
obtained at:

http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?url=/msdn-files/027/001/733/msdncompositedoc.xml

3. If you are running on WinME, Win2000/W2KPro, or WinXP, you will need to delete a key in the registry.
Here is how:

* Do a Start, Run, Regedit
* Navigate to HKEY_CURRENT_USER/SOFTWARE/Dream Company/
* With your mouse highlighting Dream Company, hit the Delete key

4. Install or re-install MS IE5.5. This contains required files certain OS'es, like Win95a and WinNT 4.0

5. Remove any and all other versions of WinExp on your PC. Sometimes older version interfere with the 4.6 version

6. When using scripts in WinExp 4.6 for HU's, be sure that WinExp is set for Unlooper mode as follows:

* In the main menu, choose Configure, and choose Program Parameters
* Click on the communications tab.
* In the Quick settings drop down box, choose Unlooper
* Uncheck Flush Echo Bytes
* Uncheck Flush Receive Buffer Before Writes
* Click on the Advanced tab and make sure there IS a check in Ignore Receive Timeouts,
and IS NOT a check in Reset After Timeout; Leave the other settings at its defaults
* Click on the Program Settings tab and make sure that Associate WinExplorer Files IS checked and
Log Transactions does NOT have a check in it.
* Click on Save, at the top of the panel, and when it asks for the name, leave as Unlooper and click Yes to
overwrite

Click on OK after you have made these changes.

If you still cannot get WinExplorer working, double check your Com Port settings in Configure, Program
Properties, Communications, and be sure you have the correct Com Port selected, and no other programs
are running that may interfere with WinExplorer. That includes Extreme HU, so be sure it's closed also.

If you receive a Timeout from 2a, you are running a script that requires you to be in unlooper mode in
quick settings.

If after all of this, your WinExplorer scripts are not working, check the forums or #dsstech for suggestions.

4.0 Card Cleaning
----------------

Ok, there is LOTS to say about cleaning right now with all the USW updates in the stream.

- Cleaning with a program OTHER than Extreme HU 1.71 or NewEraAct1.0 / NewEra1.3c will remove some of
the USW Code/Data placed on the card by the USW's 0100-0600, and or result in an all 00000000's CAM ID.

Refer to this post at chat.hitecsat.com for further details:

http://chat.hitecsat.com/showthread.php?s=cb0b7524dd5ba2fdbc4151fd3526dae2&threadid=13901

* Note !!! It was discovered fairly quickly that Extreme HU 1.7 had a bug in the clean operation.
If you clean a card and apply the ExtremeActv1.5, you were STILL getting hashed,
meaning that some portion of the EEPROM that is being checked for by the current hash,
was not being cleaned properly. This was quickly resolved with Extreme HU 1.71.

These are the main things needed when cleaning:

* USW Counter - no clean affects this, but the above clean routines check this and verify the data matches
the counter
* USW Data - all cleans EXCEPT the above programs / versions will remove USW data on cards at any
USW other than 00 or 01
* 3m Code - The above cleaners will remove any public HU 3m's, and most private ones to (certain
exceptions apply)
* CAM / ZKT tables - Some scripts, like Merlin corrupts this. The only way to clean if you installed this,
is to restore virgin bin
* Group Keys - same as above

What this all means is that if you clean a card that is at ANY USW other than 0000 or 0001, with Extreme
HU prior to 1.71, or Eclipse, or ArrowPointe, then you have a VERY strong chance of looping the card
(worst case) or being hashed (best case).

- To perform a clean in Extreme HU 1.71, select Card, Clean card. Most scripts will auto-clean, but it will not
hurt to clean 2x, assuming you have a good loader. Alternatively, you can do a Card, Read Card, then an
EEPROM, Clean EEPROM, then a Card, Write Card; generally this is not recommended as it requires an
additional glitch into the card. This is helpful when trying to examine EEPROM for areas that Extreme HU
cleaned for analysis purposes.

- To perform a clean in NewEraAct1.0, close Extreme HU, open WinExp4.6 with the above settings
(unlooper), then do a File, Open script, and select NewEraActv1.0.VXB, then do a Card, Execute Script.

Then select the Remove Option.

- To perform a clean in NewEra1.3c, close Extreme HU, open WinExp4.6 with the above settings (unlooper),
then do a File, Open script, and select NewEra1.3c.VXB, then do a Card, Execute Script. Then select the
Clean Option.

* Note !!! If you have any doubts that your card is getting cleaned correctly, due to some prior action
done to the card, restore a known good backup bin, prior to loading with any script !!!!

- Restoring Backup EEPROM from BIN format in Extreme HU 1.71.

* If the file is in .txt or .bin format, do a File, Open Bin, and find your bin that matches your card,
then do a Card, Write, Current EEPROM.

This card is now safe to clean, and should accept any USW and DSW updates, given documented USW
issues elsewhere in this document.

5.0 Activation Scripts
---------------------

- General Notes

* Activation scripts are designed to mimic a subscription card as closely as possible, therefore,
no "jump points" are implemented to be possible Hash or Loop targets.
BUT, if you install old or invalid Tiers, you are subject to Hashing or Looping; an old tier became a
target for H cards on Black Sunday

* Activation script "Marry" to the first receiver they are put into. This means to move card with an
activation script on it, you will need to "un-marry" the card from the receiver. To do this, open Extreme
HU 1.71, and select Card, Utilities, IRD, UnMarry (or the chain link icon).

* PPV's - Channel 100's and 594,596-598 and special events on various channels are NOT tiers, and can't be
activated, or "turned on" by activation scripts. There is a hard limit of 25 PPV purchases or a given
dollar amount, which can be changed in the NewEraAct1 file, or in Extreme HU 1.71 by doing a Card,
PPV Wipe (toilet paper icon), and selecting "custom". You can do this anytime your PPV limit is
exceeded.

* Note !!! Do not set this higher than $300-400

* "Call Ext. 711" error, with activation scripts. This is normal, expected behavior from an ex-sub or
partially activated sub card / bin. This means that the card is receiving EOS (End Of Service) packets,
and changing the Fuse bytes from 25DA to 24DB or 20DF. This causes the "Call Ext. 711"; the only
thing you can do in this case, until/unless those packets are no longer being sent to the card's present
CAM, is to install a 3m that has fuse byte protection (none public), or clone the card. Cloning is not
recommended, please see Section 2.0 - Recommendations

* Note !!! Although some Activation scripts (Extreme HU 1.5) have a Tier Wipe blocking option that will
prevent the normal tier update process from functioning, thusly allowing the installed tiers to
work until their expiration date is reached (BTW you can only set the Tier Expiry dates about 60
days out), it is NOT recommended as this corrupts group keys !!!!

Group Key Corruption was a major target on Black Sunday for the H cards.
Please consider this a friendly warning.

* For a more detailed description of how activation works, please refer to chat.hitecsat.com

http://chat.hitecsat.com/showthread.php?s=cb0b7524dd5ba2fdbc4151fd3526dae2&threadid=11844

- NewEraAct1.0

This script is a basic Activation script, which has no tier wipe blocking (group key corruption) and is applied
via WinExp4.6. Please refer to "getting WinExp4.6 installed / working."

* Installation / Operation

To apply NewEraAct1.0, close Extreme HU, open WinExp4.6 with the above settings (unlooper), then do a
File, Open script, and select NewEraActv1.0.VXB, then do a Card, Execute Script.

Now select the Activate button. You have 2 options: "Default" and "Select values." Look at the panel and
see if those options are ok; if so click on "Default". Otherwise, click on "Select" and follow the prompts
and make your selections. When using the "Select" option, choose 25DA for your fuse bytes.

* Customizing the Default Values

If you would like to change the default settings to your own, so you don't have to keep typing them in,
simply do a file, Open Script. Then in the upper right hand panel, cursor through the script and change the
defaults in blue to whatever you want. Then do a File, Save.

* Note !!! This is the only place to select the Sports Tiers !!!

* Note !!! Do not set the PPV limit higher that $300-400 dollars

* Refreshing Tiers- When you start to receive the "Call Ext. 722" messages, simply select
the "Refresh" button

* Note !!! Because this script does not implement any form of tier wipe blocking, your tiers will fall off
quickly, (hours to 4 days) and you will lose channels and receive a "Call Ext. 722" message.
THIS IS NORMAL. To refresh tiers, from the main NewEraAct1.0 menu, select refresh tiers.

- ExtremeActv1.5

* Operation / Usage

Please refer to Section 3.0 Required Software and Installation - for the correct installation instructions.

* Note !!!!! Please read this entirely and perform the selections in the order given below

In Extreme HU 1.71, Do a Card, Write, Extreme HU Hex file. This will bring up the Activation Options as
follows:

1. Activation Days - This sets the date that the Tiers installed on the card will be set to expire, counting
out from the current date. Please use the default days of 55, as any date further out than ~60, will not
work.

* Note !!! This setting is immaterial / moot as long as it sets the dates post today's date, if you do NOT
enable Tier wipe blocking. The normal Tier update packets will wipe the tiers much more
rapidly than the 55 days set here. For more information, please refer to Section 2 -
Recommendations

2. Ratings - Self explanatory; sets the ratings limit to be used when the receiver is "locked" using the
Locks and Limits feature of your receiver. Note that the Locks and Limits routines work correctly with
this script.

3. Guide Byte - The default is 49, which is fine, but you may want to try 4D

4. Zip Code - It is best to put in a Zip code that matches your locals market selection, if any

5. IRD Selection - 1-4 Generation receivers are receivers that DO get the 900's, if that's what you have,
select that, it will give you the 900's. If you have a "Plus" or 5th generation receiver, select 5th Gen IRD,
and that will reveal the locals market option pull down. Please select a locals market that matches the
Zip code entered above.

* Note !!! See the General FAQ Section on the LNB requirements for each locals market.

6. Optional Tiers - select these NOW, prior to selecting anything else !!!

Only select the ones you want / will use. Less is better here. Do not select a tier that you cannot
utilize, such as UltimateTV, if you don't have an UltimateTV receiver. To use the "Custom" tiers, you
must know the tier name/code that you want to add, just type it in the option box. Click "Continue"
after you have selected the "Optional Tiers"

* Note !!! Be sure to double-check your locals settings, as they sometimes revert back to the default.

7. Prevent Area Related Blackouts - Does just what it says, select it now if you commonly receive the
message "Program Not Available In Your Area" message on channels you would like to view.

* Note !!! This could be used as another Hash or Loop target, use at your own risk.

8. Add Locks and Limits - This field allows you to enter the Locks And Limits password that will enforce
the Rating selected in Step 2. This step is optional.

9. Prevent Tier wipes - This option should be selected now, if you wish to prevent Tier Wiping.

* Note !!!! This is NOT recommended !! See above in this section, General Notes,
and in Section 2.0 - Recommendations

10. AutoSave Bin Before Programming - I suggest Selecting this to ensure you have a backup bin....

You all have virgin backup bins, right ?!?!?!? Select this one for sure !

11. Enable Batch Mode - Does just what it says... Select to install the same settings on
multiple cards. You will be prompted for removal and insertion of each card, press the Halt Icon when
you want to stop batch mode.

12. Do Not Clean Card (add tiers only) - This is ONLY used when you wish to add or refresh
the tiers on the card. It can be used on sub cards (you do have a backup bin right ?),
or to refresh a previously activated card. Please be sure to select your Optional Tiers.

* Note !!! This does NOT complete the activation requirements on a clean or virgin card !!
This is only for refreshing tiers or adding tiers to an already working card,
primarily one that is getting "Call Ext. 722" messages.

- Once you start receiving the "Call Ext. 722" messages, either clean and re-install, starting
at step 1, or just perform step 12 to only refresh tiers

- When you receive the message "PPV full" or "Spending limit Met", or "Call Ext. 732", on the
PPV channels, in Extreme HU 1.71 you can "wipe" the PPV's, by doing a Card, PPV Wipe
(toilet paper icon), and selecting "custom".

* Note !!! Do not set this higher than $300-400

6.0 3M's
--------

* Note !!! This section DID have information on current working 3m's (NewEralsv1.hex and NewEra2.3, and
NewEra1.3c) but during the proofing and completion of this document, these have all been
Hashed.

- Public 3m's

The current Hash range is 393Dh-3F47, 2711h-2ACDh, 3159h-3939h, 393Dh-3F47h (updated 10-30-01)
which includes most, if not all public 3M jump points.

There are NO current public 3m's that are not being hashed. Expect any that come out in the next few days
to be hashed. There are some private scripts that use unique methods to circumvent the hashing, but these
are private and do not expect them to hit the net as freeware.

* Note !!! Do not clean with software OTHER than the software / scripts detailed Section 4 - Card Cleaning
as they will wipe portions of the USW data, and may result in you card being looped shortly
after being returned to the receiver. Please consider this a friendly warning.

7. General FAQ's
----------------

- Number ONE (1) rule of loading / programming HU cards is: Save a Backup BIN !!! Please do this BEFORE
you load anything onto a virgin / sub / ex-sub card. This provides you with a method to restore you bin if it
becomes corrupt. Also note that the only HU unlooping that is being performed, produces a clone, so the
only way to restore the matching EEPROM (CAM-ZKT/Keys etc.) is with a known good backup bin.

To create a backup bin, In Extreme HU 1.71, do a Card, Read Card, then a File, Save As, Bin File. This will
create a .bin file in you backup bin directory (C:\Program Files\Extreme HU\Bin).

It is also recommended that you restore your virgin bin, clean, then put in receiver to get the newest USW
updates, then creates a backup bin as above.

- To check what the current USW is on your card, in Extreme HU 1.71, do a Card, Check Card info. This well
tell you the current USW and DSW on your card.

- To just get the updates on the card for archival purposes, restore the cards virgin bin, or clean with one of
the programs above, and do not install a script of any kind, and put in receiver for around 2 hours
(It sometimes takes more or less time). Then when the card is at USW0600, in Extreme HU 1.71, do a Card,
Read card, then a File, Save as Bin. It will auto-name it with the card-type, USW number, and CAM.

- "Call Ext. 711" error, with some 3m's and/or activation scripts. This is normal, expected behavior from
an ex-sub or partially activated card / bin. This means that the card is receiving EOS (End Of Service)
packets, and changing the Fuse bytes from 25DA to 24DB or 20DF. This causes the "Call Ext. 711"; The
only thing you can do in this case, until/unless those packets are no longer being sent to the card's
present CAM, is to install a 3m that has fuse byte protection. NewEra2.31 does, but NONE of the
activation scripts do.

- If you receive a Timeout from 2a in WinExp4.6, you are running a script that requires WinExp4.6 to
be in unlooper mode; Configure, Program Properties, Quick settings - Unlooper

- Restoring virgin bin: In Extrme HU 1.71, do a File, Open Bin, and find your bin that matches your card,
then do a Card, Write, Current EEPROM.

This card is now safe to clean, and should accept any USW and DSW updates, given documented USW
issues elsewhere in this document.

- USW Update Workaround, Courtesy of AOL6945, Thanks AOL !

If a card is not updating to USW 0600 in the stream, there are one or more things that could be wrong:

* The USW counter on the card (which is at 24C8h by the way, not 24C0h) is already at 0600.
The card won't update if the counter says its already updated, even if the 0600 USW code isn't really on
the card. If this is the case with your card, clean it in Extreme 1.71 (do not use earlier versions)
and reapply your script/hex.

* The USW counter is at something less than 0600h, and the 12-byte USW key at 2EECh is not the correct
value. This can occur if the CAM ID and ZKT have been changed on the card but the key was not.
You can fix this by writing a 00h byte to 3224h, which will force the USW updates to be taken even if the
key is incorrect. Realize, of course, that this is an EEPROM modification, and can be hashed or targeted
for ECM. I recommend that if you use that method, that you allow the card to update to 0600h, and once
it is getting video, you re-edit the 3224h byte back to 02h.

You can also fix this problem by writing a virgin bin back to the card (preferably the bin that matches the
CAM ID printed on the back of the card, that way it's not cloned).

* The CAM ID for that bin is in a group of 256 cards where none of those 256 cards is subscribed.
In this case, the USW updates for that card group are not in the datastream. You can fix this by writing
the updates to the card manually (editing EEPROM) and editing the USW counter to 0600h

(this method is very advanced, not recommended for beginners, and will leave the 12-byte key at 2EECh
out of sync with the updates, preventing the card from taking further updates unless the virgin bin is
rewritten or the 3224:00 modification is done). You can also fix this by cloning a valid bin to the card
where the CAM ID of the cloned bin is in a group that updates are being sent for (not recommended to
clone your card).

Realize, also, that an incorrect 2EECh key can be targeted for ECM (although it cannot be hashed).

* If you decide to edit the USW counter at 24C8h for any reason, remember that those two bytes
(06 00) must be encrypted with the EEPROM key before they're written (you have to do this by hand).
If you're not familiar with how to manually encrypt those two bytes with the EEPROM key,
I recommend you not attempt it.

- AOL6945

- Locals Table and LNB requirements

01 Atlanta 16 Greenville** 25 Pittsburgh*
19 Austin* 08 Houston 26 Portland
1A Baltimore* 20 Indianapolis 17 Raleigh**
1B Birmingham* 21 Kansas City* 10 Sacramento
02 Boston 09 Los Angeles 18 Salt Lake
1C Charlotte 22 Memphis* 27 San Antonio*
03 Chicago 0A Miami 28 San Diego*
1D Cincinnati 23 Milwaukee 11 San Francisco
04 Cleveland 0B Minneapolis 12 Seattle
1E Columbus 24 Nashville 13 St. Louis
05 Dallas 0C New York, NY 14 Tampa
06 Denver 0D Orlando 29 W Palm Beach*
07 Detroit 0E Philadelphia 15 Washington, D.C.
1F Greensboro* 0F Phoenix 00 No Locals

* Double LNB Required" ** Triple LNB Required

Please allow 2 hours for your local 1-99 channels to appear in the guide.

88 All locals for 1st to 4th Generation DSS Receivers Only
No sub has 88 so it's at your risk.