MSFN Forum: Error Opening .ul File - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Error Opening .ul File Help

#1 User is offline   zulebg 

  • Group: Members
  • Posts: 4
  • Joined: 14-November 06

Posted 15 November 2006 - 11:36 AM

I receive Unhandled exception error dialog box ...

I click details button and it says this :

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

************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(String fileName)
at WUD.formMain.toolStripButtonAddUL_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WUD
Assembly Version: 2.23.842.0
Win32 Version: 2.23.842.0
CodeBase: file:///C:/Program%20Files/Windows%20Updates%20Downloader/WUD.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.84.0.0
Win32 Version: 0.84.0.0
CodeBase: file:///C:/Program%20Files/Windows%20Updates%20Downloader/ICSharpCode.SharpZipLib.DLL
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (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 computer
rather than be handled by this dialog box.


#2 User is offline   zulebg 

  • Group: Members
  • Posts: 4
  • Joined: 14-November 06

Posted 16 November 2006 - 05:31 PM

Help anyone ?

thanks in advance

#3 User is offline   Red Knight 

  • Newbie
  • Group: Members
  • Posts: 22
  • Joined: 30-August 06

Posted 20 November 2006 - 08:38 AM

Can you say when exactly this error occures? May be I just don't understand...
If you need to OPEN .ul file - try notepad.
If to install to WUD - place it to WUD dir on your HDD & open WUD , try to double-click on file after extracting or something :)
No answers in this top indicates that nobody ever seen this error...May be you do something wrong?

P.S. Please , describe what are you doing when ulz file downloaded on your machine.

This post has been edited by Red Knight: 20 November 2006 - 08:42 AM


#4 User is offline   EasternShore 

  • Group: Members
  • Posts: 1
  • Joined: 20-November 06

Posted 20 November 2006 - 11:12 PM

got the same error, until I figured out that the update lists are compressed when downloaded. All I had to do was double click on each download list to extract and the program runs fine now.

#5 User is offline   Red Knight 

  • Newbie
  • Group: Members
  • Posts: 22
  • Joined: 30-August 06

Posted 21 November 2006 - 12:16 PM

View PostRed Knight, on Nov 20 2006, 07:38 PM, said:

try to double-click on file after extracting

Well I thought about it , so asked for details :) It's all described on this forum , now installation an ULs is much more easy then it was :)
For example , ENG ULs installs by double-click on them from ANY location on your PC , but RUS ULs which I needed - only if it's placed in WUD dir.

Thanks to EasternShore for his post & it's really interesting , what will author say :)

#6 User is offline   jcarle 

  • MSFN Master
  • Group: Developers
  • Posts: 2,563
  • Joined: 14-August 04

Posted 21 November 2006 - 01:55 PM

UL is the uncompressed update list. ULZ is the compressed update list. When WUD is first run, it is associated with the ULZ file extension so that when you open a ULZ file, it will extract the UL and save it to the WUD program directory.

The point is so that you can just click on the UL you want on the WUD home page, and instead of doing Save As... you choose Open, and the UL will automatically be installed.

#7 User is offline   trefrog 

  • Newbie
  • Group: Members
  • Posts: 10
  • Joined: 12-December 06

Posted 27 January 2008 - 05:01 PM

mine isn't working that way for some reason. It's been a while since I ran it, but today I noticed the ulz extension wasn't registered to WUD, so I uninstalled and reinstalled WUD. The association was restored, but when WUD opens after running the ulz it still says no update list was found. Seems that the file is being passed into WUD, but it doesn't know what to do with it, so it doesn't act to decompress & create any new ul file.

#8 User is offline   jcarle 

  • MSFN Master
  • Group: Developers
  • Posts: 2,563
  • Joined: 14-August 04

Posted 28 January 2008 - 01:56 AM

Make sure after you install a install the ULZ, if WUD is already open, to hit the Refresh button.

#9 User is offline   trefrog 

  • Newbie
  • Group: Members
  • Posts: 10
  • Joined: 12-December 06

Posted 31 January 2008 - 01:04 AM

Tried that. Still didn't work. I don't believe the ulz is even decompressing, and I know it's not copying the ul to WUD dir, like it's supposed to. I'm running it out of J:\Program Files by the way, which isn't my official Program Files dir (C: partition is too small due to my nLite attempt only half finished - the goal being to seperate the WINDOWS dir from Documents and Settings, Program Files and pagefile.sys as well - a pristine windows partition - FYI), if that has any bearing on the issue...

All my other programs run fine this way so far, I just change C: to J: whenever I install something. this was only intended to be a temporary install for testing my nLite build... moons ago.

Edit:
oh, when I run WUD first before opening the ULZ, a new instance opens up with the not found message and stays open. It's definitely not supposed to do that, I'm sure.

This post has been edited by trefrog: 31 January 2008 - 01:06 AM


#10 User is offline   jcarle 

  • MSFN Master
  • Group: Developers
  • Posts: 2,563
  • Joined: 14-August 04

Posted 31 January 2008 - 10:11 AM

Make sure the ICSharpCode.SharpZipLib.dll binary is in the same folder as WUD.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy