[PaulDG]

Different Day - more questions :D

This new Grub4dos support for ubcd4win that you have kindly supplied, is it intended for the usb implimentations only? or is it also for the standard ubcd4win cd version? if so how do i activate/switch to it?

Where is the "multiboot plugin's main inf file" located?

Thanks for the clarification of the kicker cd and usb device matching.

WARNING... Shmorning, that never happens to me..... Oh wait!!! :D I was lucky this time, the share was RO and it was a cd drive. But no pain no gain!

ATB
Paul

[pcuser]

Quote

This new Grub4dos support for ubcd4win that you have kindly supplied, is it intended for the usb implimentations only? or is it also for the standard ubcd4win cd version?

It's only for the usb drive.

Quote

Where is the "multiboot plugin's main inf file" located?

The main inf file for memtest86 is memtest.inf, the main inf for dban is dban.inf, etc...

[PaulDG]

Ok Thanks for the clearup.

Can we get a switch to leave the kicker.img on disk after the iso has been compiled so i don't have to mount it and pull it everytime i make a new one. I can then write a tool that compliments this to create my custom cd and add all the other menu options into menu.lst

Below is what i am trying to achive. using tools and programs as ill forget what i was doing when i move on to something else :D

A cd that contains the standard ubcd4win installaton enviroment with any multiboot options i may add (aoss, kaspersky and memtest) that also can start the kicker and a usb stick/hd that complements this.

On a modern bios i would boot from the usb - after updating all the antivirus and malware utils.
On a old bios without usb support i would boot from the cd and use the kicker to load the ubcd4win enviroment from the same usb device as above
and on a real nasty bios i would fall back to the same cd and use the utils from the time i created the cd - maybe with an alternate usb device containing updates.

Paul

[pcuser]

Quote

Can we get a switch to leave the kicker.img on disk after the iso has been compiled

Sure. I'll get it added

[pcuser]

1.0.0.13 has been uploaded.

It now leaves kicker.img after creating the iso image. I've also made a plugin for adding your kicker image(s) to your UBCD4Win multiboot menu, you can download it from HERE (extract it to your plugin\multiboot-003 folder).

The plugin is disabled by default because you have to build UBCD4Win atleast once before running UBUSB and creating your kicker.img

Your kicker images go in the "kickers" folder and you'll need to edit kicker_grub4dos.ini if you want to include other images besides the default "kicker.img" (or if you change the name of it). Don't forget to enable the plugin before building UBCD4Win again to include your images!

Thanks for the reports and good suggestions Paul, please keep them coming :)

[PaulDG]

pcuser, on Oct 3 2008, 02:07 AM, said:

It now leaves kicker.img after creating the iso image. I've also made a plugin for adding your kicker image(s) to your UBCD4Win multiboot menu, you can download it from HERE (extract it to your plugin\multiboot-003 folder).

Now thats what i'm talking about.... Thanks for this, i'll check it out tomorrow, need sleep now.

Paul

[PaulDG]

okeydoky - 1 Question and 1 observation.

Why does the kicker plugin boot to grub4dos first and then loads the kicker image when you select it, instead of directly booting the kicker img via the std menu?

Also the menu.lst file presented to the above loaded grub4dos contains all the other multiboot options instead of just the kicker but they dont work.

Oh and its possible that the UBUSB.exe program has lost its "done/completed msg" though it was late when i tested last and i might have lost it in the 15 windows i had open.

Paul

This post has been edited by PaulDG: 03 October 2008 - 10:54 AM

[pcuser]

Quote

Why does the kicker plugin boot to grub4dos first and then loads the kicker image when you select it, instead of directly booting the kicker img via the std menu?

The kicker.img needs to be chainloaded via Grub4dos but the initial UBCD4Win bootmenu is BCDW so we call GRLDR from BCDW to load Grub4dos. Does that make sense?

Quote

Also the menu.lst file presented to the above loaded grub4dos contains all the other multiboot options instead of just the kicker but they dont work.

That's because of the added Grub4dos support in all of the other multiboot plugins and the fact that there can only be one menu.lst file. The only workaround that I know of is to use the original multiboot set or comment out the "*_grub4dos.ini" line in the affected multiboot plugins.

[PaulDG]

and visa versa, the menu.lst presented to grub4dos on the actual usb device contains the kicker option, but it does work!!!

[pcuser]

Quote

and visa versa, the menu.lst presented to grub4dos on the actual usb device contains the kicker option, but it does work!!!

That's an interesting side affect! I've noticed that some computers with native usb boot support can take a long time to boot but using the kicker cd makes the boot alot faster. This could be a nice feature?

[pcuser]

I'm going to do some tests on a Dell that normally gets the 0x7B BSOD unless I use the 2k3sp1 files and see if I can boot using the kicker from the usb drive.

[PaulDG]

pcuser, on Oct 3 2008, 05:24 PM, said:

I'm going to do some tests on a Dell that normally gets the 0x7B BSOD unless I use the 2k3sp1 files and see if I can boot using the kicker from the usb drive.

Maybe a usb 1 vs usb 2 thing, bios support is only usb1 and im guessing your kicker.img is using 2

[pcuser]

Drum roll... It worked!!! I booted the kicker image from the usb drive on that same Dell and it booted straight to the desktop (without the need for win2k3sp1 files) and rather quickly too!

[cdob]

pcuser, on Oct 3 2008, 01:39 PM, said:

I booted the kicker image from the usb drive on that same Dell and it booted straight to the desktop (without the need for win2k3sp1 files) and rather quickly too!

Thanks for confirmantion: No BSOD 0x7b with the Kicker image.

Ktp reported faster boot speed at USB1.1 BIOS too
http://www.911cd.net...&...st&p=149295

[pcuser]

First test: Dell Dimension 2400. Can natively boot from USB but fails with 0x7B BSOD

Booting UBCD4Win from USB: 7 minutes 35 seconds before 0x7B BSOD
Booting UBCD4Win from CD: 5 minutes 45 seconds before completely booted (rocket dock icons appeared)
Booting kicker image from CD: 8 minutes 50 seconds before completely booted
Booting kicker image from USB: 3 minutes 25 seconds before completely booted

I'll have to do more testing but based on these results it looks like booting the kicker image from usb might be the best way to go, even if the computer can natively boot from usb.