XP booting direct from USB Options

[abcslayer]

Hi everybody.
I have successed with hints from Dietmar, martin and sisal. In my case, windows XP pro SP2 was install with enormous software and services installed on many different location. I have to modified the registry, change ntdetect.com to get success.
For the error that dlag has encounted, that message means that the installer can not find the correct txtoem.
Now Im working on a Win2k backup from a very old computer (the hardware nolonger alive) and Recovery Console on USB (it seem to be a harder task).
Nice to meet you here.
And a notice for you: If any one has install the EZ_Recovery.exe it is a reason for 0x007b if you boot from USB. Just uninstall it, the install contain a usb driver filter.
For jaclaz: a present for you, hope you find it useful! http://www.freewebtown.com/abcslayer/USBoot.rar

[Dietmar]

Hi abcslayer,

congratulations to you.

Can you please describe, what you mean with "In my case, windows XP pro SP2 was install with enormous software and services installed on many different location. "

Have you tried to put your generic XP SP2 from one computer back to another one, after new hardware has been found there?
This works for me only for XP SP1.

My generic XP SP1 is ready. It works on notebooks, barebones, normal computers, simply everywhere.
But I have no idea to bring this to you without violating the EULA from Microsoft.
The idea is simple: Use VMware, install XP SP1 there with VMware tools, and make a real XP from this.
After that, you only have to put USB 2.0 support to it (Tutorial3 )and otto.reg with the special Vid and Pid from your USB device. This works also on all normal harddisks. Thanks to VMware .
DirectX and the missed software can be installed after. This is no problem. .

Good luck
Dietmar

[dennis123123]

My generic XP SP1 is ready. It works on notebooks, barebones, normal computers, simply everywhere.
But I have no idea to bring this to you without violating the EULA from Microsoft.
The idea is simple: Use VMware, install XP SP1 there with VMware tools, and make a real XP from this.
After that, you only have to put USB 2.0 support to it (Tutorial3 )and otto.reg with the special Vid and Pid from your USB device. This works also on all normal harddisks. Thanks to VMware .
DirectX and the missed software can be installed after. This is no problem. .

Which part violates the EULA?

[Dietmar]

Hi dennis123123,

I can give you Tutorial 6, how to set up a generic XP SP1 or SP2, that runs on any computer,
doesnt matter whether it starts from USB or normal. But this Tutorial 6 will be as twice as long
as Tutorial 5. Until now, I heard only from one person, that he succeeds with the Tutorial 5.
There are some errors in the Tutorial 5 on www.WINUSB.de, but they can be solved comparing
it with the Tutorial 5 here in this forum, that has no errors as far that I know.

Tutorial 5 works on about 80% of all compis.

I think, that I reach now 100 %, but not with an installations CD but 1,1GB XP SP1, SP2 image (simple all the files and folders of XP) that you can simply copy and past to your device (USB or normal).
This "installation" of XP lasts only a few minutes!
Together with my pupils we have a lan party at our school. There I tested my XP SP2 image...waaaoh.
It works.

But this is only legal, if you have the original XP Microsoft installations CD, from which this image is build.
Now I get questions from people to give them this image . The only solution from which I think it is legal is, that they send me their original XP CD. The image is then build from this CD.
But each image, that is build in that way, needs my time, because I have to use their CD.
What do you think about?

Nice to hear from you
Dietmar

[paraglider]

The eula is quite clear:

1.1 Installation and use. You may install, use, access,
display and run one copy of the Software on a single
computer, such as a workstation, terminal or other
device ("Workstation Computer"). The Software may not
be used by more than two (2) processors at any one
time on any single Workstation Computer.

...


1.5 Storage/Network Use. You may also store or install a
copy of the Software on a storage device, such as a
network server, used only to install or run the
Software on your other Workstation Computers over an
internal network; however, you must acquire and
dedicate an additional license for each separate
Workstation Computer on or from which the Software is
installed, used, accessed, displayed or run. Except
as otherwise permitted by the NetMeeting and Remote
Assistance features described above, a license for
the Software may not be shared or used concurrently
on different Workstation Computers.

[dennis123123]

But each image, that is build in that way, needs my time, because I have to use their CD.
What do you think about?

Nice to hear from you
Dietmar

Because all XP cds are identical, how about you leave out lots of critical system files - eg shell32.dll etc, and create a batch file to copy these from our own legal windows cd's, then you could distribute an image which would only work if the user had a legal xp.

[Dietmar]

Hi all,

Paraglider is right. If you have 4 compis, that run at the same time, you need 4 XP CDs.
Only if one compi of them is running at a time, a generic XP is allowed to be used.

I have a question to those, who tried Tutorial 5.
Have you ever tried on a new compi, when you got there BSOD 0x7b, to hit F8 and then the "last good configuration" option? XP simply works after that with the registry ControlSet002 in SYSTEM.


This is nearly the same, whether you use EWF also on your (system) harddisk, not USB stick only!!! . EWF on the system partition is not only good against viruses and trojans.



Nice to hear from you
Dietmar

[bshoangl1]

Hi Dietmar ,
You seem so optimistic with 80% success in any computer ( XP in USB-HDD ).
I tested it with 4 different computers : all have BSOD in booting to XP .
Hit F8 is also a total booting failure with another computer
One sole success is mine ( no BSOD )
I still wait for your 6th tutorial to have the best result for installing XP in any USB-HDD to any computers
Dr Hoang

[Finkster]

@Finkster

I have send you the ndetect.com

Thanks Ilux. Unforunatley hotmail blocks attached files with exe, com etc xtensions. Could you place ntdetect.com in zip archive and resend please. Thankyou.
Also I am somewhat confused my tutorial 5. It says copy files from c:\drive\usb folder to your xp build I386 folder and overwite. If however inf files are unpacked then what is there to overwrite. Do I delete the original in_ files? And where the heck is ultra.cat ultra.sys and ultra.inf? They are not in iata55_cd.exe whcih I i ran using /A switch to get contents. Is this ultra.sys the same as the promise technology one for WLAN driver. PCI VEN number is same. Maybe so.

thankx again Ilux

[Dietmar]

Hi Dr Hoang,

do you mean, that those computers show BSOD 0x7b at the first time when booting after installation from the modified XP CD?

Then, something went wrong with your XP installations CD. The only BSOD I saw is because the silly XP
changes its registry values, when you put your working USB harddisk to another computer. That behavior can
be overcome if you use EWF .

Today I will have a closer look, what entries in registry causes this BSOD. It is very astonishing to me,
because BSOD 0x7b is seen, when a bootdriver is not present at the right time. Because we do USB boot,
this must belong to the USB drivers. And this should be easy to solve .

Good luck
Dietmar

PS: IN XPSP2 you cant disable detection of new hardware with renaming of newdev.dll. Only you see not,
that XP installs something new, but it installs. This give you that Bsod. I think, that I can solve this today.

[Dietmar]

Hi all,

I solved my BSOD 0x7E, and I am writing this from my generic XP SP2 .

It is the driver intelppm.sys in WINDOWS\system32\drivers.
Rename it to iintelppm.sys and this BSOD is gone..Yippihhh.
Now I am knowing not a single compi, that does not work with the generic XP SP2.

Good luck,

write whether you succeed
Dietmar

PS: This error appeared by changing between AMD and Intel compis with one and the same USB device
and only with XPSP2.

And have a look, whether your USB drivers are those from XPSP1.
The silly systemrestauration changes them sometimes against those USB*.sys drivers from XP SP2.
Unpack therefore your Driver Cache, change those files and pack them again.

[abcslayer]

