(Version 6.0 last revised on 07/21/2000. Any comments or suggestions please direct them to Dredger. However do not email Deejay or myself about where to locate and download any DSS related files recommended in this programming guide. Any such emails will just be deleted).
PLEASE READ, VERY IMPORTANT:
The 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 WILL NOT BE HELD RESPONSIBLE FOR THE ACTIONS OF THE PEOPLE USING THIS DOCUMENT. This Programming Guide is strictly for EDUCATIONAL USE ONLY. Also the DSS Underground (DSSU) also does not and will not take any responsibility for what might happen to any card using the following procedures. In other words, USE THIS PROGRAMMING GUIDE AT YOUR OWN RISK.
Also please take special note of anything that has been bolded. This has been done so for a reason and that is to stress some importance or a warning. So with that all out of the way let us say that what we are trying to offer here is a basic and simple procedure that hopefully will make everything as easy for you as possible. We also recommend steps in this procedure so that it is as safe as possible, meaning we want to try our best to avoid having your card become looped or 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 or write a script to an H 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. We understand that programming a card, especially that first card, can be a very intimidating process. But in reality it is not a difficult thing to do with today’s current software scripts. So the guide contains four sections: getting started, cleaning, programming and for those who require to do so, cloning. Follow each section exactly as you are directed and you should be finished before you know it. That is unless there is a problem with your card. Many times 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 steps 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 the DSS Underground Forums 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. Give as much detail as possible. But generally a majority of you will have no problems and hopefully this process will be smooth as silk. Also it is strongly recommended that you thoroughly read through this whole guide before you actually attempt to do anything to the card so that you can clear up any questions you might have before you start.
We’d like to also point out that we do try to keep this programming guide as updated as possible. Often it will be revised within hours of a script or other software change that gets released. However at times we may not be able to update fast enough to stay absolutely current depending on what may be occurring as far as what Dave is doing or if we are busy due to other obligations like work or site maintenance. So if this programming guide at times isn’t 100% up to date please be patient and understanding. After all, this is just a hobby and for educational purposes only.
Our first point of business is to take a moment to thank a few people for contributing some outstanding software that we recommend and use in this guide. Often we all take this stuff for granted but all of us owe these people a ton of gratitude for what they have contributed to this hobby. First of course we have to give a big thanks to Squeem for his great BasicH program. Without this excellent card-cleaning program the process couldn’t even begin. Next a special thanks goes out to Dexter for the excellent WinExplorer program. As important as BasicH was for cleaning this program is every bit as important since it allows scripts to be written to the card. Then we have to thank those who have supplied the outstanding programming scripts. So first we have to thank DSSDumbie for the DssStealthPro script and for keeping that script as updated as he has. Actually that script evolved from the JSP29 script so we should also thank all those who were involved with JSP as well. Again because of these guys as well as countless others that we will most likely never know about we continue to have a great hobby. So thanks to all the people that help make this hobby what it is today. And finally we have to make sure to really thank Deejay since he’s the one who makes it possible for all of you to have access to this guide as well as the DSSU forums where all the great information of this hobby is passed between us all.
Now we have a very important announcement and actually what originally looked like a sad one now looks like it will actually turn out ok. There was a rumor that CloakWorks who gave us the SummitStealth script apparently had decided that the version 1.6 release of this great script may very well be the last PUBLIC RELEASE. But it looks like that may have been premature. The following is taken directly out of the SummitStealth 1.6b read me file.
“Unfortunately, version 1.6a was released with a modified Read Me that was NOT approved by the CloakWorks team. A member of our E-team who is particularly upset about OmenStealth modified the Read Me before handing it off to our C-team for distribution. The team does NOT currently have any plans to abandon future public releases. Although the entire CloakWorks team is disappointed that the author of OmenStealth chose to release a modified version of SummitStealth to the public even AFTER he was personally asked not to, there is nothing we can do about that. (We prefer to see new features requested. We evaluate them and consider them for inclusion in a future release. This avoids confusing people with "yet another script" syndrome.) Although the E-team member in question may have personally felt better by doing what he did, it did not accomplish anything. And it may have actually made matters worse. We would like to apologize to any other scriptwriters who were offended by the comments in the Read Me included in version 1.6a. (Although we do think dealers who profit from freeware still suck.) The original 1.6a Read Me had a special thanks to "Anonymous" for posting an elegant solution to closing the 48 hole. Our hats off to whoever that was for their generosity and ingenuity. The real reason the 1.6a release was delayed was because there was a problem with our dynamic password back door that took a while for us to track down. Unfortunately an older version of the script was released with the modified Read Me, and therefore has problems during installation under certain circumstances. We hope that the version of the script included here as version 1.6b addresses this issue.”
Who can really blame them for being pissed off? They offered this script out to the DSS community for free, asked that it not be modified and yet they were ripped them off and it got distributed anyway. I recommend that any of our members reading this should boycott the OmenStealth script out of courtesy to Cloakworks. Besides why use the imitation when you can use the real deal. All I can say is thank God that what appeared as a potential tragedy for the hobby with the end of SummitStealth looks now like something that has been averted. I just want to say (and everybody whoever used the SummitStealth scripts should also do as well) is thank you for everything that you guys have contributed to this hobby. Those of us especially here at the DSSU who do this, as a hobby, definitely will be glad that you guys will still be around giving us such a great script.
OK let me first explain what the term valid card or valid bin means since it is referenced all throughout this guide and some people still seem a bit confused by what exactly it really means. By valid we mean a card or bin that does not get the invalid card or call ext 745 error messages when in a receiver. The only cards that will not get those messages are generally cards that are still currently being subscribed (sub’d) to Dave. Once a card is no longer being sub’d (subscription is cancelled) it’s CAM ID becomes invalid and will get added to Dave’s database making it a prime target for the 745. I continue to get email from people telling me that they reprogrammed their card and after they were done they put their card in the receiver and after a certain period of time (can be up to 2 hours) they still get the Invalid Access Card and Call Ext 745 Nags. It totally amazes me that by now some people still do not understand what causes these messages and also what they need to do to get around them. This just proves to me that some people just don’t take any time to do any reading in the forums (something that we PREACH about constantly) before attempting to program their cards. Or else they just don’t understand what they read (if they bothered to read at all) very well since this has been talked about in the cleaning section in previous versions and also in this programming guide as well. So I’m going to explain this one last time and hopefully I won’t be just wasting my time.
If you are currently getting the Invalid Access Card or Call Ext 745 messages then there is NOTHING that you can really do outside of either cloning that card with the saved EPROM image (called a bin) of a known valid H card or running a special script such as SpooFeR or X2000. What cloning with a valid bin file will do is keep that card or CAM ID off of the D** invalid card list. Once a CAM ID is added to this invalid list it becomes a target for the 745 Nag. I’m not going to go into the whole explanation of why it actually happens because this info is readily available in the DSSU forums. But again if the CAM ID of the card is invalid you will get the 745 Nag, if the CAM ID is valid then you won’t. It’s really just as simple as that. So if you are getting the 745 Nag message and you DO NOT have access to a valid H card or a valid bin file you might as well STOP RIGHT NOW.
Now if do have a valid bin file don’t waste your time cleaning and programming your card because it’s a total waste of time since again it has nothing to do with the programming that is on your card. Also locating a valid bin file will be very difficult at this time. Most people who have them are now unwilling to offer them since they are getting harder to locate as more and more CAM Ids become invalid. So I wouldn’t bother going onto the forums asking because it’s very unlikely you will get any response. Especially don’t waste your time asking any of the administrators or moderators on the DSSU to supply you with a valid bin because those types of requests will just be ignored. Your best option will be to locate a friend or family member who might still be subbing. But remember it has to be an H card. An HU card is useless to you at this time.
OK so if you understand all that and have what you need the following is a quick overview of what you will be doing by following this guide:
This can be pretty simple stuff as long as you can read and follow the directions as they are written. You’ll be watching TV in no time. So to get started proceed to Section 1 - What You Need To Do To Get Started.
Section 1 -
What You Need To Do To Get Started:
Important notice: effective
immediately the DSSU will no longer offer a files section for downloading the
required software necessary to use this programming guide. We are not sure if
this will be permanent or temporary but for now we will no longer offer the
files on this site. So any files required or recommended in this programming
guide will need to be located and downloaded from elsewhere. Do not email
Deejay or myself asking where to locate such files. Any such email will be
ignored and deleted. We are sorry about needing to do this but D**’s lawyers
are pushing this issue with the site’s ISP and until it is resolved we have
just decided to play it safe. Hopefully everyone understands.
First thing that is required of course is that you actually have an H card. No other card at this time can be programmed so unless what you have is an H card, don’t bother going any further. If you are not sure that what you have is an H card then go to the following links on the DSS Underground to verify your card. The first link will give text information about H cards including CAM or serial number ranges. The second link will give you actual pictures of H cards.
H Card Info (text only)
DTV/DSS Card Info (pictures)
The next requirement is to purchase a programmer making sure that it is ISO7816 compliant. There are many to choose from and just about all of them are fine programmers. We recommend that you purchase a programmer from one of our dealers on the DSS Underground who by purchasing banners help to support and maintain the site. You can find these banners at the top of the home page or also on the main DSS Underground Forum page. Another great place to check out some of the programmers as well as other products out there is on the DSS Underground product review pages.
Once you have a programmer then you will need software. The following is a list of files that we recommend and will refer to in this programming guide. Again we no longer offer these files for download so are required to locate these files elsewhere.
The first files are MS Scripting Files that are required in order to use WinExplorer 4.4. Some of the above files may not actually be necessary depending on what version of MS Internet Explorer you are running. However instead of getting too much into that it is just as easy to tell you to go ahead and install the files since installing them will not hurt one way or the other and you will be sure to have them if indeed you do need them. Once you download them they are each self-extracting so just go ahead and execute them. They will install where they need to be installed. Again note that you only need to install the dcom that is appropriate for whatever version of windows you are running. If you are running Windows NT or Windows 2000 then no dcom file is required so only install ste51en and sct10en.
Ste51en
Sct10en
Dcom95 (for Windows95 only)
Dcom98 (for Windows98 only)
The following files are utilities needed for unzipping files and testing PC COMM ports:
WinZip 8.0 (Application used to zip and unzip files)
RS232.exe (Utility used to verify that comm ports on a PC are open and functional)
The following files and scripts are used for cleaning and programming H cards for educational purposes only:
BasicH 2.7 (Application used for cleaning, adding updates, reading and writing EPROM images to and from H cards)
Viyada 1.6 (An older version of BasicH that sometimes works better with older H cards)
WinExplorer 4.4 (Application used for writing scripts to H cards)
SummitStealth 1.6b (An excellent and super user friendly installer script for programming H cards)
DssSteathPro32a (Another script for programming H cards, especially if you have a cloned card)
We will now continue assuming that you have located and downloaded any required files. First thing you will need to do is to execute and install WinZip 8.0 if you required this file since all of the other files will require being unzipped. After WinZip is installed you can go ahead and unzip the other files. Take note as to where or what folder WinZip is unzipping the files. Generally it is into a folder called "unzipped" which should be at the root level of your C drive. After all files are unzipped it is recommended that you move those unzipped files into a folder named DSS or whatever you prefer to call it so that all the files will be together and easily located.
There is one configuration setting to WinExplorer 4.4 that we’d like for you to verify to make sure that it is properly set correctly. So open WinExp and go to the configuration menu / program parameters / program settings and make sure that the Associate WinExplorer Files box is checked. Click OK and quit out of WinExp. What this setting allows you to do is to just double click a script file, which will launch and open into WinExplorer 4.4. This will make it much easier for you to load scripts, as you will see below.
That is pretty much it as far as what is needed. You will of course need to connect the programmer to your PC and make sure that it is functioning. That is what the file called RS232.exe is used for. Run the file and it will give you a listing of four comm ports. If you click on a port it will ping or go out and verify that the port is open and that it can talk to your programmer. If you watch the light(s) on the programmer they will flash when you click the appropriate comm port (generally comm port 1) that the programmer is connected to. If you see no light flash then possibly you will need to configure the port. To do this requires that you to go into the computers BIOS. This is something that is different from computer to computer so we recommend that if you do not know how to do this that you seek help in doing this.
Section 2 - Cleaning An H Card:
The card environment has changed quite a bit due to few recent occurrences which has impacted how and why a card must be cleaned. First came the emergence of newer programming scripts that closed the E3 hole such as SS1.2a and DSSPro30. Now Dave has started to send out new updates (started with 30, then 31, and now to whatever the current Update is in the datastream), which has resulted in problems with hashing (losing channels). This requires cards to be constantly updated to whatever the current update that Dave is sending out in the datastream. I’m not going to bother listing which exact update is currently out there since it is changing so frequently. For that information you will just need to go onto the forums and seek that information out. This guide does try to stay as current as possible and I try to update it to reflect scripts, which are current for whatever update is in the datastream. If it isn’t current it soon will be depending on how quickly an updated script becomes available so please do not email asking why the guide does not reflect whatever update is in the datastream or to ask what you should do. When I know and I can get the guide updated it will become available. Sometimes it just takes time to get the updated scripts and to make sure that the scripts are tested. So at this time the update problem should not be of a major concern. However the most troublesome problem is still the 745 Nag. This more than anything else has increased the need for many people to clean and clone their cards.
If you do not have a valid bin available to you so you can clone your card then you might as well just stop right here as far as this guide is concerned. However you do have other possible options available. Specialized scripts like SpooFer and X2000 do offer scripting that will include working CAM IDs. Now there is no telling how long these CAM IDs will stay valid but if you do not have access to a valid card or bin it might be your only option. I do not cover these scripts in this guide but if you go the DSSU Forums you will find quite a bit of information available about them.
Ok, with that out of the way, if the card that you have only requires basic cleaning and isn’t a card with programming already installed then you can skip down to the “Basic Card” Cleaning section just below. If you think that your card has already been programmed then you will want to go to the next section “Cleaning A Programmed H Card”.
Cleaning A Programmed H Card
If you attempt to clean a card without first removing an installed script you will most likely encounter the error “can’t open the E3 hole” or “E3 hole doesn’t appear to be open”. The reason for this is because most of the current programming scripts stealth this hole, making it impossible for BasicH to access the card to clean it. If you continue to screw around with a card that gives you this error message then you run a good chance of looping your card. The current release of BasicH does appear to have the capability of removing installed stealth scripts in expert mode. However there have been some reports that this works ok for some scripts but not for others. We have seen reports of cards being looped when attempting removal of some scripts. Therefore we still strongly recommend that whenever possible that you first uninstall any known script on a card with the actual uninstall script supplied with whatever programming script you have on your card. Different scripts have different ways of uninstalling. DssStealthPro has a separate unique uninstall script called RemoveDssStealthPro* (* indicates whatever the current release version) that comes with the DssStealthPro download. You would just run this script to uninstall the current programming script from a card if this was the programming script currently installed on the card. SummitStealth however is different in that you actually run the same script used for installation and at the main programming menu you would either do a remove or possibly an update. A more thorough explanation is detailed just below as the first suggested option to try.
So if you know what script is on the card and know the backdoor password that was used when it was installed then go ahead and uninstall it now. When finished the card can then be considered just a normal card needing cleaning so you can skip on down to the next section “Basic Card Cleaning” and follow whatever steps are required. However if you do not know what script is on the card or if you know but do not know the backdoor password then you may have a more difficult time cleaning the card and quite possibly will never be able to clean it yourself. You can attempt the following options below but if none of these options work then you have to just resign yourself to the fact that the card has to be sent out to be cleaned.
The first option you can try is to run the SS1.6b installer script just like you would if you were doing a normal installation of SS1.6b. If an earlier version of SummitStealth is already installed on the card then when you get to the main menu you will see update, change, remove, verify and exit options. Selecting the remove option will attempt to uninstall whatever version of SummitStealth script is installed on the card. If you are lucky and the password was saved to the card during the initial installation then the script will be removed from the card and you can then skip down to the “Basic Card Cleaning” section to continue the card cleaning procedure. If the remove button was enabled but you were asked for a password when you selected it then the password was not saved onto the card you will not be able to remove the SummitStealth script from the card. So without knowing the password you have to accept the fact that you have to send the card out to be cleaned. There is absolutely no way around this with SummitStealth. However if the remove button was not even available then SummitStealth was not previously installed on the card so you can move on and try the second option.
Run BasicH 2.7 in Expert Mode and try doing a passive read of the card by clicking on the magnifying glass icon located all the way to the right on the tool bar. Make sure that it is the icon on the far right and NOT the magnifying glass icon to left of the ambulance icon. If you do not see this icon then you are not in Expert Mode. If you are able to do this read ok, then update 32 as well as any script should be able to be safely removed by doing a manual clean. Please do not use one step clean even though you will see many who will tell you different. We just feel that manually cleaning is safer especially in expert mode. For instructions on how to do that you can jump down to the "Cleaning With BasicH 2.7 In Expert Mode" section below and follow that procedure.
However, if you are unable to do a passive read then don’t waste your time trying anything else because the card needs to be sent out and cleaned. Remember, if you keep screwing around with the card, especially one with programming on it, you can run the risk of looping the card which can be much worse than just needing the card cleaned. Pretty much any card can be cleaned though it might take unlooper, but not every card can be unlooped.
Since BasicH 2.7 has been released it will now successfully clean cards with the 32 updates. Isn’t this hobby and the people in it great? No sooner does Dave hit us with a punch and he just gets counterpunched. Gotta love it. So now with the applications and scripts needed lets go ahead and explain about the cleaning process when it comes to normal basic cleaning. The cleaning process will depend on a number of factors with the primary one being the state of the USW (Update Status Word aka Update) on your card. If you do not first correctly determine the USW and you attempt to clean a card with updates below 26 and above whatever the current update is in the datastream you will run the risk of looping or damaging your card. So this is a very important first step and we cannot stress the importance of this enough. To determine the USW you need to run WinExplorer 4.4 and get the card info (camera icon). When you do so you should now see something like what is shown below. Actually you will see much more info but all we’re interested in at this time is the USW. So we only displayed down to the USW info.
Trying to reset card...
Reset Successful
RX ATR: 3F 78 12 25 01 40 B0 03 4A 50 20 48 55
Card Information Hex Decimal
---------------------------------------------------
Card ID xxxxxxxx xxxxxxx
IRD Number 00000000 00000000
USW 001D
32
(Note: Since you never know who else is reading the forums, Card ID # and IRD Numbers should never be published especially in a thread posted on the forums. They should always be edited with X’s and 0’s unless you need to supply part of the Card ID when troubleshooting a problem. In that case only supply no more than this example: XXX1 234X XXXX).
The card info above shows the USW with the 32 updates, which should be common for any previously subscribed card that has been in the datastream recently. If your card returns a value that is below 26 and above the current update that is in the datastream then you will not be able to continue cleaning the card until you update the USW. You can try to run Viyada 1.6 and then add 28 updates. If this doesn’t work then try to run BasicH 2.7 and add the 32 updates. If neither of these were successful then you have a problem and you need to stop and seek help on the DSS Underground Forums as to how to hopefully update the card’s current USW. Note: there is a chance that you may read a card and the USW will return as being very high. Some commercially programmed cards or cards with private or specialized scripts may sometimes have a very high USW like 6553. If you encounter such a card you may still be able to clean it. However it may require using BasicH 2.7 in Expert Mode. For a detailed procedure on how to do this please skip on down to the section called “Cleaning With BasicH 2.7 In Expert Mode”.
If your card info returned an
update between 26 and up to the update that is in the current datastream then
you may now go ahead and clean the card. However there is one other concern to
be considered. It has been reported that sometimes trying to clean older cards
with BasicH 2.7 can possibly result in a time out error. So what we recommend
is that if the card has a serial number in the range of 0000 4000 0000 - 0000
4999 9999 and you are getting timeout errors when you try to clean it using
BasicH 2.7 that you try cleaning the card with Viyada 1.6. Viyada 1.6 is actually an earlier version of
BasicH 2.7 before the name change to BasicH. So below are the procedures for
using Viyada 1.6 and BasicH 2.7. Also with both procedures we recommend doing
each step of the cleaning process manually and not to use the one step clean process. Now with the latest
releases of BasicH the problems that were present with earlier versions where
cards were sometimes looped appears to have been fixed according the author
Squeem. But we still just feel that manual cleaning is the better procedure to
use for cleaning a card since it allows you to see what steps are involved even
though cleaning manually will take a few more minutes and will require more
mouse clicks. But this shouldn’t matter since nobody should be in much of a
rush anyway when it comes to cleaning his or her cards anyway.
Note: If while
doing the following procedure you should get an error while trying to read the
EPROM image from the card saying that the E3 hole appears not to be then you
may have to instead clean the card using BasicH 2.7 in Expert Mode. If so
please skip down to the section called
“Cleaning With BasicH 2.7 In Expert Mode”. Also if you have an older H
card and the USW is at 29 or up to whatever the current update that is in the
datastream then first run BasicH 2.7 and roll the updates back to either 26.
This is required since Viyada 1.6 will not work with a card with updates higher
than 28.
Note: If while
doing the following procedure you should get an error while trying to read the
EPROM image from the card saying that the E3 hole appears not to be then you
may have to instead clean the card using BasicH 2.7 in Expert Mode. If so
please skip down to the section called
“Cleaning With BasicH 2.7 In Expert Mode”.
Note: The latest release of BasicH appears capable of removing stealth scripts in expert mode. However there also have been some reports that attempting to remove some scripts have resulted in looped cards. So just remember that attempting to do this can be very risky and if at all possible always remove any script from your card using whatever uninstall or remove script procedure is recommended by the programming script that is on the card. Removing a script from a card with BasicH in expert mode should be a last ditch effort used only if all else has failed.
Section Three – Programming Your H Card:
There are many scripts available (3M stealth, 3M non-stealth, activation etc.) for programming your card but we recommend and offer step-by-step instructions for two specific scripts in this guide, SummitStealth1.6b (SS1.6b) and DssStealthPro30D1 (DssSteathPro32a).
Note: If you currently have a previous SummitStealth script installed on your card and you have not removed and cleaned your card as yet then all you need to do is run the newly released SS1.6b and just do an update and you will be back up and running. No need to uninstall clean and then reinstall from scratch.
If ever you installed SS1.2a or any other script, you were generally asked to input a backdoor password somewhere during the installation. Well with the new versions of SummitStealth you are not required to input a password. User-selected passwords are GONE. SummitStealth now uses a new dynamic password backdoor. This dynamic password is unique to each card and changes automatically as the card is used. The password is automatically queried from the card when it is needed. Finally, the use of the PPV area to store information about the SummitStealth installation has been removed. This should alleviate any problems with this information not being found and allow full IRD functionality for scheduling PPV events, etc. that existed in earlier versions of SS. The script can also add the update 32, which is the current update in the datastream. I recommend that you read the Read Me file that comes with SummitStealth for all the other changes that were made to this new release.
OK so now lets begin the installation of SummitStealth.
Installing DssSteathPro32a
This latest release of DssStealthPro has gone to an option of using a dynamic key for the backdoor password. What this means is that you do not need to supply your own backdoor password if you choose to let the script generate and store the password. This feature is the same thing that SummitStealth now uses however with DssStealthPro you do have the option to use the dynamic key feature or if you prefer you can still input your own password if you prefer. And of course this release does now supports the 32 Update.
· Located and launch the DssSteathPro32a.xvb script that you previously unzipped. Now it is assumed here that you did what we recommended above and have made or verified the configuration change to WinExplorer 4.4. If not then you will need to run WinExplorer 4.4 first and then select the file menu, choose open script and then browse to wherever you have either saved the DssSteathPro32a files to when you unzipped them or where you moved them after unzipping. As you see this is more involved than if you had just done the configuration to WinExplorer like we recommended in the first place.
· Go to the card menu and select "execute script".
· The first dialogue box will warn you that the card needs to be cleaned before continuing. Since you already should have cleaned the card previously any update between 26 and 31 is acceptable. So you can select “Yes”.
· The next dialogue box will show the default settings. You will want to change some of these from the default setting so select “No”. This will now allow you to make the changes necessary to the following setting:
· Enter Update - Select the default setting will be whatever the current update currently in the datastream. This is a generic statement so that as the script changes and gets updated depending on the current update in the datastream I do not have to keep changing it here in the programming guide. I’m just trying to cut down on the amount of changes I need to make with each update. So just understand that as each new update of the script is released it will of course always default to whatever USW update the script was updated for (ex: DSSPro31 was updated for the 31 Update so it had a default of 31 and DSSPro32 was updated for the 32 Update so it had a default of 32 etc.).
· Enter USW – Again select the default setting.
· Enter Fuse Byte – Select the default of 25 DA ( Married_Activated)
· DTV Purchase Limit - Default is 300.00, which will be ok.
· Do you want to patch the CMD 48 Write? Again read this closely. We are at this time recommending selecting Yes since it is the default setting. We really don’t know much about this new option added to this release of DssSteathPro32a at this time but we are researching it.
· Do you want to block 2D Writes? Reading what this is asking is very confusing. We recommend that you block 2D Writes so that your card is as close to looking like a sub’d card as possible. This is also the default setting if you were to have selected all the default settings above. If you do chose to block 2D writes then just follow the instructions. It’s pretty straightforward.
· Do you want to cloak 8008 Data – If you are NOT installing this script onto a CLONED CARD then select “No”. If you DO NOT have the saved valid bin file that was used to clone the card then you should also select “No”. However if you are installing this script onto a cloned card and you do have the saved valid bin file that was used to clone the card then select “Yes”.
· You will now be asked if you want to use the default 8008 cloak data or to use the original card’s bin file. The original card’s bin file is referencing the saved valid bin file used to clone the card. We recommend that since you are electing to cloak the 8008 data that you elect to use the original card’s bin file. So answer “No”. No seems a bit confusing but if you read closely it is the correct answer.
· You will then be asked to select the original donor card’s bin file. Again this will be the saved valid bin file that you used to clone the card. So browse to wherever you have saved this bin file and select it.
· Enter Guide Byte - 4F will give you all the local network channels. But you can choose whatever you prefer. From time to time D** will test new channels that are to be added to the programming guide. Recently there have been a couple of UPN channels being tested. In order to be able to receive these new channels the guide byte needs to set to FF, which enables the full engineering guide. However be aware that this could possibly open you up to a potential ECM. We have never seen an ECM that targeted this area but it is still a potential risk. Also if there are no new channels actually being tested then this setting has no value.
· Enter Activation Date – Ignore this and just leave this at the default setting.
· Backdoor Key – first off the way the text is written at this step of installation it is a bit hard to understand. But I’ll try to explain it a bit better. You now have the choice of using the dynamic key password that is generated by the script or to enter your own password. Now if you choose to use the dynamic key the way we understand it is that it will work much like the way that the SummitStealth script implements this feature. In theory you would not have to remember this password if you wanted to remove or edit the script and I have verified that this feature does work. However with some limited testing it seems like it may not generate enough random keys, so if you do multiple cards and want each card to have a unique key this may be of some concern. Personally I would still input a unique password and of course if you do it is very important that you use something you can remember and to also write it down! Also it needs to be in hex format so birthdays (01 03 19 75) work real well but you can actually use any combination of the following Hex characters you like (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F). Also make sure that you leave a space between each two digits but do not put a space after the final 2 digits. In the end counting the spaces the string will include a total of 11 characters. Once again. After choosing the password please make sure to write this number down. If you ever need to remove this script or modify the card in the future this password will be required. If you forget or you lose it then you will not be able to do anything with the card other than send it out to be cleaned. So right now if you chose to supply your own password and haven’t done so write it down and put it in a safe place.
· Re-enter Backdoor Key – again if you inputted your own password then retype it exactly like before (hopefully you remember or wrote it down already). However if you chose to use the dynamic key then all should need to do is select OK.
· Final last chance to review and either agree to the settings you have set or say no to start over. Hopefully all the setting will be correct and you can just select “Yes”.
· Script will now install. When script has finished you will then get a window detailing a verification of the stealth and the also the updates of the card. You can go ahead and click “OK”.
· When finished you should see the following in the WinExp text window along with other information as well. Note the first line below where it gives a key to remove this script (ex: D4 C3 B2 A1). On your screen you will see the actual backdoor password that you selected during the installation. One last time to write it down if you haven’t already.
***
Use the RemoveDssSteathPro32a& D4 C3 B2 A1 key to remove this script!
***
DO NOT USE ANY REMOVER LESS THAN VERSION 32A ON THIS CARD WHEN REMOVING
SCRIPT!***