Archive

Archive for January, 2011

Using OpenSearch.xml

January 26, 2011 Leave a comment

 

If your website is searchable, then you can let your browser know how to search it, and create a shortcut search box in the top right of the user’s browser using a few lines of HTML and XML

Add the line

<link rel=”search” type=”application/opensearchdescription+xml” href=”/opensearch.xml” title=”.NET Source Code” />

to the head of the page, where opensearch.xml is:

<?xml version=”1.0″ encoding=”UTF-8″?>
<OpenSearchDescription xmlns=”http://a9.com/-/spec/opensearch/1.1/&#8221; xmlns:moz=”http://www.mozilla.org/2006/browser/search/”&gt;
<ShortName>.NET Source</ShortName>
<Description>.NET Framework source code</Description>
<InputEncoding>UTF-8</InputEncoding>
<Image height=”16″ width=”16″ type=”image/x-icon”>http://reflector.webtropy.com/images/favicon.ico</Image&gt;
<Url type=”text/html” method=”get” template=”http://reflector.webtropy.com/Search.aspx?search={searchTerms}” />
<moz:SearchForm>http://reflector.webtropy.com</moz:SearchForm&gt;
</OpenSearchDescription>

I’ve used this on my .NET Source code browser website.

 

Categories: Uncategorized

ModMii 4.4.5 Custom Guide for Wii

January 25, 2011 1 comment

ModMii 4.4.5 Custom Guide
Generated on 25/01/2011 – 18:48:55.34
Check for updates at tinyurl.com/ModMiiNow

This Guide was generated using the following parameters:

* Wii is currently a virgin (un-modified)
* Current firmware is 3.XE
* Desired firmware is 4.1E

* Download Extra Brick Protection
* Update active IOSs

* External Hard Drive to be Formatted as FAT32
* Download Configurable USB-Loader
* USB-Loader Settings and config files saved to USB Hard Drive

This software is not for sale. If you paid for this software or a “bundle” you have been scammed.

THIS PACKAGE COMES WITH ABSOLUTELY NO WARRANTY, NEITHER STATED NOR IMPLIED.
NO ONE BUT YOURSELF IS TO BE HELD RESPONSIBLE FOR ANY DAMAGE THIS MAY CAUSE TO YOUR NINTENDO WII CONSOLE!
USE THIS AT YOUR OWN RISK!

IMPORTANT NOTES:

*This guide does NOT require a Wifi connection on your Wii.
*An SD card formatted to FAT(32) required (Best results are with non-SDHC cards, SDHC will only work on 4.0 or above).
*If you get errors during any of the steps reformat your SD card as FAT or FAT32
*Turn off WiiConnect24 and take out all gamecube memory cards/controllers when modding the Wii (unless instructed otherwise).
*If your Wii ever freezes, hold the power button on the Wii for 5 seconds to power it off then try again.
*Don’t ever accept a new Nintendo update without first googling to see if it’s safe. The last update (to 4.3) was released in late June 2010 and is NOT safe to accept. If you accept an official Nintendo update after modding the Wii, you may lose some or all of your modifications.
*Never uninstall a system menu or IOS
*Do not install untested wads/themes without Bootmii or Priiloader installed.
*Not all external hard drive’s are compatible with the Wii, for a list of which USB Hard Drive’s are compatible, see this webpage: http://wiki.gbatemp.net/wiki/USB_Devices_Compatibility_List
*If you have questions, a more detailed guide can be found here: http://www.sites.google.com/site/completesg/
*This custom guide is great start, but Wii modding is always evolving. Check for updates online, and remember, google is your friend.
*If you have questions, a more detailed guide can be found here: http://www.sites.google.com/site/completesg/

1) INSTALLING THE HOMEBREW CHANNEL (HBC) AND BOOTMII
=================================================

Run BannerBomb v1 by going to Settings, Data Management, Channels, SD Card and choosing yes to load boot.dol/elf
Note: If it doesn’t work for you, visit http://bannerbomb.qoid.us/ for more variations of either version of bannerbomb.

