[PaulDG]

Thats good news, obviously booting on a very modern board with native usb2 support for usb booting should not produce the same results.

I have a brand new Asus P45 system downstairs waiting to be assembled, ill get some testing done on that in the next few days.

I am going to try and figure out a way to tidy up the other side affect first.

[pcuser]

Quote

Thats good news, obviously booting on a very modern board with native usb2 support for usb booting should not produce the same results.

I just booted a on a Gigabyte P35-DS3P / Core2Dou E6750 / 4GB 800Mhz Ram that normally takes about 12 to 13 minutes to boot UBCD4Win from USB and booting kicker.img from USB takes about 3.5 minutes. Same thing on a Compaq presario SR1303WM / Sempron 3000+ / 512MB Ram, it usually takes around 15 minutes to boot from USB but booted in about 3.5 minutes booting kicker.img from usb.

Another nice thing I noticed is that booting kicker.img from usb doesn't produce the message "An unexpected error (769) ocurred at line 5182 in D:\XPSPRTM\BASE\BOOT\SETUP\SETUP.C Press any key to continue." like it does when booting kicker.img from cd on a system that natively supports usb booting.

The tests I've done today are enough to convince me that booting kicker.img from usb should be included by default when Grub4dos is selected as the bootloader. I can have UBUSB copy kicker.img to the images folder on the usb drive (if it doesn't already exist) and put an entry in menu.lst

[pcuser]

1.0.0.14 has been uploaded.

A new boot option called "PE-Boot (Compatibility Mode)" is now created by default if Grub4dos is selected for the bootloader and %USB%\images\kicker.img doesn't already exist.

This method seems to boot much faster than standard usb booting and can boot on computers that normally stop at 0x7B BSOD

[rdsok]

pcuser, on Oct 3 2008, 09:42 PM, said:

1.0.0.14 has been uploaded.

A new boot option called "PE-Boot (Compatibility Mode)"

This works great on my system as well. Also using a Gigabyte MB ( GA-M55PLUS-S3G ) .

I tested the Grub4Dos method and the boot time difference is just great. If this also ends up addressing USB boot compatibility issues as well as the boot speed... I'll be switching to USB finally from the CD/DVD boot methods.

[datarunner]

hi there

ive followed your method and have some questions

there are 2 iso's produced "kicker" and "no usb" which one do i use, also

on clicking "test kicker" and pressing enter in qemo i get the following error "The file i2omp.sys cannot be found"

i used fat32 with grub4dos method

regards

[pcuser]

Quote

there are 2 iso's produced "kicker" and "no usb" which one do i use

Look again, only one of them is an ISO (NoUSB.iso)

Quote

on clicking "test kicker" and pressing enter in qemo i get the following error "The file i2omp.sys cannot be found"

Are you using the same faulty usb drive as you described in THIS thread?

Does your UBCD4Win cd boot using the same build that the usb drive was prepared with?
Does this error appear when booting the usb drive on a real computer?
Does this error appear when booting the kicker cd on a real computer?
What source files are you using?
Are BTS drivers enabled?
What OS are you building on?

[datarunner]

pcuser, on Oct 4 2008, 06:12 PM, said:

Quote

there are 2 iso's produced "kicker" and "no usb" which one do i use

Look again, only one of them is an ISO (NoUSB.iso)

Quote

on clicking "test kicker" and pressing enter in qemo i get the following error "The file i2omp.sys cannot be found"

Are you using the same faulty usb drive as you described in THIS thread?

Does your UBCD4Win cd boot using the same build that the usb drive was prepared with?
Does this error appear when booting the usb drive on a real computer?
Does this error appear when booting the kicker cd on a real computer?
What source files are you using?
Are BTS drivers enabled?
What OS are you building on?

hi there

boots ok on a "real" system. i built on xp sp2 with server 2003 sp1 cd so all seems well

btw wots the "kicker" cd .img for?

thanx again

regards

[pcuser]

Quote

btw wots the "kicker" cd .img for?

If you use Grub4dos as the bootloader it adds a menu option called "PE-Boot (Compatibility mode)". Previous posts in this thread explain it in more detail.

[dirkgently42]

"PE-Boot (Compatibility Mode)"

pcuser said:

1.0.0.14 has been uploaded.

A new boot option called "PE-Boot (Compatibility Mode)" is now created by default if Grub4dos is selected for the bootloader and %USB%\images\kicker.img doesn't already exist.

This method seems to boot much faster than standard usb booting and can boot on computers that normally stop at 0x7B BSOD

Normal boot selection results in ~ eight minute wait until 0x7b ( no win2k3sp1 added)

"PE-Boot (Compatibility Mode)" boots very fast and shows rocket dock icons within four minutes!
Wow! Thanks Tom!
----

Dell Dimension 4600 and Dell Dimension 2400
Media : Lexar Firefly 2GB

----------------
Past builds without this tool:
Roughly eight minutes for successful boot after manually adding win2k3sp1 files.

This post has been edited by dirkgently42: 05 October 2008 - 12:11 AM

[datarunner]

hi there

i still get the following error on different systems following error "The file i2omp.sys cannot be found"


using fat32 and grub4dos

regards

[pcuser]

@datarunner,

Quote

Does your UBCD4Win cd boot using the same build that the usb drive was prepared with?
Does this error appear when booting the usb drive on a real computer?
Does this error appear when booting the kicker cd on a real computer?
What source files are you using?
Are BTS drivers enabled?
What OS are you building on?

[datarunner]

pcuser, on Oct 6 2008, 04:39 PM, said:

@datarunner,

Quote

Does your UBCD4Win cd boot using the same build that the usb drive was prepared with?
Does this error appear when booting the usb drive on a real computer?
Does this error appear when booting the kicker cd on a real computer?
What source files are you using?
Are BTS drivers enabled?
What OS are you building on?

Hi there

sorry for the lack of info and being a noob, im just learning as i go along here

anyway on testing my ubcd4win iso on virtual pc and burning to cd i got a "ntldr is corrupt" error

strangely enough i can still build working bootable usb drives using both your and compros methods - i just cannot get them to boot on an ami bios

i used server enterprise sp1 cd as the source and built on a xp host system

gonna rebuild using an xp sp2 cd and let u know

just as a matter of interest - which source files are best to use - xp or server 03?

regards

[pcuser]

Thanks for the additional info.

Quote

gonna rebuild using an xp sp2 cd and let u know

Yes, please do report back with your results.

Quote

just as a matter of interest - which source files are best to use - xp or server 03?

I don't which is better but I use XP SP2 as do most others on the development team.

[atc_traffic856]

Please tell me where can I find the Plug in folder? I have the 3.20 ver??
thankyou

[pcuser]

Quote

Please tell me where can I find the Plug in folder?

It's the "plugin" folder that resides in the same directory that you installed UBCD4Win to.