Skip to main content

I-485

Confusion, confusion and more confusion. No body know what to do and what not do do. Rumors every day, some says to send application while some suggest to hold.

As per http://www.hammondlawfirm.com/:
HLG has confirmed that the CIS is not returning I-485 Applications back to those who filed I-485 during the first week of July. This is leading many to speculate that the CIS may reverse course and re-re-amend the July Visa Bulletin; whether the Visa Bulletin actually reopens remains to be seen. HLG normally refrains from commenting on rumors, but we have talked to several Washington insiders and believe that this is seriously being considered.

While as per http://immigrationvoice.org/: A BIG ANNOUNCEMENT LIKELY IN NEXT 24 HOURS:
Immigration Voice core has learned that something is likely to happen in next 24 hours (or Monday) possibly to fix the issues caused by recent visa bulletin.
We have been told not to divulge details of this development.
All we can say as of now is that :
1). The solution will be announced in next 24 hours or on Monday.2). The solution is not going to be a change in visa bulletin of July. The bulletin will most likely stay as-is. This is not about August bulletin either.3). This fix will be of a more permenant nature and this idea has been highly popular in this community in the past. Last edited by eagerr2i : Yesterday (07/12/2007) at 10:39 PM.

Comments

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog Deadspin: Spor

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck