[jeff.sadowski]

I installed nlite version 1.4.9.1.
Maybe I need to downgrade net 2.0
I have net 2.0 SP2 installed. I see that it recommends net 2.0 SP1
I haven't used nlite for such a long time maybe I am doing something wrong.

The first time when it asked for the "Windows Installation" a gave it my virtual drive of my xp pro sp2.
Next it asked to "Select where to save the CD installation files for modification." I picked c:\nlite (a newly created directory)
I clicked next on the Presets options.
Selected Drivers and Bootable ISO from the Task Selection then next.
On the Drivers window I select Insert->single driver
When I select Winvblk.inf it gives the following message:

Unhandled exception has occured in you application. If you click
Continue, the application will ignore this error and attempt to continue. If
you click Quit, the application will close immediately.

Length cannot be less than zero.
Parameter name: length.

Details

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

************** Exception Text **************
System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length
   at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
   at 
.#..ctor(String )
   at 
.
.(String )
   at 
.
.(String )
   at 
.
.01(Object , EventArgs )
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.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.ToolStripDropDown.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.ToolStripDropDown.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.5456 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
nLite
    Assembly Version: 1.4.9.1
    Win32 Version: 1.4.9.1
    CodeBase: file:///C:/Program%20Files/nLite/nLite.exe
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
nLite
    Assembly Version: 1.4.9.1
    Win32 Version: 1.4.9.1
    CodeBase: file:///C:/Program%20Files/nLite/nLite.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)
    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.5462 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
nlgw
    Assembly Version: 1.1.0.0
    Win32 Version: 1.4.9.1
    CodeBase: file:///C:/Program%20Files/nLite/nLite.exe
----------------------------------------
MCDBNET2
    Assembly Version: 1.32.0.0
    Win32 Version: 1.32.0.1302
    CodeBase: file:///C:/Program%20Files/nLite/MCDBNET2.DLL
----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.6195
    Win32 Version: 8.00.50727.6195
    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/msvcm80.dll
----------------------------------------
CabLib
    Assembly Version: 9.7.0.0
    Win32 Version: 9.7
    CodeBase: file:///C:/Program%20Files/nLite/CabLib.DLL
----------------------------------------
msvcm90
    Assembly Version: 9.0.30729.1
    Win32 Version: 9.00.30729.1
    CodeBase: file:///C:/Program%20Files/nLite/msvcm90.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.

I downloaded winvblock version WinVBlock_0.0.1.8.zip from http://reboot.pro/8168/ just yesterday

This post has been edited by jeff.sadowski: 31 July 2012 - 02:48 PM

[allenhiltz]

