[idea] Fake Signature Method Creator

I have Windows XP on USB HDD (Full XP, using USBoot) and it works great even the BIOS has a functional USB boot support. This is not always the case, one nice workarround is PLoP Bootmanager, but it's also not compatible anywhere.

Another nice method is the so called 'Fake Signature Method'. It is similar to - Linux "distro" specific kicker disc: the computer will boot from some supported medium (such as floppy, internal harddisk, CD or DVD) but the operating system start phase will be hand over to the USB device. Unlike the "BIOS extender like method" (PLoP Bootmanager) this should work in any case on any hardware.

The original thread is here http://www.911cd.net...showtopic=21242

The creation of such a kicker disc is very voluminous and therefore error prone. If you end up with an error while trying the modified setup CD you have basically no clue if you followed the guide correctly or not or if it's a "real" error. It's always bad to bother people in forum if you just done something wrong while creating the modified CD.

As announced, I'm writing a script.

Which conditions do you expect?
Do you use a USB bootable solution, and like to add a kicker image?
Do you use a default XP, like to add USB bootable solution and a kicker image?

Do you like to add booting from firewire devices?
Do you like to add booting from PCMCIA devices (PCMCIA, PC Card, Express Card) ?
Any other booting devices?

Do you like to add some kind of univeral booting?
Boot at different hardware, different kernel, different hal, AMD CPU drivers, Intel CPU drivers, ACPI enabled/disabled?
Does existing boot solution provide univeral booting?
Do you expect univeral booting from kicker image?

Any other requirements?

Do you have some USB device boot.ini examples?

Which multi(?)disk(?)rdisk(?)partition(?) do you use?
Do you use /kernel=* and /hal=* at boot.init?

Which BIOS USB speed do you use?
Do you use BIOS Low-Speed (1.5 Mbit/s), BIOS Full-Speed (12 Mbit/s) or BIOS High-Speed (480 Mbit/s) ?

Do you boot from USB hardware without USBoot?
USBoot requires a activation, hence is not free.

Many and good questions, more people then me should try to answer them.

Which conditions do you expect?

