My notes, things I have learned, and documentation I have created.

The default Windows Photo Viewer does not give you the same printer options when dealing tiff files containing many pages.

The solution I have used on a Windows 7 machine with Office 2010 already installed is to download and install the Microsoft Office Document Imaging portion of .

I started by choosing a custom installation and setting everything to Not Available. Then, under Office Tools I chose Microsoft Office Document Imaging and selected Run all from My Computer, and proceeded through the installation.

Once installed, I right moused clicked on a tiff file, and selected “Open with.” Then, I selected “Choose default program.” Click Browse, and navigate to C:\Program Files\Common Files\microsoft shared\MODI\12.0 and select MSPVIEW.EXE. Ensure that “Always use the select program to open this kind of file” is checked, if you want to open all tiff file with this application.

This will allow you print the entire tiff or select pages to print as you could previously with Windows Photo Viewer.

Used the following method to move comments in WordPress 3.

Key information needed:

Determine the post ID (comment_post_ID) for where the comment was made. You can determine this from the WordPress Dashboard. In this post, (http://jim-zimmerman.com/?p=781) 781 is the comment_post_ID.

Determine the post ID (comment_post_ID)for where the comment should go.

Determine the comment ID (comment_ID). There are many ways you could determine this, but you should probably choose something unique to the comment like the comment_author_email that you should be able to get from the comment.

Move the comment:

mysql> UPDATE wp_comments SET comment_post_id=”newcommentpostid” WHERE comment_post_ID=”oldcommentpostid” AND comment_author_email=”commentauthoremail“;

Determine the number of comments where the post has moved to:

mysql> SELECT COUNT(*) FROM wp_comments WHERE comment_post_id=”newcommentpostid“;

Determine the updated number of comments for the post where the comment was originally made:

mysql> SELECT COUNT(*) FROM wp_comments WHERE comment_post_id=”oldcommentpostid“;

Update the counts for each of the posts:

mysql> UPDATE wp_posts SET comment_count=”newcommentcountwhereadded” WHERE id=”newpostid“;

mysql> UPDATE wp_posts SET comment_count=”newcommentcountwhereremoved” WHERE id=”oldpostid“;

Well, I finally got around to looking into getting Ice Cream Sandwich (Android 4.0.x) on my original Samsung Galaxy Tab. This is extremely experimental, and I can tell you that I had no 3G access using the 20120704 nightly build. However, the 20120708 build does seem to be working. I don’t believe that this due to the build, but that at some point in the process, I didn’t do a “wipe data” and “wipe cache”. From a stability perspective, you might want to stick with Gingerbread, and go with the latest Overcome version to get Android 2.3.6, however despite the rough start it does seem to be working well and I like ICS a lot.

Anyway, I am going to try recall the steps I took to get to this point. I usually try to document as I go when getting into these things, but this one was a challenge. However, I do feel that I have the basics, since I went through this several times.

There are two important things that are key. One is being able to get your Tab back to stock Ginderbread using Overcome. The other is getting the correct CWM Recovery version (5.5.0.4) installed.

I used Windows 7 64 bit to run ODIN to install the Overcome related ROMs.

Software:
Here is the source for all the Overcome software used: http://www.teamovercome.net/p1000/?page_id=17]

Stock safe Gingerbread: http://www.teamovercome.net/p1000/wp-content/plugins/download-monitor/download.php?id=1

Overcome Kernel: http://www.teamovercome.net/p1000/wp-content/plugins/download-monitor/download.php?id=4

Overcome 4.1.0 Wipe Edition ROM: http://www.teamovercome.net/p1000/wp-content/plugins/download-monitor/download.php?id=2

Modem (Modem-TMO.zip): http://www.teamovercome.net/p1000/wp-content/plugins/download-monitor/download.php?id=9

Cyanogenmod 9: http://get.cm/?device=p1 Note: There are different versions for the CDMA Tabs. The T-Mobile version is referred to as the p1 version. p1c is the CDMA version.

Google Apps: http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip

Cyanogenmod 9 T-Mobile Modem software: (modem-galaxytab-t849uvjjb.zip): http://cmw.22aaf3.com/p1/p1/radio/modem-galaxytab-t849uvjjb.zip

Process used:
Ensure that your computer is able to see the device properly. Windows 7 should be able to detect the Galaxy Tab without issue.

With all the software downloaded to a working directory, unzip GB-Stock-Safe-v5.zip, and the Modem-TMO.zip files.

Put the Tab into Download mode. To put it into Download mode, power it off. Then, hold the power button and the volume down on the volume rocker. Connect the Tab to your computer via the USB cable.

Start odin. Note: I am not sure what the deal with this is, but it is not clear where you can find this. I have been using a very old version, however, I did find this link to a version from 5/25/2012: http://androidfirmwares.net/Tools/Download/8 and other file sharing sites. You will know that the drivers used to detect the Tab are sufficient, if you see “COM:#” highlighted in ODIN.

Click the PIT button, and browse to and select the gt-p1000_mr.pit from the GB-Stock-Safe-v5 directory.

Click the PDA button, and browse to and select the GB_Stock_safe_v5.tar file from the GB-Stock-Safe-v5 directory.

Next, click the PHONE button, and browse to and select the modem.bin file in the Modem-TMO directory. NOTE: It is very important that you select the correct modem software. These are the instructions I used on a U.S. T-Mobile Galaxy Tab.

Click the START button. You should see a PASS notification appear in ODIN once complete, and the Tab will reboot.

This will install a fresh stock version of Gingerbread. Next, you need to install the Overcome kernel.

Run through the wizard on the Tab, and enable Mass Storage. Unplug the device, go to Settings/Wireless and Network/USB Settings and choose Mass Storage. Plug the Tab back in, and copy the Overcome_7_Series_v4.1.0_Wipe.zip file to the root of the Tab.

Power off the Tab and put in back into Download mode.

Launch ODIN, and use the same files for the PIT option and the MODEM option. However, for the PDA option select the Overcome_Kernel_v4.0.0.tar you downloaded earlier.

Click the START button. This time when it reboots the file system will be converted. This will take some time.

Once up, you need to put the Tab in Recovery Mode. Power off the Tab. Hold the power and volume up on the volume rocker. To navigate around these menus, you the volume rocker to move up and down, and the power button to select. Navigate to the “install menu”, and select “choose zip from internal sdcard.” Select the Overcome_7_Series_v4.1.0_Wipe.zip file copied to the Tab earlier.

Once completed, navigate to the reboot menu, and reboot the Tab. At this point, you should have Gingerbread 2.3.6 on your Tab.

Once up, disconnect the Tab from the computer, run through the wizard again and enable Mass Storage.

Plug the Tab back in, and copy the download CyanogenMod (cm-9-yyyymmdd-NIGHTLY-p1.zip), the Cyanogenmod 9 T-Mobile Modem software: (modem-galaxytab-t849uvjjb.zip), and Google Apps (gapps-ics-20120317-signed.zip) to the root of the Tab.

Put the Tab back in Recovery Mode, and choose the cm-9-yyyymmdd-NIGHTLY-p1.zip copied to the root of the Tab from the “choose zip from internal sdcard” option.

Now, this is where this get a little fuzzy for me. I believe I had boot issues at this point with 20120704 nightly build, however I noticed that the CWM Recovery version was now 5.5.0.4, so I did a “wipe data/factory reset” and a “wipe cache partition”. Then, I tried again and this time I also select the Google apps zip copied earlier and the T-Mobile Modem software: (modem-galaxytab-t849uvjjb.zip). This time ICS came up, and 3G worked, and seems to be working much better than I expected.

Below is a site that lists nightly changes, so you can determine whether you want to update:

CyanogenMod9 Changelog site: http://changelog.bbqdroid.org/#tenderloin/cm9

It would appear that using a ROM Manager is really not supported on this version of the Galaxy Tab. I haven’t tried to use it, because I have found nothing that indicates that it is supported.

So, if you want to update to a newer nightly build, I would recommend downloading the build and copying it to the root of the Tab and install it from Recovery Mode via “choose zip from internal sdcard”. You should probably do a “wipe data/factory reset” and a “wipe cache partition” prior to installing the update too.

UPDATE: I did an update to a last night’s build, and did not have to “wipe data” or “wipe cache”. It just took awhile for the 3G to come up after the first boot. Since then, it has been fine. Maybe you just need a little patience when installing the nightly builds.

Click the Home tab.

Click the Junk drop down in the Delete section, and go to Junk E-Mail Options.

Select the “No Automatic Filtering …” option.

Note: this will work as long as you do not have a group policy that sets this.

You can also access the Junk E-Mail Options by right mouse clicking on a message, going to Junk and select Junk E-Mail Options.

I suppose the first question is why downgrade the baseband now? Well, I got AT&T to unlock my 06.15.00 baseband 3Gs when it was announced that they would if you phone was no longer under contract. The only reason anybody installed the iPad (06.15.00) baseband was to unlock their phone. Since, it was no longer needed I wanted to be able to update my phone without having to use redsn0w to install a custom ISPW each time.

Software used:
Redsn0w 0.9.14b1.zip
iPhone2,1_5.1_9B176_Restore.ipsw

Download redsn0w 0.9.14b1.
Unzip redsn0w.
Download the version of IOS currently running on your device. 5.1 in my case.
Launch redsn0w.
Select Extras.
Click Select ISPW..
Navigate to the downloaded ISPW for your version.
Click Back.
Select Jailbreak.

If already jailbroken, uncheck Install Cydia and select Downgrade from iPad baseband.

Ensure that the phone is connected to your computer, and put it in DFU mode or hit Next and follow the prompts on the next screen. It might take you a few times to get the timing right.

Redsn0w will begin fetching baseband files.

The phone will reboot and you will get a message in redsn0w stating that the rest of the process takes place on your device.

On your phone, you will see several message on your phone relating to disk checks and then the familiar running pineapple on screen. Be patient.

Your phone will reboot with the downgraded baseband.

Now, if you want to go back to a completely stock installation, you will need to restore the most currently supported version of IOS (5.1.1 for the 3Gs), after putting the phone back into DFU mode.

A couple things I discovered when attempting to remove the jailbreak from my iPhone 4s:

1) You cannot just delete the Cydia icon. When you press down on the icon and all the icons start wiggling, you have no option to press the “x” to delete the icon.

