Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.Login to AccountCreate an Account

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

nlite crashing when I try to add winvblock

jeff.sadowski

Posted 31 July 2012 - 09:04 AM

jeff.sadowski

Junior

Member

73 posts

Joined 01-March 07

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 SP1I 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 driverWhen 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.

allenhiltz

Posted 19 February 2013 - 11:57 PM

allenhiltz

Member

1 posts

Joined 19-February 13

OS:none specified

Country:

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.png56.14KB5 downloads

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 WinVBlockI 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.

jeff.sadowski

Posted 22 February 2013 - 05:04 PM

jeff.sadowski

Junior

Member

73 posts

Joined 01-March 07

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.png56.14KB5 downloads

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 WinVBlockI 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

Posted 25 February 2013 - 05:48 PM

jeff.sadowski

Junior

Member

73 posts

Joined 01-March 07

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.png56.14KB5 downloads

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 WinVBlockI 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. :-)

Howto get winvblockgoto http://reboot.proon the upper right it says registerregister for an account on reboot.proafter finishing registering make sure you can loginthen goto http://reboot.pro/8168/it then says to go to his recent postit it will have a link to download winvblockif your not logged into reboot.pro it will ask you to, to download the driver.

uncompress winvblockedit the txtsetup.oemremove 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 ISOWhen you get to the "Bootable ISO" screen select "Make ISO"

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/

jeff.sadowski

Posted 09 April 2013 - 03:56 PM

jeff.sadowski

Junior

Member

73 posts

Joined 01-March 07

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.

Ponch

Posted 10 April 2013 - 08:39 AM

jaclaz

Posted 10 April 2013 - 09:35 AM

jaclaz

The Finder

Developer

15,789 posts

Joined 23-July 04

OS:none specified

Country:

@jeffit 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).