This runs the Hackmii Installer (and silently/automatically installs BootMii as IOS). Use the installer to install the Homebrew Channel (HBC) and Bootmii as Boot2 if possible. If you cannot install BootMii as Boot2, you also need to ‘prepare an SD Card’ for BootMii (as the ‘BootMii’ folder is required to launch BootMii as IOS or Boot2).

Note: If you get a ‘no vulnerable IOS’ error message, run ModMii again and this time select the ‘Hackmii Solutions’ option instead of ‘ModMii Wizard’ and follow the new instructions before continuing this guide.

After you exit the hackmii installer, you will be taken to the HBC.
Hit the home button. In the top right corner you will see the IOS used by the HBC.

If the HBC is using an IOS other than IOS58 or your homebrew channel is upside-down, make a note of it as it applies later in the guide (you will have to reinstall the HBC).

If it is using IOS58 and your HBC is not upside-down, you can skip the Reinstall The Homebrew Channel step when you get to it.

2) MAKING A NAND BACKUP
====================

While inside the Homebrew Channel, load BootMii by pressing home and clicking Launch Bootmii.
Press the power button on the wii 3 times to get to the last option, then press the reset button. [You can also navigate with a Gamecube controller]

Press reset to choose the first option, then follow the directions on the screen to make your NAND backup. [Bad blocks are no problem.]

Backup the Bootmii folder, NAND.bin, and keys.bin elsewhere and erase from the sd card (or rename it). You’ll need these in case of emergencies, so don’t lose them.
Go back to The Homebrew Channel.

Note: if Bootmii was installed as boot2, then it will show up as soon as the Wii is turned on AS LONG AS it finds the bootmii folder (mentioned above) on the root of the SD card.

3) INSTALL A PATCHED IOS236
========================

Start the Homebrew Channel.

VERY IMPORTANT!
In the Homebrew channel, if you do not have a working internet connection already set up, you will see an icon flashing in the bottom right corner of the screen indicating its inability to initialize the network. You MUST wait for the icon to stop flashing OR let it flash for 30-60 seconds before proceeding otherwise these apps will error shortly after being launched. If you encounter this harmless error, power off the Wii and repeat this step from the beginning. To increase your chances of success, add a working internet connection to your Wii via the official Wii Settings Menu, but be sure to say “No” when asked to perform an update.

You only need to perform ONE of the below methods.

Method A: Using IOS236 Installer
——————————–

After waiting 30-60 seconds for the HBC to attempt to initialize the network, launch “IOS236 Installer v5 MOD”.
Note: This app must be launched using HBC v1.0.7 or higher in order to work properly.

It should say “IOS236 installation is complete!” and return to The Homebrew Channel.

If you experience errors, keep trying and it should eventually work.
If you continue to experience errors you can try using Simple IOS Patcher instead.
Once either method successfully installs IOS236, you can move onto the next step.

Method B: Using Simple IOS Patcher
———————————-

After waiting 30-60 seconds for the HBC to attempt to initialize the network, launch “IOS236 Installer”.
Note: This app must be launched using HBC v1.0.7 or higher in order to work properly.

Choose “IOS36” (already selected by default) and push A,
Select “Install IOS to slot” and choose 236,
Select “Install patched IOS36” leaving the 4 patches set to “yes” and press A,
Choose “Load IOS from SD card”.

Confirm your choice with the A button,
When prompted, push A to continue the installation.
When the installation is over you’ll be back at the Main Menu,
Then push B button to exit.

If you experience errors, keep trying and it should eventually work.
If you continue to experience errors you can try using IOS236 Installer instead.
Once either method successfully installs IOS236, you can move onto the next step.

4) INSTALL WADS
============

Load Multi-Mod Manager (MMM) via the HomeBrew Channel.
If IOS236 is not already loaded, select “Load another IOS”, then select IOS236

Note: If this step fails with error -ret 2011 or other, you may need to retry patching IOS236. If the Wii was previously softmodded, you can try loading cIOS250 (or others like 202,222,223,224,236,249)

In Multi-Mod Manager’s main menu, go down to select “WAD Manager”.

Install the following WADs from the WAD folder (this list of WADs is unique to how you answered the Wizard’s questions).

