Recent Activity

• 

  Downloading pre-2.0 beta?

  Hi again, people!

  I had a huge problem with the 0.9.2375.0 build - any feeds clicked-on generates the "Runtime error in '/' application" webpage (see that topic for more info)

  I went and uninstalled 0.9.2375.0 and did a reboot to make sure things were "clean", and then proceeded to install what I thought was the 0.9.2375.0 build - lo and behold I the install that I thought was 0.9.2375.0 turned out to be 0.9.2258.0 !!

  I am totally unable to install 0.9.2258.0 - .Net Framework asserts all over the place, and it will not run.

  Can *anyone* point me to actual 0.9.2375.0 install bits that I can download and try to resolve this? Feel free to email me at scott-at-kindorf-dot-net.

  Thanks!!

   

  Posted 03 Aug 08

• 

  V2 Status?

  Any info, folks? Many of us here seem to be chomping at the bit here.

  -ScottK

  Posted 01 Aug 08

• 

  "Runtime error in "/" application

  Hi, folks!

  I had poster about an issue I had with Particls two days ago, but it seems to have been lost. It was concerning an error that indicated that the disk image database was corrupted. Lo and behold, I fire up Particls today and no error....well, not really...just a NEW one!

  This happens when I click on ANY feed on the News Ticker:

  Runtime Error

  Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
  
  Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
  

  <!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

  
  Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
  

  <!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

  (Signal Flare fired into the air...ummm...the Net)

  --ScottK

  Posted 01 Aug 08