Hi, Dietmar.
I just have chance to test only on my computer at the moment. I prefer a "perfect" solution work and a I think a much more complicate (but fool proof) is not the problem at the moment when we could not understand all the crazy things that M$ burried inside the PnP detect of Win 2k/XP platform. At least now I think I fully understand that Mounted Devices does not related much to 0x007b, my focus is ntdetect.com, Critical Devices and services. Maybe next week when I got bigger flash disk I continued to work on Recovery Console, that is the most "bare" win32 system without full PnP services.
And luckily for me, I just got the install CD of XPe from my friend, the trial key work fine, my build is about 100MB but it too large for my 64MB flash at the moment.
Until now I dont know exactly why my HDD appear as fixed-drive but the pagefile always be directed to other location (that not the config faulty - I have checked, I think it related to the order virtual memory services start - I will check this night). The hibernation feature can not work too.
Does your generic solution work with correct HAL for each system or just a generic HAL for all? (maybe acpi HAL>!).
I hope at next week my study on this project will come to next stage...
A cheer for all of you.

[Dietmar]

Hi abcslayer,

I only see one yellow questionmark because of the killed intelppm.sys (Intel Processor...blablabla) in devicemanager.

I teached my XP SP2:

I started connecting my USB harddisk (one and only) to an AMD D1607 (Siemens) compi, then Notebook Intel M, then Shuttle Barebone SB61G2V3, then Intel P4C800-E Deluxe (Asus) . All the hardware is recogniced step by step. Also the amnesia is gone.

If you do not repack your Driver Cache with new USB drivers and kill intelppm.sys there, you have to do
this by hand after each compi. This is easy: Connect simply this USB harddisk to a running XP.

When I went back to my first compi, all the drivers, that I installed first are still there . I have total different
hardware: SCSI, mixt with SATA, different SOUND and network and all works now...puhhh.
Boottime is about 40 seconds, the size of this XPSP2 image is 1,3 GB only .

Believe me , its true.


Nice to hear from you
Dietmar

[ztronics]

hi folks and special thanks to Dietmar,

greetings and sorry to post so many words but for now here are my initial ideas and theories.

I do not like a vmware solution to create a generic image.

I think a virtual disk in the HAL will give major compatibility problems, with more problems appearing among different legacy, current, and future IDE controllers.
I think unpredictable problems may occur also because the XP image created by vmware has only been subjected to one type and generation of *mainboard* BIOS.
This should provide good consistency for the vmware engineering customer, but probably limits the addressability of larger HDD's or partitions on the mainboard bus if a target PC you plug your generic booting USB HDD into does not have great similarity to the one presented to the XP install by the vmware virtual machine.

I think its worthwhile to think of XP as already virtual enough like it is, if not too much.
Seems to me that XP simply has a suitably patched W95b inside configured with *standard* devices as kind of a *kernel*, with limited INFs and corresponding legacy device drivers accessible from within, then protected and enhanced by a HAL which accomodates all user devices in a virtual way, including those that once were well-handled by the *kernel* itself with its rudimentary PnP capability.
But this could mean that to enable or disable some of the core PnP functions, the HAL may sometimes present a new device in such a way as to trigger a reconfiguration of the *kernel* itself, especially those devices like Drive Volumes or other hardware which were handled so beautifully under non-virtual control by legacy windows versions.
Or OTOH maybe all *kernel* reconfiguration is forbidden, with all 26 alphabetical volumes always visible to it, but filtered by the HAL.

Actually Drive Volumes were handled so well by DOS they are a special case. Upon reboot, DOS is designed to be able to simply & automatically handle if you add or remove, hide or unhide, up to 24 visible formatted volumes at a time, naturally it assigns them the letters from C: to Z: in a strict and predictable hierarchy based on what the bios tells it. But the hierarcy is so confusing and the letters intentionally change automatically to completely accomodate random drive relocation, so its never been wise to depend on an alphabetical letter of a storage or swap drive being constant in relation to a booted system drive. So you really have always needed to label every partiton to make sure you absolutely know which HDD it is on and what its posititon on that HDD is. This was not changed substantially for DOS-based windows, all you need to do is have the Volume be recognizable by DOS based on what data the BIOS settings tell DOS are recorded at the key clusters, and a FAT32 formatted volume is seen and assigned a letter before windows even loads on top of that. These alphabetical drive letters assigned by dos are retained unchanged by default in dos-windows (but have always been reassignable in DOS itself), and XP appears to follow the trend when it is first presented with each new volume upon a reboot, so far I am almost sure I have seen adherence to the original assignment hierarchy when for example 3 previously formatted HDD's are added to the unused IDE plugs, and XP is rebooted.
But after that point XP has memorized what letter it has assigned to each (unhidden) volume based on some data stored on that volume (perhaps considering the drive label), and even after that volume is removed from the system for quite some time, if it sees that same volume again *after* a future reboot, it will attempt to assign the same old previous drive letter that it had the first time. If that same letter is not available then it reverts to a more confusing hierarchy, details of which may be undocumented as far as I know.
I am certainly no expert, just an experimenter.

