nlite may throw an exception

[icnocop]

Hi.

nlite v1.4.8 sometimes throws one of these exceptions:

Unhandled Exception: System.IO.FileNotFoundException: Could not find file 'UNATTEND.TXT'

Unhandled Exception: System.IO.FileNotFoundException: Could not find file 'SWTCHBRD.BM_'

This happens when I try to run nlite on a windows 2003 sp2 or windows xp x64 sp2 source files where the service pack was slip streamed through command line (outside of nlite)

In this scenario, nlite is run in unattended mode.

Any ideas?

Thank you.

[Guest]

I have never received this error and I used the command line to slipstream SP2 into XP x64 as well. Both of those files exist in my source. My source is clean and unaltered except for slipstreaming SP2.

I have not used nLite in unattended mode, however.

[icnocop]

I have tried nlite v1.4.9.1 and it seems to throw this exception even more times than before.

I would like to request that nlite catch "System.IO.FileNotFoundException" Exceptions and at least log the error.

Both of those files do not exist in my source and they should not be required to exist.

Thank you.

Here are some more details on the exception that sometimes gets reported:

Unhandled Exception: System.IO.FileNotFoundException: Could not find file 'SWTCHBRD.BM_'.

File name: 'SWTCHBRD.BM_'

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileInfo.get_Length()

at ..(DirectoryInfo )

at ..(DirectoryInfo )

at ..

()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

Edited September 16, 2008 by icnocop

[newsposter]

nlite is reliable ONLY with a 'pure' unmodified source of XP.

[icnocop]

In the case of Windows 2003 R2 Enterprise Edition, UNATTEND.TXT and SWTCHBRD.BM_ exist in \i386 but I am still getting an exception.

I even tried to remove swtchbrd.bmp from the [RemoveFiles] section of the presets file.

This Windows 2003 R2 Enterprise Edition source is unmodified.

[icnocop]

Here is a different exception that sometimes occurs when using nlite v1.4.9.1 with Windows Server 2003 R2 Enteprise Edition because of what appears to be a missing "sysoc.inf", but SYSOC.IN_ exists in .\I386 (and a SYSOC.INF exists in .\CMPNENTS\R2\PACKAGES\COREBINS\I386 but that is probably not applicable)

Unhandled Exception: System.IO.FileNotFoundException: Could not find file 'sysoc.inf'.

File name: 'sysoc.inf'

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileInfo.get_Length()

at ..(DirectoryInfo )

at ..(DirectoryInfo )

at ..

()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

[johnhc]

icnocop,

I notice your OS (on the left of your posts) says XP x64. Are you nLiteing a 32 or 64 bit version of Win 2003? Are you able to try nLite under the same OS as you are building? I would also suggest you start with a fresh copy of your CD and use nLite to integrate only SP2 and see if that works. I certainly don't know what effect a command line slipstreamed source has on nLite.

Enjoy, John.

[icnocop]

Hi John.

I am actually using nlite on both Windows XP x32 and x64.

On Windows XP SP2 x64, using nlite with a Windows Server 2003 SP2 R2 Enterprise Edition source does not seem to throw any exceptions with v1.4.9.1.

But on Windows XP SP3 x32, using nlite with a Windows Server 2003 SP2 R2 Enterprise Edition source seems to throw these exceptions more often than not (about 4 times out of 5).

I was hoping not having to use nlite on the same os as the one i'm trying to nlite. (The final cd works fine when an exception is not thrown)

I successfully created an nlited XP x32 and x64, and I'm currently working on an nlited Windows 2003 x32, all on Windows XP x64.

(There are some nlite independent issues with the unattended Windows 2003 x32 I am working on, but the unattended os installation works just fine)

I am sure slipstreaming SP2 on a Windows 2003 source will work fine with nlite, but I am trying to avoid having to keep two copies of the os on my HD (the original, and the one with SP2 slipstreamed) and so I am always starting with SP0 and slipstreaming SP2 using the command line. (It doesn't take too long, and sometimes I need to create a nlited SP0)

I am just having a hard time figuring out why these exceptions are being thrown when the files it reports are missing actually exist and why exceptions are not being caught in the source code.

Thank you.

Edited September 18, 2008 by icnocop

[johnhc]

icnocop,

I am getting a headache just trying to sort the combinations of 32/64/XP/2003! Here is what I think:

• You need to use a 64 bit OS to create a 64 bit OS ISO
  
• You may get away with creating a 32 bit ISO on a 64 bit OS if you select XP Compatibility Mode for nLite.exe
  
• You should be able to create Win 2003 ISOs on XP and vice versa, if the first two above are met
  
• From what I have seen on these forums, when something fundamental is wrong, many really strange errors are thrown
  
• You must start with a fresh (not nLited before) source.
  

Please notice that this is what I think, based on my experience and what I have seen in these forums.

I suggest you get a virtual system for your testing. If you will be running 64 bit OSs, I recommend VMware Server. It is free but huge. Get this Processor Check tool to make sure your CPU is 64 VM capable.

Enjoy, John.