SlimmGBPVR - replacement for GBPVRTray

[bluesxman]

I get no luck with this version, I'm afraid. As soon as I fire it up, I see the "Slimm GBPVR has encountered a problem and needs to close" message box along with the offer to send the details to Microsoft.

SlimmGBPVR.exe.log contains:

Code:

29/12/2005 09:37:15.640    VERBOSE    [1]    installDirectory is D:\Program Files\devnz\gbpvr\
29/12/2005 09:37:15.640    VERBOSE    [1]    configurationFile is config.xml
29/12/2005 09:37:15.656    VERBOSE    [1]    getValue() loading new key/value into cache: /settings/DatabaseConnectionString
29/12/2005 09:37:15.656    VERBOSE    [1]    getValue: /settings/DatabaseConnectionString : Provider=Microsoft.Jet.OLEDB.4.0;Data Source=".\gbpvr.mdb";User Id=admin;Password=
29/12/2005 09:37:15.656    VERBOSE    [1]    databaseConnectionString is Provider=Microsoft.Jet.OLEDB.4.0;Data Source="D:\Program Files\devnz\gbpvr\\gbpvr.mdb";User Id=admin;Password=
29/12/2005 09:37:15.656    VERBOSE    [1]    getValue() loading new key/value into cache: /settings/DontAntiAlias
29/12/2005 09:37:15.656    VERBOSE    [1]    getValue: /settings/DontAntiAlias : false
29/12/2005 09:37:15.656    VERBOSE    [1]    getValue() loading new key/value into cache: /settings/LoggingLevel
29/12/2005 09:37:15.656    VERBOSE    [1]    getValue: /settings/LoggingLevel : Debug
29/12/2005 09:37:15.656    VERBOSE    [1]    getDatabaseConnection() creating new connection
29/12/2005 09:37:15.687    VERBOSE    [1]    MusicLibrary2: Skin Loaded
29/12/2005 09:37:15.765    VERBOSE    [1]    MyMusicTask created
29/12/2005 09:37:15.890    VERBOSE    [1]    WeatherTask created
29/12/2005 09:37:15.921    VERBOSE    [1]    creating DirectRecordingSource
29/12/2005 09:37:15.921    VERBOSE    [1]    Loading DirectRecordingSource Configuration : 1
29/12/2005 09:37:15.937    VERBOSE    [1]    About to connect to remote recording service
29/12/2005 09:37:15.937    VERBOSE    [1]    getValue() loading new key/value into cache: /settings/RecordingServiceLocation
29/12/2005 09:37:15.937    VERBOSE    [1]    getValue: /settings/RecordingServiceLocation : tcp://localhost:7968/RecordingRemote
29/12/2005 09:37:15.953    VERBOSE    [1]    RecordingFactory.loadSchedule()
29/12/2005 09:37:15.953    VERBOSE    [1]    getValue() loading new key/value into cache: /settings/AutoRemoveMissingRecordings
29/12/2005 09:37:15.953    VERBOSE    [1]    getValue: /settings/AutoRemoveMissingRecordings : true
29/12/2005 09:37:15.953    VERBOSE    [1]    Purging any stale logically deleted recordings
29/12/2005 09:37:15.968    VERBOSE    [1]    RecordingFactory.loadSchedule()
29/12/2005 09:37:15.968    VERBOSE    [1]    getValue cached value: /settings/AutoRemoveMissingRecordings : true

The previous version (.832) worked fine. Any ideas?

*edit* just seen this in event viewer, under .NET Runtime 2.0 Error Reporting

Code:

EventType clr20r3, P1 slimmgbpvr.exe, P2 0.9.2189.6510, P3 43b359dd, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 1546, P8 21, P9 system.argumentoutofrange, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[Mister Slimm]

I get no luck with this version, I'm afraid. As soon as I fire it up, I see the "Slimm GBPVR has encountered a problem and needs to close" message box along with the offer to send the details to Microsoft.

Youch, nasty. As is probably obvious, I don't get this on my setup but I have an idea it may be to do with .NET 2.0 handling multi-threading much more strictly than .NET 1.1. Typically unhelpful Microsoft error message though. Anyone else having the same problem?

Thanks to your edit, I have found the cause of the error. It is a breaking change in .NET 2.0! I now need to track down the piece of my code that's got the problem and causing .NET 2.0 to terminate my process.

Do you see the splash screen? Does the system tray icon appear then disappear? Or do you see absolutely nothing except the error message?

[Mister Slimm]

I get no luck with this version, I'm afraid. As soon as I fire it up, I see the "Slimm GBPVR has encountered a problem and needs to close" message box along with the offer to send the details to Microsoft.

Does this version (0.9.2189.26067) help with the insta-crash problem?

Download latest version from Slimm Solutions.
Direct download link

[BobAtTorrey]

