crash at region load

I just purchased a sony vaio VGN-NR140E Intel(R) Pentium(R) Dual CPU T2330 @ 1.60GHz (2 CPUs), ~1.6GHz Memory: 1014MB RAM and as soon as sl tries to load the region it crashes...can anyone help?

Sorry not with that vid card, you cannot expect it to run with SL , intel vid card no matter their label is something i wouldnt recommend for SL;

http://www.amazon.com/Sony-VGN-NR140E-Notebook-Pentium-Processor/dp/B000VXVI3O
Sony VAIO VGN-NR140E
Video is powered by the Intel Graphics Media Accelerator X3100, which uses shared video memory

Second Life may not run on graphics/video cards other than the ones listed above. Unfortunately, if your graphics card includes any of the following words, it's NOT compatible with Second Life:

Intel chipsets less than a 945 (any really)

+ shared video memory with system is the easiest way to crash graphic intensive rendering, you basicly have 1024 - 251 mb ~ 773mb ram on that pc, SL highly need min 2 gig ram for decent performance, theres a big diffrence from 1 ~ 2.

Wow..thst sucks. Ok well thanks a lot appreciate your help.

Hi there,
I hAVE a vgn-nr120e/s and I am logged in now and running SL. I've been logged in for about two hours and have yet to crash. Its not perfect, but it works well enough.

I just used the following instructions (im copying them from the posting for you)

"While I probably would not recommend the X61 as a great Second Life platform, I have succeeded in making it work. The X61 uses the Intel GM965 chipset with the X3100 Graphics Media Accelerator. I am running 32-bit Vista and the latest Intel beta drivers (15.6b). The fix will require you to track down the settings.xml file and modify it. Although it is unlikely that you will do anything harmful to your computer or Vista, all of the usual do-so-at-your-own-risk warnings apply.

Out of the box, Second Life will allow you to log in but will crash immediately before displaying the world. The first problem is that the OpenGL driver claims to support object occlusion but it doesn't (at least, not properly). The trick is to turn off Object Occlusion.

Now we come to the second problem. Object Occlusion is an option in the Debug menus which you can't get to until you are in-world. Fortunately, this option is stored in the settings.xml file. Once Second Life has started it creates a settings.xml file in the \Users\<yourname>\AppData directory tree. In my case this is \Users\myname\AppData\Roaming\SecondLife\user_sett ings\settings.xml. You will have to manually add the command to disable Object Occlusion to this file. The lines to add are:

<!--Enable object culling based on occlusion (coverage) by other objects-->
<UseOcclusion value="FALSE"/>

Open settings.xml with notepad and paste the two lines into the <settings ...> section (somewhere after the second line but before the final </settings> line). Save the file and have fun running Second Life! By the way, there may be multiple directories under AppData. I have three: Local, LocalLow, and Roaming. My SecondLife directory is under Roaming since I am running on a wireless link. You may have to search a bit to find the directory which has the SecondLife subdirectory."

let me just add that since we have similar computers, you will probably not need the updated driver, because I didn't. My computer said it has the most updated driver when I tried to update them at intel.com. Also, the easiest way I found the file was by searching for the Appdata file in the search function under the windows menu. From there it shows the Roaming folder mentioned in the intructions above.

Try it out, you won't be disappointed!