If you use a Filemonitor you'll see what libraries will load for the .NET Framework at startup. There is no specific dependency list I'm aware of.
Can we get a list of file dependencies so us nLiters can choose the correct components for PhoCo to operate?
Status: 40%
Car: 2006 Scion tC (Buying)
CPU: AOpen Pandora/1.5 Cel M/1GB DDR2/Ipod Vid
Screen: Lilliput 7"
Power: Carnetix 1900
GPS: Deluo GPS
Software: nLiteXP, RR, IG, PhoCo
XM: XM Direct
http://www.chrispuckett.com/mp3car/
If you use a Filemonitor you'll see what libraries will load for the .NET Framework at startup. There is no specific dependency list I'm aware of.
Skinning to go... VisualDesigner2!
Hi Zorro,
I am new to PhoCo... in fact my only reason why I have chosen to give it a try was I installed Centrafuse so I want to try integration with Radiator, PhoneControl and Destinator.
Thats why I have downloaded latest 1.4 beta I found the link for in CF annoncement thread. I have it installed with no errors but it does not launch showing folowing error:
-----
PhoneCtl.NET.exe - Common language debug...
Application has generated an exception that can not be handled
Process id= 0x498 (1176) Thread id 0x49c (1180)
Press...
-----------
I wonder whether this is caused by my setup or because I use MS only BlueTooth driver (from SP2), or because of some dependancy problem.
OS: WinXP w. SP2 Professional Czech
.NET: 1.1 SP1
BT adaptor: Billionton USBBT02-B (MS drivers only)
Would you have any advice for me?
Please check that you have the latest DirectX installed.
Skinning to go... VisualDesigner2!
Yes, 9.0c, all the DXDIAG tetst were executed with no issues found.
Try it on another machine. I guess your XP installation has a problem.
Skinning to go... VisualDesigner2!
I neither can get the software to start. XP Pro, SP2. Same error message as above.
Coz you asked about DX9...Might this problem be caused by VGA driver incpomatibility or so? BTW I am trying to run PhoCo on EPIA M10K, latest BIOS and VGA drivers.
I run it as well on a EPIA M10K... but with the standard drivers.
This error occures when some (OS) component is missing. Sometimes this can be corrected by letting Windows-Update to check your system and install (missing) patches.
Skinning to go... VisualDesigner2!
Bookmarks