[sldev] compile is ok, but i get error at startup

karen at lindenlab.com karen at lindenlab.com
Thu Feb 22 23:10:57 PST 2007
Previous message: [sldev] compile is ok, but i get error at startup
Next message: [sldev] mono embedded on SL client
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alright, my last idea (before I turn in for the night) is to compile the
debug version and run it from Dev Studio. A console window should open up
when you launch which may give more detailed information.

Have you reviewed the items on the Open Source Windows build page
(http://wiki.secondlife.com/wiki/Compiling_the_viewer_%28MS_Windows_-_Visual_Studio_.NET_2003%29)
to be sure you're not missing anything?

-=-Karen


> Karen,
>
> Thank you.
>
> I've found the SecondLife/logs directory.
>
> There is a file in there called debug_info.log.
>
> I didn't see anything useful in there, but you may know what to look for.
> I've appended it...
>
> <<<<
>
>
> SL Log:
> Second Life version 1.13.3 build 3
> Not supported (3000 Mhz)
> RAM: 2146676736
> OS: Microsoft Windows XP Service Pack 2 (Build 2600)
>
> StartAllDevices
> StartDevice
> DeviceName:Texas Instruments OHCI Compliant IEEE 1394 Host Controller
> PCIString:PCI\VEN_104C&DEV_8023&SUBSYS_808B1043&REV_00\4&2411F011&0&5890
> Filename:1394bus.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:arp1394.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:enum1394.sys
> Ver:5.01.2600.0000
> Date:8/17/2001 05:46:40
> Filename:nic1394.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:ohci1394.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:Silicon Image SiI 3132 SATALink Controller
> PCIString:PCI\VEN_1095&DEV_3132&SUBSYS_819F1043&REV_01\4&29E3D116&0&0028
> Filename:SI3132.sys
> Ver:1.00.0000.0009
> Date:1/19/2005 06:30:52
> Filename:SiWinAcc.sys
> Ver:1.00.0000.0011
> Date:11/1/2004 03:21:32
> Filename:SilSupp.cpl
> Ver:3.00.0000.0018
> Date:1/11/2005 02:56:46
> EndDevice
> StartDevice
> DeviceName:PCI standard ISA bridge
> PCIString:PCI\VEN_10DE&DEV_0050&SUBSYS_00000000&REV_A4\3&267A616A&0&50
> Filename:isapnp.sys
> Ver:5.01.2600.0000
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:NVIDIA nForce PCI System Management
> PCIString:PCI\VEN_10DE&DEV_0052&SUBSYS_81621043&REV_A2\3&267A616A&0&51
> EndDevice
> StartDevice
> DeviceName:Standard Dual Channel PCI IDE Controller
> PCIString:PCI\VEN_10DE&DEV_0053&SUBSYS_81621043&REV_F3\3&267A616A&0&78
> Filename:atapi.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:pciide.sys
> Ver:5.01.2600.0000
> Date:8/4/2004 04:00:00
> Filename:pciidex.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:NVIDIA nForce4 Serial ATA Controller
> PCIString:PCI\VEN_10DE&DEV_0054&SUBSYS_81621043&REV_F3\3&267A616A&0&80
> Filename:NVCOI.DLL
> Ver:1.00.0000.0029
> Date:8/2/2005 22:52:08
> Filename:idecoi.dll
> Ver:1.00.0000.0001
> Date:8/18/2005 01:52:08
> Filename:idecoins.dll
> Ver:1.00.0000.0001
> Date:8/18/2005 01:52:08
> Filename:nvata.sys
> Ver:5.10.2600.0552
> Date:8/18/2005 01:52:06
> EndDevice
> StartDevice
> DeviceName:NVIDIA nForce4 Serial ATA Controller
> PCIString:PCI\VEN_10DE&DEV_0055&SUBSYS_81621043&REV_F3\3&267A616A&0&88
> Filename:NVCOI.DLL
> Ver:1.00.0000.0029
> Date:8/2/2005 22:52:08
> Filename:idecoi.dll
> Ver:1.00.0000.0001
> Date:8/18/2005 01:52:08
> Filename:idecoins.dll
> Ver:1.00.0000.0001
> Date:8/18/2005 01:52:08
> Filename:nvata.sys
> Ver:5.10.2600.0552
> Date:8/18/2005 01:52:06
> EndDevice
> StartDevice
> DeviceName:NVIDIA Network Bus Enumerator
> PCIString:PCI\VEN_10DE&DEV_0057&SUBSYS_81D31043&REV_A3\3&267A616A&0&98
> Filename:bdco1.dll
> Ver:1.00.0000.0000
> Date:7/26/2005 01:45:30
> Filename:bdco1ins.dll
> Ver:1.00.0000.0000
> Date:7/26/2005 01:45:30
> Filename:nvconrm.dll
> Ver:1.00.0000.0027
> Date:7/20/2005 01:08:20
> Filename:nvconrmins.dll
> Ver:1.00.0000.0027
> Date:7/20/2005 01:08:20
> Filename:nvnetbus.sys
> Ver:1.00.0000.0509
> Date:7/26/2005 01:48:30
> Filename:nvnrm.sys
> Ver:1.00.0000.0509
> Date:7/26/2005 01:48:14
> Filename:nvsnpu.sys
> Ver:1.00.0000.0509
> Date:7/26/2005 01:48:06
> EndDevice
> StartDevice
> DeviceName:Realtek AC'97 Audio
> PCIString:PCI\VEN_10DE&DEV_0059&SUBSYS_812A1043&REV_A2\3&267A616A&0&68
> Filename:ALCXWDM.SYS
> Ver:5.10.0000.5900
> Date:8/19/2005 01:31:52
> Filename:ALSNDMGR.CPL
> Ver:2.02.0000.0048
> Date:8/17/2005 02:25:20
> Filename:ALSNDMGR.WAV
> Ver:
> Date:2/4/2002 21:54:58
> Filename:RTLCPAPI.dll
> Ver:1.00.0000.0004
> Date:9/6/2004 22:23:16
> Filename:RTLCPL.EXE
> Ver:1.00.0001.0050
> Date:8/17/2005 02:21:38
> Filename:SOUNDMAN.EXE
> Ver:5.01.0000.0043
> Date:8/17/2005 02:39:58
> Filename:drmk.sys
> Ver:5.01.2600.2180
> Date:8/3/2004 22:08:00
> Filename:ks.sys
> Ver:5.03.2600.2180
> Date:8/3/2004 22:15:22
> Filename:ksproxy.ax
> Ver:5.03.2600.2180
> Date:8/3/2004 23:56:58
> Filename:ksuser.dll
> Ver:5.03.2600.2180
> Date:8/3/2004 23:56:44
> Filename:portcls.sys
> Ver:5.01.2600.2180
> Date:8/3/2004 22:15:50
> Filename:stream.sys
> Ver:5.03.2600.2180
> Date:8/3/2004 22:08:04
> Filename:wdmaud.drv
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:Standard OpenHCD USB Host Controller
> PCIString:PCI\VEN_10DE&DEV_005A&SUBSYS_81621043&REV_A2\3&267A616A&0&58
> Filename:usbhub.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbohci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbport.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbui.dll
> Ver:5.01.2600.2180
> Date:8/3/2004 16:56:48
> EndDevice
> StartDevice
> DeviceName:Standard Enhanced PCI to USB Host Controller
> PCIString:PCI\VEN_10DE&DEV_005B&SUBSYS_81621043&REV_A4\3&267A616A&0&59
> Filename:hccoin.dll
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbehci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbhub.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbport.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> Filename:usbui.dll
> Ver:5.01.2600.2180
> Date:8/3/2004 16:56:48
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&267A616A&0&90
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&267A616A&0&A0
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&267A616A&0&B0
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&267A616A&0&B8
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:nForce4 HyperTransport Bridge
> PCIString:PCI\VEN_10DE&DEV_005E&SUBSYS_81621043&REV_A4\3&267A616A&0&48
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_006F&SUBSYS_81891043&REV_A1\3&267A616A&0&03
> EndDevice
> StartDevice
> DeviceName:PCI standard host CPU bridge
> PCIString:PCI\VEN_10DE&DEV_0071&SUBSYS_00000000&REV_A3\3&267A616A&0&00
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_0075&SUBSYS_81891043&REV_A1\3&267A616A&0&02
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_0076&SUBSYS_81891043&REV_A1\3&267A616A&0&08
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_0078&SUBSYS_81891043&REV_A1\3&267A616A&0&09
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_0079&SUBSYS_81891043&REV_A1\3&267A616A&0&0A
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_007A&SUBSYS_81891043&REV_A1\3&267A616A&0&0B
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_007B&SUBSYS_81891043&REV_A1\3&267A616A&0&0C
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_007C&SUBSYS_81891043&REV_A1\3&267A616A&0&0D
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_007D&SUBSYS_81891043&REV_A1\3&267A616A&0&0E
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&267A616A&0&10
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&267A616A&0&20
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&267A616A&0&28
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&267A616A&0&30
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard PCI-to-PCI bridge
> PCIString:PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&267A616A&0&38
> Filename:pci.sys
> Ver:5.01.2600.2180
> Date:8/4/2004 04:00:00
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_007F&SUBSYS_81891043&REV_A1\3&267A616A&0&01
> EndDevice
> StartDevice
> DeviceName:PCI standard RAM Controller
> PCIString:PCI\VEN_10DE&DEV_00B4&SUBSYS_81891043&REV_A1\3&267A616A&0&04
> EndDevice
> StartDevice
> DeviceName:NVIDIA Quadro FX 1400
> PCIString:PCI\VEN_10DE&DEV_00CE&SUBSYS_024310DE&REV_A2\4&20C03BEB&0&0010
> Filename:nv4_disp.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nv4_mini.sys
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvapi.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvcod.dll
> Ver:1.00.0000.0032
> Date:11/4/2005 08:38:00
> Filename:nvcodins.dll
> Ver:1.00.0000.0032
> Date:11/4/2005 08:38:00
> Filename:nvcpl.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvcpl.hlp
> Ver:
> Date:11/4/2005 08:38:00
> Filename:nvhwvid.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvmccs.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvmctray.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvnt4cpl.dll
> Ver:6.14.0010.11009
> Date:11/4/2005 08:38:00
> Filename:nvoglnt.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvsvc32.exe
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> Filename:nvwcplen.hlp
> Ver:
> Date:11/4/2005 08:38:00
> Filename:nvwddi.dll
> Ver:6.14.0010.8167
> Date:11/4/2005 08:38:00
> EndDevice
> StartDevice
> DeviceName:Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller
> PCIString:PCI\VEN_11AB&DEV_4362&SUBSYS_532111AB&REV_22\4&2145A711&0&0038
> Filename:yk51x86.sys
> Ver:8.24.0003.0003
> Date:3/30/2005 07:24:00
> EndDevice
> EndAllDevices
>
>
>
>
>
> On 2/22/07, karen at lindenlab.com <karen at lindenlab.com> wrote:
>>
>> Unfortunately, I don't have a dev environment in front of me right now.
>> When you run release_noopt, you should have a log console that shows you
>> errors. Generally, the errors write to the normal SL log. To find that
>> log, you will need to turn on "Show Hidden Files" in the Folder Options
>> menu. Once you've done that, you can go to C:\Documents and
>> Settings\(your
>> user name)\Application Data\SecondLife\logs and you should find the log.
>>
>> Please let me know if this still doesn't help and I can take a look at
>> the
>> problem tomorrow when I'm in the office.
>>
>> -=-Karen
>>
>>
>> > Karen,
>> >
>> > Yes, that one gave me the error.
>> >
>> > I am building the production version as I write this.
>> >
>> >
>> >
>> > On 2/22/07, karen at lindenlab.com <karen at lindenlab.com> wrote:
>> >>
>> >> Hi George,
>> >>
>> >> What option are you compiling with? Release_NoOpt?
>> >>
>> >> -=-Karen
>> >>
>> >> > Karen,
>> >> >
>> >> > I can't seem to find this log file anywhere under my src/build
>> >> folders.
>> >> > Is
>> >> > it located somewhere else on the machine?
>> >> >
>> >> > Thank you.
>> >> >
>> >> >
>> >> >
>> >> > On 2/22/07, karen at lindenlab.com <karen at lindenlab.com> wrote:
>> >> >>
>> >> >> Hi George,
>> >> >>
>> >> >> There should be something useful in your logs/SecondLife.log file.
>> >> Can
>> >> >> you
>> >> >> send in the last 50 lines or so?
>> >> >>
>> >> >> -=-Karen
>> >> >>
>> >> >>
>> >> >> > Hi,
>> >> >> >
>> >> >> > I think I'm being a bonehead - can someone help?
>> >> >> >
>> >> >> > I am building "slviewer-src-FL-1.13.3.58018".  It builds ok.
>> When
>> >> a
>> >> >> start
>> >> >> > the program, I get a dialogue a few seconds later:
>> >> >> >
>> >> >> > "Second Life is unable to access a file that it needs.
>> >> >> >
>> >> >> > This can be because you somehow have multiple copies running, or
>> >> your
>> >> >> > system
>> >> >> > incorrectly thinks a file is open.  If this message persists,
>> >> restart
>> >> >> your
>> >> >> > computer and try again.  If it continues to persist, you may
>> need
>> >> to
>> >> >> > complete uninstall Second Life and reinstall it."
>> >> >> >
>> >> >> > Thank for your help, in advance.
>> >> >> > _______________________________________________
>> >> >> > Click here to unsubscribe or manage your list subscription:
>> >> >> > /index.html
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>
Previous message: [sldev] compile is ok, but i get error at startup
Next message: [sldev] mono embedded on SL client
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the SLDev mailing list