Filed under: OS Updates, Hardware, Apple

According to OSXDaily, Apple’s next scheduled update to Snow Leopard, OS X 10.6.2, doesn’t support Intel Atom processors. This is no problem for anyone on Apple hardware, because no Mac product runs an Atom. If you’re on a hacked netbook, though, it looks like this is the end of the line for your OS X updates.

Although it’s not confirmed, rumor has it that next update to Apple’s previous Leopard OS (10.5.9) will also knock out Atom support. Until a workaround pops up from netbook hacker circles, Atom machines running 10.6.1 and 10.5.8 should probably avoid upgrading. Is Apple sending a message to users running its software on third-party machines? It seems likely, but it also doesn’t seem like it will do much to stop determined netbook enthusiasts.

Apple breaks Atom Hackintoshes with upcoming OS X 10.6.2 update originally appeared on Download Squad on Mon, 02 Nov 2009 10:00:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Apple – Operating system – Mac OS X – Intel Atom – Download Squad

Go to Source

Apple breaks Atom Hackintoshes with upcoming OS X 10.6.2 update originally appeared on Shai Perednik.com on November 5, 2009.

Quoted from source below:

I mentioned before that Windows XP does not allow concurrent sessions for its Remote Desktop feature. What this means is that if a user is logged on at the local console, a remote user has to kick him off (and ironically, this can be done even without his permission) before starting work on the box. This is irritating and removes much of the productivity that Remote Desktop brings to Windows. Read on to learn how to remove that limitation in Windows XP SP2

A much touted feature in SP2 (Service Pack 2) since then removed was the ability to do just this, have a user logged on locally while another connects to the terminal remotely. Microsoft however removed the feature in the final build. The reason probably is that the EULA (End User License Agreement) allows only a single user to use a computer at a time. This is (IMHO) a silly reason to curtail Remote Desktop’s functionality, so we’ll have a workaround.

Microsoft did try out the feature in earlier builds of Service Pack 2 and it is this that we’re going to exploit here. We’re going to replace termserv.dll (The Terminal Server) with one from an earlier build (2055).

To get Concurrent Sessions in Remote Desktop working, follow the steps below exactly:

1. Download the termserv.zip file below and extract it somewhere. (You have to be registered to see the file)
2. Reboot into Safe Mode. This is necessary to remove Windows File Protection.
3. Copy the termserv.dll in the zip to %windir%\System32 and %windir%\ServicePackFiles\i386. If the second folder doesn’t exist, don’t copy it there. Delete termserv.dll from the dllcache folder: %windir%\system32\dllcache
4. Merge the contents of Concurrent Sessions SP2.reg file into the registry.
5. Make sure Fast User Switching is turned on. Go Control Panel -> User Accounts -> Change the way users log on or off and turn on Fast User Switching.
6. Open up the Group Policy Editor: Start Menu > Run > ‘gpedit.msc’. Navigate to Computer Configuration > Administrative Templates > Windows Components > Terminal Services. Enable ‘Limit Number of Connections’ and set the number of connections to 3 (or more). This enables you to have more than one person remotely logged on.
7. Now reboot back into normal Windows and try out whether Concurrent Sessions in Remote Desktop works. It should!

If anything goes wrong, the termserv_sp2.dll is the original file you replaced. Just rename it to termserv.dll, reboot into safe mode and copy it back.

The termserv.dl_ file is provided in the zip is for you slipstreamers out there. Just replace that file with the corresponding file in the Windows installation disks.

Concurrent Remote Desktop Sessions in Windows XP SP2 originally appeared on Shai Perednik.com on October 19, 2009.

Filed under: Internet Tools, iPhone

If you use Gmail, you have something to be excited about today, because you can finally have new email messages pushed directly to your iPhone when they arrive.

For many users, however, their first response is “it’s about time!” and others have even gone as far as saying “it’s finally here, no thanks to Apple.” This new feature, unveiled this morning by Google, has even been called a “workaround” to Apple’s alleged refusal to support push email, but in reality this isn’t the case.

Push: What is it, and how does it work?

To understand why push services have not been available before, let’s first discuss what exactly push is. When a client (be it a mail program, Twitter client, or web browser) needs to notify a user when new content or information is available, it has to periodically connect to the server and check for changes.

This is the way email clients have worked for years: the client checks with the server at a defined interval (usually every 5-15 minutes), downloads any new messages, and notifies the user that new mail has arrived. Many other services, such as RSS feeds, Twitter, Facebook, and even the Gmail website work the same way; they just check the server more often, which gives the appearance of real-time notifications.

Other services, such as instant messaging clients, maintain a constant, active connection to the server at all times. When new information is available for the client, the server sends, or “pushes” the information directly to the client as soon as it is available. In corporate environments, mail services such as Microsoft Exchange have paved the way for push email, by having the mail client (usually Outlook, Entourage, or other clients that support Exchange) maintain an active connection to the mail server, which allows the server to notify the client immediately when new mail arrives.

Read on to find out how Gmail push works, and what you need to know to get it set up on your phone.

Continue reading Push for Gmail: it’s here, it works, and it’s limited

TUAWPush for Gmail: it’s here, it works, and it’s limited originally appeared on The Unofficial Apple Weblog (TUAW) on Tue, 22 Sep 2009 16:00:00 EST. Please see our terms for use of feeds.

Read | Permalink | Email this | Comments

Go to Source

Push for Gmail: it’s here, it works, and it’s limited originally appeared on Shai Perednik.com on September 23, 2009.

I found a workaround here

Thanks to Vinh Pham for his post!

I know how to activate if F11 does not help to start recovery.

If U can access to START > Control Panel > Administrative tools or shorter way:

START > run > compmgmt.msc and press enter

then Disk management

Find which is recovery partition

Make Mark partition as Active

Then restart pc.

HP Compaq Recovery Manager F11 originally appeared on Shai Perednik.com on August 17, 2009.