SP3, USB_Multiboot_10, KBdus.dll error

[ecommerce]

Thanks for all the hard work on this great project.

I searched the forum, FAQ, and google for information on this, but I still haven't been able to resolve it successfully. I don't think it has been covered before (at least, not directly). Forgive me if I've omitted something important; I've tried to be thorough, but I'm still learning here.

I am trying to install SP3. In the past I've had successful unattended SP3 installs using CD/HDD (on hardware, not just simulated). Being a beginner to USB installation, I pretty much followed the instructions in the guide here.

Settings (all done from within USB_Multiboot_10):

HP USB format tool (NTFS, 4GB andisk U3 Micro flash drive)

[uSB stick] for drive type

[C:\SP3] for XP source (YES to custom winnt.sif and $OEM$, unattended)

[K:\] for USB target

[YES] for copy LANG/WIN98X (actually I tried both yes and no)

[C:\MULTI_CONTENT] for USB content source (acutlly I tried with and without these extras)

[b_ini_XP_Setup_boot.ini]

[w_sif\Current_winnt.sif]

[C:\SP3\$OEM$]

yes to "copy XP + EXTRA sources to USB-Drive"

yes to "Make USB-stick in XP Setup to be Preferred Boot Drive U:"

Multiboot finished without errors.

First install (failed):

I installed to an 8GB RAID-0 drive, Gibabyte 965P, Intel Pentium D 805 with no other HDD/optical drives/card readers connected. This attempt failed in Text-mode setup (at the very end of the drivers being loaded, but before format/partition) due to missing raid drivers for the HDD.

Second install (failed):

I fixed the RAID driver problem by copying a raid driver (jraid.sys) to K:\$WIN_NT$.~BT\ and modifying TXTSETUP.sif. On this installation, I can enter Text-mode setup and drivers are correctly loaded. But before I get to the format/partition screen and error message comes up: "Setup cannot load the keyboard layout file KBdus.dll".

From what I could find off google, this is not a problem with a missing or corrupt KBdus.dll file. Microsoft says in Q239722:

This behavior occurs when all drive letters are already used and assigned to existing disk partitions, because the CD-ROM drive is the last device to be assigned a drive letter by Mount Manager (MountMgr). After you start from the Windows 2000 installation CD-ROM, MountMgr queries your hard disks and assigns drive letters to all partitions that exist. If your computer contains more than 24 partitions, MountMgr cannot assign a drive letter to the CD-ROM drive to continue Setup.

There is also another article from Microsoft which says:

This behavior occurs because the system does not have any rights (Access Control Lists [ACLs]) to the root of the volume on which the $Win_nt$.~bt folder is located.

Of course, both these refer to Windows 2000 which I am not using. BUt they shed some light on what might be happening.

Third install (semi-successful, but not optimal):

The first MSN article makes me think that setting the USB drive to U: is the problem. I redid my flash drive using USB_Multboot_10 again, but this time I changed the final setting to [NO] " For Mixed SATA/PATA Config: Don't change migrate.inf". On this installation, I went through the Text-mode setup without a problem (no RAID driver or KBdus.dll problems). Problem is, the HDD is listed as D:\ and the USB stick is listed as C:\ (at Text-mode setup's format/partition screen). Therefore, SP3 is being installed to D:\ (which I could live with, but this is not ideal).

Fourth install (failed):

In order to install SP3 to C:\, I tried this from the FAQ (Q&A #13): enter Text-mode setup, partition the HDD (which is not listed as C:\), quit using F3, reboot, enter Text-mode setup again (at which point, the drive should be set to C:). I did this--enter Text-mode setup, partition HDD (the one listed as D:\), quit via F3, reboot, and re-enter Text-mode setup a second time. But now, on the second Text-mode setup, I get this error (before the Format/Partition/Install screens): "Setup cannot load the keyboard layout file KBdus.dll".

I'm really at the limit of my technical ability here. I don't need anything particularly fancy--I just want to get SP3 onto my C:\. Has anyone else resolved this issue?

Thanks.

Edited July 25, 2008 by ecommerce

[ilko_t]

Hi,

Apart from copying the missing driver to ~BT folder you need to add a few lines to TXTSETUP.SIF in root, or the driver will NOT be used.

Did you do that?

There are other options to supply the missing driver:

1) F6 and floppy disk

2) grub4dos and floppy image of the disk with drivers

3) Integrating it to your source with tools like nLite

4) Slipstreaming BTS mass storage drivers pack

And a few other methods which are a bit more complicated to mention.

Try first this.

I guess without the proper driver being used you installed Windows on your USB stick, hence the error about HAL.DLL. Are you sure that your HARD DISK was displayed when you got past Text Mode? What drive letter each hard disk and USB stick got?

Edited July 25, 2008 by ilko_t

[ecommerce]

Ilko--

