vLite 1.1B; Unhandled exception; Invalid URI

[pub3lic@gmail.com]

Hello,

vLite looks great, but I'm not getting very far.

I get the below error, when run in the following contexts:

- VMWare 6 vm of vista32 x32 ultimate after loading v32 ultimate files from dvd to local folder, choosing vista version

- WinSrv 08 x64 RCO on quad core intel cpu, 8GB RAM, after loading either v32 or v64 ultimate from dvd to local folder, choosing vista version

Thank You,

Mark

["Details" from Error msg box follow:]

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.UriFormatException: Invalid URI: A Dos path must be rooted, for example, 'c:\'.

at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)

at System.Uri..ctor(String uriString, UriKind uriKind)

at System.Xml.XmlResolver.ResolveUri(Uri baseUri, String relativeUri)

at System.Xml.XmlUrlResolver.ResolveUri(Uri baseUri, String relativeUri)

at System.Xml.XmlTextReaderImpl..ctor(String url, XmlNameTable nt)

at System.Xml.XmlTextReader..ctor(String url)

at ..

()

at .. ()

at ..(Boolean )

at ..$(Object , EventArgs )

at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)

at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)

at System.Windows.Forms.ComboBox.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.1416 (REDBITS.050727-1400)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

vlite

Assembly Version: 1.1.0.0

Win32 Version: 1.1.0.0

CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vLite.exe

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.1416 (REDBITS.050727-1400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

vLite

Assembly Version: 1.1.0.0

Win32 Version: 1.1.0.0

CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vLite.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.1416 (REDBITS.050727-1400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.1416 (REDBITS.050727-1400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

MCDBNET2

Assembly Version: 1.3.3.33894

Win32 Version: 1.33.0.133

CodeBase: file:///C:/Program%20Files%20(x86)/vLite/MCDBNET2.DLL

----------------------------------------

msvcm80

Assembly Version: 8.0.50727.1416

Win32 Version: 8.00.50727.1416

CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1416_none_d08931de442e89b3/msvcm80.dll

----------------------------------------

vhelper

Assembly Version: 1.0.2773.19826

Win32 Version: 1, 0, 0, 1

CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vhelper.DLL

----------------------------------------

msvcm80

Assembly Version: 8.0.50727.762

Win32 Version: 8.00.50727.762

CodeBase: file:///C:/Program%20Files%20(x86)/vLite/msvcm80.DLL

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.1416 (REDBITS.050727-1400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

[pub3lic@gmail.com]

Hello,

It appears it be caused by a silent lack of temp space.

I had previously cleared my temp partition enough to clear vLite's red warning text, but it appears that vLite eneded up needing more space. When vLite's temp setting is pointed to a big, empty partiton, no more unhandled exception. (I like easy fixes, even if they are a couple hours of searching to find.)

Your tool looks great. Thank you, very much.

Mark

[nuhi]

Oh, do you maybe remember how much you had when it failed so that I can up the warning?

[pub3lic@gmail.com]

Hello,

Sorry, but I no longer think that this error is related to a lack of temp space (less than 1GB is the answer to your question).

I got vLite to work once, which I reported above, but it has failed in the same, or a similar, way ever since. The other error I'm seeing appears more helpful. Its a "Mounting image error." It asks if I've restated after installing the FilterManager. vLite reported finding the FilterManager upon first run, but not the wimfilter, which it then installed. ...

I've been reinstalling and running under different condiitions ever since, but haven't found the causal condition, only one of these two noted errors. Also, I've installed the WAIK, but I still see the same errors.

I'm impressed with vLite's functionality from the time that it worked for me. Please help.

Thanks,

Mark

[nuhi]

If you get Invalid URI then it was probably networked drive or something like that out of the local drive.

But that Filter Manager error is one of those rare bugs. I don't have any explanation for it so far. People say that it's solved by reinstalling the host machine but that cannot be the recommended solution.

Try to run it in VMWare from some freshly installed OS, that way you can configure your ISO and just get it out of there after it's done.

[pub3lic@gmail.com]

All but video-intensive apps I do run in an (optionally clean) vm, so it looks like I'm screwed with respect to vLite. (If a program fails for me, and then fails in the same way on the host os, I move back into the lovin' arms of a vm.)

As an aside, with the repeditive testing I've been doing on this issue, I finally broke down and made an 11GB virtual hard drive that contains vLite-converted source files for vista ultimate x86 & x64 and server 08 RC0 x86 & x64. The trick being to then set this disk as vmware's "non-persistent" mode. Destructive writes, such as vLite would do, to these os sources are transparently written to hidden-from-the-guest-os temp files. This drive is now usable by vLite, VistaPE, etc... inside vms and, when mounted read-only in the host, in the host. VistaPE runs without error with this drive as its source of os files. Again, vLite fails in the same ways with this drive and with vLite freshly converted sources, so I don't suspect this drive. And, of course, more generally, this "non-persistent" mode is a mature feature.

Thought the above bit to be of general interest, so I wanted to mention it, but personally, I continue to be blocked & searching for workarounds.

The clean vm os' that I use don't have any apps, but have my configured user profile. Per your sugestion, I'll next try a truly clean os.

Please let me know of any other possible workarounds that I may try.

Thanks for your time,

Mark

[pub3lic@gmail.com]

I've found a positive (working) case:

- a Server 03 vm with enough disk space on its C: drive to contain the os sources & the vLite temp directory.

Thanks,

Mark