Be careful not to install any additional wads that may have been previously saved in this folder (they may be safe, but I cannot say for sure).

Hold + for 2 seconds to select all the WADs in the folder. Then Press A twice to install them all.
If any files fail to install properly, they will remain marked for installation, so just retry installing those files.

Your unique list of wads to install are as follows:

* IOS11v16174(IOS60v6174[FS-ES-NP])
* IOS20v16174(IOS60v6174[FS-ES-NP])
* IOS30v16174(IOS60v6174[FS-ES-NP])
* IOS50v14889(IOS50v4889[FS-ES-NP])
* IOS60v16174(IOS60v6174[FS-ES-NP])
* IOS70v16687(IOS70v6687[FS-ES-NP])
* SystemMenu_4.1E_v450
* cIOS202[57]-v5
* cIOS223[37-38]-v4
* cIOS222[38]-v5
* cIOS224[57]-v5
* cIOS250[57]-v20
* cIOS249[56]-v20
* RVL-cmios-v4_WiiGator_GCBL_v0.2
* IOS9-64-v1034
* IOS12-64-v526
* IOS13-64-v1032
* IOS14-64-v1032
* IOS15-64-v1032
* IOS17-64-v1032
* IOS21-64-v1039
* IOS22-64-v1294
* IOS28-64-v1807
* IOS31-64-v3608
* IOS33-64-v3608
* IOS34-64-v3608
* IOS35-64-v3608
* IOS36-64-v3608
* IOS37-64-v5663
* IOS38-64-v4124
* IOS41-64-v3607
* IOS43-64-v3607
* IOS45-64-v3607
* IOS46-64-v3607
* IOS48-64-v4124
* IOS53-64-v5663
* IOS55-64-v5663
* IOS56-64-v5662
* IOS57-64-v5919
* IOS58-64-v6176
* IOS61-64-v5662
* USBLoader(s)-ahbprot58-SD-USB-v8-IDCL
This is a forwarder channel that will load the first file it finds from the following list:
SD+USB:\apps\usbloader\boot.dol
SD+USB:\apps\usbloader\boot.elf
SD+USB:\apps\usb-loader\boot.dol
SD+USB:\apps\usb-loader\boot.elf
SD+USB:\apps\usbloader_cfg\boot.dol
SD+USB:\apps\usbloader_cfg\boot.elf
SD+USB:\apps\WiiFlow\boot.dol
SD+USB:\apps\WiiFlow\boot.elf
SD+USB:\apps\usbloader_gx\boot.dol
SD+USB:\apps\usbloader_gx\boot.elf
Notes: IOS58 is required to launch apps from an SD Card and hard drives formatted as
FAT32, NTFS, ext2, ext3 and ext4. It also supports meta.xml arguments
and is able to launch apps with direct hardware access.
You should always have at least one forwarder channel installed on your Wii,
that way, in the event of accidental update, you will be able to rehack your Wii without relying on a disc based exploit

Note: Whenever you install a new System Menu, Priiloader is uninstalled. So be sure to reinstall it afterwards (especially if you do not have bootmii as boot2)

5) INSTALL PRIILOADER
==================

Launch “Priiloader 236” via the Homebrew Channel

After the Priiloader Installer loads, press + to install it.

You may get an error for “loader.ini” and/or “password.txt” simply ignore these.

After successfully installing Priiloader, access it by powering off the Wii,
then powering it back on while holding reset until you see the Priiloader menu.

You should install some system menu hacks now (by going to System Menu hacks option).

RECOMMENDED HACKS: Block Disc Updates, Block Online Updates, Replace Health Screen, Auto-Press A at Health Screen, Region-Free Everything, remove no copy save file protection, and Move Disc Channel.

The priiloader menu is white by default, you can change it to black in the Priiloader settings if you prefer.

One of the special functions of Priiloader is that it can autoboot any app/file instead of the system menu. Some apps (like crazyIntro) can’t be used without it.
For details on how to do so, visit http://www.sites.google.com/site/completesg/system-hacks/priiloader

6) REINSTALL THE HOMEBREW CHANNEL (if applicable)
==============================================