Sorry to further complicate things, but .....
As I reported earlier, I installed v .9 which crashed. I then installed .832 and it ran. However, after that I've got two other solid problems:

1. Net Radio doesn't work. Every station gets "Failed to connect", whereas it previously worked perfectly. No apparent error in any of the logs.

2. Music Player, which previously worked fine, now gets the error "Object reference not set to an instance of an object" [using MVP, Flat Blue-High Vis skin]. This seems to show up in the logs, but strangely. (see below)

Is there anything in the SlimmGBPVR installation process of either .9 or .832 or execution of .832 that could have messed up these other plugins?

_____________________
12/29/2005 9:42:55 AM.809 ERROR [137] Object reference not set to an instance of an object.
12/29/2005 9:42:55 AM.809 ERROR [137] at MyPicturesPlugin.GBPVREventViewer.Notify(EventTypes type, String eventText)
at xd426863f4d052758.xc4f12ec3a8a4c96b.x85b8d963f05ddf09(EventTypes x4f04899de3605e17, String xbc19b591abc4848a)
at xae10db17d26ba033.x62b73fb0db4f3947.x826e5d374a1e5ab9(String x8b449efd64797843, Boolean x859a785ef30c9007, Boolean xe1ea8da9364d6bfb)
at xae10db17d26ba033.x62b73fb0db4f3947.x313dba8d86564907(Queue x67c4bec203dc37ec)
at xae10db17d26ba033.xbb1566157f5f8b1f.AddAudioFileToQueue(String x8b449efd64797843)
at MusicPlayerPlugin.MusicPlayerTask.QueueDirectoryContents(DirInfo rootDir)
at MusicPlayerPlugin.MusicPlayerTask.QueueDirectoryContents(DirInfo rootDir)
at MusicPlayerPlugin.MusicPlayerTask.OnKeyDown(KeyEventArgs e)
at xae10db17d26ba033.x86396f56243de9fb.OnKeyDown(KeyEventArgs xc4f45905cb1fc7ba)
at xae10db17d26ba033.x86396f56243de9fb.OnKeyDown(KeyEventArgs xc4f45905cb1fc7ba)
at xae10db17d26ba033.xbb1566157f5f8b1f.xdae9991ab918b397(Object xdf2e3583f942db7b, KeyEventArgs xc4f45905cb1fc7ba)
at xae10db17d26ba033.xbb1566157f5f8b1f.x458c85690540575e()

[Mister Slimm]

Is there anything in the SlimmGBPVR installation process of either .9 or .832 or execution of .832 that could have messed up these other plugins?

To the best of my knowledge, installation and execution of SlimmGBPVR should have no effect on the GB-PVR installation. It is a separate utility and makes no changes to GB-PVR in any way. The files installed in the GB-PVR folder are SlimmGBPVR.exe, SlimmGBPVRHelper.dll, SlimmGBPVR.exe.manifest and SlimmGBPVRHelp.chm.

[bluesxman]

Does this version (0.9.2189.26067) help with the insta-crash problem?

No, unfortunately it's still the same.

Do you see the splash screen? Does the system tray icon appear then disappear? Or do you see absolutely nothing except the error message?

Sorry, I should have said. I do see the splash screen and the icon. The icon disappears on mouse over.

[Mister Slimm]

Thanks for the feedback and bug reports. Beta version moves up to version 0.9.2191.29032

Features:

• Program errors are now written to "SlimmGBPVR.error.log" in the GBPVR program folder. If reporting any bugs or errors, please include any error information found in this file.
  

Bug fixes:

• Hopefully, the crashing bugs users have experienced with the beta should now be gone. Please report.
  

[bluesxman]

I'm still seeing the same thing. Had a look in SlimmGBPVR.error.log, but all it had was this one line:

SlimmGBPVR.exe Information: 0 : Started at 31/12/2005 18:11:24

Happy new year!

[Mister Slimm]

I'm still seeing the same thing.

Guess I'll have to complete full exception handling in the other half of the program aswell then. Oh well, I'll post another new version in a bit. Sorry to be putting you through this bother but, as I mentioned before, I don't see these problems on my own machine. Programmers are absolutely useless at causing bugs, it's always easier for someone else to find them, and I am very grateful for your patience and assistance in this regard.

[bluesxman]

Guess I'll have to complete full exception handling in the other half of the program aswell then. Oh well, I'll post another new version in a bit. Sorry to be putting you through this bother but, as I mentioned before, I don't see these problems on my own machine. Programmers are absolutely useless at causing bugs, it's always easier for someone else to find them, and I am very grateful for your patience and assistance in this regard.

It's certainly no bother to test these builds out for you, I'm grateful for the work you've put in as I find this utility really useful. That said I'm more than happy with the version that does work for me and am unlikely to make much use of the new features, so don't put yourself out on my account!