The arcane boot lettering hierarchy for old DOS volumes as they appear or disappear from primary & secondary, master & slave positions on the bus, as well as multiple partitions per HDD some of which may or may not be recognizable by DOS or intentionally hidden from DOS at the time, are well detailed at www.pcguide.com

One thing is for sure, PC hardware is intended for you to choose any primary partition which begins within about the first 8.2GB of any HDD and boot to it, and it will always be assigned C: by default. All the other letters are up for grabs each time. Of course you can only boot to one partition at a time so if you want to change which one you need to do that at restart, it has to be an *active* partition and you can only have one partition be marked active on each HDD at any one time too.
With a fairly large HDD I like to make three bootable primary partitions at the front of each HDD. The first two are 4GB each, this takes all the space up to the 8GB milestone. Then the third partition starts at the 8GB point and will also be bootable when marked active whether it is 4GB or 30GB. Then the rest of the HDD is created as a primary extended partition, with logical volumes inside this extended partition where FAT32's occur below the absolute 137GB point only, and NTFS's beyond that.
Simply because the original IBM PC was designed to handle a maximum of 4 primary partitions per HDD with random booting access to any one of them which does not begin beyond the range of BIOS addressability. Using incredibly simple partition table editing, a boot loader has never been necessary to choose which volume on which HDD you want to boot to during a computer restart sequence. And naturally the intention of a PC is to have a different OS on each bootable partition for the most powerful capablities.

And when you are booted to a particular OS on a particular volume, the other bootable volumes (if recognized by that OS to begin with and not marked hidden or something) are inactive and appear no different than regular non-bootable storage volumes, so you can copy & paste them intact at will. This is the only fundamental intelligent backup method which has existed since day one and has not been surpassed, the purpose of an OS on a PC is primarily to make identical copies of data, and secondarily to process data.
And an OS is intended to be placed intact and bootable onto a blank volume properly formatted for that OS to begin with. The process of *installing* an OS is unfortunately the answer that became too often accepted when exponential increases in technology outpaced the ability of the engineers to build robust enough software for simple copying into place from an archive.
But one thing leads to another and the seemingly small headache of installing rather than cloning gave rise to the massive nightmare known as the registry.
The registry is not your friend, unless it can be tamed it will keep you from getting maximum productivity from your machine.

I highly recommend Partition Magic 7 for creating, formatting, and especially erasing, labeling, hiding, and unhiding partitions.
But for backing up and restoring you need to copy & paste or drag & drop, nothing else comes close.

W95b was the latest version where it was easily installed from the user menus selecting all standard devices and searching for no PnP hardware during install whatsoever, then after the first reboot you got a bootable volume on a HDD and as long as you canceled each time windows tried to install a new nonstandard (nongeneric) recognized PnP device, you would be able to power down the machine and put this *virgin* HDD into a very different machine and it would work fine, simply asking you for the devices that were on the new machine without any conflict from ones that were present on the install machine.