2) If you try to reset the phone by going to Settings/General/Erase All Content and Setting, this process will either never start or never finish. You end having to hold Power+Home to restart the phone.

So I tried to restore the phone. I was running 5.0.1 and wanted to keep it that way. Now, the simplest way to do it would have been to put the phone in DFU mode and download and restore the latest version of IOS from Apple. However, as I stated I wanted to try to keep the same version of IOS, 5.0.1 in my case. I downloaded the latest version of redsn0w , unzipped it and ran it. With the phone in DFU mode, I chose Extras/Even More/Identify. This verified that my phone was in DFU mode. Next, I went into Extras/Even More/Restore, and clicked ISPW and browsed to the version of IOS I wanted to restore. At this point, you are prompted to browse to the most current version of IOS (5.1.1 in my case). This is required to upgrade the baseband. If you do NOT want upgrade the baseband, DO NOT DO THIS! Once the latest version of IOS has been identified, you need to tell redsn0w where to find your shsh blobs. I chose remote to pull them from the Cydia servers, Once that is done, click Next and the baseband is upgraded and IOS 5.0.1 is restored. If you want to preserve your baseband, then you need to go the Extras/Custom IPSW route.

While trying to connect to shared printer on a Windows 2003 server (32 bit) from a Windows 7 (32 bit) client, I kept getting a “Windows cannot connect to the printer. Operation failed with error 0x0000002.” I stumbled on an interesting little trick to get around this issue.

First, I created the printer locally and allowed Windows 7 to install the appropriate driver. After the printer has been created, I went into the printer Properties and clicked on the Ports tab. Then, Add Port… Select Local Port, and click New Port… Enter the UNC to the printer share name. For example, \\servername\printersharename.

Then, the printer worked an used the Windows 2003 print share. It is not the cleanest solution, but it does get the printer working using the shared printer on the Windows 2003 server.

You can use the scutil command to change the hostname of a MacOS computer.

$ hostname
mycomputer.domain.com

$ sudo scutil –set HostName mynewcomputername.domain.com
$ hostname
mynewcomputername.domain.com

Likewise, you can change the ComputerName variable too:

$ sudo scutil –set ComputerName mynewcomputername.domain.com

I keep forgetting the location of this setting, so I am documenting it so I can find it easilly next time.

Tested on Windows 7.

To configure a Windows computer to execute a login script whenever anybody logs in to the machine, you can you use the Local Group Policy Editor. From the command prompt or “Search programs and file”, launch the Local Group Policy Editor by entering gpedit.msc. Then, navigate to User Configuration\Windows Settings\Script (Logon/Logoff). Double click Logon, and add the script. Note: you can use PowerShell scripts as well, but do that under the PowerShell Scripts tab so the correct command line interpreter is used. Also, if you have user specific portions of the script, you should construct the logic of your script as such. The Logoff option works the same way.

Last week, I called AT&T to have my iPhone 3Gs unlocked by Apple under AT&T’s new unlock policy. I had already unlocked this phone using Ultrasn0w, but I wanted to see if I would be able to just do the IOS updates using redsn0w and that is it. I have to use redsn0w, because I have baseband 06.15.00 on this phone.

Well, it turned out that yes, I can just use redsn0w, but I still had this annoying issue with MMS. In order to fix that, I needed to jailbreak the phone again.

Here is the procedure I used.

Again, this is an iPhone 3Gs running IOS 5.0.1 baseband 06.15.00 unlocked using ultrasn0w. I called AT&T with my IMEI number and had them send the unlock request to Apple. I got the email pretty quickly from AT&T telling me my phone had been unlocked and that I just needed to restore it to activate the unlock.

Software installed/downloaded:

OS: MacOS Lion 10.7.3
iTunes 10.6.1
iPhone2,1_5.1_9B176_Restore.ipsw
redsn0w_mac_0.9.10b6b.zip

First, connect the phone to your computer using the USB cable.

From iTunes, right mouse click on the phone under DEVICES and select Backup.

With your phone backup complete, create a custom IPSW IOS installation package using redsn0w:

Unzip the redsn0w download, and execute the redsn0w.app.

Select Extras.

Select Custom IPSW, and browse to the location where your saved you IOS 5.1 download (iPhone2,1_5.1_9B176_Restore.ipsw).

On the next screen, select whether you have the old iPhone 3Gs or newer. I have the original 3Gs, so I selected No.

To determine which version you have:
Put the phone in DFU mode. In MacOS Lion, bring up System Information by clicking Apple/About this Mac and selecting System Report. Then, click USB and look for Apple Mobile Device (DFU Mode). Look at the Serial Number line for iBoot. The number following iBoot will help you determine whether your 3Gs in the old version. 359.3 is the old version. Anything above that is the newer version.

This will create a file called NO_BB_OLDROM_iPhone2,1_5.1_9B176_Restore.ipsw. This is the file you are going to use to restore your iPhone from.

Ensure that you have your phone connected to your computer. Put the iPhone in DFU.

Here is the procedure I have used to put the phone in DFU mode:

With the phone on and unlocked, hold the Power and Home button. When the screen goes completely black, count to 2. Then, release the Power button and remain holding the Home button for 10-15 seconds. iTunes will report that the device is in recover mode. Now, I have done this several times, and have fairly confidently determined that this is not DFU mode. If you try to restore with the phone like this, you will get a 1600 error. This is what I have done consistently that last few times that has worked every time. Once in recover mode as determined by iTunes, I fire up redsn0w again. Click Extras, and Pwned DFU. This quickly puts the phone in DFU mode, so you can restore your custom IPSW.

Once in DFU mode, go back to iTunes, select your phone from DEVICES, if not already there, and hold the option key and click Restore.

Browse to your newly created custom IPSW file (NO_BB_OLDROM_iPhone2,1_5.1_9B176_Restore.ipsw), and click Open. IOS 5.1 will be installed and the phone will reboot and prompt you to restore settings from a backup or setup the phone as new. Now, because Apple had unlocked my phone, at this point I got the message congratulating me for successfully unlocking my phone.

Cool. Except for one problem. I was hoping that this (new redsn0w + IOS 5.1) would also fix the inability to send MMS messages without using iMessage. Well, it didn’t. I am using a T-Mobile SIM in the phone, so I thought I might try setting Cellular Data APN or the MMS APN to either epc.tmobile.com or wap.voicestream.com. Neither of these worked.

So, I went back to jailbreaking (untethered supported). With the phone connected, I fired up redsn0w again, and this time selected jailbreak. Again, the phone needs to be in DFU mode. This took me a couple tries, because the first time it did not appear to go through the jailbreaking process. But it did the second time.

Once the phone rebooted, I verified that I had the Cydia icon installed. Funny note, it was right back where I had it before I started this process.

I started Cydia, and updated as prompted. I go the developer route, and update everything.

Once updated, and Cydia or the phone was restarted, I navigated to Sources, clicked Edit and Add to add the following repository:

http://beta.leimobile.com/repo

Once the repository was added, I tapped the newly added repository to browse the packages available. I selected MMS Tmobile Fix, and installed it.

Then, I navigated to the phone Settings/General/Network/Cellular Data Network.

Cellular Data APN: epc.tmobile.com
MMS APN: wap.voicestream.com

And that was it. So, I guess in the end, I only got rid of needing Ultrasn0w, but at least I have MMS working and have IOS 5.1.