I wanted to slipstream WinVBlock into a USB installer of XP using nlite (so I wouldn't have to press F6 during setup)
But a problem occured when trying to slipstream this driver.
nlite would report "unhandled exception" and "length cannot be less than zero"
 nlite error.png (56.14K)
Number of downloads: 4

However, I found a solution for this!

The problem is caused by some empty space between lines 24 and 27 in the TXTSETUP.OEM within WinVBlock
I found if I deleted all the space after WinVBlock64 = "WinVBlock Bus (64-bit)" and before ; iaAHCI.inf then the error goes away.

So here's what to do:
Open up TXTSETUP.OEM, place you cursor at the end of line 24. Press delete 4 or 5 times to remove all the empty space. Press Enter twice to recreate some empty space. Save.

I hope this helps someone else as much as it helped me.

[jeff.sadowski]

allenhiltz, on 19 February 2013 - 11:57 PM, said:

I wanted to slipstream WinVBlock into a USB installer of XP using nlite (so I wouldn't have to press F6 during setup)
But a problem occured when trying to slipstream this driver.
nlite would report "unhandled exception" and "length cannot be less than zero"
nlite error.png

However, I found a solution for this!

The problem is caused by some empty space between lines 24 and 27 in the TXTSETUP.OEM within WinVBlock
I found if I deleted all the space after WinVBlock64 = "WinVBlock Bus (64-bit)" and before ; iaAHCI.inf then the error goes away.

So here's what to do:
Open up TXTSETUP.OEM, place you cursor at the end of line 24. Press delete 4 or 5 times to remove all the empty space. Press Enter twice to recreate some empty space. Save.

I hope this helps someone else as much as it helped me.

Thank you so much I will give this a try and let you know how it works.

[jeff.sadowski]

jeff.sadowski, on 22 February 2013 - 05:04 PM, said:

allenhiltz, on 19 February 2013 - 11:57 PM, said:

I wanted to slipstream WinVBlock into a USB installer of XP using nlite (so I wouldn't have to press F6 during setup)
But a problem occured when trying to slipstream this driver.
nlite would report "unhandled exception" and "length cannot be less than zero"
nlite error.png

However, I found a solution for this!

The problem is caused by some empty space between lines 24 and 27 in the TXTSETUP.OEM within WinVBlock
I found if I deleted all the space after WinVBlock64 = "WinVBlock Bus (64-bit)" and before ; iaAHCI.inf then the error goes away.

So here's what to do:
Open up TXTSETUP.OEM, place you cursor at the end of line 24. Press delete 4 or 5 times to remove all the empty space. Press Enter twice to recreate some empty space. Save.

I hope this helps someone else as much as it helped me.

Thank you so much I will give this a try and let you know how it works.

Worked like a champ!!! The new Winvblock had a different TXTSETUP.OEM I deleted the blank lines and it worked fine.
I now have a working USB XP installer. :-)

[jeff.sadowski]

Complete Steps to create a USB bootable XP intsaller

Note: this method requires enough Ram to run the setup and store a CD image in RAM.

Get a windows XP cd.
Download nlite http://www.nliteos.com/download.html

Howto get winvblock
goto http://reboot.pro
on the upper right it says register
register for an account on reboot.pro
after finishing registering make sure you can login
then goto http://reboot.pro/8168/
it then says to go to his recent post
it it will have a link to download winvblock
if your not logged into reboot.pro it will ask you to, to download the driver.

uncompress winvblock
edit the txtsetup.oem
remove all empty lines as per the rest of this thread.
resave after deleting the empty lines.

Run nlite install. It will ask for windows xp source use the XP cd that you have.
It will ask where you want to put it select where you want the files on your computer.
When you get to "Task Select" Select Drivers and bootable ISO
When you get to the "Bootable ISO" screen select "Make ISO"

Now you should have an ISO image that MEMDISK can use.

Download a zip file for syslinux from here https://www.kernel.o.../boot/syslinux/
5.01 worked on some systems however I had more luck with 4.06 on others

Unzip syslinux to a directory.
open a command prompt (as Admin on Windows Vista and above) and cd to that directory.

then under win32 or win64 depending on if you have a 64 bit windows or 32 bit.

Carefully use syslinux to make your USB drive bootable.
Notes: You have to have a fat32 partition on your USB drive for syslinux to work.
syslinux -i -m -a <drive letter of USB>:

This will create put info at the beginning of the partition needed for syslinux.

copy the iso for windows to the USB stick
copy the memdisk (no file extension) file to the USB stick
note: memdisk can be found in the memdisk directory from syslinux

create a file named syslinux.cfg
the contents of mine are as follows

default xp_install
timeout 100
label xp_install
  kernel memdisk
  initrd xp.iso
  APPEND iso

This post has been edited by jeff.sadowski: 09 April 2013 - 03:42 PM

[jaclaz]

jeff.sadowski, on 09 April 2013 - 10:34 AM, said:

Complete Steps to create a USB bootable XP

Well, no.
That is a USB bootable SETUP for XP.
I.e. it is what has been talked and is being about here:
http://www.msfn.org/...ndows-from-usb/
something that you can install XP FROM USB stick.

Only issue is that you'll have most probably issues with disk numbering/letters assigned if you don't re-map disks, something that Syxlinux/Memdisk cannot do AFAIK, and that's mainly the reason why grub4dos is generally used instead (besides allowing NTFS, support for it in Syslinux exists, but it was still experimental last time I checked).
http://reboot.pro/to...ux-please-test/

BTW, there is no real need to press F6, see:
http://www.msfn.org/...rom-a-iso-file/
http://www.msfn.org/...aded-iso-image/

jaclaz

[jeff.sadowski]

Correct it is an installer. Advantages of the method I discussed here are as follows: with my method you can use gpxelinux to do this from a network share with very few differences. If someone wants more instructions on this I'd be glad to give them. I originally used winvblock with bartpe to create a network bootable bartpe. I never could get the grub method working. Nor could I really figure grub out. I was going to mess with it. I think my iso I created might even work with that method without needing to try loading the floppy disk image. (Is that what you where saying?) I also corrected my other post I accidentally put -s as a syslinux option bad idea that took forever to load an image.

This post has been edited by jeff.sadowski: 09 April 2013 - 03:57 PM

[Ponch]

You can get winvblock from here also.

[jaclaz]

@jeff
it is not about grub.
It is about grub4dos.
Though grub4dos is derived from grub (legacy) it has a whole lot of added features.
If you use network booting you won't have issues with drive lettering, if you do it from USB, you will, as 99.99% of the motherboard will set the USB device as disk 0 (and thus first active partition on it will get C: drive letter).

@ponch
it is also in the mentioned links.
http://www.msfn.org/...rom-a-iso-file/
http://www.msfn.org/...post__p__956290

jaclaz

[jeff.sadowski]

Ponch, on 10 April 2013 - 08:39 AM, said:

You can get winvblock from here also.

This doesn't come with a version you can slipstream. You need txtsetup.oem, WinVBlk.INF and, wvblk32.sys to be able to slipstream it with nlite. To be able to network boot you need it slip streamed.

[jaclaz]

jeff.sadowski, on 10 April 2013 - 10:45 AM, said:

This doesn't come with a version you can slipstream. You need txtsetup.oem, WinVBlk.INF and, wvblk32.sys to be able to slipstream it with nlite. To be able to network boot you need it slip streamed.

Well, network install has never been a problem, though it was a bit troublesome to setup.

JFYI, there is a relatively newish "all in one" TFTP and RIS/BINL server, that makes network install "a breeze":
http://www.vercot.co...indowsPXE1.html

jaclaz