Thanks for the input. I guess I didn't make things clear. I already solved the problem with the RAID drivers. My TXTSETUP.sif file is already customized and the jraid.sys file has been added appropriately. Once I took care of the RAID issue, my main problem comes up (which is the KBdus.dll error).

I believe this problem is coming from the final step in USB_Multiboot_10 where the user is asked to "Make USB-stick in XP Setup to be Preferred Boot Drive U:". When I do this, I get stuck in Text-mode setup with this error message: "Setup cannot load the keyboard layout file KBdus.dll". This happens before any oppportunity to format/partition drives. As I said in the OP, I think the problem is coming from Windows (or MountMgr) not being able to assign a drive letter to USB flash drive (see MSN article Q239722).

I can solve this problem by setting USB_Multiboot_10 to [NO] " For Mixed SATA/PATA Config: Don't change migrate.inf". With this setting, I avoid the KBdus.dll error and can get to the Text-mode setup format/partition screen. From here, the computer registers 2 drives: the USB stick and the HDD (listed as D:\). I can successfully partition, NTFS format, and install windows (well... at least the Text-mode setup portion). BUT I believe this solution is suboptimal since I am forced to install Windows to D: (versus C:). Like I said in the OP, I could live with this, but it isn't ideal.

I think that answers your questions, but for completeness:

-Question 1-add a few lines to TXTSETUP.SIF in root, Did you do that?

- Yes (RAID drivers are not an issue)

-Question 2-Are you sure that your HARD DISK was displayed when you got past Text Mode?

- Yes (I definitely installed to the HDD and not the USB stick)

-Question 3-What drive letter each hard disk and USB stick got?

- USB stick is labeled as C:\ (at the Text-mode setup screen)

- HDD is labeled as D:\ (at the Text-mode setup screen)

Anyone else with suggestions (or questions regarding what I did/didn't do)?

Thanks

Hi,

Apart from copying the missing driver to ~BT folder you need to add a few lines to TXTSETUP.SIF in root, or the driver will NOT be used.

Did you do that?

There are other options to supply the missing driver:

1) F6 and floppy disk

2) grub4dos and floppy image of the disk with drivers

3) Integrating it to your source with tools like nLite

4) Slipstreaming BTS mass storage drivers pack

And a few other methods which are a bit more complicated to mention.

Try first this.

I guess without the proper driver being used you installed Windows on your USB stick, hence the error about HAL.DLL. Are you sure that your HARD DISK was displayed when you got past Text Mode? What drive letter each hard disk and USB stick got?

Edited July 25, 2008 by ecommerce

[ilko_t]

Now it's way clearer, thanks.

Try to rebuild the USB stick and change USB disk type to HARD DISK.

What letters each drive got? USB stick should be D. If it is then continue Setup and tell results.

If it is C again, then you might have to try with another USB stick, unless something else comes up.

Edited July 25, 2008 by ilko_t

[wimb]

Is it because you use U3 stick ?

Try simple stick, so that your HDD wll get drive letter C

[ecommerce]

Ilko--

OK. I'll try again. Thanks.

Now it's way clearer, thanks.

Try to rebuild the USB stick and change USB disk type to HARD DISK.

What letters each drive got? USB stick should be D. If it is then continue Setup and tell results.

If it is C again, then you might have to try with another USB stick, unless something else comes up.

Wimb--

Thanks. I think U3 just refers to the name of the USB stick or whatever programs Sandisk put on the USB stick. Of course, I just formatted over whatever they had there. I think, then, that what I have is "just a simple USB stick" and nothing more. I could be wrong, but I really don't think the problem is with the USB stick--I think it has more to do with how Text-mode setup labels the drives. What do you think?

Is it because you use U3 stick ?

Try simple stick, so that your HDD wll get drive letter C

[JoeMSFN]

Thanks. I think U3 just refers to the name of the USB stick or whatever programs Sandisk put on the USB stick. Of course, I just formatted over whatever they had there. I think, then, that what I have is "just a simple USB stick" and nothing more. I could be wrong, but I really don't think the problem is with the USB stick--I think it has more to do with how Text-mode setup labels the drives. What do you think?

U3 is a way of having the system tray menuing system autorun. Since older Win versions (and maybe even XP and Vista) can't autorun from anything other than a CD/DVD, they "fake" a CD drive to autorun the menu.

Simply formatting will not get rid of the CD drive.

There may be other ways to do this, but the only way I know to "get rid of" the fake CD drive is to run the U3 removal tool (not sure of the real name). If it's a Sandisk, I think you can reverse the removal if you want the CD drive back. If it's another brand product, removing the fake drive is permanent. (unless there's been clever hacks to do it).

I have succesfully "un-U3ed" my Sandisk. It's wonderful! because the annoyance is gone. What annoyance...? Read on.

I find the fake CD drive an annoyance on slow computers, since it has to install two devices for one physical piece of hardware. Although there are clever folk who have generously contributed various hacks to put a custom ISO on the U3 stick so you can have an auto running software of choice. Also the custom ISO has a very restricting size limit.

Edited July 25, 2008 by JoeMSFN

[ecommerce]

Ilko--

Thanks again. Setting USB_Multiboot_10 to USB HDD doesn't really change anything. Thanks for your help my friends (and I hate to disagree), but I really don't think the problem is with the USB stick. I think things lie more towards modification of migrate.INF. Anyone else with a suggestion?

Now it's way clearer, thanks.

Try to rebuild the USB stick and change USB disk type to HARD DISK.

What letters each drive got? USB stick should be D. If it is then continue Setup and tell results.

If it is C again, then you might have to try with another USB stick, unless something else comes up.

[ecommerce]

JoeMSFN--

ahh... I see (and bow to your knowledge). I guess it might be helpful to un-U3 my USB stick. Do you recommend using Sandisk (or U3's) removal tool available at their website or something else?

Thanks

Thanks. I think U3 just refers to the name of the USB stick or whatever programs Sandisk put on the USB stick. Of course, I just formatted over whatever they had there. I think, then, that what I have is "just a simple USB stick" and nothing more. I could be wrong, but I really don't think the problem is with the USB stick--I think it has more to do with how Text-mode setup labels the drives. What do you think?

U3 is a way of having the system tray menuing system autorun. Since older Win versions (and maybe even XP and Vista) can't autorun from anything other than a CD/DVD, they "fake" a CD drive to autorun the menu.

Simply formatting will not get rid of the CD drive.

There may be other ways to do this, but the only way I know to "get rid of" the fake CD drive is to run the U3 removal tool (not sure of the real name). If it's a Sandisk, I think you can reverse the removal if you want the CD drive back. If it's another brand product, removing the fake drive is permanent. (unless there's been clever hacks to do it).

I have succesfully "un-U3ed" my Sandisk. It's wonderful! because the annoyance is gone. What annoyance...? Read on.

I find the fake CD drive an annoyance on slow computers, since it has to install two devices for one physical piece of hardware. Although there are clever folk who have generously contributed various hacks to put a custom ISO on the U3 stick so you can have an auto running software of choice. Also the custom ISO has a very restricting size limit.

[ilko_t]

There is not much we do to migrate.inf, we use it to:

1) make the USB disk write-protected during Text mode Setup, works for XP SP2 only, possibly for SP3 too.

and optionally-

2) to preassign drive letter to the USB disk

If Setup fails with those errors when you preassign drive letter and gives letter C to your USB disk when letter is not preassigned, then look the problem in the USB disk itself, in particular this 'dual' mode CD/HD.

There was a possibility that USB stick was seen as FIXED disk, but you ruled it out.

So yes- using another, simple stick or removing U3 from yours should help.

[ecommerce]

Ilko, JoeMSFN, Wimb,

You all seem to be going down the same road. Sorry for my stubborness that the problem is elsewhere--I really am quite ignorant of some of these things. I will try to remove the U3 or get another USB stick. I'll let you know what happens (...well, maybe I'll have dinner first).

Thanks again

There is not much we do to migrate.inf, we use it to:

1) make the USB disk write-protected during Text mode Setup, works for XP SP2 only, possibly for SP3 too.

and optionally-

2) to preassign drive letter to the USB disk

If Setup fails with those errors when you preassign drive letter and gives letter C to your USB disk when letter is not preassigned, then look the problem in the USB disk itself, in particular this 'dual' mode CD/HD.

There was a possibility that USB stick was seen as FIXED disk, but you ruled it out.

So yes- using another, simple stick or removing U3 from yours should help.

[jaclaz]

The error you report is "strange".

Following for the moment you train of thoughts (as I haven't a better alternative one right now ), would it be possible that it is the U:\ that creates problems?

Can you manually edit the migrate.inf (and possibly other files referencing to U:\ ) to a "lower" letter, say E:\ and see what happens?

jaclaz

[jaclaz]

Double posted, sorry.

jaclaz

Edited July 27, 2008 by jaclaz

[ecommerce]

Jaclaz--

I did try manually editing migrate.inf to change the USB drive from U: to somehting else, but that did not solve the problem. I can't remember the exact result, but it was either the KBdus.dll error or an inability to install to C:\.

Thanks

The error you report is "strange".

Following for the moment you train of thoughts (as I haven't a better alternative one right now ), would it be possible that it is the U:\ that creates problems?

Can you manually edit the migrate.inf (and possibly other files referencing to U:\ ) to a "lower" letter, say E:\ and see what happens?

jaclaz

[jaclaz]

If the problem is that of the KB, with the stick set as U:, you need anyway to have V:, W:, X: ,Y: and Z: for the CD-ROM part to (maybe) get "out of the 24 assigned devices".

I would try two things:

1) try with a SP2 source, to make sure that it is not something SP3 related

2) try editing MkMigrateInf2.cmd, changing this line:

set MigrateDrive=U:

to:

set MigrateDrive=E:

(or another "low" letter)

jaclaz