Skip to main content

Getting an AppleID Without a Credit Card

So you bought a new iPod Touch . You have heard a lot of those cool games and cool applications that runs over it . You opened up iTunes and excited to see what is in store for you . Last thing you know , Apple is asking you for a credit card number . Boom ! all that excitement is gone.

For an average iPod owner who does not have a credit card number or does not want to have one , applying for an Apple ID to get hold of those freebies and goodies Steve Jobs has to offer is a pain in the ass . But there are several ways to get over with it . One , you could buy a iTunes gift card and redeem it . This is good , if and only if , gift cards are available . Two, try jailbraking your iPod touch and risk voiding its warranty . Lastly , read on and follow the steps below. Just a note , I assume that you are responsible enough to take care of yourself . Take note that even if the software is free , a billing statement will be sent to you registered email address . And if you intend to buy one , pay for it.

1. Launch you iTunes application and go to the iTunes Store .
2. Scroll down to the bottom of the page and select the country. The country is significant , different country can mean different offered applications.

3. Go to the Top Free Apps widget and click on the top free application.
4. Clicking on the Get App button prompts you to enter your AppleID , select Create New Account.
5. Proceed and create a new AppleID account.
6. If you got all the previous steps working , you may be able to see the "NONE" option on the Payment method section.

7. Select the NONE option and provide the billing information . Make sure that your address is a valid address from the country you have choosen in Step 2.
8. Click CONTINUE and you are good to go.
Labels:

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more