Jump to content
  • 0
Sign in to follow this  
Sophiaperis31

VFS initialization error continues..

You are about to reply to a thread that has been inactive for 2954 days.

Please take a moment to consider if this thread is worth bumping.

Question

  • 0

Hi Sophia,

I read your previous edit to last post so there is no graphics card driver conflict now if you are getting to the VFS initialisation stage.  You're past the SL not recognising your graphics card or driver. VFS unfortunately is another issue. VFS stands for Virtual File System and when it comes up like this in SL loading usually means there is an issue with the SL cache and deleting the SL files in AppData Local and Roaming normally fixes the problem. Hoewever, you already deleted them.

Can you please post your full computer specs from login page > Help > About Second Life.

At this stage I suggest you try another viewer such as Firestorm for Windows from http://www.phoenixviewer.com/

Sometimes one viewer will work fine when another doesn't.

  • Like 1

Share this post


Link to post
Share on other sites

9 answers to this question

Recommended Posts

  • 0

Hi Sophia,

I read your previous edit to last post so there is no graphics card driver conflict now if you are getting to the VFS initialisation stage.  You're past the SL not recognising your graphics card or driver. VFS unfortunately is another issue. VFS stands for Virtual File System and when it comes up like this in SL loading usually means there is an issue with the SL cache and deleting the SL files in AppData Local and Roaming normally fixes the problem. Hoewever, you already deleted them.

Can you please post your full computer specs from login page > Help > About Second Life.

At this stage I suggest you try another viewer such as Firestorm for Windows from http://www.phoenixviewer.com/

Sometimes one viewer will work fine when another doesn't.

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Sounds like you are having a terrible time with it. . I have only had this happen once and deleting the folder in the app data took care of it for me...

Have you tried installing Sl by running the exe as administrator? Might be worth a try. right click on the install EXE and run as administrator. Or try running your current install as administrator by right clicking the launch exe and run as admin.

Good Luck . I hope you get it sorted

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Hi Sophia,

Your computer specs look fine. The CPU has SSE2 support required by SL for v2/v3 viewers and your graphics card is fine.

Can you please provide more information on your network connection. I thought bluetooth modems were for dial-up 56kb/s connections using bluetooth to connect modem to computer and that won't work for Second Life. You need a broadband connection, preferably wired. Wireless can work too but is not supported by Linden Lab as it's prone to various issues.

Edit: Were you using your office connection with your old laptop when you joined as I see you joined in April and in various groups etc.

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Hi Sophia,

Well, that network connection is way more than SL needs so no problem there either.

I've run out of ideas other than to suggest you once again remove the folders in AppData. Ensure you restart the computer after doing so before you start the viewer again. Also, delete the Second Life Prefetch file in C > Windows > Prefetch as well just in case it is corrupted.

I'll drop a PM to a couple of other helpers who are expert  on computer issues and see if they can spot someting amiss.

 

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Looks like a lot of issues with OpenGl which SL uses. Maybe the Nvidia driver has not installed correctly but you have already uninstalled and reinstalled the driver. I'm out of ideas. I've sent a PM to someone who hopefully can add some suggestions when she comes online next. :)

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

I'm going to give this my best shot.  Before I do, I have to tell you that I'm no expert by anyone's definition......almost all my experience with computers and software comes from reading on the Internet and then attempting to fix what I'm trying to fix myself (I've messed up more operating systems and programs than most people......call me brave or foolish.  I'll admit to both).

I Googled VFS (virtual file system).  I found a Wiki article that is sort of technical but not so much that it's incomprehensible.  After reading the article with your problem in mind I found two possible sources that could be at the root of the issue.  The first being that you did not say if your XP is 32 bit or 64 bit instruction set.  You're CPU is a 64 bit processor but I know XP came in both flavors (either XP Pro x32 or XP Pro x64).  That is determined by the specific XP system that was installed on the computer (either initially or by some reinstallation at a later time).  Some recovery and full license disks have both versions and some don't.......if you don't have an x64 version then I would not worry too much about this suggestion (number 1  reason is that you are not likely to find a legal copy of XP anymore since Microsoft has set a date for discontinuing support for the OS).  But, there may be an option to convert the x32 to x64 either on the recovery/license disk that you have (I know my old XP Home Premium did have that conversion....but that was years ago).  X64 systems have been around long enough now that the chances of loosing any program by making the conversion is very low........I would try that myself.

The other thing (that I do think could be a factor) is that you also did not specify if your XP Pro's file system is FAT (file allocation table) either x32 or x64 or NTSF (new technology file system).  The older Windows OS's grew up based on the ancient DOS (disk operating system) developed by IBM for the first generation PC's (personal computers) and later "improved" by Microsoft with the MS-DOS) systems.  Beginning with XP you could install either FAT or NTSF on your computer.  I initially installed FAT 32 on my old computer when I moved up to XP from Win ME then later, during one of my many re-installs of XP I went with the NTSF.........things in XP suddenly started working better and I went from wondering why everyone was so in love with XP to a believer (I actually thought XP was worse than ME which everyone hated).

http://en.wikipedia.org/wiki/Virtual_file_system

The reason I think the NTSF (if you are still on a FAT system) might be the problem is after reading the Wiki I linked to I saw that Sun Microsystems developed VFS for Unix based system (Mac and Linux for the home users) and later added support for DOS based systems (Windows).  That indicates to me that the FAT system was an after thought.  Though NTSF is not Unix based it's much more in line with the more efficient Unix systems.........plus Microsoft was well aware of the necessity to support VFS when they developed the file system (VFS wasn't even thought about when DOS came about).  Patching up software to address a problem after the fact is never as good as addressing the problem from the ground up in development.  I can't remember whether or not you can convert from FAT to NTSF without reinstalling XP (it's been years ago and when I coverted I did at a reinstallation is all I remember about making the change).

And one other suggestion that might be easier and less scary.  I pretty sure your recovery/intallation disks have an option to repair or reinstall the system.  You might want to "repair" and see if that fixes the problem.  There is always the possibility that something damaged one of the system files that a repair would fix......and that would certainly be more painless than diving in head first like I often do :).

I'm sorry I can't be more helpful.  After reading all that you've done so far and nothing's worked and the fact that your problem isn't just one viewer I don't think it's a viewer problem or a driver problem.......and that leaves a system problem.  Not the best of news, I know........but I've got to be honest.  Keep in mind that XP's days are limited.  It just might be time to consider a new computer (or, at least, a new operating system).

Good luck.

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

That's great Sophia and thanks for coming back and explaining how you solved the problem, which may help others in the future. Enjoy your Second Life. :)

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

I want to second Nyil's congraduations on resolving your problem.  And, also, a great big "Thank you" for posting what you did to fix the sort of unusual problem you have been experiencing......I'm sure your detailed avenue to the solution will be of help for others with the problem.  It's not often that people come back and post their solution to problems for the benefit of others.  If I could give you more than 1 kudo I would.  :)

  • Like 1

Share this post


Link to post
Share on other sites
You are about to reply to a thread that has been inactive for 2954 days.

Please take a moment to consider if this thread is worth bumping.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...