Earlier you should have checked what IOS is used by the Homebrew Channel (HBC). If the IOS used by your HBC is IOS58 and your HBC is not upside-down, you can skip this step.

If the HBC is using an IOS other than IOS58 or your HBC is upside-down, you should reinstall the HBC.

Launch the HackMii_Installer via the HBC.
Use the Hackmii Installer to fix/re-install the HBC. Once you’ve successfully reinstalled the HBC, you can move onto the next step of the guide.

If the HBC is failing to load the HackMii_Installer (just blackscreens), instead launch the Hackmii Installer using the method described in the First Step

======================================================================================
THE REST OF THE GUIDE IS PERFORMED ON YOUR COMPUTER IN ORDER TO SET UP YOUR USB-LOADER
======================================================================================

7) FORMAT THE EXTERNAL HARD DRIVE (if applicable)
==============================================

First check if your drive needs to be formatted by checking the current Format\File-System of the drive.
Open ‘My Computer’, right-click the external hard drive you want to use, then select ‘properties’.
Make note of the Drive Letter of the external hard drive as this will be important later.
If the ‘File-System’ is already FAT32, you can skip this step.

If you have anything saved on the hard drive, you should back it up now as all the data will be lost once you format it.

Launch FAT32_GUI_Formatter.exe saved here:
D:\FAT32_GUI_Formatter\FAT32_GUI_Formatter.exe

Make sure you select the drive letter corresponding to your external hard drive.
You may optionally uncheck the ‘Quick Format’ box, then click start.

8) COPY FILES TO HARD DRIVE
========================

Copy everything inside the D: folder to the root of your FAT32 hard-drive\partition.

9) MANAGE WII BACKUPS USING WII BACKUP MANAGER (OPTIONAL)
======================================================

Launch WiiBackupManager.exe saved here:
D:\WiiBackupManager\WiiBackupManager.exe

You can use this program to manage/transfer your electronic backups of Wii Games.
It is very simple to use, but a detailed tutorial on using Wii Backup Manager can be found here:
http://www.sites.google.com/site/completesg/backup-launchers/iso/wbfs-managers/wii-backup-manager

Note: Original Wii Disc’s cannot be read/copied by using a computer (unless you have one of the rare LG Drives that is capable of doing so)

To copy ORIGINAL Wii Disc’s, insert the disc into your Wii and…
– Launch Configurable USB-Loader, and hit the plus sign ‘+’.

10) CONFIGURE/CUSTOMIZE CONFIGURABLE USB-LOADER (OPTIONAL)
======================================================

To Configure/Customize your USB-Loader, use the Configurator for Configurable USB-Loader found here:
D:\usb-loader\CfgLoaderConfigurator.exe

Optional: additional themes can be found here:
http://wii.spiffy360.com/themes.php

* IMPORTANT NOTES ON DEFAULT SETTINGS:
————————————

Two potentially dangerous features have been locked:
1) The ability to remove/delete games
2) the ability to format a hard drive.

To unlock these features, while in the configurable USB-Loader menu, hold ‘1’ for 5 seconds, then enter the password to unlock these features. The password is ‘AAAA’, you can change the password/settings by using the Configurator for Configurable USB-Loader. Hold ‘1’ again for 5 seconds to lock the USB-Loader again (or it will lock automatically again once you exit the USB-Loader).

11) AFTER MODDING
=============

After you are done modding your Wii, you can optionally delete any unnecesarry files
by using ModMii’s “File Cleanup” Feature.

If you choose not to use the File Cleanup feature, in order to avoid having your Wii freeze when accessing the SD Card Menu, you should delete the ‘aktn’ folder where bannerbomb is saved (SD:\private\wii\title\aktn), or rename the entire ‘private’ folder.

At this point you’re practically done.
Now you should be downloading the latest homebrew applications and setting them up on
your SD Card (or FAT32 USB Hard Drive) so they can be launched via the HBC.

For downloading applications, you should:
* Check out ModMii’s batch download pages as it has many popular apps available for download.
* Download Homebrew Browser via ModMii to get many popular apps, but this is an online only Wii application (www.sites.google.com/site/completesg/how-to-use/hbb)
* For those without internet on their Wii, check out this list of Homebrew applications (wiibrew.org/wiki/List_of_all_homebrew).
Another great resource is webrewwii.blogspot.com

After getting whatever apps you want, you should get a boot.dol file and possibly a icon.png and meta.xml.
For HBC to read your SD/USB correctly, your card must be structured SD:/apps/application name/boot.dol
If you have a *.dol not named boot.dol, rename it boot.dol, otherwise it will not be recognized by the HBC.
(optional: the icon.png and meta.xml should be saved in the same place as the boot.dol)

12) SUPPORT XFLAK
=============

IF MODMII WORKED FOR YOU, PLEASE VOTE IN FAVOUR OF THE PROGRAM HERE (tinyurl.com/ModMiiNow)

DONATIONS CAN OPTIONALLY BE MADE VIA PAYPAL TO XFLAK40@HOTMAIL.COM

CHECK OUT MY TOP CHANNELS HERE (tinyurl.com/topchannels)

CHECK OUT MY CRAZY INTRO VIDEOS HERE (tinyurl.com/crazyintro)

Categories: Uncategorized

Skype Attach protocol 8

January 23, 2011 5 comments

This is an update to my previous post about getting Skype to attach from the C# API, the problem is, that you should attach asynchronously, and handle the attachement event

((_ISkypeEvents_Event)skype).

AttachmentStatus += OurAttachmentStatus;
skype.Attach(8, false);
Where OutAttachementStatus can be as follows:
void OurAttachmentStatus(

TAttachmentStatus status)
{
Attached = false;

try
{
Debug.WriteLine(DateTime.Now.ToLocalTime() + ” Attachment Status: ” + skype.Convert.AttachmentStatusToText(status));
}
catch (Exception ex)
{
Debug.WriteLine(DateTime.Now.ToLocalTime() + ” Error: ” + ex.Message + ” Unable to write Skype attach status change”);
}

if (status == TAttachmentStatus.apiAttachAvailable)
{
try
{
skype.Attach(8, true);
}
catch (Exception ex)
{
Debug.WriteLine(DateTime.Now.ToLocalTime() + ” Error: ” + ex.Message + ” Unable to send Skype API Attach Request Message”);
}
}
else
if (status == TAttachmentStatus.apiAttachSuccess)
{
Attached = true;
WasAttached = true;
}
}

On first attach, it asks for permission from the locally running Skype Client, if granted, then it’s not asked for again,
and the attachment works alot faster.
You can then do cool stuff, like search for users:
foreach (User user in skype.SearchForUsers(“bob”))
I’ve found that “user” has the following ‘interesting’ properties:
Handle – banzigof
FullName – fiach
Country – France
City – strasbourg
CountryCode – fr
I’ve put together a skype contact browser, running off a MySQL database
The list is semi-random, so it’ll always show cities with over 500 users, but can randomly push smaller cities into the list.

select city,count(*) as count from skypeUsers group by city order by count(*) + rand()*500 desc
limit 50

Categories: Uncategorized

Getting started with Skype for C#

January 20, 2011 1 comment

I’m trying to connect to Skype from c#, but not very sucessfully. Hopefully I’ll crack this in the future …

Using the code snippet:

Skype skype = new Skype();
if (!skype.Client.IsRunning)
{
// start minimized with no splash screen
skype.Client.Start(true, true);
}

// wait for the client to be connected and ready
skype.Attach(8, true); // Not 6?

But then skype gives the error:

Another Application (blah.exe) is attempting to access Skype but we are unable to respond.Please try again later.

Although SEHE, the testing app for the API does work, with the messages:

20/01/2011 10:17:14:  Our Code – SEHE 1.0.31.12 Copyright By Don Kennedy aka TheUberOverLord@gmail.com – Tested with Skype4COM Lib version 1.0.31.0 Skype Windows client 3.8.0.188 Standard Version  3.8.32.188 – Business Version – 4.0.0.169 Beta Version
20/01/2011 10:17:14:  Our Code – TheUberOverLord_Initialize: Main Logic
20/01/2011 10:17:14:  Our Code – FirstTime: True
20/01/2011 10:17:14:  Our Code – AutoScrollOn_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – UseAutoDebug_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – NonWaitedAttachRequests_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – SkypeStop_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – UserLogoff_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – StartNoSplash_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – StartSkype_CheckedChanged: True
20/01/2011 10:17:33:  Our Code – Skype Attachment Request Non-Waited Sent
20/01/2011 10:17:33: Attachment Status – Converted Status: Pending Authorization – TAttachmentStatus: apiAttachPendingAuthorization
20/01/2011 10:17:34:  Our Code *** Check The Skype Window to Allow this Program ***  – Check New Events at the top right of the Skype Window  – Then click on the link under plugin authorization
20/01/2011 10:18:39: Attachment Status – Converted Status: API Available – TAttachmentStatus: apiAttachAvailable
20/01/2011 10:18:39:  Our Code – Non-Waited Attachment Sent
20/01/2011 10:18:40: Attachment Status – Converted Status: Pending Authorization – TAttachmentStatus: apiAttachPendingAuthorization
20/01/2011 10:18:40:  Our Code *** Check The Skype Window to Allow this Program ***  – Check New Events at the top right of the Skype Window  – Then click on the link under plugin authorization
20/01/2011 10:19:15: Connection Status – Converted TConnectionStatus Status: Connecting – TConnectionStatus: conConnecting
20/01/2011 10:19:15: User Status – TUserStatus Converted Status: Offline – TUserStatus: cusOffline
20/01/2011 10:19:16: Attachment Status – Converted Status: Success – TAttachmentStatus: apiAttachSuccess
20/01/2011 10:19:16:  Our Initialization Logic – Begin
20/01/2011 10:19:16:   Skype Ver: 4.2.0.187 – Skype4COM Ver: 1.0.31.0 – Protocol: 8 – Timeout: 30000
20/01/2011 10:19:16:   User: fiach.reid – SkypeOut: False – SkypeIn: False – Voicemail: False
20/01/2011 10:19:16:   PSTN Balance Currency: FREECALL – PSTN Balance: 100
20/01/2011 10:19:16:   Calls Go To Voicemail: FALSE – Calls Go To Call Forwarding: FALSE – Call Forward Rules:  – SMS Validated Numbers:
20/01/2011 10:19:16:   Language: en – Predictive Dialer Country: us – IP Country:  us
20/01/2011 10:19:16:   Audio In: Microphone (Realtek High Definition Audio) – Audio Out: Speakers (Realtek High Definition Audio)
20/01/2011 10:19:16:   Video In: Chicony USB 2.0 Camera
20/01/2011 10:19:16:   Auto Away: True – PC Speaker: False – Ringer:  – Users waiting for authorization: 0
20/01/2011 10:19:16:   AEC: True – AGC: True – Voicemails: 0  – Mute: False
20/01/2011 10:19:16:  Our Initialization Logic – End