You could then take a couple of these *install* HDD's with the same virgin image in a bootable partition on each one, and put them both in a new machine at the same time, and when you boot, only the one assigned as C: at the time will have the new devices installed. So then after the first drive has all its devices set up, it is just a regular system volume for that specific machine.
Then using that system volume you could copy & paste the virgin system from where it is presently on a storage volume to a blank bootable partition on a third HDD for backup or to prepare a spare-parts type bootable generic HDD. Well, you may need a number of different sized HDD's but at least you could have the same generic image on each one, so whichever one you used it would always boot the same on any machine. Just like we expect our USB Drive to do now in XP. This is about the closest to ideal as you can get when a HDD or its OS fails or is not 100 percent reliable, when you need to instantly replace a system HDD it has never been an option to start with a blank HDD right out-of-the-box, you need something that will boot the first time and get the job done so you can go back and fix or replace the damaged HDD and/or system later when the emergency is over.

An OS which doesn't perform up to at least this standard is defective or crippled, or both since this is what a PC is designed for to begin with.

W95b is also the earliest version to well handle virtual devices to begin with.
Naturally it has no support for USB whatsoever natively though, the seldom-encountered USB extensions for W95b did work fairly well (still do) but will never give USB 2.0 performance. USB apparently was handled by W95b analogous to other virtual devices using VXD's, but by W98 VXD's were surpassed by WDM which seems to still be prevalent. Maybe a key element of HAL is a WDM-to-VXD interface.
I do not think any of the old USB extensions are included in a possible W95b XP kernel, HAL does it all so no problem moving up to USB 2.0 in XP once they had the snap to get the drivers decently mature.
Plus remember the way XP would only handle up to 32GB FAT32 volumes natively before there was Service Pack 1? That's the limit that W95b topped out at.

if there is interest in W95 it is quite easy for it to use today's large HDD's, you just have to partition & format them universally as I have mentioned earlier using FAT32 volumes smaller than 32G each and all occuring below the 137G cutoff point beyond which you will need NTFS just like everyone else.
The same way you needed to set up any FAT32 volumes in XP before service pack 1, basically that means to be most compatible with all windows versions you needed to avoid setting up any 32GB+ or 64GB+ FAT32 volumes which became possible in patched W98 & Wme.

In 2003 when I got a Toshiba laptop with USB 2.0, I first booted to USB using W95b without any USB extensions by installing it onto a 256MB USB stick. IIRC completely generic since the laptop devices were too new to be recognized by W95b. Too bad the stick itself was only USB 1.1, plus had an internal SCSI interface, it was slow but it worked well.
Now with a USB HDD I can get USB 2.0 performance, it rocks.
This Toshiba is great, the BIOS handles USB 2.0 natively, assigns a drive letter to non-crippled USB storage devices just like for DOS use, so when you boot to the internal HDD in DOS you already get to see the FAT32 volumes on the USB devices, and transfer data over USB without DOS drivers or anything. The bios delivers the external USB volumes to DOS transparently as it should. So you can format them and install dos or windows like you are supposed to. Then select a USB device from bios to boot to.
Now I am able to get access to the internal HDD and the other volumes residing on the same USB HDD as the system volume, at USB 2.0 speeds, from W98SE when it is installed on the USB HDD without it having any USB 2.0 drivers at all, just the native W98 USB 1.1 defaults.


ztron

"I'm afraid I can't do that, Dave" - HAL9000, 2001

[Dietmar]

Hi ztronics,

I think, you do not understand everything, that I am doing with VMware .
There is nothing virtual anymore. Of course, you have to look at your real Vmware image, what
is missed. Because of Windows Embedded (oh my, one year painfull learning), I know how to put part after part to an existing XP.
For example: You have to add USB 2 support by hand, DirectX, grafikdriver and other more difficult things like "Plug and Play Software Enumerator". For that you have to extract and install swenum.sys
streamci.dll and machine.inf wherein you delete "ExcludeFromSelect=*" and install this "by hand" with the
hardware detection. My first attempts with Vmware ended with catastrophal results. Also some simple things: You do not know the administrator name under Vmware but that can be overcome with typing
"net user administrator didi" in commandline.
But I am getting better hihi . I would say, that now I have the best and generic XP SP2 image (files and folders)
with a size of 1,3 GB, that can be copied and past to any USB device or any harddisk and runs with no modification at once on any computer. I am very interested if someone here can say the same. Today I compare a XP SP2 that has been installed to a normal harddisk with my "Vmware"
result. This is quiet easy, if you use the same compi with the same hardware for the first time.
Some interesting things will appear, how Vmware works. And there is nothing illegal: The images, build with Vmware, life forever even with the Vmware evaluations version .

