I have this little dance I generally have to go through to start SL on my WinXP box.
1. Crank the PC up.
2. Log in to WinXP (I keep a Guest account for folks who occasionally want to use the box.)
3. Start Newview.exe (now SecondLife.exe)
4. Watch the title bar and window frame form for the SL client, along with the "Loading Second Life" alert box...and then the screen freezes. I'm able to open other apps over the top of the stalled client, but if I close them, the windows remain painted on top of the SL client. I can minimize the SL client down into the task bar, but I can neither stop it (by X-ing out the window) nor proceed with it. If I maximize the SL window, it shows its last corrupted condition.
5. Open Task Manager, and kill both the application and the associated process tree.
6. Wait 5-15 minutes
for the Process Manager to actually seize the task and kill it.7. Re-start the Sl client.
8. Log in normally.
For some reason, if I start a WinXP session and just let the machine sit for anywhere from 10 minutes to an hour, I can get a normal startup on the SL client the very first time. I'm mystified by what WinXP could be doing in the background for that long after a session start to interfere with the SL startup.
Does anyone have any idea what I could do to fix this? I'm strictly a consumer-level Windows user
Thanks!
-- jj