20/01/2011 10:17:14:  Our Code – SaveText_CheckedChanged: True
20/01/2011 10:17:14:  Our Code – UseCommandId_CheckedChanged: True – Command Id Reset To: 10000
20/01/2011 10:19:15: Command – Command Id: 1 – Command: PROTOCOL 9 – Expected: PROTOCOL  – Blocking: True – Timeout: 30000
20/01/2011 10:19:15: Reply – Command Id: 0 – Reply: CONNSTATUS CONNECTING – Expected:  – Blocking: False – Timeout: 30000
20/01/2011 10:19:15: Reply – Command Id: 0 – Reply: CURRENTUSERHANDLE fiach.reid – Expected:  – Blocking: False – Timeout: 30000
20/01/2011 10:19:15: Reply – Command Id: 0 – Reply: USERSTATUS OFFLINE – Expected:  – Blocking: False – Timeout: 30000
20/01/2011 10:19:15: Reply – Command Id: 1 – Command: PROTOCOL 9 – Reply: PROTOCOL 8 – Expected: PROTOCOL  – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 2 – Command: GET SKYPEVERSION – Expected: SKYPEVERSION – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 2 – Command: GET SKYPEVERSION – Reply: SKYPEVERSION 4.2.0.187 – Expected: SKYPEVERSION – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 3 – Command: #3 GET PRIVILEGE SKYPEOUT – Expected: #3 PRIVILEGE SKYPEOUT – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 3 – Command: #3 GET PRIVILEGE SKYPEOUT – Reply: #3 PRIVILEGE SKYPEOUT FALSE – Expected: #3 PRIVILEGE SKYPEOUT – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 4 – Command: #4 GET PRIVILEGE SKYPEIN – Expected: #4 PRIVILEGE SKYPEIN – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 4 – Command: #4 GET PRIVILEGE SKYPEIN – Reply: #4 PRIVILEGE SKYPEIN FALSE – Expected: #4 PRIVILEGE SKYPEIN – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 5 – Command: #5 GET PRIVILEGE VOICEMAIL – Expected: #5 PRIVILEGE VOICEMAIL – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 5 – Command: #5 GET PRIVILEGE VOICEMAIL – Reply: #5 PRIVILEGE VOICEMAIL FALSE – Expected: #5 PRIVILEGE VOICEMAIL – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 6 – Command: #6 GET PROFILE PSTN_BALANCE_CURRENCY – Expected: #6 PROFILE PSTN_BALANCE_CURRENCY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 6 – Command: #6 GET PROFILE PSTN_BALANCE_CURRENCY – Reply: #6 PROFILE PSTN_BALANCE_CURRENCY FREECALL – Expected: #6 PROFILE PSTN_BALANCE_CURRENCY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 7 – Command: #7 GET PROFILE PSTN_BALANCE – Expected: #7 PROFILE PSTN_BALANCE – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 7 – Command: #7 GET PROFILE PSTN_BALANCE – Reply: #7 PROFILE PSTN_BALANCE 100 – Expected: #7 PROFILE PSTN_BALANCE – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 8 – Command: #8 GET PROFILE CALL_SEND_TO_VM – Expected: #8 PROFILE CALL_SEND_TO_VM – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 8 – Command: #8 GET PROFILE CALL_SEND_TO_VM – Reply: #8 PROFILE CALL_SEND_TO_VM FALSE – Expected: #8 PROFILE CALL_SEND_TO_VM – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 9 – Command: #9 GET PROFILE CALL_APPLY_CF – Expected: #9 PROFILE CALL_APPLY_CF – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 9 – Command: #9 GET PROFILE CALL_APPLY_CF – Reply: #9 PROFILE CALL_APPLY_CF FALSE – Expected: #9 PROFILE CALL_APPLY_CF – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 10 – Command: #10 GET PROFILE CALL_FORWARD_RULES – Expected: #10 PROFILE CALL_FORWARD_RULES – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 10 – Command: #10 GET PROFILE CALL_FORWARD_RULES – Reply: #10 PROFILE CALL_FORWARD_RULES  – Expected: #10 PROFILE CALL_FORWARD_RULES – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 11 – Command: #11 GET PROFILE SMS_VALIDATED_NUMBERS – Expected: #11 PROFILE SMS_VALIDATED_NUMBERS – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 11 – Command: #11 GET PROFILE SMS_VALIDATED_NUMBERS – Reply: #11 PROFILE SMS_VALIDATED_NUMBERS  – Expected: #11 PROFILE SMS_VALIDATED_NUMBERS – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 12 – Command: #12 GET UI_LANGUAGE – Expected: #12 UI_LANGUAGE – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 12 – Command: #12 GET UI_LANGUAGE – Reply: #12 UI_LANGUAGE en – Expected: #12 UI_LANGUAGE – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 13 – Command: #13 GET PREDICTIVE_DIALER_COUNTRY – Expected: #13 PREDICTIVE_DIALER_COUNTRY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 13 – Command: #13 GET PREDICTIVE_DIALER_COUNTRY – Reply: #13 PREDICTIVE_DIALER_COUNTRY us – Expected: #13 PREDICTIVE_DIALER_COUNTRY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 14 – Command: #14 GET PROFILE IPCOUNTRY – Expected: #14 PROFILE IPCOUNTRY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 14 – Command: #14 GET PROFILE IPCOUNTRY – Reply: #14 PROFILE IPCOUNTRY us – Expected: #14 PROFILE IPCOUNTRY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 15 – Command: #15 GET AUDIO_IN – Expected: #15 AUDIO_IN – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 15 – Command: #15 GET AUDIO_IN – Reply: #15 AUDIO_IN Microphone (Realtek High Definition Audio) – Expected: #15 AUDIO_IN – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 16 – Command: #16 GET AUDIO_OUT – Expected: #16 AUDIO_OUT – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 16 – Command: #16 GET AUDIO_OUT – Reply: #16 AUDIO_OUT Speakers (Realtek High Definition Audio) – Expected: #16 AUDIO_OUT – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 17 – Command: #17 GET VIDEO_IN – Expected: #17 VIDEO_IN – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 17 – Command: #17 GET VIDEO_IN – Reply: #17 VIDEO_IN Chicony USB 2.0 Camera – Expected: #17 VIDEO_IN – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 18 – Command: #18 GET AUTOAWAY – Expected: #18 AUTOAWAY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 18 – Command: #18 GET AUTOAWAY – Reply: #18 AUTOAWAY ON – Expected: #18 AUTOAWAY – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 19 – Command: #19 GET PCSPEAKER – Expected: #19 PCSPEAKER – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 19 – Command: #19 GET PCSPEAKER – Reply: #19 PCSPEAKER OFF – Expected: #19 PCSPEAKER – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 20 – Command: #20 GET RINGER – Expected: #20 RINGER – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 20 – Command: #20 GET RINGER – Reply: #20 RINGER  – Expected: #20 RINGER – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 21 – Command: #21 SEARCH USERSWAITINGMYAUTHORIZATION – Expected: #21 USERS  – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 21 – Command: #21 SEARCH USERSWAITINGMYAUTHORIZATION – Reply: #21 USERS  – Expected: #21 USERS  – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 22 – Command: #22 GET AEC – Expected: #22 AEC – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 22 – Command: #22 GET AEC – Reply: #22 AEC ON – Expected: #22 AEC – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 23 – Command: #23 GET AGC – Expected: #23 AGC – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 23 – Command: #23 GET AGC – Reply: #23 AGC ON – Expected: #23 AGC – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 24 – Command: #24 SEARCH VOICEMAILS – Expected: #24 VOICEMAILS  – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 24 – Command: #24 SEARCH VOICEMAILS – Reply: #24 VOICEMAILS  – Expected: #24 VOICEMAILS  – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Command – Command Id: 25 – Command: #25 GET MUTE – Expected: #25 MUTE – Blocking: True – Timeout: 30000
20/01/2011 10:19:16: Reply – Command Id: 25 – Command: #25 GET MUTE – Reply: #25 MUTE OFF – Expected: #25 MUTE – Blocking: True – Timeout: 30000

 

