Twitter
Facebook
Flickr
RSS
Free iTunes Account without redemption code
Well, lately everyone was having trouble creating Free iTunes accounts. After some searching through the internet, I find another way how to create free account for ANY country. You are going to see the guide in this post ..
[UPDATE] - I updated the post with screenshots, now it should me more explainable :)
These are the steps:
* [Step 1] Go to the iTunes Store, go to the bottom of the page and press on the “Flag icon”, probably it is the “USA Flag”.
Click the Flag Icon
Click the Flag Icon
* [Step 2] Now a page with all available iTunes Stores will show up, select your country. If your country is not listed, like mine “Malta”, then you should select another country preferably USA.
Choose Your Country
Choose Your Country
* [Step 3] Now the front page of iTunes Store should loads up, go and click the first app [Mine is iBowl] from the “Top Free App” section [It is on the bottom right of the page].
Free Apps Section
Free Apps Section
* [Step 4] When the App Page load, hit the “GET APP” Button
Select 'GET APP' button
Select ‘GET APP’ Button
* [Step 5] Then a login prompt window will appear, You need to click on “Create New Account”
bfsg
Select ‘Create New Account’
* [Step 6] A welcome screen will appear, then you need to click “Continue”.
Welcome Page
* [Step 7] Then a ‘Terms & Conditions’ page will load up, you need to read the Terms & Conditions and then tick the “I Accept” box and again click “Continue”.
Terms & Conditions Page
Terms & Conditions Page
* [Step 8] In this page you need to enter your details, [You will need a real and valid email address], then click “Continue”
Create iTunes Store Account
Create iTunes Store Account
* [Step 9] Now, this is the important part .. If you have followed all the six steps, in the next page, where you should enter your details, you should have a “None” option as a payment method.
* [Step 10] Now you need to fill in your details, if you don’t live in the country you chose, just make up an address, [Or just go to YellowPages website and find your preferred advert and take its address ;)]. Then again click “Continue”.
Details Page with 'None' option
Details Page with ‘None’ Option
* [Step 11] Now you will see a message to click on the confirmation link that was sent to the email you entered earlier.
Verify email
* [Step 12] Check your email inbox [or Junk Mail], open the email that Apple sent you and click on the confirmation link.
* [Step 13] When you press the link, automatically iTunes will show up, telling you to enter your brand new iTunes account Details.
* [Step 14] If you have done everything Okay, you will be greeted with a congratulations page.
iTunes Account Created
iTunes Account Successfully Created Page
* [Step 15] Now you are done, You can download free apps, the weekly free song and some free HDTV Tv Shows, without any redemption codes or nothing .. it’s that simple :)
Monday, October 27, 2008
Tuesday, October 14, 2008
Windows Mobile ported to iPhone
Most of the Windows Mobile / iPhone cross-breeding we've seen has either involved elaborate WinMo skinning or terrible iPhone KIRFs, but we suppose it was just a matter of time before Microsoft's mobile OS was made to run on Apple's hardware -- or at least that's what it looks like here. Pretty much everything about this video is suspect, from the shadiness of the MyPhone2008 conference it was shot at to the interviewer's ridiculously inane questions ("You don't have girlfriends in Norway?"), but damn if that isn't WinMo happily booting on what appears to be an iPhone 3G -- we can't tell, but it's a good bet it's jailbroken. The developer, Erik Kristiansen, says that mod is in beta right now but that he's looking at a January release -- we'll see what more we can dig up before then. Video after the break.
Update: As several commenters have pointed out, this has the trappings of a bad viral for the crappy SonicEmotion app also on that page -- all of the other videos are suspiciously fake / ridiculous, and the phone responds oddly to several touches. So much for that, we suppose.
Update: As several commenters have pointed out, this has the trappings of a bad viral for the crappy SonicEmotion app also on that page -- all of the other videos are suspiciously fake / ridiculous, and the phone responds oddly to several touches. So much for that, we suppose.
Sunday, September 28, 2008
Thursday, September 11, 2008
Windows XP Blue Screen of Death STOP Codes, A list of most BSoD errors and solutions
have been seeing quite a few posts regarding the dreaded Blue Screen of Death, and what the STOP codes mean. This is a fairly extensive list of the most common stop errors, their corrasponding codes, and recommended solutions.
Windows XP Blue Screen of Death STOP Codes
When Windows XP detects a problem from which it cannot recover, it displays Stop messages. These are text-mode error messages that report information about the condition.
Stop messages, sometimes referred to as blue screens (BSoD), contain specific information that can help you diagnose and possibly resolve the problem detected by the Windows kernel.
This list describes these messages and helps you understand and interpret them.
This list is NOT exhaustive or meant to resolve EVERY error.
This list of messages is a guide to individual messages and their possible causes and resolutions... Having a basic understanding of these error messages enables you to communicate with your technical support professional more effectively too.
With all these Stop messages, you can pretty much assume someone else has encountered the problem before you. That is why tying in the error message into www.google.com , posting a notice for help on a relevant newsgroup and entering the stop code into the "Microsoft Knowledge Base" can yield help just when you need it!
Here is the (long) list:
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Possible Resolutions:
• A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
• A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
• If you encounter a Stop 0xA message while upgrading to Windows XPl, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.
Possible Resolutions:
• Stop 0x1E messages typically occur after installing faulty drivers or system services, or they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop message lists a driver by name, disable, remove, or roll it back to correct the problem. If disabling or removing applications and drivers resolves the issue, contact the hardware manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
• If the Stop message mentions the file Win32k.sys, the source of the error might be a third-party "remote control" program. If such software is installed, you might be able to disable it by starting the system in safe mode. If not, use Recovery Console to manually delete the system service file that is causing the problem.
• Problems can result from system firmware incompatibilities. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware.
• Other possible causes include insufficient disk space while installing applications or performing certain functions that require more memory. You can free up space by deleting unneeded files. Use Disk Cleanup to increase available disk space. From Recovery Console, remove temporary files (those with .tmp file extensions), Internet cache files, application backup files, and .tmp files generated by Chkdsk.exe or Autochk.exe. You can also choose to install additional applications to another hard disk with more free space or move data files, paging files, and so on.
• The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the components that are causing kernel memory leaks. For more information about troubleshooting memory leaks, see Microsoft Knowledgebase articles Q177415, "How to Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding Pool Tags Used by Third Party Files Without Using the Debugger."
Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.
Possible Resolutions:
• Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.
• Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity
Method 1:
1. In the Run dialog box, in the Open box type:
cmd
2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f
Method 2:
1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.
If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!
• Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.
Stop 0x0000002E or DATA_BUS_ERROR
The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems.
Possible Resolutions:
• Stop 0x2E is typically due to defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Stop 0x2E messages can also occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
• Hard disk corruption can also cause this Stop message.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
The Stop 0x3F message indicates one or more of the following problems:
• The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions.
• A faulty device driver is not managing memory properly.
• An application, such as a backup program, is improperly allocating large amounts of kernel memory.
Possible Resolutions:
• Stop 0x3F messages can occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
• The system might not actually be out of PTEs, but a contiguous memory block of sufficient size is not available to satisfy a driver or application request. Check for the availability of updated driver or application files and consult the hardware or program documentation for minimum system requirements.
• Another cause is excessive demands for system PTE by applications. This situation is more common in server environments. Windows XP Professional provides a registry entry, SystemPages, that you can use to increase the number of PTEs allocated.
Caution
o Do not edit the registry unless you have no alternative. The registry editor bypasses standard safeguards, allowing settings that can damage your system, or even require you to reinstall Windows. If you must edit the registry, back it up first...
To increase the number of PTEs allocated in the registry
1. In the Run dialog box, and in the Open box, type: regedit
2. In the registry editor, navigate to the subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Memory Management.
3. Double-click on PagedPoolSize and SystemPages to view the value for each entry.
4. If PagedPoolSize is not zero, assign a value of 0.
5. If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less) of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with more memory, do not increase the SystemPages value above 110000 without contacting Microsoft technical support.
6. Click OK, and then close the registry editor.
7. Restart your computer.
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
Possible Resolutions:
• If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
• Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.
Possible Resolutions:
• Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a disk controller error. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, which is an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
• Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For more information about Stop 0x7A messages, see "Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR" later in this list.
Stop 0x00000079 or MISMATCHED_HAL
The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when mismatched single and multi-processor configuration files are copied to the system.
Possible Resolutions:
• A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the system. This error also occurs when using mismatched files, such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows XP Professional operating system CD using two different file names. For example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the correct HAL or kernel files from the CD to the appropriate folder on the hard disk.
• If you experience Stop 0x79 messages after changing firmware settings, restore the original settings used during Windows XP Professional Setup.
Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some x86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI, you must change firmware settings and reinstall Windows XP. Because of the numerous registry and system file changes required, you must run Setup again (an upgrade installation does not work).
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.
Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:
• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.
Possible Resolutions:
• Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.
• Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.
IMPORTANT
o You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:
o Press F6 if you need to install a third party SCSI or RAID driver.
o Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this list.
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.
The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:
• Disks or storage controllers that are failing, defective, or improperly configured.
• Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
Possible Resolutions:
• During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.
• Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.
• Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.
• Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
• Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:
• A condition that the kernel is not allowed to have or intercept (also known as a bound trap).
• Software problems.
• Hardware failures.
Possible Resolutions:
• Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Running the CPU beyond the rated specification, known as "overclocking," can cause Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services. Contact the software manufacturer about possible Windows XP specific updates. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.
Possible Resolutions:
• Stop 0x9F messages can occur after installing faulty applications or drivers or system services. If a file is listed by name and you can associate it with an application, uninstall the application. For drivers, disable, remove, or roll back that driver to to determine if this resolves the error. If it does, contact the hardware manufacturer for a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
• For information about troubleshooting standby and hibernate mode issues, see KB article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000."
Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
The Stop 0xBE message indicates that a driver attempted to write to read-only memory.
Possible Resolutions:
• A Stop 0xBE message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0xC2 or BAD_POOL_CALLER
The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:
• By allocating a memory pool size of zero bytes.
• By allocating a memory pool that does not exist.
• By attempting to free a memory pool that is already free.
• By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.
Possible Resolutions:
• A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
• A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.
• If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.
Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT
_CANCELLING_PENDING_OPERATIONS
This Stop messages indicates that a driver failed to cancel pending operations before exiting.
Possible Resolutions:
• Stop 0xCE messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.
Possible Resolutions:
• Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.
Possible Resolutions:
• Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers) or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.
Possible Resolutions:
• If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.
• Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.
• Problems that cause 0xED errors might also cause Stop 0x7B errors. For more information about 0x7B Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.
Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.
Possible Resolutions:
• You can use Driver Rollback or System Restore from safe mode, to restore a previous driver. You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore a previous working configuration. After restoring from backup media, you might need to reapply service packs or hotfixes, depending on when the backups were made.
• If the Stop message names the specific file, try replacing it manually with a fresh copy from the Windows XP Professional operating system CD using safe mode or Recovery Console. For systems using the FAT16 or FAT32 file system, you have the option of using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.
If the original file from the operating system CD has a file name that ends with an underscore (_) character, you cannot use the file until it is uncompressed. The Recovery Console's Copy command is ideal for copying compressed files because it detects and expands them. If you do not specify a destination file name, you must rename the expanded file with the correct extension before using it. From safe mode or Recovery Console, you can use the Expand command to uncompress and copy a file to a destination location. In Recovery Console, the expanded file is given the correct name after being copied to the destination location. For more information about the Copy or Expand commands, see Windows XP Help and Support Centre.
Windows XP Blue Screen of Death STOP Codes
When Windows XP detects a problem from which it cannot recover, it displays Stop messages. These are text-mode error messages that report information about the condition.
Stop messages, sometimes referred to as blue screens (BSoD), contain specific information that can help you diagnose and possibly resolve the problem detected by the Windows kernel.
This list describes these messages and helps you understand and interpret them.
This list is NOT exhaustive or meant to resolve EVERY error.
This list of messages is a guide to individual messages and their possible causes and resolutions... Having a basic understanding of these error messages enables you to communicate with your technical support professional more effectively too.
With all these Stop messages, you can pretty much assume someone else has encountered the problem before you. That is why tying in the error message into www.google.com , posting a notice for help on a relevant newsgroup and entering the stop code into the "Microsoft Knowledge Base" can yield help just when you need it!
Here is the (long) list:
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Possible Resolutions:
• A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
• A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
• If you encounter a Stop 0xA message while upgrading to Windows XPl, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.
Possible Resolutions:
• Stop 0x1E messages typically occur after installing faulty drivers or system services, or they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop message lists a driver by name, disable, remove, or roll it back to correct the problem. If disabling or removing applications and drivers resolves the issue, contact the hardware manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
• If the Stop message mentions the file Win32k.sys, the source of the error might be a third-party "remote control" program. If such software is installed, you might be able to disable it by starting the system in safe mode. If not, use Recovery Console to manually delete the system service file that is causing the problem.
• Problems can result from system firmware incompatibilities. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware.
• Other possible causes include insufficient disk space while installing applications or performing certain functions that require more memory. You can free up space by deleting unneeded files. Use Disk Cleanup to increase available disk space. From Recovery Console, remove temporary files (those with .tmp file extensions), Internet cache files, application backup files, and .tmp files generated by Chkdsk.exe or Autochk.exe. You can also choose to install additional applications to another hard disk with more free space or move data files, paging files, and so on.
• The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the components that are causing kernel memory leaks. For more information about troubleshooting memory leaks, see Microsoft Knowledgebase articles Q177415, "How to Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding Pool Tags Used by Third Party Files Without Using the Debugger."
Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.
Possible Resolutions:
• Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.
• Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity
Method 1:
1. In the Run dialog box, in the Open box type:
cmd
2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f
Method 2:
1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.
If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!
• Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.
Stop 0x0000002E or DATA_BUS_ERROR
The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems.
Possible Resolutions:
• Stop 0x2E is typically due to defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Stop 0x2E messages can also occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
• Hard disk corruption can also cause this Stop message.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
The Stop 0x3F message indicates one or more of the following problems:
• The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions.
• A faulty device driver is not managing memory properly.
• An application, such as a backup program, is improperly allocating large amounts of kernel memory.
Possible Resolutions:
• Stop 0x3F messages can occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
• The system might not actually be out of PTEs, but a contiguous memory block of sufficient size is not available to satisfy a driver or application request. Check for the availability of updated driver or application files and consult the hardware or program documentation for minimum system requirements.
• Another cause is excessive demands for system PTE by applications. This situation is more common in server environments. Windows XP Professional provides a registry entry, SystemPages, that you can use to increase the number of PTEs allocated.
Caution
o Do not edit the registry unless you have no alternative. The registry editor bypasses standard safeguards, allowing settings that can damage your system, or even require you to reinstall Windows. If you must edit the registry, back it up first...
To increase the number of PTEs allocated in the registry
1. In the Run dialog box, and in the Open box, type: regedit
2. In the registry editor, navigate to the subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Session Manager\Memory Management.
3. Double-click on PagedPoolSize and SystemPages to view the value for each entry.
4. If PagedPoolSize is not zero, assign a value of 0.
5. If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less) of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with more memory, do not increase the SystemPages value above 110000 without contacting Microsoft technical support.
6. Click OK, and then close the registry editor.
7. Restart your computer.
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
Possible Resolutions:
• If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
• Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.
Possible Resolutions:
• Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a disk controller error. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, which is an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
• Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For more information about Stop 0x7A messages, see "Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR" later in this list.
Stop 0x00000079 or MISMATCHED_HAL
The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when mismatched single and multi-processor configuration files are copied to the system.
Possible Resolutions:
• A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the system. This error also occurs when using mismatched files, such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows XP Professional operating system CD using two different file names. For example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the correct HAL or kernel files from the CD to the appropriate folder on the hard disk.
• If you experience Stop 0x79 messages after changing firmware settings, restore the original settings used during Windows XP Professional Setup.
Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some x86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI, you must change firmware settings and reinstall Windows XP. Because of the numerous registry and system file changes required, you must run Setup again (an upgrade installation does not work).
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.
Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:
• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.
Possible Resolutions:
• Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.
• Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.
IMPORTANT
o You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:
o Press F6 if you need to install a third party SCSI or RAID driver.
o Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this list.
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.
The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:
• Disks or storage controllers that are failing, defective, or improperly configured.
• Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
Possible Resolutions:
• During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.
• Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.
• Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.
• Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
• Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.
Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:
• A condition that the kernel is not allowed to have or intercept (also known as a bound trap).
• Software problems.
• Hardware failures.
Possible Resolutions:
• Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
• Running the CPU beyond the rated specification, known as "overclocking," can cause Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.
• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
• Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services. Contact the software manufacturer about possible Windows XP specific updates. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.
Possible Resolutions:
• Stop 0x9F messages can occur after installing faulty applications or drivers or system services. If a file is listed by name and you can associate it with an application, uninstall the application. For drivers, disable, remove, or roll back that driver to to determine if this resolves the error. If it does, contact the hardware manufacturer for a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
• For information about troubleshooting standby and hibernate mode issues, see KB article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000."
Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
The Stop 0xBE message indicates that a driver attempted to write to read-only memory.
Possible Resolutions:
• A Stop 0xBE message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0xC2 or BAD_POOL_CALLER
The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:
• By allocating a memory pool size of zero bytes.
• By allocating a memory pool that does not exist.
• By attempting to free a memory pool that is already free.
• By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.
Possible Resolutions:
• A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
• A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.
• If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.
Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT
_CANCELLING_PENDING_OPERATIONS
This Stop messages indicates that a driver failed to cancel pending operations before exiting.
Possible Resolutions:
• Stop 0xCE messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.
Possible Resolutions:
• Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.
Possible Resolutions:
• Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers) or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.
Possible Resolutions:
• If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.
• Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.
• Problems that cause 0xED errors might also cause Stop 0x7B errors. For more information about 0x7B Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.
Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.
Possible Resolutions:
• You can use Driver Rollback or System Restore from safe mode, to restore a previous driver. You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore a previous working configuration. After restoring from backup media, you might need to reapply service packs or hotfixes, depending on when the backups were made.
• If the Stop message names the specific file, try replacing it manually with a fresh copy from the Windows XP Professional operating system CD using safe mode or Recovery Console. For systems using the FAT16 or FAT32 file system, you have the option of using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.
If the original file from the operating system CD has a file name that ends with an underscore (_) character, you cannot use the file until it is uncompressed. The Recovery Console's Copy command is ideal for copying compressed files because it detects and expands them. If you do not specify a destination file name, you must rename the expanded file with the correct extension before using it. From safe mode or Recovery Console, you can use the Expand command to uncompress and copy a file to a destination location. In Recovery Console, the expanded file is given the correct name after being copied to the destination location. For more information about the Copy or Expand commands, see Windows XP Help and Support Centre.
Monday, September 1, 2008
Saturday, August 30, 2008
Stereo Bluetooth on iPhone - Have A2DP working!
It is now possible to hack the iPhone to work with your bluetooth stereo headset. The tested platform:-
iPhone 8GB Unlocked using 1.1.1
Nokia BH-503
Also working with 1.0.2
A2DP on iPhone:-
1. Pair your headset, make a test call to see if it works. End the call normally.
2. Dial *#307#, press call.
3. Press the answer button twice with 2 seconds delay in your bluetooth headset (If you don’t do this correctly, you will continue to listen the ringtone in headset)
4. Press answer on iPhone.
5. Press the home button, do NOT end the call.
6. Open iPod and play a song, you won’t get sound from iPhone, nor headset.
7. Once it is playing, press the home button.
8. Open phone.
9. Dial 0, press Call.
10. It will ring again, answer.
11. Press audio source, select your headset.
12. Press home button, do NOT end call. (we’re almost there)
13. Open iPod and play anything you like.
Shorter Way:
1. *#307# Dial, press the bluetooth headset button twice.
2. Answer on iPhone, press source.
3. Select bluetooth headset.
4. Press home button, open iPod, play anything.
Caveat: You cannot receive the calls while the music plays this way.
iPhone 8GB Unlocked using 1.1.1
Nokia BH-503
Also working with 1.0.2
A2DP on iPhone:-
1. Pair your headset, make a test call to see if it works. End the call normally.
2. Dial *#307#, press call.
3. Press the answer button twice with 2 seconds delay in your bluetooth headset (If you don’t do this correctly, you will continue to listen the ringtone in headset)
4. Press answer on iPhone.
5. Press the home button, do NOT end the call.
6. Open iPod and play a song, you won’t get sound from iPhone, nor headset.
7. Once it is playing, press the home button.
8. Open phone.
9. Dial 0, press Call.
10. It will ring again, answer.
11. Press audio source, select your headset.
12. Press home button, do NOT end call. (we’re almost there)
13. Open iPod and play anything you like.
Shorter Way:
1. *#307# Dial, press the bluetooth headset button twice.
2. Answer on iPhone, press source.
3. Select bluetooth headset.
4. Press home button, open iPod, play anything.
Caveat: You cannot receive the calls while the music plays this way.
Wednesday, August 27, 2008
6 Cool Firefox Tricks
1. Tab navigation. Instead of using the mouse to select different tabs that you have open, use the keyboard. Here are the shortcuts:
* Ctrl+Tab (rotate forward among tabs)
* Ctrl+Shft+Tab (rotate to the previous tab)
* Ctrl+1-9 (choose a number to jump to a specific tab)
2. Mouse shortcuts.
* Middle click on link (opens in new tab)
* Shift-scroll down (previous page)
* Shift-scroll up (next page)
* Ctrl-scroll up (decrease text size)
* Ctrl-scroll down (increase text size)
* Middle click on a tab (closes tab)
3. Speed up Firefox. If you have a broadband connection (and most of us do), you can use pipelining to speed up your page loads. This allows Firefox to load multiple things on a page at once, instead of one at a time (by default, it’s optimized for dialup connections). Here’s how:
* Type “about:config†into the address bar and hit return. Type “network.http†in the filter field, and change the following settings (double-click on them to change them):
* Set “network.http.pipelining†to “trueâ€
* Set “network.http.proxy.pipelining†to “trueâ€
* Set “network.http.pipelining.maxrequests†to a number like 30. This will allow it to make 30 requests at once.
* Also, right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay†and set its value to “0?. This value is the amount of time the browser waits before it acts on information it receives.
4. Keyboard shortcuts.
* Spacebar (page down)
* Shift-Spacebar (page up)
* Ctrl+F (find)
* Alt-N (find next)
* Ctrl+D (bookmark page)
* Ctrl+T (new tab)
* Ctrl+K (go to search box)
* Ctrl+L (go to address bar)
* Ctrl+= (increase text size)
* Ctrl+- (decrease text size)
* Ctrl-W (close tab)
* F5 (reload)
* Alt-Home (go to home page)
5. About:config. The true power user’s tool, about.config isn’t something to mess with if you don’t know what a setting does. You can get to the main configuration screen by putting about:config in the browser’s address bar. Clck here for more Mozillazine’s about:config tips and screenshots.
6. Remove the close tab button. Sometime you accidentally click on the close button of Firefox’s tabs? But with this trick you can move them or remove them, again through about:config. Edit the preference for “browser.tabs.closeButtonsâ€.
* 0: Display a close button on the active tab only
* 1:(Default) Display close buttons on all tabs
* 2:Don’t display any close buttons
* 3:Display a single close button at the end of the tab bar (Firefox 1.x behavior)
* Ctrl+Tab (rotate forward among tabs)
* Ctrl+Shft+Tab (rotate to the previous tab)
* Ctrl+1-9 (choose a number to jump to a specific tab)
2. Mouse shortcuts.
* Middle click on link (opens in new tab)
* Shift-scroll down (previous page)
* Shift-scroll up (next page)
* Ctrl-scroll up (decrease text size)
* Ctrl-scroll down (increase text size)
* Middle click on a tab (closes tab)
3. Speed up Firefox. If you have a broadband connection (and most of us do), you can use pipelining to speed up your page loads. This allows Firefox to load multiple things on a page at once, instead of one at a time (by default, it’s optimized for dialup connections). Here’s how:
* Type “about:config†into the address bar and hit return. Type “network.http†in the filter field, and change the following settings (double-click on them to change them):
* Set “network.http.pipelining†to “trueâ€
* Set “network.http.proxy.pipelining†to “trueâ€
* Set “network.http.pipelining.maxrequests†to a number like 30. This will allow it to make 30 requests at once.
* Also, right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay†and set its value to “0?. This value is the amount of time the browser waits before it acts on information it receives.
4. Keyboard shortcuts.
* Spacebar (page down)
* Shift-Spacebar (page up)
* Ctrl+F (find)
* Alt-N (find next)
* Ctrl+D (bookmark page)
* Ctrl+T (new tab)
* Ctrl+K (go to search box)
* Ctrl+L (go to address bar)
* Ctrl+= (increase text size)
* Ctrl+- (decrease text size)
* Ctrl-W (close tab)
* F5 (reload)
* Alt-Home (go to home page)
5. About:config. The true power user’s tool, about.config isn’t something to mess with if you don’t know what a setting does. You can get to the main configuration screen by putting about:config in the browser’s address bar. Clck here for more Mozillazine’s about:config tips and screenshots.
6. Remove the close tab button. Sometime you accidentally click on the close button of Firefox’s tabs? But with this trick you can move them or remove them, again through about:config. Edit the preference for “browser.tabs.closeButtonsâ€.
* 0: Display a close button on the active tab only
* 1:(Default) Display close buttons on all tabs
* 2:Don’t display any close buttons
* 3:Display a single close button at the end of the tab bar (Firefox 1.x behavior)
Tuesday, August 26, 2008
http://www.phonesreview.co.uk/2008/06/09/new-apple-3g-iphone-designs-new-in-will-the-iphone-2-look-like-any-of-these/
We have some awesome pictures of the Apple 3G iPhone mock-ups which we know you will love; this one goes out to all you Apple fans. Many of us have wanted to know what the real 3G iPhone will look like and here are some from designers.
Basically the pictures below will get you thinking and all we say is “Dream On”, got to admit they are mind blowing and would be fantastic if the real phone is like one of these, all a bit of fun at the end of the day. We found these pictures via “Wired” and they say that these mock-ups were designed by the readers of iLounge who held a competition to find the best ideas and creations of the brand new Apple iPhone. Check out our top 10 that we have listed below.
We have listed the title, then the picture then the description of that phone. So Title – Photo - Description
iPhone See-through
iphone concept mockup pic 1
This mock-up by Robert Davis of Cornelius, North Carolina, is thin, lightweight and crystal clear. It runs a full version of Leopard (not a stripped-down one) and has a 5-megapixel camera. Not very realistic — or practical — but pretty.
iPhone Pro
iPhone Pro
The iPhone Pro by A. Berio of Los Angeles is an iPhone for well, the pros. Boasting a 1024×768 display, the iPhone Pro also has Intel’s latest Atom processor and runs OS X Leopard. Dream on!
iPhone Mirror
iPhone Mirror
The iPhone Mirror by an unnamed iLounge reader from Boston has two touch screens and two cameras — one on either side. This makes video conferencing very easy — and also taking self-portraits.
iPhone Pico
iPhone Pico
iPhone Pico. Smallest. iPhone. Ever.
iPhone Classic and Mini
iPhone Classic and Mini
A lot of Apple watchers expect the iPhone line to diversify like that of the iPod: different models for different pocketbooks. Many except to see a smaller, slimmed-down iPhone — like the iPhone Mini. By Frank Reinders, Venlo, Netherlands.
iPhone 3-G Slider With Virtual Keyboard
iPhone 3-G Slider With Virtual Keyboard
This 3-G iPhone by Aaron Besson of Port of Spain, Trinidad & Tobago, is a slider with a difference. The slide-out keyboard is actually a second touch screen, and the keyboard its displaying is virtual. Clever.
iPhone Air
iPhone Air
The iPhone Air by Renato Ruiz of Oxnard, California, is the perfect complement to the MacBook Air. It’s a clamshell and has two screens — one for a virtual keyboard — that are both protected when the device is closed. There’s a third screen on the lid that shows what music is playing while the iPhone is being used as a media player.
Two Trackballs
Two Trackballs
This next-gen iPhone has two home buttons, which are now trackballs for gaming and easier scrolling. It also uses the built-in accelerometers as game controls. Designed by an unnamed iLounge reader from Skokie, Illinois.
iPhone Bio
iPhone Bio
The iPhone Bio has the usual 3-G for video calls and video chat, but also uses biometric fingerprint security to protect your sensitive data.
iPhone Duo
http://www.phonesreview.co.uk/2008/06/09/new-apple-3g-iphone-designs-new-in-will-the-iphone-2-look-like-any-of-these/
Basically the pictures below will get you thinking and all we say is “Dream On”, got to admit they are mind blowing and would be fantastic if the real phone is like one of these, all a bit of fun at the end of the day. We found these pictures via “Wired” and they say that these mock-ups were designed by the readers of iLounge who held a competition to find the best ideas and creations of the brand new Apple iPhone. Check out our top 10 that we have listed below.
We have listed the title, then the picture then the description of that phone. So Title – Photo - Description
iPhone See-through
iphone concept mockup pic 1
This mock-up by Robert Davis of Cornelius, North Carolina, is thin, lightweight and crystal clear. It runs a full version of Leopard (not a stripped-down one) and has a 5-megapixel camera. Not very realistic — or practical — but pretty.
iPhone Pro
iPhone Pro
The iPhone Pro by A. Berio of Los Angeles is an iPhone for well, the pros. Boasting a 1024×768 display, the iPhone Pro also has Intel’s latest Atom processor and runs OS X Leopard. Dream on!
iPhone Mirror
iPhone Mirror
The iPhone Mirror by an unnamed iLounge reader from Boston has two touch screens and two cameras — one on either side. This makes video conferencing very easy — and also taking self-portraits.
iPhone Pico
iPhone Pico
iPhone Pico. Smallest. iPhone. Ever.
iPhone Classic and Mini
iPhone Classic and Mini
A lot of Apple watchers expect the iPhone line to diversify like that of the iPod: different models for different pocketbooks. Many except to see a smaller, slimmed-down iPhone — like the iPhone Mini. By Frank Reinders, Venlo, Netherlands.
iPhone 3-G Slider With Virtual Keyboard
iPhone 3-G Slider With Virtual Keyboard
This 3-G iPhone by Aaron Besson of Port of Spain, Trinidad & Tobago, is a slider with a difference. The slide-out keyboard is actually a second touch screen, and the keyboard its displaying is virtual. Clever.
iPhone Air
iPhone Air
The iPhone Air by Renato Ruiz of Oxnard, California, is the perfect complement to the MacBook Air. It’s a clamshell and has two screens — one for a virtual keyboard — that are both protected when the device is closed. There’s a third screen on the lid that shows what music is playing while the iPhone is being used as a media player.
Two Trackballs
Two Trackballs
This next-gen iPhone has two home buttons, which are now trackballs for gaming and easier scrolling. It also uses the built-in accelerometers as game controls. Designed by an unnamed iLounge reader from Skokie, Illinois.
iPhone Bio
iPhone Bio
The iPhone Bio has the usual 3-G for video calls and video chat, but also uses biometric fingerprint security to protect your sensitive data.
iPhone Duo
http://www.phonesreview.co.uk/2008/06/09/new-apple-3g-iphone-designs-new-in-will-the-iphone-2-look-like-any-of-these/
Thursday, August 21, 2008
iPhone completely unlocked (hacked) using Turbo SIM card
iPhone completely unlocked (hacked) using Turbo SIM card
iPhone Unlock finally reached its goal,guys iPhone finally unlocked.dream comes true,thats right you can unlock your iPhone using Turbo SIM cards,(only 80$ for blank SIM)
i will release a full how-to article but for now just goto bladox forum and find out how.
iphone fully unlocked
this is turbo SIM
HOWTO:(by MetalRat)
OK I have seen so many questions still circulating regarding how to get the TurboSIM method working. I am going to try and illustrate the simplest method.
WARNING: If you are non-technical, confused as to how to use or install application on computers without an installer or are unfamilliar with terms such as ssh, scp or chmod then you probably should NOT be attempting to use the TurboSIM method anyway.
Seriously, you can waste a lot of money if you get this wrong.
1. Get an iPhone. Try an applestore, or even ebay.
2. Once you get it, make sure you read the manual.
3. At the top of the phone is the SIM card tray, in there is your AT&T sim. Go on, have a look. Now put it back.
4. Use one of the many, many well documented methods to activate your phone. Any of them will be fine, and if you can get to this part then you can probably continue.
5. Order a TurboSIM (Blank version) from www.bladox.com
6. Wait.
7. Wait.
8. If you ordered via an express shipping method you can skip to step 11
9. wait
10. wait a bit more
11. You could have done this step while you were waiting, but install SSH. Use these instructions http://cre.ations.net/blog/post/howt…on-your-iphone (in the comments there is a mac version of the SSH installer)
While you are at it install the iPhone binary kit, too: http://iphone.natetrue.com/iphone-binkit-0.06.tar.gz
12. Once you have done that and are able to ssh into your phone over wireless (if you dont know how already then I suggest you give up now. cancel your order with bladox.)
Hint 1: Find your iPhone IP address under: Settings ->WiFi -> -> blue arrowy thing
Hint 2: Either using Putty (for windows) or ssh (for mac from the terminal) use that IP address to connect to the iPhone. E.g: ssh -l root 123.123.123.123
The root password is dottie. I suggest you change it unless you want someone like me to totally take the shine off your afternoon.
13. download the iPhone port of the bladox utilities: http://www.gofilego.com/?fileid=71ae…3da7541ee37ae8
Extract these files and in there somewhere you will see a little file called “turbo-app” copy this to your iPhone using scp for instance:
scp turbo-app root@123.123.123.123:/
Download this: http://www.bladox.com/pub/applesaft-0.92.tar.gz
in the “bin” directory copy applesaft.trb to the iphone:
scp applesaft.trb root@123.123.123.123:/
14. copy the follwing file from the iPhone /System/Library/LaunchDaemons/com.apple.CommCenter.plist
and add the following line:
Disabled
after these lines, already present in the file
OnDemand
Now copy the file back. Yes, to the same location you got it from.
15. now you will have to reboot your iPhone. (Told you to read the manual) You can do this by pressing the power button for a few seconds until it asks you if you want to switch it off, or you can just take out the battery….
16. Now, get your AT&T sim and carefully cut it as indicated in the packet that the TurboSIM came in.
17. Do the same for the SIM you want to be using eventually in the iPhone.
18. CAREFULLY, VERY CAREFULLY. place the AT&T sim along with the TurboSIM into the sim tray and pop it into the iPhone.It should slide in without too much effort, DO NOT FORCE IT IN. BE CAREFUL.
19. Now ssh into your phone and do the following (yes include the slashes):
chmod 755 /turbo-app
/turbo-app /applesaft.trb
This will take several seconds to run just be patient.
20. Go to Settings -> Phone -> SIM Applications -> Apple Saft and then click SET.
21. Eject the sim tray CAREFULLY.
22. CAREFULLY, REALLLY EFFING CAREFULLY, put the TurboSIM and your target SIM into the iPhone.
23. Remember that file I told you to edit? Right edit it again and take out that line I told you to put in, then copy it back to the iPhone.
24. Do 14. Again.
25. Fingers crossed it should be working now.
26. Go to Settings -> General -> Network -> EDGE and change your details according to your operators instructions.
27. Thank everyone who has put time and effort into this, including Ozbimmer, ZF, the bladox developers. Yadda yadda.
OK? Any questions? I can answer all of them:
a) read the instructions again
b) google for it
From http://hadi.wordpress.com/2007/08/14/iphone-unlocked/
iPhone Unlock finally reached its goal,guys iPhone finally unlocked.dream comes true,thats right you can unlock your iPhone using Turbo SIM cards,(only 80$ for blank SIM)
i will release a full how-to article but for now just goto bladox forum and find out how.
iphone fully unlocked
this is turbo SIM
HOWTO:(by MetalRat)
OK I have seen so many questions still circulating regarding how to get the TurboSIM method working. I am going to try and illustrate the simplest method.
WARNING: If you are non-technical, confused as to how to use or install application on computers without an installer or are unfamilliar with terms such as ssh, scp or chmod then you probably should NOT be attempting to use the TurboSIM method anyway.
Seriously, you can waste a lot of money if you get this wrong.
1. Get an iPhone. Try an applestore, or even ebay.
2. Once you get it, make sure you read the manual.
3. At the top of the phone is the SIM card tray, in there is your AT&T sim. Go on, have a look. Now put it back.
4. Use one of the many, many well documented methods to activate your phone. Any of them will be fine, and if you can get to this part then you can probably continue.
5. Order a TurboSIM (Blank version) from www.bladox.com
6. Wait.
7. Wait.
8. If you ordered via an express shipping method you can skip to step 11
9. wait
10. wait a bit more
11. You could have done this step while you were waiting, but install SSH. Use these instructions http://cre.ations.net/blog/post/howt…on-your-iphone (in the comments there is a mac version of the SSH installer)
While you are at it install the iPhone binary kit, too: http://iphone.natetrue.com/iphone-binkit-0.06.tar.gz
12. Once you have done that and are able to ssh into your phone over wireless (if you dont know how already then I suggest you give up now. cancel your order with bladox.)
Hint 1: Find your iPhone IP address under: Settings ->WiFi ->
Hint 2: Either using Putty (for windows) or ssh (for mac from the terminal) use that IP address to connect to the iPhone. E.g: ssh -l root 123.123.123.123
The root password is dottie. I suggest you change it unless you want someone like me to totally take the shine off your afternoon.
13. download the iPhone port of the bladox utilities: http://www.gofilego.com/?fileid=71ae…3da7541ee37ae8
Extract these files and in there somewhere you will see a little file called “turbo-app” copy this to your iPhone using scp for instance:
scp turbo-app root@123.123.123.123:/
Download this: http://www.bladox.com/pub/applesaft-0.92.tar.gz
in the “bin” directory copy applesaft.trb to the iphone:
scp applesaft.trb root@123.123.123.123:/
14. copy the follwing file from the iPhone /System/Library/LaunchDaemons/com.apple.CommCenter.plist
and add the following line:
after these lines, already present in the file
Now copy the file back. Yes, to the same location you got it from.
15. now you will have to reboot your iPhone. (Told you to read the manual) You can do this by pressing the power button for a few seconds until it asks you if you want to switch it off, or you can just take out the battery….
16. Now, get your AT&T sim and carefully cut it as indicated in the packet that the TurboSIM came in.
17. Do the same for the SIM you want to be using eventually in the iPhone.
18. CAREFULLY, VERY CAREFULLY. place the AT&T sim along with the TurboSIM into the sim tray and pop it into the iPhone.It should slide in without too much effort, DO NOT FORCE IT IN. BE CAREFUL.
19. Now ssh into your phone and do the following (yes include the slashes):
chmod 755 /turbo-app
/turbo-app /applesaft.trb
This will take several seconds to run just be patient.
20. Go to Settings -> Phone -> SIM Applications -> Apple Saft and then click SET.
21. Eject the sim tray CAREFULLY.
22. CAREFULLY, REALLLY EFFING CAREFULLY, put the TurboSIM and your target SIM into the iPhone.
23. Remember that file I told you to edit? Right edit it again and take out that line I told you to put in, then copy it back to the iPhone.
24. Do 14. Again.
25. Fingers crossed it should be working now.
26. Go to Settings -> General -> Network -> EDGE and change your details according to your operators instructions.
27. Thank everyone who has put time and effort into this, including Ozbimmer, ZF, the bladox developers. Yadda yadda.
OK? Any questions? I can answer all of them:
a) read the instructions again
b) google for it
From http://hadi.wordpress.com/2007/08/14/iphone-unlocked/
