Monday, July 31, 2006

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.Net.WebException: An exception occurred during a WebClient request. ---> System.ArgumentException: The path is not of a legal form.
   at System.IO.Path.nGetFullPathHelper(String path, Char[] invalidPathChars, Char[] whitespaceChars, Char directorySeparator, Char altDirectorySeparator, Char volumeSeparator, Boolean fullCheck, String& newPath)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.Path.GetFullPath(String path)
   at System.Net.WebClient.GetUri(String path)
   at System.Net.WebClient.OpenRead(String address)
   --- End of inner exception stack trace ---
   at System.Net.WebClient.OpenRead(String address)
   at Accentra.Applications.BlogObjects.Util.StringFromURL(String URL)
   at Accentra.Applications.BlogObjects.Publishing.Drops.RssSubscriptionDrop.GetRemoteRssDocument(String url)
   at Accentra.Applications.BlogObjects.Publishing.Drops.RssSubscriptionDrop.ImportAllPosts()
   at Accentra.Applications.BlogObjects.Publishing.Drops.RssSubscriptionDrop.Synchronize()
   at Accentra.Applications.BlogObjects.Blog.Synchronize()
   at Accentra.Applications.BlogObjects.PowerBlog.PersonalClient2.Gui.MainForm.SynchronizeBlog(Blog blog)
   at Accentra.Applications.BlogObjects.PowerBlog.PersonalClient2.Gui.MainForm.MainToolbar_ButtonClick(Object sender, ToolBarButtonClickEventArgs e)
   at System.Windows.Forms.ToolBar.OnButtonClick(ToolBarButtonClickEventArgs e)
   at System.Windows.Forms.ToolBar.WmReflectCommand(Message& m)
   at System.Windows.Forms.ToolBar.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
PowerBlog
    Assembly Version: 2.4.30.0
    Win32 Version: 2.4.30.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/PowerBlog.exe
----------------------------------------
BlogObjects2
    Assembly Version: 2.4.30.0
    Win32 Version: 2.4.30.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/BlogObjects2.DLL
----------------------------------------
System.Windows.Forms
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
CommonUtil
    Assembly Version: 2.1.18.28835
    Win32 Version: 2.1.18.28835
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/CommonUtil.DLL
----------------------------------------
System.Xml
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
PBAxScriptDrop
    Assembly Version: 2.2.20.28838
    Win32 Version: 2.2.20.28838
    CodeBase:
file:///c:/program%20files/comms/blogging/powerblog/exe/lib/pbaxscriptdrop.dll
----------------------------------------
Interop.MSScriptControl
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/Interop.MSScriptControl.DLL
----------------------------------------
Microsoft.mshtml
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.0.3300.0
    CodeBase:
file:///c:/winnt/assembly/gac/microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/microsoft.mshtml.dll
----------------------------------------
PBBloggerDrop
    Assembly Version: 2.2.20.28840
    Win32 Version: 2.2.20.28840
    CodeBase:
file:///c:/program%20files/comms/blogging/powerblog/exe/lib/pbbloggerdrop.dll
----------------------------------------
PBFtpDrop
    Assembly Version: 2.4.30.28839
    Win32 Version: 2.4.30.28839
    CodeBase:
file:///c:/program%20files/comms/blogging/powerblog/exe/lib/pbftpdrop.dll
----------------------------------------
PBNntpSubscriptionDrop
    Assembly Version: 2.2.20.28839
    Win32 Version: 2.2.20.28839
    CodeBase:
file:///c:/program%20files/comms/blogging/powerblog/exe/lib/pbnntpsubscriptiondrop.dll
----------------------------------------
PBRssSubscriptionDrop
    Assembly Version: 2.2.20.28839
    Win32 Version: 2.2.20.28839
    CodeBase:
file:///c:/program%20files/comms/blogging/powerblog/exe/lib/pbrsssubscriptiondrop.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 7.0.5000.0
    Win32 Version: 7.10.3052.4
    CodeBase:
file:///c:/winnt/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
----------------------------------------
MagicLocalLibrary
    Assembly Version: 1.8.0.0
    Win32 Version: 1.8.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/MagicLocalLibrary.DLL
----------------------------------------
AxInterop.SHDocVw
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/AxInterop.SHDocVw.DLL
----------------------------------------
Interop.SHDocVw
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/Interop.SHDocVw.DLL
----------------------------------------
Accessibility
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
----------------------------------------
CodeEditor
    Assembly Version: 2.0.2080.28837
    Win32 Version: 2.0.2080.28837
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/CodeEditor.DLL
----------------------------------------
System.Web.Services
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
----------------------------------------
Interop.ScriptableObjects
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/Interop.ScriptableObjects.DLL
----------------------------------------
System.Web
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase:
file:///c:/winnt/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
XmlRpc
    Assembly Version: 2.1.1.28834
    Win32 Version: 2.1.1.28834
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/XmlRpc.DLL
----------------------------------------
AxInterop.PBGrid6
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/AxInterop.PBGrid6.DLL
----------------------------------------
Interop.PBGrid6
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase:
file:///C:/Program%20Files/Comms/Blogging/PowerBlog/exe/Interop.PBGrid6.DLL
----------------------------------------


************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.


For example:


<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

Sunday, July 30, 2006

tag cloud

Monday, June 12, 2006

Open Office - Writer

Switching to linux also necessitates switching to an alternative office suiter, in this case OpenOffice.org's Writer. It gives me various bits of grief, so I'll be adding notes about those too. For example: I want section headings to be numbered, and to generate a table of contents from those headings. I also want footnote numbering in superscript

Tuesday, May 09, 2006

Kubunting - Notes & Categories

1. Notes:
how to do a forced shutdown; what's the equivalent of scandisk/chkdsk; do any versions of Linux run windows applications (e.g. Word & Excel?)
2. Let's see if I can get a tagger working...<br />
<br />
{Application Setup}<br />
{Desktop Configuration}<br />
{Networking}<br />
{O/S Basics}<br />
{System Maintenance}<br />
{Ubuntu Forums}
{Notes}

Kubuntu Queries 2

{System Maintenance}
I have had misadventures in discovering how to sequence the reinstallation of XP and Kubuntu, and would like to develop an efficient method for backing up and restoring both, including backup and restore of the GRUB bootloader.

At present I use the XP CD to reformat the drive, then reinstall XP, then use the Kubuntu CD to reinstall Kubuntu and the bootloader. However, I have noted that the bootloader is corrupted/wiped out whenever I do an XP repair, so I'd like to have way of restoring that independently of doing the Kubuntu installation.

Having read the "HOWTO: Restore GRUB (if your MBR is messed up)" thread and a few others, I am still looking for a way to back-up the bootloader. I am still working out the conceptual differences between and MBR bootloader and a root directory bootloader, and guess that a root bootloader would be easier to backup and restore. But I think my current installation uses an MBR option. So there's that to deal with in addition...
Suggestions?

{System Maintenance}
During one of my attempts to read the windows partition via kubuntu, I created a mount point that doesn't do anything, but which I cannot delete. I suspect that I created it via the Disk and Filesystems utility when I failed to replace <mount point> with something else in one of the options fields.
Click here to see a large version
Now it shows up every time I visit the home directory. How do I ret rid of it?

Click here to see a large version
* Note: there is an additional question about setting permissions so that I can make changes to files on the Windows partition. But I haven't gotten to that yet...

{Ubuntu Forums}
Is there a way of searching for an exact phrase? "phrase strings" and phrase+strings don't do anything other than return results of the individual words. So when I want to search on "backup GRUB" it returns all results for 'backup' and 'GRUB', which makes the trawling task much longer.