The user should create an bootable version of Windows XP on USB HDD (or maybe also pendrive - I wouldn't use pendrives myself.) and TEST if it already works on a good BIOS and/or in a Virtualizer + BIOS Extender.

Maybe as fallback he could simply use it without USB involved but as raw disk in Qemu or so.

Do you use a USB bootable solution, and like to add a kicker image?

Sorry, dunno what is a USB bootable solution? You mean a working operating system (XP) on USB and I want to create a kicker image for this? Yes.

Do you use a default XP, like to add USB bootable solution and a kicker image?

If you think about a "XP to XP USB creator" (USBoot) I think it would burst the volume of this project, this should be IMHO it's own project as it's already big enough without kicker image. Or I am wrong.

This idea was "only" a "XP ready on USB and working on 'good' BIOS" to kicker image creator.

Do you like to add booting from firewire devices?

Personally I don't have any firewire devices and I don't know how much future is inside this technology. Not useful for me, but maybe useful for someone else.

Do you like to add booting from PCMCIA devices (PCMCIA, PC Card, Express Card) ?

PCI(e) / PCMCIA PC Card / Express Card - USB hub addon cards are useful if you have not enough USB slots, "buggy" USB slots (behind an internal HUB) or no USB slots (older notebooks). If the amount of effort to add it is reasonable and people want it (what it guess?) then it should be added?

Any other booting devices?

USB HUB support would be useful, but does this need support by the kicker or isn't this inside the USB drivers already?

eSATA booting is also nice if you have eSATA, even if eSATA is not widespread. But adding eSATA support is not hard for a user like adding USB support. You can install and boot eSATA just like you can with SATA and the installation of the driver is mostly easy.

I don't know if it would be useful inside the kicker image.

Do you like to add some kind of univeral booting?

Booting from pXE? W-LAN? Read/write Image over https?
Well, it would be great but I guess it would burst the project. Perhaps it's good to add first "only" USB and to see if it makes point to add other things later?

Boot at different hardware,

Yes.

different kernel,

"Windows only" and maybe also "XP only", see below.

different hal,

Yes

AMD CPU drivers, Intel CPU drivers

Dunno, I think this is up to the "XP to XP USB Creator" (USboot)?

ACPI enabled/disabled?

To be choosen in bootmenu, see below.

Does existing boot solution provide univeral booting?

For Linux some distros provide kicker images and theoretically you can boot from any media to any media.

Do you expect univeral booting from kicker image?

No. The Fake Signature Method Image Creator is also "only" a "distro" (Windows XP in this case) specific kicker disc.

Kicker discs for booting Linux is up to the distro or other project, same for other operating systems.

Vista and Windows 7 well... Theoretically great, I don't know how far Fake Signature Method is working for them and how much point it would make for the kicker image to share some code between all those Windows versions.

Any other requirements?

- The kicker image should be bootable from grub4dos (for multi boot menu) if possible / reasonable afford. I think it will depend on which point the kicker image switches into protected mode which is something I am not aware of.

- Fake Signature Method Image Creator is probable not a name to let as much as users profit from this software, the name is technical and to cryptic. This was something I did not think about before posting this idea.
What about BootFromCDtoUSB; UniversalBooting; Ultimate Kicker Disc (hehe, with a collection of PLoP, Fake Signature Method, Linux specific kicker discs, GRUB2); Ultimate (XP) Booting Disc; Bootable (XP) USB Loader; yes, the name is still questionable and suggestions welcome.

Do you have some USB device boot.ini examples?
Which multi(?)disk(?)rdisk(?)partition(?) do you use?
Do you use /kernel=* and /hal=* at boot.init?

This is my boot.ini autogenerated by USBoot.

[boot loader]

timeout=5

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows" /fastdetect /noexecute=optin

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows (observe bootmessages)" /sos /fastdetect /noexecute=optin

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows ACPI APIC MP HAL" /sos /hal=halmacpi.dll /kernel=ntkrnlmp.exe /fastdetect /noexecute=optin

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows ACPI APIC UP HAL" /sos /hal=halaacpi.dll /kernel=ntkrnl.exe /fastdetect /noexecute=optin

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows ACPI UP HAL" /sos /hal=halacpi.dll /kernel=ntkrnl.exe /fastdetect /noexecute=optin

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows EISA UP HAL" /sos /hal=haleisa.dll /kernel=ntkrnl.exe /fastdetect /noexecute=optin

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="USBoot activated Windows EISA UP HAL  !SOS!" /basevideo /bootlog /sos /hal=haleisa.dll /kernel=ntkrnl.exe /fastdetect /noexecute=optin

The default should be partition(1) but I installed into partition(2). This is very useful, on different hardware different options are working.

Which BIOS USB speed do you use?

Do you use BIOS Low-Speed (1.5 Mbit/s), BIOS Full-Speed (12 Mbit/s) or BIOS High-Speed (480 Mbit/s) ?

Depends on the hardware I am using to boot. Some BIOS have no USB support, others have USB support but no booting, other USB 1.1 and others USB 2.0.

The kicker image may be used in case of no USB support, only USB 1.1 or buggy BIOS. In this case it boots from CD or DVD, loads Windows USB drivers and starts the rest from USB. Even if the BIOS has no USB support or only USB 1.1 but the hardware is USB 2.0 the booting speed after the kicker image is afaik always USB 2.0.

Do you boot from USB hardware without USBoot?

XP made USB-bootable with USBoot? Currently not, but other users are using ngine Method or done the manual / Ditmar way.

USBoot requires a activation, hence is not free.

Yes, unfortunately only free in price.

Did you consider to write something like "XP to XP USB creator" (USBoot) and with an additionally kicker image creator as you wrote this? Well, to beat USBoot is hard since it's not only the published tweaks, it has a kernelmode and a usermode module and I guess them are programmed from scratch.

Like said, my idea was "only" the kicker image creator as this is complicated enough already, but for the deccsssion on what you planed is up to you.

Hopefully something will come up out of marv new service, see 911cd:
http://www.911cd.net...showtopic=22473



Which is free as in freedom, besides being free as in free beer.

jaclaz

First testing release, under construction:

Select SourceDir: your USB windows systemroot: e.g. U:\windows
And select play.

As for a first testing release there are some limitations:
fixed boot.ini, use first partition only
ntoskernl.exe and hal.dll from external media used. No user choice.

Config options (dummy, under construction) dosn't work so far.

Assumptions:
Running windows use default applications, e.g. cmd.exe, findstr.exe, xcopy.exe, makecab.exe, expand.exe, cscript.exe
Build will fail at havy nlited windows.

Script dosn't write to USB drive itself.
Contrary backup files at USB drive yourself.
Booting may fail and %systemroot%\system32\config\system may get corrupt.

There are two images created:
a ChainBoot.img. This is direct acessed by grub4dos.

And a compressed a ChainBoot.gz. This is RAM loaded by grub4dos: Memeory Mapped
Compressed image may work or get a BSOD 0x7b.
I get works at qemu, fails at real hardware. Maybe timing is involved.

There are two target choices:
ISO image: boot from CD.
disk: boot from the same USB or other USB

Use qemu for basic chainboot testing, boot fom ISO image.
And maps USB drive to Physicaldrive. Hence a internal hard disk.
USB windows has to support some universal imaging.

ImgBurn is included too. Burn ISO image to CD.

Not tested with USBoot. May fail.
Does USBoot set windows USB drivers to load early? E.g. usbstor.sys start=0


http://www.geocities...ChainbootXP.zip

solemnwarning (author of kexec-loader) wants to help to make the kicker disk on the fly (at boot time), so you can use kexec-loader to boot every Windows installation.
He only needs to know the exact files and things that need to be done.
http://www.boot-land....php?...&st=0

solemnwarning (author of kexec-loader) wants to help to make the kicker disk on the fly (at boot time)

Great, that's nice.

know the exact files and things that need to be done.

Integrated ImageCopyFilesXP.cmd does copy files.
There is a static list. And there is registry parsed: boot start=0 drivers are added.

Checksum has to match: RAM disk image MBR and real hardware MBR has to match. There is integrated copysgcs.exe and copycgs.txt conains source code.
copysgcs by karyonix http://www.911cd.net...&...st&p=145456

Partition type has to match real hardware: e.g. FAT to FAT

Nice to see the progress.

I wanted to test the first release but unfortunately it's offline.

I wanted to test the first release but unfortunately it's offline.

Files are online. Please try again previous given link.

And maybe one day http://www.boot-land...?...ost&p=54616

Files are online. Please try again previous given link.

Not working right now.

Lin k redirects to:
http://us.share.geoc...ChainbootXP.zip

This page is not available.
We're sorry, but this page is currently unavailable for viewing.
If this site belongs to you, please read this help page for more information and assistance.

jaclaz

Next version:
kernel, hal, firewire, pcmcia added
Files are extracted from \Driver Cache\i386\*.cab.
Windws default application expand.exe is used.
use expand.exe friendly *.cab files. XP default *.cab files are recomemnded.

It's fixed to partition(1) still.

Unfortunately http://cdob.boot-land.net/ is down still.

core files are attached:
Add Winbuilder.exe 075 beta5 or beta6 yourself.
And add Projects\Tools files.
Start another WinBuilder project to get files.

It's not recommended to use Peter's nightly build anything than testing.
http://exec-se.de/Wi...arebone_075.zip
Contrary this may work anyway. Add ChainbootXP project.

In addition you may add 'ImgBurn ISO' http://livexp.boot-land.net/


@mr_
Thanks for previous answers.
USB HUB is support by default. Any motherboard use a internal USB HUB.
eSATA: not supported as addition. Read: existing windows has to support eSATA already.
If existing windows contain drivers, drivers are added to kicker image.

Unfortunately http://cdob.boot-land.net/ is down still.

cdob, post about it here:
http://www.boot-land...?showtopic=6434

I would do it for you, but Nuno might not notice it if I am still the last poster....

jaclaz

Finally I found some time to test this great piece of software.

I did run into 3 minor problems, easy to fix.

---------------------------

D:\Programme\WinBuilder075-Beta6\Projects\Tools\7z.exe

---------------------------

"D:\Programme\WinBuilder075-Beta6\Projects\Tools\7z.exe" konnte nicht gefunden werden. Stellen Sie sicher, dass Sie den Namen korrekt eingegeben haben und wiederholen Sie den Vorgang. Klicken Sie auf "Start" und anschließend auf "Suchen", um eine Datei zu suchen.

---------------------------

OK   

---------------------------





Der Befehl ""D:\Programme\WinBuilder075-Beta6\Projects\Tools\mkisofs.exe"" ist entweder falsch geschrieben oder

konnte nicht gefunden werden.





---------------------------

mkisofs.exe - Komponente nicht gefunden

---------------------------

Die Anwendung konnte nicht gestartet werden, weil cygwin1.dll nicht gefunden wurde. Neuinstallation der Anwendung könnte das Problem beheben. 

---------------------------

OK   

---------------------------

Tested it in VMware, boot fine.

Further tests on bare metal will follow soon.

Finally I found some time to test this great piece of software.

I did run into 3 minor problems, easy to fix.

---------------------------

  D:\Programme\WinBuilder075-Beta6\Projects\Tools\7z.exe

  ---------------------------

  "D:\Programme\WinBuilder075-Beta6\Projects\Tools\7z.exe" konnte nicht gefunden werden. Stellen Sie sicher, dass Sie den Namen korrekt eingegeben haben und wiederholen Sie den Vorgang. Klicken Sie auf "Start" und anschließend auf "Suchen", um eine Datei zu suchen.

  ---------------------------

  OK   

  ---------------------------

  

  

  Der Befehl ""D:\Programme\WinBuilder075-Beta6\Projects\Tools\mkisofs.exe"" ist entweder falsch geschrieben oder

  konnte nicht gefunden werden.

  

  

  ---------------------------

  mkisofs.exe - Komponente nicht gefunden

  ---------------------------

  Die Anwendung konnte nicht gestartet werden, weil cygwin1.dll nicht gefunden wurde. Neuinstallation der Anwendung könnte das Problem beheben. 

  ---------------------------

  OK   

  ---------------------------

Tested it in VMware, boot fine.

Further tests on bare metal will follow soon.

Fine that you found your solution!

I really from the very beginning of this topic did not try to understand the background, because I have so many other tasks to do and the title itself did not interest me.

But please allow me a small interrupt:

I do not like if everything is running well and nobody knows why.

You mention three smaller issues which do not prohibit a successful start into the emulator.
And I understand your enthusiasm and your decision to 'hurry up'

But I suggest that you first eliminate the smaller issues (inspite they do not hinder the emulator start)

And continue only if the current project runs Warning- and Error- free, continue!
Maybe (you wrote 'easy to fix') it is only a question of some minutes, but fix it before continuing!

Just a well meant hint of a Dinosaur!

Peter

Ehrm, I am only a user who gives some feedback. The erros are obvious to fix, just copy the missing files into the mentioned directory. It would look stupid if I start explaining this into detail.

I have no clue about winbuilder developement and can not fix this bug on source level nor I know the licence or if this is wanted.

Ehrm, I am only a user who gives some feedback. The erros are obvious to fix, just copy the missing files into the mentioned directory. It would look stupid if I start explaining this into detail.

I have no clue about winbuilder developement and can not fix this bug on source level nor I know the licence or if this is wanted.

Two possibilities:

• You downloaded a project and got the errors:
  Then post the issue in the apps forum or wherever it is applicable, present the error messages and add the log!
• You did some modifications by yourself and got the errors:
  Two possibilities again:
• You want to have some help
  Then post the issue in the apps forum or wherever it is applicable, present the error messages and add the log!
• You do not want to have help:
  Then do not mention it here as 'besides'

Peter

No log needed as it's pretty clear and no long wanted from the developer yet. Why take extra work no one needs? This isn't an ultra complicated bug, it's pretty simple.

With all due respect, if you are not really interested in this software for any reason it's more logical not to try to force me to do anything. If you would have involved yourself into this you would see what you want in this case is pretty unnecessary.

I am not going to argue with you if you are not really interested here, if you want to contribute here please get involved, otherwise it's pointless.

I am not going to argue with you if you are not really interested here, if you want to contribute here please get involved, otherwise it's pointless.

Pointless to try to help you

Peter

Idea for partition(n):
Fake equal partitions at a fake equal MBR for a fake equal hard disk:

Fake image with four equal partition entries, non active

00 01 01 00 04 0F 3F 31 3F 00 00 00 A1 C4 00 00
00 01 01 00 04 0F 3F 31 3F 00 00 00 A1 C4 00 00
00 01 01 00 04 0F 3F 31 3F 00 00 00 A1 C4 00 00
00 01 01 00 04 0F 3F 31 3F 00 00 00 A1 C4 00 00

That way all boot.ini partition(n) maps to the same partition.

Fake image dosn't contain boot code at MBR or boot sector.

Grub4dos maps image and chainload ntldr from first partition:
chainloader (hd0,0)/ntldr

It's alive at qemu


First full release:
kicker image, kernel, hal, USB, firwire, pcmcia and partition(n) support
All build files included. Don't copy files (like 7z.exe) to project anymore.

http://cdob.boot-lan.../ChainbootXP.7z

Thanks to Nuno for hosting.


@mr_
Of course you may update mkisofs.exe and cygwin1.dll.
I apologize broken mingw32 port is included. It's commonly used at winbuilder projects.
As timestamps dosn't matter for chainboot, this version works fine.

I apologize broken mingw32 port is included. It's commonly used at winbuilder projects.

Hi cdob,

Are you able to link to or provide one that is acceptable, in your estimation?

Thanks,
Galapo.

First full release:
kicker image, kernel, hal, USB, firwire, pcmcia and partition(n) support
All build files included. Don't copy files (like 7z.exe) to project anymore.

Very nice work cdob!

I especially enjoyed this line:

//greetings to Jaclaz: no more boot used

I especially enjoyed this line:

//greetings to Jaclaz: no more boot used

WHO dared taking my name invain?

http://www.boot-land...?...=2958&st=16






jaclaz

New version:
support ntldr chainboot: Windows 2000, XP 64 added. NT4 should work too, not tested.
FAT32 reenabled
exFAT added - assumption: source file contain KB955704: exfat.sys is integrated.

previous link is valid still
http://cdob.boot-lan.../ChainbootXP.7z

Windows load required file system driver at boot only.
default registry setting: ntfs: start=4 disabled
Booting from ntfs media, ntldr load file system driver ntfs.sys. Booting is possible.
Booting from fat32 media, ntldr load file system driver fastfat.sys. Booting is possible.

Booting from fat media, chainboot fat/fat32 is possible.
Chainboot exFAT fails by default, no device driver loaded: BSOD 0xED UNMOUNTABLE_BOOT_VOLUME

Chainboot script set file system start=0 at appropiate media.
Target chainboot file system ntfs: ntfs.sys start=0
Target chainboot file system exFAT: exfat.sys start=0
Target chainboot file system FAT/FAT32: grub4dos loaded image is FAT,
fastfat.sys is be loaded anyway: no changes done

Build process works out of the box without downloading, very nice.

I see no reason to have this add firewire and pcmcia boot driver as a seperate option? The more drivers the better? As long it can't break things I would simply add it anyway, maybe you need it later. But this is just minnor.

What does 'add windows default kernel and hal' mean?

Did I got it right? (how to use your application)
- I just need to create a bootable USB drive and test if it works at some good BIOS.
- Then I create the iso and burn it.
- Boot the iso at some good/bad BIOS and test it.

I've made a test in VMware (with an USB harddisk working on bare metal/good BIOS and also on VMware/PLoP Bootmanager 5.0), it boots very fast but I got BSOD STOP: 0x0000008E.

Well I like small solutions. And prefer to add firewire and pcmcia boot if required only.
There is no sense to load firewire drivers for a USB stick.
Maybe nice to have for USB / firewire combo hard disk. I prefer a user choice.

What does 'add windows default kernel and hal' mean?

http://support.microsoft.com/kb/309283 describes HAL options for Windows XP and Windows Server 2003.
Chainboot script add this HAL and relating kernel.
Options are selectable at boot.ini.

Did I got it right? (how to use your application)
- I just need to create a bootable USB drive and test if it works at some good BIOS.
- Then I create the iso and burn it.
- Boot the iso at some good/bad BIOS and test it.

Script use existing USB solution. Yes, create bootable USB drive first.
As for testing: don't try several different hadware. This may include inproper drivers.
Booting different hardware require some universal imaging features.
This is not part of the script.

it boots very fast but I got BSOD STOP: 0x0000008E.

When do you get BSOD 0x8E? Does windows boot? Do you get a desktop?
A non proper driver is loaded, hence the BSOD.
Reminds to acpiec.sys. As far as I remember Dietmar reported similar several years ago.
Sorry I don't know the true reason.