Nice to hear from you
Dietmar

[Dietmar]

Windows XP boots from USB

Author: Dietmar Stölting, 6. Juni 2006
dietmar.stoelting@t-online.de
Germany


Tutorial (Version 6)


Hi all,

at 13:00 I am starting with normal XP SP2 install on a brandnew 250 GB WD IDE harddisk, formatted with FAT32 and 8.0 GB partitions size on my AMD compi Siemens with D1607 motherboard.
This is the same hardware as for my VMware image.
I use an original XP SP2 installations CD.

Lets see , how long I now need to build a generic XP SP2 from this install for USB or normal use.
I will edit this post, what I am doing.

Dietmar

EDIT1: In the meantime I format a WD160BB USB harddisk with Fat32 and 7.5 GB partitionssize by
Partition Magic 8.0 and set it aktiv. After that, I formatted it once more bút now from a working XP.
This is because I noticed differences in the bootsector. The XP formatting gives the best results for USB booting from a harddisk.
This is the best USB harddisk, that I know. It has an USB to IDE controller, that is recogniced through
booting by any compi. Because I have about 20 different USB harddisks, I know what I am writing.
Now I copy the modified ntdetect.com, the XP SP2 ntldr and boot.ini with an extra line to the USB harddisk.
Ok, all my compis show now the two lines from the boot.ini, meaning that the preparation of the USB
device is perfect.

Ok, the XP SP2 install (as normal) on the IDE harddisk is ready. I disable the pagefile.
This XP needs 1.3 GB space.
I dont install anything there (no extra drivers no extra programs)!!!

I connect my WD 160BB USB harddisk to this fresh XP SP2 simply for recognicing.


I copy and past all the files and folder of this new XP SP2 to a folder AMD64XPSP2Rhein from an other outstanding XP. (I use an USB XP hihi)
System Volume Information and Recycled copy not.

I disconnect my brandnew IDE harddisk with the new XP SP2 on it. I do not need it any more. It is only
therefor, if something went wrong with the XP SP2 image in AMD64XPSP2Rhein.

I connect my normal XP working harddisk to do all the needed things ( I need some programs ) with the image.

In AMD64XPSP2Rhein I change the ntdetect.com against the modified one.
I change the USB*.sys files against them from XP SP1.
I delete the driver intelppm.sys in Driver cache. This intelppm.sys has to be renamed in system32\drivers.
I also change there the USB*.sys files against them
from XP SP1 . I use winrar to unpack the sp2.cab file and CABPack to pack it again.
I delete in Registry the key CriticalDeviceDatabase and put the CriticalDeviceDatabase from Tutorial 3 for Windows Embedded in.
I put in inf folder the USB*.inf files with System Reserved and Start = 0 in it (see Tutorial3).
I also change in registry the entries for USB* as described in Tutorial 3.

I delete key MountedDevices. This step should not be done if you use a USB stick, because then it can happen, that your USB device gets the drive letter E:\ (for example).

Now I am copying the files and folders to the WD160BB USB harddisk.

ntldr, ntdetect.com and boot.ini copy not, because they are there and must not be overwritten!!!

I connect it to the AMD D1607 Siemens compi.

Yeahh, it boots at once to Desktop.

Now I change the IDE driver. Go to Device Manager and there IDE Controller.
Rightclick on Bus Master IDE-Controller. (Via or Intel or whatever)
Update driver, choose for advanced users, dont search, choose Standard IDE Controller. Thats all.
Now, Standard IDE Controller can be seen in the Device Managers.

Your generic XPSP2 should be ready. I test and compare it now with the VMware solution.
The whole process lasts only 2 hours.

Nice to hear from you
Dietmar.


Test on next compi without any modifikation of this image: Notebook Acer Extensa 4102WSXGA+
This is with Intel M processor: OK, solved. (WAAAAOOOHH)
It asks for intelppm.sys hihi...but I do not give it
I changed the IDE Controller there also against the generic one. All hardware is detected and installed.
For first only from original XP SP2 !!!
Reboot of the notebook: All ok.

Now, without any modification, connecting the USB WD160BB harddisk back to the first compi AMD D1607
This is the hardest test of all: OK, solved: no amnesia is seen, no driver was loaded, the USB drivers
in devicemanager seems to have been changed by a ghost...hihi


Test on next compi without any modification: Shuttle Barebone SB61G2 V3: OK, solved. Waaaaoooh...
I also change there the IDE controller against the Standard IDE controller.

Next Test: ASUS P4C800-E deluxe:OK, solved...Yippiiieheh, this here is TUTORIAL 6.
I also change there the IDE controller against the Standard IDE controller.

The task, how to build a generic XP SP2 image has been done.
I will test some other compis, but I think that they all work.

Nice to hear from you
Dietmar

EDIT2: You can rename the processor driver back to intelppm.sys in system32\drivers.
After that, restart your compi (must be an Intel machine for this) or you get BSOD.
Go to the registry to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor
and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm .
Change in both the 'Start' value to '4'.
After this you have to rename in system32\drivers intelppm.sys again to iintelppm.sys
or you got BSOD when you boot next time on an AMD machine. Funny thing, but true.
You receive a yellow questionmark in the devicemanager for processor.
But this has no bad sideeffekt as far as I know.
Now, the always appearing message, that new hardware with missing intelppm.sys is found, is gone.

PS: Tutorial 7 will describe, how to do USB boot with a compi, that never heard anything about USB in his live.
I am in contact with Microsoft .

EDIT3: I noticed, that sometimes intelppm.sys also stays in dllcache. You can delete it there
or do the following:

I let intelppm.sys been installed. After that I disabled in the devicemanger the processors entry.
Then I go to WINDOWS\inf folder cpu.inf and set there starttype=4 for intelppm.sys and processr.sys.
I set Loadordergroup from... Extended Base... to ... Base also there.
Have a look in registry, whether there stands in Services also start = 4 and Group = Base
for intelppm and processr.

[abcslayer]

Hi Dietmar.
I believe in the generic solution. As your posted test machine configurations, I think all of them is ACPI (even APIC) compatible, what do you think if the generic image can work on non-ACPI? or bad ACPI BIOS (on old machine this is much happen).

[cesar_panter]

Hi Dietmar. do you have any luck with compis without boot usb bios support?
I know you are making some test with a pci card usb port

[Dietmar]

Hi abcslayer,

You can hit F5 (as I remembered) during setup of XP.
If you chose Standard Computer (or similar), no Acpi is installed.
I know from Embedded, that also without any ACPI you can do USB boot.


Hi cesar_panter,

I make a try with this in my next holidays at 20. Juli.
Here in Germany is Dawicontrol, who builds and sells SCSI cards with Bios.
It is possible, to use a CD or Floppy or PCI to USB slotcard with a USB (!) bios.
But this is music of the future and needs very hard work.

Nice to hear from you
Dietmar

[cesar_panter]

Hi abcslayer,

You can hit F5 (as I remembered) during setup of XP.
If you chose Standard Computer (or similar), no Acpi is installed.
I know from Embedded, that also without any ACPI you can do USB boot.
Hi cesar_panter,

I make a try with this in my next holidays at 20. Juli.
Here in Germany is Dawicontrol, who builds and sells SCSI cards with Bios.
It is possible, to use a CD or Floppy or PCI to USB slotcard with a USB (!) bios.
But this is music of the future and needs very hard work.

Nice to hear from you
Dietmar

Thanks for your prompt reply Dietmar