Categories: Uncategorized

Nand.bin BootMii Wii Backup

January 18, 2011 Leave a comment

Here is the Nand.Bin backup from the BootMii program for the Wii

www.wikiencyclopedia.net/wii/NandBin.zip

 

Categories: Uncategorized

BINARY_CHECKSUM vs HASHBYTES in SQL

January 14, 2011 Leave a comment

If you need to create a short checksum or hash code in SQL, you can use CHECKSUM, BINARY_CHECKSUM or HASHBYTES.

HASHBYTES is the best for ensuring lower collisions, whereas BINARY_CHECKSUM is worst. But for performance, here is a comparison on a 1 million row table.

 

declare @timeStart as datetime
set @timeStart = getdate()
select MAX(hashbytes(‘MD5’,x)) from y
select datediff(ms,@timestart,getdate())

checksum = 370,363,370,410,356 = 373 ms
binary_checksum = 403,356,360,390,356 = 373 ms
MD5 = 2083, 1976, 1743 , 1746 , 1753 = 1860 ms

Therefore, Binary_Checksum is 5 times faster than MD5 HASHBYTES, and the same speed as checksum.

So, my advice,

Iif you need speed over accuracy – use CHECKSUM, not BINARY_CHECKSUM.

If you need accuracy over speed  – use HASHBYTES.

 

Categories: Uncategorized